10B2: nvidia-framebuffer hassle
![](https://seccdn.libravatar.org/avatar/ef4a9e79ac93283f3e4baef147a242ec.jpg?s=120&d=mm&r=g)
Hi, Seems like it's more or less impossible to install nvidias driver to 10-beta2 (x86-64). First thing is that installer is entirely broken on ncurses mode, but that can be worked out. However, more vital problem is that installer bails out as it's unable to load kernel module due to frame buffer driver ( nvidiafb ) already having took over the device. So how do i disable it *not* to load this module (other than throwing it away)? Disabling fbset doesn't do the trick. Module won't unload either as its on use by someone. And of course fuser or lsof won't tell whos using it. This driver is even more annoying as it produces random display garbling .. -- // Janne
![](https://seccdn.libravatar.org/avatar/ced15a38e5d3f1b425e118547840a1a6.jpg?s=120&d=mm&r=g)
Quoting Janne Karhunen
Hi,
Seems like it's more or less impossible to install nvidias driver to 10-beta2 (x86-64). First thing is that installer is entirely broken on ncurses mode, but that can be worked out. However, more vital problem is that installer bails out as it's unable to load kernel module due to frame buffer driver ( nvidiafb ) already having took over the device.
So how do i disable it *not* to load this module (other than throwing it away)? Disabling fbset doesn't do the trick. Module won't unload either as its on use by someone. And of course fuser or lsof won't tell whos using it. This driver is even more annoying as it produces random display garbling ..
-- // Janne
Hmph. Can you ssh into the box from elsewhere? Or, can you, at a boot prompt, go to "More Options" (F3, I believe), type in "init 3"? Do this, edit xorg.conf at /etc/X11/, and make sure that you find an entry that looks like this - Section "Device" BoardName "RV250 Lf" BusID "1:0:0" Driver "radeon" <- (You'll want to change this!!!) Identifier "Device[0]" Option "usevnc" "no" VendorName "ATI" EndSection Look for this, and find the "Driver" portion (which I have attempted to highlight above). Edit this to "vesa" or "nv" and try an "init 5" to see what happens. Alternatively, you could run re-run SaX while in runlevel 3 (sax2), and this should fix your problems. Hope this helps -Chris
![](https://seccdn.libravatar.org/avatar/ef4a9e79ac93283f3e4baef147a242ec.jpg?s=120&d=mm&r=g)
On Monday 22 August 2005 01:31, Christopher P Robbins wrote:
go to "More Options" (F3, I believe), type in "init 3"? Do this, edit xorg.conf at /etc/X11/, and make sure that you find an entry that looks like this -
It's not X that loads frame buffer driver. Something else triggers it during bootup. 'Driver' setting in xorg.conf is already 'nvidia'. -- // Janne
participants (2)
-
Christopher P Robbins
-
Janne Karhunen