<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - After boot, the APU is powered with its maximum voltage (trinity/ARUBA)" href="https://bugs.freedesktop.org/show_bug.cgi?id=67982#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - After boot, the APU is powered with its maximum voltage (trinity/ARUBA)" href="https://bugs.freedesktop.org/show_bug.cgi?id=67982">bug 67982</a> from <a class="email" href="mailto:laszlo.kertesz@gmail.com" title="Kertesz Laszlo <laszlo.kertesz@gmail.com>"> Kertesz Laszlo</a> <pre>I did some more poking and i found that setting the cpu governor to "conservative" i get correct voltage handling at bootup after logging into lightdm. But if i restart lightdm and log in, it will get stuck at the 1.34-1.36 levels. With ondemand after boot i always had (maybe 1 or 2 exceptions) the 1.34 and 1.36 voltage levels. Its weird that in that state changing to a vt and back sometimes elevates the voltage to 1.44v and keep it there. I also removed and loaded again the acpi-cpufreq driver - after unloading, the voltage is a fixed (it seems) 1.15v, after loading it again it jumps to 1.34 and stays there (or goes up to 1.36 and back sometimes) until i turn dpms force off and on the monitor, after which it starts to change the voltage levels correctly.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>