this post was submitted on 28 Oct 2025
502 points (98.5% liked)

Linux Memes

996 readers
1 users here now

A community for posting memes relating to linux!

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP



founded 2 years ago
MODERATORS
(page 2) 41 comments
sorted by: hot top controversial new old
[–] henfredemars 50 points 1 week ago (2 children)

Bootloader’s gone boss. Now what?

[–] iloveDigit@piefed.social 64 points 1 week ago (2 children)
[–] b_tr3e@feddit.org 25 points 1 week ago

Reboot from live image if you really need to.

[–] rem26_art@fedia.io 7 points 1 week ago (1 children)

every linux installation that was ever made was really about trying to break the uptime world record

[–] Sxan@piefed.zip -3 points 6 days ago (2 children)
load more comments (2 replies)
load more comments (1 replies)
[–] Winged_Hussar@lemmy.world 37 points 1 week ago (4 children)

Me learning Linux:

I have no idea what the difference between systemd-boot and grub.

Also, I'm not going to check which one is being used, I'll just remove the one I don't like

Linux:

Get after it chief

Why did I have both installed? No idea. Did I have to make and use a recovery USB? Absolutely.

[–] InnerScientist@lemmy.world 35 points 1 week ago (3 children)

Linux user seeing a 50% chance to uninstall their bootloader:

Let's go gambling!

load more comments (3 replies)
load more comments (3 replies)
[–] InnerScientist@lemmy.world 33 points 1 week ago* (last edited 1 week ago) (2 children)

I once redid the whole bootloader remotely.

I had a remote server that wasn't luks encrypted because I didn't do that some 3 years ago when setting it up.

So naturally I did the sane thing and kexec a live environment with ssh and a wireguard client, did an in-place encryption of the software raid disks, set up remote unlocking with VPN and rebooted.

And I still can't believe that it actually reconnected after that.

load more comments (1 replies)
[–] I2jgwh0hYtxrCZQ@lemmy.sdf.org 26 points 1 week ago (1 children)

Your system will break

So it is actually my system not Microsoft’s?

[–] iloveDigit@piefed.social 8 points 1 week ago

According to the windows logo face guy, I suppose

[–] Hadriscus@jlai.lu 13 points 1 week ago (23 children)

I so wish this were representative. I have been trying to install nvidia drivers on debian and doing so bricked my entire workstation lol. If you know anything about this don't hesitate to chime in btw

[–] ILikeBoobies@lemmy.ca 1 points 6 days ago (1 children)

Like the hardware or just the install?

A live usb would let you in to fix it

[–] Hadriscus@jlai.lu 1 points 6 days ago

The secureboot is borked apparently, which prevents me from booting anything. Fortunately I just had to disable it from the UEFI. It boots now! I have other issues but everything in time! I think I can fix them from a live image actually. Thanks for the help!

[–] WolfLink@sh.itjust.works 1 points 6 days ago (1 children)

SSH in and forcibly uninstall all Nvidia packages, then reinstall them fresh following Nvidia’s website.

At least this has worked for me on Ubuntu on several occasions.

[–] Hadriscus@jlai.lu 1 points 6 days ago

Thanks, the issue was with secureboot actually, I found how to disable it and I can boot again. As for nvidia I will wipe the disk from a live image and start over, I am not familiar enough with what you suggested to tackle it (for now...). Thanks a lot for the suggestion.

[–] Ziglin@lemmy.world 6 points 1 week ago (1 children)

No clue how to fix it. I had a similar issue and it fixed itself when I switched to endeavouros with i3.

[–] Hadriscus@jlai.lu 3 points 1 week ago (1 children)

Ok, thank you for the feedback still. You were able to install a different OS and boot into it normally?

[–] Ziglin@lemmy.world 2 points 6 days ago* (last edited 6 days ago) (2 children)

~~Yes, it was only after grub that the drivers were loaded and the kernel presumably panicked or at least nothing was displayed. Not sure if that is what you mean by bricked the entire workstation. If something broke before the kernel is loaded I doubt it was because of the drivers. If you want to keep your current Debian installation alive you can try to chroot into it from a live usb. Sorry if this is completely obvious to you but I really don't know what to expect based on your description.~~

Having looked at your other comments and the post you linked I too am intimidated. It looks as though you have access to your boot menu and bios though. I don't know what the upsides of secure boot are but I never turned it on on my current desktop PC. Maybe disabling it could help?

load more comments (2 replies)
[–] Skullgrid@lemmy.world 3 points 1 week ago* (last edited 1 week ago) (1 children)

I ran dpkg --get-selections to get all my installed packages and here's the installed Nvidia stuff. Try to install what's missing.

If you can't even get to command line, try to backup your data to an external source by using a live USB, and replace your debian with Pika OS, which has all the Nvidia stuff out the gate.

nvidia-alternative                              
nvidia-driver                                   
nvidia-driver-bin                               
nvidia-driver-libs:amd64                        
nvidia-driver-libs:i386                         
nvidia-egl-common                               
nvidia-egl-icd:amd64                            
nvidia-egl-icd:i386                             
nvidia-installer-cleanup                        
nvidia-kernel-common                            
nvidia-kernel-dkms                              
nvidia-kernel-support                           
nvidia-legacy-check                             
nvidia-modprobe                                 
nvidia-persistenced                             
nvidia-settings                                 
nvidia-smi                                      
nvidia-support                                  
nvidia-suspend-common                           
nvidia-vdpau-driver:amd64                       
nvidia-vulkan-common                            
nvidia-vulkan-icd:amd64                         
nvidia-vulkan-icd:i386                          

EDIT : from apt list --installed

libnvidia-allocator1/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-allocator1/stable,now 550.163.01-2 i386 [installed,automatic]
libnvidia-cfg1/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-egl-gbm1/stable,now 1.1.2.1-1 amd64 [installed,automatic]
libnvidia-egl-gbm1/stable,now 1.1.2.1-1 i386 [installed,automatic]
libnvidia-egl-wayland1/stable,stable,now 1:1.1.18-1 amd64 [installed,automatic]
libnvidia-egl-wayland1/stable,stable,now 1:1.1.18-1 i386 [installed,automatic]
libnvidia-eglcore/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-eglcore/stable,now 550.163.01-2 i386 [installed,automatic]
libnvidia-encode1/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-encode1/stable,now 550.163.01-2 i386 [installed,automatic]
libnvidia-glcore/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-glcore/stable,now 550.163.01-2 i386 [installed,automatic]
libnvidia-glvkspirv/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-glvkspirv/stable,now 550.163.01-2 i386 [installed,automatic]
libnvidia-gpucomp/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-gpucomp/stable,now 550.163.01-2 i386 [installed,automatic]
libnvidia-ml1/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-pkcs11-openssl3/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-ptxjitcompiler1/stable,now 550.163.01-2 amd64 [installed,automatic]
libnvidia-ptxjitcompiler1/stable,now 550.163.01-2 i386 [installed,automatic]
libnvidia-rtcore/stable,now 550.163.01-2 amd64 [installed,automatic]
[–] Hadriscus@jlai.lu 3 points 1 week ago* (last edited 1 week ago) (2 children)

Thanks a bunch for the advice but I can't start my system. That's regardless of the distro I try and install (I already overwrote Trixie with Bazzite... and now with Nobara). I followed this tutorial :https://fostips.com/install-nvidia-driver-in-debian-13/?amp=1

I explain the situation over here in more detail if by any chance this rings a bell with you :

https://forums.debian.net/viewtopic.php?t=164124

Cheers, appreciate the advice

[–] Skullgrid@lemmy.world 5 points 1 week ago (2 children)

you done fucked up the secure boot settings I think. I am in no way qualified to help you.

I don't even understand how you can install a different OS. Work off a live USB if you even can.

As far as I understand this is the bit you fucked up. btw, the images in the debian forum post just show "filename1.jpg" as text and don't display. post on !/c/linux4noobs@programming.dev

Step 2: Enroll MOK key for Secure Boot

Debian updates its kernel (minor versions) regularly for security updates and fixes. Without re-building kernel modules every time, DKMS is used, which however needs be signed for secure boot using a machine owner key (MOK).

1. First, run the command below to check if Debian was installed with UEFI boot by running the command below in terminal:

ls /sys/firmware/efi

The command tells to list the /sys/firmware/efi directory content. If it says “No such file or directory”, then you have Debian installed as legacy boot.

2. Next, run command to check if secure boot enabled:

sudo mokutil --sb-state

If both UEFI and secure boot enabled (as the screenshot below shows you), then you need to run commands below one by one to create and enroll MOK key.

3. First, run the command below to manually generate a mok key.

sudo dkms generate_mok

Run sudo apt install dkms if the dkms command not found, and set a password for the key.

4. Next, run command to import the key:

sudo mokutil --import /var/lib/dkms/mok.pub

5. Finally, reboot your computer. At next boot, it should pop-up a screen (see the screenshot below), asking to perform MOK menagement.

There, just choose to Enroll MOK -> continue -> confirm -> enter password (you set when creating the key) -> reboot.

After enabled non-free repository and enrolled MOK key, you may then run the commands below to install NVIDIA driver.

First, install the kernel headers for DKMS:

sudo apt install linux-headers-$(dpkg --print-architecture)
[–] Hadriscus@jlai.lu 4 points 1 week ago

Thank you that's already a lead !

I did follow the instructions to the letter so not sure what I should have done differently

I am going to ask on the community you linked. Thanks again

[–] Hadriscus@jlai.lu 3 points 1 week ago* (last edited 1 week ago)

I just cross-posted my cry for help over there. Thanks again for the redirection. https://programming.dev/post/39832602

[–] dondelelcaro@lemmy.world 2 points 1 week ago (1 children)

Can't see the images in the forum, but is the kernel actually starting? (Does it get past grub? Does it get to grub?)

From your forum post it sounds like you're seeing a secure boot issue, which may require changing some bios settings. (Installing the non free driver definitely breaks secure boot.)

[–] Hadriscus@jlai.lu 2 points 1 week ago* (last edited 1 week ago) (2 children)

Hi, how do I check for that ? how do I recognize grub ?

Here is a crosspost of my thread from the Debian forums :
https://programming.dev/post/39832602

Thanks a bunch for stopping by...

load more comments (2 replies)
load more comments (19 replies)
load more comments
view more: ‹ prev next ›