Summary: | Module *radeon* takes over two seconds to load | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Paul Menzel <paulepanter> | ||||
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||
Status: | RESOLVED NOTABUG | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | medium | CC: | paulepanter, pmenzel+bugs.freedesktop.org | ||||
Version: | DRI git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Paul Menzel
2018-06-17 08:13:07 UTC
Just to put this into perspective, that without loading the radeon module, the OS, that means Linux kernel + user space, takes around two to three seconds to start (substracting the LUKS passphrase dialog). Is that a firmware or hardware problem? That is expected behavior. Because of stability issues we don't enable power management during startup initially which makes the hardware run at it's default clock (usually between 17 and 100MHz) during startup. Is there a switch to override that behavior? (In reply to Paul Menzel from comment #4) > Is there a switch to override that behavior? Long story short, no there isn't. You could try to disable certain blocks with radeon.uvd=0 and radeon.vce=0 to speed up boot a bit if you don't need that functionality. But that's basically all you can do without implementing a different approach to power management. |
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.