Results 1 to 6 of 6

Thread: Common theme lately: fglrx = segfault

  1. #1
    Join Date
    Oct 2007
    Posts
    91

    Default Common theme lately: fglrx = segfault

    I installed fglrx 10.6 last night after removing the Ubuntu supplied driver via Synaptic, only to receive a segfault on reboot. This seems like a common thread lately, what is going on over there with the fglrx QA?

    GPU: AMD 890GX (HD4290)
    Kernel: Stock Lucid 2.6.32-22 x86_64
    Xorg: Stock Lucid 7.5
    Xserver: Stock Lucid 1.7.6


    Code:
    Backtrace:
    0: /usr/bin/X (xorg_backtrace+0x28) [0x46d5b8]
    1: /usr/bin/X (0x400000+0x6c42d) [0x46c42d]
    2: /lib/libpthread.so.0 (0x7f7841ec8000+0xf8f0) [0x7f7841ed78f0]
    3: /usr/bin/X (0x400000+0x110188) [0x510188]
    4: /usr/bin/X (xf86ParsePciBusString+0x35) [0x504665]
    5: /usr/bin/X (xf86ComparePciBusString+0x2e) [0x5048de]
    6: /usr/lib/xorg/extra-modules/modules/drivers/fglrx_drv.so (atiddxProbe+0x8b3) [0x7f783eb36043]
    7: /usr/bin/X (xf86CallDriverProbe+0x2bd) [0x47cc4d]
    8: /usr/bin/X (InitOutput+0x345) [0x47e075]
    9: /usr/bin/X (0x400000+0x26005) [0x426005]
    10: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f7840bc0c4d]
    11: /usr/bin/X (0x400000+0x25d59) [0x425d59]
    Segmentation fault at address (nil)
    
    Caught signal 11 (Segmentation fault). Server aborting
    Xorg log
    dmesg

  2. #2
    Join Date
    Oct 2007
    Posts
    91

    Default

    It appears that the workaround for me was to add an option to the Device section of xorg.conf. I'm not home to verify that Xorg is fully loaded, but the segfault is no longer in Xorg.0.log

    BusID "PCI:1:5:0"

    See bug#1836 for details.

  3. #3
    Join Date
    Aug 2007
    Posts
    6,610

    Default

    That's pure crap, ATI should not have released the driver or at least push a prerelease out with a fix for that.

  4. #4
    Join Date
    Oct 2007
    Posts
    91

    Default

    I used your script to install fglrx, Kano. You might want to add this workaround to the other ones. I could probably come up with a patch, if you would like.

    And yes, this is pure crap. Line 52 of the Xorg.0.log file pasted above shows that at least some part of the xserver already knows the PCI address of my video card!

  5. #5
    Join Date
    May 2007
    Posts
    352

    Default

    It is pretty amazing that this slipped through. I'm seeing this exact error here, too, on Ubuntu 10.04 which is supposedly a supported distribution. Adding the BusID to the Device section gets it working.

    Adam

  6. #6
    Join Date
    Jun 2010
    Posts
    38

    Default

    It's quite normal for "linux"... with 1% market share for desktop, we might get 2% support from ATi devs, the rest goes to Windows. That being said, you should be glad your card doesn't get burn wile using FGLRX, yet that could also happen with a future release... maybe 10.7.

Posting Permissions

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