Announcement

Collapse
No announcement yet.

ati catalyst 10.6 released

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

  • Color Issues with World Of Padman

    Hi,

    I installed the 10.6 yesterday and when playing to World Of Padman I can see weird differences in the color of textures respect to the previous Catalyst. For example if you go into the sink, in the kitchen, and switch to the Punchy, the Punchy is completely white instead to keep its original colors.

    Have you noticed that?

    Regards,

    Comment


    • Hope this
      "Xorg -probeonly" no longer causes screen corruption or the system to fail to respond
      means that the issue I'm facing since the catalyst 9.9 is resolved and will be able to replpace 9.8 with 10.6 - will see when come back from work

      Comment


      • Originally posted by maciejus View Post
        Hope this

        means that the issue I'm facing since the catalyst 9.9 is resolved and will be able to replpace 9.8 with 10.6 - will see when come back from work
        I doubt it. I just don't understand why driver works fine on windows with nforce430 chipset, but fail on linux. Every version higher than 9.8 = blank screen and i guess bug filling on unofficial ati bugzilla isn't even worth it. This makes me so angry

        Comment


        • phoen1x, is that ticket #1700 you're talking about on ati.cchtml.com ? If so, that ticket was reported as debian-only and the debian ticket containing the info was subsequently closed because the debian devs felt it was a kernel issue (mucked up MTRRs).

          Any chance you could confirm the problem also occurs on a supported distro (maybe try Ubuntu 9.10) and update the ticket ?

          Comment


          • Originally posted by sandain View Post
            You are using an unsupported kernel. Your best bet is to downgrade to the stock 2.6.32 kernel. Someone around here might have a patch for you to enable 2.6.34.. Good luck.
            Yeah, I hope this.
            The "stable" 2.6.32 of Canonical, it's unstable. It have an huge bug with my platform that cause random and frequently freeze with the hdds. From 2 months of 10.04, not fix yet...

            Comment


            • Originally posted by bridgman View Post
              phoen1x, is that ticket #1700 you're talking about on ati.cchtml.com ? If so, that ticket was reported as debian-only and the debian ticket containing the info was subsequently closed because the debian devs felt it was a kernel issue (mucked up MTRRs).

              Any chance you could confirm the problem also occurs on a supported distro (maybe try Ubuntu 9.10) and update the ticket ?
              I can confirm that this is not debian only bug. It doesn't depend on distribution, tested on ubuntu 9.04/9.10, archlinux and gentoo. The problem now is i got only gentoo and yesterday i tried cat 10.6 and still blank screen as usual xorg.log shows nothing suspicious. I tested cat 9.4-10.6, all versions higher than 9.8 just dont work and kernel version really doesn't matter, i tried 2.6.28-2.6.33 (even 2.6.34rc). Should i fill bug report? Bug #1794 perfectly describes problem.

              Comment


              • The mtrr output looks funny, doesn't it ? That sounds like it might be a system BIOS issue; do you know if you're running the most recent BIOS image available for your mobo ?

                Comment


                • btw, i wanted to note that i seem to ahve fixed my issues with a clean reinstall, speed is very fast :O

                  Comment


                  • Originally posted by bridgman View Post
                    The mtrr output looks funny, doesn't it ? That sounds like it might be a system BIOS issue; do you know if you're running the most recent BIOS image available for your mobo ?
                    Could You please specify which mtrr output Your are referring to?
                    Mine mtrr output:
                    reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
                    reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
                    reg02: base=0x0c0000000 ( 3072MB), size= 512MB, count=1: write-back
                    reg03: base=0x100000000 ( 4096MB), size= 512MB, count=1: write-back
                    Does this looks bad?

                    Comment


                    • Ati did it again!Worst tearing ever with 10.6.In 2d and 3d (Ati HD3870)Going back to 10.5
                      Sorry for bad english

                      Comment


                      • I have to say I was pleasantly surprised by this new driver! I'm using a supported OS (openSUSE 11.2) but I've installed some extra libraries that aren't standard in the distro, namely Kernel 2.6.33, libdrm 2.4.21 and a few others I can't remember right now, although I'm still using xorg-server 7.4. I just build a package from the list of distros (SuSE/SUSE 11.2), but I wasn't hoping for much due to the upgraded kernel and not being sure if SUSE was referring to openSUSE or the commercial variant. The package build fine and I installed it, again with no errors to my big surprise. I just assumed that it would probably break my system on reboot since so far it had been a pleasant process. But once again my expectations weren't met and the damn thing worked fine and booted nicely.

                        By this time I was thinking that something HAD to be wrong, since I haven't had such a trouble free graphics driver installation process since the days I had a geforce4. I tried a few 3D apps and desktop effects and all worked great. So I have to say this is the best catalyst release yet for me and it is working perfectly... almost! After I changed the screen mode in the CCC everything also worked fine, until the next time I booted the system. This time it was more like a real catalyst driver and X wouldn't start. Some complaint about a ModeLine that was expecting H"something". Turns out that in each ModeLine line the first number after the mode name ("1600x1200") was like this -> 217,0 and xorg was expecting only integers so I had to manually delete the ",0" from every line to be able to boot into X. Why did this happen? I did an aticonfig --initial as was stated and everything was working perfectly until this. Why?? I suppose that CCC added those unnecessary ",0" to each number, I just don't understand why...

                        Anyway, it's not news that there are problems installing the catalyst drivers, and this was an easy one to solve, but it's a shame this still isn't a flawless victory for the driver. Maybe next month

                        Comment


                        • Originally posted by phoen1x View Post
                          Could You please specify which mtrr output Your are referring to?
                          Mine mtrr output:
                          reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
                          reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
                          reg02: base=0x0c0000000 ( 3072MB), size= 512MB, count=1: write-back
                          reg03: base=0x100000000 ( 4096MB), size= 512MB, count=1: write-back
                          Does this looks bad?
                          Just to add to the discussion, very similar setup (HD5770, Nforce 430, 64-bit Ubuntu, mobo: Asus M2NPV-VM, btw just upgraded to the last BIOS available, as per Bridgman suggestion) same negative experience (black screen / hanging). I'll append my mtrr too, who knows..

                          reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
                          reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
                          reg02: base=0x0c0000000 ( 3072MB), size= 256MB, count=1: write-back
                          reg03: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back
                          reg04: base=0x0cff00000 ( 3327MB), size= 1MB, count=1: uncachable

                          And no, the MTRR ranges didn't change upgrading the BIOS.

                          I've tried w/ all recent Catalyst versions, now I'm going to try the 10.6 release but I have little hope..

                          Comment


                          • oh btw.
                            with fglrx 10.6 you can finally record your desktop without everything slowing to a crawl.
                            runs smooth as silk!

                            Comment


                            • What I put in x-updates is working with xserver 1.8 here outside of the crashes unless you specify a busID in xorg.conf (aticonfig --initial works)

                              http://sarvatt.com/downloads/Xorg.0.log

                              backtrace with jockey's xorg.conf

                              http://sarvatt.com/downloads/xserver.gdb.txt

                              Comment


                              • Catalyst 10.6 bug in amdcccle?

                                Hi ATI-devs,

                                amdcccle messed up comma and decimal point in my modelines. It exchanged (for example)
                                ModeLine "1280x1024" 107.0 1280 1360 1496 1712 1024 1025 1028 1059
                                against
                                ModeLine "1280x1024" 107,0 1280 1360 1496 1712 1024 1025 1028 1059

                                X complains: "Parse error on line 95 of section Modes in file /etc/X11/xorg.conf
                                ModeLine Hdisplay expected"

                                long story:
                                I installed 10.6 yesterday starting ati-driver-installer-10-6-x86.x86_64.run from a konsole with su. I use the same xorg.conf since many Catalyst versions, so I let the file untouched and rebooted the PC. Everything worked fine.

                                Then I connected a projector to the second DVI port of my HD3850. amdcccle told me to run it with su privileges to be able to change screen settings. (that will bring me to a second question, later)
                                I run amdcccle as su and could activate the clone mode for both screens. I also wanted to change the resolution to 1280x720 to fit the projector but amdcccle told me that I have to reboot for this change. So I let the resolution at 1280x1024 because I just wanted to watch a DVD and go to bed.
                                Today I switched on my PC and it booted to text mode instead of KDE login.
                                My xsession-errors are here: http://pastebin.org/342355
                                After changing all "," back to "." manually my X started.

                                Cheers,
                                mibo

                                Opensuse 11.1 64 bit
                                KDE 4.3.5
                                HD3850 + 19"TFT@DVI

                                Comment

                                Working...
                                X