<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Hetz,<br>
<br>
The chipset is cle266, Linux Ubuntu 8.04, I configured Xserver to use
openchrome driver ( Ubuntu has it inside ) <br>
<br>
I suppose these VESA messages were printed before I rerun Xserver and I
did not realize it<br>
<br>
Now the messages are come from OpenChrome but what does VESA Bios
means I still do not now ???<br>
<br>
(II) CHROME(0): Modeline "800x600"x84.9 56.75 800 848 928 1056 600
603 607 633 -hsync +vsync (53.7 kHz)<br>
(II) CHROME(0): Modeline "1024x768"x84.9 94.50 1024 1096 1200 1376
768 771 775 809 -hsync +vsync (68.7 kHz)<br>
(II) CHROME(0): Modeline "1280x960"x84.9 148.25 1280 1368 1504 1728
960 963 967 1011 -hsync +vsync (85.8 kHz)<br>
(II) CHROME(0): Modeline "1280x1024"x84.8 159.50 1280 1376 1512 1744
1024 1027 1034 1078 -hsync +vsync (91.5 kHz)<br>
(II) CHROME(0): Modeline "1600x1200"x75.0 204.75 1600 1720 1888 2176
1200 1203 1207 1255 -hsync +vsync (94.1 kHz)<br>
(II) CHROME(0): ViaOutputsDetect<br>
(II) CHROME(0): VIATVDetect<br>
(WW) CHROME(0): This device is supposed to have a TV encoder, but we
are unable to detect it (support missing?).<br>
(II) CHROME(0): ViaOutputsSelect<br>
(II) CHROME(0): ViaOutputsSelect: X Configuration: 0x00<br>
(II) CHROME(0): ViaOutputsSelect: BIOS Initialised register: 0x00<br>
(II) CHROME(0): ViaOutputsSelect: CRT.<br>
(II) Loading sub module "int10"<br>
(II) LoadModule: "int10"<br>
(II) Loading /usr/lib/xorg/modules//libint10.so<br>
(II) Module int10: vendor="X.Org Foundation"<br>
compiled for 1.4.0.90, module version = 1.0.0<br>
ABI class: X.Org Video Driver, version 2.0<br>
(II) Loading sub module "vbe"<br>
(II) LoadModule: "vbe"<br>
(II) Loading /usr/lib/xorg/modules//libvbe.so<br>
(II) Module vbe: vendor="X.Org Foundation"<br>
compiled for 1.4.0.90, module version = 1.1.0<br>
ABI class: X.Org Video Driver, version 2.0<br>
(II) Loading sub module "int10"<br>
(II) LoadModule: "int10"<br>
(II) Reloading /usr/lib/xorg/modules//libint10.so<br>
(II) CHROME(0): initializing int10<br>
(II) CHROME(0): Primary V_BIOS segment is: 0xc000<br>
(II) CHROME(0): VESA BIOS detected<br>
(II) CHROME(0): VESA VBE Version 3.0<br>
(II) CHROME(0): VESA VBE Total Mem: 65536 kB<br>
(II) CHROME(0): VESA VBE OEM: VIA P4N800 PRO<br>
<br>
(II) CHROME(0): VESA VBE OEM Software Rev: 1.0<br>
(II) CHROME(0): VESA VBE OEM Vendor:<br>
(II) CHROME(0): VESA VBE OEM Product:<br>
(II) CHROME(0): VESA VBE OEM Product Rev:<br>
(II) CHROME(0): Searching for matching VESA mode(s):<br>
Mode: 101 (640x480)<br>
<br>
II) CHROME(0): VIASwitchMode<br>
(II) CHROME(0): [drm] Cleaning up DMA ring-buffer.<br>
(II) CHROME(0): VIAWriteMode<br>
(II) CHROME(0): Trying VBE Mode 1280x960 (0xc16a) Refresh 85.00:<br>
(II) CHROME(0): ViaVbeSetRefresh<br>
(II) CHROME(0): Active Device: 1<br>
(II) CHROME(0): Refresh Rate Index: 7<br>
?????????????????<br>
(II) CHROME(0): VBESetVBEMode failed...but worked OK without customized
refresh and dotclock.<br>
<br>
??????????<br>
(II) CHROME(0): VIAAdjustFrame<br>
<br>
<br>
Hetz Ben Hamo wrote:
<blockquote
cite="mid:41e41e7a0905050334o31efdae3od0260944481c8314@mail.gmail.com"
type="cite">
<pre wrap="">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:
<a class="moz-txt-link-freetext" href="http://linux.via.com.tw/support/downloadFiles.action">http://linux.via.com.tw/support/downloadFiles.action</a>
You can use the forum here (<a class="moz-txt-link-freetext" href="http://www.tkarena.com/forums/via-arena/">http://www.tkarena.com/forums/via-arena/</a>)
which I'm sure your question has been asked before.
Thanks,
Hetz
On Tue, May 5, 2009 at 2:09 PM, Lev Olshvang <a class="moz-txt-link-rfc2396E" href="mailto:levo@vboxcomm.com"><levo@vboxcomm.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="mailto:levo@vboxcomm.com"><levo@vboxcomm.com></a> 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
<a class="moz-txt-link-abbreviated" href="mailto:Linux-il@cs.huji.ac.il">Linux-il@cs.huji.ac.il</a>
<a class="moz-txt-link-freetext" href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>