I got into 157! 🥳 Thank you everyone for your help! It turns out that my case was weird for two reasons, so here are the steps if anyone has a similar problem:
(1) The grub menu was completely hidden for me by default, and I never got it up. (This was also the case for the other 160 error/bug reporter at #2128904. Maybe it affected those of us with Victoria rather than Virginia.) I had to work within the "grub>" command line the whole time, and I found these directions the clearest to follow: https://www.linuxfoundation.org/blog/blog/classic-sysadmin-how-to- rescue-a-non-booting-grub-2-on-linux --- Btw, Benno, thanks for the tip about leaving out "quiet splash nomodeset." I could see the process working! (Well, up to a point... lol...) (2) The "successful" 157 boot always ended with errors and a "BusyBox" command prompt with "initramfs." I figured out eventually I should type "Exit" to see more details on the errors. (Here is a great link about BusyBox/initramfs: https://ostechnix.com/how-to-fix-busybox-initramfs- error-on-ubuntu/ .) The initramfs report told me that there was no root file system! 😱 I was about to try booting from a live usb as William suggested, but I was afraid of data loss. By chance I happened to check whether I had got the partition name right for my root file back when I put it in the "grub>" command. I assumed I should use the "sda" nomenclature that is standard for Linux. It turns out that within "BusyBox" you can run commands to see your partitions, so I looked at them... and they weren't "sda" but "nvme-." So I went back to "grub>" and tried to boot into kernal 157 again using nvme- as the partition name, and the boot worked like a charm. I'm sure these must look like the dumbest newbie things to figure out. So thanks everyone for your patience. I guess it confirms what the #2128904 bug report says: "Recovery required understanding of GRUB, kernel parameters, and initramfs" and "Users without advanced Linux knowledge would be unable to recover their systems." Somehow I got lucky. 😅 I hope this helps others too! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2128729 Title: Kernel 5.15.0-160 boots without any video output (on AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128729/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
