PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Slackware 9 - Fehler beim X11-Start (lang - config dabei)



_-=Unreal=-_
07.01.04, 09:47
hallo,

ich hab eine radeon 9600 pro graka, aber das teil funktioniert weder mit dem generic ati-radeon-, noch mit dem vesa-treiber (3d ist erstmal wurscht, daher kann ich vorläufig auch den nehmen)

beim starten von x11 kommt folgende meldung:


...
(==) Using config file: "/etc/X11/XF86Config"
(WW) RADEON: No matching Device section for instance (BusID PCI:2:0:1) found
(EE) No devices detected.

Fatal server error:
no screens found.

...

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.


hier meine XF86Config:


#
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),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

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

# ModulePath "/usr/X11R6/lib/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 <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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "deutsch"

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
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
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config 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 "tco"

# 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 - 82.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-100

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 "ati_radeon"
Driver "radeon"
#VideoRam 131072
# 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_radeon"
Monitor "tco"
DefaultDepth 16

Subsection "Display"
Depth 8
Modes "1280x1024" "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


ich hab zunächstmal alle screenmodes dringelassen, in der hoffnung es würde wenigstens ein 640x480 gehen...

nächstes problem ist, dass die maus nicht funktioniert. da hängt eine wireless optical mouse dran, (no-name, ms-kompatibel), die auf dem selben rechner unter suse9.0 als PS/2 - sysmouse an /dev/tty0 funktioniert.

vielleicht kann mir ja wer helfen!

gruss
peter

kadei
07.01.04, 16:34
mein freund:D

Mal ne frage, hast du dass tool "xf86config" schon aufgerufen ? und richtig konfiguriert?

Wenn ja , dann musst du noch in /etc/X11/XF86Config-4 was aendern.

<>
WW) RADEON: No matching Device section for instance (BusID PCI:2:0:1) found
(EE) No devices detected.

Fatal server error:
no screens found.
<>

sagt aus das er kein screen findet koennte daran liegen dass
a)sich in /etc/X11/XF86Config

diese zeilen gegenseitig nicht moegen

# Standard VGA Device:

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

mit

# Device configured by xf86config:

Section "Device"
Identifier "ati_radeon"
Driver "radeon"
#VideoRam 131072
# Insert Clocks lines here if appropriate
EndSection

-> ich wuerd mal die erste sektion ganz kommentieren

oder b)
was ich viel eher glaube

mach /etc/X11/XF86Config-4 auf da musst noch ein wenig rumschreiben.

Schau dir deine XF86Config-4 genau an , in dieser config findest du wo alles verkettet wird screen ,mouse usw.
da stimmt etwas nicht mit der XF86Config.


Leider kann ichs dir nicht sagen , sitze gerade 20 km von zuhause weg und diese x86 maschine hat Redhat drauf, der macht das mit Anaconda automatisch.

wenn ich wieder zu hause bin kann ichs dir sagen oder du kommst in #unixfreunde (<-drp bin ich->) , schickst mir schnell config und ich veraenders dir .(kann aber noch lange dauern)

so far.

core
07.01.04, 17:49
Also die Datei /etc/X11/XF86config wird verwendet - du musst nichts mit deiner -4 hinten dran machen...

Die beiden Devices dürften sich auch nicht gegenseitig stören, da in der Section Screen nur eine Device verwendet wird.
Um den Xserver erst mal zum laufen zu bringen, empfehle ich vorerst des VESA Treiber. der sollte auf jeden Fall Laufen... Gehe am besten so vor:

Deinen Radeon Eintrag änderst du erstmal wie folgt ab:



Section "Device"
Identifier "ati_radeon"
Driver "vesa"
#Driver "radeon"
#VideoRam 131072
#Insert Clocks lines here if appropriate
EndSection


Um die Radeon mit hardwarebeschleunigung zu verwenden brauchst du übrigens den fglrx Treiber von ATI. Der builtin radeon Treiber funktioniert nur mit einigen Radeon Boards, z.B. der 8500.

Also versuch das erstmal so, und dann schau mal hier vorbei, wenn dein Englisch ok ist:
http://www.linuxquestions.org/questions/showthread.php?s=&threadid=126958

Gruss


PS: um eine Flimmerfrei Auflösung zu erhalten, müsstest du noch deine Refreshrates erhöhen... (Bei nem Röhrenmonitor jedenfalls) Entweder siehe Handbuch des Monitors, oder:

Section "Monitor"
...
HorizSync 30-70
VertRefresh 50-120
..
EndSection


*edit* und Achja... Wenn das auch nichts bringt mit dem VESA Treiber, dann poste mal die relevante Ausgabe von /sbin/lspci -vvv

kadei
07.01.04, 17:52
hmm ich hatte aber bei slackware 8.0 arge probleme mit der **-4 conf.

core
07.01.04, 18:22
Name
XF86Config - Configuration File for XFree86
Description
XFree86 uses a configuration file called XF86Config for its initial setup. This configuration file is searched for in the following places when the server is started as a normal user:


/etc/X11/<cmdline>
/usr/X11R6/etc/X11/<cmdline>
/etc/X11/$XF86CONFIG
/usr/X11R6/etc/X11/$XF86CONFIG
/etc/X11/XF86Config-4
/etc/X11/XF86Config
/etc/XF86Config
/usr/X11R6/etc/X11/XF86Config.<hostname>
/usr/X11R6/etc/X11/XF86Config-4
/usr/X11R6/etc/X11/XF86Config
/usr/X11R6/lib/X11/XF86Config.<hostname>
/usr/X11R6/lib/X11/XF86Config-4
/usr/X11R6/lib/X11/XF86Config

where <cmdline> is a relative path (with no ".." components) specified with the -xf86config command line option, $XF86CONFIG is the relative path (with no ".." components) specified by that environment variable, and <hostname> is the machine's hostname as reported by gethostname(3) .

http://www.xfree86.org/4.3.0/XF86Config.5.html



_-=Unreal=-_ hat geschrieben:
...
(==) Using config file: "/etc/X11/XF86Config"

VonBroesel
08.01.04, 14:29
@unreal
Führe als root mal "lspci" aus. Schau dann mal was für eine BusID deine Grafikkarte hat. Dies muß dann mit dem Eintrag in der XF86config-4 identisch sein.

Susu
08.01.04, 14:37
Du kannst das "radeon"-Modul nutzen, wenn Du mittels ChipID eine andere Graka vortäuscht (einfach mal nach RADEON und CHIPID googlen!). Allerdings ist die 3D-Beschleunigung ziemlich bescheiden.

Besser ist es, wenn Du Dir den Treiber von ATI.com installierst. Auch dazu solltest Du genügend Anleitungen finden...

Susu

kadei
08.01.04, 15:15
bla, wusst ichs doch hat was mit XF86config-4 zu tun:D

_-=Unreal=-_
09.01.04, 09:36
@kadei:

ähm, eigentlich habe ich X11 mittels xf86config konfiguriert... und laut ausgabe benutzt er ja nicht die -4...

seltsam:
auf dem rechner läuft noch eine suse 9.0.
ich hab die xf86config mal genau nach der aus der suse konfiguriert, hat nichts gebracht - obwohl sämtliche einträge gleich waren. dann hab ich dreissterweise die config umbenannt und testhalber die suse-config benutzt, dann startete zumindest der xserver, nur die usb-mouse (/dev/mouse) hat nicht funktioniert, die musste ich auf /dev/psaux stellen.

würde mich mal interessieren, warum der xserver vorher nicht gestartet ist, obwohl ich unter xf86config dieselben einträge stehen hatte wie unter der suse ...

naja, zumindest läuft x11 jetzt, dafür darf ich jetzt mit der soundkarte kämpfen :ugly:

jedenfalls danke für die tips.