Fails to boot

[claydoh]

The Swiss Army knife Mkusb may be able to properly make a boot drive for those mbr systems that won't boot to the newer ISO images (21.10 and newer, possibly earlier?) that now use grub2 to boot as opposed to isolinux
https://askubuntu.com/questions/1406...tead-of-a-bios

then there are these unintelligible gobbledygook pages
https://help.ubuntu.com/community/In...so2usb/isoboot
https://askubuntu.com/questions/1403...th-mbr-and-efi
.
But I think in your case this may be hardware-specific. The 22.04 changelogs mention some known issues involving MBR and slow boots from USB but no mention of it not being supported at all
https://discourse.ubuntu.com/t/jammy...se-notes/24668
look waaaayyyy down near the bottom

[claydoh]

22.04 boots for me on an ancient dual core Pentium desktop I managed to get powered on. Definitely no UEFI there.
I am definitely going to use something else for my planned NAS project this weekend. I could stuff some spinny hard drives in this thing (3) and velcro an ssd to the lid, but there is only room for two fans, one for the cpu and the other being the power supply
Toasty, I think

[Snowhog]

22.04 boots for me on an ancient dual core Pentium desktop I managed to get powered on. Definitely no UEFI there.

But how did you install 22.04? How did you burn the ISO and to what medium?

[claydoh]

Another thought is to try using tools that install custom boot loaders when "burning" , such as Unetbootin, Ventoy, and I believe Etcher (my go-to for a a gui tool).

This might explain why my old dusty machine booted my 22.04 stick, if one assumes that Bios booting is foobar in general. (I don't, yet).

I don't recall if i used dd or Etcher.

[MoonRise]

I've been using Ventoy for a while now. Haven't been disappointed. I do have two boot USB devices one is for MBR Secure Boot and the other MBR No Secure Boot. Depending on the machine, I use one or the other. To date, not issues.

[Snowhog]

Etcher (my go-to for a a gui tool)

I added the repository and downloaded/installed balena-etcher-electron. I'm flashing my 32GB USB thumb drive as I type. I wan't to see if the result is a bootable USB.

Added:
Finished. I closed the application and restarted my laptop. Nope. Same as originally reported. The screen shows GRUB, followed by GRUB Error: can't find command "grub_platform", and then the Grub Menu. I didn't even try to see if Kubuntu would launch from there; I know it won't.

So, balenaEtcher also doesn't produce a bootable USB thumb drive that will work 'as is' on my laptop with a newer *buntu ISO. I'll have to resort to the 'fix' detailed in https://bugs.launchpad.net/ubuntu/+s...491/comments/8

[claydoh]

Ventoy and Unertbootin most definitely add their own boot loaders (using isolinux etc, versus Ubuntu's' straight grub2), it doesn't look like Etcher does.
Again, this may be specific hardware related, and not a general lack of support.

I stripped the old HP system for parts for the NAS build - mainly chassis bits and psu items that match a less old i7 3770 box that definitely has UEFI, but a dead power unit.
If I can coax the dead psu to fire, Ill see if I can see what I used to boot the thing.


Nope, She's dead, Jim.

An old Dell latitiude D-something laptop I have laying around that boots to both (not sure if it has both bios and uefi, or a bios emulation running under uefi) does boot 22.04 when set to bios boot mode.

[Snowhog]

I'm not going to worry much about this. As a more experienced computer user, I did (and usually can) find the exact condition I'm experiencing, and a workable solution to 'fix' it. That's good enough for me.

Interesting post (#16) from https://bugs.launchpad.net/mkusb/+bug/1971119

I think since Ubuntu 22.04 Jammy being first LTS release with new Ubuntu installer / new Grub (started with Ubuntu 20.10 Groovy), many people are going to run into unbootable flash drive issue with non-UEFI machines.

Here's a person having exact same issue with 2 different machines at AskUbuntu:

https://askubuntu.com/questions/1406...tead-of-a-bios

[claydoh]

This sort of feels like the frustration I had when I installed my first NVME drive, and hit the Intel RST problem, which I only figured out *after* sending the original drive back and ordering a different one.