| View previous topic :: View next topic |
| Author |
Message |
filmore
n00b
Joined: 16 Jan 2004
Posts: 18
|
 Posted: Tue Feb 03, 2004 1:41 am Post subject: NVidia 1.0.5336 Ctr+Alt+F1 == Black screen |
 |
|
I just recently upgraded to 2.6.1-gentoo from 2.4.something-gaming so I had to get a more recent NVidia driver. Unfortunately the 5336 seems to cause my console selection to go all haywire.
Symptoms
Screen is black
Monitor appears to be in power-save mode
Only happens when on a non-X11 console
The X11 console works fine (Ctrl-Alt-F7)
The console seems to still accept input (i.e. Ctrl-Alt-Del)
Some OpenGL stuff wouldn't initialize on an older version of the driver (4496 if memory serves) and the new kernel, but console switching worked flawlessly
How to reproduce
Boot into 2.6.1-gentoo and `modprobe nvidia` the 5336 module
Load up X
Switch to a different virtual console
Switch back to X console when bored of black screen
Now, this isn't a critical problem because the symptoms only appear after X is started, but I would still like to squish this bug/feature/setting.
I would like to help de-bug this, but don't even know where to start. Any pointers would be helpfull.
Can anyone out there re-produce this? |
|
| Back to top |
|
 |
Drewgrange
Guru
Joined: 29 Mar 2003
Posts: 483
Location: Ohio, US
|
| Posted: Tue Feb 03, 2004 3:55 am Post subject: |
|
|
Same thing happens to me using the 4496 drivers, although I have twinview set up. With the drivers that were out just before 5336, the machine would hard lock if I had twinview enabled and tried to switch terminals. Without twinview it just gave me a garbled mess.
I added an extra variable in there, but I'm just one of probably many other stories out there of nvidia and messed up terminals. |
|
| Back to top |
|
|
filmore
n00b
Joined: 16 Jan 2004
Posts: 18
|
| Posted: Tue Feb 03, 2004 5:00 am Post subject: |
|
|
That post gave me an idea. I had TwinView turned on because I sometimes use a second monitor. So I tried disabling it, with interesting results. X decided not to start with the below MetaModes transferred to the Modes section.
X wouldn't start, but the console was visible. The console was visible, but did not refresh correctly. To see what was on the current console I had to switch to another VC then back.
So I don't think it's solely the TwinView stuff
| Code: | #Second Monitor stuff
Option "TwinView" "True"
Option "TwinViewOrientation" "RightOf"
Option "SecondMonitorHorizSync" "30-96"
Option "SecondMonitorVertRefresh" "50-160"
Option "MetaModes" "1280x1024@2560x1024,NULL; 1280x1024,NULL; 800x600@1600x600,NULL; 800x600,NULL; 640x480@1280x480,NULL; 640x480,NULL"
Option "ConnectedMonitor" "CRT,CRT"
|
I forgot to mention earlier that I have a GForce4 |
|
| Back to top |
|
|
AceTheFace
n00b
Joined: 16 Aug 2003
Posts: 49
Location: Germany/Ulm
|
| Posted: Tue Feb 03, 2004 7:46 am Post subject: |
|
|
I solved this problem by unplugging the permanent connection between tv and tv-out. After a reboot, the virtual terminals worked great again...
Greetz,
Ace |
|
| Back to top |
|
|
russofris
Apprentice
Joined: 14 Sep 2003
Posts: 163
|
| Posted: Tue Feb 03, 2004 8:44 am Post subject: |
|
|
| AceTheFace wrote: | I solved this problem by unplugging the permanent connection between tv and tv-out. After a reboot, the virtual terminals worked great again...
Greetz,
Ace |
Looking at the nvnews.net forums, removing secondary displays is a valid workaround. The problem appears to be caused by problematic VBios's. If your mfr has a VBios update, I would recommend downloading and installing it.
Thank you for your time,
Frank Russo |
|
| Back to top |
|
|
filmore
n00b
Joined: 16 Jan 2004
Posts: 18
|
|
| Back to top |
|
|
|
Multimedia
