LinuxQuestions.org - [SOLVED] 20.1" Flat Panel LCD Artifacts @startup Problem

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - 20.1" Flat Panel LCD Artifacts @startup Problem (https://www.linuxquestions.org/questions/slackware-14/20-1-flat-panel-lcd-artifacts-%40startup-problem-600214/)

20.1" Flat Panel LCD Artifacts @startup Problem

Getting Monitor Artifacts at XFCE startup issue: ATI Rage 128 Pro. Running Xfce with hugesmp.s kernel can't compile kernel if I cant get xorg configured right.

Do u think I shouldn't be using slackware12? Hope this is all not too much.

1. I don't know what my LCD Monitor Dot Frequency Clock is and there is no mention of it in its manual.

2. What is the refresh rate? Is it the same as monitor's response time, ie.25ms?

Monitor Auto Self adjusts, No software Driver. When I tried to generate a modeline using, (http://xtiming.sourceforge.net/cgi-bin/xtiming.pl this is what) I got:

Use this modeline at your own risk.
Modeline "1600x1200@59" 174.01 1600 1632 2288 2320 1200 1224 1236 1261
Horizontal sync frequency: 75 kHz
This is not encouraging!
Warning!
# Horizontal sync frequency below minimum of 79.976kHz!
# Horizontal sync frequency above maximum of 31.475kHz!
# Refresh rate below minimum of 75.024Hz!

Don't understand the Warning Lines? They don't make sense because the manual states Frequency range is: FH:31.469~79.97Khz
FV:59.9~75.0240Hz

What is more important to have the most accurate the Horizontal or Veritical refresh rates?

Issue this command.

cat /etc/X11/xorg.conf

And copy/paste it to here. If using xterm, highlight the page by holding down the left mouse button, and paste with middle button.

Try running 'xorgsetup', it will help you get a usable configuration.

MY Xorgconfig Settings

Quote:

Originally Posted by simcox1 (Post 2961799)

Issue this command.

cat /etc/X11/xorg.conf

And copy/paste it to here. If using xterm, highlight the page by holding down the left mouse button, and paste with middle button.

Code:

cat /etc/X11/xorg.conf

# File generated by xorgconfig.



#

# Copyright 2004 The X.Org Foundation

#

# Permission is hereby granted, free of charge, to any person obtaining a

# copy of this software and associated documentation files (the "Software"),

# to deal in the Software without restriction, including without limitation

# the rights to use, copy, modify, merge, publish, distribute, sublicense,

# and/or sell copies of the Software, and to permit persons to whom the

# Software is furnished to do so, subject to the following conditions:

# 

# The above copyright notice and this permission notice shall be included in

# all copies or substantial portions of the Software.

# 

# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL

# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF

# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

# SOFTWARE.

# 

# Except as contained in this notice, the name of The X.Org Foundation shall

# not be used in advertising or otherwise to promote the sale, use or other

# dealings in this Software without prior written authorization from

# The X.Org Foundation.

#



# **********************************************************************

# Refer to the xorg.conf(5x) man page for details about the format of 

# this file.

# **********************************************************************



# **********************************************************************

# Module section -- this  section  is used to specify

# which dynamically loadable modules to load.

# **********************************************************************

#

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 font modules

    Load        "type1"

    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/share/X11/rgb"



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

# as well as specifying multiple comma-separated entries in one FontPath

# command (or a combination of both methods)

# 

# 



    FontPath  "/usr/share/fonts/TTF"

    FontPath  "/usr/share/fonts/OTF"

    FontPath  "/usr/share/fonts/Type1"

    FontPath  "/usr/share/fonts/misc"

    FontPath  "/usr/share/fonts/75dpi/:unscaled"

#    FontPath  "/usr/lib/X11/fonts/local/"

    FontPath  "/usr/lib/X11/fonts/misc/"

    FontPath  "/usr/lib/X11/fonts/75dpi/:unscaled"

    FontPath  "/usr/lib/X11/fonts/100dpi/:unscaled"

    FontPath  "/usr/lib/X11/fonts/Speedo/"

    FontPath  "/usr/lib/X11/fonts/Type1/"

    FontPath  "/usr/lib/X11/fonts/TTF/"

    FontPath  "/usr/lib/X11/fonts/OTF/"

    FontPath  "/usr/lib/X11/fonts/cyrillic/"

    FontPath  "/usr/lib/X11/fonts/75dpi/"

    FontPath  "/usr/lib/X11/fonts/100dpi/"



# The module search path.  The default path is shown here.



#    ModulePath "/usr/lib/xorg/modules"



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 <Ctrl><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 <Ctrl><Alt><BS> server abort sequence

# This allows clients to receive this key event.



#    Option "DontZap"



# Uncomment this to disable the <Ctrl><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      "kbd"



# 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"    "pc105"

# 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 Xorg

#    Option "XkbRules"    "xorg"

#    Option "XkbModel"    "pc105"

#    Option "XkbLayout"  "us"

#    Option "XkbVariant"  ""

#    Option "XkbOptions"  ""



#    Option "XkbDisable"



    Option "XkbRules"  "xorg"

    Option "XkbModel"  "logicdpa"

    Option "XkbLayout"  "us"



EndSection





# **********************************************************************

# Core Pointer's InputDevice section

# **********************************************************************



Section "InputDevice"



# Identifier and driver



    Identifier  "Mouse1"

    Driver      "mouse"

    Option "Protocol"    "Auto" # Auto detect

    Option "Device"      "/dev/input/mice"



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

# the following line.



#    Option "Protocol"  "Xqueue"



# Mouse-speed setting for PS/2 mouse.



#    Option "Resolution"        "256"



# Baudrate and SampleRate are only for some Logitech mice. In

# almost every case these lines should be omitted.



#    Option "BaudRate"  "9600"

#    Option "SampleRate"        "150"



# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,

# horizontal wheel to buttons 6 & 7.  Change if your mouse has more than

# 3 buttons and you need to map the wheel to different button ids to avoid

# conflicts.



    Option "ZAxisMapping"  "4 5 6 7"



# Emulate3Buttons is an option for 2-button 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 

# this is optional and is required only if you

# are using extended input devices.  This is for example only.  Refer

# to the xorg.conf man page for a description of the options.

# **********************************************************************

#

# Section "InputDevice" 

#    Identifier  "Mouse2"

#    Driver      "mouse"

#    Option      "Protocol"      "MouseMan"

#    Option      "Device"        "/dev/mouse2"

# EndSection

#

# Section "InputDevice"

#    Identifier "spaceball"

#    Driver    "magellan"

#    Option    "Device"        "/dev/cua0"

# EndSection

#

# Section "InputDevice"

#    Identifier "spaceball2"

#    Driver    "spaceorb"

#    Option    "Device"        "/dev/cua0"

# EndSection

#

# Section "InputDevice"

#    Identifier "touchscreen0"

#    Driver    "microtouch"

#    Option    "Device"        "/dev/ttyS0"

#    Option    "MinX"          "1412"

#    Option    "MaxX"          "15184"

#    Option    "MinY"          "15372"

#    Option    "MaxY"          "1230"

#    Option    "ScreenNumber"  "0"

#    Option    "ReportingMode" "Scaled"

#    Option    "ButtonNumber"  "1"

#    Option    "SendCoreEvents"

# EndSection

#

# Section "InputDevice"

#    Identifier "touchscreen1"

#    Driver    "elo2300"

#    Option    "Device"        "/dev/ttyS0"

#    Option    "MinX"          "231"

#    Option    "MaxX"          "3868"

#    Option    "MinY"          "3858"

#    Option    "MaxY"          "272"

#    Option    "ScreenNumber"  "0"

#    Option    "ReportingMode" "Scaled"

#    Option    "ButtonThreshold"      "17"

#    Option    "ButtonNumber"  "1"

#    Option    "SendCoreEvents"

# EndSection



# **********************************************************************

# Monitor section

# **********************************************************************



# Any number of monitor sections may be present



Section "Monitor"



    Identifier  "SYNAPS, Composite, DPMS"



# 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-79



#    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 59-75



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 xorgconfig:



Section "Device"

    Identifier  "ATI RAGE 128 PRO, 32M, AGP"

    Driver      "r128"

    #VideoRam    32000

    # 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      "ATI RAGE 128 PRO, 32M, AGP"

    Monitor    "SYNAPS, Composite, DPMS"

    DefaultDepth 24



    Subsection "Display"

        Depth      8

        Modes      "1600x1200" "1280x1024" "1024x768"

        ViewPort    0 0

    EndSubsection

    Subsection "Display"

        Depth      16

        Modes      "1600x1200" "1280x1024" "1024x768"

        ViewPort    0 0

    EndSubsection

    Subsection "Display"

        Depth      24

        Modes      "1600x1200" "1280x1024" "1024x768"

        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

Do I run xorsetup as root or user? Maybe all I need is to enter Display Demensions and an accurate modeline? Thanks you guys are great.

run 'xorgsetup' as root, while X is not running.

Quote:

Warning!
# Horizontal sync frequency below minimum of 79.976kHz!
# Horizontal sync frequency above maximum of 31.475kHz!
# Refresh rate below minimum of 75.024Hz!

It might just be that you need to set more exact horiz and vert refresh rates. So maybe change it to this:

HorizSync 31.475 - 79.976
VertRefresh 59.9 - 75.024

Or round them up rather than down.

My optimal 1600x1200 @
Horizontal Frequency 75.00KHz
Vertical Frequency 60.00Hz
I will try your suggestions. Thanks

How do I revert to xorgconfig backup file?

Quote:

Originally Posted by H_TeXMeX_H (Post 2962848)

run 'xorgsetup' as root, while X is not running.

Ran 'xorgsetup' as root and monitor artifacts increased at the startup of xfce.

Can u tell me how to revert to previous xorgconfig
file(backup file). Thanks

1) Kernel compilation is not related to X.
2) Check /etc/X11 for xorg.conf~ or smth similar

Code:

cd /etc/X11

ls

There should be an 'xorg.conf.backup'.

You can also try xorgconfig but I recommend setting things manually.

Hi NightSky,

The xorg.conf that you posted had two device sections, one stating the driver was "vga" the other said "r128"
I think "r128" is the correct one, and personally I would comment out or remove the reference to vga in case the wrong driver is getting loaded.
You could check that the correct driver is being loaded (and for errors) by looking at /var/log/Xorg.0.log

tobyl

How do I change it back?

Quote:

Originally Posted by H_TeXMeX_H (Post 2963821)

There should be an 'xorg.conf.backup'.

I am qcommandline beginner user.*

There is an xorgconfig backup file, but I don't know how to change it back? Please explain, like this:

1. Find the path in XFCE GUI
2. Logout of GUI
3. commandline su root
4.

Code:

 cd /etc/X11/xorg.conf

? 5. vi xorg.conf ?

? 6. delete the backup extension and replace it with what?

? 7. delete current xorgconfig ?

? 8. :wq ?

tobyl: "r128" is the correct driver for my video card.

I thought the following section is just for discriptive purposes?
# Graphics device sections:
# Standard VGA Device:"
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Is the above just a discriptive example, automatically generated?

Should I remove # from videoram and what are clock lines?
# Device configured by xorgconfig:

Section "Device"
Identifier "ATI RAGE 128 PRO, 32M, AGP"
Driver "r128"
#VideoRam 32000 (remove # ..?)
# Insert Clocks lines here if appropriate (What are clock lines?)
EndSection

NightSky,

Lines beginning with # and whitespace are ignored, so you effectively have

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Driver "vga"
EndSection

Section "Device"
Identifier "ATI RAGE 128 PRO, 32M, AGP"
Driver "r128"
EndSection

I believe the last entry will be the one thats used anyway, but its a good idea to keep things clean and simple, so comment out with # the entries you dont want.
The video memory entry is commented out by xorgconfig on purpose.You only need to uncomment it if the system reads the amount of video ram incorrectly

If you want to change a file's name from the command line, you use the mv command, something like this

su (root)
cd /etc/X11
mv xorg.conf xorg.conf.old
mv xorg.conf.backup xorg.conf

tobyl

edit: i'm not sure if Vendorname and Boardname are required entries or not (i doubt it) but in any case you can write whatever you like for those entries. Some xorg config programs interrogate the video card and put entries in there, but they are basically just informational if you only have one video card.

edit2:
Ok, one more thing, if you want to edit files from the command line, but are not used to vi or vim, it is just too much to master right now, you can learn that later. Instead use nano. Eg
(as root)
# nano /etc/X11/xorg.conf

its as easy as notepad! (ctrl+x to exit)

Super Thanks, I am comfortable using Vi with Old Slackware Book instructions.
I am commands defficient.

Commenting out: Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Driver "vga"
EndSection ---> resulted in no screen error...
Added video crd info and StartX worked. 1/4"-1/2" color artifact band across top of display persists. Found Display EE and WW - how do I fix them? Thanks

Code:

 

cat /var/log/Xorg.0.log



(II) Setting vga for screen 0.

(II) R128(0): PCI bus 1 card 0 func 0

(**) R128(0): Depth 24, (--) framebuffer bpp 32

(II) R128(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)

(==) R128(0): Default visual is TrueColor

(II) Loading sub module "vgahw"

(II) LoadModule: "vgahw"

(II) Loading /usr/lib/xorg/modules//libvgahw.so

(II) Module vgahw: vendor="X.Org Foundation"

        compiled for 1.3.0, module version = 0.1.0

        ABI class: X.Org Video Driver, version 1.2

(II) R128(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000

(==) R128(0): RGB weight 888

(II) R128(0): Using 8 bits per RGB (8 bit DAC)

(II) Loading sub module "int10"

(II) LoadModule: "int10"

(II) Loading /usr/lib/xorg/modules//libint10.so

(II) Module int10: vendor="X.Org Foundation"

        compiled for 1.3.0, module version = 1.0.0

        ABI class: X.Org Video Driver, version 1.2

(II) R128(0): initializing int10

(II) R128(0): Primary V_BIOS segment is: 0xc000

(--) R128(0): Chipset: "ATI Rage 128 Pro ULTRA TF (AGP)" (ChipID = 0x5446)

(--) R128(0): Linear framebuffer at 0xd4000000

(--) R128(0): MMIO registers at 0xd9000000

(--) R128(0): VideoRAM: 32768 kByte (128-bit SDR SGRAM 1:1)



(**) R128(0): Using external CRT for display -->? Problem? Using FlatPanel ?

(II) R128(0): Primary Display == Type 3

(WW) R128(0): Can't determine panel dimensions, and none specified.-->? Problem?

        Disabling programming of FP registers. --> ? 411 310 display size 

(II) R128(0): PLL parameters: rf=2950 rd=65 min=12500 max=35000; xclk=12000

(II) Loading sub module "ddc"

(II) LoadModule: "ddc"(II) Module already built-in

(II) Loading sub module "vbe"

(II) LoadModule: "vbe"

(II) Loading /usr/lib/xorg/modules//libvbe.so

(II) Module vbe: vendor="X.Org Foundation"

        compiled for 1.3.0, module version = 1.1.0

        ABI class: X.Org Video Driver, version 1.2

(II) R128(0): VESA BIOS detected

(II) R128(0): VESA VBE Version 2.0





(II) R128(0): Max H-Image Size [cm]: horiz.: 41  vert.: 31 -> 

(II) R128(0): Gamma: 2.





(EE) R128(0): No DFP detected --> What is DFP? --> ?Problem?

(II) R128(0): SYNAPS, Composite, DPMS: Using hsync range of 31.00-79.00 kHz

(II) R128(0): SYNAPS, Composite, DPMS: Using vrefresh range of 59.00-75.00 Hz

(II) R128(0): Clock range:  12.50 to 350.00 MHz





Setting up tile and stipple cache:

                32 128x128 slots

                19 256x256 slots

(II) R128(0): Acceleration enabled

(==) R128(0): Backing store disabled

(==) R128(0): Silken mouse enabled

(II) R128(0): Using hardware cursor (scanline 14412)

(II) R128(0): Largest offscreen area available: 1600 x 1198->? Problem 1600x1200

(II) R128(0): X context handle = 0x1

(II) R128(0): [drm] installed DRM signal handler

(II) R128(0): [DRI] installation complete

(II) R128(0): [drm] Added 128 16384 byte vertex/indirect buffers

(II) R128(0): [drm] Mapped 128 vertex/indirect buffers

(II) R128(0): [drm] dma control initialized, using IRQ 11

(II) R128(0): Direct rendering enabled







drmOpenDevice: node name is /dev/dri/card0

drmOpenDevice: open result is 10, (OK)

drmOpenByBusid: Searching for BusID pci:0000:01:00.0

drmOpenDevice: node name is /dev/dri/card0

drmOpenDevice: open result is 10, (OK)

drmOpenByBusid: drmOpenMinor returns 10

drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0

(WW) AIGLX: 3D driver claims to not support visual 0x23

(WW) AIGLX: 3D driver claims to not support visual 0x24

(WW) AIGLX: 3D driver claims to not support visual 0x25

(WW) AIGLX: 3D driver claims to not support visual 0x26

(WW) AIGLX: 3D driver claims to not support visual 0x27

(WW) AIGLX: 3D driver claims to not support visual 0x28

(WW) AIGLX: 3D driver claims to not support visual 0x29

(WW) AIGLX: 3D driver claims to not support visual 0x2a

(WW) AIGLX: 3D driver claims to not support visual 0x2b

(WW) AIGLX: 3D driver claims to not support visual 0x2c

(WW) AIGLX: 3D driver claims to not support visual 0x2d

(WW) AIGLX: 3D driver claims to not support visual 0x2e

(WW) AIGLX: 3D driver claims to not support visual 0x2f

(WW) AIGLX: 3D driver claims to not support visual 0x30

(WW) AIGLX: 3D driver claims to not support visual 0x31

(WW) AIGLX: 3D driver claims to not support visual 0x32

(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/r128_dri.so

(II) GLX: Initialized DRI GL provider for screen 0

Let's try something a little exciting and progressive, even if we are using Slackware.

Backup your /etc/X11/xorg.conf.

As root, run `xorgcfg`.

With a display panel like that, and a reasonably recent video card (AGP you say? Should be good enough) there's a more than moderate chance that X will be able to probe both the card, and the display, and in a few moments you'll likely see a stick-figurish representation of your hardware arrangement and things will "just work".

The best part is that even if it doesn't work, you only blew about 60-90 seconds trying it.

Good luck with evilDagmar's suggestion, I have never tried that.

Does your graphics card have a dvi output, or just vga? dvi is preferable if it is available and might fix the problem.
Also, you may want to investigate the displaysize option in the monitor section of xorg.conf

heres a useful link:

http://www.x.org/wiki/FAQVideoModes

tobyl

edit:
Ok I worked it out for you :-)
if your monitor's dot pitch is correctly reported as .258 (vert & horiz), then at 1600x1200 I get 412.8 x 309.6
rounded down to the nearest mm gives (1st entry in section "Monitor")

DisplaySize 412 309

xorgcf direction needed

Quote:

Originally Posted by evilDagmar (Post 2965202)

Tried 'xorgcf' and go stuck on black screen because I did not know how to navigate the options and selection on the small box. Would I just run probe command in that application?
I had to shutdown the pc and booted into windows to post this question: can u give me a little more direction on using xorgcf?

Tobyl, only vga connector on the back. Thanks

I know when I couldn't get X configured I copied a working version of xorg.conf from Mandrake! The vesa driver didn't work for me. But it might be best if you run xorgsetup again as root, and if it doesn't work, check the error log to see why. It depends how messy your xorg.conf has become. Also, what does 'artifacts' refer to?

simcox1, by artifacts I am referring something that looks like video noise in colors white,black,blue and now its more red... like when you switch your tv channel from cable 3 to none recieving channel...lol One thing about xorgcfg is that it did have the easy option for display size but can you save setting from that application to xorconfig file and how? Going to look at my xorgcongfig file now. My video card only has vga connector. My mobo
is PC100. My just delete xorgconfig file and start over. Already ran xorgsetup but it requires you still config
xorgconfig by hand. Thanks

Nightsky,

did you try my
DisplaySize 412 309

suggestion?

tobyl

Looking for the right format xorgconf file... it will stop working and spit out a "Parsing Error" if format doesn't match.

Tried putting writing to monitor section "Display Size" but startx would not accept it
generated "Parsing Error". Do you have a Display Size in your xorgconf file? Getting fed up.. Goto my Help With Cups Thread Now. lol If I can accomplish one thing to recharge my motivation.

I don't seem to need a DisplaySize in my xorg.conf as the monitor reports its dimensions ok, but I tried it anyway, and it worked (athough I used different dimensions as my screen is different to yours).
The syntax is simply

DisplaySize 412 309

no quotes, no space in the word DisplaySize (but note the capitalization)
If that doesn't work, it would be interesting to see the xorg log, if it gets that far...

tobyl

Tobyl, where exactly did you place your entry? Within Section Monitor? I will try again now. I have been re-reading the X5, Xorg.con-Configuration File and according to that information I should be able to include an 'Auto Option' Allowing the monitor auto feature to run,U think?
Reasoning being this: "(WW) R128(0): Can't determine panel dimensions, and none specified. Disabling programming of FP registers." from /var/log/Xorg.0.log

yes, I put it as the first entry in section Monitor.
I'm not familiar with the Auto option you describe, could you elaborate?

Quote:

"(WW) R128(0): Can't determine panel dimensions, and none specified. Disabling programming of FP registers."

It is this entry in your log that has prompted my suggestions up to now. My reasoning being, if no panel dimensions are determined and none specified, then we should specify them ourselves...

The DisplaySize command is not foolproof, there are many examples if you google, of people complaining that it is ignored, (probably driver dependent), but we can try it. A parsing error as you suggest, is most likely a syntax error. If we get the syntax right, then the log may reveal more...

tobyl

tobyl, I so appreciate your consistent support, you're a find. Good news, I was able to get xorg.conf file to accept DisplaySize Entry and it shows up in the middle of /var/log/Xorg.0.log but so does the inital warning you quoted above.
The band across top of my monitor is intermittent and not as wide now.
What I mean by Setting an 'Auto Adjust Option' for monitor is that this monitor does not run on software driver, it self adjusts...In windows all I had to do was set the desktop resolution to 1024x768 and refresh
rate to 60Hz before disconnecting the CRT and Pluging this one in. It has an OSD Menu and ABT light reading Sensor so it can auto adjust brightness. So far all worked well so I never do any manual adjusting. Probably will get into that if I can ever switch over and start doing some web graphics.
So I was wondering if there is some way to set xorg.conf to just let monitor do its thing? And yes I noticed "bug posts related to DisplaySize in Xorg", but it is confusing because there are so many hardware and configuration options. I promise to dedicate a plain english site for slackware if I ever get it all working. [Still no printer, paper feed turns on everytime i start and shut off pc ??? Tried installing some package and have no clue what I did.]

Nightsky,

As far as I know there are two ways that X gets its info. If the monitor sends EDID info (ie screen dimensions, timings etc), and the driver can interpret it, then it can be setup automatically. Otherwise, we have to give a bit of extra help in the xorg.conf file.

Your monitor is not sending this information. Whether there is an option in your monitor OSD to change that, I don't know, but I doubt it.

So we have to work out what to tell Xorg to get a good working configuration. Our problem is compounded by the fact that your graphics card is a little on the old side, and the linux driver development for r128 is probably not getting attention anymore.

The options open to you that I can think of are
1.Play around with the DisplaySize settings, maybe reducing the vert size by a small amount

2.Try using a lower resolution. Actually, if a lower res works and fills you screen correctly, run

$ xdpyinfo |grep dimensions

it should give the correct dimensions for your DisplaySize parameter

3. Try temporarily disabling module DRI from xorg.conf (google tells me this worked for another ati rage user) just to see if it makes a difference.

4.Try generating a modeline again (gtf is one way to do this, type at the prompt:

$ gtf 1600 1200 60

5.Try using the slightly scary xvidtune (better read up on it before doing this one, I have never used it)

6.Splash out on a new graphics card (You could get a midrange Nvidia card pretty cheap, and they are much better supported in Linux and you would really be glad you did) AGP cards are still easy enough to find, or you could get one from ebay for a few dollars) or cadge one off a friend who has just upgraded :-)

that little lot should keep you busy - I am sure it can be done, its just a matter of how much time/patience you have

tobyl

Thanks tobyl, Will try your suggestions. Actually this ATI Rage card is a replacement for a agp nvidia geForce, I did try to get another agp Nvidia Card, got this one through ebay. I just rebuilt a box for my neighbor will check to see their video card. Thing is if I can get this slackware12 to where I need it to be 'the graphics' is not top priority for web/file server and I have a new XP Build. This Slackware Box is dualboot w/win98 I would like to migrate to slackware, but so far Win98 is much faster than slackware12 and stable for my online usage, just downloaded adobe flash player, it installed successfully. I would feel alot more secure with my online functions running in slackware12, I don't want to run XP online unless its through slackware server. Tall order???
Started to use xvidtune but decided against it after its warning about breaking the monitor ;) lol not worth the risk for me.

tobyl, From command line outside of Xfce I tried code:$ xdpyinfo |grep dimensions and got Can not open window /code

Fireded up Xfce, openned terminal code:$xdpyinfor |grep demensions and got back nothing. Tried same code as root with same results./code Maybe a syntax error on my part? Oh, missed you saying to change res and then do the |grep,
have to do that.

Question: Would displaysize belong in Screen Section? This info. was requested for screen section in xorgcf tool if I remember correctly. hmmm

Can I compile kernel although I don't have everthing settup yet,ie. Display and printer?

code:$gtf 1600 1200 60
1600x1200@60.00Hz (GTF) hsync: Modeline 74.52KHz; pclk: 160.96MHz
Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +VSync
(These numbers look high? My monitor doesn't go above 1600x1200? What do you think? Where do I place the modeline? Will look it up too. Thanks

Nightsky,

Quote:

From command line outside of Xfce

If you didn't have X running then xdpyinfo hasn't got anything to look at!

From within X it should work, check your typing...
(I only said to try a lower res as I am not sure if xdpyinfo would give the correct numbers when your fault is in evidence)

DisplaySize goes in section Monitor. Haven't tried it elsewhere.

Quote:

Can I compile kernel although I don't have everthing settup yet,ie. Display and printer?

yes.

Quote:

These numbers look high? My monitor doesn't go above 1600x1200

The big numbers refer to clock timings not pixels

Put the line in section Monitor again (Disable the DisplaySize parameter with a # for now)
All of it just like this:

Section "Monitor"
Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +VSync

tobyl

edit: oops I forgot something

you should also change the line in section Screen
under your default depth to
Modes "1600x1200_60.00" "1600x1200" "1280x1024" "1024x768"

to tryout the modeline thing.

tobyl, Thank you so much. I added the modeline, edited Section Screen: default depth line, removing "Dri" or "GLX" just created errors on shutdown, and finally changed the HorizSync to the more precise 31.475-79.976, as well change VertRefresh 59.9-75.024 and Xfce starts with a little more delay in black and much more stable colored start screen, so I am happy. Sorry it took so long to respond, I have been working on setting up my printer, yuk!

Bad news is the new shutdown errors:

"Failed to shutdown GConf daemon on logout: Failed to execute child process ""gconftool-2"(No such file or directory) Agend pid 3238 Killed"

"Waiting for Xserver to shutdown Xfce-mcs-manager: Fatal I0 error 11 (Resource-temporarily unavailable) on Xserver :0:."

"Free Font Path:FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing." It always says its fixing but doesn't apparently.

Also, do you know how to get rid of Xscreensaver error related to permission during startup and shutdown from Xfce?

Hi Nightsky,

Glad you got you display working ok.

As for the shutdown errors:

Quote:

"Failed to shutdown GConf daemon on logout: Failed to execute child process ""gconftool-2"(No such file or directory) Agend pid 3238 Killed"

I guess you don't have gconf2 installed. It doesn't come as default with Slackware as I think it is mainly a gnome thing.
You can install it if you wish, (you do not have to have gnome installed) you can get it (plus its dependencies) at http://www.slackbuilds.org/

slackbuilds.org is a superb way to build & install packages that are not native to Slackware, yet have been contributed by Slackware experts who know what they are doing. It is a site endorsed by Pat Volkerding. There is a small learning curve, but all you need to know is on the site.

I am wondering if you have "Load Gnome services at Startup" in the Sessions and Startup section of XFCE config, which you may not require, however I can't test that for you as I have gconf2 installed.

Quote:

"Waiting for Xserver to shutdown Xfce-mcs-manager: Fatal I0 error 11 (Resource-temporarily unavailable) on Xserver :0:."

I get this too, doesn't seem to have any adverse effects, I think you can safely ignore it

Quote:

"Free Font Path:FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing."

I get this too, I have investigated this extensively for myself, and failed to find a fix :-(

Quote:

Also, do you know how to get rid of Xscreensaver error related to permission during startup and shutdown from Xfce?

I get this too! I have looked for a solution, I believe it is an XFCE problem as kde doesn't suffer from it, but if xscreensaver is working, probably not worth wasting time worrying about it. I think it is related to the shadow group, but maybe someone else can comment on this.

If those are your worst problems, you are doing ok. Other operating systems have as many or more errors, they just don't tell you about them. If you don't want to be bothered by them, why not boot straight into XFCE?

Just change /etc/inittab from

# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:

# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:

Another way is to have two /etc/lilo.conf entries (I do this)

Leave inittab at id:3:initdefault:

then in lilo.conf

image = /boot/vmlinuz
root = /dev/sda1
label = Slack
append = 4
read-only

image="/boot/vmlinuz"
root="/dev/sda1"
label= Slack-console
read-only

the 'append = 4' overrides inittab to boot straight into your chosen xwmconfig choice, but the second stanza will respect inittab, and leave you at the command line, where you can type startx etc.
Of course, the label is your choice. *Don't copy my entries - they are just an example, keep your own image and root definitions*. If you choose to modify lilo.conf, you need to run lilo (as root) afterwards.

tobyl

tobyl, thanks
I too have researched the 'Xscreensaver error related to permission during startup and shutdown from Xfce' All I could find out is that: Xscreensaver for some reason starts up as root and then switches to usr - but I could not find any solution -except maybe in the Xfce initscript which I have not a clue as to the what the proper settings needed.

I don't have gnome, but do have gnome desktop themes I did try and then reverted to the regular Xfce theme. If this is as good as it gets I would like to figureout how to get MY Documents and Firefox Bookmarks backup and onto slackware12 so I can go ahead and remove win98 from my first hde1 and install slackware12 on it as my main distro for this old box. Once Slackware12 is by itself I will run init at runlevel4.

I just have to learn how to get one of my printers working before I make that move because I print out everything from forum responses to online manuals for everything I do. lol

Really enjoyed working with you to get Xorgconf workng with this old ATI r128 video card.

toby, I wiped out my second hard drive and fdisked my 1st hdd removing windows98 finally. So Slackware12 is my only distro on this box now.
Did the inittab 4runlevel and did not have any xorg.conf problems. Now I just have to install whatever software I want to use in Xfce and configure the network. Thanks so much

great, I'm glad you got it all sorted out.
I assume you got your printer going too. If not, bump your printer thread, and I will try and help there too.

regards, tobyl

For xscreensaver error maybe xhost +localhost could help. I've patched xscreensaver and recompiled, but later it was updated and I don't remember now what i've done.