Warning: Woeful whining (wearisome)
I don't even get a black window... I just get a total freeze up. The screen tends to get diagonal tears (~30 deg off horizontal w/ green or pink pixels) in a checkerboard across the screen (sometimes there aren't even tears warning me of what just happened). Mouse movement is operational up to a point. Most of the time it freezes up with the next mouse click but allows me to switch to a TTY terminal via the keyboard; however, recently I've simply lost all ability to do anything but stare at an eerily frozen screen after ANY interaction (save for the mouse movement available before any other form of keyboard/mouse interaction) during the tears. This occurs almost at random, but with higher frequency at higher resolutions, and I'm pretty sure only when I run my browsers or, most recently, the SDL-based-game Abuse (just some subjective observations).
This tends to happen with either Chrome or Firefox running, and I'm starting to think that it possibly has something to do with flash more than the actual browser.
Xorg logs point at segfaults within the fglrx driver having something to do with RandR and suspend state and something or another. I can provide it if anyone's interested?
Also, resizing to larger resolutions results in the new real-estate being totally pixelated and tiled up in black/white/colorful-lsd-induced-colors. I can still interact with the screen however (even under the mask of colored craziness, input seems to work).
System specs in case anyone cares (also because the ATI bugzilla still doesn't have 10.7 up as an option for reporting, so I might as well here...):
OS: Ubuntu 10.04 (64-bit)
Mobo: MSI 890FXA-GD70
CPU: AMD Phenom II X6
GPU: 2x ATI Radeon HD 5970 (not crossfired for future OpenCL purposes)
PSU: 1200 Watts (hellz yes.)
Using one screen on the DVI output of one card.
^ And that's all that matters in this case (haha - pun), really, yes?
This'd all work in Windows, though, probably, right...? I really don't want to resort to using it, but if that's what it takes to make it *work* (with OpenCL mind you)...
Heck, if all I get is a black window bug, I'll be happy... I just wanna program the darned thing and have it run a long simulation without intermittently going caput. >_<
Things I'm gonna try (not necessarily in this order):
~ uninstall flash and navigate the web with firefox & chrome to see if it crashes (see if flash does something weird to trigger it)
~ crossfire both cards
~ disconnect one of the cards (try with both of em' individually)
~ disconnect the wireless card (which I had problems with before in weird conflicting ways with the graphics card during installation - can give limited details if wanted)
~ *wait for possibly positive forum response*
~ start using the OSS drivers when they're available, assuming they support OpenCL...
~ resort to M$ Windoze... *sigh*
Any advice? (Should I have made this a separate topic?)
~ Thanks
I don't even get a black window... I just get a total freeze up. The screen tends to get diagonal tears (~30 deg off horizontal w/ green or pink pixels) in a checkerboard across the screen (sometimes there aren't even tears warning me of what just happened). Mouse movement is operational up to a point. Most of the time it freezes up with the next mouse click but allows me to switch to a TTY terminal via the keyboard; however, recently I've simply lost all ability to do anything but stare at an eerily frozen screen after ANY interaction (save for the mouse movement available before any other form of keyboard/mouse interaction) during the tears. This occurs almost at random, but with higher frequency at higher resolutions, and I'm pretty sure only when I run my browsers or, most recently, the SDL-based-game Abuse (just some subjective observations).
This tends to happen with either Chrome or Firefox running, and I'm starting to think that it possibly has something to do with flash more than the actual browser.
Xorg logs point at segfaults within the fglrx driver having something to do with RandR and suspend state and something or another. I can provide it if anyone's interested?
Also, resizing to larger resolutions results in the new real-estate being totally pixelated and tiled up in black/white/colorful-lsd-induced-colors. I can still interact with the screen however (even under the mask of colored craziness, input seems to work).
System specs in case anyone cares (also because the ATI bugzilla still doesn't have 10.7 up as an option for reporting, so I might as well here...):
OS: Ubuntu 10.04 (64-bit)
Mobo: MSI 890FXA-GD70
CPU: AMD Phenom II X6
GPU: 2x ATI Radeon HD 5970 (not crossfired for future OpenCL purposes)
PSU: 1200 Watts (hellz yes.)
Using one screen on the DVI output of one card.
^ And that's all that matters in this case (haha - pun), really, yes?
This'd all work in Windows, though, probably, right...? I really don't want to resort to using it, but if that's what it takes to make it *work* (with OpenCL mind you)...
Heck, if all I get is a black window bug, I'll be happy... I just wanna program the darned thing and have it run a long simulation without intermittently going caput. >_<
Things I'm gonna try (not necessarily in this order):
~ uninstall flash and navigate the web with firefox & chrome to see if it crashes (see if flash does something weird to trigger it)
~ crossfire both cards
~ disconnect one of the cards (try with both of em' individually)
~ disconnect the wireless card (which I had problems with before in weird conflicting ways with the graphics card during installation - can give limited details if wanted)
~ *wait for possibly positive forum response*
~ start using the OSS drivers when they're available, assuming they support OpenCL...
~ resort to M$ Windoze... *sigh*
Any advice? (Should I have made this a separate topic?)
~ Thanks
Comment