🦋⃟💙 This city makes me feel so small A million people in this town But I could scream without a sound So I get high to pass the time Talk to someone I met online To make myself feel less alone

  • 760 Posts
  • 3.49K Comments
Joined 2 years ago
cake
Cake day: September 28th, 2023

help-circle







  • Arch recently moved legacy Nvidia support to the AUR. That might have left you with a broken install.

    You would probably have an easier time with a mainstream distro like kubuntu LTS. They tend to be better suited for older equipment.

    It can be challenging to fix the bootloader once it dumps you into this situation. On a UEFI secure boot installation the EFI shim is responsible for allowing the modules to load each time there’s a change.

    If you have a legacy MBR installation the Nvidia modules might just need to be reinstalled. This was a common issue when updating the kernel.

    Edit: switching it to the Nouveau drivers might get you back into the OS. Would need to tweak your environment from a working one with a live environment potentially.






  • This issue feels like a stack problem, peeling back the layers.

    Most of the information I’m finding about this flavour of arch doesn’t reveal much about libreboot’s role in this issue. I’m not familiar with the device and online results are vague about what the specs are.

    My main thought is If you’re using a Nvidia GPU or other proprietary software to run hardware, did you reinstall its software after changing the kernel? I’m not sure if your distro automatically does that for you.

    Are you using shim for anything?

    I’m wondering if something went funny with your mok enrolment or if it failed to use the key to sign the module? Could test by temporarily disabling secure boot. (But would continue to fail if not the problem; such as the modules are compiled against the wrong kernel)

    My other thought was that I’m under the impression that endeavourOS uses pinned versions and swapping out the kernel puts you in an undefined state.

    You might have some luck jailing it on an working os with the configuration you desire and regenerating the boot files. Same idea as using the rescue environment on a livecd. The last time I had this idea it was a big waste of effort. When I realized I could just roll back using a backup.

    Edit: maybe the drive is dying try testing it?