Search results
Create the page "Vesa" on this wiki! See also the search results found.
- ...ne.. (Note - haven't tested with fglrx or the avivo X drivers yet, but the vesa X driver is ok).--[[User:Jescombe|Jescombe]] 15:40, 28 August 2006 (CEST) Sorry, my ignorance. I was talking about the X vesa driver, not the vesafb kernel framebuffer. Better do better reading from n2 KB (383 words) - 08:35, 25 March 2008
- ...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
- 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
- ...al mode. After rebooting, the GUI loads and I can see that I am using the "vesa" driver.4 KB (773 words) - 20:47, 9 September 2007
- ...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
