Arch Linux User Repository

Hi

I have adopted this package and have updated it!

Thanks!

GCC13.1 is mainlined in arch, so this means znver4 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver4 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver3 based hardware, please use linux-amd-znver3
If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

GCC11.1 is mainlined in arch, so this means znver3 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver3 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :

[linuxkernels]
Server = http://nhameh.ovh/$repo/$arch
SigLevel = Optional TrustAll

It should be accepting at least the limits on the charge. Try in Windows if you can please if not. Pls give info in that link. https://gist.github.com/klausenbusk/643f15320ae8997427155c38be13e445

@agm yeah about being busy, I know the feeling :) Im working on it now.

I have a GL702ZC, it was the first ryzen laptop for ASUS, So I think they gave it a B treatment back then. (it shipped with a broken BIOS, and they updated it later...)

@eggz both of them were working good :) sorry for the late response i have been very busy these days. I am now having the file that control the charges and the limits are working with the backwards compability. What asus are you using? it is something weird that your asus wmi doesn't control the battery

Can you say if it was the dirty BATT override (-3 http://nhameh.ovh/linuxkernels_archive/linux-amd-5.5.v.4-3-x86_64.pkg.tar.xz, http://nhameh.ovh/linuxkernels_archive/linux-amd-headers-5.5.v.4-3-x86_64.pkg.tar.xz) or the backwards compatibility one (-2 http://nhameh.ovh/linuxkernels_archive/linux-amd-5.5.v.4-2-x86_64.pkg.tar.xz, http://nhameh.ovh/linuxkernels_archive/linux-amd-headers-5.5.v.4-2-x86_64.pkg.tar.xz) that worked? I really liked my way better...

I never had the file so asuswmi is not working for my hardware at all. But I can patch it for other people like you.

@eggz sorry. Put the patch of Asus again with you backwards compability please. The limits of the battery were working good. But only 80, 60 and 100 percent values are accepted, with other values the laptop just ignore them. Try to edit that file. You will get limits on your battery charge.

@eggz Sorry, noob fault. I didn't reboot. Now It worked perfect! thanks!

@dunkiper

is this virtualbox-host-dkms-6.1.2-1-x86_64 ?

Nevermind what I said (without looking, silly me!), it seems to be working for me; ==> dkms install vboxhost/6.1.2_OSE -k 5.5.4-AMD (no errors)

Did you reboot after installing the headers/kernel and then install the dkms??

@agm i have /sys/class/power_supply/BAT0/ but not the charge_* file. I had placed debug messages down in the asus wmi module, and it is not finding/adding batteries at all. The only section that does something is the initialisement. So asuswmi doesnt work/do anything on my laptop aswell.

I have BAT0 according to the generic acpi module.

It seems asus wmi only supports specific laptop models. I think im going to delete the patch as this seems pointless.

@dunkiper it seems the vboxdrv does not support structleak, a proven vulnerability. I have serveral other dkms modules (3+) on other systems that work fine, so this seems a specific vbox-dkms issue (why am I not supprised...) with unsafe struct declarations.

Ill have a look at it anyway to see if it can be mitigated.

I tried to install your packages linux-amd and linux-amd-headers, but then virtualbox DKMS says this:

==> dkms install vboxhost/6.1.2_OSE -k 5.5.4-AMD Error! Bad return status for module build on kernel: 5.5.4-AMD (x86_64) Consult /var/lib/dkms/vboxhost/6.1.2_OSE/build/make.log for more information.

In the log says something like this:

make: se entra en el directorio '/usr/lib/modules/5.5.4-AMD/build' AR /var/lib/dkms/vboxhost/6.1.2_OSE/build/built-in.a CC [M] /var/lib/dkms/vboxhost/6.1.2_OSE/build/vboxdrv/linux/SUPDrv-linux.o CC [M] /var/lib/dkms/vboxhost/6.1.2_OSE/build/vboxdrv/SUPDrv.o CC [M] /var/lib/dkms/vboxhost/6.1.2_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o CC [M] /var/lib/dkms/vboxhost/6.1.2_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o cc1: error: incompatible gcc/plugin versions cc1: error: no se puede inicializar el plugin ./scripts/gcc-plugins/stackleak_plugin.so cc1: error: incompatible gcc/plugin versions cc1: error: no se puede inicializar el plugin ./scripts/gcc-plugins/structleak_plugin.so

I suppose I am doing something wrong or missing something on virtualbox kernel module.

thanks in advance

@eggz It is not working in my girlfriend's laptop. Don't know why, your battery is BAT0 or BATT? if it is BAT0 you can edit in.. nano /sys/class/power_supply/BAT0/charge_end_control_threshold ( the last path I am not very sure) and put the percent you want to have limits on your battery charge. The only thing is happening to my girlfriend is that her laptop is putting the battery in BAT0, not BATT ones. Try it and tell me. It is suppose to work well with asus laptops...