flat panel hard lockups

[elanthis]

I've never been able to get my flat panel (SyncMaster 172t) to work in digital mode. I posted a problem report on this previously and never had a fix, so I'll try again.

Some notes: this problem happened both on my old mobo (asus, via k266 based iirc) and the new one (fix an19c). This happened both on Debian/Sid with a custom 2.4.{18-20} kernel, and now on RedHat 9 with it's stock kernel. Happened both on older 3xxx series, and the 4xxx series.

The first post I made, I was told to check my ram (512 DDR, I forget manufacturer, some "cheap" brand, admittedly) w/ memtest86 - I do so, and no problem were found, and I posted those results (and never had a further response; ah well).

The problem only happens in digital mode, not using the CRT connection (this monitor supports both, and can switch between them on the fly). When using the DFP setting, the kernel locks hard - pings do not respond from other machines on the network once X tries to start. The monitor also starts acting rather funky (like it too locks up) until I unplug it from power and back in again.

If I eneable GLX, the logs show it locking up there. If I disable GLX, it locks up when RANDR is loaded. Will of course attach those.

The digital mode does work in the console just fine.

Specs and info:
Video Card: GeForce 3 Ti500
Driver Version: 1.0.4349
Distro: RedHat 9 + rawhide (including XF86)
Video Bios: 03.20.00.16.10
Processor: Athlon XP 1800+
Motherboard: FIC AN19C (kt400 chipset)

Those are just the current specs; had this same problem with older mobo and os, as stated.

[elanthis]

here's the log

[Andy Mecham]

First of all - make sure you're not hitting the KT400 hang. Update to 1.0-4363, and use NVAGP (not AGPGART).

I'll look into this.

--andy

[elanthis]

Updated to latest revision, and set NvAgp 1. Same problem. Attaching updated log.

One line sticks out to me tho:
(II) NVIDIA(0): Verifying AGP usage for Screen 0...
(WW) NVIDIA(0): Failed to verify AGP usage

Anyways, got to the GLX bit and locked up, like before - monitor got all screwy, altho this time it started working again after the computer rebooted (I usually need to power cycle monitor). The console and all that was running over CRT tho ( I have both the CRT and the DVI cables plugged in to both the display and the geforce card, to make testing easier - as a note, the problem is the same whether I do this or have only the dvi cable plugged in).

[Andy Mecham]

Why are you using the ConnectedMonitor option? If you have just the DVI connected as your sole boot device (ie: only monitor connected), what's the output?

--andy

[elanthis]

With only the DVI cable plugged in, the machine comes up fine, all the bootup/console stuff works fine, etc. When I start X, everything comes up, GNOME destkop all that, only I don't see anything. If I quit X (ctrl-alt-backspace) I go back to the console where everything is fine.

The monitor tries some mode changes it appears, then goes into the "no valid input" mode where the power led turns orange.

The log shows that it can't find a display, and is assuming CRT. DVI definitely works, tho, else the console wouldn't show...

[Andy Mecham]

(II) NVIDIA(0): SyncMaster 172t: Using hsync range of 30.00-81.00 kHz
(II) NVIDIA(0): SyncMaster 172t: Using vrefresh range of 56.00-75.00 HzFrom a quick search, it looks like your hsync range is inappropriate for digital. Can you try setting your hsync to 30-63?

--andy

[elanthis]

OK, tried hsync at 30-63, same thing - hard lockup.

And the log...

[Andy Mecham]

OK, i'll track one of these panels down and take a look.

--andy

[elanthis]

righty, thank you.

these things are hard to find; the only place I've seen that carries them in stock is CDW - dunno if you have super nVidia powers and can get samples/test-units tho. ;-)

is it also possibly a hardware problem with the graphics card? i've had several geforce cards fails on me, i'm not too confident in their workmanship. ;-)

the only other card I have to test around here is an old ati radeon 7000, I think it has dvi off the top of my head, but it certainly wouldn't be using the same drivers to test against...

(the card failures all were related to power issues I think - I've since changed the power supply, motherboard, and added a ups system, after having to get two replacements and an upgrade; this card has at least kept working for over 4 months, so that was probably the issue)

[elanthis]

Just an update; same hardware, still doesn't work. I have just yesterday upgraded to the latest nVidia drivers. The machine no longer hard-locks (I can ctrl-alt-del to reboot the dumb thing, anyways), altho I still need to power cycle the monitor afterwards for it to start working again.

DVI works fine until X starts.

Just a refresher:
RedHat9 + various Rawhide and other updates
Kernel 2.4.20 (athlon optimized)
XFree86 4.3
GeForce3 Ti 500
Samsung SyncMaster 172T tft display
Athlon XP 1800+
512MB DDR RAM
Via k400 based mobo (I think)

I'm getting pretty desperate to get this working; I want me my DVI. ;-)

[capybara]

I'm getting pretty desperate to get this working; I want me my DVI. ;-)

Wow, finally I found someone who has nearly my exact problem. See my post (http://www.nvnews.net/vbulletin/showthread.php?threadid=15703) for more details. I'm using a GeForce3 Ti 200, so maybe the similarity between our cards explains why we see it and nobody else does.

With the 4496 drivers I get "No signal" and sometimes a brief "Out of range" error when starting X over DVI. My monitor doesn't need power cycling, and actually ctrl-alt-bksp brings me back to the text console with no trouble. I have played with all possible permutations of the options, and still see nothing on the screen.

Any ideas? I'll be watching this thread now...

[elanthis]

Well, you're lucky then, because nothing I seem to do fixes my display; I have to power-cycle both the display and the machine. i think.

I havent' tested every single option because, frankyl, that would be way too much of a pain in the arse given all the power cycling/rebooting I need to do to test anything. ;-)

[decay]

[QUOTE]Originally posted by capybara
[B]Wow, finally I found someone who has nearly my exact problem. See

I have had the same problem for over a year now.

I get a no signal on my Philips 180P.

It is getting better though, as I have no more lockups or cold boots, just exit X and the screen pops back.

[capybara]

Originally posted by decay
I have had the same problem for over a year now.

I get a no signal on my Philips 180P.

It is getting better though, as I have no more lockups or cold boots, just exit X and the screen pops back. [/B]

So maybe it's not just something I misconfigured.

Decay, what card do you have?

Does anyone out there have a GeForce3 Ti 200 or something close working with DFP?

[decay]

Originally posted by capybara
So maybe it's not just something I misconfigured.

Decay, what card do you have?

Does anyone out there have a GeForce3 Ti 200 or something close working with DFP?

I have a VisionTek 6964, Ti500

Ironically, a long time ago I put Windows on, and the DVI worked great.

[capybara]

The old 2960 drivers seem to work with DFP. So if you value your DVI more than 3d, downgrading might be worthwhile. Can anyone confirm this?

[elanthis]

alright, so I got it working in digital mode. only, here's the catch - I have to use the nv driver. :( Also, I have to boot in DVI mode, which means I have to unplug the VGA cable during boot up (altho I can plug it back in after).

in order to get the nv driver to work, i had to set the CRTCNumber option to "1" (i.e., use the second monitor connection, which is the DVI plug). I also set FlatPanel to on, tho it seems to work without it.

I _still_ can't get the nvidia driver to work. However, the nvidia driver no longer locks up the machine or the monitor. If I try to foce the nvidia monitor to use DVI (set ConnectedMonitor to DFP), my desktop loads up (can tell by sounds/etc.) but I have a blank screen, mode light blinks then turns to orange, etc. If I exit X, the screen switched back to Analog mode, but stays blank - nothing I do except reboot (which I can do cleanly, since the machine isn't locked, and X has exited) will fix it.

If I boot in DVI mode, the same happens. However, if I boot in DVI (i.e., console is digital) and start X in analog mode (what the nvidia and nv driver both do by default), X loads fine, and works, etc. If I then exit X, or even switch to a console, the monitor auto-switches back to digital mode and things work fine - i can switch between console and X happily, and the monitor adjusts accordingly. I just can't for the life of me get it to fricken use DVI/digital mode in X with the nvidia driver.

[elanthis]

log w/ nvidia driver booting using crt display

[elanthis]

log w/ nvidia using forced dfp display

[elanthis]

the config file used for the above logs. teh only difference is for the second log, the ConnectedMonitor DFP option was added.

[Xin(tEb]

Hello all,

I encounter the same problem
Yes I have the nvidia geforce ti 200
and a 1702FP dell
I have installed the latest open source drivers form nvidia, they load well, and i change to "nvidia" in XF86Config
All works in D-sub output with correct tech specs added vert refresh and horiz synchro
ok
But when swithcing to DVI output -it works also in text mode-
in X, something readable appear i can see the desktop but all is green
(on windows 3 monts ago my cable DVI cable worked fine, so it's propaby not hardware problem)
Greeen like grass and pixelate 1 cm line?!?
Help...

Someone on Linux Questions says the problem can be resolved replacing by "vesa" the driver section in XF86Config
ok but what vesa means?
and does this trick will make my output use the nvidia video card or not
I haven't tried yet I need advice

[elanthis]

has any progress been made tracking down the cause of this problem? it's getting to the point I'm quite willing to sacrafice performance to get a card that will actually work in DVI mode - it's rather rediculous having a $600 monitor and a $300 graphics card when neither work together. guess which is cheaper to replace. ;-)

seriously, *anything* I can do to help expediate finding a solution to this, I'm willing to do. if there's any further tests, logs, etc. that I could provide that would help, please let me know so I can do so.

thanks nvidia linux devs. ^,^

[int19]

Seems that you guys are experiencing the same problem I am with getting the DVI panel working. I have a NEC LCD1850X and a PNY Geforce2 ti200
and the latest drivers that I can get to work for me is 3126. After that I get the slow startups (not fixed by the EID or connected monitor tips) and the greenish yellow colors. Something interesting to note is that I tried a geforce 2 ultra (hercules 3d prophet 2 GTS ultra) and not only did that not work with the new drivers, it hard locked the machine. I'll provide a startx --logverbose 5 log if there is interest, and I can send you (Andy) the machine and the monitor (sans hard drives) if you still need a test machine...

Richard

[ToastyX]

To anyone with a GeForce3 experiencing the same problem:

I had the same exact problem with my VisionTek GeForce3 Ti 500 and the Samsung SyncMaster 191T. After searching Google for a bit, I found out that older versions of the GeForce3 BIOS have a bug which causes this problem.

I called VisionTek, and they already knew about the problem. Within 5 minutes, they sent me a new video BIOS via e-mail. I updated the video BIOS, and that took care of the problem.

I'm surprised nobody mentioned this since this is apparently a known problem. I just wish I would have found this thread sooner.