GF4 + 4393 + RH 9 major problem

[tealeaf]

I'm too lazy to attach anything at the moment (i need to go to sleep), but I figure I will let you know about my problem anyway in case you know something about it.

Everything works fine, like glxgears (high framerates too: 4500+), and gl games as long as they run in a window. As soon as anything (like tuxracer) tries to go fullscreen, bang. I lose video signal. Everything still works, because I can hit ESC to get out of the game and the video comes back. I'm using an LCD panel with DVI (my preferred method). I have an old but reliable Asus A7V-133 board with Athlon 1.2Ghz and 512M PC133 RAM.

I've had nvidia driver installed previously and I had all sorts of games running, like tuxracer and ut2k3 without any problems (other than being somewhat slow in ut2k3), fullscreen and all. However, I've used other distros like Gentoo and Debian with older glibc and obviously no NTPL in the linux kernel, etc. So, basically my hardware is good :). I had no stability issues with nvagp in the past. This looks like a software bug to me.

So if you want, yes, I can attach logs, just not right now. Over and out. Nice installer btw.

[Andy Mecham]

Yes, please attach your X log and XF86Config file.

--andy

[tealeaf]

Please note that in the log, everything up to and INCLUDING this line:

AUDIT: Sat Apr 5 14:04:42 2003: 2449 X: client 4 rejected from local host

Is what happens during normal X startup (startx command).

Everything AFTER that line is what happens when I run tuxracer, which tries to enter fullscreen mode where I lose the video signal.

Additional info: this is pretty much vanilla RH9 setup (workstation, default package selection for workstation). I did add ALSA 0.9.2 driver from freshrpms.net (and there is some minorly flaky behavior with that driver), but tuxracer runs fine with music and all in a window and xmms runs fine and I can play music from my CD-ROM too. I followed instructions when installing NVIDIA driver. Also, everything worked in the past under Gentoo and Debian with older NVIDIA drivers, including fullscreen mode w/ DVI, etc... In other words, I had no problem whatsoever (not even stability problems).

Thanks in advance for any help. If you want I can also provide strace or any other info you may want.
--Leo

[Andy Mecham]

Can you start X in 640x480 at all?

--andy

[tealeaf]

Yes, I can.

I'm attaching a verbose log. The only difference in config file is that modes line only has one mode in it.
--Leo

[tealeaf]

First I tried running with Option "UseEdidFreqs" "1".

This didn't cure the loss of viceo signal issue, but it made display look pretty bad with the jittering pixels (same as running at higher than 60hz refresh).

Second, I plugged the analog cable in during a reboot. When I was running via analog connection, lo and behold, tuxracer and frozen bubble were no longer refusing to enter a fullscreen mode!

So, if you have Hitachi CML181SXW panel with GF4 card and RH9 + 4349 NVIDIA driver, please use analog connection as a work around for now.

Thanks Andy!
--Leo

[tealeaf]

One minor correction. Tuxracer doesn't run in a window (at least I don't know how). I meant I was running frozen bubble in a window with music. Tuxracer music doesn't work.
--Leo

[bwkaz]

Sounds like another facet of "the DVI bug" to me.

Especially since it's fixed by using an analog connection... (did I read that right? they both work now?)

[tealeaf]

Yes you read it right. :)
--Leo

[tealeaf]

RH Bug Report for DVI (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=84834)

Check out the above. I wish I found this sooner.
--Leo

[Andy Mecham]

No, this is separate. That thread involves the 2D opensource "nv" driver, not the 3D "nvidia" driver.

Also, I don't think this is another instance of the other DVI bug we're tracking now - your machine would have hung if it were.

--andy