LXFB should be blacklisted in /etc/modprobe.d/blacklist-framebuffer
Bug #237186 reported by
jwishnie
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| module-init-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: module-init-tools
Release: 8.04
Module: module-init-tools 3.3-pre11-4ubuntu5
On Geode LX hardware, the kernel will attempt to use the 'lxfb' module to draw the framebuffer (used for Bootsplash).
This code interacts poorly with Bootsplash and causes the system to hang on reboot and halt.
'lxfb' should be blacklisted along with all the other framebuffer modules in /etc/modprobe.
Under 8.04, it is _not_ blacklisted here and should be
Revision history for this message
| Pythonator (john-schnittker) wrote | #1 |
| Changed in module-init-tools: | |
| status: | New → Confirmed |
Revision history for this message
| Pythonator (john-schnittker) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in module-init-tools: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Confirmed this bug -- on the Pepper Pad 3.
The lxfb module does *not* fail gracefully. Unless lxfb is supplied with the exact timings needed for the exact TFT Panel or CRT attached, lxfb will cause the screen to flicker and freak out. lxfb makes the Ubuntu distro unusable after the system is installed.
It needs to be understood that the lxfb framebuffer module is a special purpose module intended only for niche applications -- where a standard X server is not desirable. Ordinary users should use the standard geode X server, *not* lxfb. This bug -- lxfb being permitted to load by default -- makes Ubuntu unusable for many users.
This bug remains in Hardy Heron and persists in Intrepid Ibex.
lxfb should be blacklisted ASAP