* Michael Sacco [07-26-03 22:00]:

On Saturday 26 July 2003 10:30 pm, Patrick Shanahan wrote:

...

I can no longer boot into X? I have done nothing that I can think of, expecially to the display. I get the following message:

(==) Log file: "/var/log/XFree86.0.log", Time: Sat Jul 26 21:19:17 2003 (==) Using config file: "/etc/X11/XF86Config" (EE) NVIDIA(0): Failed to initialize the NVdriver kernel module! (EE) NVIDIA(0): *** Aborting *** (EE) Screen(s) found, but none have a usable configuration.

I am completely open to suggestions ....

tks, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

IIRC, a semi-recent update from YaST downloaded a kernel update for me, and gave a warning about having to reinstall the NVidia graphics drivers. I don't have this, so I disregarded the message. Have you recently run YOU? Did it install a kernel update?

I do not recall a kernel update and/or the warning about nVidia. I do not run YaST, I use fou4s regularly (cron). I ran yast from text mode (all I can get rite now) and configured the display/video card, but there were no changes. Should I remove XF86Config (rename) and start from there. tks, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

On Sun, 2003-07-27 at 05:33, Patrick Shanahan wrote:

I also notice: Fatal server error: no screens found

Why would 'no screens' happen?

Because it failed to initialise the driver. NVdriver is very old, exactly which version of nvidia's driver are you running. Automated updates are *not* a good thing. I'm guessing you got an old GLX driver but you still have the new kernel driver (named nvidia.o, not NVdriver)

On Sun, 2003-07-27 at 05:55, Patrick Shanahan wrote:

* Anders Johansson [07-26-03 22:47]:

...

On Sun, 2003-07-27 at 05:33, Patrick Shanahan wrote:

...

I also notice: Fatal server error: no screens found

Why would 'no screens' happen?

Because it failed to initialise the driver.

NVdriver is very old, exactly which version of nvidia's driver are you running.

NVIDIA_GLX-1.0-3123 NVIDIA_kernel-1.0-3123

hm, I don't remember when they switched names, but 3123 is pretty old.

336520 Sep 16 2002 /usr/X11R6/lib/modules/drivers/nvidia_drv.o

...

Automated updates are *not* a good thing. I'm guessing you got an old GLX driver but you still have the new kernel driver (named nvidia.o, not NVdriver)

And to correct this (?? go to nVidia and get later driver ??).

Either that, or if you want to keep your old driver, check why NVdriver won't load. perhaps "modprobe NVdriver" gives some interesting error messages. Perhaps you need to reinstall it. But I would go for the upgrade. The newer drivers are better

* Patrick Shanahan [07-26-03 23:28]:

* Anders Johansson [07-26-03 23:02]:

...

On Sun, 2003-07-27 at 05:55, Patrick Shanahan wrote:

...

336520 Sep 16 2002 /usr/X11R6/lib/modules/drivers/nvidia_drv.o

...

Automated updates are *not* a good thing. I'm guessing you got an old GLX driver but you still have the new kernel driver (named nvidia.o, not NVdriver)

And to correct this (?? go to nVidia and get later driver ??).

Either that, or if you want to keep your old driver, check why NVdriver won't load. perhaps "modprobe NVdriver" gives some interesting error messages. Perhaps you need to reinstall it.

But I would go for the upgrade. The newer drivers are better

Trying to download from nVidia now. Does SuSE have the drivers on their site. I am still running 8.1.

rpm --justdb -Uhv NVIDIA_kernel*.rpm rpm -Uhv NVIDIA_GLX*.rpm 2) Kernel sources must be installed and configured. Usually this means installing the 'kernel-source' RPM with YaST2 and configure it then with the following commands: cp /boot/vmlinuz.config /usr/src/linux/.config cp /boot/vmlinuz.version.h /usr/src/linux/include/linux cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux cd /usr/src/linux make cloneconfig dep NVIDIA-Linux-x86-1.0-4363.run --extract-only cd NVIDIA-Linux-x86-1.0-4363/usr/src/nv make install depmod -a 5) Enable 3D support with SaX2. No good feelings here. I still have the same error...: wahoo:~ # SaX2 SaX: initializing please wait... SaX: including [Card:0] profile: nvidia... SaX: startup xc: sorry could not start configuration server xc: this could have the following reasons: - the card is still not supported. To get further information about the driver status please have a look at: http://www.xfree86.org/4.2.0/Status.html - the card was not detected correctly. In this case please get the information which XFree86 module provide support for the card and set the module using the following command: sax2 -m 0=<name of the module> Note: 0 is a digit not a letter Note: Information about modules are provided on the mentioned WWW-Page - the card was detected but the server fails to start in spite of the detection. In this case something more serious had happened. Please have a look at the log file: /var/log/SaX.log xc: if you can not determine the cause please get in contact with: Please include the log file and a detailed description into your e-mail xc: abort... Open for suggestions, tkx, (going to bed, 12:30pm here). -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

* Anders Johansson [07-27-03 00:52]:

On Sun, 2003-07-27 at 07:26, Patrick Shanahan wrote:

...

5) Enable 3D support with SaX2.

Never mind that stage, it's obviously already enabled.

is NVdriver loaded from your earlier escapades? If so "rmmod NVdriver"

not loaded

Does "modprobe nvidia" give you any errors?

wahoo:~ # modprobe nvidia Warning: loading /lib/modules/2.4.19-4GB/kernel/drivers/video/nvidia.o will taint the kernel: non-GPL license - NVIDIA See http://www.tux.org/lkml/#export-tainted for information about tainted modules Module nvidia loaded, with warnings

If you can get the module "nvidia" loaded, try startx

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. tks, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

* Anders Johansson [07-27-03 01:37]:

On Sun, 2003-07-27 at 07:59, Patrick Shanahan wrote:

...

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.

Is that the only error message you get? If so, then I'm out of ideas

Yes, but.... I did modprobe nvidia and it took w/o an error. Did init 5 and X is back . Did init 3, sax2, and still have same error, quoted above. Question, should I be doing sux - before sax2 ?? Just hit me in the face. Been up toooo long for my age w/o enough cold beer. Now I feel strupidd. One _good_ think came out of all this, I no longer have to boot with vga=normal. I don't know why but vga=794 works now, but no splash. tks much, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org