On Mon, 09 Aug 2004 18:25:34 +0000, philicorda wrote:


> It would be helpful if you could post your xorg config, and details about
> graphics card and monitor.
> Apart from that, try looking at the X logs in /var/log, it may be
> attempting the higher resolution, finding that your monitor is not capable
> of the required refresh rate (according to the settings in xorg.cfg), and
> falling back to a lower res.
>
> Also, you have to select the right cheese for the mouse, dell mice
> like Edam, Abit ones like Emmentale, and Microsoft ones a pungent Gruyere.

I'm afraid this is a rather long post.

The mouse is a Logitech M-xxxxx so it prefers mozzarella, reflecting its
light soft touch

The card is a Nvidia Riva128 4MB. The monitor is an old Fujitsu 514(C5D1R)
which never seems to occur in lists. Mandrake reads it as 1024x768@70Hz.
and happily runs it at 15 bits colour depth. Ditto SuSE.


File generated by xf86config. I've trimmed some of the obviously irrelevant
stuff to reduce size. The last twenty odd lines of this post baffle me.


Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"

EndSection

# ************************************************** ********************
# Files section. This allows default font and rgb paths to be set
# ************************************************** ********************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),


EndSection

# ************************************************** ********************
# Server flags section.
# ************************************************** ********************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# ************************************************** ********************
# Input devices
# ************************************************** ********************

# ************************************************** ********************
# Core keyboard's InputDevice section
# ************************************************** ********************

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for X.Org
# Option "XkbRules" "__XKBDEFRULES__"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "gb"

EndSection


# ************************************************** ********************
# Core Pointer's InputDevice section
# ************************************************** ********************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

Option "ChordMiddle"

EndSection


# ************************************************** ********************
# Other input device sections

# ************************************************** ********************
# Monitor section
# ************************************************** ********************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 57.0

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-70

EndSection


# ************************************************** ********************
# Graphics device section
# ************************************************** ********************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "My Video Card"
Driver "vga"
# unsupported card
VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection


# ************************************************** ********************
# Screen sections
# ************************************************** ********************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 8

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection

# ************************************************** ********************
# ServerLayout sections.
# ************************************************** ********************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
# Mode 0666
# EndSection




Looking at Xorg.0.log I found this bit


(**) VGA(0): Depth 8, (--) framebuffer bpp 8
(==) VGA(0): RGB weight 666
(==) VGA(0): Default visual is PseudoColor
(==) VGA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) VGA(0): videoRam: 4096 kBytes (using 64 kBytes).
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(II) VGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(==) VGA(0): Virtual size is 320x200 (pitch 320)
(**) VGA(0): Built-in mode "Generic 320x200 default mode": 12.6 MHz (scaled from 25.2 MHz), 31.5 kHz, 70.2 Hz (VScan)
(II) VGA(0): Modeline "Generic 320x200 default mode" 12.59 320 336 384 400 200 206 207 224 vscan 2 -hsync +vsync
(==) VGA(0): DPI set to (75, 75)


Out of my depth here but is it loading a 300x200 screen instead of
1024x768 ? It would explain the six times too big look I referred to in
the original post.

Ken.

Ken Parkes wrote:

<snip>

> # ************************************************** ********************
> # Monitor section
> # ************************************************** ********************
>
> # Any number of monitor sections may be present
>
> Section "Monitor"
>
> Identifier "My Monitor"
>
> # HorizSync is in kHz unless units are specified.
> # HorizSync may be a comma separated list of discrete values, or a
> # comma separated list of ranges of values.
> # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
> # USER MANUAL FOR THE CORRECT NUMBERS.
>
> HorizSync 31.5 - 57.0
>
> # HorizSync 30-64 # multisync
> # HorizSync 31.5, 35.2 # multiple fixed sync frequencies
> # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
>
> # VertRefresh is in Hz unless units are specified.
> # VertRefresh may be a comma separated list of discrete values, or a
> # comma separated list of ranges of values.
> # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
> # USER MANUAL FOR THE CORRECT NUMBERS.
>
> VertRefresh 50-70
>
> EndSection


Are the HorizSync and VerRefresh numbers correct for your monitor? The
numbers Mandrake and Suse use put here will work.


<snip>

> # Device configured by xf86config:
>
> Section "Device"
> Identifier "My Video Card"
> Driver "vga"
> # unsupported card
> VideoRam 4096
> # Insert Clocks lines here if appropriate
> EndSection

Don't you want the nv driver?

>
>

<snip>

> Looking at Xorg.0.log I found this bit
>
>
> (**) VGA(0): Depth 8, (--) framebuffer bpp 8
> (==) VGA(0): RGB weight 666
> (==) VGA(0): Default visual is PseudoColor
> (==) VGA(0): Using gamma correction (1.0, 1.0, 1.0)
> (**) VGA(0): videoRam: 4096 kBytes (using 64 kBytes).
> (II) Loading sub module "vgahw"
> (II) LoadModule: "vgahw"
> (II) Loading /usr/X11R6/lib/modules/libvgahw.a
> (II) Module vgahw: vendor="X.Org Foundation"
> compiled for 6.7.0, module version = 0.1.0
> ABI class: X.Org Video Driver, version 0.7
> (II) VGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is
> 0x0000 (==) VGA(0): Virtual size is 320x200 (pitch 320)
> (**) VGA(0): Built-in mode "Generic 320x200 default mode": 12.6 MHz
> (scaled from 25.2 MHz), 31.5 kHz, 70.2 Hz (VScan)
> (II) VGA(0): Modeline "Generic 320x200 default mode" 12.59 320 336 384
> 400 200 206 207 224 vscan 2 -hsync +vsync (==) VGA(0): DPI set to (75,
> 75)
>
>
> Out of my depth here but is it loading a 300x200 screen instead of
> 1024x768 ? It would explain the six times too big look I referred to in
> the original post.

So it would seem. "Virtual size is 320x200." And the 8bpp depth is the
default specified. Suspect your monitor specs are wrong, and you need to
be using the nv driver.


--
Old Man

On Mon, 09 Aug 2004 21:17:36 +0000, Old Man wrote:


>
> Are the HorizSync and VerRefresh numbers correct for your monitor? The
> numbers Mandrake and Suse use put here will work.
>


> Don't you want the nv driver?
>
>>

>
> So it would seem. "Virtual size is 320x200." And the 8bpp depth is the
> default specified. Suspect your monitor specs are wrong, and you need to
> be using the nv driver.


These monitor settings are as MDK and SuSE.

Not had to install drivers by hand before, should be useful experience.
Should be on the other two distro discs, will have a look for them.

The reference to re-install was a touch of irony which I didn't flag
properly.

Many thanks for your help.

Ken.

On Tue, 10 Aug 2004 13:26:42 +0100, Ken Parkes wrote:

> On Mon, 09 Aug 2004 21:17:36 +0000, Old Man wrote:
>
>
>>
>> Are the HorizSync and VerRefresh numbers correct for your monitor? The
>> numbers Mandrake and Suse use put here will work.
>>
>
>
>> Don't you want the nv driver?
>>
>>>
>
>>
>> So it would seem. "Virtual size is 320x200." And the 8bpp depth is the
>> default specified. Suspect your monitor specs are wrong, and you need to
>> be using the nv driver.
>
>
> These monitor settings are as MDK and SuSE.
>
> Not had to install drivers by hand before, should be useful experience.
> Should be on the other two distro discs, will have a look for them.

The nv driver is installed already, it comes with Xorg. Just change
Driver "vga"
to
Driver "nv"

There seem to be two references to 'Driver "vga"' in the file, you should
perhaps remove the first one.

If you wish to force X to use a particular resolution in a kind of 'work
or break, damm you!' way, remove the other resolutions for all bit depths.

So...

Modes "1280x1024" "1024x768" "800x600" "640x480"

Becomes

Modes "1024x768"

I'd do that after getting the nv driver working properly though.

>
> The reference to re-install was a touch of irony which I didn't flag
> properly.
>
> Many thanks for your help.
>
> Ken.

Once you got the blighter working, have a look at nvidia drivers them
selves. I am using one for Geforce and blender gl window certainly is
more usable.

cheers
sreekant

On Wed, 11 Aug 2004 01:47:57 +0000, philicorda wrote:

>
> The nv driver is installed already, it comes with Xorg. Just change
> Driver "vga"
> to
> Driver "nv"
>
>...........etc.


Thanks for that, and sreekant.

Couldn't find the driver in MDK ?????? But played around with different
setups last night and found the system works beautifully set for vesa, and
the next lower horizontal sync rate. Really dont understand it but it's
giving better quality pictures than MDK and SuSE, with crisper fonts. I
shall try your suggestions, and will have to spend some time looking into
monitors, There are obviously some things about them I dont understand.

Ken.

On Wed, 11 Aug 2004 14:14:04 +0100, Ken Parkes wrote:

> On Wed, 11 Aug 2004 01:47:57 +0000, philicorda wrote:
>
>>
>> The nv driver is installed already, it comes with Xorg. Just change
>> Driver "vga"
>> to
>> Driver "nv"
>>
>>...........etc.
>
>
> Thanks for that, and sreekant.
>
> Couldn't find the driver in MDK ?????? But played around with different
> setups last night and found the system works beautifully set for vesa, and
> the next lower horizontal sync rate. Really dont understand it but it's
> giving better quality pictures than MDK and SuSE, with crisper fonts. I
> shall try your suggestions, and will have to spend some time looking into
> monitors, There are obviously some things about them I dont understand.

Vesa can be a little slow compared to using the specific driver, but
if it works fine, I guess that's not a problem.

Try xvidtune (should be installed already) when running X if you want to
try tweaking refresh rates and suchlike. I've tried 'overclocking'
monitors sometimes with it when I've been stuck with an old 15"... You can
often go quite far over the manufacturers specs before the screen is
obscured by smoke.

>
> Ken.

> >>
> Couldn't find the driver in MDK ?????? But played around with different

Have a look at this driver. I can't remember what the file I
downloaded is called but it is an year old now anyway. This might be a
new driver.

http://www.nvidia.com/object/linux_d..._1.0-6111.html

Ta
sreekant