Arch Linux User Repository

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

@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...

I did some debugging, and for my laptop asus wmi is not responsible at all for any battery stuff but the ACPI interface is. For my laptop its not used at all, BAT0 is added with acpi, it doesnt matter what I write in asus_wmi.

So if you're not having any positive results I'm probably going to revert, it's probably not worth it then.

uhm okay,

can you try

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

with pacman -U?

No need to spam other people for this. :-)

The batttery is not using the thresholds,,the file exists but there is no working limits. Don't know why. Can you put another package with the only change I said before with no backware compability . It is to see if it is working well without the backwards compatibility

Yes repo is always synced with AUR. I hope my backwards compatible move worked but I think it did. My asus laptop uses BAT0 and the wmi interface still seems to work.

@eggz is in your repo, no? I will try this afternoon because I am busy and the laptop is from my girlfriend. I was seeing how to do it in the moment u have read it, much thanks eggz. Anyways I have discovered that patch the kernel with only one line is so easy. The only thing is that after that I have to compile with a core 2 duo... XD