Ubuntu-3.4.0-202.7
** Changed in: linux-ti-omap4 (Ubuntu Quantal)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
omapdss only works on some
just because nobody mentioned it yet, switching an installed system that
exposes this issue to a 12.04 omap4 kernel makes everything work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
if you want to collect more information, use the ubuntu-server
preinstalled image which does the whole install on serial console.
after you are done with the installation edit the omap bootscript in
/usr/share/flash-kernel/bootscript/bootscr.omap and drop quiet and
splash from the bootarg line,
oops, sorry, the changes above should have been: omapdss.debug=1
drm.debug=7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
omapdss only works on some monitors in quantal
To manage
Worked fine for me with a PandaBoard A2 connected over HDMI to a Samsung
TV (LN46C610), got 1920x1080 without any tweaks required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
so it is likely that along with the framebuffer driver bug we also have
a plymouth bug that keeps the screen black during boot instead of
showing a splash screen (bug 1018907)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http://people.canonical.com/~ppisati/linux-
image-3.4.0-202-omap4_3.4.0-202.7_armhf.deb
this kernel fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
omapdss only works on
** Changed in: linux-ti-omap4 (Ubuntu Quantal)
Milestone: quantal-alpha-2 = quantal-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
omapdss only works on some monitors in
** Summary changed:
- omapdss fails to properly detect some monitors in quantal
+ omapdss only works on some monitors in quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
Workaround in #4 doesn't work for me on 4 different monitors of
different makes and models, this occurs on both a Panda ES and Panda A1
board with the same monitors.
Monitor Make and models:
Hannspree HF257 via HDMI HDMI-DVI cable
ASUS VW224T via HDMI-DVI cable
ViewSonic VX2450 via HDMI-DVI
I have a panda A1 I am unable to get to display on a monitor here with
any of the work arounds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
omapdss only works on some monitors in
My monitor is an AOC e2243Fw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
omapdss only works on some monitors in quantal
To manage notifications about this bug go to:
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010009
Title:
omapdss only works on some monitors in quantal
To manage notifications about this bug go to:
Panda ES here, booted today's quantal armhf desktop build, and the
backlight on my monitor fired up and stayed up (did not go into sleep
mode) but nothing displayed on the monitor at all.
I'm using a 23 inch Samsung PX2370.
I tried the stock image, and then rebuilt my boot.scr per comment #4
Just to clarify Comment #8, using the workarounds (rebuilding boot.scr)
with either:
* video=HDMI-A-1:1920x1080@60
* video=HDMI-A-1:1280x800@60
... yield no difference in behaviour, identical to the behaviour on
today's daily build.
--
You received this bug notification because you are a
15 matches
Mail list logo