Failsafe X should pick fbdev instead of vesa if KMS is in use
Bug #496773 reported by
Robert Hooker
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| xorg (Ubuntu) |
Fix Released
|
Wishlist
|
Bryce Harrington | ||
Bug Description
Binary package hint: xorg
xserver-
grep -q -E '(nouveau|drm)fb' /proc/fb
a nouveau KMS fb is called nouveaufb, a radeon KMS fb is called radeondrmfb a vmware KMS fb is called svgadrmfb and an intel KMS fb is called inteldrmfb. those are the only use cases of KMS currently.
Related branches
| Changed in xorg (Ubuntu): | |
| assignee: | nobody → Bryce Harrington (bryceharrington) |
| Changed in xorg (Ubuntu): | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| description: | updated |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in xorg (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This bug was fixed in the package xorg - 1:7.5+1ubuntu7
---------------
xorg (1:7.5+1ubuntu7) lucid; urgency=low
* debian/
+ Actually produce xorg.conf.failsafe with the detected driver.
Important for failures while running in KMS mode.
(LP: #496773)
+ Force overwrite of existing xorg.conf.failsafe. Since above
change produces different xorg.conf.
what driver was selected, we must force it to regen each time.
(LP: #480747)
-- Bryce Harrington <email address hidden> Mon, 22 Feb 2010 22:38:22 -0800