LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-09-2020, 12:37 PM   #1
xcom
LQ Newbie
 
Registered: Aug 2016
Location: Germany, Hanau
Distribution: Debian, Slackware
Posts: 11

Rep: Reputation: Disabled
How to remove nouveau from the initramfs on Slackware-current


Hello everyone,

last weekend reinstalled slackware-current (I messed up the last install) and wanted install the nvidia driver from the nvidia webpage. The only problem is, that I'm not able to completely disable nouveau.

I created the /etc/modprobe.d file named blacklist_nouveau with the content of
Code:
blacklist nouveau
options nouveau modeset=0
In addition I added the "nomodeset" to the grub cmd and updated the config. There was no modesetting anymore and the nvidia driver installed without a problem. But by accident I discovered the nouveau still is loaded, although you can easily remove it via modprobe -r. I did some research and as far as I understood, you have to rebuild the initramfs (via dracut on RedHat or update-ramfs on Debian/Ubuntu), but I can't manage to get this done under slackware. The mkinitrd doesn't have an option for this, has anyone tried this yet and can give me a hint on that?
 
Old 07-09-2020, 12:45 PM   #2
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 2,925

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
Try the blacklist package under --Current located in /extra/, labeled as xf86-video-nouveau-blacklist-1.0-noarch-1.txz
 
Old 07-09-2020, 12:51 PM   #3
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 525

Rep: Reputation: 333Reputation: 333Reputation: 333Reputation: 333
/usr/sbin/geninitrd

Last edited by Petri Kaukasoina; 07-09-2020 at 12:58 PM.
 
Old 07-09-2020, 01:12 PM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Check the output of /usr/share/mkinitrd/mkinitrd_command_generator.sh and see if it includes the nouveau driver in the modules. If it does, it might be as simple as just removing that module from the generated list of modules.
 
1 members found this post helpful.
Old 07-09-2020, 03:36 PM   #5
xcom
LQ Newbie
 
Registered: Aug 2016
Location: Germany, Hanau
Distribution: Debian, Slackware
Posts: 11

Original Poster
Rep: Reputation: Disabled
Thanks for your answers. Bassmadrigals hint solved it. After /usr/share/mkinitrd/mkinitrd_command_generator.sh I could create the appropiate ramdisk, now there is no nouveau.
 
Old 07-09-2020, 03:38 PM   #6
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 2,925

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
Quote:
Originally Posted by xcom View Post
Thanks for your answers. Bassmadrigals hint solved it. After /usr/share/mkinitrd/mkinitrd_command_generator.sh I could create the appropiate ramdisk, now there is no nouveau.
Excellent, so what does that mean for the blacklist package - perhaps Pat may need to look that over, as I am now confused as to the purpose of it .
 
1 members found this post helpful.
Old 07-09-2020, 03:57 PM   #7
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Quote:
Originally Posted by Jeebizz View Post
Excellent, so what does that mean for the blacklist package - perhaps Pat may need to look that over, as I am now confused as to the purpose of it .
It is because the nouveau is a module and having the blacklist prevents the system from loading the module. However, now that -current has switched to a generic kernel and needs an initrd to boot, if that initrd contains that module, the blacklist won't apply since it will be loaded before the system is booted enough to be able to read that file.

You could also try adding module_blacklist=nouveau to your kernel appends line in your bootloader. That might prevent the initrd from loading it, but I don't know for sure.

Last edited by bassmadrigal; 07-09-2020 at 03:59 PM.
 
1 members found this post helpful.
Old 07-09-2020, 04:00 PM   #8
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware14.2 64-Bit Desktop, Devuan 2.0 ASCII Toshiba Satellite Notebook
Posts: 2,925

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
Quote:
Originally Posted by bassmadrigal View Post
It is because the nouveau is a module and having the blacklist prevents the system from loading the module. However, now that -current has switched to a generic kernel and needs an initrd to boot, if that initrd contains that module, the blacklist won't apply since it will be loaded before the system is booted enough to be able to read that file.

You could also try adding [FONT="Courier New"]module_blacklist=nouveau/FONT] to your kernel appends line in your bootloader. That might prevent the initrd from loading it, but I don't know for sure.
That is an interesting answer, so to confirm by what you are stating the package is essentially obsolete I guess? I think maybe this could also be the reason for the missing penguins in that other thread? All I can say also about that - is on my bare metal install of 14.2 , as soon as I removed the nouveau driver by blacklisting via package, the penguins were there and never disappeared after a while, but now I am getting off topic.

So - as for the package, maybe it should be dropped in current and just a little hint in the readme adding that that blurb if one wants to blacklist it that way?
 
Old 07-09-2020, 04:59 PM   #9
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Quote:
Originally Posted by Jeebizz View Post
That is an interesting answer, so to confirm by what you are stating the package is essentially obsolete I guess?
I don't know about obsolete, but if an initrd is generated with the nouveau driver and the system is booted off that initrd, I don't think the blacklist file is used.

Quote:
Originally Posted by Jeebizz View Post
I think maybe this could also be the reason for the missing penguins in that other thread? All I can say also about that - is on my bare metal install of 14.2 , as soon as I removed the nouveau driver by blacklisting via package, the penguins were there and never disappeared after a while, but now I am getting off topic.
That's possible, but I am not familiar enough with Nvidia hardware to understand all that.

Quote:
Originally Posted by Jeebizz View Post
So - as for the package, maybe it should be dropped in current and just a little hint in the readme adding that that blurb if one wants to blacklist it that way?
Either way probably works. I know there are people who recompile their kernels or switch to the huge so they don't require an initrd. They could still benefit from the package. And if someone builds an initrd without the nouveau module, the package could also be useful.
 
Old 07-10-2020, 08:42 AM   #10
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,240

Rep: Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518
Quote:
Originally Posted by xcom View Post
I created the /etc/modprobe.d file named blacklist_nouveau with the content of
Code:
blacklist nouveau
options nouveau modeset=0
It is interesting to note, that is very similar to the one created by the NVIDIA installer if it detects the nouveau driver and you allow it to create it. This is what is created by the installer.
Code:
# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0
The xf86-video-nouveau-blacklist-1.0-noarch-1.txz package add this.
Code:
# Do not load the kernel nouveau dri module, since it interferes with both
# the nv and binary nvidia drivers.

blacklist nouveau
I don't see the purpose of that options line. My logic is, your are blacklisting nouveau, why give it options.
 
Old 07-14-2020, 11:45 AM   #11
xcom
LQ Newbie
 
Registered: Aug 2016
Location: Germany, Hanau
Distribution: Debian, Slackware
Posts: 11

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by chrisretusn View Post
It is interesting to note, that is very similar to the one created by the NVIDIA installer if it detects the nouveau driver and you allow it to create it. This is what is created by the installer.
Code:
# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0
The xf86-video-nouveau-blacklist-1.0-noarch-1.txz package add this.
Code:
# Do not load the kernel nouveau dri module, since it interferes with both
# the nv and binary nvidia drivers.

blacklist nouveau
I don't see the purpose of that options line. My logic is, your are blacklisting nouveau, why give it options.
Well, I had this from various Debian Forums, and they included even some aliases like lrm_nouveau. In Debian these contents of the blacklist file are mostly done by the packaged binary drivers from the non-free repository.
 
Old 07-15-2020, 04:48 AM   #12
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,240

Rep: Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518Reputation: 518
Quote:
Originally Posted by xcom View Post
Well, I had this from various Debian Forums, and they included even some aliases like lrm_nouveau. In Debian these contents of the blacklist file are mostly done by the packaged binary drivers from the non-free repository.
Thanks! That is interesting. Still, it seems weird, at least to me, that option line is included.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
dmesg says:[ 23.443246] nouveau 0000:01:00.0: msvld: unable to load firmware data [ 23.443256] nouveau 0000:01:00.0: msvld: init failed, pixelmatrix Linux - Hardware 2 10-05-2019 10:16 AM
[SOLVED] Problem starting Xorg Slackware-Current with nouveau Melke Slackware 14 05-04-2015 04:11 PM
slackware 14.1 from current tree 10/23 - kernel 3.10.17 bug (nouveau) marbangens Slackware 8 10-25-2013 11:50 AM
Slackware-current (2011-01-31) - Nouveau Driver - What do people think? rmjohnso Slackware 22 02-03-2011 04:57 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:22 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration