Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Mobo change = blank screen on startx

  1. #1

    Default Mobo change = blank screen on startx

    So, I have a nice Asus EAH4870X2, with 2GS of RAM, and 4GB on the mobo. I just upgraded the mobo to an MSI K9A2v2, with an AMD 6400+ 64-bit CPU. Prior to the upgrade, I only had the issue of the driver not compiling against the 2.6.27 kernel, which I circumvented by booting the 2.6.26 one. Now, after upgrading the mobo, startx (as called by gdm) gives me a blank screen. The computer remains responsive (I can even log in), just gives no video output.

    The Xorg.0.log file is attached. If anyone could advise on what the problem is, I'd appreciate it.

    Thanks!

    EE

    Xorg.0.log, minus previous startx stuff:
    Code:
    (II) Loading /usr/lib64/xorg/modules//amdxmm.so
    (II) Module amdxmm: vendor="X.Org Foundation"
    	compiled for 7.1.0, module version = 1.0.0
    	ABI class: X.Org Server Extension, version 0.3
    (WW) fglrx(0): Option "VendorName" is not used
    (WW) fglrx(0): Option "ModelName" is not used
    (II) fglrx(0): [DRI] installation complete
    (==) fglrx(0): Silken mouse enabled
    (==) fglrx(0): Using hardware cursor
    (==) RandR enabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension XAccessControlExtension
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 9, (OK)
    drmOpenByBusid: Searching for BusID PCI:4:0:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 9, (OK)
    drmOpenByBusid: drmOpenMinor returns 9
    drmOpenByBusid: drmGetBusid reports PCI:3:0:0
    drmOpenDevice: node name is /dev/dri/card1
    drmOpenDevice: open result is 9, (OK)
    drmOpenByBusid: drmOpenMinor returns 9
    drmOpenByBusid: drmGetBusid reports PCI:4:0: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
    (WW) AIGLX: 3D driver claims to not support visual 0x33
    (WW) AIGLX: 3D driver claims to not support visual 0x34
    (WW) AIGLX: 3D driver claims to not support visual 0x35
    (WW) AIGLX: 3D driver claims to not support visual 0x36
    (WW) AIGLX: 3D driver claims to not support visual 0x37
    (WW) AIGLX: 3D driver claims to not support visual 0x38
    (WW) AIGLX: 3D driver claims to not support visual 0x39
    (WW) AIGLX: 3D driver claims to not support visual 0x3a
    (WW) AIGLX: 3D driver claims to not support visual 0x3b
    (WW) AIGLX: 3D driver claims to not support visual 0x3c
    (WW) AIGLX: 3D driver claims to not support visual 0x3d
    (WW) AIGLX: 3D driver claims to not support visual 0x3e
    (WW) AIGLX: 3D driver claims to not support visual 0x3f
    (WW) AIGLX: 3D driver claims to not support visual 0x40
    (WW) AIGLX: 3D driver claims to not support visual 0x41
    (WW) AIGLX: 3D driver claims to not support visual 0x42
    (WW) AIGLX: 3D driver claims to not support visual 0x43
    (WW) AIGLX: 3D driver claims to not support visual 0x44
    (WW) AIGLX: 3D driver claims to not support visual 0x45
    (WW) AIGLX: 3D driver claims to not support visual 0x46
    (WW) AIGLX: 3D driver claims to not support visual 0x47
    (WW) AIGLX: 3D driver claims to not support visual 0x48
    (WW) AIGLX: 3D driver claims to not support visual 0x49
    (WW) AIGLX: 3D driver claims to not support visual 0x4a
    (WW) AIGLX: 3D driver claims to not support visual 0x4b
    (WW) AIGLX: 3D driver claims to not support visual 0x4c
    (WW) AIGLX: 3D driver claims to not support visual 0x4d
    (WW) AIGLX: 3D driver claims to not support visual 0x4e
    (WW) AIGLX: 3D driver claims to not support visual 0x4f
    (WW) AIGLX: 3D driver claims to not support visual 0x50
    (WW) AIGLX: 3D driver claims to not support visual 0x51
    (WW) AIGLX: 3D driver claims to not support visual 0x52
    (WW) AIGLX: 3D driver claims to not support visual 0x53
    (WW) AIGLX: 3D driver claims to not support visual 0x54
    (WW) AIGLX: 3D driver claims to not support visual 0x55
    (WW) AIGLX: 3D driver claims to not support visual 0x56
    (WW) AIGLX: 3D driver claims to not support visual 0x57
    (WW) AIGLX: 3D driver claims to not support visual 0x58
    (WW) AIGLX: 3D driver claims to not support visual 0x59
    (WW) AIGLX: 3D driver claims to not support visual 0x5a
    (WW) AIGLX: 3D driver claims to not support visual 0x5b
    (WW) AIGLX: 3D driver claims to not support visual 0x5c
    (WW) AIGLX: 3D driver claims to not support visual 0x5d
    (WW) AIGLX: 3D driver claims to not support visual 0x5e
    (WW) AIGLX: 3D driver claims to not support visual 0x5f
    (WW) AIGLX: 3D driver claims to not support visual 0x60
    (WW) AIGLX: 3D driver claims to not support visual 0x61
    (WW) AIGLX: 3D driver claims to not support visual 0x62
    (WW) AIGLX: 3D driver claims to not support visual 0x63
    (WW) AIGLX: 3D driver claims to not support visual 0x64
    (WW) AIGLX: 3D driver claims to not support visual 0x65
    (WW) AIGLX: 3D driver claims to not support visual 0x66
    (WW) AIGLX: 3D driver claims to not support visual 0x67
    (WW) AIGLX: 3D driver claims to not support visual 0x68
    (WW) AIGLX: 3D driver claims to not support visual 0x69
    (WW) AIGLX: 3D driver claims to not support visual 0x6a
    (WW) AIGLX: 3D driver claims to not support visual 0x6b
    (WW) AIGLX: 3D driver claims to not support visual 0x6c
    (WW) AIGLX: 3D driver claims to not support visual 0x6d
    (WW) AIGLX: 3D driver claims to not support visual 0x6e
    (WW) AIGLX: 3D driver claims to not support visual 0x6f
    (WW) AIGLX: 3D driver claims to not support visual 0x70
    (WW) AIGLX: 3D driver claims to not support visual 0x71
    (WW) AIGLX: 3D driver claims to not support visual 0x72
    (II) AIGLX: Loaded and initialized /usr/lib64/dri/fglrx_dri.so
    (II) GLX: Initialized DRI GL provider for screen 0
    (II) fglrx(0): Enable the clock gating!
    (**) Option "Protocol" "Auto"
    (**) Mouse1: Device: "/dev/input/mice"
    (**) Mouse1: Protocol: "Auto"
    (**) Option "CorePointer"
    (**) Mouse1: always reports core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Buttons" "5"
    (**) Option "Emulate3Buttons" "false"
    (**) Option "ZAxisMapping" "4 5"
    (**) Mouse1: ZAxisMapping: buttons 4 and 5
    (**) Mouse1: Buttons: 9
    (**) Mouse1: Sensitivity: 1
    (**) Option "CoreKeyboard"
    (**) Keyboard1: always reports core events
    (**) Option "Protocol" "standard"
    (**) Keyboard1: Protocol: standard
    (**) Option "AutoRepeat" "500 5"
    (**) Option "XLeds" "1 2 3"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard1: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) Keyboard1: XkbModel: "pc105"
    (**) Option "XkbLayout" "de"
    (**) Keyboard1: XkbLayout: "de"
    (**) Option "XkbVariant" "nodeadkeys"
    (**) Keyboard1: XkbVariant: "nodeadkeys"
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard1: CustomKeycodes disabled
    (II) evaluating device (Keyboard1)
    (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
    (II) evaluating device (Mouse1)
    (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
    (--) Mouse1: PnP-detected protocol: "ExplorerPS/2"
    (II) Mouse1: ps2EnableDataReporting: succeeded
    Could not init font path element /usr/share/fonts/TTF/, removing from list!
    Could not init font path element /usr/share/fonts/OTF, removing from list!
    Could not init font path element /usr/share/fonts/Type1/, removing from list!

  2. #2

    Default

    Okay, here's an update. When I run 'startx' it actually quits out with useful information. I see the two following lines:

    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
    and then a bunch of stuff about fontpath elements being not found, and the message
    Code:
    Could not find device entity for slave adapter
    'lspci' reports that the card's two cores are at PCI 03:00:0 and 04:00:0. So I'm guessing this is an incorrect xorg-conf setup. I've uset aticonfig, but it hasn't helped. Any suggestions?

    Thanks,

    EE

  3. #3

    Default

    Okay, I rebuilt the kernel, re-installed the xorg-server. My error message is somewhat different now. This appears to be a failure of the driver itself. Can anybody here help debug?

    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
    Thanks,

    EE

  4. #4

    Default

    fixed the ABI mismatch, and removed the nv driver. Still the same segfault as above when I run X, but if I run 'startx' (say, as a regular user), the only thing approaching an error is is the warning about being unable to find a Device section for PCI:3:0:0. This makes no sense, as the relevant section of my xorg conf is:

    Code:
    Section "Device"
            Identifier  "EAH4870X2-0"
            Driver      "fglrx"
            BusID       "PCI:3:0:0"
    EndSection
    
    Section "Device"
            Identifier  "EAH4870X2-1"
            Driver      "fglrx"
            BusID       "PCI:4:0:0"
    EndSection
    
    Section "Screen"
            Identifier "aticonfig-Screen[0]-0"
            Device     "EAH4870X2-0" 
            Device     "EAH4870X2-1"
            Monitor    "aticonfig-Monitor[0]-0"
            DefaultDepth     24
            SubSection "Display"
                    Viewport   0 0
                    Depth     24
            EndSubSection
    EndSection
    is something wrong there?

    Thanks,

    EE

  5. #5
    Join Date
    Oct 2007
    Posts
    321

    Default

    Some people are here, and as a major informative note for you, this is actually an easily fixed issue, and not a bug.. when you upgrade from one motherboard to another, it's highly possible that the xorg configuration file of yours will need to be updated... take my device section for example, if i upgraded and for some reason i could not get x11 to work, i'd haft to know the steps to identify the new video card and such.
    Code:
    Section "Device"
    	Identifier	"aticonfig-Device[0]-0"
    	Driver		"fglrx"
    	Busid		"PCI:1:5:0"
    EndSection
    The first step is identifying where the video display controllers are, that is easy enough if you have the command lspci... just type this...

    Code:
    lspci | grep VGA
    now, the output of it, if i had upgraded would identify where the video card is and where on the bus it is... the sample output is as follows...

    Code:
    02:01.0 VGA compatible controller: ATI Technologies Inc RS780MC [Radeon HD 3100 Graphics]
    This output tells me exactly where the video card is, and who made it... notice the "02:01.0", this is where on the pci bus the device is. pretty much, the last step was to replace the busid's paramater with the appropriate statement.

    since for this example, it changed, the line...
    Code:
    	Busid		"PCI:1:5:0"
    would need changing to...
    Code:
    	Busid		"PCI:2:1:0"
    and as for other issues... It's actually a known issue if you change from an nvidia video card to an ati card... This is because Nvidia's proprietary driver modifies the key system file of...
    /usr/lib/libGL.so

  6. #6

    Default

    those are the correct PCI addresses for the card's two cores, or at least the card in some form viz.:

    Code:
    #lspci | grep ATI
    -snip-
    03:00.0 VGA compatible controller: ATI Technologies Inc Device 9441
    03:00.1 Audio device: ATI Technologies Inc HD48x0 audio
    04:00.0 Display controller: ATI Technologies Inc Device 9441
    So, the VGA controller is at 3, and a "display controller" is at 4. How, then, is the display controller mis-listed here? Because if I simply comment out that Device listing for BusID 4, I get a warning about there being "no Device listing for instance with BusID (PCI:4:0:0)." incidentally, I also now get a message that X has "Enable Crossfire Successfully!"

    I also see the cursor for a fraction of a second, so I guess that's progress?

    I am new at setting up dual-core vid cards. Can you help with this?

    Thanks,

    EE

  7. #7
    Join Date
    Oct 2007
    Posts
    321

    Default

    Your already as far as you can go for now, because the ATI driver from what i understand currently lacks enabling the crossfire capabilities on the radeon HD3870x2 and the radeon hd4870x2 ( which is your card), however crossfire on the single card setups works.

  8. #8

    Default

    I only have one card in the box. It isn't using Crossfire to use the two cores, is it?

    At any rate, it did work fine previously, on the old mobo (well, "fine" in a relative sense: 3D acceleration didn't really work). I suspect there's something wrong with the xorg.conf file; I just don't know what.

    Thanks for the help,

    EE

  9. #9
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,538

    Default

    Yes, Crossfire is used to run the two GPUs on an X2 board. I thought Crossfire on Linux supported a single 4870X2 board though, will ask around.

    I'm pretty sure we don't support running two X2 boards together (ie 4 GPUs) yet.
    Last edited by bridgman; 10-24-2008 at 10:53 PM.

  10. #10

    Default

    Well, as I said, I only have one card, and it was working - sorta - prior to the new mobo. Now X fails out completely. I'm now using the 8.10 driver; could this possibly be the reason why?

    Thanks for the help,

    EE

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •