Comment 26 for bug 506717

Revision history for this message
Steve Langasek (vorlon) wrote :

As already noticed in the duplicate bug report, booting with 'vga=<mode>' also works around this issue by forcing the use of the VESA fb instead of the VGA16 fb. That's not suitable as a solution for this by default on users systems, however.