On Tue, 2014-09-23 at 10:12 -0400, Felix Miata wrote: > Adam Jackson wrote on 2014-09-23 09:52 (GMT-0400): > > > On Tue, 2014-09-23 at 04:44 -0400, Felix Miata wrote: > > >> So, what exactly are people needing this driver supposed to do, particularly > >> those for whom X worked before last round of updates, install Mageia's or > >> openSUSE's driver (tried both in F22 with rpm. both failed deps, but with > >> nodeps switch for Mageia's 0.10.7-15, startx gives me KDE)? Switch distros? > >> If some other driver, why doesn't Xorg figure that out on its own? > > > The vesa driver should work as well as it ever does; > > Which is to say only on screens whose native modes are 4:3. Not entirely true. It's a function of your video BIOS, not of the vesa driver. The vesa driver can only set modes that are listed by the video BIOS, but it does know how to query the monitor for supported modes, and will attempt to set the monitor's native mode if it happens to be exposed by the BIOS. The X log you provided elsewhere in the thread seems to say you're not using the vesa X driver though: > [ 819.945] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16 > [ 819.945] (==) FBDEV(0): RGB weight 565 > [ 819.945] (==) FBDEV(0): Default visual is TrueColor > [ 819.945] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) > [ 819.945] (II) FBDEV(0): hardware: VESA VGA (video memory: 3072kB) That's the fbdev X driver, pointed at either vesafb or uvesafb kernel driver. Which I suppose will get you a high-res console, but isn't especially great for mode selection in X. (The fbdev interface has no way to query the kernel for supported resolutions, so X can't even know what to ask for.) If you stopped using vesafb you might have a better time of it. - ajax -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
