Summary: | HD 3650: Couldn't find valid PLL dividers | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Tormod Volden <bugzi11.fdo.tormod> | ||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | stephan | ||||
Version: | unspecified | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
URL: | https://bugs.launchpad.net/bugs/336348 | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Tormod Volden
2009-03-04 05:39:38 UTC
Created attachment 23513 [details]
Xorg.0.log
should be fixed in 592bcac52f113a95923a8f1cb8427e7552d5670b This problem is present with Ubuntu 8.10, Ubuntu 9.04 alpha 5 as well as OpenSolaris 2008.11, OpenSolaris 2009.06 Build 108 on Toshiba A350 64 bit. The patch does not work, according to two different testers in the Ubuntu report. (In reply to comment #4) > The patch does not work, according to two different testers in the Ubuntu > report. > bad mode or the same error? Sorry for not being more descriptive. Yes, it is the same error. Are you sure the patch was applied and the packages were updated properly? It should definitely find a set of PLL dividers. I've tested it here and it works properly. One tester now got the installation right, confirmed by the log, and it shows that the PLL issue is fixed. However, now it blocks on repeated (EE) RADEON(0): Idle timed out, resetting engine... but he will file a new bug on that issue. This seems to have been fixed now, but a comment in https://bugs.launchpad.net/bugs/341681 says: "Also with 2GB of RAM the PLL rd parameter is 12, but with 4GB of RAM the PPL rd parameter is 1023. Maybe the PLL divider bug wasn't really a bug after all..." BTW, for reference, the new "resetting engine" bug was filed as bug 20645. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.