Announcement

Collapse
No announcement yet.

AMD Catalyst 9.4 Finally Brings X Server 1.6 Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Originally posted by tball View Post
    How are you setting up your dualscreen? With amdcccle or randr?
    I didn't try with randr because randr didn't recognize the tv-out with driver 9.3 (see this topic about it: http://www.phoronix.com/forums/showthread.php?t=16265). So I tried with aticonfig to setup a dual-head configuration:

    Code:
    aticonfig --initial=dual-head --adapter=0
    This gave me the config with tv and main screen reversed (login screen on tv). I also tried setting up only my main screen (--initial --adapter=0) and after I got that working, I tried to add the tv-out device, monitor and screen section manually to the xorg.conf file. This gave me screen corruption (xorg.conf was correct, I used my backup which worked perfectly fine with 9.3).

    Comment


    • #62
      Is there a gentoo ebuild? Can't find any.

      Comment


      • #63
        Wielkie G, thank you for the reminder, on that test box I have 8 installs, and in fact you're right I believe, I neglected to hold that package, let me confirm or deny the libdrm2 thing and get back to you, thanks for the reminder, in fact, now that I think of it, that broken top red blur and x start failure was the same with the new libdrm2, I'll report back.

        Re the now broken Sid 32 bit package builder, which joins the long broken 64 bit package builder, that's still of course an issue, sigh... personally I only distribute code that I've tested and know works, but I guess I'm strange that way.

        Comment


        • #64
          Wielkie G, you were correct, I should have recognized the shattered top red line and black screen, lol. But I honestly can't keep all these fglrx issues straight, I'll have to implement a libdrm2 status test, i was hoping that issue would be resolved by 9-4, but that was apparently a bit too optimistic.

          Code:
          inxi -d
          System:    Host sx-32-1 Kernel 2.6.29-1.lqx.4-liquorix-686 i686 (32 bit) Distro Debian Sid
          CPU:       Dual core AMD Athlon 64 X2 4400+ (SMP) clocked at 2300.00 MHz 
          Graphics:  Card ATI RV710 [Radeon HD 4350] X.Org 1.4.2 Res: [email protected] 
                     GLX Renderer ATI Radeon HD 4350 GLX Version 2.1.8591
          Disks:     HDD Total Size: 122.9GB (17.1% used)
          Info:      Processes 121 Uptime 9 min Memory 192.4/2025.9MB Client Shell inxi 1.0.11
          So working using direct install method, but debs fail to install, though they do build

          Oh, now I can upgrade the system to xorg 1.6, I didn't want to do that until I could get working fglrx on it. Hard to keep all these installs straight, heh..

          I'm using the previous 9-3, 9.2 patches and they work still apparently.
          Last edited by gfxdrone; 18 April 2009, 02:10 PM.

          Comment


          • #65
            Originally posted by blabub View Post
            Is there a gentoo ebuild? Can't find any.
            don't you have a local overlay like all those other geeks out there?

            make it on your own like I do! (not only for catalyst)

            Comment


            • #66
              Definitely can't get hybrid crossfire working anymore with 9.4.

              But the bigger problem is that I can't get dual-head (with two separate X screens) working anymore. Xrandr now recognizes my TV out (it didn't with the 9.3 driver release). But the problem is that on my main screen, which uses a resolution of 1280x1024, gnome only uses 1024x768 of the available space (like people describe in this bug report: https://bugs.launchpad.net/fedora/+s...rg/+bug/156550).

              I see the background stretched all over the full 1280x1024, but panels in top and bottom of the screen only cover 1024 pixels and the bottom panel hovers somewhere in the middle of the screen (768 pixels from the top). Maximizing a window makes it 1024x768, while I am able to manually create larger windows up to 1280x1024.

              I tried the solutions that are suggested in the above bug report, but xrandr doesn't list any other output devices turned on except CRT1 for screen 0 and TV for screen 1. Xrandr also reports the correct resolutions (1280x1024 for CRT1 on screen 0 and 1024x768 for TV on screen 1).

              Comment


              • #67
                Originally posted by Vighy View Post
                Code:
                Apr 18 13:48:37 Obi-Wan [fglrx] Firegl kernel thread PID: 5543
                Apr 18 13:48:38 Obi-Wan [fglrx] Gart cacheable size:1000 M.
                Apr 18 13:48:38 Obi-Wan [fglrx] Reserved FB block: Shared offset:0, size:1000000 
                Apr 18 13:48:38 Obi-Wan [fglrx] Reserved FB block: Unshared offset:fdff000, size:201000 
                Apr 18 13:48:38 Obi-Wan [fglrx] Reserved FB block: Unshared offset:1fffb000, size:5000 
                Apr 18 13:48:38 Obi-Wan BUG: scheduling while atomic: X/5371/0x00000002
                Apr 18 13:48:38 Obi-Wan Modules linked in: vboxnetflt vboxdrv fglrx(P) uvcvideo [last unloaded: microcode]
                Apr 18 13:48:38 Obi-Wan Pid: 5371, comm: X Tainted: P           2.6.28-tuxonice-r9-BeN-g8fdd299 #2
                Apr 18 13:48:38 Obi-Wan Call Trace:
                Apr 18 13:48:38 Obi-Wan [<ffffffff80672fb0>] 0xffffffff80672fb0
                Apr 18 13:48:38 Obi-Wan [<ffffffff8023142a>] 0xffffffff8023142a
                Apr 18 13:48:38 Obi-Wan [<ffffffff80231e23>] 0xffffffff80231e23
                Apr 18 13:48:38 Obi-Wan [<ffffffffa0014a18>] 0xffffffffa0014a18
                Apr 18 13:48:38 Obi-Wan [<ffffffff80253800>] 0xffffffff80253800
                Apr 18 13:48:38 Obi-Wan [<ffffffffa002c6e7>] 0xffffffffa002c6e7
                Apr 18 13:48:38 Obi-Wan [<ffffffffa002dce6>] 0xffffffffa002dce6
                Apr 18 13:48:38 Obi-Wan [<ffffffffa00debd1>] 0xffffffffa00debd1
                Apr 18 13:48:38 Obi-Wan [<ffffffffa00e86e5>] 0xffffffffa00e86e5
                Apr 18 13:48:38 Obi-Wan [<ffffffff8028a49c>] 0xffffffff8028a49c
                Apr 18 13:48:38 Obi-Wan [<ffffffff8028ad63>] 0xffffffff8028ad63
                Apr 18 13:48:38 Obi-Wan [<ffffffffa00dded9>] 0xffffffffa00dded9
                Apr 18 13:48:38 Obi-Wan [<ffffffffa002eb37>] 0xffffffffa002eb37
                Apr 18 13:48:38 Obi-Wan [<ffffffffa0022354>] 0xffffffffa0022354
                Apr 18 13:48:38 Obi-Wan [<ffffffffa0021435>] 0xffffffffa0021435
                Apr 18 13:48:38 Obi-Wan [<ffffffff802c0d6f>] 0xffffffff802c0d6f
                Apr 18 13:48:38 Obi-Wan [<ffffffff802bd5cb>] 0xffffffff802bd5cb
                Apr 18 13:48:38 Obi-Wan [<ffffffff8023e4b5>] 0xffffffff8023e4b5
                Apr 18 13:48:38 Obi-Wan [<ffffffff802406d8>] 0xffffffff802406d8
                Apr 18 13:48:38 Obi-Wan [<ffffffff802407b3>] 0xffffffff802407b3
                Apr 18 13:48:38 Obi-Wan [<ffffffff80240832>] 0xffffffff80240832
                Apr 18 13:48:38 Obi-Wan [<ffffffff8020b94b>] 0xffffffff8020b94b
                nice! ain't it??
                It appeared compiling asus_laptop built-in.
                Rebuilding the kernel, leaving asus_laptop as a module did work.

                ehhhhhhhhhhhh!?!??! what the heck do those things match!?

                should I open a ticket for that?
                Obviously it crashes my system.
                If I understand you right; If you didn't have the asus_laptop building the kernel, it didn't crash when resizing? Because I got an asus laptop, which has that problem.

                Comment


                • #68
                  Originally posted by Heiko View Post
                  I didn't try with randr because randr didn't recognize the tv-out with driver 9.3 (see this topic about it: http://www.phoronix.com/forums/showthread.php?t=16265). So I tried with aticonfig to setup a dual-head configuration:

                  Code:
                  aticonfig --initial=dual-head --adapter=0
                  This gave me the config with tv and main screen reversed (login screen on tv). I also tried setting up only my main screen (--initial --adapter=0) and after I got that working, I tried to add the tv-out device, monitor and screen section manually to the xorg.conf file. This gave me screen corruption (xorg.conf was correct, I used my backup which worked perfectly fine with 9.3).
                  I have had alot of trouble getting dualhead working with amdcccle in 9.3. But randr worked perfectly with compiz etc. Though the randr gui in kde seems kinda broken, so I just use the xrandr cli. Just type 'xrandr -q' and you should see your tv-out.

                  Comment


                  • #69
                    If i try to view a video on mplayer on my second screen in fullscreen-mode, the whole screen is corrupted. If i try this on the first screen everything is fine. The problem occurs only on the second screen.

                    Comment


                    • #70
                      Originally posted by storma View Post
                      Hmm.. with 8.* I saw steady improvement with fglrx.
                      Now with the 9.* series, I see steady regressions.

                      9.3 introduced graphical glitches to savage 2, with 9.4 I can't even start s2:
                      X Error of failed request: BadValue (integer parameter out of range for operation)
                      Major opcode of failed request: 147 (XFree86-DRI)
                      Minor opcode of failed request: 8 ()
                      Value in failed request: 0x2200009
                      Serial number of failed request: 81
                      Current serial number in output stream: 107

                      9.3 Mythtv playback was great, 9.4 playback is unwatchable due to stuttering. This happens with both SD and HD playback, though HD playback with mplayer is fine. :/

                      card: 4870, reckon I'm done with it.
                      You need to rebuild your kernel module. You've probably updated your kernel at some point. Use dkms or just reinstall the driver.

                      Comment

                      Working...
                      X