HDMI detected as DVI [Solved]

Issues Related to Hardware (Sound, Video, Printers, Scanners, Webcams, Touchpads, Keyboards, Sensors, Drives, GRUB, etc.)

Moderator: Moderators

HDMI detected as DVI [Solved]

Postby Antidieu » Tue Jun 15, 2010 6:33

I've got an up to date SL 5.3 Gnome x86_64 edition. Well since KMS is force enabled in kernel, the HDMI port of my laptop appears as DVI1 instead of as HDMI1 and I've got no sound from it no matter what I do when I plug it to my LCD TV. But if the TV is plugged in to the laptop at bootup then the HDMI port shows up in xrandr as HDMI1 and TV gets sound from the computer.

I haven't found a solution to the HDMI1 device name changing to DVI1 depending on wether or not a device is connected to that port and I cannot pass the nomodeset option to the kernel because X.org and xf86-video-intel-2.11.0 require KMS to be enabled by default. I'm using HDMI-HDMI cable, no adapters, and this happens with any TV with an HDMI port.

On Windows partition this works out of the box. Before enabling KMS, device name was immutable always appearing as HDMI-1 and always sending the audio signal through it whenever TV was connected. Now when showing up as DVI1 there is no audio signal as if it was a DVI port. Here's my hardware info:

Code: Select all
# lspci | grep -i intel
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)


Perhaps this info is useful too:

Code: Select all
# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: INTEL HDMI 0 [INTEL HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


Yep, it's one of those Intel chipset laptop, in this case a Gateway M-6804m. I googled a little and found in some forums that this behaviour was supposedly fixed in previous kernel versions, but no solution so far. Maybe a kernel patch? Neither am I able to dimm panel backlight since KMS, but that's for yet another post. Please tell me if you need more info.
Last edited by Antidieu on Sun Apr 24, 2011 5:13, edited 1 time in total.
Gateway M-6804m (2 GiB RAM)
Intel Core 2 Duo T5250
Intel GM965/GL960
Antidieu
Simple Hen
 
Posts: 68
Joined: Fri Apr 24, 2009 5:45

Re: HDMI detected as DVI

Postby genfool » Tue Jun 15, 2010 20:21

First I would try alsamixer in a user terminal (not root) f6 to select your sound card, m to unmute...turn all the slides up to max.
Now if you only have 1 slider for pulse, you could try this command,
echo "autospawn = no" > ~/.pulse/client.conf && pulseaudio -k
This will kill pulse audio and get you on alsa. Where you have more control. You can always undo the command and get back on pulse if you want.
Just an idea.
genfool
Technological Hen
 
Posts: 342
Joined: Fri Apr 03, 2009 17:56
Location: Albuquerque, NM

Re: HDMI detected as DVI

Postby Antidieu » Wed Jun 16, 2010 5:49

Hi genfool, thanks for your reply. I've already tried to configure alsamixer and disable pulseaudio. I also made all the steps in Fitzcarraldo guide to setup pulseaudio with no avail.

The problem is NOT that I get no sound at all from HDMI, but that I get sound ONLY when HDMI is plugged since boot up. And accordingly the port is shown as HDMI1 when doing xrandr --prop and I do have sound when I set up the HDMI output in Pulseaudio. But if TV is plugged in to the laptop after kernel booted up and/or a session has been started, then the port appears as DVI1 and there's no sound at all via HDMI cable no matter the configs in Pulseaudio or Alsa. :(

That's why I'm guessing it's actually hardware detection issue related to either KMS or udev. This is affecting my xorg.conf config too as I have a custom modeline for my TV and the monitor section is associated to HDMI output with option

Code: Select all
Option "Monitor-HMDI1" "MyMonitorSection"


in the device section. But if the name keeps changing to DVI1 then X doesn't take the custom modeline for the monitor on that output (besides the sound problem). So I should only add another line in the device section like this

Code: Select all
Option "Monitor-DVI1" "MyMonitorSection"


to cover both cases, but there's still this issue with no sound outputting when output is named DVI1 (instead of HDMI1). English is not my native language, sorry if it's not been clear enough.
Last edited by Antidieu on Fri Jun 25, 2010 13:53, edited 1 time in total.
Gateway M-6804m (2 GiB RAM)
Intel Core 2 Duo T5250
Intel GM965/GL960
Antidieu
Simple Hen
 
Posts: 68
Joined: Fri Apr 24, 2009 5:45

Re: HDMI detected as DVI

Postby Antidieu » Wed Jun 16, 2010 13:03

Briefly, audio doesn't work over HDMI on hotplug, only on coldplug. Take a look at the last post in the forum link below so you can read a simple description of the misfunction I'm talking about:

http://www.uluga.ubuntuforums.org/showthread.php?p=9161492

And these topics are somehow related to the problem of misfunctional hotplugging over HDMI, except for the fact that their problem has to do with both resolution and audio:

http://osdir.com/ml/fedora-test-list/2009-05/msg00583.html
http://osdir.com/ml/fedora-test-list/2009-05/msg00655.html

Finally this bug report concerning display names (only my problem has nothing to do with nonkms booting):

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/392017

In Upstream Kernel Changes section from Ubuntu Launchpad under Karmic Koala branch, it is reported the next changelog

[ Upstream Kernel Changes ]

* e1000e: swap max hw supported frame size between 82574 and 82583
* drm/i915: Initialize HDMI outputs as HDMI connectors, not DVI.
- LP: #392017
* ALSA: hda - Add quirks for some HP laptops
- LP: #449742
* ALSA: hda - Add support for HP dv6
- LP: #449742


Almost a year later, it comes out that HDMI output is still getting initialized as a DVI connector if no monitor is plugged in into the HDMI port before X starts, thus not sending audio signal through it. This happens in either Ubuntu 10.04, Fedora 13, Sabayon 3.5 and every brand new GNU/Linux I've recently tested. So it's likely about a kernel bug or a detection issue. Somebody patch that kernel please!

P.S. All this mess started with KMS. When support for UMS (non-KMS) was available, the port was always properly set up and named as HDMI-1 by X and it output audio signal whenever I plugged in my LCD TV.
Gateway M-6804m (2 GiB RAM)
Intel Core 2 Duo T5250
Intel GM965/GL960
Antidieu
Simple Hen
 
Posts: 68
Joined: Fri Apr 24, 2009 5:45

Re: HDMI detected as DVI

Postby Antidieu » Sat Jun 26, 2010 20:29

Now my conclusion is that it's not kernel's fault maybe, but I'm not pretty sure. It seems likely to be related to a HAL or UDEV detection issue (again) accordingly to my recent discovers, but until now I have not been able to figure it out. :(

I filled a bug report in here

http://bugs.sabayon.org/show_bug.cgi?id=1551

hoping that this issue will be resolved maybe someday or at least proprerly adressed.
Gateway M-6804m (2 GiB RAM)
Intel Core 2 Duo T5250
Intel GM965/GL960
Antidieu
Simple Hen
 
Posts: 68
Joined: Fri Apr 24, 2009 5:45

Re: HDMI detected as DVI [Solved]

Postby Antidieu » Sun Apr 24, 2011 5:17

Upgrading my system to kernel linux-sabayon-2.6.38-r1 solved the detection issue. Now the HDMI port appears as HDMI1 and sound is always sended through it.
Gateway M-6804m (2 GiB RAM)
Intel Core 2 Duo T5250
Intel GM965/GL960
Antidieu
Simple Hen
 
Posts: 68
Joined: Fri Apr 24, 2009 5:45


Return to Hardware

Who is online

Users browsing this forum: No registered users and 1 guest

cron