I've recently bought my G14 and didn't experience the CPU power drop mentioned here: https://bbs.archlinux.org/viewtopic.php?id=248477 Now, this might be because I used an existing installation (by swapping in my old SSD), but the reported thread is about the ASUS G GA502DU, which is a different laptop. Has this issue actually been observed on the G14? (no offence intended, honest question) Sebb767 (talk) 20:18, 12 August 2020 (UTC)
- I was playing GTA 5 when the problem occurred. lscpu showed that the CPU freq was 400MHz. I guess maybe it happens only under high load. YHNdnzj (talk) 14:53, 15 August 2020 (UTC)
- In that case it makes sense to leave it alone, as the patch surely does not hurt. However, this might be a scheduler problem, see here: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#CPU_frequency_governor Sebb767 (talk) 15:31, 15 August 2020 (UTC)
Outdated information - needs update
Please do not use this wiki article, as long as it's providing outdated information and no longer appliable hooks.
Please see: https://asus-linux.org for further information and howtos. (and be so kind and update this wiki article accordingly)
- rog-core (deprecated)
- manual linux kernel patch (deprecated)
- direct links to rapid changing repos
- PowerManagemnt (dGPU)
- missing GPU setupguide
- missing hardware like Touchpad
Next time it would be better to ask the guys who build all this stuff ontop on ASUS Zephyrus G14/15 directly before starting such a wiki-article. (feel free to join our discord: https://discord.gg/PVyFzWj)
- asus-nb-ctrl is not in the AUR yet. I'll update this article as soon as it gets submitted.
- I don't see manual patching as an issue.
- There is already a page containing information about NVIDIA Optimus.
- Libinput is required by and works out of the box. is deprecated on Arch Linux.
Added asus-nb-ctrl-git to AUR. Let me know if I misclassified any dependencies. Relies on the DKMS module from asus-linux instead of kernel patches.
Quick question, in the pacman hook section why are you reading the patch into the patch utility through stdin? Wouldn't it be faster to just use the input (-i) flag? (I've tested it and it seems like the answer is yes.)
Also, that patch, while it follows the Asus-Linux guide, only allows what I assume to be the bottom 2 speakers work. To get the treble, or what I assume is the top two speakers, to work properly the "Master" and "Speaker" elements must be at 100 in ALSA.
This was step 87 for me but you can check with
amixer -c N. I'm not sure the repercussions of these modifications so I'm not going to propose them just yet but I would like to hear how this works for other people.
[Element Hardware Master] switch = mute volume = 87 [Element Master] switch = mute volume = 87 [Element Speaker] required-any = any switch = mute volume = 87 override-map.1 = all override-map.2 = all-left,all-right
For me, the volume slider seems to only control the "Tweeters", while the "Subs" stay at the same volume. I'll play around with it, maybe I find a solution.
I recommend using alsamixer to adjust the channels individually. That's how I isolated the issue to the Speaker and Master channels.