an option to set
min_cap through say /sys (right now param is readonly, even for root).
Thank you in advance for looking into this, with regards: Romano
"""
And while at it, let me add this issue to the tracking as well
[TLDR: I'm adding this report to the list of tracked Lin
ithin vendor's limits) for example and crash the system.
On 2/20/24 19:09, Alex Deucher wrote:
On Tue, Feb 20, 2024 at 11:46 AM Romano wrote:
For Windows, apps like MSI Afterburner is the one to try and what most
people go for. Using it in the past myself, I would be surprised if it
adhered
re, but hassle of whole kernel setup, patching and recompilation on
the user's side.
On 2/20/24 21:18, Alex Deucher wrote:
On Tue, Feb 20, 2024 at 2:41 PM Romano wrote:
If the increased low range is allowed via boot option, like in proposed
patch, user clearly made an intentional dec
for whatever reason.
I don't know how much power you guys have over them, but please
consider either reverting this change, or give us an option to set
min_cap through say /sys (right now param is readonly, even for root).
Thank you in advance for looking into this, with regards: Romano
&quo
9, Alex Deucher wrote:
On Wed, Feb 21, 2024 at 1:06 AM Linux regression tracking (Thorsten
Leemhuis) wrote:
On 20.02.24 21:18, Alex Deucher wrote:
On Tue, Feb 20, 2024 at 2:41 PM Romano wrote:
If the increased low range is allowed via boot option, like in proposed
patch, user clearly made an inte
em a word, cards operate
safely and this could not be missed.
On 2/21/24 16:15, Christian König wrote:
Am 21.02.24 um 07:06 schrieb Linux regression tracking (Thorsten
Leemhuis):
On 20.02.24 21:18, Alex Deucher wrote:
On Tue, Feb 20, 2024 at 2:41 PM Romano wrote:
If the increased low range
