Thanks for your information manu. I have a very similar xorg.conf that uses the trident driver like the one posted by manu, and X more-or-less works with some glitches mentioned in http://ubuntuforums.org/showthread.php?t=301082 I may try the vga=791 option to see if that fixes the glitches.
However, this is not the point of this bug, which is specifically about the *vesa* driver. There are two reasons I think vesa is important: * As I understand it, it's the de facto standard driver. Any card should work with the vesa driver * AFAIK the trident driver doesn't work with data projectors. I have to admit I haven't tested this with my machine, but a friend's machine with Fedora core 6 and the same version of the trident driver didn't work with a data projector. The vesa driver in dapper used to work, and my friend's FC6 vesa driver worked (cue embarassment on part of this Ubuntu fan). @manu: Does your config work with data projectors? @anyone else with this problem: Did you install edgy freshly or did you upgrade from dapper? I've got the impression that fresh installs of edgy were more reliable, but I haven't got round to trying a fresh install myself. -- Edgy X vesa driver blank screen on Toshiba Portege R100 https://launchpad.net/bugs/68814 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
