Detecting HDMI Samsung TV plug/unplug

ruppertus · 06-22-2013, 06:26 PM

Hi,

I have a problem with plugging my Monitor/TV (with both D-SUB and HDMI connectors - D-SUB/VGA works fine, HDMI is not detected) to my Debian media server.
The problem is when I plug either HDMI cable or DisplayPort adapter, connected to the same HDMI cable to my motherboard,
then system doesn't register any event. I've tried that using the following command:

Code:

udevadm monitor

(there isn't any new event)

I checked xrandr (using VNC server):

Code:

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)

I checked directly what drm module registred:

Code:

cat /sys/class/drm/card0-HDMI-A-1/status
cat /sys/class/drm/card0-HDMI-A-2/status

and neither HDMI nor DP doesn't work.

Of course I've checked the cable and TV and I'm able to connect it to my laptop with NVidia Optimus and everything works.
But in case of my server I have only Intel HD 2000 build-in my Core i7 (Sandy-Bridge) processor and I use intel driver.

I've been digging in this problem for several days.
I fought I may force graphic card to see connected monitor:

Code:

Option         "ConnectedMonitor" "DP1"
Option         "CustomEDID" "DP1:/etc/X11/edid.bin"
Option         "IgnoreEDID" "false"
Option         "UseEDID" "true"

but these options only work for NVidia card. Btw. I had to dump edid data for that.

Another probe was flashing the Bios of my mainboard, because I've noticed some changes around HDMI in the bios changelog.
But that also didn't work.

I've noticed that there is an option in the DRM (DRM_LOAD_EDID_FIRMWARE) to force using EDID data from file, but I don't think that may be the good path.

Then I updated the kernel to the newest one (3.9.7). Almost the default for debian configuration didn't work as well.
Finally I've noticed that there is a special module in the kernel called
Samsung HDMI Driver (VIDEO_SAMSUNG_S5P_HDMI) but I can't turn it on playing with make menuconfig.
I've stacked in VIDEO_SAMSUNG_SP_TV. I can't find it and PLAT_S5P as well.

Code:

Symbol: VIDEO_SAMSUNG_S5P_TV[=n]
Type  : boolean
Prompt: Samsung TV driver for S5P platform
Defined at drivers/media/platform/s5p-tv/Kconfig:9
Depends on: MEDIA_SUPPORT [=m] && V4L_PLATFORM_DRIVERS [=y] && PLAT_S5P && PM_RUNTIME[=y]
Location: -> Device
        Drivers -> Multimedia support (MEDIA_SUPPORT [=m])
                (1)     -> V4L platform devices (V4L_PLATFORM_DRIVERS [=y])

This is what I've found here:
http://lwn.net/Articles/449661/

Quote:

HDMI. The auxiliary driver used to control HDMI interface. It exports its
subdev in its private data for use by other drivers. The following callbacks are
implemented:
(...)
- g_mbus_format: returns information on data format expected by on HDMI input
The driver supports an interrupt. It is used to detect plug/unplug events in
kernel debugs. The API for detection of such an events in V4L2 API is to be
defined.

Anyone can help me with compiling this module?
Thanks.

Robert

Code:

uname -a
Linux smithy 3.9.7 #1 SMP Sat Jun 22 22:04:11 CEST 2013 x86_64 GNU/Linux (now it's the newest stable one)
Linux smithy 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux (I used to check on this one as well)

Code:

lsb_release -a
Distributor ID: Debian
Description:    Debian GNU/Linux testing (jessie)
Release:        testing
Codename:       jessie

Code:

lshw -C display
  *-display
       description: VGA compatible controller
       product: 2nd Generation Core Processor Family Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:52 memory:fb800000-fbbfffff memory:e0000000-efffffff ioport:ff00(size=64)

Code:

lspci -nnk | grep -iA2 vga
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
        Kernel driver in use: i915

Code:

dmidecode -t 1
# dmidecode 2.12
SMBIOS 2.4 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: Gigabyte Technology Co., Ltd.
        Product Name: H67MA-UD2H-B3
        Version:
        Serial Number:
        UUID: 00000000-0000-0000-0000-1C6F65D503D0
        Wake-up Type: Power Switch
        SKU Number:
        Family:

Code:

cat /var/log/Xorg.0.log | grep -e WW -e EE | grep -v '(II)'
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   387.576] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   387.576] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   387.576] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   387.576] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   387.576] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   387.860] (WW) intel(0): No outputs definitely connected, trying again...
[   387.860] (WW) intel(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[   387.902] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.

Code:

cat /etc/default/grub | grep -v ^#
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
GRUB_GFXMODE=1600x1200
GRUB_DISABLE_RECOVERY="true"

business_kid · 06-24-2013, 03:34 PM

That website doesn't seem to have been updated recently. Are you sure that thing isn't in recent kernels?
I think you will find that bios & graphics drivers do the thinking for you, switching things on & off. It takes a reboot here to wake up hdmi. I would look at the hdmi spec, to see if you can fiddle the cable to make it look like something's there, and keep the hdmi on. You can do that with vga & the power supply.

ruppertus · 06-24-2013, 05:31 PM

Quote:

Originally Posted by business_kid

That website doesn't seem to have been updated recently. Are you sure that thing isn't in recent kernels?
I think you will find that bios & graphics drivers do the thinking for you, switching things on & off. It takes a reboot here to wake up hdmi. I would look at the hdmi spec, to see if you can fiddle the cable to make it look like something's there, and keep the hdmi on. You can do that with vga & the power supply.

I've consulted my contact in Samsung and found out that the mentioned above module was used for HDMI out in older phones and tablets,
so that's another dead end.

I forgot to add that I was able to connect my TV and multimedia server about a 1-1.5 year ago and they were see each other.
I used to have Debian Wheezy (at that time Debian testing disto). Though, I'm sure that this hardware is able to detect my monitor connected by HDMI cable.

More over, I've connected the same monitor and HDMI cable with different pair of devices and operating system:
- Laptop1 (Core i5 + Nvidia1 card) + Display Port adapter + Arch Linux
- Laptop2 (Core i5 + Nvidia2 card) + Ubuntu12.10/Windows7

When I connect Monitor to server using D-SUB (VGA) port, then everything works fine (including booting process).
I tried to connect the cable during the booting time, after connecting D-SUB, together, etc.
Then do that again with different order and reboot gdm display manager - without any sucess.
There was only one exception - after booting with D-SUB, activating VNC, disconnecting D-SUB, connecting HDMI
I've noticed that xrander shows some extra model lines even though it didn't report any device connected to VGA/HDMI/DP port.

The distro blocks me here a little bit. I prefer Debian for professional server solutions but except sid (unstable) release it offers very old packages. I have software raid, dm-crypt, postfix, jabber, virtual domains apache, etc. configured on this server (mostly for personal purpose) and want to leave them stable and easy to manage as they are now. Maybe I need to consider moving e.g. to Arch Linux (I use that distro on my notebook and I'm rather satisfied) and virtualize stable, isolate environment with my Debian stable.

What do you suggest I may do without migrating to another distro?
I've noticed that intel has just release a new 2013Q1 Intel Graphics Stack Release
https://01.org/linuxgraphics/downloads, based on:
Kernel - 3.8.2, Mesa - 9.1, xf86-video-intel - 2.21.3, Libdrm - 2.4.42, Libva - 1.1.1, vaapi intel-driver - 1.0.20
Cairo - 1.12.14, Xserver - 1.13.2.902

that's far, far away what debian testing offers at the moment but on the other hand my HDMI monitor used to work on Debian wheezy (currently stable).

business_kid · 06-25-2013, 03:53 AM

My experience was with oss radeon stuff on a HP.
I could swap from screen to external early on in a boot. If I did, when the kernel loaded the radeon module, both remained on at console level. If not, I couldn't raise an external monitor until I started X. Then I might have it in X, but not outside.

I have a Samsung laptop now, and hdmi(from HD4000) is possible somehow. I still haven't figured it; Fn + something but there does seem to be a time delay. I've used it 3 or 4 times, that's all.

EDIT: Just a thought. Can you get a video switcher (one hdmi to either of 2 monitors), with enough brains in there to keep the software happy?

ruppertus · 06-25-2013, 04:43 PM

Quote:

Originally Posted by business_kid

My experience was with oss radeon stuff on a HP.
I could swap from screen to external early on in a boot. If I did, when the kernel loaded the radeon module, both remained on at console level. If not, I couldn't raise an external monitor until I started X. Then I might have it in X, but not outside.

I have a Samsung laptop now, and hdmi(from HD4000) is possible somehow. I still haven't figured it; Fn + something but there does seem to be a time delay. I've used it 3 or 4 times, that's all.

EDIT: Just a thought. Can you get a video switcher (one hdmi to either of 2 monitors), with enough brains in there to keep the software happy?

Hi, the problem is I have only one TV device (with HDMI and D-SUB interfaces) and only one long HDMI cable.
Just for testing purpose I may switch these cables but normally that's not the final solution.
But anyway I'm not able to run screen with my VGA cable and then switch to HDMI one. That doesn't work.

business_kid · 06-26-2013, 03:48 AM

Quote:

Originally Posted by ruppertus

Hi, the problem is I have only one TV device (with HDMI and D-SUB interfaces) and only one long HDMI cable.
Just for testing purpose I may switch these cables but normally that's not the final solution.
But anyway I'm not able to run screen with my VGA cable and then switch to HDMI one. That doesn't work.

The thread title on this is "Detecting HDMI plug/unplug". Don't switch cables, and you won't have to detect it. Software doesn't seem to do it. And search ebay for hdmi switchers with enough intelligence to fool the hdmi drivers.