Read on Twitter
For, err, no apparent reason, trying to customize a #Kubuntu (Bionic) Desktop #LiveCD in order to get it to work on an #Intel #NUC8i7HNK (just like that #Fedora Rawhide pendant which simply works OOTB) for a couple of days now suddenly reminded me of this:
For the record: I'm not (primarily) blaming the hardware here…
Once you find the required parameters for use with "mkisofs" (which are not mentioned in the document you likely refer to first, namely help.ubuntu.com/community/Live…), you're able to re-image an #Ubuntu/#Kubuntu daily #LiveCD with #UEFI support: askubuntu.com/a/504750
The problem starts the moment you want to replace the files vmlinuz/initrd.lz, though. Even if you follow the (seemingly more detailed) German howto wiki.ubuntuusers.de/LiveCD_manuell… apart from the last step, the resulting image ("dd"'d onto an USB flash drive) will boot… in a VM only.
Even if you do not touch a single file related to GRUB, the Intel NUC happily ignores the flash drive (remember, w/o changing anything it would still boot). Why GRUB stops working altogether is a mystery to me; the boot menu should always come up, right?
The #KISS principle dictates that at one point it does not make sense to continue fiddling. The resulting "straightforward" solution in order to use a customized #Ubuntu/#Kubuntu #LiveCD? Boot a #Fedora #Rawhide #LiveCD, install, e.g., #VirtualBox, and boot your image there… 🤓
• • •
Missing some Tweet in this thread? You can try to
force a refresh
