The r128 driver silently throws away the dotclock and timing numbers for all modes, using numbers from the BIOS instead. This would be fine, except the dotclock is locked to the value for the 1400x1050 mode, which means that lower res modes, even when perfectly valid and displayable ( and necessary for getting the S/Video output to a TV going ) are rejected.
I've managed to patch Xfree86 4.1.0 to allow the user to specify the dotclock as well as the X and Y res (it works for me): I've also adapted the patch for 4.3.0 ( but haven't tested that one yet - It does compile cleanly though ). In addition, the patch(es) report the available modelines, with the dotclocks adjusted for a 60Hz refresh (seems to be what laptops like) in the Xfree86 log. I've submitted the bug+patches to [EMAIL PROTECTED] (seq# A.1685) as well (just before I read the announcement about bugs.xfree86.org). The radeon driver looks like it might have the same problem. ( It all depends on the BIOS reporting a sane dotclock, which the A20p doesn't. ) [patches to follow] ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
