|07-08-12, 01:26 AM||#1|
Join Date: May 2006
302.17 regression, HDMI hotplug
I just got around to upgrading from 302.11 to 302.17 today.
On the 302.11 driver, I could plug my HDMI cable into my laptop at any time and the X would blink black, then enable the HDMI display. On the 302.17 driver nothing happens when I plug in the HDMI cable. I have to go into the GNOME display manager and as soon as I do the X server blinks blank and then the HDMI display is enabled.
The reverse will happen when I unplug the HDMI cable. The 302.11 driver automatically turned off the HDMI display. On 302.17 nothing automatic happens. I have to go into the GNOME display manager and tell it to turn off the second display, which is still visable even though it is no longer connected.
I preferred the automatic behavior. Is this an intentional change?
Edit: The behavior seems sparatic, which is the worse kind to try and fix. One boot-up the laptop was able to automatically enable/disable if I plugged or unplugged the HDMI cable. On another instance where I closed the lid (GNOME is set to blank the screen) and re-open it the HDMI output was never re-awoken and turning off or unplug/plug did not help. I had to reboot to have HDMI working again. This is turning into a general (collection) of bugs with HDMI.
|Thread||Thread Starter||Forum||Replies||Last Post|
|IOGEAR 3D Complete+ 4-Port HDMI Switcher with 2D/3D Video Processor||News||Latest Tech And Game Headlines||0||06-28-12 06:40 PM|
|302.17 doesn't support my GT 640M||balgo||NVIDIA Linux||14||06-23-12 03:42 PM|
|302.17 for Linux x86/x86_64 released||AaronP||NVIDIA Linux||0||06-16-12 05:12 PM|
|Blu-ray 3D Movie Playback With PC on a 3D HDTV Using HDMI 1.4||News||Latest Tech And Game Headlines||0||05-16-12 04:30 AM|
|HDMI audio ELD weirdness||RockHound||NVIDIA Linux||0||05-11-12 04:45 AM|