During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
Wondering if there is a more permanent way to remove/stop a kernel module from loading?
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
You need to reboot without the module loaded.
Module unloading is now unsupported for the most part in 2.6 kernels.
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
You need to reboot without the module loaded.
Module unloading is now unsupported for the most part in 2.6 kernels.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Am Do, den 01.07.2004 schrieb akonstam@trinity.edu um 19:56:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Aaron Konstam
Do you both - Greg and you Aaron - use the rivafb Riva framebuffer module to have framebuffer resolution on the console? I ask because I got the warning too when installing the new NVidia module, though I do not use the rivafb module, nor is it ever loaded.
Alexander
On Thu, Jul 01, 2004 at 08:22:11PM +0200, Alexander Dalloz wrote:
Am Do, den 01.07.2004 schrieb akonstam@trinity.edu um 19:56:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Aaron Konstam
Do you both - Greg and you Aaron - use the rivafb Riva framebuffer module to have framebuffer resolution on the console? I ask because I got the warning too when installing the new NVidia module, though I do not use the rivafb module, nor is it ever loaded.
Alexander
Ok here is the mystery. When I do a: lsmod |grep rivafb before running modprobe -r I do not see any rivafb loaded but the nvidia will not work until I remove that module. modprobe -r rivafb does not complain that rivafb is not loaded so I remain with a mystery which I have not really unraveled. My plan was to get nvidia to work and that happened. ------------------------------------------- Aaron Konstam Computer Science Trinity University One Trinity Place. San Antonio, TX 78212-7200
telephone: (210)-999-7484 email:akonstam@trinity.edu
On Fri, 2004-07-02 at 04:22, Alexander Dalloz wrote:
Do you both - Greg and you Aaron - use the rivafb Riva framebuffer module to have framebuffer resolution on the console? I ask because I got the warning too when installing the new NVidia module, though I do not use the rivafb module, nor is it ever loaded.
I had this warning as well. It's just a precautionary measure and unless you use a nVidia Riva 128, TNT or TNT2 card (quite old!) then there's no chance of having this module loaded.
Matt
On Friday 02 July 2004 00:37, Matt Hansen wrote:
On Fri, 2004-07-02 at 04:22, Alexander Dalloz wrote:
Do you both - Greg and you Aaron - use the rivafb Riva framebuffer module to have framebuffer resolution on the console? I ask because I got the warning too when installing the new NVidia module, though I do not use the rivafb module, nor is it ever loaded.
I had this warning as well. It's just a precautionary measure and unless you use a nVidia Riva 128, TNT or TNT2 card (quite old!) then there's no chance of having this module loaded.
Matt
Thanks for this thread, its reminded me to make the rivafb a module next time I build a new kernel. Its currently built in. Do I need anything special in my /etc/modprobe.conf for that?
On Fri, 2004-07-02 at 14:43, Gene Heskett wrote:
Thanks for this thread, its reminded me to make the rivafb a module next time I build a new kernel. Its currently built in. Do I need anything special in my /etc/modprobe.conf for that?
Gene, just specifying rivafb as a module in 'make {menu,g,x}config' should be all that's necessary to compile it as a module. FC kernels have it set as a module by default. Maybe a 'alias rivafb off' in /etc/modprobe.conf wouldn't hurt though.
Matt
On Friday 02 July 2004 05:51, Matt Hansen wrote:
On Fri, 2004-07-02 at 14:43, Gene Heskett wrote:
Thanks for this thread, its reminded me to make the rivafb a module next time I build a new kernel. Its currently built in. Do I need anything special in my /etc/modprobe.conf for that?
Gene, just specifying rivafb as a module in 'make {menu,g,x}config' should be all that's necessary to compile it as a module. FC kernels have it set as a module by default. Maybe a 'alias rivafb off' in /etc/modprobe.conf wouldn't hurt though.
Matt
Ok Matt, but not FC kernel. I've been running 2.6.x kernels since this was an rh8 install. Currently running 2.6.7-mm3 since -mm4 did something to the networking, reducing the pipe size to only 40k/sec, and it continues to plague -mm5.
This machine has no pieces of SElinux netfilter, etc in it as its behind a firewall about 3 courses of bricks thick. I had a fellow scan me from outside last night after giving him my ip address and he couldn't even find the closed identd port the commercial scanners occasionally find. I'd just closed another hole in the router config. But I'll set that alias in case it gets in the way of nvidia-6106. With it builtin, its ok, but when I switch, that should kill it completely.
Yeah, I like to bleed at times, but I just feed it to my glucose meter, I'm borderline :-)
On Fri, Jul 02, 2004 at 02:37:10PM +1000, Matt Hansen wrote:
On Fri, 2004-07-02 at 04:22, Alexander Dalloz wrote:
Do you both - Greg and you Aaron - use the rivafb Riva framebuffer module to have framebuffer resolution on the console? I ask because I got the warning too when installing the new NVidia module, though I do not use the rivafb module, nor is it ever loaded.
I had this warning as well. It's just a precautionary measure and unless you use a nVidia Riva 128, TNT or TNT2 card (quite old!) then there's no chance of having this module loaded.
Matt
What you say makes sense except unless I do a modprobe -r rivafb before starting X it does not start.
On Thu, 2004-07-01 at 10:56, akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
I have a better idea:
cat "install rivafb /bin/true" >> /etc/modprobe.conf
This will stop it from loading at all.
On Thu, Jul 01, 2004 at 12:03:36PM -0700, Florin Andrei wrote:
On Thu, 2004-07-01 at 10:56, akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
I have a better idea:
cat "install rivafb /bin/true" >> /etc/modprobe.conf
This will stop it from loading at all.
Ok I will try that but I am not sure why that works.
On Thu, Jul 01, 2004 at 12:03:36PM -0700, Florin Andrei wrote:
On Thu, 2004-07-01 at 10:56, akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
I have a better idea:
cat "install rivafb /bin/true" >> /etc/modprobe.conf
This will stop it from loading at all.
cat or echo?
# echo "install rivafb /bin/true" >> /etc/modprobe.conf
The comment made by the nVidia installer is that the module has been marked to be loaded dynamicaly. i.e. if any of it's functions are called.
It smells as if there is a symbol collision between the two driver objects and a reference to one of the riva symbols missing in the nVidia driver could cause the second driver to be linked causing a tangle.
If and only if you are having lockups it might pay to move the 'rivafb.ko' object out of the way so that it cannot be loaded no matter what. An error should signal that there was an attempt to load the unwanted object and that this was the problem. Do this only to one kernel and keep the other as a recovery path.
I expect that a stub symbol or some other code change will be added in a future package to make this problem a non-issue.
On Thu, 1 Jul 2004 akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
You need to reboot without the module loaded.
Module unloading is now unsupported for the most part in 2.6 kernels.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Modifying rc.sysinit is dangerous as your mods will be nuked in an upgrade. Better is /etc/rc.local or /etc/rc.modules. The latter is called early in the init process by rc.sysinit and the former is the last thing done at startup.
On Thu, Jul 01, 2004 at 04:35:31PM -0400, Matthew Saltzman wrote:
On Thu, 1 Jul 2004 akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
You need to reboot without the module loaded.
Module unloading is now unsupported for the most part in 2.6 kernels.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Modifying rc.sysinit is dangerous as your mods will be nuked in an upgrade. Better is /etc/rc.local or /etc/rc.modules. The latter is called early in the init process by rc.sysinit and the former is the last thing done at startup.
I will look again but I could not find anywhere that rc.local is called in the rc.sysinit script.
On Fri, Jul 02, 2004 at 08:17:25AM -0500, akonstam@trinity.edu wrote:
On Thu, Jul 01, 2004 at 04:35:31PM -0400, Matthew Saltzman wrote:
On Thu, 1 Jul 2004 akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
You need to reboot without the module loaded.
Module unloading is now unsupported for the most part in 2.6 kernels.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Is my face red and I am going to have to give back my sysadmin badge. Computers are supposed to consistant but right now things are really strange. 1. Yesterday the nvidia would not work without the modprobe -r rivafb. Today it does. 2. lsmod |grep rivafb gives no response. 3. But I can do: modprobe -r rivafb and get no error. If I do : modprobe -r joe I get an immediate error that joe is not a loaded module. 4. If I do modprobe rivafb then I can see the module with lsmod.
Go figure. I am confused.
On Fri, 2004-07-02 at 08:41, akonstam@trinity.edu wrote:
Is my face red and I am going to have to give back my sysadmin badge. Computers are supposed to consistant but right now things are really strange.
- Yesterday the nvidia would not work without the modprobe -r rivafb.
Today it does. 2. lsmod |grep rivafb gives no response. 3. But I can do: modprobe -r rivafb and get no error. If I do : modprobe -r joe I get an immediate error that joe is not a loaded module. 4. If I do modprobe rivafb then I can see the module with lsmod.
Go figure. I am confused.
You're right, and I get the same behavior. Fwiw, my new nvidia install went fine from the start and I've never attempted to unload rivafb.
On Friday 02 July 2004 09:17, akonstam@trinity.edu wrote:
On Thu, Jul 01, 2004 at 04:35:31PM -0400, Matthew Saltzman wrote:
On Thu, 1 Jul 2004 akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
You need to reboot without the module loaded.
Module unloading is now unsupported for the most part in 2.6 kernels.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Modifying rc.sysinit is dangerous as your mods will be nuked in an upgrade. Better is /etc/rc.local or /etc/rc.modules. The latter is called early in the init process by rc.sysinit and the former is the last thing done at startup.
I will look again but I could not find anywhere that rc.local is called in the rc.sysinit script.
It isn't, thats the S99local in your /etc/rc.d/rc#runlevel.d directory that runs it.
On Fri, 2004-07-02 at 09:17, akonstam@trinity.edu wrote:
I will look again but I could not find anywhere that rc.local is called in the rc.sysinit script.
/etc/rc.d/rc.local is symbolically linked to /etc/rc.d/rc#.d/S99local where # is your runlevel. So it is actually executed at the tail end of the boot process.
Of course the /etc/rc.d/rc#.d/ files are called by inittab line that runs /etc/rc.d/rc #
HTH,
--Rob
On Fri, 2 Jul 2004 akonstam@trinity.edu wrote:
On Thu, Jul 01, 2004 at 04:35:31PM -0400, Matthew Saltzman wrote:
On Thu, 1 Jul 2004 akonstam@trinity.edu wrote:
On Wed, Jun 30, 2004 at 03:15:52PM -0700, Mike Fedyk wrote:
Greg Swallow wrote:
During installation of the new 4kstacks compatible nvidia driver, am informed it will not operate correctly with the kernel module rivafb loaded/active. Tried modprobe -r rivafb to remove, but still have garbage cursor.
You need to reboot without the module loaded.
Module unloading is now unsupported for the most part in 2.6 kernels.
I made this work by what may be the kludge of the year. I placed the: modprobe -r rivafb as the next to last line in the rc.sysinit file. Ask me why not the last line? The last line looked like it should be last.
Well nvidia module seems to work so unless someone has a better idea I leave it the way it is,
Modifying rc.sysinit is dangerous as your mods will be nuked in an upgrade. Better is /etc/rc.local or /etc/rc.modules. The latter is called early in the init process by rc.sysinit and the former is the last thing done at startup.
I will look again but I could not find anywhere that rc.local is called in the rc.sysinit script.
rc.local is called via the SysV startup mechanism. If you look in /etc/rc5.d (e..g.), you'll find 99local, which links to /etc/rc.local
-
akonstam＠trinity.edu -
Alexander Dalloz -
Florin Andrei -
Gene Heskett -
Greg Swallow -
Marc Williams -
Matt Hansen -
Matthew Saltzman -
Mike Fedyk -
Robert Locke -
Tom Mitchell