NVIDIA 4496 driver woes
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks). THE PROBLEM : After installation of the new NVIDIA 4496 driver on my system (with an Nvidia GeForce4 488Go card), I only got a black screen when starting X. This could be solved by setting Option "NvAGP" "0" in the Device section of XF86Config, but ....... it was not possible anymore to go to a console with CTRL-ALT-F1 .... F6. When doing that, I only got a strange garbled multicolor screen without the system reacting to anything. It was only possible to go back to X again (with CTRL-ALT-F7). The same garbled screen was shown when shutting down the system. THE SOLUTION : After having tried in vain many things as suggested by helpful people in this discussion group, I followed the one and only useful advice (from Basil Chupin) : Throw away the 4496 driver !!!!! And install the older 4363 driver. After having done so everything worked perfect (without having changed anything else on my system), so the 4496 driver really must be incorrect. Now I could also set Option "NvAGP" "1" and all still works well. For those who want to know, here's what I did to move back to the 4363 : 1. Download the 4363 driver from www.nvidia.com 2. Goto runlevel 3 (or restart in Safe Mode) 3. Do the following : nvidia-installer --uninstall (to remove the 4496) cd /usr/src/linux make cloneconfig && make dep cd << your download directory >> sh NVIDIA-Linux-x86-1.0-4363.run 4. Goto runlevel 5 And .... you will be happy again. Cheers, -- Jan Elders Nuenen the Netherlands
On Thursday 23 October 2003 8:18 pm, Jan Elders wrote:
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks).
<snip> To successfully install the 4496 drivers, the kernel sources have to be installed and correctly configured. The kernel source can be installed from the install cd / dvd. Change to /usr/src/linux and run make cloneconfig, make dep, make bzImage and make modules. After this the Nvidia packages compiled but a variable "IGNAOE_CC_MISMATCH=yes" has to be set. HTH. LW999
On Friday 24 October 2003 22:05, LinuxWorld999 wrote:
On Thursday 23 October 2003 8:18 pm, Jan Elders wrote:
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks).
<snip> To successfully install the 4496 drivers, the kernel sources have to be installed and correctly configured. The kernel source can be installed from the install cd / dvd. Change to /usr/src/linux and run make cloneconfig, make dep, make bzImage and make modules. After this the Nvidia packages compiled but a variable "IGNORE_CC_MISMATCH=yes" has to be set.
Yes, I did all of that (as part of my struggling), but nevertheless this 4496 driver does not work well for me (and other people). The 4363 driver works perfect ! There definitely IS something wrong with the 4496. Maybe it depends on the type of card that is being used ?? Anyway, I maintain my advice to go back to the 4363 driver for the unlucky people that can't get it right with the 4496. Cheers, -- Jan Elders Nuenen the Netherlands
On Saturday 25 October 2003 9:51 am, Jan Elders wrote:
On Friday 24 October 2003 22:05, LinuxWorld999 wrote:
On Thursday 23 October 2003 8:18 pm, Jan Elders wrote:
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks).
<snip> To successfully install the 4496 drivers, the kernel sources have to be installed and correctly configured. The kernel source can be installed from the install cd / dvd. Change to /usr/src/linux and run make cloneconfig, make dep, make bzImage and make modules. After this the Nvidia packages compiled but a variable "IGNORE_CC_MISMATCH=yes" has to be set.
Yes, I did all of that (as part of my struggling), but nevertheless this 4496 driver does not work well for me (and other people). The 4363 driver works perfect ! There definitely IS something wrong with the 4496. Maybe it depends on the type of card that is being used ?? Anyway, I maintain my advice to go back to the 4363 driver for the unlucky people that can't get it right with the 4496. <snip>
If the compile is successful, running "init 3" and then sax2 also helps. If however all else fails, then reverting to the old driver is the only option. LW999
I'm using this same driver on a TI 4200 card, and on this card the carbled screen is connected with what monitors you use. I'm using the primary interface "VGA" interface. If I set my card, to use the second interface which in my case, is always the "tv", by: Option "ConnectMonitor" "Crt,TV" I get a carbled console screen, if I only set it to "crt" it works ok. It's my assumption, that it's when you use the second output device or the DVI connector for your monitor that it causes problems. But that's only a guess, anyway in my case ... the driver works fine. Hope it helps. On Thursday 23 October 2003 21:18, Jan Elders wrote:
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks).
THE PROBLEM : After installation of the new NVIDIA 4496 driver on my system (with an Nvidia GeForce4 488Go card), I only got a black screen when starting X. This could be solved by setting Option "NvAGP" "0" in the Device section of XF86Config, but ....... it was not possible anymore to go to a console with CTRL-ALT-F1 .... F6. When doing that, I only got a strange garbled multicolor screen without the system reacting to anything. It was only possible to go back to X again (with CTRL-ALT-F7). The same garbled screen was shown when shutting down the system.
THE SOLUTION : After having tried in vain many things as suggested by helpful people in this discussion group, I followed the one and only useful advice (from Basil Chupin) : Throw away the 4496 driver !!!!! And install the older 4363 driver. After having done so everything worked perfect (without having changed anything else on my system), so the 4496 driver really must be incorrect. Now I could also set Option "NvAGP" "1" and all still works well.
For those who want to know, here's what I did to move back to the 4363 : 1. Download the 4363 driver from www.nvidia.com 2. Goto runlevel 3 (or restart in Safe Mode) 3. Do the following : nvidia-installer --uninstall (to remove the 4496) cd /usr/src/linux make cloneconfig && make dep cd << your download directory >> sh NVIDIA-Linux-x86-1.0-4363.run 4. Goto runlevel 5 And .... you will be happy again.
Cheers, -- Jan Elders Nuenen the Netherlands
Jan Elders wrote:
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks).
THE PROBLEM : After installation of the new NVIDIA 4496 driver on my system (with an Nvidia GeForce4 488Go card), I only got a black screen when starting X. This could be solved by setting Option "NvAGP" "0" in the Device section of XF86Config, but ....... it was not possible anymore to go to a console with CTRL-ALT-F1 .... F6. When doing that, I only got a strange garbled multicolor screen without the system reacting to anything. It was only possible to go back to X again (with CTRL-ALT-F7). The same garbled screen was shown when shutting down the system.
THE SOLUTION : After having tried in vain many things as suggested by helpful people in this discussion group, I followed the one and only useful advice (from Basil Chupin) : Throw away the 4496 driver !!!!! And install the older 4363 driver. After having done so everything worked perfect (without having changed anything else on my system), so the 4496 driver really must be incorrect. Now I could also set Option "NvAGP" "1" and all still works well.
For those who want to know, here's what I did to move back to the 4363 : 1. Download the 4363 driver from www.nvidia.com 2. Goto runlevel 3 (or restart in Safe Mode) 3. Do the following : nvidia-installer --uninstall (to remove the 4496) cd /usr/src/linux make cloneconfig && make dep cd << your download directory >> sh NVIDIA-Linux-x86-1.0-4363.run 4. Goto runlevel 5 And .... you will be happy again.
Cheers,
I have to add something to the above, Jan, which will clarify the problem with the nVidia 4496 driver and why some people are not experiencing problem with it. The problem with the 4496 driver seems to be restricted to those running the Athlon-oriented kernel in SuSE v8.2 BUT *specifically* the Athlon kernel patched to #100 - ie k_athlon-2,4,20-100.i586 . From what I tested, patches prior to #100 do not cause a problem with the 4496 driver. As I said, the problem seems to be when the Athlon-specific kernel is used, and those running an Intel CPU do not appear to have a problem. Cheers. -- Wagner's music is really not as bad as it sounds.
On Monday 03 November 2003 09:45, Basil Chupin wrote:
Jan Elders wrote:
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks).
THE PROBLEM : After installation of the new NVIDIA 4496 driver on my system (with an Nvidia GeForce4 488Go card), I only got a black screen when starting X. This could be solved by setting Option "NvAGP" "0" in the Device section of XF86Config, but ....... it was not possible anymore to go to a console with CTRL-ALT-F1 .... F6. When doing that, I only got a strange garbled multicolor screen without the system reacting to anything. It was only possible to go back to X again (with CTRL-ALT-F7). The same garbled screen was shown when shutting down the system.
THE SOLUTION : After having tried in vain many things as suggested by helpful people in this discussion group, I followed the one and only useful advice (from Basil Chupin) : Throw away the 4496 driver !!!!! And install the older 4363 driver. After having done so everything worked perfect (without having changed anything else on my system), so the 4496 driver really must be incorrect. Now I could also set Option "NvAGP" "1" and all still works well.
For those who want to know, here's what I did to move back to the 4363 : 1. Download the 4363 driver from www.nvidia.com 2. Goto runlevel 3 (or restart in Safe Mode) 3. Do the following : nvidia-installer --uninstall (to remove the 4496) cd /usr/src/linux make cloneconfig && make dep cd << your download directory >> sh NVIDIA-Linux-x86-1.0-4363.run 4. Goto runlevel 5 And .... you will be happy again.
Cheers,
I have to add something to the above, Jan, which will clarify the problem with the nVidia 4496 driver and why some people are not experiencing problem with it.
The problem with the 4496 driver seems to be restricted to those running the Athlon-oriented kernel in SuSE v8.2 BUT *specifically* the Athlon kernel patched to #100 - ie k_athlon-2,4,20-100.i586 . From what I tested, patches prior to #100 do not cause a problem with the 4496 driver.
As I said, the problem seems to be when the Athlon-specific kernel is used, and those running an Intel CPU do not appear to have a problem.
Well, I'm running the k_deflt-2.4.20-100 (with an Intel Pentium 4) and experiencing all of the described problems with the 4496 driver !! How about that ? So, there seems to be more to it than you thought. ;-( Cheers, -- Jan Elders Nuenen the Netherlands
Jan Elders wrote:
On Monday 03 November 2003 09:45, Basil Chupin wrote:
Jan Elders wrote:
Hi everybody, This my attempt to contribute some information for people who are struggling with the NVIDIA 4496 driver (like I have been doing for many weeks).
THE PROBLEM : After installation of the new NVIDIA 4496 driver on my system (with an Nvidia GeForce4 488Go card), I only got a black screen when starting X. This could be solved by setting Option "NvAGP" "0" in the Device section of XF86Config, but ....... it was not possible anymore to go to a console with CTRL-ALT-F1 .... F6. When doing that, I only got a strange garbled multicolor screen without the system reacting to anything. It was only possible to go back to X again (with CTRL-ALT-F7). The same garbled screen was shown when shutting down the system.
THE SOLUTION : After having tried in vain many things as suggested by helpful people in this discussion group, I followed the one and only useful advice (from Basil Chupin) : Throw away the 4496 driver !!!!! And install the older 4363 driver. After having done so everything worked perfect (without having changed anything else on my system), so the 4496 driver really must be incorrect. Now I could also set Option "NvAGP" "1" and all still works well.
For those who want to know, here's what I did to move back to the 4363 : 1. Download the 4363 driver from www.nvidia.com 2. Goto runlevel 3 (or restart in Safe Mode) 3. Do the following : nvidia-installer --uninstall (to remove the 4496) cd /usr/src/linux make cloneconfig && make dep cd << your download directory >> sh NVIDIA-Linux-x86-1.0-4363.run 4. Goto runlevel 5 And .... you will be happy again.
Cheers,
I have to add something to the above, Jan, which will clarify the problem with the nVidia 4496 driver and why some people are not experiencing problem with it.
The problem with the 4496 driver seems to be restricted to those running the Athlon-oriented kernel in SuSE v8.2 BUT *specifically* the Athlon kernel patched to #100 - ie k_athlon-2,4,20-100.i586 . From what I tested, patches prior to #100 do not cause a problem with the 4496 driver.
As I said, the problem seems to be when the Athlon-specific kernel is used, and those running an Intel CPU do not appear to have a problem.
Well, I'm running the k_deflt-2.4.20-100 (with an Intel Pentium 4) and experiencing all of the described problems with the 4496 driver !! How about that ?
So, there seems to be more to it than you thought. ;-(
Cheers,
Aah, you are the first to say, or if you did said it before I did not pay attention, that this is also occurring with the Intel-specific kernel. OK, so now it possibly boils down to the patch number- you are using the #100 patch which is what I found to be the problem with the Athlon-specific kernel. Cheers. -- Wagner's music is really not as bad as it sounds.
participants (4)
-
Basil Chupin -
Jan Elders -
LinuxWorld999 -
Örn Hansen