Search results
Create the page "Vesa" on this wiki! See also the search results found.
- This chip will work with either the 'vesa' or 'savagefb' driver as part of any recent 2.4 or 2.6 kernel.6 KB (1,009 words) - 15:00, 22 January 2021
- Use Vesa driver instead of the proprietary NVidia driver.16 KB (2,636 words) - 09:33, 23 September 2020
- This chip will work with either the 'vesa' or 'intelfb' driver as part of any recent 2.4 or 2.6 kernel.3 KB (271 words) - 14:56, 22 January 2021
- ==== <tt>vesa</tt> driver ==== Using the [[vesa]] driver built into X.org, mode switching modes. However, this loses accele6 KB (901 words) - 14:52, 22 January 2021
- ...'trident' driver as part of the X.Org distribution. If that fails try the 'vesa' driver instead.902 bytes (119 words) - 15:02, 22 January 2021
- This chip is supported by the 'vesa' driver as part of the X.Org distribution. The 'trident' driver doesn't wor814 bytes (107 words) - 15:02, 22 January 2021
- ...ted, however, by the [http://ftp.x.org/pub/X11R6.9.0/doc/html/vesa.4.html 'vesa'] driver; at a full 800x600@8bpp.1 KB (151 words) - 15:02, 22 January 2021
- ...lt Ubuntu uses the ''ati/radeon'' graphics driver. You have to switch to ''vesa'' and set up a working display configuration. Either you use the new ''Scre ...Screen and Graphics'' Dialog choose ''Graphics Card'' Tab and select the ''vesa'' driver. On ''Screen'' Tab select the standard ''LCD Panel 1024x768''. Aft7 KB (971 words) - 14:10, 12 November 2007
- | Laptop Screen ||class="diff-addedline"| Yes || both vesa driver, and i810 (with Intel 915 support) ...="diff-addedline"| Yes || with i810 driver. (screen/crt are exclusive with vesa)19 KB (2,799 words) - 23:51, 27 April 2006
- * VESA 2.0 compatible graphics chipset * In the Graphics section select VESA VGA graphics support but DO NOT select nVidia Framebuffer Support as it int19 KB (3,073 words) - 15:51, 1 March 2008
- *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
