-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zenbook Pro 14 Performance mode & MUX support #1301
Comments
@bunyan-k hello, Does FullSpeed mode have only different fan curve, or also different power limits ? Also it would be good to know if it's specific only to high-end 2023 models or to other ones as well (i don't want to add extra buttons / overload UI for the rest) As for MUX switch try to run it by yourself
And reboot after setting it to 1 or 0 . And check in windows settings what GPU runs internal screen (it should change if it's indeed a MUX) Thanks P.S.
Are you (current) fan speed readings :) |
In short burst, performance and full speed performs pretty much the same (~105w). But both mode hit throttling temp in seconds and bring it down to ~80w, with full speed performing better becauce of fan speed. So whether both modes share the same power limit, or whether they reach the throttle limit at the same time is unknown. Custom fan curve does not work (BIOS rejected) so can't test the two modes with the same fan curve. You might need people with the 16 inch variant for a better answer. I think these 4 modes exist in all trims of this year's Pro14 and Pro16x. I agree that an extra button for just a few rare models might be too much. Hide it in the fan curve page maybe?
These are working as intended. No iGPU activity for value=0. Thanks. |
@bunyan-k oke, thanks for checking. I will add "fallback" to Ultimate mode using your endpoint then. Just need to modify UI logic a bit, as it also expects Eco to exist. Does you device have anything like Eco mode on ROG/TUF (when dGPU is disabled completely) in Proart Creator Hub / MyAsus ? |
Nope, no eco mode. |
@bunyan-k for FullSpeed mode you can try to set it in config actually (w/o any changes in the app code)
To clarify
|
This works well, thank you! |
@bunyan-k try this build for Ultimate / Standard switch |
The buttons are showing the correct mode, but the function itself is not working. |
@bunyan-k can you try this build instead, and post a log after trying to switch in each situation ? |
It's working now! Related logs for your reference:
Performance modes working as intended too. I think we can call this case closed. Thanks. |
@bunyan-k great, I will include it in next release then. |
I can confirm that on K6604 (Vivobook Pro 16X OLED 2023), fan speed does goes to maximum on mode 3. Mode 2 and 3 does have different power limit on GPU (RTX 4060 Laptop) as checked via As for CPU, it seems they are the same on my machine. When Mode 1 is enabled, CPU already has unlimited PL and is mainly constrained by the cooling. During load, fans will ramp up to maximum regardless since core temp is so high. Thanks for finding out. |
First of all, thank you for your wonderful app.
Performance mode selection seems to be working on my Zenbook pro 14 OLED since Vivobooks are added to the support. But on my laptop there's actually 4 performance modes: Whisper (i.e. Slience), Standard, Performance, and Full Speed (not ultimate, still hybrid on the GPU side). There are set in Asus's Proart Creator Hub app.
So I read #1089 and try ran this command with different values:
and these are the values corresponding to different modes, in order of performance and fan noise:
slience = 1
standard = 0
performance = 2
Full speed =3
Would be great if these can be implented to the app. I think proart laptops might benefit from this as well.
=======
Next is the MUX switch. Currently Ghelper cannot detect my laptop has it.
It can be triggered in myASUS app with a reboot.
I ran scan-atkacpi on hybrid GPU mode and ultimate mode. Endpoint 90026 seems to be the only value that is changing.
hybird mode = 1, ultimate = 0
(110014 and 110013 changed too but the values are weird, not sure what are they.)
Not sure what to do next, Happy to help with further tests.
FYI, my system spec:
Zenbook pro 14 OLED UX6404VV 2023
i9-13900H
RTX4060
The text was updated successfully, but these errors were encountered: