Results 1 to 7 of 7

Thread: Lockups with RSS-GLX screensavers

  1. #1
    Join Date
    Dec 2007
    Location
    United Kingdom
    Posts
    54

    Unhappy Lockups with RSS-GLX screensavers

    It seems every time I test one of the RSS-GLX screensavers (http://rss-glx.sourceforge.net/ if they're not already packaged for your distro) with fglrx, it displays for a few seconds, but then either the screen freezes or turns off, and I have to hard reset my computer.

    I haven't yet tested every one, but I've had lockups so far with lattice and skyrocket. Also, not RSS-GLX, but clicking in the fireflies screensaver (http://somewhere.fscked.org/fireflies/) locks up.

    I ran through each one with mesa r300 dri, and they all worked fine, some not particularly fast, but hey, they don't lockup the system.

    I have a Radeon 9550 in a AGP 4X SiS 650 based motherboard, most recently running Fedora 8 with vanilla kernel 2.6.24.2 and X Server 1.4.0.90. All recent fglrx, 7-11 to 8-2 are affected.

    Can anyone confirm this? Is it limited to r300 class hardware? Or just 9550? Or just me?

  2. #2
    Join Date
    Feb 2008
    Posts
    11

    Default

    I'm having exactly the same problem, is also happening with UT2004, but with an X1800XT on a MSI K9N Ultra. Using 8.2 on Debian Sid/Sidux, 2.6.24.2 kernel, xorg 7.3. It was the same with 8.1, but not with 7.12 or earlier as far as I recall.

  3. #3
    Join Date
    Feb 2008
    Posts
    11

    Default

    After a lot of tweaking with xorg.conf and countless lockups, I've managed to stop the lockups with OpenGL apps (*crosses fingers*). It seems that using Compiz or any of the xorg.conf settings for it (Textured2D, TexturedXrender, RENDER, DAMAGE, etc) causes immediate lockups, and not disabling BlockSignalsOnLock and enabling XAANoOffScreenPixmaps causes lockups after 1-2 minutes.

    Here's my xorg.conf that appears to be working:
    Code:
    Section "ServerLayout"
            Identifier      "Xorg Configured"
            Screen          "Screen 0"
            InputDevice     "Keyboard 0"
            InputDevice     "Microsoft Microsoft Wireless Optical Mouse� 1.0A 0"
            Option          "Clone" "off"
            Option          "Xinerama" "off"
            Option          "AIGLX" "off"
    EndSection
    
    Section "ServerFlags"
            Option          "AllowMouseOpenFail"    "true"
    EndSection
    
    Section "InputDevice"
            Identifier      "Keyboard 0"
            Driver          "kbd"
            Option          "CoreKeyboard"
            Option          "XkbRules"              "xorg"
            Option          "XkbModel"              "pc105"
            Option          "XkbLayout"             "gb,us"
            Option          "XkbOptions"            "altwin:super_win"
    EndSection
    
    Section "InputDevice"
            Identifier      "Microsoft Microsoft Wireless Optical Mouse� 1.0A 0"
            Driver          "mouse"
            Option          "Device"                "/dev/input/mice"
            Option          "Protocol"              "Auto"
            Option          "Emulate3Buttons"       "true"
            Option          "CorePointer"
    EndSection
    
    Section "Device"
            Identifier      "Device 0"
            Driver          "fglrx"
            Option          "XAANoOffscreenPixmaps" "on"
            Option          "VideoOverlay" "on"
            Option          "TexturedVideo" "on"
            Option          "TexturedVideoSync" "on"
    #       Option          "Textured2D" "on"
    #       Option          "TexturedXrender" "on"
            Option          "UseFastTLS" "2"
            Option          "MaxGARTSize" "512"
            Option          "BlockSignalsOnLock" "off"
    #       Option          "BackingStore" "on"
            BoardName       "ATI Technologies Inc R520 [Radeon X1800]"
            BusID           "PCI:6:0:0"
    EndSection
    
    Section "Monitor"
            Identifier      "Monitor 0"
            ModelName       "Default Monitor"
            Option          "DPMS" "true"
    EndSection
    
    Section "Screen"
            Identifier      "Screen 0"
            Monitor         "Monitor 0"
            DefaultColorDepth 24
            SubSection "Display"
                    Depth   8
            EndSubSection
            SubSection "Display"
                    Depth   15
            EndSubSection
            SubSection "Display"
                    Depth   16
            EndSubSection
            SubSection "Display"
                    Depth   24
            EndSubSection
    EndSection
    
    Section "DRI"
            Mode 0666
    EndSection
    
    Section "Extensions"
            Option          "RENDER" "Disable"
            Option          "DAMAGE" "Disable"
            Option          "Composite" "Disable"
    #       Option          "XVideo" "Enable"
    EndSection

  4. #4
    Join Date
    Dec 2007
    Location
    United Kingdom
    Posts
    54

    Default

    I did some further testing, and it's only these 3 screensavers that lockup:

    rss-glx-lattice
    rss-glx-skyrocket
    fireflies

    I'll just stick with the open source drivers for now.

  5. #5
    Join Date
    Feb 2008
    Posts
    11

    Default

    I'll be joining you on that, I spoke too soon earlier - after 20-30+ mins getting massive amounts of 3D glitches (looks like a frikking laser show) and 'soft lockups', X taking up 100% CPU and needing to be killed. After starting up X again, mouse cursor animation/transparency, anti-aliasing of images and gamma on icons etc all disappeared, needing a re-install of fglrx to get them back.

    There wasn't anything in the tail of the Xorg log that was any different from the current log:
    Code:
    Warning: LookupDrawable()/SecurityLookupDrawable() are deprecated.  Please convert your driver/module to use dixLookupDrawable().
    Receive 3D performance mode message with status: 00000001
    Receive 3D performance mode message with status: 00000000
    Receive 3D performance mode message with status: 00000001
    Receive 3D performance mode message with status: 00000000
    Receive 3D performance mode message with status: 00000001
    Receive 3D performance mode message with status: 00000000
    Receive 3D performance mode message with status: 00000001
    Receive 3D performance mode message with status: 00000000
    Receive 3D performance mode message with status: 00000001
    Receive 3D performance mode message with status: 00000000
    (Can't post whole log due to posting restrictions...)

    I'm done with experimenting as I think another few lockups will fsck my hard drives.

    In the name of science, I fired up UT2004 on my XP partition @ 1680x1050 with the graphics settings maxed out, played for an hour and everything was just fine and dandy...

  6. #6
    Join Date
    Dec 2007
    Location
    United Kingdom
    Posts
    54

    Default Same with 8.3

    Exactly the same behaviour with 8-3, bug 1061 filed at http://ati.cchtml.com/show_bug.cgi?id=1061 .

  7. #7
    Join Date
    Jun 2007
    Posts
    69

    Default

    confirmed by me too.. catalyst 8.3 on R520 any GL screensaver freezes the computer

Posting Permissions

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