blob: 3b51c3c01cf2385b5fae4b7318ed72c3e0fff5df (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
### `linux-xanmod-rog`
This is an Arch linux `linux-xanmod` derived kernel with hardware enablement patches for ASUS ROG laptops.
### Notes:
- Xanmod builds with the performance governor by default; this is great for performance but doesn't clock down easily and reduces battery life when used on mobile devices. Since this kernel package is primarily targeted at ROG laptop users I've switched the build config to default to the schedutil governor. I strongly suggest making a couple of bash aliases to make switching modes/governors easier, this allows you to easily boost performance or conserve battery power as needed.
* `alias gosilent='(set -x; asusctl profile silent -t false -f silent; sudo cpupower frequency-set -g schedutil >&/dev/null;)'`
* `alias gonormal='(set -x; asusctl profile normal -t true -f normal; sudo cpupower frequency-set -g schedutil >&/dev/null;)'`
* `alias goboost='(set -x; asusctl profile boost -t true -f boost; sudo cpupower frequency-set -g performance >&/dev/null;)'`
* Eg: To switch performance profiles during a kernel build you'd run something like: `goboost; makepkg -Ccsr; gonormal`
- Use the included `myconfig` script fragment to make minor changes to the kernel configuration during build.
- We now build for the `x86-64-v3` target by default; this supports Haswell era and newer CPUs and should be ~10% more performant than a generic `x86_64` build while maintaining wide compatibility. This supports all recent ROG laptops, including Intel machines.
- Package now requires GCC >= 11 to support the new default build target.
- Suggested architecture build targets:
* `_microarchitecture=14 makepkg ...` Zen2 optimization; AMD 4000 series CPUs, 2020 AMD ROG laptops
* `_microarchitecture=15 makepkg ...` Zen3 optimization; most AMD 5000 series CPUs, 2021 AMD ROG laptops
* `_microarchitecture=38 makepkg ...` Skylake optimization; Use this on [Comet Lake](https://wiki.gentoo.org/wiki/Safe_CFLAGS#Skylake.2C_Kaby_Lake.2C_Kaby_Lake_R.2C_Coffee_Lake.2C_Comet_Lake) machines
* `_microarchitecture=92 makepkg ...` x86-64-v2; compatible with most machines from 2008 onward
* `_microarchitecture=93 makepkg ...` x86-64-v3; the PKGBUILD default, most machines from 2013/2014 onward are supported
* `_microarchitecture=98 makepkg ...` Intel -march=native
* `_microarchitecture=99 makepkg ...` AMD -march=native
- GA503Q models hava an ACPI DSDT table bug in all currently available BIOS that prevents the machine from suspending correctly.
Errors generated by this will look like the following in `dmesg` or the system journal:
```log
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: I/O 460 QID 3 timeout, aborting
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: I/O 461 QID 3 timeout, aborting
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: I/O 462 QID 3 timeout, aborting
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: I/O 463 QID 3 timeout, aborting
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: I/O 0 QID 0 timeout, reset controller
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: Abort status: 0x371
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: Abort status: 0x371
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: Abort status: 0x371
Jun 19 18:56:26 arch-zephyrus kernel: nvme nvme0: Abort status: 0x371
```
See this project on github to produce an ACPI override ramdisk that works around the issue while you wait for ASUS to publish a fixed BIOS:
https://github.com/foundObjects/GA503QR-StorageD3Enable-DSDT-Patch
If you're experiencing this yourself *please* go make a vendor support ticket with ASUS and ask them to fix their BIOS.
- UKSM is an optional feature in the PKGBUILD for those that want to use it. Now that lru_gen is available I no longer recommend using UKSM.
* WARNING: Do *not* turn on UKSM and the multigenerational LRU together at runtime. The PKGBUILD disables automatic lru_gen when UKSM is included in the build, switching both on at runtime is practically guaranteed to crash your system.
See the commit log for full version history and changes.
[//]: # ( vim: set tw=120: )
|