Activity log for bug #496773

Date Who What changed Old value New value Message
2009-12-14 23:53:31 Robert Hooker bug added bug
2009-12-14 23:54:20 Robert Hooker xorg (Ubuntu): assignee Bryce Harrington (bryceharrington)
2009-12-15 04:18:31 Bryce Harrington xorg (Ubuntu): importance Undecided Wishlist
2009-12-15 04:18:36 Bryce Harrington xorg (Ubuntu): status New Triaged
2009-12-25 23:24:39 Robert Hooker description Binary package hint: xorg xserver-xorg-video-vesa doesn't work when KMS is in use on my machines, but changing /etc/X11/xorg.conf.failsafe to use fbdev lets failsafe X work. pm-utils has a method of determining of KMS is in use that could possibly be used in the /etc/gdm/failsafeXServer script to determine which driver should be picked for fallback_driver in there instead of just using vesa. grep -q -E '(nouveau|drm)fb' /proc/fb a nouveau KMS fb is called nouveaufb, a radeon KMS fb is called radeondrmfb and an intel KMS fb is called inteldrmfb. those are the only use cases of KMS currently. Binary package hint: xorg xserver-xorg-video-vesa doesn't work when KMS is in use on my machines, but changing /etc/X11/xorg.conf.failsafe to use fbdev lets failsafe X work. pm-utils has a method of determining of KMS is in use that could possibly be used in the /etc/gdm/failsafeXServer script to determine which driver should be picked for fallback_driver in there instead of just using vesa. 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.
2010-02-23 06:50:08 Launchpad Janitor xorg (Ubuntu): status Triaged Fix Released
2011-02-24 18:08:43 Launchpad Janitor branch linked lp:ubuntu/xorg