Search results
Create the page "Vesa" on this wiki! See also the search results found.
- *Change Driver "i810" to Driver "vesa"17 KB (2,771 words) - 12:51, 19 August 2010
- ...around: Don't use the ATI driver if you want to use this feature - use the VESA driver instead.2 KB (233 words) - 14:52, 22 January 2021
- ...nt to use this feature (i.e. during presentations), you should use the <tt>vesa</tt> server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fgl30 KB (4,482 words) - 03:47, 17 November 2009
- The VESA driver in Xorg 6.8.2 works. When configured in Fedora Core 4, the hardware boot: linux vesa3 KB (392 words) - 15:10, 22 January 2021
- ====With the VESA driver==== I have fixed the problem on my T42 by switching to the generic VESA driver in xorg.conf, and rebooting, as mentioned on the xorg bug page above9 KB (1,494 words) - 05:05, 31 October 2009
- === VESA (console) resolution === Largest video resolution, supported by VESA for T60 is 1280x1024. You can set that for console in grub or lilo by addin11 KB (1,734 words) - 14:55, 22 January 2021
- ...s and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP11 KB (1,746 words) - 14:49, 22 January 2021
- == Linux X.org vesa driver == The vesa driver works out of the box. If you can't make it to show higher resolutio4 KB (662 words) - 14:52, 22 January 2021
- * X wouldn't start. I changed the driver in xorg.conf from "ati" to "vesa".743 bytes (106 words) - 08:22, 1 March 2008
- ...error of "No Screen Found." Workaround is configuring X to use the generic VESA driver. This does not offer, however, any acceleration and thus - I'm told7 KB (1,138 words) - 11:14, 13 May 2007
- ...that if a monitor is connected to the VGA connector the highest available VESA resolution will not be selected unless it has a refresh rate of 75Hz or mor25 KB (3,612 words) - 08:00, 2 March 2008
- Be sure to use the i810 video driver. The default VESA driver will work fine, but you won't be able to use 3D programs like Google3 KB (541 words) - 23:27, 11 December 2006
- ...chipset and the 15" display as well at 1400x1050, but it uses the generic VESA drivers.4 KB (603 words) - 16:17, 9 June 2007
- ...(shown below, it may have more items) Look for "savage" and change it to "vesa". This is one of several workarounds, but seems successful for one contribu 3. Find your video card, and change driver "savage" to "vesa".13 KB (2,132 words) - 04:57, 2 July 2008
- : Fedora does not ship the proprietary ATi driver, as a reult the VESA driver is used. Installation of the ATi fgrlx driver is described later in #Driver "vesa"15 KB (2,296 words) - 15:00, 27 July 2008
- * VESA Graphics (crappy, yet functional out of box)8 KB (1,267 words) - 06:24, 28 September 2007
- #Driver "vesa" <---- COMMENT OUT THIS LINE ...g fglrx to start up (/var/log/Xorg.0.log showed the driver falling back to VESA and fgl_glxgears would crash). Without that ChipID line my chip was identi17 KB (2,546 words) - 09:40, 1 March 2008
- ...810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.12 KB (1,816 words) - 15:25, 2 March 2010
- ...(linux-2.6.21-1-686)||1400x1050 14" min-bright, iwpriv wlan0 set_power 7, VESA driver|| 12,7W ...ia,ethernet,usb,firewire,sd,snd) and stopped (no X11,only cron/syslog), no vesa-fb, min brightness, 5 min idle, measured with powertop 1.7 (ACPI)||7.7W11 KB (1,442 words) - 14:42, 29 March 2011
- # VESA framebuffer console @ 800x600x25611 KB (1,728 words) - 19:14, 26 June 2007
