Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Radeon 8000M problematic on Linux?

  1. #11
    Join Date
    Nov 2010
    Posts
    95

    Default

    "Will lspci and dmesg help out if I execute them from the other TTYs without resorting to ssh? "

    Yes, they could.
    Old X server logs would be probably more helpful, though. They are usually saved even when X.org crashes.
    Old kernel logs (when Xorg crashes) could probably also be found on the HDD.

  2. #12
    Join Date
    Mar 2014
    Posts
    30

    Default

    So, here is the result of lspci and dmesg commands plus the Xorg log file.

    lspci: https://drive.google.com/file/d/0B8s...it?usp=sharing

    dmesg: https://drive.google.com/file/d/0B8s...it?usp=sharing

    Xorg log file: https://drive.google.com/file/d/0B8s...it?usp=sharing
    thanks!

  3. #13
    Join Date
    Mar 2014
    Posts
    30

    Default

    *UPDATE*

    Definitely a RadeonSI bug.

    Tried the fglrx driver available in the software center and it work like a charm.

    I could mark the topic solved, but I would have liked it to be able to use RadeonSI (

    Ah, maybe one day....

  4. #14
    Join Date
    Oct 2012
    Posts
    273

    Default

    Did you read this thread? http://www.phoronix.com/forums/showt...t-what-they-do , read it and test the commands provided there.

    Quote Originally Posted by Adriannho View Post
    So, here is the result of lspci and dmesg commands plus the Xorg log file.

    lspci: https://drive.google.com/file/d/0B8s...it?usp=sharing

    dmesg: https://drive.google.com/file/d/0B8s...it?usp=sharing

    Xorg log file: https://drive.google.com/file/d/0B8s...it?usp=sharing
    thanks!
    I couldn't read a thing... can you send the logs to pastebin.com ?

  5. #15
    Join Date
    Dec 2007
    Posts
    2,402

    Default

    It's an issue with runtime pm. Append radeon.runpm=0 to the kernel command line in grub to work around it. You can follow the progress of debugging it here:
    https://bugs.freedesktop.org/show_bug.cgi?id=75127

  6. #16
    Join Date
    Aug 2012
    Posts
    435

    Default

    You should have installed Ubuntu 14.04 development instead -- that's the first thing I did when I got a new Kabini APU laptop (A4-5000) in December. Worked perfectly out of the box with open source drivers ever since. The only thing really holding it back is the horrible performance of GLAMOR, which is still a lot faster than Catalyst's even worse 2D rendering.

  7. #17
    Join Date
    Mar 2014
    Posts
    30

    Default

    Quote Originally Posted by mmstick View Post
    You should have installed Ubuntu 14.04 development instead
    I have (K)ubuntu 14.04 (development, and now final) installed. The testing was mostly done on it.

    Quote Originally Posted by AGD5F
    agd5f
    It's an issue with runtime pm. Append radeon.runpm=0 to the kernel command line in grub to work around it. You can follow the progress of debugging it here:
    https://bugs.freedesktop.org/show_bug.cgi?id=75127
    I tried disabling both runpm and dpm many times, but it simply didn't work. Also, the problems described in the linked bug post differ from the one I'm experiencing.

    Well, after a lot of testing I think I narrowed down the problem to a kernel regression.

    This explains the strange behaviour I experienced after installing arch and ubuntu. It worked for the first 2-3 times, and after that, it would no longer boot.

    It seems that when upgrading kernel (in Ubuntu) from 13.0.19 to 13.0.24, my machine becomes unbootable with radeon (fglrx can boot perfectly fine with 13.0.24 though).
    When selecting the old kernel in Grub I can boot with no problem again.

    (I have to add that booting kernel 3.12 also leads to a failure).

    Does anyone have any idea about something that went between the afore mentioned kernel releases that could cause my system to become unbootable?
    Also, I would need advice on how to proceed next and better isolate the problem (pet commit).

    Thanks!

  8. #18
    Join Date
    Dec 2007
    Posts
    2,402

    Default

    Quote Originally Posted by Adriannho View Post
    Does anyone have any idea about something that went between the afore mentioned kernel releases that could cause my system to become unbootable?
    Also, I would need advice on how to proceed next and better isolate the problem (pet commit).
    Please use git to bisect the problem and file a bug (https://bugs.freedesktop/org).

  9. #19
    Join Date
    Mar 2014
    Posts
    30

    Default

    Quote Originally Posted by agd5f View Post
    Please use git to bisect the problem and file a bug (https://bugs.freedesktop/org).
    Well, I did that, and after all, it seems you were right Alex, it was runpm's fault.

    But the bug is very different to the one you pointed in the link.
    Also, for me, setting
    Code:
    radeon.runpm=0
    didn't work.

    Bug report https://bugs.freedesktop.org/show_bug.cgi?id=77930

    Similar situation: http://forums.gentoo.org/viewtopic-p-7529160.html

Posting Permissions

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