Results 1 to 8 of 8

Thread: Disabling BlockSignalsOnLock?

Hybrid View

  1. #1
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,070

    Default Disabling BlockSignalsOnLock?

    Blob 12.6 from AMD's site, not sure if it's different than the latest 12.6 beta mentioned here.
    E-350 hw, unrecognized by aticonfig (no supported adapters detected). It's 1002:9802, a standard E-350 AFAIK.

    Now, in order to use gDebugger on this without it locking up, I need to disable the blob's BlockSignalsOnLock option.

    gDebugger tells to run "aticonfig --sb off", which obviously gives the no supported adapters message.
    The release notes say that one can also add that to the Device section in xorg.conf, so I added it.

    But:
    /var/log/Xorg.0.log:(WW) fglrx(0): Option "BlockSignalsOnLock" is not used
    Any hints? The unofficial bugzilla gave zero hits for "block".

  2. #2
    Join Date
    Feb 2011
    Posts
    130

    Default

    Replace /etc/ati/control with the version from 12.6b or 12.4.
    Please search the forum a bit more in detail as this question has been answered multiple times - never the less: have fun with the blob

  3. #3
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,070

    Default

    Ah, thanks. I thought my problem was with the blob ignoring the xorg.conf option, but getting aticonfig to recognize the card should work too

  4. #4
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,070

    Default

    Worked, now aticonfig recognizes it and gdebugger could start.

    Shame on you, blob release team, for removing Evergreen pci ids when they are still supported.

    --

    Well, gdebugger fails to profile my app, heh. I'll take that to the AMD devguru forums.

    My respect for the blob itself has just been knocked down a few notches, it fails to draw my terrain, sky, and SSAO, all things that Mesa draws just fine. And this is the "superior" driver, reporting GL 4.2 support and having a team of hundreds of people? lol.

  5. #5
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,434

    Default

    If you check the bug ticket, we're already investigating how the IDs got dropped. Stay tuned.

    http://ati.cchtml.com/show_bug.cgi?id=551

    Where did you get the idea there were hundreds of people working on the Linux-specific parts of the driver (everything related to install, IDs etc is Linux-specific) ? The whole idea of a code-shared driver is that only the Linux-specific parts need separate development effort.
    Last edited by bridgman; 07-15-2012 at 10:11 AM.

  6. #6
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,070

    Default

    The OpenGL part is cross-OS, and the failure to draw big parts of my app is about that part, not the linux-specific parts.

    Note that you should take this as an accomplishment, the FOSS drivers beat the blob here hands down

Posting Permissions

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