After install the new kernel with YOU, the system hangs when start graphics (keyboard leds blinks, kernel panic) This is the last message in /var/log/messages: 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004 I've restarted in runlevel 3 and returned to the old kernel: kernel-smp-2.6.5-7.151.i586.rpm kernel-source-2.6.5-7.151.i586.rpm New kernel that doesn't works: kernel-smp-2.6.5-7.155.29.i586.rpm kernel-source-2.6.5-7.155.29.i586.rpm -- Benjamí http://weblog.bitassa.net .
On Saturday 11 June 2005 01:05 pm, Benjamí Villoslada wrote:
After install the new kernel with YOU, the system hangs when start graphics (keyboard leds blinks, kernel panic)
This is the last message in /var/log/messages: 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004
Everytime you install a new kernel, you need to reinstall your NVIDIA drivers. If you did this via YOU in the first place, fire up YOU, view installed packages and update the NVIDIA drivers. -- __________ CorvusE: Linux User #370082 live free. die free. use free software.
Benjamí Villoslada a écrit :
After install the new kernel with YOU, the system hangs when start graphics (keyboard leds blinks, kernel panic)
This is the last message in /var/log/messages: 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004
I've restarted in runlevel 3 and returned to the old kernel: kernel-smp-2.6.5-7.151.i586.rpm kernel-source-2.6.5-7.151.i586.rpm
New kernel that doesn't works: kernel-smp-2.6.5-7.155.29.i586.rpm kernel-source-2.6.5-7.155.29.i586.rpm
Hello, When you change your kernel, you have to reinstall the Nvidia module with the install script. Don't forget to install the kernel headers before. Michel.
El Dissabte 11 Juny 2005 19:22, Catimimi va escriure:
When you change your kernel, you have to reinstall the Nvidia module with the install script.
What's the script name?
Don't forget to install the kernel headers before.
I use YOU 1. Install new kernel and not reboot. 2. Reinstall nVidia module with script. or 2. Reinstall nVidia module with YOU (thanks, CorvusE). Is right? :) -- Benjamí http://weblog.bitassa.net .
On Saturday 11 June 2005 19:22, Catimimi wrote:
When you change your kernel, you have to reinstall the Nvidia module with the install script. Don't forget to install the kernel headers before.
Not if you use the nvidia driver for which there is a precompiled module, in this case the rpm install script will re-link the driver module. However, the 5336 module is extremely old, I would get the latest version. As mentioned, the kernel source matching the new kernel should be installed, then boot to runlevel 3 and run cd /usr/src/linux make mrproper make cloneconfig make prepare-all nvidia-installer --update
El Dissabte 11 Juny 2005 19:57, Anders Johansson va escriure:
However, the 5336 module is extremely old, I would get the latest version. As mentioned, the kernel source matching the new kernel should be installed, then boot to runlevel 3 and run
cd /usr/src/linux make mrproper make cloneconfig make prepare-all nvidia-installer --update
Thanks (all) now is woking fine and with the 1.0-7664 module. From now, I should make this operations in every kernel update? (since now I've used YOU only, but my nVidia module are old) -- Benjamí http://weblog.bitassa.net .
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-06-11 at 20:34 +0200, Benjamí Villoslada wrote:
As mentioned, the kernel source matching the new kernel should be installed, then boot to runlevel 3 and run
cd /usr/src/linux make mrproper <-- overkill make cloneconfig make prepare-all nvidia-installer --update <-- not really.
Thanks (all) now is woking fine and with the 1.0-7664 module.
From now, I should make this operations in every kernel update?
Yes. In the NVidia home page you have instructions, and for SuSE, it tells you to read ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HOWTO. I'll paste the relevant section: | | People who aren't afraid of recompiling the nvidia kernel module or even | reinstalling the nvidia driver each time the kernel has been updated and | want or need to use the latest and greatest nvidia driver can use the | following steps 1-3. The others should use the instructions above using | YOU and skip the steps below. | | 1) Kernel sources must be installed and configured. Usually this means | installing the 'kernel-source', 'make' and 'gcc' packages with YaST2. | Update it - if not already done - via YaST2 Online Update (YOU). | | 2) Use the nvidia installer for 1.0-7664. | | modprobe agpgart | sh NVIDIA-Linux-x86-1.0-7664-pkg1.run -q | | 3) Configure X.Org with | | sax2 -m 0=nvidia (0 is a digit, not a letter!) | | NOTE: There is no need to try to enable 3D support. It's already | enabled, when the nvidia driver is running. | The procedure just after updating the kernel would be: 1) Edit '/etc/X11/xorg.conf'. Change line Driver "nv" for Driver "nvidia" (I use customized device sections instead). Reboot. The new kernel will be active, but X will use the open driver, without 3D. 2) Log-off your X session. Open a text terminal (ctrl-alt-f1), login as root, type "init 3". 3) Change to /usr/src/linux, and run: make cloneconfig make prepare-all cd whatever (probably /usr/share/doc/nvidia/) ./NVIDIA-Linux-x86-1.0-7664-pkg1.run (the '-q' option in the readme is for "no questions"). 4) Edit '/etc/X11/xorg.conf' again, undo the previous change (put 'nvidia' now). 5) Test with 'startx'. 6) Works? Exit session, type init 5 again. Doesn't work? Probably reboot, make sure to enter runlevel 3. Think what could have gone wrong... This procedure "might" be more involved, but I have it running faster, without 3D, of course. Only when I need 3D (I only need it for gaming) I install the nvidia driver. But the open driver is more stable: I updated the kernel, but I haven't bothered to reinstall the nvidia driver yet, I stopped after step 1 ;-) - -- Cheers, Carlos Robinson P.D.: La costa está libre ;-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCq3CbtTMYHG2NR9URAqqQAJ9mXic3PFhAHP2aq5OOf3p0RrgqJwCcDUtb QlN+eNWYosgNlc4xcrQtdvs= =ivAK -----END PGP SIGNATURE-----
On Sunday 12 June 2005 01:15, Carlos E. R. wrote:
1) Edit '/etc/X11/xorg.conf'. Change line
Driver "nv"
for
Driver "nvidia"
(I use customized device sections instead). Reboot. The new kernel will be active, but X will use the open driver, without 3D.
There is no need for this, or for running sax2 with cryptic parameters, if the nvidia driver was installed and working with the old kernel. Just go to runlevel 3, make sure the kernel sources are installed and prepared, run the nvidia installer, go back to runlevel 5, done. Nothing else needed
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-06-12 at 02:43 +0200, Anders Johansson wrote:
1) Edit '/etc/X11/xorg.conf'. Change line
Driver "nv"
for
Driver "nvidia"
(I use customized device sections instead). Reboot. The new kernel will be active, but X will use the open driver, without 3D.
There is no need for this, or for running sax2 with cryptic parameters, if the nvidia driver was installed and working with the old kernel. Just go to runlevel 3, make sure the kernel sources are installed and prepared,
For doing that, I like to have the new kernel already running (or make cloneconfig will fail). And to have the new kernel running, either I boot into runlevel 3 (as nvidia module is not yet installed), or use module nv instead for a while - and that "while" make last for a week or two till I find a real need to have 3D again. And... there is nothing cryptic about a 4 letter change. It's just a precaution, a safeguard. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCrOKytTMYHG2NR9URAinUAJ4xlv0/qSrEVL6viF1zpigUtGFC0QCdFOzc bKqlNOxPuS3od7ScN2t+Ddg= =6OBz -----END PGP SIGNATURE-----
On Monday 13 June 2005 03:34, Carlos E. R. wrote:
The Sunday 2005-06-12 at 02:43 +0200, Anders Johansson wrote:
1) Edit '/etc/X11/xorg.conf'. Change line
Driver "nv"
for
Driver "nvidia"
(I use customized device sections instead). Reboot. The new kernel will be active, but X will use the open driver, without 3D.
There is no need for this, or for running sax2 with cryptic parameters, if the nvidia driver was installed and working with the old kernel. Just go to runlevel 3, make sure the kernel sources are installed and prepared,
For doing that, I like to have the new kernel already running (or make cloneconfig will fail). And to have the new kernel running, either I boot into runlevel 3 (as nvidia module is not yet installed), or use module nv instead for a while - and that "while" make last for a week or two till I find a real need to have 3D again.
And... there is nothing cryptic about a 4 letter change. It's just a precaution, a safeguard.
The "cryptic" bit referred to the sax2 parameter, not the config file change. And it's fair enough that you do it because you're not actually interested in running the accelerated driver, but then you really shouldn't include it as item 1 in a "how to install the nvidia driver". It makes beginners think it's something they have to do, instead of just something you choose to do
Hi, The missing piece of information here seems to be that you need to: 1.) Run YOU 2.) Select Installed/Installable as the the patch filter 3.) Select to update the SuSE supplied nvidia patch from list 4.) Click install This will install a little script into your _current_ kernel, which means that each time there is a kernel update the relevant module is automagically rebuilt, without you EVER having to invoke the nvidia-installer. This problem stems from the fact that when you originally install the OS, and run a YOU update as the last step, if you select both the nvidia patch and a new kernel, the nvidia patch is applied to current running (i.e. the install) kernel - not the one you just downloaded. Hence on the first boot the nvidia patch is lost. Hope this helps, Jon. Anders Johansson wrote:
On Monday 13 June 2005 03:34, Carlos E. R. wrote:
The Sunday 2005-06-12 at 02:43 +0200, Anders Johansson wrote:
1) Edit '/etc/X11/xorg.conf'. Change line
Driver "nv"
for
Driver "nvidia"
(I use customized device sections instead). Reboot. The new kernel will be active, but X will use the open driver, without 3D.
There is no need for this, or for running sax2 with cryptic parameters, if the nvidia driver was installed and working with the old kernel. Just go to runlevel 3, make sure the kernel sources are installed and prepared,
For doing that, I like to have the new kernel already running (or make cloneconfig will fail). And to have the new kernel running, either I boot into runlevel 3 (as nvidia module is not yet installed), or use module nv instead for a while - and that "while" make last for a week or two till I find a real need to have 3D again.
And... there is nothing cryptic about a 4 letter change. It's just a precaution, a safeguard.
The "cryptic" bit referred to the sax2 parameter, not the config file change.
And it's fair enough that you do it because you're not actually interested in running the accelerated driver, but then you really shouldn't include it as item 1 in a "how to install the nvidia driver". It makes beginners think it's something they have to do, instead of just something you choose to do
-- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-06-13 at 04:06 +0200, Anders Johansson wrote:
And it's fair enough that you do it because you're not actually interested in running the accelerated driver, but then you really shouldn't include it as item 1 in a "how to install the nvidia driver". It makes beginners think it's something they have to do, instead of just something you choose to do
It is a method of having the graphical session running straight away after reboooting, while the nvidia installation is done, or if it fails (which is possible). An intermediate step, of course, that can be bypassed. Novices should stick to the nvidia driver version installed by YOU, which is "guaranteed" no to be spoilt by security kernel updates done by YOU - as stated in the suse documentation (ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/nvidia-installer-HOWTO): | It is recommended to use YOU (YaST Online Update) for (re)installation | of the nvidia driver. There are several reasons for this. First, it's | simple. Second, and this is the most important one, you won't need to | recompile the nvidia kernel module after a kernel update. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCrdcOtTMYHG2NR9URAqBEAJ9zilRPamFN2eFcXsFMmrOYGPtdAwCdHxJC rem0Jq8mvDy6gO1HlaCu5N4= =wopz -----END PGP SIGNATURE-----
On Saturday 11 June 2005 02:34 pm, Benjamí Villoslada wrote:
From now, I should make this operations in every kernel update?
You bet! Before long you won't even have to think twice about it. In fact, now that you're using the script (hooray!), issuing the following commands: nvidia-installer -f sax2 -m 0=nvidia ...after every kernel update will keep your drivers up to date easily.
(since now I've used YOU only, but my nVidia module are old)
The first time I tried to update my NVIDIA drivers in a non-YOU fashion, I made such a mess of things. Now that I've got it down, I'll never look back. -- __________ CorvusE: Linux User #370082 live free. die free. use free software.
On Sunday 12 June 2005 00:33, CorvusE wrote:
On Saturday 11 June 2005 02:34 pm, Benjamí Villoslada wrote:
From now, I should make this operations in every kernel update?
You bet! Before long you won't even have to think twice about it. In fact, now that you're using the script (hooray!), issuing the following commands:
nvidia-installer -f
sax2 -m 0=nvidia Errrrrr you do NOT need this bit every time you update the kernel OR the Nvidia driver Your xorg.conf is NOT touched by the kernel updates OR the Nvidia updates so please for get the sax2 bit you only need to run it ONCE then can it unless you rebuild your machine ,ie complete reinstall after frelling it up ..
...after every kernel update will keep your drivers up to date easily.
(since now I've used YOU only, but my nVidia module are old)
The first time I tried to update my NVIDIA drivers in a non-YOU fashion, I made such a mess of things. Now that I've got it down, I'll never look back. -- __________ CorvusE: Linux User #370082 live free. die free. use free software.
Pete. -- If Bill Gates had gotten LAID at High School do YOU think there would be a Microsoft ? Of course NOT ! You gotta spend a lot of time at your school Locker stuffing underware up your ass to think , I am going to take on the worlds Computer Industry -------:heard on Cyber Radio.:-------
On Saturday 11 June 2005 1:22 pm, Catimimi wrote:
Benjamí Villoslada a écrit :
After install the new kernel with YOU, the system hangs when start graphics (keyboard leds blinks, kernel panic)
This is the last message in /var/log/messages: 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004
I've restarted in runlevel 3 and returned to the old kernel: kernel-smp-2.6.5-7.151.i586.rpm kernel-source-2.6.5-7.151.i586.rpm
New kernel that doesn't works: kernel-smp-2.6.5-7.155.29.i586.rpm kernel-source-2.6.5-7.155.29.i586.rpm
Hello, When you change your kernel, you have to reinstall the Nvidia module with the install script. Don't forget to install the kernel headers before.
I didn't have to.........there was an update yesterday....security. NO problem with my nVidia. Fred -- Planet Earth - a subsidiary of Microsoft. We have no bugs in our software, Never! We do have undocumented added features, that you will find amusing, at no added cost to you, at this time.
Fred A. Miller wrote:
On Saturday 11 June 2005 1:22 pm, Catimimi wrote:
Benjamí Villoslada a écrit :
After install the new kernel with YOU, the system hangs when start graphics (keyboard leds blinks, kernel panic)
This is the last message in /var/log/messages: 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004
I've restarted in runlevel 3 and returned to the old kernel: kernel-smp-2.6.5-7.151.i586.rpm kernel-source-2.6.5-7.151.i586.rpm
New kernel that doesn't works: kernel-smp-2.6.5-7.155.29.i586.rpm kernel-source-2.6.5-7.155.29.i586.rpm
Hello, When you change your kernel, you have to reinstall the Nvidia module with the install script. Don't forget to install the kernel headers before.
I didn't have to.........there was an update yesterday....security. NO problem with my nVidia.
Fred Why don't you folks just download a real kernel from "www.kernel.org" and the Nvidia run. It is so easy to build your own with all of your machine needs and know it has not be fiddled with.. Why seek out a RPM with a CPU that doesn't fit your CPU (or atleast likely doesn't). Once booted you will have learned something and beside NVidia (which this machine is loaded with ) and run the Nvidia-run script. Oh yea! you might checkout /usr/src/kernel-modules and find "/subfs" also.
NOTE: 2.6.12-rc4 finds all kinds of Nvidia chipsets -> ethernet, controllers and sound. It does miss the Video Chipset but NVidia takes care of that. -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316
On Saturday 11 June 2005 22:20, Donn Washburn wrote:
Fred A. Miller wrote:
On Saturday 11 June 2005 1:22 pm, Catimimi wrote:
Benjamí Villoslada a écrit :
After install the new kernel with YOU, the system hangs when start graphics (keyboard leds blinks, kernel panic)
........................... trim ........................... Why don't you folks just download a real kernel from "www.kernel.org" and the Nvidia run. It is so easy to build your own with all of your machine needs and know it has not be fiddled with.. Why seek out a RPM with a CPU that doesn't fit your CPU (or atleast likely doesn't). Once booted you will have learned something and beside NVidia (which this machine is loaded with ) and run the Nvidia-run script. Oh yea! you might checkout /usr/src/kernel-modules and find "/subfs" also. Hi Don,
Why would we want to give up all those patches and newer modules that SUSE puts into their kernels? PeterB
participants (10)
-
Anders Johansson -
Benjamí Villoslada -
Carlos E. R. -
Catimimi -
CorvusE -
Donn Washburn -
Fred A. Miller -
Jonathan Brooks -
Peter B Van Campen -
Peter Nikolic