I have a strange problem here.
First I am complete Linux noob, so bear with me.
Got BBB, updated to latest version ( cat /etc/dogtag reads "Cloud9 GNOME Image 2013.06.20 ).
Upon powerup there is Beagleboeo logo displayed. The board continues to boot, logo disappears. Board boots fine, I can ssh to it
However, no prompt is shown on the monitor.
I know that monitor is fine, because when I boot board to Ubuntu or Debian there is a prompt display on the same monitor, same cable, etc… Does it mean that the latest distribution disables monitor output?
Below is results of edid parse:
root@beaglebone:~# cd /sys/class/drm/card0/card0-HDMI-A-1/
root@beaglebone:/sys/class/drm/card0/card0-HDMI-A-1# parse-edid edid
parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.
You can try and see if any of the other settings may work. You are not likely to have very many, based on audio support, but you could try some of the other ones.
I tried getting my new Beaglebone Black working with a small 7 inch display purchased from Adafruit.
Because it didn’t work I went into debug mode for quite some time. Please see my Adafruit forum post: http://forums.adafruit.com/viewtopic.php?f=49&t=41690
In testing the BBB worked fine with a Sony Bravia KLD-46EX521 TV with the stock Angstrom image (kernel 3.2.13).
It’s pretty clear to me that the HDMI circuity is sound, we need more software support!
If the EDID information doesn’t read back from the device for whatever reason, or there’s some error/bug in the EDID exchange, there needs to be a way to set a static resolution on the BBB that doesn’t get bombed on by a failing part of the “EDID/DRM subsystem.”
Above you had mentioned you guys are working on making this route an option - possibly via the uEnv.txt file? Please update us on the progress of this.
I have no such update. I have no indication that any work is being done on this. There is a way with a serial port to change it, but there are limitations.
You can set the resolution via uENV.txt file and it works great, at boot up. The DRM driver it appears does not even know the uENV.txt file exists. The issue seems to be the DRM driver.
It cannot be forced for the uENV.txt file. If you read the WIKI you would see that it says that only works on boot up. That is what I said in my previous response as well.
Until the SW folks get this fixed, there isn’t anything I can do to force a resolution.