Re:EPA Plans to Shut Down the Energy Star Program
by mrandish on Wednesday May 07, 2025 @01:39PM
(#43918556)
I've had problems with modern monitors shutting themselves off if they don't detect a signal in something like five or ten seconds, which is far too short when I'm trying to debug a PC having boot issues, configure a multi-monitor setup (like a 3-screen virtual pinball cabinet) or even just figure out which HDMI cable is which on the PC end. I don't mind the auto-off feature but the incredibly short time period is unnecessary and the delay time isn't adjustable (at least on the LG monitors I have).
This over-aggressiveness turns a good feature into a problem forcing me to completely disable power saving. Which is sad because the biggest savings of the feature are when a screen is left on for hours when the PC is off or disconnected (which I don't do anyway, as the entire system is on a smart power strip). A monitor should hunt for a valid signal for at least 45 or 60 seconds by default before auto-offing itself.
Another "power saving gone awry" issue is that USB selective suspend can cause wireless mice to stutter after not moving for just a few seconds. I think this is due to lag in the wake-up time. Unfortunately, the interface doesn't have any time adjustment, so I have to just turn selective suspend.
Re:EPA Plans to Shut Down the Energy Star Program
by stefanfisk on Wednesday May 07, 2025 @12:45PM
(#43917902)
AFAICT my MBP M1 is energy star certified but has no such issue. Might it just be that the Lenovo has a bad implementation?
Re:EPA Plans to Shut Down the Energy Star Program
by Pwntastic on Wednesday May 07, 2025 @12:25PM
(#43917676)
That sounds like Lenovo just being bad? Certainly they could fix the issue but instead chose the cheaper option.
Re:EPA Plans to Shut Down the Energy Star Program
by anonymousiam on Friday May 09, 2025 @09:40PM
(#43942586)
The cheaper option would have been to not implement the Energy Star feature that dynamically powers the chipset on and off.
I would rather have sound without these issues, even if my computer consumes an extra 100mW at idle to keep the sound system ready.
I'm aware that most sound chipsets allow a user override that keeps the circuits on, but the this newer chipset doesn't seem to implement the feature correctly. No combination of arguments to the linux sound system, or loadable modules seems to keep the sound circuits from switching to standby.