8086:0166 [Toshiba Portege Z935-ST4N03] cannot boot Ubuntu ISO image off USB stick

[JenniferHodgdon]

Somehow (and I cannot remember what was involved), after purchasing this laptop
[Toshiba Portege Z935-ST4N03]
in June of 2013, I was able to install Ubuntu from a USB drive, and have set up a dual-boot system with Windows 8 and Ubuntu.

However, in testing of another bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214180 I have been asked a couple of times to download an Ubunto development ISO image, boot into it, and see if the suspend-resume problem described there has been fixed.

This machine does not have a CD/DVD drive, so I made a USB stick, but I was unable to boot off the USB in August and again recently in December of this year, and I was asked in that bug to report the booting problem separately using the terminal "ubuntu-bug linux" command, so here I am.

Here are the details of my latest attempt:

a) I downloaded the ISO from http://cdimage.ubuntu.com/daily-live/current/ labeled

 trusty-desktop-amd64.iso 03-Dec-2013 07:49 884M Desktop image for 64-bit PC (AMD64) computers (standard download)

and used the Startup Disk Creator utility on my desktop machine (which is running the 12.0-4 LTS version of Ubuntu currently) to create a startup USB stick from it.

This is almost certainly the same Startup Disk Creator utility I used when I originally set up my computer in June, but it is probably a different USB stick.

b) Following the instructions on
https://help.ubuntu.com/community/UEFI
(because I do have UEFI on this computer), I also verified that I have Secure Boot disabled in the BIOS (that was already the case) and that RapidStart Technology is disabled (that was also already the case). And I set the BIOS to boot off USB first. I am booting in UEFI mode.

c) I then attempted to boot my Toshiba Portege laptop off that USB stick. I have USB as first in boot order (and I also tried by hitting F12 during bootup and manually selecting to boot off the USB stick) (and I tried all 3 USB ports on the computer, just in case they behaved differently, because I think one is USB-3 and the other two are USB-2).

In all cases, I got an error message that was too quick to see, and then ended up at my normal hard disk (well, SSD disk) boot menu, where I could boot normally (not off the USB in other words).

d) By filming the bootup sequence with my digital camera, I was able to freeze the frame where the error message appeared and read it. I attached a screen shot in that other issue, and I think the message says (I'm not entirely sure about the first line, as it was a bit blurry):

Could not get fio for li->DevIceHandle: 2
Failed to find fs
Failed to load image
Failed to find fs
Failed to load image
Press any key to continue...

I will also attach the screen shot here.

e) I was able to use the USB stick to boot my desktop machine. It does not use UEFI, but at least I was able to confirm that the USB stick is bootable and works as a "Live" version of Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-27-generic 3.8.0-27.40
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jhodgdon 2208 F.... pulseaudio
CurrentDmesg:
 [ 9.616245] postgres (1483): /proc/1483/oom_adj is deprecated, please use /proc/1483/oom_score_adj instead.
 [ 9.960883] init: anacron main process (1384) killed by TERM signal
 [ 11.475801] init: plymouth-stop pre-start process (1885) terminated with status 1
Date: Wed Dec 4 08:07:02 2013
HibernationDevice: RESUME=UUID=83309235-54d3-42b7-92d8-7fac594f6e68
InstallationDate: Installed on 2013-06-17 (169 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MachineType: TOSHIBA PORTEGE Z935
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=UUID=cc61d39a-8b97-457b-88b2-710d49656f9f ro acpi_backlight=vendor
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-27-generic N/A
 linux-backports-modules-3.8.0-27-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/04/2013
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 6.70
dmi.board.asset.tag: 0000000000
dmi.board.name: PORTEGE Z935
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.70:bd04/04/2013:svnTOSHIBA:pnPORTEGEZ935:pvrPT234U-07101X:rvnTOSHIBA:rnPORTEGEZ935:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE Z935
dmi.product.version: PT234U-07101X
dmi.sys.vendor: TOSHIBA

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Do you also see this issue if you try an earlier release, like Saucy or Raring?

[JenniferHodgdon (yahgrp)]

Back in August 20, I downloaded the daily build and had the same problem. I think that would have been Saucy (pre-release). If you can point me to other specific ISO images you'd like me to try, I'd be happy to do so.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[JenniferHodgdon (yahgrp)]

I don't see how this bug can be tested using this method. Can someone please add the bug-stop-nagging tag? I do not think I have permission to do that.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]