Yep, that bug is fixed but not on hardy yet.
I'm not sure what to do with the real problem; why does it fall back to failsafe. When x-x-v-ati driver supports these chips it'll probably be "fixed" automatically, but vesa seems to have issues.
Yep, that bug is fixed but not on hardy yet.
I'm not sure what to do with the real problem; why does it fall back to failsafe. When x-x-v-ati driver supports these chips it'll probably be "fixed" automatically, but vesa seems to have issues.