[SOLVED] Blank screen, cant login after kernel upgrade to .38. Slackware 15.0, Nvidia

knet · 05-17-2022, 07:47 AM

I'm on runlevel 4 and It's fine before the kernel upgrade. I had a feeling that it might not work after the upgrade, i suspect possible conflict with kernel and my ancient gpu nvidia gk208.

Is it possible to disable nvidia on boot? from grub prompt?

edit
sorry im on mobile. Ive tried adding 'nomodset' and 'module_blacklist=nvidia' on kernel parameter but unsuccessful. My plan is to disble nvidia on boot and reinstall it if possible with adjustments for new kernel .38

Daedra · 05-17-2022, 08:08 AM

I assume "nomodset" is a typo and you meant "nomodeset"? A couple of things off the top of my head are you could ssh into your machine from another computer if you have that option and change back to runlevel 3 then fix the NVIDIA driver. Or you could use a live distro like Alien Bob's or partedmagic to boot the machine then mount the partition and change the runlevel to 3 to at least get to a bootable state so you can reinstall the drivers for the new kernel.

knet · 05-17-2022, 08:13 AM

Hi Daedra no it's not typo. I will try again and boot a liveusb distro. Thanks.

knet · 05-17-2022, 08:33 AM

Solved. The "nomodeset" (thanks to Daedra) parameter allowed me to login on runlevel 3 and reinstall Nvidia binary.

enorbet · 05-18-2022, 02:48 AM

Just FTR, although recent version of Slackware (AFAIK) no longer offer the old, awesome rescue boot prompt, you can still use the install media for rescue. At the 3rd prompt, the one that asks you to login as root (no passwd required) the installer does allow quick chroot rescue.

Code:

mount /dev/"Slackware Root" /mnt
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
mount -o bind /proc /mnt/proc 
chroot /mnt /bin/bash

and you're IN!

knet · 05-18-2022, 07:39 AM

Hi enorbet thank you how do I implement this and I mean when exactly? On the grub commandline prompt? The one with grub>?

edit
sorry you did mention "install media". So i boot the install media and then on the 3rd prompt i will have to run the commands above in that order?

elcore · 05-18-2022, 08:50 AM

Quote:

Originally Posted by knet

Hi enorbet thank you how do I implement this and I mean when exactly? On the grub commandline prompt? The one with grub>?

edit
sorry you did mention "install media". So i boot the install media and then on the 3rd prompt i will have to run the commands above in that order?

Don't worry about it, you don't need a live cd or chroot just to correct a grub typo.
Next time, you can select the relevant line on grub prompt and hit "E" which lets you edit the line, then just hit F10 to boot.
It's temporary edit, but it'd let you boot the system where you can correct grub configuration with an editor.

enorbet · 05-18-2022, 01:32 PM

My apologies if I confused you, I don't care much for Grub. I use LILO or rEFInd. However maybe copy that chroot process down someplace because it is very useful in nastier circumstances. Often the Slackware install media will work to chroot into many other distros, at least enough to be able to edit important files. This box has almost a dozen operating systems on it so I use chroot quite a lot. It can also be done from Liveslak but the install media is faster.

Note: FWIW one of the systems on here is OpenSuse which did by default install Grub. I boot it with rEFInd usually but Grub still works so I have options. I like redundancy.

knet · 05-18-2022, 10:18 PM

Quote:

Originally Posted by elcore

Don't worry about it, you don't need a live cd or chroot just to correct a grub typo.
Next time, you can select the relevant line on grub prompt and hit "E" which lets you edit the line, then just hit F10 to boot.
It's temporary edit, but it'd let you boot the system where you can correct grub configuration with an editor.

Yeah i have to learn the grub commands there. Thank you.

Quote:

Originally Posted by enorbet

My apologies if I confused you, I don't care much for Grub. I use LILO or rEFInd. However maybe copy that chroot process down someplace because it is very useful in nastier circumstances. Often the Slackware install media will work to chroot into many other distros, at least enough to be able to edit important files. This box has almost a dozen operating systems on it so I use chroot quite a lot. It can also be done from Liveslak but the install media is faster.

Note: FWIW one of the systems on here is OpenSuse which did by default install Grub. I boot it with rEFInd usually but Grub still works so I have options. I like redundancy.

I hear you and trust me I will save that chroot maneuver somewhere. Thanks again.