Might make sense to red-flag the post and ask to have the email addy removed...
"Ask ATI" dev thread
Collapse
X
-
Originally posted by monraaf View PostYeah I'll use that as a workaround. Would be nice if Michael finally fixes this bug that prevents you from editing your own posts though.
Seriously -- as I understand it the edit window was deliberately cut down to make it harder for spammers.Test signature
Comment
-
-
Originally posted by bridgman View PostIt's not a bug, it's a feature
Seriously -- as I understand it the edit window was deliberately cut down to make it harder for spammers.
As for monraaf's remark, yes they can be used with openSUSE. That's what the installer refers to with SuSE/SUSE, in contrast with SuSE/SLE which is for the commercial version. 10.7 adds support for openSUSE 11.3
@lukem33p
openSUSE's wiki page about the catalyst drivers. In all fairness, the page history shows it was updated on the 6th of august to reflect 11.3 changes. However it would still be interesting to know where you got your information.
Since you seem to favor ease of installation, was there any reason for you not to use the open source drivers?
Comment
-
-
No Open-Source Hardware Acceleration for Evergreen So I Switched
Originally posted by PsynoKhi0 View PostThen it would make sense to remove that limit once a member has reached a given post count. (Still off-topic but oh well)
As for monraaf's remark, yes they can be used with openSUSE. That's what the installer refers to with SuSE/SUSE, in contrast with SuSE/SLE which is for the commercial version. 10.7 adds support for openSUSE 11.3
@lukem33p
openSUSE's wiki page about the catalyst drivers. In all fairness, the page history shows it was updated on the 6th of august to reflect 11.3 changes. However it would still be interesting to know where you got your information.
Since you seem to favor ease of installation, was there any reason for you not to use the open source drivers?
Another thing: When I took the plunge and used the ATi proprietary (from the ATi site, newest version (10.7), I had a bad time as I am useless at the terminal, and unfortunately that's all the driver left me with. Runlevel 5 skipped some pieces including what was called xdm. Not good. I don't know if it was just me, and in said case I don't care, but I had a similar scenario with previous drivers, RV700, and OpenSuSe 11.2. Seems to be a recurring pattern. Did I miss a step? I'm curious.
Comment
-
-
EDIT!
Originally posted by PsynoKhi0 View PostThen it would make sense to remove that limit once a member has reached a given post count. (Still off-topic but oh well)
@lukem33p
openSUSE's wiki page about the catalyst drivers. In all fairness, the page history shows it was updated on the 6th of august to reflect 11.3 changes. However it would still be interesting to know where you got your information.
Since you seem to favor ease of installation, was there any reason for you not to use the open source drivers?
Comment
-
-
Where are users suppose to report fglrx bugs to?
I've searched the amd/ati website for where you can report bugs and have not found where i can report an issue. If your interested its:
sleep 1; xset dpms force off ; sleep 10; xset dpms force on
This should and does work with ati open source driver, but with fglrx it does not completly wake up from sleep. I think this would take one of your engineers like 2 minutes to fix this. In any case i would still like to know where you are suppose to report bugs officially. Its the last part of this that is the concern, when my screen saver goes off on htpc I want it to wake on remote keypress, the remote keypress runs xset dpms force on and should turn back on the screen but it does not, at least with the property driver.
Comment
-
Comment