Search results
Create the page "Vesa" on this wiki! See also the search results found.
- ...aticonfig --initial segfaults destroying xorg.conf file when run in X with Vesa driver.", search for "737-28261" on the ATI website.13 KB (1,798 words) - 03:17, 15 April 2013
- This chip will work with either the 'vesa' or 'intelfb' driver.1 KB (143 words) - 14:54, 22 January 2021
- | {{bootparm|video|vesa:ywrap,mtrr}} || enables mtrr and .... | {{bootparm|video|radeonfb:vesa:1400x1050-32@60}} || for using accelerated radeonfb framebuffer3 KB (518 words) - 18:09, 12 March 2017
- ...r doesn't show this problem either, see [[Talk:Problem with garbled screen#VESA Driver]] ...nd it allows for the screen to run in 1600x1200, which I could not get the VESA driver to do.9 KB (1,597 words) - 17:40, 16 November 2016
- VIDEO_CARDS="vesa vga i810"3 KB (472 words) - 11:18, 24 July 2011
- The easiest solution is to switch to the "vesa" driver in xorg.conf.856 bytes (123 words) - 05:46, 23 May 2007
- Works with VESA & mplayer3 KB (395 words) - 14:57, 22 January 2021
- ...tro sources, which are pretty much 2.6.x kernels with patches for Reiser4, vesa-fbtng, fbsplash, Software Suspend 2, and a couple of other things. You can <*> VESA VGA graphics support34 KB (5,558 words) - 16:49, 20 October 2006
- This chip will work with either the 'vesa' or 'intelfb' driver as part of any recent 2.4 or 2.6 kernel.12 KB (1,433 words) - 14:55, 22 January 2021
- This chip will work with either the 'vesa' or 'savagefb' driver as part of any recent 2.4 or 2.6 kernel.2 KB (354 words) - 15:01, 22 January 2021
- 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
