Color ghosting on BeagleBoard xM rev C
Darren Hart suggested I send this to the list...
Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom doesn't display these problems, so the setup should be fine.
I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the newer DSS2 omapfb.mode variant).
Thanks,
Jeff
Jason, Koen,
Does anything spring to mind as an obvious fix for this? Perhaps some kernel parameter initialization string for the graphics hardware?
--
Darren
Quoted 20 lines · Jeff Mitchell
Darren Hart suggested I send this to the list...
Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom doesn't display these problems, so the setup should be fine.
I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the newer DSS2 omapfb.mode variant).
Thanks,
Jeff_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Op 15 jul 2011, om 20:33 heeft Darren Hart het volgende geschreven:
Quoted 4 lines
Jason, Koen,
Does anything spring to mind as an obvious fix for this? Perhaps some kernel parameter initialization string for the graphics hardware?
I've never seen it in angstrom, so you'd have to see what meta-yocto is doing different. In other news, for beagleboard please use the meta-ti layer for that, it's the offcial upstream for beagle and is known to work.
Quoted 30 lines
--
DarrenQuoted 20 lines · Jeff Mitchell
Darren Hart suggested I send this to the list...
Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom doesn't display these problems, so the setup should be fine.
I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the newer DSS2 omapfb.mode variant).
Thanks,
Jeff_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoSignature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 5 lines · Koen Kooi
Op 15 jul 2011, om 20:33 heeft Darren Hart het volgende geschreven:
Quoted 2 lines
Jason, Koen,
Quoted 8 lines
Quoted 3 lines
Does anything spring to mind as an obvious fix for this? Perhaps some kernel parameter initialization string for the graphics hardware?
I've never seen it in angstrom, so you'd have to see what meta-yocto is doing different. In other news, for beagleboard please use the meta-ti layer for that, it's the offcial upstream for beagle and is known to work.
I'm not using meta-ti because I'm working with Darren to test out support for the rev C board in meta-yocto. We just don't know what difference is causing this :-)
--Jeff
Quoted 7 lines · Jeff Mitchell
Darren Hart suggested I send this to the list...
Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom doesn't display these problems, so the setup should be fine.
I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the newer DSS2 omapfb.mode variant).
Did you ever find out what is causing this?
When you say that it works on one system (Poky?) vs another (Angstrom?) are they both running the same version of U-Boot? I'm seeing this same behaviour on one of my boards, but only when I run U-Boot from 2011.06
BTW - why did you send your original query to the Poky list?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 10 lines · Gary Thomas
Quoted 7 lines · Jeff Mitchell
Darren Hart suggested I send this to the list...
Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom doesn't display these problems, so the setup should be fine.
I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the newer DSS2 omapfb.mode variant).
Did you ever find out what is causing this?
No, but I'll be testing out a new build soon -- haven't been able to for a bit.
Quoted 3 lines
When you say that it works on one system (Poky?) vs another (Angstrom?) are they both running the same version of U-Boot? I'm seeing this same behaviour on one of my boards, but only when I run U-Boot from 2011.06
Yes -- Yocto/Poky/Sato vs. Angstrom. I doubt they're running the same version of U-Boot, but I don't know the version numbers offhand.
Quoted 1 line
BTW - why did you send your original query to the Poky list?
Because Darren suggested that I do so, to get various eyes on it :-)
Thanks,
jeff
Quoted 12 lines · Jeff Mitchell
Quoted 10 lines · Gary Thomas
Quoted 7 lines · Jeff Mitchell
Darren Hart suggested I send this to the list...
Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom doesn't display these problems, so the setup should be fine.
I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the newer DSS2 omapfb.mode variant).
Did you ever find out what is causing this?
Quoted 7 lines
No, but I'll be testing out a new build soon -- haven't been able to for a bit.
Quoted 3 lines
When you say that it works on one system (Poky?) vs another (Angstrom?) are they both running the same version of U-Boot? I'm seeing this same behaviour on one of my boards, but only when I run U-Boot from 2011.06
Yes -- Yocto/Poky/Sato vs. Angstrom. I doubt they're running the same version of U-Boot, but I don't know the version numbers offhand.
Check the display setup. In my case, my old U-Boot (which works great) was using dvimode=1024x768-24@60 and the new U-Boot is using dvimode=1024x768MR-16@60 When I switch back to the old setting, even with the new U-Boot, my display runs great again. n.b. this may be kernel revision sensitive as well.
Quoted 4 lines
Quoted 2 lines
BTW - why did you send your original query to the Poky list?
Because Darren suggested that I do so, to get various eyes on it :-)
Sounds reasonable - I only asked because your original email didn't really spell out why it went to the Poky list.
Thanks & good luck
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------