nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Switching from X to console results in black console in 169.07 (http://www.nvnews.net/vbulletin/showthread.php?t=104931)

Maxim Levitsky 12-23-07 06:13 PM

Switching from X to console results in black console in 169.07
 
1 Attachment(s)
It is actually bit more complicated

1) I suspend the system to ram.
2) Resume works perfectly (with compiz running)
3) Switch from X to VT works.
4) I restart the X (ether normally, or with Ctrl+Alt+Bks)
4) Switching to VT now results in black screen.

100.14.23 works perfectly (it is probably the best release ever)

Nvidia GeForce 7600 GS.

Maxim Levitsky 12-24-07 10:55 PM

Re: Switching from X to console results in black console in 169.07
 
After downgrading to 100.14.23 I realized that it has the same problem.
I installed 100.14.19 and I it for sure works fine.

So this bug happened between 100.14.19 and 100.14.23.
Please take a look at it, there were not many changes between those version
(Expect for long awaited fix for compiz vt switch bug)

Maxim Levitsky 12-25-07 09:20 PM

Re: Switching from X to console results in black console in 169.07
 
I checked few more things:

1) Bug doesn't depend on whenever framebuffer enabled or not.
I get exactly the same behavior, black screen, after X restart after suspend to ram.

2) It seems that X driver sets screen to an invalid mode, as the display doesn't react to OSD menus, and if I connect it via VGA cable (normally it is connected via DVI) I get "signal out of range" error

3) VGA bios seems to be totaly confused, all commands like
vbetool vgamode 0, vbetool vbemode 283, vbetool vgastate on/off all return without error message, but do nothing.

Any ideas?

Maxim Levitsky 12-27-07 06:47 AM

Re: Switching from X to console results in black console in 169.07
 
Also same thing happen if I suspend system to disk.

Maxim Levitsky 12-28-07 06:18 AM

Re: Switching from X to console results in black console in 169.07
 
Bump

Maxim Levitsky 12-28-07 11:38 PM

Re: Switching from X to console results in black console in 169.07
 
I don't understand why, but it seems now that I see same behavior with 100.14.19.

It did work fine, but it seems that it shows same black consoles now.
I tried lot of different configurations, but now I can 100% reproduce this bug on 100.14.19.
It is very annoying, especially now since I know when this happens.

I remember I have seen black consoles for quite long time, but I didn't know why this happens.

Anyway this is the last time I ask about this.

I have one single question, does nvidia listen to bug reports?
If I get no answer from nvidia, I assume that it is useless to report anything here.

Thanks for support,
Maxim Levitsky

Maxim Levitsky 01-04-08 01:34 AM

Re: Switching from X to console results in black console in 169.07
 
Now I am using 96.43 for three days, and I don't see this problem.
Other drivers just don't work.

So to summarize:

096.43.00 - works
100.14.11 and above doesn't

zander 01-04-08 04:07 AM

Re: Switching from X to console results in black console in 169.07
 
Just to be sure (since the versions you reported the problem against changed a few times), you're saying that 96.xx drivers work, but more recent drivers don't? Does this include 100.14.xx releases before 100.14.11?

Maxim Levitsky 01-04-08 07:56 AM

Re: Switching from X to console results in black console in 169.07
 
I myself don't understand now why the versions changed.

First driver I have ever used for this card was 9746.
Then I progressively updated the driver up to 169.07.
At some point I did see those black consoles, but I didn't understand the reason behind them.

Then I finally understood the sequence that 100% reproduces this bug, and reported it (and I assumed that 100.14.23 works)

Then I did test 100.14.23, and found that bug is there, and I tested 100.14.19 and I remember it did work fine. I reported this here, and I installed 169.07 again to try and gather more info about the bug.
But for my surprise, I can't anymore "not reproduce" this bug on 100.14.19
I always see black console, after running the above sequence.
Probably I forgot to reset X after suspend to ram when I did the test.

Now I installed 96.43, and I actually use it for few days, and all my attempts to reproduce this bug failed, so I assume that this version works.

Now I did more testing:
9746 - works
9755 - works
100.14.03 - doesn't work.
10.14.19 (tested again) - doesn't work

96.43.01 - (tested again) - works

Also the bug doesn't seem to be random, I repeated the tests for 100.14.03
and 10.14.19 for 3 times, and have seen the same thing.


So I assume that somewhere between 9755 and 100.14.03 this bug occurred.

Note: to make the drivers work I edited the kernel layer code (but all changes I did were trivial) and since I use Xorg 7.3+ 2.6.24-rc6, I had to use -ignoreABI, and for 9746+9755 copy drivers from /usr/X11R6.9 to /usr/lib/xorg/.. .

I am sure that this bug doesn't depend on xorg and/or kernel, since I did see those black console for qute long time, and just days ago I updated the system from kubuntu feisty to kubuntu hardy, and I did test the driver with 2.6.23 , and I have seen same black consoles.

Now about vbetool.
I told that vbetool doesn't help when consoles are black, so I did more testing, and this is what I found:

Running 'vbetool vbemode set $mode' when X is active works eg:

vbetool vbemode set 279 ; sleep 10 ; vbetool vbemode set 283
works as expected.

but when I use conspy to type the commands on console, then switch to it, and press "enter", I also see screen that screen blink, and then I can finally open monitor's OSD and see there the resolution I selected with vbetool, but the console is still black, even if I select the same resolution the console driver thinks console is (I use 1280x1024 on both console and X)

Regards,
Maxim Levitsky

hussam 01-10-08 06:01 AM

Re: Switching from X to console results in black console in 169.07
 
same as http://www.nvnews.net/vbulletin/show...35#post1514035
"Steps to fix:
1. Run CTRL+ALT+F1.
2. It's blank so I have to blindly type in stuff.
3. Type root and enter the root password.
4. Run init 3 to exit Xserver.
5. At this moment, I'm blindly typing in stuff because I only see a blank screen.
6. Run pm-hibernate or any other hibernate script.
7. Resume from hibernate.
8. Virtual terminals are no longer blank (I can see again)."

Maxim Levitsky 01-11-08 09:10 AM

Re: Switching from X to console results in black console in 169.07
 
Yes, this helps thanks, but it is very very slow and annoying and what can I say more.

I need to know one thing from nvidia: will this bug be fixed?
Like I said 100.14.03 is the first driver that shows this bug.
9755 works fine (but it is unusable with modern xorgs)

ikhnaton 01-19-08 12:10 PM

Re: Switching from X to console results in black console in 169.07
 
Hi,

I have a GeForce Go 6150 and upgraded the nvidia driver to the newest one, 169.07. So I became to expect this problem. Everything is alright unless I switch X to console using CTRL+ALT+FX. Problem persistis when I exit X. The same with XTRL+BACKSPACE...

I remember that, in the past, was a bug likely this and the solution was disable the TV output, but this is unlikely.

I'm still waiting the solution...

--------------------------------

The old driver 100.14.19 works fine were.


All times are GMT -5. The time now is 05:27 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.