No hdmi video on Asus AT3N7A-I with versions newer than 195.36.31

[mh9]

Hello all,

Sorry if this has already been addressed, but I searched the forums and the web and didn’t find anything.

My system/configuration:
Asus AT3N7A-I
hdmi video out to Samsung HL-S6187 DLP
optical audio out to Yamaha RX-V995
Mythbuntu 10.04 x86_64 using mythbuntu-repos Auto Builds for 0.23.1

Everything has worked perfectly since I bought the motherboard (Feb 2010) up to, and including, the NVIDIA driver version 195.36.31. However, with every version I have tried since 195.36.31, including the latest 260.19.12 version, the hdmi video absolutely refuses to work once the NVIDIA driver kicks in. I get normal video output with the Grub boot loader and the Mythbuntu splash screen, but as soon as the NVIDIA logo flashes, the screen goes blank and I get the “Weak or no signal” message.

The system is still alive. I can ssh into it, stop the gdm service (yes, the installer says gdm is still active), revert to 195.36.31 and everything works like it should again.

After a little more sleuthing on 260.19.12, I found that if I connect a VGA cable between the motherboard and the TV, the video is actually coming through on the VGA port. I can then use nvidia-settings to reconfigure the xscreens, save to xorg.conf (overwriting, never merging) and restart gdm, but the same exact thing happens...the NVIDIA logo flashes on the hdmi output and the screen goes blank with the “Weak or no signal” message.

A copy of the bug report log is attached.

Thanks in advance for your help,
mh9

[Fackamato]

I had this board running 2xx.xx drivers for months (almost a year), I never had any issues with the audio. I doubt this is NVIDIA related. (and there's the bug report?)

[mh9]

Nowhere in my post did I ever say I had an audio issue. Also not sure how you could have been running 2xx.xx drivers for almost a year since they have only been out for six months. And finally, I didn't say there was a bug report; I said I attached the bug report log as outlined in the posting guidelines. But thanks for your help!

[Fackamato]

Originally Posted by mh9

Nowhere in my post did I ever say I had an audio issue. Also not sure how you could have been running 2xx.xx drivers for almost a year since they have only been out for six months. And finally, I didn't say there was a bug report; I said I attached the bug report log as outlined in the posting guidelines. But thanks for your help!

Chill. Busy day.

Anyway, just saying that it works perfectly!

[crajohns6965]

I have the exact same issue - I am pretty sure it is related to something with the TV (I have a Samsung HLS-6187w). If I a DVI-HDMI cable, it works great. I'm not sure if it is the EDID or something, but I definitely have the same symptoms.

[BigdaveyL]

*bump*

I have a similar problem when I hook my ION box up to my TV via HDMI.

Worked with older drivers (as per title).

Looks like a regression of some sort. Any word on getting this fixed?

[mh9]

bump (again)

Unfortunately the AT3N7A-I motherboard doesn't have DVI out so the crajohns6965 workaround won't work for me.

Would really appreciate some Nvidia help here. Please?

[Stephen Warren]

mh9, A couple of things spring to mind:

1) The X log file claims that your TV is connector to your PC via *both* HDMI and VGA. Do you have two cables plugged in? If so, removing whichever connection you aren't using wouldn't hurt.

2) I see the following in your xorg.conf:

Option "metamodes" "DFP: 1360x768 +0+0"

Can you please try removing this? It's possible that even though that mode is within the timing limits specified by your monitor's EDID, your monitor won't display that mode.

[mh9]

Hi Stephen (and thanks!),

Unfortunately, I have tried both of your suggestions and still get the same results...a black screen with the “Weak or no signal” message.

The only reason I had the two cables connected was to see if video was actually going through the VGA vs the HDMI, but my normal configuration is HDMI only. As for the resolution, I used to use 1360x768 because 1920x1080 resulted in blurry text, but with the 195 driver I am now running at the native 1920 and it looks perfect.

But still, as soon as I install any newer driver...black screen with the “Weak or no signal” message.

If you have any other suggestions or would like me to try any debug stuff, I am happy to experiment. I am a software engineer of 20+ years and quite technically competent so I should be able to figure things out without a lot of handholding.

Thanks again!

[Stephen Warren]

I'd suggest installing both a failing/working driver, and running on each:

X -logverbose 6

That should spew a bunch of mode validation data into /var/log/Xorg.0.log. Perhaps there will be some obvious difference there; post them here, and we can take a look too.

Finally, if you can ssh into the system while there's no display, you could try running:

DISPLAY=:1 nvidia-settings -c :0

(Replace :1 with your SSH forwarded X display name)

and that'll fiddle with your main X server's display yet display on your client machine.

Then, go to the page for your monitor, and try tweaking the GPU scaling options, or even the X Server Display Configuration and see if you can find a mode that works.

[mh9]

Hello Stephen,

Per your suggestions, here's what I did.

Connection via HDMI cable only running at the native 1920 resolution.

Working driver: 195.36.31
Non-working driver: 260.19.29

Ran 'X -logverbose 6' and captured the Xorg.0.log for each driver (see attached).

Since both logs contained timestamps which would cause major comparison issues, I ran them through a simple sed script to clean them up a bit.

mh9@m0:~
$ sed -e's/Jan 11 17.*NVIDIA/NVIDIA/' Xorg.0.log.195 > 195.txt 
mh9@m0:~
$ sed -e's/Jan 11 17.*NVIDIA/NVIDIA/' Xorg.0.log.260 > 260.txt

Then a diff.

mh9@m0:~
$ diff 195.txt 260.txt 
16c16
< (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 11 17:19:42 2011
---
> (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 11 17:35:22 2011
79c79
< (II) NVIDIA GLX Module  195.36.31  Thu Jun  3 08:59:25 PDT 2010
---
> (II) NVIDIA GLX Module  260.19.29  Wed Dec  8 12:24:30 PST 2010
105c105
< (II) NVIDIA dlloader X Driver  195.36.31  Thu Jun  3 08:27:29 PDT 2010
---
> (II) NVIDIA dlloader X Driver  260.19.29  Wed Dec  8 12:10:14 PST 2010
172c172
< (--) NVIDIA(0): Connected display device(s) on ION at PCI:2:0:0:
---
> (--) NVIDIA(0): Connected display device(s) on ION at PCI:2:0:0
mh9@m0:~

Also, Immediatley after installing 260, I did a diff on the xorg.conf to be sure nothing had changed in there.

mh9@m0:/etc/X11
$ diff xorg.conf xorg.conf.backup 
2c2
< # nvidia-xconfig:  version 260.19.29  (buildmeister@swio-display-x86-rhel47-04.nvidia.com)  Wed Dec  8 12:27:39 PST 2010
---
> # nvidia-xconfig:  version 1.0  (buildmeister@builder62)  Thu Jun  3 09:41:37 PDT 2010
mh9@m0:/etc/X11

No matter what I did remotely via nvidia-settings with 260, I couldn't get anything to display on the screen. However, I could change everything interactively with 195.

Finally, reverted back to 195.36.31 but had to reboot in order to get gdm to start again. I couldn't simply do a 'sudo service gdm restart'.

Hmm...?

Thanks,
mh9 (michael)

[Leech]

I have the same motherboard, and have recently tried to get it finally set up.

So I can say without a doubt that it does (mostly) work with the 260.19.29 driver. The thing that is breaking it for me is the fact that with the 260 driver, it no longer provides the option for the ION chipset to do overscan compensation.

Since the ION is almost specifically tailored to HTPCs and connecting to HDTVs, I can't imagine why this is disabled in newer drivers. From other forum postings, it apparently works fine to do overscan compensation in Windows, but in Linux the option is simply not there.

Could you verify for me that the option is there under the 195.x drivers? If so, I'll try to manage a way to downgrade them for Arch Linux.

For your issue, I can't recall if Ubuntu 10.04 still has an xorg.conf, or if it uses the xorg.conf.d structure, but I would try to rename your xorg.conf (or move the files out of xorg.conf.d) and let Xorg autodetect with only the HDMI cable plugged in and see if it works.

leech