Live USB boot failure (SOLVED)

[Member orcrist]

This is the message I get when trying to boot from USB:

Could not get fio for li->DeviceHandle: Unsupported
Failed to find fs: Unsupported
Failed to load image \EFI\BOOT\grubx64.efi: Unsupported
start_image() returned Unsupported

My machine specs:

pan@LIFEBOOK-S761:~$ inxi -FG
System:    Host: LIFEBOOK-S761 Kernel: 5.0.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.32.0 
           Distro: Ubuntu 19.04 (Disco Dingo) 
Machine:   Type: Laptop System: FUJITSU product: LIFEBOOK S761 v: 10601115935 serial: <root required> 
           Mobo: FUJITSU model: FJNB225 v: B1 serial: <root required> UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.20 
           date: 04/26/2013 
Battery:   ID-1: CMB1 charge: 2.1 Wh condition: 2.4/62.2 Wh (4%) 
CPU:       Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP L2 cache: 3072 KiB 
           Speed: 831 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 797 2: 797 3: 797 4: 797 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.0.2 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.0.0-13-generic 
Network:   Device-1: Intel 82579LM Gigabit Network driver: e1000e 
           IF: enp0s25 state: down mac: 5c:9a:d8:e0:c8:35 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi 
           IF: wlp2s0 state: up mac: a0:88:b4:28:d5:bc 
           Device-3: Sierra Wireless type: USB driver: qcserial,qmi_wwan 
           IF: wwan0 state: down mac: c2:fb:28:09:c3:46 
Drives:    Local Storage: total: 298.09 GiB used: 155.48 GiB (52.2%) 
           ID-1: /dev/sda vendor: Toshiba model: MK3276GSX size: 298.09 GiB 
Partition: ID-1: / size: 19.23 GiB used: 10.89 GiB (56.6%) fs: ext4 dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 55.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 223 Uptime: 37m Memory: 3.59 GiB used: 1.00 GiB (27.9%) Shell: bash inxi: 3.0.33

The problem occurs when using antix version greater than 17.0, both 32 and 64 bit. The live USB stick is created by using the antix live usb maker from github.
Also when I create the stick from a snapshot of my running antix system installed on HDD.
It boots OK if I first create the stick from antix-17.0 ISO and then update it from e.g. 17.4 ISO, always using the usb maker program from github.

Thanks in advance for any help!

• This topic was modified 2 years, 12 months ago by orcrist.

[Forum Admin BitJam]

Helpful

Up

0

::

A Google(Could not get fio for li->DeviceHandle: Unsupported) shows other people have this problem on other distros. The first hit was for a Fujitsu Lifebook computer with Ubuntu.

I compared our antiX-17_x64-full.iso with antiX-17.1_x64-full.iso and there were no differences in the Grub bootloaders except in grub.cfg, help.txt and theme.txt. HOWEVER the Grub bootloader did get upgraded in antiX-17.4. So my guess is that 17.1 and 17.3 will also work for you.

If you can legacy boot then try that. otherwise, the only thing I can suggest is to make sure your BIOS/UEFI is up to date. Our dev fehlix may have other ideas. We were forced to upgrade Grub because the signing key of the older version was blacklisted or expired so there were a number of machines it couldn’t boot on even if secure boot was disabled.

There may be a fix in the Google search results but if you can’t boot legacy and you cant’t upgrade the BIOS/UEFI (or the upgrade fails to fix the problem) then I think the only answer might be that you have to downgrade Grub on the live-usb to get it to boot UEFI on your Lifebook. IOW, replace the directories /boot/grub and /EFI on the broken live-usb with the same directories on the working one. This may be confusing because the grub menu will list the wrong version of antiX unless you copy back in the original grub.cfg from the broken live-usb.

Context is worth 80 IQ points -- Alan Kay

[Forum Admin BitJam]

Helpful

Up

0

::

I contacted fehlix. He is having trouble getting an account here. He had a coupe of ideas:

1) use the command-line version of live-usb-maker and add the –gpt option. We were forced to use msdos partitioning as the default due to a stupid bug in some Dells but your machine may be expecting gpt partitioning to boot via UEFI.

2) You could trying making a live-usb with the dd-live-usb command which makes a standard “dd” live-usb. This will lack some of the nifty live-usb features we’ve added but it might at least boot.

Context is worth 80 IQ points -- Alan Kay

[Member orcrist]

Helpful

Up

0

::

Thank you BitJam for the interest. Sorry for my late response – I hadn’t had access to my computer for several days.

I’m afraid that my laptop does not boot UEFI, so the solutions that concern UEFI do not apply…

pan@Lifebook-S761:~
$ sudo efibootmgr 
EFI variables are not supported on this system.
pan@Lifebook-S761:~
$ 

I have nevertheless tried the –gpt solution but to no avail. I have also tried with the stick burned with dd. Same result.
I am always talking about the antiX-17.4.1_x64-full.iso – you are right, 17.1 and 17.3 do work. I have not tried to update my BIOS as I have no idea how to do it (I believe it should be done through Windows) and I am afraid to try, to be honest.

This is not a big problem for me as I can always burn the stick with a 17.3 version of antiX and then update it with the 17.4 version. But I can not be sure that the same will apply to the 19.0 version when it is ready.

• This reply was modified 3 years, 12 months ago by orcrist.

[Member stevesr0]

Helpful

Up

0

::

For what its worth,

My Fujitsu T4220 is having no problem with 17.3.1. I was told that as long as I updated regularly, it isn’t different than a 17.4 install.

This model is older than yours by ~ 5 years?

I am running a BIOS/GPT setup.

If I can try something for you, let me know.

stevesr0

[Forum Admin BitJam]

Helpful

Up

0

::

@orcrist, the antiX-19.a2 (alpha 2) is available now but I doubt you will be able to boot it. I suggest trying to change to legacy booting in the BIOS/UEFI. This is less perilous than a BIOS update.

Another idea would be to get an account on the MX Forums. There is an antiX sub-forum and fehlix has an account over there.

If worse comes to worse, I suppose we could make a version of antiX-19 with an older kernel.

Context is worth 80 IQ points -- Alan Kay

[Member orcrist]

Helpful

Up

0

::

So even after exactly one year I think that I ought to let know that the problem was solved.

Thanks a lot to the people who got involved.

[Author]

Posts