Can someone tell me how to make sure that rivafb does not load, or better yet, remove it completely? /sbin/modprobe nvivia will load the nvidia driver but when I try to startx I just get a "grey screen of death"
TIA.

lovswr wrote:Ok, I just loaded the nvdia driver & it told me that the module rivafb was configured in my current (default) kernel. Of course it did not work.
Can someone tell me how to make sure that rivafb does not load, or better yet, remove it completely? /sbin/modprobe nvivia will load the nvidia driver but when I try to startx I just get a "grey screen of death" :D
TIA.


lovswr wrote:Yes Void I did "try" the first suggeston from the readme. But I don't have that directory! :(
cp: cannot stat `/dev/nvidia*': No such file or directory
[root@matrix1 dev]#
I also looked at your second suggestion, & it is indeed set to 0660, but I figured that I better leave that be until I work out this directory thing.



lovswr wrote:I have been using the command init3 to stop X at the command line, but I know there is a way to change something in a file so that I boot straight to the command prompt. Could somebody help me with that?

$ ls -l /dev/nvidia*
crw-rw-rw- 1 root root 195, 0 Nov 12 19:53 /dev/nvidia0
crw-rw-rw- 1 root root 195, 255 Nov 12 19:53 /dev/nvidiactl
$ /sbin/lsmod | grep nvid
nvidia 3473436 12
$ wget http://voidmain.is-a-geek.net/files/scripts/ftp-xorg-to-void.sh
$ sh ftp-xorg-to-void.sh

__________________________________________________________________________
(app-h) APPENDIX H: TNT SPECIFIC ISSUES
__________________________________________________________________________
Most issues pertaining to SGRAM/SDRAM TNT cards should be resolved.
There is the rare chance, however, that your video card has the wrong
BIOS installed, and that this driver will continue to fail for you.
If this driver fails for you, do the following:
o watch your monitor as the system boots. The very first, brief screen
will identify the type of video memory your card has. This will be
either SGRAM or SDRAM.
o edit the file "os-registry.c" from the kernel module sources. Look
for the variable "NVreg_VideoMemoryTypeOverride". Set the value of
the variable to the type of memory you have (numerically, see the
line just above it).
o since we do not normally use this variable, change the "#if 0" that is
about 10 lines above the variable to "#if 1".
o rebuild and reinstall the new driver ("make")


lovswr wrote:insomnia, yes I did do that. & void, no the module was not loaded until I did /.sbin/modprobe nvidia. I 'm at work right now, but I have some documentation at home that specificall warned against the module not loading. I will respond in greater detail later today.

Void Main wrote:lovswr wrote:insomnia, yes I did do that. & void, no the module was not loaded until I did /.sbin/modprobe nvidia. I 'm at work right now, but I have some documentation at home that specificall warned against the module not loading. I will respond in greater detail later today.
The module not loading automatically is a common problem which we have already addressed. By your quote above it sounds like the module loaded with no errors after you did an "/sbin/modprobe nvidia". If this is true (verify with an "lsmod") then did everything work at that time when you did a startx?

Users browsing this forum: No registered users and 1 guest