Comment 5 for bug 539730

Revision history for this message
Bryce Harrington (bryce) wrote :

With modeset=0 it looks like it's falling back to -vesa, which explains the wrong resolution (since it is not doing any modesetting in that case, just using VESA defaults.)