I tried image: http://cdimage.ubuntu.com/daily-live/20130409/raring-
desktop-armhf+omap4.img and the bug is gone, everything's fine now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/116198
This bug was fixed in the package xorg-server - 2:1.13.3-0ubuntu5
---
xorg-server (2:1.13.3-0ubuntu5) raring; urgency=low
[ Bryce Harrington ]
* Add no-nv.patch: Don't autoprobe -nv on linux.
* Refresh drm_device_keep_trying.patch (LP: #1161981)
- Set empty busid for usb de
** Changed in: linux-ti-omap4 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.
Some notes on the final patch (not attached here, but in ubuntu5 upload):
- tested on panda, confirmed to work
- tested on a normal (hybrid) laptop, previous versions had a bug which
triggered ssp due to an incorrect offset, confirmed to work with the incorrect
offset removed.
- tegra, was found
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1161981
Title:
Boot stalls after Ubuntu Raring desktop ARM (Panda board) install
To manage notifications about this bu
I tested it on my main system by stuffing the logic in a separate
function..
** Attachment added: "fixed to compile correctly"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/1161981/+attachment/3623538/+files/patch
--
You received this bug notification because you are a member
Does this patch fix things?
** Attachment added: "Probe platform devices correctly"
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/1161981/+attachment/3623525/+files/patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-s
I can confirm it works fine again after removing
drm_device_keep_trying.patch.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1161981
Title:
Boot stalls after Ubuntu Raring desktop ARM (P
Expected values at panda:
syspath: /sys/devices/platform/omapdrm/drm/card0
busid: platform:omapdrm:0
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1161981
Title:
Boot stalls after Ubunt
The problem here is that the BUSID support for platform devices got
broken after patch drm_device_keep_trying.patch was added to xorg-server
(bug 982889).
As the BUSID is empty when initializing the omap x11 driver, it fails
and move back to the old probing method, which allows more than one
drive
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has finished using the drm driver
--
You received this bug notification because you are a member of Ubuntu-X,
which
21 xnox, ogra@chromebook:~/xf86-video-omap-0.4.0$ grep 24 src/*
<ogra_> src/omap_driver.c: default_depth = 24; /* TODO: get from kernel
*/
Changing that to 32, recompiling, in-place replacing allows me to boot
and be presented with the "you are running in a low graphics mode" and
allows
12 matches
Mail list logo