<---- template headericclude ----->
ATI fglrx install killing OpenOffice? - Page 2
FedoraForum.org - Fedora Support Forums and Community
Page 2 of 2 FirstFirst 12
Results 16 to 22 of 22
  1. #16
    Join Date
    Dec 2005
    Posts
    38
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    >Try disabling Xinerama


    >Code:

    >Option "Xinerama" "off"

    Negative - no help with Presentation/OpenOffice

  2. #17
    dwnwrd Guest

    Unhappy

    You aren't alone. The only way I can get OOanything to run is with sudo. Also my disk is filling with giant /var/log/Xorg.0.log and /var/log/gdm/:0.log which grow rapidly with the following:

    Code:
    (EE) fglrx(1): [DRI] Unlocking inconsistency:
            Context 10483172 trying to unlock lock held by context 2
    (EE) fglrx(1): [DRI] Locking deadlock.
            Already locked with context 10483172,
            trying to lock with context 2.
    (EE) fglrx(1): [DRI] Unlocking inconsistency:
            Context 10483172 trying to unlock lock held by context 2
    (EE) fglrx(1): [DRI] Locking deadlock.
            Already locked with context 10483172,
            trying to lock with context 2.
    Fully patched fedora 8 with livna fglrx drivers.

  3. #18
    Join Date
    May 2004
    Location
    Mexico City, Mexico
    Age
    46
    Posts
    4,428
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Wild thought, have you tried to install the reference ATI driver from AMD's site? If it presents the same behavior, I think you can safely say that the problem lies within Livna's packages, otherwise you will have to issue a bug report in Livna or alternatively to AMD themselves. I highly suspect this is not the case with official AMD's releases, as I've not heard of any other ATI users complaining about this specific issue.
    If ain't broken, don't fix it! :eek:
    If can be improved, go for it! :cool:

    FedoraForum Community forums lurker.
    Fedora user since RHL 5.2 :cool:

  4. #19
    sarantius Guest
    I recently installed F8 and had similar problems. I can confirm that using the official AMD release continues to cause the problem. As a workaround, downgrading Xorg to the latest available version for F7 (xorg-x11-server-Xorg-1.3.0.0-16.fc7) seems to fix the problem for me with both the livna and AMD packages (at least with AIGLX/composite turned off). I no longer have "DRI" errors filling the logs and I'm able to run apps like Google Earth successfully. Downgrading to an earlier F8 version (xorg-x11-server-Xorg-1.3.0.0-33.fc8) doesn't work and continues to produce the errors.

  5. #20
    Join Date
    Aug 2006
    Posts
    57
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Hosanna!

    Thank you a million leigh123@linux:
    I did a cut and paste of your xorg.conf file - lo and behold, it worked great. I now have two gorgeous screens. Perfect, with no adjustment needed. Man, am I impressed - these monitors never looked so good in windoz.

    Did a clean install to FC8 (upgraded FC6) in December, and until just now, it was unusable. And while FC6 had multihead, the screens had not the quality I see now in FC8. Wow, they even have independent full screen mode - which FC6 did not. My hat's off to the Livna team - great work.

    Thanks again to all the Fedoraites.
    --nybigjet

  6. #21
    jonastio Guest

    Angry

    Quote Originally Posted by sarantius
    I recently installed F8 and had similar problems. I can confirm that using the official AMD release continues to cause the problem. As a workaround, downgrading Xorg to the latest available version for F7 (xorg-x11-server-Xorg-1.3.0.0-16.fc7) seems to fix the problem for me with both the livna and AMD packages (at least with AIGLX/composite turned off). I no longer have "DRI" errors filling the logs and I'm able to run apps like Google Earth successfully. Downgrading to an earlier F8 version (xorg-x11-server-Xorg-1.3.0.0-33.fc8) doesn't work and continues to produce the errors.

    This is what worked for me. Before I did the downgrade, I played with the xorg.conf and the flag that kills it is:

    Code:
    BusID "PCI:1:0:0"
    You pull that out and you'll notice there aren't anymore issues, except that now you've got a cloned screen instead of dual screen.

  7. #22
    AI8W Guest
    Quote Originally Posted by dwnwrd
    You aren't alone. The only way I can get OOanything to run is with sudo. Also my disk is filling with giant /var/log/Xorg.0.log and /var/log/gdm/:0.log which grow rapidly with the following:

    Code:
    (EE) fglrx(1): [DRI] Unlocking inconsistency:
            Context 10483172 trying to unlock lock held by context 2
    (EE) fglrx(1): [DRI] Locking deadlock.
            Already locked with context 10483172,
            trying to lock with context 2.
    (EE) fglrx(1): [DRI] Unlocking inconsistency:
            Context 10483172 trying to unlock lock held by context 2
    (EE) fglrx(1): [DRI] Locking deadlock.
            Already locked with context 10483172,
            trying to lock with context 2.
    Fully patched fedora 8 with livna fglrx drivers.

    For what it's worth, I'm in the same boat. Seems the only way to get rid of it is to turn off FGLRX, or downgrade X... Neither option is really desirable.

Page 2 of 2 FirstFirst 12

Similar Threads

  1. fglrx install guide
    By TyraelOdium in forum Using Fedora
    Replies: 0
    Last Post: 20th August 2007, 03:44 AM
  2. how to install openoffice from openoffice website?
    By sdowney717 in forum Using Fedora
    Replies: 13
    Last Post: 20th March 2007, 02:25 AM
  3. FC5 Fresh Install... do I need fglrx?
    By zackiv31 in forum EOL (End Of Life) Versions
    Replies: 1
    Last Post: 9th August 2006, 05:35 PM
  4. FC3 installation hangs killing my working FC2 install
    By pembo13 in forum EOL (End Of Life) Versions
    Replies: 0
    Last Post: 18th December 2004, 06:26 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]