Bug 191419 - fbdev(4) driver broken
fbdev(4) driver broken
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-fbdev (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adam Jackson
Depends On:
Blocks: FC6Blocker OLPCBlocker
  Show dependency treegraph
Reported: 2006-05-11 15:29 EDT by David Zeuthen
Modified: 2013-03-05 22:45 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-06-22 20:17:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Zeuthen 2006-05-11 15:29:42 EDT
Description of problem:

(EE) FBDEV(0): FBIOBLANK: Invalid Argument

See also


Reproduced on radeonfb, the kernel fbdev driver used on qemu, vesa fbdev on i830
(according to krh) and also imacfb (out of tree experimental driver) on the
Macbook Pro. (the latter works in Ubuntu btw and inspecting their xorg packages
shows little divergence from ours so I suspect it may be a kernel issue?)

We need this to work for OLPC for booting OS images on regular laptops. Please
advise. Thanks.

Version-Release number of selected component (if applicable):


How reproducible:

Comment 1 David Zeuthen 2006-05-15 11:16:28 EDT
Adding to FC6Blocker
Comment 2 Adam Jackson 2006-05-15 13:40:38 EDT
that error message isn't actually fatal, just irritating.  i think krh was
looking into the fix for this, but you should be able to say Option "ShadowFB"
"off" as a workaround for now.
Comment 3 Kevin E. Martin 2006-05-18 17:15:45 EDT
There were two issues for this one.

The first was the crasher, which was fixed by krh's patch in:

The second was caused by recent miext/shadow changes, which I've just fixed
upstream (it also caused the VESA driver to fail).

Both are now checked in upstream and should be included in the next driver spin.
Comment 4 Adam Jackson 2006-06-22 20:17:49 EDT
fixed in 0.3.0-1

Note You need to log in before you can comment on or make changes to this bug.