problems escaping from X - Page 4

wilq · 08-13-03, 03:04 PM

So... I am lucky

pe1chl · 08-13-03, 03:39 PM

After configuring TV-OUT I have noticed that sometimes the screen goes black after exiting X, but the system does not crash! When I hit CTRL-ALT-DEL at that time it cleanly shuts down and reboots.
(but I cannot see that on the screen, just by watching the disk activity and hearing the beeps)

This is on a SuSE-8.2 system (kernel 2.4.20)

guills · 08-13-03, 05:09 PM

pe1chl, that's another problem though I guess... this bug freezes everything solid.. doesn't respond to ctrl-alt-del or even network activity

zgwortz · 08-13-03, 05:32 PM

Just adding my quick two cents -- I also am seeing this problem on the new Mandrake 2.4.21-0.25mdk kernel I compiled and installed yesterday (with the newest NVidia drivers). I had not seen this with the Mandrake 9.1 default kernel (0.13mdk), but I don't know which drivers that installs.

This machine is ONLY connected via it's TV-Out, being intended to eventually turn into a PVR machine. And I only noticed the problem when shutting down or rebooting the machine, since I was using Konsole under KDE for my command line stuff. Interestingly, it did NOT crash during the reboots -- just sat long enough for it to finish shutting down, and it eventually rebooted just fine.

I'm not as sure it survived the shutdown though -- had to guess it was done and power off manually.

Oh, and it *really* looks to me like a lot of old graphics errors I haven't seen in years -- the pixel shifter thinks it's in a monochrome bit depth, while the system thinks the frame buffer is a color bit depth. I used to see this exact type of pattern all the time when debugging on the Mac as it shifted into monochrome during a breakpoint...

-->Zgwortz

guills · 08-16-03, 02:28 AM

just trying to get this thread up in the front page...maybe Andy will notice us again

mweissen · 08-16-03, 04:55 AM

i just wanted to note that this problem also occurs on my laptop, a Toshiba Satellite 2430-402 which is equipped with the GeForce4 420Go.
with the 4363 driver a switch to the console produces a total hangup (doesn't even respond to ping's after that). with the 4496 driver this doesn't occur any more but i get a black screen instead of the console. i can switch back to x, but the console doesn't work. it may have something to do with the fact that this laptop has a tvout plug, but the problem occurs regardless if i use the tvout or not.
there is one driver that works correctly: the 4191 drivers works correctly for me, but it's noticeable slower!
i hope that there will be a solution for this problem soon.

The Daan · 08-27-03, 08:40 AM

Quote:

Originally posted by guills
just trying to get this thread up in the front page...maybe Andy will notice us again

Andy?? any progress yet...?

vnpenguin · 08-27-03, 10:02 AM

Hi all,
The same problem for me:
Athlon 1800;
GForce 4 MX 440 64 MB
Redhat 9 / Kernel 2.4.22 (build from kernel.org)
nVidia driver 4496.

I HAVE TO downgrade to 4363 and the problem was solved

So I think there is a bug(?) in the latest driver nVidia ?

rehabdoll · 08-27-03, 08:39 PM

I have this problem. tried a bunch of drivers, kernel 2.4.20, 2.4.22, 2.6.0-test4

Works when removing the s-video cable.

nforce2, Ti4200 (creative)

mweissen · 08-28-03, 03:37 AM

the fact that this problem occurs in every driver that was released past december 2002 shows me that nvidia's qa for linux drivers isn't really doing a good job.
if i had i choice now i would have bought a laptop with an ati chip...
for my desktop it's clear for me now that i won't go nvidia.

guills · 08-28-03, 09:48 AM

I must agree. I've always been a big supporter of NVIDIA because of their committment to release good linux drivers, as opposed to ATI who used to release half-a**ed drivers and no specs for their cards. Now it seems ATI has decent support.

It's been a year now since I've begun experiencing problems with nvidia drivers under Linux and nobody seems to care. It looks like there's 1 or 2 engineers working part-time on the linux drivers and no QA. Plus they've lost the tech. edge they once had on ATI.

I don't know what's going on inside NVIDIA but it sure doesn't look good from the outside

rehabdoll · 09-02-03, 09:26 AM

Does anybody know in which version this bug started to appear? i need 3d-support in linux (and my tv connected) on my gf4.

08-16-03, 04:55 AM	#42
mweissen Registered User Join Date: Aug 2003 Posts: 8	i have this problem too i just wanted to note that this problem also occurs on my laptop, a Toshiba Satellite 2430-402 which is equipped with the GeForce4 420Go. with the 4363 driver a switch to the console produces a total hangup (doesn't even respond to ping's after that). with the 4496 driver this doesn't occur any more but i get a black screen instead of the console. i can switch back to x, but the console doesn't work. it may have something to do with the fact that this laptop has a tvout plug, but the problem occurs regardless if i use the tvout or not. there is one driver that works correctly: the 4191 drivers works correctly for me, but it's noticeable slower! i hope that there will be a solution for this problem soon.

08-28-03, 03:37 AM	#46
mweissen Registered User Join Date: Aug 2003 Posts: 8	really bad qa for linux drivers the fact that this problem occurs in every driver that was released past december 2002 shows me that nvidia's qa for linux drivers isn't really doing a good job. if i had i choice now i would have bought a laptop with an ati chip... for my desktop it's clear for me now that i won't go nvidia.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
problems with drivers after 295.40 (OpenSuSE 12.1, GeFroce 7900 GS, Phenom II X4)	alawa	NVIDIA Linux	0	06-09-12 06:37 PM
If you are having problems w/your 9700 please take a look	5150 Joker	Other Desktop Graphics Cards	3	10-05-02 05:01 PM
Nvidia Problems in Slackware 8.1	xtreme	NVIDIA Linux	3	10-01-02 12:03 PM
F1 2002 problems with driver 40.41	arutten	NVIDIA Windows Graphics Drivers	6	10-01-02 07:07 AM
DirectX 8 problems with GeForce4	Derwin	NVIDIA GeForce 7, 8, And 9 Series	19	08-20-02 01:23 AM

08-13-03, 03:04 PM	#37
wilq Registered User Join Date: Aug 2003 Posts: 3	So... I am lucky

08-13-03, 03:39 PM	#38
pe1chl Registered User Join Date: Aug 2003 Posts: 1,026	After configuring TV-OUT I have noticed that sometimes the screen goes black after exiting X, but the system does not crash! When I hit CTRL-ALT-DEL at that time it cleanly shuts down and reboots. (but I cannot see that on the screen, just by watching the disk activity and hearing the beeps) This is on a SuSE-8.2 system (kernel 2.4.20)

08-13-03, 05:09 PM	#39
guills Registered User Join Date: Aug 2002 Posts: 28	pe1chl, that's another problem though I guess... this bug freezes everything solid.. doesn't respond to ctrl-alt-del or even network activity

08-13-03, 05:32 PM	#40
zgwortz Registered User Join Date: Aug 2003 Posts: 2	Just adding my quick two cents -- I also am seeing this problem on the new Mandrake 2.4.21-0.25mdk kernel I compiled and installed yesterday (with the newest NVidia drivers). I had not seen this with the Mandrake 9.1 default kernel (0.13mdk), but I don't know which drivers that installs. This machine is ONLY connected via it's TV-Out, being intended to eventually turn into a PVR machine. And I only noticed the problem when shutting down or rebooting the machine, since I was using Konsole under KDE for my command line stuff. Interestingly, it did NOT crash during the reboots -- just sat long enough for it to finish shutting down, and it eventually rebooted just fine. I'm not as sure it survived the shutdown though -- had to guess it was done and power off manually. Oh, and it really looks to me like a lot of old graphics errors I haven't seen in years -- the pixel shifter thinks it's in a monochrome bit depth, while the system thinks the frame buffer is a color bit depth. I used to see this exact type of pattern all the time when debugging on the Mac as it shifted into monochrome during a breakpoint... -->Zgwortz

08-16-03, 02:28 AM	#41
guills Registered User Join Date: Aug 2002 Posts: 28	just trying to get this thread up in the front page...maybe Andy will notice us again

08-27-03, 10:02 AM	#44
vnpenguin GeForce4 Join Date: Mar 2003 Location: Belgium Posts: 28	Hi all, The same problem for me: Athlon 1800; GForce 4 MX 440 64 MB Redhat 9 / Kernel 2.4.22 (build from kernel.org) nVidia driver 4496. I HAVE TO downgrade to 4363 and the problem was solved So I think there is a bug(?) in the latest driver nVidia ?

08-27-03, 08:39 PM	#45
rehabdoll Registered User Join Date: Aug 2003 Posts: 4	I have this problem. tried a bunch of drivers, kernel 2.4.20, 2.4.22, 2.6.0-test4 Works when removing the s-video cable. nforce2, Ti4200 (creative)

08-28-03, 09:48 AM	#47
guills Registered User Join Date: Aug 2002 Posts: 28	I must agree. I've always been a big supporter of NVIDIA because of their committment to release good linux drivers, as opposed to ATI who used to release half-a**ed drivers and no specs for their cards. Now it seems ATI has decent support. It's been a year now since I've begun experiencing problems with nvidia drivers under Linux and nobody seems to care. It looks like there's 1 or 2 engineers working part-time on the linux drivers and no QA. Plus they've lost the tech. edge they once had on ATI. I don't know what's going on inside NVIDIA but it sure doesn't look good from the outside

09-02-03, 09:26 AM	#48
rehabdoll Registered User Join Date: Aug 2003 Posts: 4	Does anybody know in which version this bug started to appear? i need 3d-support in linux (and my tv connected) on my gf4.