View previous topic :: View next topic |
Author |
Message |
gsnerf n00b
Joined: 11 Nov 2003 Posts: 32
|
Posted: Tue Nov 02, 2004 10:30 pm Post subject: Probleme mit Grafik und gdm |
|
|
Hi leute,
nachdem ich von xfree auf xorg 6.8 umgestiegen bin hab ich 2 Probleme:
1. Ab und zu bekomm ich beim starten von gdm die Meldung das der "greeter anscheinend abgestürtzt" sei und er deshalb der standartgreeter gestartet würde. Wenn ich den XDPM chooser (oder so ähnlich) starte und wieder abbreche dann startet der greeter einwandfrei.
2. Die hardware unterstüzung für GL funzt nicht mehr. Wenn ich meine GL-Screensaver ect laufen lasse hab ich ne nette ruckelparty die nach Softwarerendering schreit.
Hier mal meine xorg.conf:
Code: | 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"
# This loads the touchpad
Load "synaptics"
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/"
FontPath "/usr/share/fonts/corefonts"
# 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 "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" "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 "XkbVariant" "nodeadkeys"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
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
Section "InputDevice"
Driver "synaptics"
Identifier "Touchpad"
Option "CorePointer" ""
Option "Device" "/dev/input/event0"
Option "Protocol" "ImPS/2"
Option "MaxTapTime" "300"
# Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.02"
Option "MaxSpeed" "0.18"
Option "AccelFactor" "0.0010"
Option "SHMConfig" "on"
Option "Repeater" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "UpDownScrolling" "on"
Option "Edges" "1900 5400 1800 3900"
Option "Finger" "25 30"
Option "Emulate3Buttons"
Option "Emulate3Timeout" "50"
EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Monitor0"
# 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 30 - 60
# 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 20 - 60
Option "DPMS"
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 "** Intel i810 (generic) [i810]"
Driver "i810"
VideoRam 65536
Screen 0
Option "RenderAccel" "1"
# 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 0"
Device "** Intel i810 (generic) [i810]"
Monitor "Monitor0"
DefaultDepth 24
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 "Server 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 0"
# 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 "Touchpad" "SendCoreEvents"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
EndSection |
So, nu zerreist mich meiner wahrscheinlichen Dummheit und zeigt mir den billigen Fehler auf den ich gemacht hab
greetz gsnerf
PS: fast vergessen, ich hab hier nen BenQ Joybook (Notebook) mit integriertem intel Grafikchip. Das Synaptics zeug da in der conf ist mein Touchpad. |
|
Back to top |
|
|
gsnerf n00b
Joined: 11 Nov 2003 Posts: 32
|
Posted: Wed Nov 03, 2004 11:27 am Post subject: |
|
|
Hat wirklich keiner ne Idee?
Ich hab sonst nix direkt dazu gefunden (vor allem zum gdm Problem)
Ihr die Ahnung habt bitte meldet euch
greetz gsnerf |
|
Back to top |
|
|
ralph Advocate
Joined: 02 Mar 2003 Posts: 2001 Location: Hamburg
|
Posted: Wed Nov 03, 2004 11:35 am Post subject: |
|
|
Also ich habe zwar keine Ahnung, aber ich melde mich trotzdem mal. Ich bilde mir ein, dass 3d Beschleunigung bei diesen Karten nur bei 16bit Farbtiefe funktioniert.
Wie gesagt, ich bin mir da alles andere als sicher, aber du kannst es ja einfach mal ausprobieren. _________________ The computer can't tell you the emotional story. It can give you the exact mathematical design, but what's missing is the eyebrows.
- Frank Zappa |
|
Back to top |
|
|
J.M.I.T. Guru
Joined: 15 Jan 2003 Posts: 481 Location: München, Germany
|
Posted: Wed Nov 03, 2004 1:49 pm Post subject: |
|
|
Wirds besser, wenn du die Composite Extension wieder raus nimmst? Die frisst ziemlich viel CPU...
und was sagt glxinfo? direct rendering = YES/NO?? _________________ Get a life...
Use at own risk... |
|
Back to top |
|
|
amne Bodhisattva
Joined: 17 Nov 2002 Posts: 6378 Location: Graz / EU
|
Posted: Wed Nov 03, 2004 7:19 pm Post subject: |
|
|
gsnerf wrote: | Hat wirklich keiner ne Idee?
|
Mit dem Bumpen bitte mindestens 24h warten, danke. _________________ Dinosaur week! (Ok, this thread is so last week) |
|
Back to top |
|
|
gsnerf n00b
Joined: 11 Nov 2003 Posts: 32
|
Posted: Wed Nov 03, 2004 9:42 pm Post subject: |
|
|
amne wrote: | Mit dem Bumpen bitte mindestens 24h warten, danke. |
Sorry hab beim posten nicht wirklich realisiert wie wenig zeit vergangen ist
Habs vorm ins Bett gehen gepostet und in der Uni dann nochmal da verliert man schonmal den Überblick
Ok zurück zum Thema:
J.M.I.T. wrote: | Wirds besser, wenn du die Composite Extension wieder raus nimmst? Die frisst ziemlich viel CPU...
und was sagt glxinfo? direct rendering = YES/NO?? |
glxinfo sagt "direct rendering = no" allerdings liefen zumindest die glscreensaver mit xfree ohne zu murren 1a, erst seit xorg ist das die reinste ruckelparty
Auflösung und Farbtiefe haben sich seit xfree auch nicht geändert also _sollte_ es nicht daran liegen.
Ok nun nochmal angenommen das ganze lief schon unter xfree software gerendert. Da ich an meinem System nur xfree zu xorg geändert habe würde das bedeuten xorg bremst das system so krass aus das die screensaver zu einer ruckelparty werden? Ist xorg wirklich SO Leistungshungrig??
Naja ich hab das Composite nun mal rausgehauen und werde x neu starten, wenns klappen sollte meld ich mich, wenn nicht wart ich auf weitere Eingebungen
greetz Micad |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|