Trinity Laptop support
Still no joy on my Asus N56DP with either the open source or proprietary drivers.
On open source driver:
The display doesn't return on Resume after suspend.
No power management, laptop runs hot and battery is drained in less than 90 minutes.
I'm using Catalyst now because at least that has power management, but it also doesn't Resume successfully. It also doesn't even Suspend successfully, most of the time.
Is anyone else having any luck with either of these drivers on a recent Trinity laptop?
The open source driver works well on the trinity laptop I have at the moment (HP Probook 6475b).
I suppose that works well because the Probook has no discrete GPU. The Asus has a discrete HD 7730M in addition to the iGPU. Pretty sure the power problem is because both GPUs are active, there's no tool to turn one or the other on or off.
With Catalyst I can use the control center to select one or the other. Even with Catalyst if I just boot into text mode, the temperature rises rapidly; it seems that the GPU configuration doesn't happen until X loads up. Frankly I would have expected the default boot-up mode to leave only one or the other active, regardless of whether X is running.
You can use vgaswitcheroo to handle the GPUs in hybrid/powerxpress laptops.
Thanks for the tip. I uninstalled catalyst again and reinstalled the radeon driver, and reenabled KMS. So I see /sys/kernel/debug/vgaswitcheroo and it appears to work. At boot, both cards are on. Doing an "echo OFF > switch" seems to turn off the discrete card ok. However, after that, lm-sensors reports
Adapter: PCI adapter
while before, it was reporting a plausible temperature.
The CPU is reporting 42C which is an improvement over the 56C it was at before, but still nowhere near as good as the 27C that it shows when using catalyst. powertop reports 26.2W and battery life of 2 hours 7 minutes, so this is still 2x worse than with catalyst.
Also, the screen is still black (no backlight) after a resume from suspend.
Note that reading back the temperature from a disabled device doesn't work since the device is disabled. You can ignore it.
Right, that's fine. It wasn't important to begin with. What matters is successful resume, and lowering the overall power consumption.
Originally Posted by agd5f