Comment 1 for bug 257711

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

For starters, it's not using the intel driver, but vesa. Can you try a livecd to see it's the upgrade that resulted in breaking it, rather than then new driver.