Prev: iceweasel window raised with remote open
Next: How to install Eclipse 3.5 on Debian 5 (lenny) stable release ?
From: Stephen Powell on 10 Jan 2010 20:50
On 2010-01-09 at 15:52:56 -0500, Stanisław T. Findeisen wrote:
> Below I attach complete /var/log/Xorg.0.log :

The X server detected 2048K (2M) of video RAM on your card.
The X server also defaulted to a color depth of 24. This means
that 24 bits, or three bytes, of video RAM are needed for each
pixel. This is known as "true color" mode. At the default desktop
size of 1024x768, you would need 1024*768*3, or 2,359,296 bytes
of video RAM to specify the color information for each pixel.
Dividing by 1024 to convert to "K", that yields 2304K of video
RAM, which is more video RAM than is installed.

I would suggest
that you drop the color depth down to 16. This is 16-bit color
or "high color" mode. It's not quite as good as 24-bit color,
but pictures still look pretty good.

On my web site at

http://www.wowway.com/~zlinuxman/tp600.htm

you will find an example X configuration file which specifies
a color depth of 16. Don't copy it verbatim, because it is
designed for a different video chipset. But it does provide
a useful template to get you started.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Stanisław T. Findeisen on 12 Jan 2010 09:20
Stephen Powell wrote:
> On 2010-01-09 at 15:52:56 -0500, Stanisław T. Findeisen wrote:
>> Below I attach complete /var/log/Xorg.0.log :
>
> The X server detected 2048K (2M) of video RAM on your card.
> The X server also defaulted to a color depth of 24. This means
> that 24 bits, or three bytes, of video RAM are needed for each
> pixel. This is known as "true color" mode. At the default desktop
> size of 1024x768, you would need 1024*768*3, or 2,359,296 bytes
> of video RAM to specify the color information for each pixel.
> Dividing by 1024 to convert to "K", that yields 2304K of video
> RAM, which is more video RAM than is installed.
>
> I would suggest
> that you drop the color depth down to 16. This is 16-bit color
> or "high color" mode. It's not quite as good as 24-bit color,
> but pictures still look pretty good.
>
> On my web site at
>
> http://www.wowway.com/~zlinuxman/tp600.htm
>
> you will find an example X configuration file which specifies
> a color depth of 16. Don't copy it verbatim, because it is
> designed for a different video chipset. But it does provide
> a useful template to get you started.

Yeah, thanks, I used to edit those X config files years ago on RedHat,
so this isn't *that* new to me. I have something like this:

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "pl"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
EndSection

Section "Device"
Identifier "Configured Video Device"
Option "UseFBDev" "true"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Monitor"
Identifier "SSM 550b"
VendorName "Samsung"
ModelName "SyncMaster 550b"
VertRefresh 85
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "SSM 550b"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1024x768"
EndSubSection
EndSection

I tried "VertRefresh 85" because I know this monitor can handle 1024x768
@ 85 Hz (well, at least it used to several years ago). Unfortunately the
error I am getting now is: "vrefresh out of range" and I am only able to
run X at:

720x400x16 @ 85Hz, or
800x600x16 @ 60Hz

(nothing better).

(**) s3(0): Chipset: "Trio32/64"
(--) s3(0): Framebuffer @ 0xfb000000
(--) s3(0): videoRam = 2048 Kb
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
(--) s3(0): MCLK 55.036 Mhz
(--) s3(0): RefClock: 16000
(--) s3(0): Max pixel clock at this depth is 80 Mhz
(II) s3(0): SSM 550b: Using default hsync range of 31.50-37.90 kHz
(II) s3(0): SSM 550b: Using vrefresh value of 85.00 Hz
(II) s3(0): Clock range: 15.60 to 80.00 MHz
(II) s3(0): Not using default mode "640x480" (vrefresh out of range)
(II) s3(0): Not using default mode "320x240" (vrefresh out of range)
(II) s3(0): Not using default mode "640x480" (vrefresh out of range)
(II) s3(0): Not using default mode "320x240" (vrefresh out of range)
(II) s3(0): Not using default mode "640x480" (vrefresh out of range)
(II) s3(0): Not using default mode "320x240" (vrefresh out of range)
(II) s3(0): Not using default mode "640x480" (hsync out of range)
(II) s3(0): Not using default mode "320x240" (hsync out of range)
(II) s3(0): Not using default mode "800x600" (vrefresh out of range)
(II) s3(0): Not using default mode "400x300" (vrefresh out of range)
(II) s3(0): Not using default mode "800x600" (vrefresh out of range)
(II) s3(0): Not using default mode "400x300" (vrefresh out of range)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "400x300" (hsync out of range)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "400x300" (hsync out of range)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "400x300" (hsync out of range)
(II) s3(0): Not using default mode "1024x768" (vrefresh out of range)
(II) s3(0): Not using default mode "512x384" (vrefresh out of range)
(II) s3(0): Not using default mode "1024x768" (hsync out of range)
(II) s3(0): Not using default mode "512x384" (hsync out of range)
(II) s3(0): Not using default mode "1024x768" (hsync out of range)
(II) s3(0): Not using default mode "512x384" (hsync out of range)
(II) s3(0): Not using default mode "1024x768" (hsync out of range)
(II) s3(0): Not using default mode "512x384" (hsync out of range)
(II) s3(0): Not using default mode "1024x768" (hsync out of range)
(II) s3(0): Not using default mode "512x384" (hsync out of range)
(II) s3(0): Not using default mode "1152x864" (hsync out of range)
(II) s3(0): Not using default mode "576x432" (hsync out of range)
(II) s3(0): Not using default mode "1280x960" (insufficient memory for mode)
(II) s3(0): Not using default mode "640x480" (hsync out of range)
(II) s3(0): Not using default mode "1280x960" (insufficient memory for mode)
(II) s3(0): Not using default mode "640x480" (hsync out of range)
(II) s3(0): Not using default mode "1280x1024" (insufficient memory for
mode)
(II) s3(0): Not using default mode "640x512" (hsync out of range)
(II) s3(0): Not using default mode "1280x1024" (insufficient memory for
mode)
(II) s3(0): Not using default mode "640x512" (hsync out of range)
(II) s3(0): Not using default mode "1280x1024" (insufficient memory for
mode)
(II) s3(0): Not using default mode "640x512" (hsync out of range)
(II) s3(0): Not using default mode "1600x1200" (insufficient memory for
mode)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "1600x1200" (insufficient memory for
mode)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "1600x1200" (insufficient memory for
mode)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "1600x1200" (insufficient memory for
mode)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "1600x1200" (insufficient memory for
mode)
(II) s3(0): Not using default mode "800x600" (hsync out of range)
(II) s3(0): Not using default mode "1792x1344" (insufficient memory for
mode)
(II) s3(0): Not using default mode "896x672" (hsync out of range)
(II) s3(0): Not using default mode "1792x1344" (insufficient memory for
mode)
(II) s3(0): Not using default mode "896x672" (hsync out of range)
(II) s3(0): Not using default mode "1856x1392" (insufficient memory for
mode)
(II) s3(0): Not using default mode "928x696" (hsync out of range)
(II) s3(0): Not using default mode "1856x1392" (insufficient memory for
mode)
(II) s3(0): Not using default mode "928x696" (hsync out of range)
(II) s3(0): Not using default mode "1920x1440" (insufficient memory for
mode)
(II) s3(0): Not using default mode "960x720" (hsync out of range)
(II) s3(0): Not using default mode "1920x1440" (insufficient memory for
mode)
(II) s3(0): Not using default mode "960x720" (hsync out of range)
(II) s3(0): Not using default mode "832x624" (hsync out of range)
(II) s3(0): Not using default mode "416x312" (hsync out of range)
(II) s3(0): Not using default mode "1280x768" (hsync out of range)
(II) s3(0): Not using default mode "640x384" (hsync out of range)
(II) s3(0): Not using default mode "1280x800" (hsync out of range)
(II) s3(0): Not using default mode "640x400" (hsync out of range)
(II) s3(0): Not using default mode "1152x768" (hsync out of range)
(II) s3(0): Not using default mode "576x384" (hsync out of range)
(II) s3(0): Not using default mode "1152x864" (hsync out of range)
(II) s3(0): Not using default mode "576x432" (hsync out of range)
(II) s3(0): Not using default mode "1400x1050" (insufficient memory for
mode)
(II) s3(0): Not using default mode "700x525" (hsync out of range)
(II) s3(0): Not using default mode "1400x1050" (insufficient memory for
mode)
(II) s3(0): Not using default mode "700x525" (hsync out of range)
(II) s3(0): Not using default mode "1400x1050" (insufficient memory for
mode)
(II) s3(0): Not using default mode "700x525" (hsync out of range)
(II) s3(0): Not using default mode "1400x1050" (insufficient memory for
mode)
(II) s3(0): Not using default mode "700x525" (hsync out of range)
(II) s3(0): Not using default mode "1440x900" (insufficient memory for mode)
(II) s3(0): Not using default mode "720x450" (hsync out of range)
(II) s3(0): Not using default mode "1600x1024" (insufficient memory for
mode)
(II) s3(0): Not using default mode "800x512" (hsync out of range)
(II) s3(0): Not using default mode "1680x1050" (insufficient memory for
mode)
(II) s3(0): Not using default mode "840x525" (hsync out of range)
(II) s3(0): Not using default mode "1920x1200" (insufficient memory for
mode)
(II) s3(0): Not using default mode "960x600" (hsync out of range)
(II) s3(0): Not using default mode "1920x1200" (insufficient memory for
mode)
(II) s3(0): Not using default mode "960x600" (hsync out of range)
(II) s3(0): Not using default mode "1920x1440" (insufficient memory for
mode)
(II) s3(0): Not using default mode "960x720" (hsync out of range)
(II) s3(0): Not using default mode "2048x1536" (insufficient memory for
mode)
(II) s3(0): Not using default mode "1024x768" (hsync out of range)
(II) s3(0): Not using default mode "2048x1536" (insufficient memory for
mode)
(II) s3(0): Not using default mode "1024x768" (hsync out of range)
(II) s3(0): Not using default mode "2048x1536" (insufficient memory for
mode)
(II) s3(0): Not using default mode "1024x768" (hsync out of range)
(II) s3(0): Not using mode "1024x768" (no mode of this name)
(--) s3(0): Virtual size is 720x400 (pitch 800)
(**) s3(0): Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz
(II) s3(0): Modeline "720x400"x85.0 35.50 720 756 828 936 400 401
404 446 -hsync +vsync (37.9 kHz)
(**) s3(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) s3(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401
404 445 -hsync +vsync (37.9 kHz)
(**) s3(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) s3(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382
385 445 +hsync -vsync (37.9 kHz)
(**) s3(0): Default mode "360x200": 17.8 MHz, 37.9 kHz, 85.0 Hz (D)
(II) s3(0): Modeline "360x200"x85.0 17.75 360 378 414 468 200 200
202 223 doublescan -hsync +vsync (37.9 kHz)
(**) s3(0): Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) s3(0): Modeline "320x200"x85.3 15.75 320 336 368 416 200 200
202 222 doublescan -hsync +vsync (37.9 kHz)
(**) s3(0): Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) s3(0): Modeline "320x175"x85.3 15.75 320 336 368 416 175 191
192 222 doublescan +hsync -vsync (37.9 kHz)
(==) s3(0): DPI set to (96, 96)

So probably it is the card that cannot handle 1024x768 @ 85 Hz? I even
tried 8-bit color for that but with no success. :-(

On the other hand, those years ago on RedHat I used to configure those
"mode" lines manually.... I will let you know should I make it work at
1024x768 @ 85 Hz.

STF

http://eisenbits.homelinux.net/~stf/
OpenPGP: DFD9 0146 3794 9CF6 17EA D63F DBF5 8AA8 3B31 FE8A


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Stephen Powell on 12 Jan 2010 10:50
On 2010-01-11 at 15:52:56 -0500, Stanisław T. Findeisen wrote:
> I tried "VertRefresh 85" because I know this monitor can handle 1024x768
> @ 85 Hz (well, at least it used to several years ago). Unfortunately the
> error I am getting now is: "vrefresh out of range" and I am only able to
> run X at:
>
> 720x400x16 @ 85Hz, or
> 800x600x16 @ 60Hz

Well, we're making progress. Your monitor apparently does not support
DDC2/EDID; so the X server does not know what your monitor's horizontal
and vertical sync frequency ranges are. You have to tell it. The "safe"
assumptions that the X server is making are well below your monitor's
capabilities.

You probably don't need to compose your own modeline though. Let's see.
You told me that your monitor is a Samsung SyncMaster 550b. According to
the owner's manual, which I found on the Internet, the horizontal sync
frequency range is 30 kHz to 70 kHz, and the vertical sync frequency range
is 50 Hz to 160 Hz. The video bandwidth (maximum pixel clock) is 110 MHz.
That's less than the maximum pixel clock rate supported by the video card;
so you should be OK there, as we can see from

> (--) s3(0): Max pixel clock at this depth is 80 Mhz

So your monitor section (you should have only one monitor section)
should look something like this:

Section "Monitor"
Identifier "Configured Monitor"
VendorName "Samsung"
ModelName "SyncMaster 550b"
HorizSync 30-70
VertRefresh 50-160
Option "TargetRefresh" "75"
EndSection

The "TargetRefresh" option is optional. If used, it will try to use only
video modes of 75 Hz vertical sync or higher. Give that a whirl and see
what happens. Make sure that you are specifying the color depth as 16
(DefaultDepth 16 in the "Screen" section).


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Stanisław T. Findeisen on 13 Jan 2010 07:20
Stephen Powell wrote:
> On 2010-01-11 at 15:52:56 -0500, Stanisław T. Findeisen wrote:
>> I tried "VertRefresh 85" because I know this monitor can handle 1024x768
>> @ 85 Hz (well, at least it used to several years ago). Unfortunately the
>> error I am getting now is: "vrefresh out of range" and I am only able to
>> run X at:
>>
>> 720x400x16 @ 85Hz, or
>> 800x600x16 @ 60Hz
>
> Well, we're making progress. Your monitor apparently does not support
> DDC2/EDID; so the X server does not know what your monitor's horizontal
> and vertical sync frequency ranges are. You have to tell it. The "safe"
> assumptions that the X server is making are well below your monitor's
> capabilities.

What are those sync frequency ranges?

> You probably don't need to compose your own modeline though. Let's see.
> You told me that your monitor is a Samsung SyncMaster 550b. According to
> the owner's manual, which I found on the Internet, the horizontal sync
> frequency range is 30 kHz to 70 kHz, and the vertical sync frequency range
> is 50 Hz to 160 Hz. The video bandwidth (maximum pixel clock) is 110 MHz.
> That's less than the maximum pixel clock rate supported by the video card;
> so you should be OK there, as we can see from
>
>> (--) s3(0): Max pixel clock at this depth is 80 Mhz

Less??

> So your monitor section (you should have only one monitor section)
> should look something like this:
>
> Section "Monitor"
> Identifier "Configured Monitor"
> VendorName "Samsung"
> ModelName "SyncMaster 550b"
> HorizSync 30-70
> VertRefresh 50-160
> Option "TargetRefresh" "75"
> EndSection
>
> The "TargetRefresh" option is optional. If used, it will try to use only
> video modes of 75 Hz vertical sync or higher. Give that a whirl and see
> what happens. Make sure that you are specifying the color depth as 16
> (DefaultDepth 16 in the "Screen" section).

With this I am able to run 1024x768x16 @ 75 Hz! However, I wanted 85 Hz.

(**) s3(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
(II) s3(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(**) s3(0): Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) s3(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
(**) s3(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) s3(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(**) s3(0): Default mode "1024x768": 44.9 MHz, 35.5 kHz, 87.0 Hz (I)
(II) s3(0): Modeline "1024x768"x87.0 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (35.5 kHz)

Why, in the log lines above, (((pixel clock rate) / ((v-res) * (h-res))) != v-refresh)? Here: http://en.wikipedia.org/wiki/XFree86_Modeline they say that there should be equality.
For instance: in the 1st line, 78.8 MHz / (1024*768) > 100, but the horizontal refresh rate is less: 75 Hz.
For instance: in the last line, 44.9 MHz / (1024*768) = 57, but the horizontal refresh rate is more: 87 Hz.

Where do those modes come from, if there are none in the config file and my monitor does not support EDID? I can also see that the monitor mode I want (1024x768 / 94.5 Mhz / 68.677 kHz / 85 Hz from the monitor manual) is not on the list. Why?

What do those line prefixes ((--), (==), (**), (WW), (II) etc.) in the log stand for? I would guess (WW) stands for "warning", but all the rest looks like "notice"...

I also tried TargetRefresh=85 but with no success.

I would say maximum pixel clock rate supported by the video card is 80 MHz and *that* is the limit?...

STF

http://eisenbits.homelinux.net/~stf/
OpenPGP: DFD9 0146 3794 9CF6 17EA D63F DBF5 8AA8 3B31 FE8A

From: Stan Hoeppner on 13 Jan 2010 09:20
"Stanisław T. Findeisen" put forth on 1/13/2010 6:18 AM:

> With this I am able to run 1024x768x16 @ 75 Hz! However, I wanted 85 Hz.

Just be glad you got it working at 75 Hz. Anything above 60 Hz will eliminate
visual flicker for most people, and anything above 70 Hz will eliminate flicker
for all people. No human has an eye with a 70 Hz plus scan rate.

> (**) s3(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
> (II) s3(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
> (**) s3(0): Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
> (II) s3(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
> (**) s3(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
> (II) s3(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)


> (**) s3(0): Default mode "1024x768": 44.9 MHz, 35.5 kHz, 87.0 Hz (I)
> (II) s3(0): Modeline "1024x768"x87.0 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (35.5 kHz)

You don't want to use this 87 Hz mode. It is interlaced, hence the (I). You
will notice interline twitter and likely interlace flicker using this mode and
it will be hard on your eyes. See: http://en.wikipedia.org/wiki/Interlace

--
Stan


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: iceweasel window raised with remote open
Next: How to install Eclipse 3.5 on Debian 5 (lenny) stable release ?