This bug was fixed in the package xf86-video-omapfb - 0.1.1-3ubuntu1
---
xf86-video-omapfb (0.1.1-3ubuntu1) lucid; urgency=low
* fix hardcoded default framebuffer device to point to something that
actually exists (LP: #567260) thanks to Graeme Gregory
-- Oliver GrawertThu,
** Tags added: patch
--
xserver-xorg-video-omap* fail due to no /dev/fb
https://bugs.launchpad.net/bugs/567260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
shashi: thanks for that snippet, though note that we dont use xorg.conf
by default anymore but indeed it can be used as a workaround ...
the requirement for a packaged driver though is to work without the file
and use the autodetection mechanisms provided by xorg.
--
xserver-xorg-video-omap* fa
The other way to solve this problem would be add a section in
/etc/X11/xorg.conf. Below is an example:
==
Section "Monitor"
Identifier "Builtin Default Monitor"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device"
Driv
I tried the patch on OMAP4 board. I rebuilt the package. it works, X
starts fine and the omapfb driver is selected.
$ grep -i omapfb /var/log/Xorg.0.log
(II) LoadModule: "omapfb"
(II) Loading /usr/lib/xorg/modules/drivers/omapfb_drv.so
(II) Module omapfb: vendor="X.Org Foundation"
(==) Matched om
Attached patch is what I have been using on my omap zoom2 to "solve"
this bug. In long term proper fb searching is probably needed. But in
short term /dev/fb0 will always be the correct fb.
** Patch added: "fb-search.patch"
http://launchpadlibrarian.net/44951669/fb-search.patch
--
xserver-xo
Olivier, I agree with this quick fix. I can try that on my OMAP4 board
whenever you make a fix available. we can think about the right method
for 10.10
--
xserver-xorg-video-omap* fail due to no /dev/fb
https://bugs.launchpad.net/bugs/567260
You received this bug notification because you are a me
given that we only support one kind of board with the current kernel and
all of these boards default to having /dev/fb0 as their default video
device i think the safe quick-fix would be to just change the above
DEFAULT_DEVICE definition (fb1 is used by the xv code in that driver in
the same way).
from src/omapfb-driver.c in the xf86-video-omapfb-0.1.1 package:
/* FIXME: We don't really want to do it like this... */
#define DEFAULT_DEVICE "/dev/fb"
** Changed in: xf86-video-omapfb (Ubuntu)
Importance: Undecided => High
** Changed in: xf86-video-omapfb (Ubuntu)
Status: New => Co
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44899129/Dependencies.txt
--
xserver-xorg-video-omap* fail due to no /dev/fb
https://bugs.launchpad.net/bugs/567260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
10 matches
Mail list logo
