Hi! I do not know what updates went out yesterday, but discover automatically applied them. I rebooted for the offline update and now I cannot get into NEON at all. I can hit escape after my BIOS screen and get to the grub prompt, but there is no Ubuntu recovery mode or whatever apparently accessible. And while I have 15 years of Linux experience, I have no idea how to manually boot the OS through grub to get in and see what's wrong. So: what do I do here?

I have a grub prompt. If I do not hit escape and enter the grub prompt, the screen stays frozen on the BIOS logo (I think because the graphics stuff never initializes -- it does POST given I can get to grub).

You can't select a different kernel in the grub menus?

claydoh wrote:You can't select a different kernel in the grub menus?

Hi! That is precisely the point of my post -- there is no grub menu. I am sent directly to the grub console ( the command line ). It doesn't "boot" far enough to get a grub menu.

I hit escape key after my BIOS screen and I get a grub terminal. That's it.

Sounds a bit like drive IDs changed somehow (or missing, unplugged damaged?)

probably the simplest, quickest, and most common route to repair grub is using a live OS disk (Neon, Ubuntu)
https://www.fosslinux.com/4477/how-to-r ... -drive.htm

There is also this method, using Boot Repair
https://www.addictivetips.com/ubuntu-li ... air-guide/

Personally, When I have broken Grub, the first method has been more successful than Boot Repair, though it has been a few years since I have had to do this task.

claydoh wrote:Sounds a bit like drive IDs changed somehow (or missing, unplugged damaged?)

probably the simplest, quickest, and most common route to repair grub is using a live OS disk (Neon, Ubuntu)
https://www.fosslinux.com/4477/how-to-r ... -drive.htm

There is also this method, using Boot Repair
https://www.addictivetips.com/ubuntu-li ... air-guide/

Personally, When I have broken Grub, the first method has been more successful than Boot Repair, though it has been a few years since I have had to do this task.

Thank you for these links! I do not have a bios boot partition, and I do have an EFI system partition, so I think I am using that. I followed the first guide, which did not work (and errored out). The second recommends boot-repair, which I cannot use as I am in a bios-boot mode USB while my computer is UEFI booting so perhaps I cannot boot because computer is coming up in bios mode with UEFI OS

So, I went to explore my BIOS. I swapped which order things boot in (set priority for EFI System) and now it "boots". None of the GUI ever shows. But it is booted because I can ctrl+alt+f<num> and get a console. So I logged in. No new updates. No gui.

So, two questions: how do I see what is failing to launch? How do I boot UI manually?

The log on the screen of the "boot console" (tty0 ? ) is:

Code: Select all

[ 0.105670] x86/cou: SGX disabled by BIOS.
[1.093434] usb 1-1: device descriptor read/64, error -71
[    OK   ] Finished Hold until boot process finishes up.
[    OK   ] Finished Terminate Plymouth Boot Screen.


I got it "working" by running startx on the other tty I logged into. I found journalctl -b and -k and I could not find anything that looked interesting. It is very slow, like UI is handled through software rendering or something. I have never seen anything like this level of breakage.

The regular boot tty (where plasma should be) is still sitting there with the 4 log lines I posted.

OK, I am done with this because it is not putting errors anywhere I can find them. The live ISO seems to boot right up so an unmodified system is fine. OK.

During the NEON installer it asks if I want to replace my existing neon with fresh neon. Is the answer yes? That option does not warn it will nuke all of my data. Will it?

Yes

thunder422 wrote:Yes

Thanks! It did.

OK -- final determination: 5.13 kernel panics at boot. 5.11 does not.

I can reproduce this reliably on a totally fresh install of NEON from the latest daily ISO.

I am facing a similar issue where the screen is getting frozen, unable to open the boot menu using the bottle Pendrive. Please help me fix this issue!

You can find the frozen screen here: https://i.imgur.com/ZtBKQNq.png

rudrakshkarpe wrote:I am facing a similar issue where the screen is getting frozen, unable to open the boot menu using the bottle Pendrive. Please help me fix this issue!

You can find the frozen screen here: https://i.imgur.com/ZtBKQNq.png

Same problem for me!
After fresh install and update frozen screen.
Clearly something is very broken here.