STEPS TO REPRODUCE 1. Boot Kubuntu 24.04.1-desktop-amd64 from USB stick 2. Install to internal SATA HDD or external USB mechanical HDD 3. Try to boot from internal SATA HDD or external USB HDD OBSERVED RESULT Black screen / or drops to grub rescue prompt / or "Reboot and select proper boot device" EXPECTED RESULT Boots into desktop NOTES: Hardware: - Intel Dual-Core E5400 CPU @ 2.7GHz - 4GB RAM - Using onboard video - 256MB system ram allocated - Successful checksum of downloaded Kubuntu-24.04.1.ISO - Tried installing using 1x generic 16GB USB stick (Win10 installer - rufus) - Tried installing using Sony 32GB usb stick (Win10 - baleno? etcher) - Same results both install media - Install system passes 100% memtest check - Install system survived 1Hr+ stress-ng test (from within live USB boot environment) Software OS Version - Kubuntu 24.04.1 Kernel 6.8.0-41-generic
Seems to be related to ?failed? Grub install? (unsure - has dropped me to grub rescue multiple times).
Created attachment 173672 [details] Boot error message file:///home/elroy/Downloads/reboot-select-proper-boot-device.jpg
Created attachment 173673 [details] Grub rescue attempt - poorly
Created attachment 173674 [details] Grub rescue
Created attachment 173675 [details] Just before install Confirmation
Created attachment 173676 [details] Erase Disk option chosen Chose "Erase Disk" option all times. NOTES: In the past, have successfully installed multiple *ubuntu using Manual install - but under non-UEFI BIOS scenarios. I chose "Erase Disk" option, so it would auto-do everything for me, as I don't have much experience with UEFI etc installs. One thing I did find that seemed weird, was it only chose to create one great big partition - no "boot" or UEFI / EFI partitions, that I've seen elsewhere.
Live USB Install system does need the "safe graphics mode" to successfully boot - but I believe this is unrelated other GPU / driver issue
I have had one successful install to USB-HDD - out of about 12x total install attempts.
Thank you for the bug report! This is a (K)ubuntu issue and does not seem to directly involve KDE software; please report it at https://bugs.launchpad.net/ubuntu