| View previous topic :: View next topic |
| Author |
Message |
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
 Posted: Mon Oct 20, 2008 7:17 pm Post subject: After new mobo, startx fails with ati-drivers |
 |
|
I used ati-drivers somewhat successfully on an old motherboard (the "somewhat" being because I couldn't get proper 3D acceleration in games under wine, but that's a different issue). However, due to an unrelated problem, I now have a new motherboard: an MSI K9A2v2. Now, on boot, if I run 'startx' it quits out to the console, gives me errors:
| Code: | (WW)fglrx: No matching Device section for instance (BusID 03:00:0) found
(WW)fglrx: More than one matching Device sections for instance (BusID 04:00:0) found |
Alas! Like a nitwit I followed the suggestion at the phoronix forum, and just ran 'aticonfig --initial'. Now I suspect my xorg.conf is hosed, giving the above error. I also get | Code: | | Could not find device entity for slave adapter |
a couple lines below that. However, there are no (EE) flags on anything.
Here is my xorg.conf, as built/garbled by aticonfig:
| Code: |
# $XdotOrg$
#
# Copyright (c) 1994-1998 by The XFree86 Project, Inc.
#
# 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 XFREE86 PROJECT 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 XFree86 Project 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
# XFree86 Project.
#
# $XConsortium: XF86Conf.cpp /main/22 1996/10/23 11:43:51 kaleb $
# **********************************************************************
# This is a sample configuration file only, intended to illustrate
# what a config file might look like. Refer to the XF86Config(4/5)
# man page for details about the format of this file. This man page
# is installed as MANPAGE
# **********************************************************************
# The ordering of sections is not important in version 4.0 and later.
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Module section -- this is an optional section which is used to specify
# which run-time loadable modules to load when the X server starts up.
# **********************************************************************
# **********************************************************************
# Server flags section. This contains various server-wide Options.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
#Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
#EndSection
# Some examples of extended input devices
# 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
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
##################
#
#Enable dri permissions
###################
# **********************************************************************
# 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.
# **********************************************************************
# 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.
# The Identifier line must be present
# 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.
# 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". In this example, "Mouse1" is the core pointer,
# and "Mouse2" is an extended input device that also generates core
# pointer events (i.e., both mice will move the standard pointer).
# InputDevice "Mouse2" "SendCoreEvents"
###################
# Enable AIGLX - for compiz
####################
Section "ServerLayout"
Identifier "Main Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
Screen "aticonfig-Screen[0]-0" RightOf "aticonfig-Screen[0]-0"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
Option "AIGLX" "Enable"
EndSection
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)
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
ModulePath "/usr/lib64/xorg/modules"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules/extensions"
ModulePath "/usr/lib64/xorg/modules/drivers"
FontPath "/usr/share/fonts/local"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
EndSection
Section "Module"
# This loads the DBE extension module.
# initialisation of the XFree86-DGA extension within that module.
# This loads the Type1 and FreeType font modules
Load "dbe"
# This loads the miscellaneous extensions module, and disables
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
Load "type1"
Load "freetype"
Load "glx"
Load "dri"
EndSection
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 "DontZoom"
# 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"
# Set the basic blanking screen saver timeout.
# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.
# Option "EstimateSizesAggresively" "0"
Option "blank time" "10" # 10 minutes
Option "standby time" "120"
Option "suspend time" "130"
Option "off time" "240"
# On some platform the server needs to estimate the sizes of PCI
EndSection
Section "InputDevice"
# Set the keyboard auto repeat parameters. Not all platforms implement
# this.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
# Option "XkbLayout" "de"
#
# or:
#
# 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" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 5"
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
Option "XkbModel" "pc105"
#
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
#
EndSection
Section "InputDevice"
# Identifier and driver
# The mouse protocol and device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.
# Option "Protocol" "Auto"
# protocol setting can be used when using a newer PnP mouse:
# the protocol as follows. On some platforms some other settings may
# be available.
# Option "Protocol" "PS/2"
# Baudrate and SampleRate are only for some older Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# 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, or any
# 3-button mouse where the middle button generates left+right button
# events.
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/input/mice"
# On platforms where PnP mouse detection is supported the following
Option "Protocol" "Auto"
# When using mouse connected to a PS/2 port (aka "MousePort"), set the
Option "Emulate3Buttons" "false"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "EAH4870X2"
Driver "fglrx"
BusID "PCI:4:0:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:3:0:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "EAH4870X2"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "enable"
EndSection
|
Thanks for the help!
EE |
|
| Back to top |
|
 |
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Tue Oct 21, 2008 4:30 am Post subject: |
|
|
| Did you rebuild your kernel with the correct chipset of the new mobo? |
|
| Back to top |
|
|
fangorn
Veteran
Joined: 31 Jul 2004
Posts: 1886
|
| Posted: Tue Oct 21, 2008 5:54 am Post subject: |
|
|
| Code: | Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:3:0:0"
EndSection
|
make sure that BusID is correct!
lspci | grep -i VGA
should give you the device in the first column.
_________________
Video Encoding scripts collection | Project page |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Tue Oct 21, 2008 6:09 am Post subject: |
|
|
lspci returns two VGA cards; as this is a dual-core card, this seems plausible. They reside at PCI 03:00.0 and 04:00.0, respectively. There is, as you can see, a small discrepancy in the format of the numbers, but I assume this is trivial. In any case, that is an apparently correct ID. Is there something I should be doing with the identifiers to name and use the two cores differently?
Thanks,
EE |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Tue Oct 21, 2008 10:07 pm Post subject: |
|
|
Thanks for the tip. Unfortunately, his problem was just the wrong defaultdepth setting. I'm not getting any fatal errors. In fact, I'm not getting any errors at all. It just ... won't startx. For some reason.
Thanks,
EE |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Wed Oct 22, 2008 12:44 am Post subject: |
|
|
Have you tried using a default Xorg config file?
| as root: | cd
X -configure
X -config /root/xorg.config.new |
What happens if you try that? |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Wed Oct 22, 2008 11:51 am Post subject: |
|
|
I get the following:
| Code: | Build Date: 14 October 2008 07:42:27AM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 22 13:48:54 2008
List of video drivers:
nvidia
fglrx
nv
(EE) module ABI major version (4) doesn't match the server's version (2)
(EE) Failed to load module "nv" (module requirement mismatch, 0)
Backtrace:
0: X(xf86SigHandler+0x6a) [0x486b7a]
1: /lib/libc.so.6 [0x7fcfa722d5a0]
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxProbeMain+0x87e) [0x7fcfa628bdbe]
3: X(DoConfigure+0x1d9) [0x478949]
4: X(InitOutput+0x866) [0x46b656]
5: X(main+0x2c6) [0x437256]
6: /lib/libc.so.6(__libc_start_main+0xf4) [0x7fcfa721a4a4]
7: X(FontFileCompleteXLFD+0x289) [0x4366f9]
Fatal server error:
Caught signal 11. Server aborting
|
Obviously I need to fix some config files. Advice? Sorry: I've been using nVidia for so long, I forgot how to write an xorg.conf for anything else.
Thanks |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Wed Oct 22, 2008 3:26 pm Post subject: |
|
|
The obvious place to start is unmerging nvidia stuff,
check /etc/make.conf VIDEO_CARDS,
check kernel config,
look here for ideas,
run eselect opengl list/set |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Wed Oct 22, 2008 11:17 pm Post subject: |
|
|
| removed nvidia from all the relevant places, rebuilt xorg-server, tried again, and got the same error. |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Thu Oct 23, 2008 12:07 am Post subject: |
|
|
| Ok, then my previous question remains, unless your new mobo is the exact same as the old one, did you rebuild your kernel to reflect the hardware changes? |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Thu Oct 23, 2008 11:34 am Post subject: |
|
|
Well, I'm not exactly sure what hardware changes would affect the video card, but I went in and rebuilt the kernel anyway. Just for fun, I enabled the framebuffer, too. No change. The board is the same make (MSI) so the only thing that's changed is the North and South Bridge chips. Everything else is the same equipment. I get the same error message, about there being no Device section for PCI:3:0:0, despite the fact that there is.
X actually starts; I even saw the mouse cursor for a sec one time. But it quits back out, with the same odd non-errors.
Thanks,
EE |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Fri Oct 24, 2008 12:35 pm Post subject: |
|
|
after rebuilding xorg-server, I still get the same error, but slightly different:
| Code: | List of video drivers:
fglrx
nv
(WW) module ABI major version (4) doesn't match the server's version (2)
Backtrace:
0: X(xf86SigHandler+0x6a) [0x486b7a]
1: /lib/libc.so.6 [0x7fcfa722d5a0]
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxProbeMain+0x87e) [0x7fcfa628bdbe]
3: X(DoConfigure+0x1d9) [0x478949]
4: X(InitOutput+0x866) [0x46b656]
5: X(main+0x2c6) [0x437256]
6: /lib/libc.so.6(__libc_start_main+0xf4) [0x7fcfa721a4a4]
7: X(FontFileCompleteXLFD+0x289) [0x4366f9]
Fatal server error:
Caught signal 11. Server aborting |
So, the fglrx driver appears to be failing. Can you give some advice as to how to fix it?
Thanks,
EE |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Fri Oct 24, 2008 3:27 pm Post subject: |
|
|
Run this after emerging xorg-server | Code: | | emerge -av $(qlist -IC x11-drivers | awk -F/ '{ print $2 }') |
|
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Fri Oct 24, 2008 3:59 pm Post subject: |
|
|
That command lists and re-installs any x11-drivers, yes? I did that, to no avail.
Thanks,
EE |
|
| 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
|
|
Desktop Environments
