Hi all,
I just flashed the latest Angstrom Distribution (BeagleBone Black)
2013-06-20 on my Beaglebone Black and I've some troubles with the
HDMI, My monitor is black and shows No Signal. From dmesg output I see
[ 0.412706] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN
conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.422326] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.429099] bone-capemgr bone_capemgr.8: loader: failed to load
slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
But seems the HDMI plugin is loaded
# cat /sys/devices/bone_capemgr.8/slots
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
The parse-edid utility, doesn't help
# parse-edid /sys/devices/ocp.2/4830e000.fb/drm/card0/card0-HDMI-A-1/edid
parse-edid: parse-edid version 2.0.0
parse-edid: IO error reading EDID
Any clue ?
Thanks in advance,
Enric
The HDMIN module is the "no-audio" version, which capemgr tries to
load after the full HDMI version (in case you have audio assigned
elsewhere, like an audio cape). It is expected it will fail to load
if the HDMI module is already loaded.
Do you have a keyboard/mouse plugged into the BeagleBone? I was
perplexed by a completely black screen and dead HDMI output until I
realized as soon as the default GUI comes up, it *IMMEDIATELY* shuts
down HDMI if you don't have a KB/Mouse connected.
If you have a serial or ssh console session and your problem is screen
blanking, you can get the HDMI output to come alive using:
echo 0 > /sys/class/graphics/fb0/blank
I have some details at the bottom of my blog post on forcing the
boot-time HDMI resolution:
http://bb-lcnc.blogspot.com/2013/06/force-beaglebone-black-hdmi-resolution.html
GERALD:
IHMO, the KB/Mouse issue should be in HUGE BLINKING LETTERS as a FAQ
somewhere on the wiki. It's really quite confusing to have the
display shut down instantly once the system boots if the first thing
you did is connect a monitor and apply power.
...or maybe disable screen blanking in the default image?
- --
Charles Steinkuehler
charles@steinkuehler.net
Either way I will add this to the top of the HDMI FAQ
Tommy
<heh> I'll have to check. I power up my BBBs all the time without a
keyboard, but I'm not sure I've _ever_ powered one up not connected to
Ethernet! 
It will take a bit as I have to revert back to the shipped image
first. I've disabled the monitor power management on all the systems
I have here.
- --
Charles Steinkuehler
charles@steinkuehler.net
OK, I verified with the restored 6/20 image I *DO* get a working HDMI
image if I have no Ethernet cable connected regardless of whether or
not I have a keyboard or mouse attached.
If I have Ethernet connected, I have to have a keyboard or mouse
plugged into USB or the HDMI output shuts down when gdm launches.
- --
Charles Steinkuehler
charles@steinkuehler.net
Hi all,
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
From my experience, this only happens when you have the Ethernet
plugged in. Is this happening without Ethernet as well? Either
way I will add this to the top of the HDMI FAQ
<heh> I'll have to check. I power up my BBBs all the time without
a keyboard, but I'm not sure I've _ever_ powered one up not
connected to Ethernet! 
It will take a bit as I have to revert back to the shipped image
first. I've disabled the monitor power management on all the
systems I have here.
OK, I verified with the restored 6/20 image I *DO* get a working HDMI
image if I have no Ethernet cable connected regardless of whether or
not I have a keyboard or mouse attached.
Same issue, in my initial tests if I have no ethernet cable connected
seems the HDMI works, if I've the ethernet cable plugged the HDMI
doesn't work.
If I have Ethernet connected, I have to have a keyboard or mouse
plugged into USB or the HDMI output shuts down when gdm launches.
But after more test, I found that if the ethernet cable is plugged or
not doesn't matter. Playing with the HDMI cable sometimes works and
sometimes not. Then, seems the problem is the HDMI cable, but I'm
pretty sure that the HDMI cable works as I tested with other boards. I
don't have another HDMI cable at this moment but I'll try with
different cables.
I think there is something really strange with the HDMI, we should
dive into more ...
Cheers,
Enric
For me, the "physical" HDMI always works. With an Ethernet cable
plugged in, I get a boot logo while the Linux kernel is booting, but
then the HDMI output shuts down as soon as the display manager launches.
"Kicking" the display blanking via:
echo 0 > /sys/class/graphics/fb0/blank
...always brings up the HDMI display. So with the latest image I have
not had any indication on my board that HDMI doesn't work, it's just
not always turned on.
- --
Charles Steinkuehler
charles@steinkuehler.net
When ethernet is connected connman will set the correct time using NTP. Since there's no backup battery for the RTC the time on boot will be 2000-01-01, so the screen will blank after ntp because it has been idle for 13.5 years.
Hi,
Hi all,
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
From my experience, this only happens when you have the Ethernet
plugged in. Is this happening without Ethernet as well? Either
way I will add this to the top of the HDMI FAQ
<heh> I'll have to check. I power up my BBBs all the time without
a keyboard, but I'm not sure I've _ever_ powered one up not
connected to Ethernet!
It will take a bit as I have to revert back to the shipped image
first. I've disabled the monitor power management on all the
systems I have here.
OK, I verified with the restored 6/20 image I *DO* get a working HDMI
image if I have no Ethernet cable connected regardless of whether or
not I have a keyboard or mouse attached.
Same issue, in my initial tests if I have no ethernet cable connected
seems the HDMI works, if I've the ethernet cable plugged the HDMI
doesn't work.
When ethernet is connected connman will set the correct time using NTP. Since there's no backup battery for the RTC the time on boot will be 2000-01-01, so the screen will blank after ntp because it has been idle for 13.5 years.
Thanks all for your support, from my part, finally I found that the
problem was the HDMI connector of beaglebone, Re-soldering the
connector solved the problem.