Lev, You didn't tell me which chipset do you use (I understand it's VIA, but which VIA?), nor distribution that you use...
You can download a driver + docs if you know what chipset in your board (lspci -v) at this site: http://linux.via.com.tw/support/downloadFiles.action You can use the forum here (http://www.tkarena.com/forums/via-arena/) which I'm sure your question has been asked before. Thanks, Hetz On Tue, May 5, 2009 at 2:09 PM, Lev Olshvang <l...@vboxcomm.com> wrote: > Thanks, > > After hard googling I managed to set up working setup in xorg.conf > > What I miss - i did not find good explanation for various Option and their > affects, ( I do not deal with graphics usually), perhaps you can give me > some reference > > It looks this way : > > Section "Monitor" > Identifier "Configured Monitor" > Vendorname "Plug 'n' Play" > Modelname "Plug 'n' Play" > HorizSync 30-98 > Option "DPMS" > Option "VBEModes" > VertRefresh 60-85 > #Gamma 1.0 > EndSection > > Section "Screen" > Identifier "Default Screen" > Device "VIA" > Monitor "Configured Monitor" > DefaultDepth 24 > Option "metamodes" "1280x1024_75 +0+0; 1280x1024 +0+0; > 1024x768 +0+0; 800x600 +0+0" > EndSection > > > > > Hetz Ben Hamo wrote: > > Hi Lev, > > Unless this is a last resort, I really recommend *NOT* to use the VESA > driver. Vesa used the least of your grpahics chip capabilities, NO > graphics acceleration, no nothing, > > Any native driver for your graphics chip would do a better job of > allocating memory (and not giving you only 64MB RAM for your chip) and > will detect all the resolutions. VESA most of the time don't know much > about those resolutions because it's trying to go "wild" with 24 bit > colors and for VESA, thats what you can get unless you fiddle with > many parameters in xorg.conf file. > > Your monitor can supports multiple resolutions as shown by your log, > but VESA is too dumb. Use the correct driver (which chip do you have? > if you can tell me, I'll be happy to tell you which driver to use) and > it should show all the fancy stuff. > > Thanks, > Hetz > > On Tue, May 5, 2009 at 12:51 PM, Lev Olshvang <l...@vboxcomm.com> wrote: > > > Hi, > > I have only two resolutions displayed by gnome-display-properties while my > Monitor connected to other systems definetly have more than 2 resolutions > available. > > > > > From the Xserver Log I got the following: > > > (II) VESA(0): Total Memory: 1024 64KB banks (65536kB) > (II) VESA(0): Configured Monitor: Using hsync range of 30.00-98.00 kHz > (II) VESA(0): Configured Monitor: Using vrefresh range of 50.00-160.00 Hz > (II) VESA(0): Configured Monitor: Using maximum pixel clock of 200.00 MHz > (II) VESA(0): Not using built-in mode "2048x1536" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1920x1440" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1920x1200" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1920x1080" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1600x1200" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1680x1050" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1600x1024" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1400x1050" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1280x1024" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1440x900" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1280x960" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1366x768" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1360x768" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1280x800" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1152x864" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1280x768" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1280x720" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1024x768" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1024x640" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1024x600" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "1024x576" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "960x600" (width too large for virtual > size) > (II) VESA(0): Not using built-in mode "1024x512" (width too large for > virtual size) > (II) VESA(0): Not using built-in mode "720x576" (no mode of this name) > (II) VESA(0): Not using built-in mode "853x480" (width too large for virtual > size) > (II) VESA(0): Not using built-in mode "852x480" (width too large for virtual > size) > (II) VESA(0): Not using built-in mode "848x480" (width too large for virtual > size) > (II) VESA(0): Not using built-in mode "720x540" (no mode of this name) > (II) VESA(0): Not using built-in mode "800x480" (no mode of this name) > (II) VESA(0): Not using built-in mode "720x480" (no mode of this name) > (--) VESA(0): Virtual size is 800x600 (pitch 800) > (**) VESA(0): *Built-in mode "800x600" > (**) VESA(0): Built-in mode "640x480" > (**) VESA(0): Display dimensions: (320, 240) mm > (**) VESA(0): DPI set to (63, 63) > (II) VESA(0): Attempting to use 85Hz refresh for mode "800x600" (114) > (II) VESA(0): Attempting to use 85Hz refresh for mode "640x480" (111) > > > _______________________________________________ > Linux-il mailing list > Linux-il@cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > > > > -- Skepticism is the lazy person's default position. my blog (hebrew): http://benhamo.org _______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
