Search results
Create the page "Vesa" on this wiki! See also the search results found.
- With thinkpad_acpi 0.16 (!) patches applied to 2.6.22 kernel, and with VESA driver only, it works perfectly so far for us. Not a real solution, but if using the vesa driver, brightness control works. ''--Daniel06'' 11:58, 4 July 200729 KB (4,654 words) - 19:04, 4 March 2008
- If X doesn't launch, try changing the Driver in /etc/X11/xorg.conf from "vesa" to "fglrx", then restart X.8 KB (1,377 words) - 14:25, 10 September 2009
- ...et this X in xen kernel. So made up my mind and wanted to give the generic VESA driver a shot and it worked!!! Finally some XServer with XEN. .../ yum selects minimum dependencies for this, includes xorg-server and xorg vesa driver9 KB (1,330 words) - 17:36, 3 July 2007
- ...of the box using the vesa driver but i wasn't able to get beryl up on the vesa driver so I ventured and used the new intel opensource drivers. My xorg.con8 KB (1,194 words) - 13:49, 6 March 2008
- Driver "vesa"15 KB (2,417 words) - 18:49, 28 August 2012
- ...810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.8 KB (1,209 words) - 08:41, 7 March 2008
- ...nd started sax2. to get a temporary X config (only 800x600 worked with the vesa driver)2 KB (333 words) - 16:09, 3 November 2016
- #* <tt>VIDEO_CARDS="radeon fbdev dummy vesa"</tt> – ''add "[[fglrx]]" for the proprietary driver from ATI.'' <nowiki>tpuser0@localhost # echo VIDEO_CARDS="radeon vesa" >> /etc/make.conf</nowiki>19 KB (2,909 words) - 19:36, 18 May 2015
- # Should we save and restore state using the VESA BIOS Extensions?23 KB (3,723 words) - 04:13, 18 May 2008
- ...m "ati" to "vesa". A resolution of 1400x1050 works fine on my T60 with the vesa drivers (but try 1280x1024 if that doesn't work). But for real support for5 KB (751 words) - 08:21, 1 March 2008
- ...not work: acpi, sound, clock restoration, wireless, graphics driver set to vesa. The ethernet card works perfectly and the vesa driver works fine.8 KB (1,192 words) - 21:49, 27 December 2008
- is to either use vesa / nv driver or to change the23 KB (3,497 words) - 14:32, 20 February 2010
- ...aller selecting the nv driver, which does not support this card. Using the vesa driver will allow X to start. ...x this, you have to reboot into rescue mode and hand-edit xorg.conf to use vesa driver until the restricted nvidia driver is enabled.17 KB (2,725 words) - 18:36, 13 January 2010
- ...VD is only working in text mode due to the nVidia cards, you can use later vesa mode or nVidia drivers or livna nVidia drivers for X <li>vesa mode, no 3D support</li>4 KB (709 words) - 18:12, 12 March 2017
- # Should we save and restore state using the VESA BIOS Extensions?22 KB (3,458 words) - 03:44, 28 January 2008
- ...t, you should have 2D and 3D acceleration working. This is while using the vesa driver: To disable the '''fglrx''' driver and use '''vesa''':12 KB (1,880 words) - 13:46, 3 March 2010
- fb0: VESA VGA frame buffer device36 KB (4,929 words) - 12:17, 10 January 2009
- # Should we save and restore state using the VESA BIOS Extensions?3 KB (415 words) - 01:42, 11 September 2008
- The default xorg.conf worked fine, but it was using the vesa driver which would not allow mplayer to play full-screen. changing: <tt>Driver "vesa"</tt> to <tt>Driver "radeon" </tt> worked great.4 KB (599 words) - 09:19, 24 April 2009
- *Video (VESA)13 KB (2,133 words) - 15:00, 21 July 2010