No X display via HDMI with nvidia driver 256

jdkdonknv · 08-08-10, 01:51 PM

I have a arch linux based htpc and everything was running perfectly with the previous driver, 195.36. I recently updated to nvidia driver version 256.35 and when I rebooted I no longer have a x display on my tv a samsung dlp.

I am able to see the post messages and the boot messages and even the fallback console, but when I startx, the display goes away. If I connect via the dsub vga, X displays fine. So it seems that only the hdmi is the problem. However, the display is much better via hdmi.

I have review the xorg logs etc but I don't see any issues there. It reports it recognizes my onboard nvidia 9300 and even reports the tv as a samsung (via hdmi). I am using the most basic xorg.conf auto generated during the install. As an additional test, I installed the open source nouveau driver, this works fine with the hdmi so the hardware is fine. I can't really use this though as I need the nvidia vdpau decoding.

How should I proceed?

Thanks,
Jeremy

Licaon · 08-08-10, 04:51 PM

Quote:

Originally Posted by jdkdonknv

How should I proceed?

read this first: http://www.nvnews.net/vbulletin/showthread.php?t=46678

jdkdonknv · 08-08-10, 05:33 PM

Sorry, seems I missed that sticky.

1). This is not a stability problem, it always happens.
2). VDPAU, not the issue.
3). I have searched the forum, although I might have missed a post.
4). See above for problem discription.
4a). nvidia-bug-report.log now attached.
4b). I did not use the nvidia installer.
4c). startx output:

Code:

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.34-ARCH x86_64 
Current Operating System: Linux media 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64
Kernel command line: root=/dev/disk/by-uuid/9f246680-5ae1-4728-9803-a44bf6b07ae8 resume=/dev/sda3 ro acpi_enforce_resources=lax 3
Build Date: 21 June 2010  12:01:49PM
 
Current version of pixman: 0.18.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug  8 17:18:35 2010
(==) Using config directory: "/etc/X11/xorg.conf.d"
gnome-session[3935]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
gnome-session[3935]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
GNOME_KEYRING_CONTROL=/tmp/keyring-hWxFjx
SSH_AUTH_SOCK=/tmp/keyring-hWxFjx/ssh
GNOME_KEYRING_PID=3975
GNOME_KEYRING_CONTROL=/tmp/keyring-hWxFjx
SSH_AUTH_SOCK=/tmp/keyring-hWxFjx/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-hWxFjx
SSH_AUTH_SOCK=/tmp/keyring-hWxFjx/ssh
Window manager warning: Failed to read saved session file /home/jman/.config/metacity/sessions/1024cc343cb44f5e85128130591912334900000039350020.ms: Failed to open file '/home/jman/.config/metacity/sessions/1024cc343cb44f5e85128130591912334900000039350020.ms': No such file or directory

(polkit-gnome-authentication-agent-1:4028): polkit-gnome-1-WARNING **: Unable to determine the session we are in: Remote Exception invoking org.freedesktop.ConsoleKit.Manager.GetSessionForUnixProcess() on /org/freedesktop/ConsoleKit/Manager at name org.freedesktop.ConsoleKit: org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '4028' org.freedesktop.ConsoleKit.Manager.GeneralError Unable%20to%20lookup%20session%20information%20for%20process%20%274028%27
Initializing tracker-miner-fs...
Tracker-Message: Checking XDG_DATA_HOME is writable and exists
Tracker-Message:   XDG_DATA_HOME is '/home/jman/.local/share'
Tracker-Message:   Path is OK
Tracker-Message: Setting process priority
Tracker-Message: Setting up monitor for changes to config file:'/home/jman/.config/tracker/tracker-miner-fs.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/jman/.config/tracker/tracker-status-icon.cfg'
Initializing tracker-store...
Tracker-Message: Checking XDG_DATA_HOME is writable and exists
Tracker-Message:   XDG_DATA_HOME is '/home/jman/.local/share'
Tracker-Message:   Path is OK
Tracker-Message: Setting up monitor for changes to config file:'/home/jman/.config/tracker/tracker-store.cfg'
** Message: Loading defaults into GKeyFile...
Tracker-Message: Loading defaults into GKeyFile...
Tracker-Message: Log verbosity is set to 2, enabling D-Bus client lookup
Tracker-Message: Registering D-Bus service...
  Name:'org.freedesktop.Tracker1'
Tracker-Message: Loading defaults into GKeyFile...
Starting log:
  File:'/home/jman/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: tracker-store 0.8.12
Starting log:
  File:'/home/jman/.local/share/tracker/tracker-store.log'
Tracker-Message: General options:
Tracker-Message:   Verbosity  ............................  2
Tracker-Message: Store options:
Tracker-Message:   Readonly mode  ........................  no
Tracker-Message: Registering D-Bus object...
Tracker-Message:   Path:'/org/freedesktop/Tracker1/Status'
Tracker-Message:   Type:'TrackerStatus'
Tracker-Message: Setting database locations
Tracker-Message: Checking database directories exist
** Message: Initializing gksu extension...
Tracker-Message: Checking database version
Tracker-Message: Checking database files exist
Tracker-Message: Loading databases files...
Tracker-Message: Didn't shut down cleanly last time, doing integrity checks
Tracker-Message: Loading database... '/home/jman/.cache/tracker/meta.db' (metadata)
Tracker-Message: Opened sqlite3 database:'/home/jman/.cache/tracker/meta.db'
Tracker-Message:   Setting cache size to 2000
Tracker-Message: Loading database... '/home/jman/.cache/tracker/contents.db' (contents)
Tracker-Message: Opened sqlite3 database:'/home/jman/.cache/tracker/contents.db'
Tracker-Message:   Setting cache size to 1024
Tracker-Message: Loading database... '/home/jman/.cache/tracker/fulltext.db' (unknown)
Tracker-Message: Opened sqlite3 database:'/home/jman/.cache/tracker/fulltext.db'
Tracker-Message:   Setting cache size to 512
Tracker-Message: Opened sqlite3 database:'/home/jman/.cache/tracker/meta.db'
Tracker-Message:   Setting cache size to 2000

4d). I hope my title is adequate.

gradinaruvasile · 08-08-10, 11:32 PM

You use a new xorg. Maybe that has to do with your issue?
Also, if you connect a monitor to the vga/digital port of the card and start the computer with it and then plug the hdmi device and launch nvidia-settings, do you see both attached displays there?
If yes, try to disable the vga and make the hdmi your primary x screen. This can be done runtime, i did it when i changed my monitor from vga to digital connector (the monitor has both interfaces).

jdkdonknv · 08-09-10, 11:10 PM

I've got the new xorg version 1.8 and I've tried a few configuration files. I just using the basic for now. I really don't think thats the issue unless there is some NEW specific setting for the hdmi, the older verison xorg.conf had nothing specific to hmdi.

nvidia-settings does show both monitors. I've tried setting it up as twin view, no hdmi display. I set the hdmi to default, with the crt disabled, no hdmi display.

I'm betting this worked with the previous driver version, 195.xx.

08-08-10, 11:32 PM	#4
gradinaruvasile Registered User Join Date: May 2008 Posts: 199	Re: No X display via HDMI with nvidia driver 256 You use a new xorg. Maybe that has to do with your issue? Also, if you connect a monitor to the vga/digital port of the card and start the computer with it and then plug the hdmi device and launch nvidia-settings, do you see both attached displays there? If yes, try to disable the vga and make the hdmi your primary x screen. This can be done runtime, i did it when i changed my monitor from vga to digital connector (the monitor has both interfaces).

08-09-10, 11:10 PM	#5
jdkdonknv Registered User Join Date: Aug 2010 Posts: 3	Re: No X display via HDMI with nvidia driver 256 I've got the new xorg version 1.8 and I've tried a few configuration files. I just using the basic for now. I really don't think thats the issue unless there is some NEW specific setting for the hdmi, the older verison xorg.conf had nothing specific to hmdi. nvidia-settings does show both monitors. I've tried setting it up as twin view, no hdmi display. I set the hdmi to default, with the crt disabled, no hdmi display. I'm betting this worked with the previous driver version, 195.xx.

08-08-10, 01:51 PM	#1
jdkdonknv Registered User Join Date: Aug 2010 Posts: 3	No X display via HDMI with nvidia driver 256 I have a arch linux based htpc and everything was running perfectly with the previous driver, 195.36. I recently updated to nvidia driver version 256.35 and when I rebooted I no longer have a x display on my tv a samsung dlp. I am able to see the post messages and the boot messages and even the fallback console, but when I startx, the display goes away. If I connect via the dsub vga, X displays fine. So it seems that only the hdmi is the problem. However, the display is much better via hdmi. I have review the xorg logs etc but I don't see any issues there. It reports it recognizes my onboard nvidia 9300 and even reports the tv as a samsung (via hdmi). I am using the most basic xorg.conf auto generated during the install. As an additional test, I installed the open source nouveau driver, this works fine with the hdmi so the hardware is fine. I can't really use this though as I need the nvidia vdpau decoding. How should I proceed? Thanks, Jeremy