As I said, I had the same problem with the 4496 driver, and the only "solution" was to go back to an older version of the driver (which was the 4363 driver). After release of the 5328 driver I tried to upgrade to that one, and luckily I appeared to belong to the happy few that have a good working combination now (using a GeForce4 488Go card). I know that many other people are suffering the same problem with the 5328 driver as you do. I'm afraid the only solution for you is to try to use an older version of the driver (so the 4496 or even the 4363) and wait till Nvidia releases a better version of the driver.
Cheers,
Thanks a lot for the suggestion Jan but I had no luck. You were right I got this crappy screen with ctr-alt-f1. I tried the 4496 but no success and trying to install 4363 got an installation error that I think should not be bothered to get into. I think (don't know what you think) that trying to go to even older drivers won't be a solution. I'll try to live with this until a new driver comes. Regards, Felipe.
* Felipe Leon
Thanks a lot for the suggestion Jan but I had no luck. You were right I got this crappy screen with ctr-alt-f1. I tried the 4496 but no success and trying to install 4363 got an installation error that I think should not be bothered to get into. I think (don't know what you think) that trying to go to even older drivers won't be a solution.
I'll try to live with this until a new driver comes.
?? switch2nv ?? Perhaps the generic nv drivers will allow console access ?? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Thursday 01 January 2004 21:05, Felipe Leon wrote:
As I said, I had the same problem with the 4496 driver, and the only "solution" was to go back to an older version of the driver (which was the 4363 driver). After release of the 5328 driver I tried to upgrade to that one, and luckily I appeared to belong to the happy few that have a good working combination now (using a GeForce4 488Go card). I know that many other people are suffering the same problem with the 5328 driver as you do. I'm afraid the only solution for you is to try to use an older version of the driver (so the 4496 or even the 4363) and wait till Nvidia releases a better version of the driver.
Cheers,
Thanks a lot for the suggestion Jan but I had no luck. You were right I got this crappy screen with ctr-alt-f1. I tried the 4496 but no success and trying to install 4363 got an installation error that I think should not be bothered to get into. Hmm, that surprises me. I thought that the 4363 was pretty reliable. Just to make sure : did you do the following ? Goto runlevel 3 (or restart in Safe Mode) Then run : nvidia-installer --uninstall cd /usr/src/linux make cloneconfig && make dep cd /your download directory containing the driver sh NVIDIA-Linux-x86-1.0-4363.run
If you didn't, please retry one more time. I agree that that you shouldn't go back to older versions. Cheers, ---- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"
Hi Jan, Even though this email was not directed to me, it did show me how to fix my problem. I originally installed the nvidia driver that you can download during installation. I then enabled 3D. Things worked for a bit then suddenly the monitor went blank. I couldn't boot into SuSE in GUI mode. It was very frustrating. It seems that whenever I look at SuSE sideways, it quits working. Anyway, I was finally able to start SaX2 but when I tried to disable 3D it told me I had to uninstall nvidia but it didn't tell me how. You just did and it worked. Thanks Russ Jan Elders wrote:
Hmm, that surprises me. I thought that the 4363 was pretty reliable. Just to make sure : did you do the following ? Goto runlevel 3 (or restart in Safe Mode) Then run : nvidia-installer --uninstall cd /usr/src/linux make cloneconfig && make dep cd /your download directory containing the driver sh NVIDIA-Linux-x86-1.0-4363.run
If you didn't, please retry one more time. I agree that that you shouldn't go back to older versions. Cheers, ---- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"
Felipe Leon wrote:
As I said, I had the same problem with the 4496 driver, and the only "solution" was to go back to an older version of the driver (which was the 4363 driver). After release of the 5328 driver I tried to upgrade to that one, and luckily I appeared to belong to the happy few that have a good working combination now (using a GeForce4 488Go card). I know that many other people are suffering the same problem with the 5328 driver as you do. I'm afraid the only solution for you is to try to use an older version of the driver (so the 4496 or even the 4363) and wait till Nvidia releases a better version of the driver.
Cheers,
Thanks a lot for the suggestion Jan but I had no luck. You were right I got this crappy screen with ctr-alt-f1. I tried the 4496 but no success and trying to install 4363 got an installation error that I think should not be bothered to get into. I think (don't know what you think) that trying to go to even older drivers won't be a solution.
I'll try to live with this until a new driver comes.
Regards,
Felipe.
There is something very odd with these drivers. Some people including a friend has never had a problem with any of them on P-III 700/Geforce 2 MMX-220, another friend has problems with the same card, but using an Athlon. I experienced problems up to 4496 (Athlon XP 2200+) on a GeForce4 MX440 128 Meg, I changed the card to a GeForce FX5200 128M and have never had a problem since. I'm now running a 2.6.0-mm1 kernel on 9.0 Pro and driver 5328 with mods from www.minion.de and have not seen any problems with 2.6.x, shall soon be booting up 2.6.1-rc1-mm1 and seeing what happens. My guess is that it depends on the hardware mix and being a Universal driver, it doesn't gel with every mix of hardware. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
participants (5)
-
Felipe Leon -
Jan Elders -
Patrick Shanahan -
Russ -
Sid Boyce