Announcement

Collapse
No announcement yet.

Catalyst 9.1 is out

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

  • #61
    Originally posted by energyman View Post
    Kde 4.2:
    Only problem still unsolved: manually resizing is still slow. Not unusable, bad slow. Menus pop up instantly, windows move around without lag. Maximising has a very short lag. Like a tenth of a second. Switching between windows is lag free. Minimizing them to the task bar is an instant action.
    Logout of KDE4 and then back in and enjoy the experience*. 9.1 is just as crappy as previous versions. You seem too happy to have broken drivers. I'm not.

    *No more desktop effects. Have to reboot. Another bug that they don't fix. Nothing that required 3D works:

    Code:
    X Error of failed request:  BadRequest (invalid request code or no such operation)
      Major opcode of failed request:  144 (GLX)
      Minor opcode of failed request:  19 (X_GLXQueryServerString)
      Serial number of failed request:  17
      Current serial number in output stream:  17
    Last edited by RealNC; 01-30-2009, 06:36 PM.

    Comment


    • #62
      Seems that this new version requires PCI_MSI enabled in the kernel which it did not do before.

      9.1 now fails to load completely on slackware's stock kernels with the error:
      Code:
      kernel: fglrx: Unknown symbol pci_disable_msi
      kernel: fglrx: Unknown symbol pci_enable_msi
      Ah well

      Comment


      • #63
        Originally posted by ArTourter View Post
        Seems that this new version requires PCI_MSI enabled in the kernel which it did not do before.

        9.1 now fails to load completely on slackware's stock kernels with the error:
        Code:
        kernel: fglrx: Unknown symbol pci_disable_msi
        kernel: fglrx: Unknown symbol pci_enable_msi
        Ah well
        chance kernel or build your own kernel is easy...

        Comment


        • #64
          Originally posted by ArTourter View Post
          Seems that this new version requires PCI_MSI enabled in the kernel which it did not do before.

          9.1 now fails to load completely on slackware's stock kernels with the error:
          Code:
          kernel: fglrx: Unknown symbol pci_disable_msi
          kernel: fglrx: Unknown symbol pci_enable_msi
          Ah well
          Yes. Same problem here trying to install 9.1 in Slackware 12.1. I had to rebuild the kernel with PCI_MSI enabled. Anyway, it didn't hurt and 9.1 is running smooth now. No complains yet.

          Comment


          • #65
            Originally posted by energyman View Post
            If you want a supported distri
            If i want supported distro i chose nvidia. They haven't got problems with supporting such crapfest (as you call it) like Fedora.

            Comment


            • #66
              Things that still annoy me with 9.1:
              - Still can't create a second instance of the X server
              - with earlier releases (since something about 8.6) the Compiz blur effect didn't work like it should. That's at least partly fixed now, it just doesn't do anything now... :-/
              - Warcraft 3 had a slowdown of 50% with 9.1, ran with 50 fps under 8.12, now only 25 fps
              - No KMS or DRI2 support

              Comment


              • #67
                because nvidia traditionally replace much more than others with their own stuff.

                Comment


                • #68
                  Originally posted by NeoBrain View Post
                  - Still can't create a second instance of the X server
                  Yes, that one is really annoying when you have more than one user on the computer. I don't want to log off just because my wife want to check her email or do something else with her account.

                  Comment


                  • #69
                    Originally posted by bridgman View Post
                    angus77, does your system use AGP or PCIE bus ?
                    I'm pretty sure it's PCI, but my wife has been hogging the last couple days, so I haven't had the chance to pop it open and double-check. It's a Japanese Dell Inspiron 531S, and googling around seems to indicate that the American version doesn't support AGP.

                    Comment


                    • #70
                      angus77, lspci - as root - or dmidecode should give you the information needed without the need to open it up.

                      Comment


                      • #71
                        Originally posted by energyman View Post
                        angus77, lspci - as root - or dmidecode should give you the information needed without the need to open it up.
                        I'll get on it when my wife gets off the desktop

                        Comment


                        • #72
                          Or, rather, I'll ssh into it and find out

                          It's PCIE.

                          Comment


                          • #73
                            with dmidecode you should get something like this, if it is pcie:
                            Handle 0x0010, DMI type 9, 13 bytes
                            System Slot Information
                            Designation: PCIE2
                            Type: x16 PCI Express
                            Current Usage: In Use
                            Length: Short
                            ID: 18
                            Characteristics:
                            3.3 V is provided
                            Opening is shared
                            PME signal is supported

                            with lspci use lspci -v
                            and you get something like this for a graka using pcie:
                            02:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3870 (prog-if 00 [VGA controller])
                            Subsystem: Info-Tek Corp. Device 4070
                            Flags: bus master, fast devsel, latency 0, IRQ 18
                            Memory at d0000000 (64-bit, prefetchable) [size=256M]
                            Memory at fdff0000 (64-bit, non-prefetchable) [size=64K]
                            I/O ports at c000 [size=256]
                            Expansion ROM at fdfc0000 [disabled] [size=128K]
                            Capabilities: [50] Power Management version 3
                            Capabilities: [58] Express Legacy Endpoint, MSI 00
                            Capabilities: [a0] MSI: Mask- 64bit+ Count=1/1 Enable-
                            Capabilities: [100] Vendor Specific Information <?>
                            Kernel driver in use: fglrx_pci
                            Kernel modules: fglrx

                            edit: too late. well. you found what you were looking for.
                            Last edited by energyman; 01-31-2009, 07:40 AM.

                            Comment


                            • #74
                              &quot;ASIC hang&quot; with Catalyst 9.1

                              Shortly after updating from 8.12 to 9.1 (on Linux 2.6.28.2) I left
                              my Thinkpad for a while with xscreensaver running. I came back to
                              find a black screen and no way of getting control back. In the
                              system log I found:

                              Loading at 14:11:36

                              Code:
                              [fglrx] Kernel PAT support detected, disabling driver built-in PAT support
                              [fglrx] module loaded - fglrx 8.57.2 [Jan 14 2009] with 1 minors
                              [fglrx] Firegl kernel thread PID: 4015
                              [fglrx] Gart cacheable size:1008 M.
                              [fglrx] Reserved FB block: Shared offset:0, size:1000000 
                              [fglrx] Reserved FB block: Unshared offset:fef9000, size:102000 
                              [fglrx] Reserved FB block: Unshared offset:fffb000, size:5000
                              Problem at 16:13:41

                              Code:
                               [fglrx] ASIC hang happened
                               Pid: 11928, comm: glknots Tainted: P		2.6.28.2 #2
                               Call Trace:
                                [<f8872869>] firegl_hardwareHangRecovery+0x19/0x30 [fglrx]
                                [<f88fafdb>] _ZN4Asic9WaitUntil15ResetASICIfHungEv+0xb/0x20 [fglrx]
                                [<f88faf77>] _ZN4Asic9WaitUntil15WaitForCompleteEv+0x97/0xf0 [fglrx]
                                [<f88f9f63>] _ZN4Asic19PM4ElapsedTimeStampERK23PM4_TS_INTERRUPT_PARAMSj14_LARGE_INTEGER+0x1c3/0x200 [fglrx]
                                [<f88d6176>] QSSubmitList+0x56/0x170 [fglrx]
                                [<f888f79d>] firegl_trace+0x3d/0x1c0 [fglrx]
                                [<f887e824>] gal_get_map_info+0x34/0x80 [fglrx]
                                [<f88ec0c0>] _Z19uQSTimeStampRetiredjjj14_LARGE_INTEGER+0xf0/0x100 [fglrx]
                                [<f88e8c99>] _Z8uCWDDEQCjjjPvjS_+0x359/0x1260 [fglrx]
                                [<f88d5794>] CMMQS_uCWDDEQC+0x34/0x40 [fglrx]
                                [<f88923a6>] firegl_cmmqs_CWDDE_32+0x3d6/0x4b0 [fglrx]
                                [<c01c64a6>] dx_probe+0x156/0x330
                                [<f889094a>] firegl_cmmqs_CWDDE32+0x8a/0x140 [fglrx]
                                [<f88908c0>] firegl_cmmqs_CWDDE32+0x0/0x140 [fglrx]
                                [<f886d73d>] firegl_ioctl+0x22d/0x2b0 [fglrx]
                                [<c01c64a6>] dx_probe+0x156/0x330
                              last message repeated 2 times
                                [<f88626c7>] ip_firegl_ioctl+0x17/0x20 [fglrx]
                                [<c01c64a6>] dx_probe+0x156/0x330
                                [<c0186290>] vfs_ioctl+0x80/0x90
                                [<c0186437>] do_vfs_ioctl+0x67/0x4d0
                                [<c017a627>] vfs_read+0x137/0x140
                                [<c01868dd>] sys_ioctl+0x3d/0x70
                                [<c010341d>] sysenter_do_call+0x12/0x25
                                [<c01c64a6>] dx_probe+0x156/0x330
                               pubdev:0x1f8a32740, num of device:-124439500 , name:<NULL>, major 57, minor 0. 
                               device 0 : 0xf8953434f66a4000 .
                               Asic ID:0x71d4, revision:0x47, MMIOReg:0x8f8540000.
                               FB phys addr: 0xd0000000, MC :0xc0000000, Total FB size :0x10000000.
                               gart table MC:0x0, Physical:0x0, size:0x0.
                               mc_node :FB, total 1 zones
                                  MC start:0xc0000000, Physical:0xd0000000, size:0x10000000.
                                  Mapped heap -- Offset:0x0, size:0xfef9000, reference count:7, mapping count:0,
                                  Mapped heap -- Offset:0x0, size:0x1000000, reference count:1, mapping count:0,
                                  Mapped heap -- Offset:0xfef9000, size:0x102000, reference count:1, mapping count:0,
                                  Mapped heap -- Offset:0xfffb000, size:0x5000, reference count:1, mapping count:0,
                               mc_node :GART_CACHEABLE, total 3 zones
                                  MC start:0x7fc00000, Physical:0x0, size:0x401e9000.
                                  Mapped heap -- Offset:0xd00000, size:0x100000, reference count:2, mapping count:0,
                                  Mapped heap -- Offset:0x900000, size:0x400000, reference count:2, mapping count:0,
                                  Mapped heap -- Offset:0x200000, size:0x700000, reference count:3, mapping count:0,
                                  Mapped heap -- Offset:0x0, size:0x200000, reference count:7, mapping count:0,
                               Dump the trace queue.
                               End of dump
                              I never saw anything like this with 8.12, which I've been using since
                              it was released.

                              Comment


                              • #75
                                Oh cool; looks like we're starting to get hang recovery and debugging info into fglrx.

                                Comment

                                Working...
                                X