Hey all recently decided to install slackware-current on my desktop and wanted to get some Nvidia drivers installed. So first thing was I blacklisted the nouveau driver by downloading the blacklist package with slackpkg.

I then rebooted and then it stopped at the part where it usually changes resolution. The system will just display the following forever.

Booted in to my installation media and just did chroot to uninstall the blacklist package and everything worked again. Tried adding nomodeset to my elilo.conf but that gave the same issue as when I blacklisted.

GPU is a RTX 3060

Any ideas on how I can blacklist the nouveau driver without hanging on boot?

Try:

• Leave nouveau alive
• Install nvidia driver.
• If nvidia install offers to blacklist nouveau, let it. (I can't remember if it does this.)
• If nvidia install does not blacklist nouveau driver, do it yourself before you reboot.

Another try: if you don't need any particular module being loaded at boot,
then an initrd.gz isn't needed anymore. The ext4 module is built in the -current generic kernel now.

It might be useful to include the option "nomodeset" in your bootloader or include it in your "/etc/modprobe.d/blacklist.conf" like this "options nouveau modeset=0". FWIW most systems will allow the "NVIDIA-foo.run" installer to do this for you if you approve. When in doubt, do it manually.

I ended up "fixing" it by building the nvidia drivers from slackbuilds, installing the nouveau blacklist package with slackpkg, and then changing my run level in /etc/inittab to 4. Confirmed the nvidia drivers are up and running on X11

However runlevel 3 is still broken and I would like to have that as an option

550 drivers? https://www.linuxquestions.org/quest...ml#post6490864 Try the nvidia_drm kernel module options I listed here.

Boot with grub. This is really the only situation where elilo is entirely broken -- when it isn't able to set up the console font on newer machines (I've heard it does, but it's black text on a black background). When you're not using nomodeset, eventually the kernel direct rendering console comes along and make a readable console, but when you are it's got to be set up correctly by the bootloader.

Thanks for the responses everyone, would this slackdoc be good to follow for getting grub installed?

It is a fairly easy process. OTB has a good video on how to get it setup during the Slackware installation process. He explains it around the 25 minute mark. You can always install it after you install slackware, but you will need to remove elilo first.
https://www.youtube.com/watch?v=OZeJd5JPQro&t=27s

I rather dislike being in a position juxtaposed to our BDKL, but I dislike Grub rather a lot and for several reasons. If you're familiar with lilo/elilo and especially if you multiboot, you should try rEFInd as it's syntax human readable and much like lilo. The learning curve is very substantially less than with Grub and rEFInd has directly edit function for configuration. No binaries or extra steps required. The documentation is quite good, too. In fact, much like how Patrick treats config files by including tips and examples, rEFInd has an excellent config file that is documented and exampled right in refind.conf.

It is also a trivial slackbuild.

1 members found this post helpful.

Grub definitely has a learning curve, but I have never found it to be as hard as its reputation in the Slackware community implies. Grub is my bootloader of choice and IMO the most feature rich and powerful and the one Slackware should be using, but If I had to use something else it would definitely be rEFInd.

I assume to uninstall ELILO I'd just need to remove the EFI/Slackware Directory and remove the boot entry with efibootmgr? Any other steps?

Edit: Ended up just taking a look at the eliloconfig script and it looks like that's all I needed to do. Booted with grub into runlevel 3 successfully. Will probably take a look at rEFInd as well when I get the chance, remember using it to dual boot in the past. Thanks again for the help everyone

1 members found this post helpful.

It's moot in this thread now since lzhiren has Grub working but it is possibly worth mentioning that I don't see Slackers complaining about how hard the learning curve is, and I certainly don't asses Grub that way. It does use arcane syntax but it's trrivial to check documentation or just web search the line in question. It seems to be a case of "One man's meat is another man's poison" in that what Daedra sees as a benefit. "feature rich", is part of what I don't like. It's a bootloader. All it needs to do is boot - "do one thing and do it well and pipe..."

However the deal breaker for me is having to run a binary instead of edit a human readable .conf file and know almost instantly if and where I've messed up. I prefer a nice KISS.

2 members found this post helpful.