Search results

Jump to: navigation, search
  • ...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 framebuffer
    3 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 & mplayer
    3 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 support
    34 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 accele
    6 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 wor
    814 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''. Aft
    7 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 int
    19 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, fgl
    30 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 vesa
    3 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 above
    9 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 addin
    11 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_LAPTOP
    11 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 resolutio
    4 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 told
    7 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 mor
    25 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 Google
    3 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 identi
    17 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.7W
    11 KB (1,442 words) - 14:42, 29 March 2011
  • # VESA framebuffer console @ 800x600x256
    11 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 2007
    29 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 driver
    9 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.con
    8 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 for
    5 KB (751 words) - 08:21, 1 March 2008

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)