Ticket #350 (closed defect: ignored)
Running gnome-display-properties with fglrx loaded causes X to spin
| Reported by: | jdreed | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Upstream Utopia |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: | LP:366687 |
Description
If I choose to enable "Restricted drivers" (as many people will), and then later try and go to System->Preferences->Display, Xorg will take up 100% of CPU on one core, and the machine becomes unusable (and gnome-display-manager never works). This appears to affect both 755s and 760s (Radeon HD 2400 and 3450 respectively).
Killing gnome-display-manager has no effect, nor does punting Compiz. Rebooting seems to be the only solution. Nothing interesting in the logs.
We should document this or file a bug upstream or something.
Change History
comment:2 Changed 15 years ago by jdreed
Apparently upgrading the the latest fglrx (from ATI, not Ubuntu) fixes this, but I bet we don't want to get back into the business of distributing fglrx ourselves.
We should probably document this for private workstation owners. Are we currently enabling fglrx ("Restricted Drivers") on any of the cluster machines? Or did we just suppress the notifications?
comment:3 Changed 15 years ago by broder
We are currently not enabling any restricted drivers on any cluster machines, and just suppressing the notifications (see r23869).
That being said, I'd like to turn on restricted drivers if I can figure out how, because that makes it possible to actually get fancy graphics out of compiz on ATI cards, etc.
comment:4 Changed 15 years ago by broder
Do we know which fglrx ended up in Karmic? Will it be new enough? (If not, can we try to get a FeatureFreeze? Exception to get it in?)
