![](https://seccdn.libravatar.org/avatar/908e2062a6ff90c087ee3deacc012f5f.jpg?s=120&d=mm&r=g)
On Wednesday 03 March 2004 18:14, Matthew Johnson wrote:
[stuff deleted]
Install the Source...Think that is needed. Then run YOU online update again to update the source, then to make sure I would go to /usr/src/linux and then run "make cloneconfig && make dep" I have had issues with agpgart on the 2.4.21 kernel, being that is seriously out of date with regards to some chipsets, notably with regards to SiS chipsets.
I read the read me on the nvidia site for SuSE users. That recommended using YOU to install the patch. I used YOU to install the nvidia driver. When I restarted X I got nothing. Just a blank screen.
Then I would proceed with their other instructions...
I then noticed the read me said something about not having the nvidia module loaded when doing the install. Even though I was using the nv module, I reinstalled SuSE, and then used Yast from runlevel 3 to install the nvidia patch. Black screen when I type startx.
Couple or more ways of doing this:
1. End session, control-alt-F1 and log in as root. Then type init 3, then you may have to manually remove the nvidia module with modprobe -r nvidia.
2. Log in as root in another screen, type rcxdm stop, remove module as per previous instruction.
sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --update then needs to be executed as root, if this fails, or if it states that its already up to date go ahead and force the update with the --force-update instead of just --update.
If I log in as root and type sax2, then sax2 uses the nv driver and everything works fine. If I type sax2 -m 0=nvidia, then I get a blank screen. Can't even Ctl-Alt-F@ to get to another console.
Can try this again after the above is done.
I assumed that I didn't need the kernel source installed if I used the YOU method. maybe i should use the alternate method of running the nvidia installer with the source package installed.
You assumed correctly, at least that is what I got from the instructions, supposedly the easiest method.
Any ideas?
dmesg would be useful, as well as lspci...Knowing the chipset helps. Dmesg primarily to see if agpgart claims an unknown chipset.
Matt
thanks for the info. Will try it this weekend. I am battling a vmware problem I have to solve first. Mike -- Michael A. Coan Woodlawn Foundation 524 North Avenue, Suite 203 New Rochelle, NY 10801-3410 tel 914-632-3778 fax 914-632-5502