Arch Linux User Repository

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

ty for the info onurmercury, I will keep trickeling down these "retrofits", but as you can see with mario, it also introduces breakage, so Im not going to move too fast here. does the kernel atleast work for you (unlike mario) ?

hi, im here again to make more comments :D

vmlinuz-* files are automatically installed by mkinitcpio. so i don't think it's necessary to copy it to /boot at build time.

*.preset files are autogenerated by mkinitcpio too. it's not necessary to create a .preset file at build time either.

and looks like System.map changed its package (kernel to kernel headers), its location and its name.

$ grep -r System.map /var/lib/pacman/
/var/lib/pacman/local/linux-headers-6.6.8.arch1-1/files:usr/lib/modules/6.6.8-arch1-1/build/System.map
/var/lib/pacman/local/linux-amd-znver3-6.6.v.9-1/files:boot/System.map-6.6.9-AMD-znver3

i think you might need to do a clean start from official pkgbuild at some point (or just rebase changes?). for the best ofc.

thx for the effort.

Yes; I use mkinitcpio.

Reinstalling:

[mario@asus-arch ~]$ sudo pacman -S linux-amd-znver3 linux-amd-znver3-headers advertencia: linux-amd-znver3-6.6.v.9-1 está actualizado -- reinstalándolo advertencia: linux-amd-znver3-headers-6.6.v.9-1 está actualizado -- reinstalándolo resolviendo dependencias... buscando conflictos entre paquetes...

Paquetes (2) linux-amd-znver3-6.6.v.9-1 linux-amd-znver3-headers-6.6.v.9-1

Tamaño total de la instalación: 184,83 MiB Tamaño neto tras actualizar: 0,00 MiB

:: ¿Continuar con la instalación? [S/n] s :: Obteniendo los paquetes... linux-amd-znver3-6.6.v.9-1-x86_64 está actualizado linux-amd-znver3-headers-6.6.v.9-1-x86_64 está actualizado (2/2) comprobando las claves del depósito [######################################] 100% (2/2) verificando la integridad de los paquetes [######################################] 100% (2/2) cargando los archivos de los paquetes [######################################] 100% (2/2) comprobando conflictos entre archivos [######################################] 100% (2/2) comprobando el espacio disponible en el disco [######################################] 100% :: Ejecutando los «hooks» de preinstalación... (1/1) Remove upgraded DKMS modules ==> dkms remove --no-depmod nvidia/545.29.06 -k 6.6.9-AMD-znver3 ==> dkms remove --no-depmod openrazer-driver/3.7.0 -k 6.6.9-AMD-znver3 ==> dkms remove --no-depmod zenpower3/0.2.0 -k 6.6.9-AMD-znver3 :: Procesando los cambios de los paquetes... (1/2) reinstalando linux-amd-znver3 [######################################] 100% (2/2) reinstalando linux-amd-znver3-headers [######################################] 100% :: Ejecutando los «hooks» de posinstalación... (1/6) Arming ConditionNeedsUpdate... (2/6) Updating module dependencies... (3/6) Install DKMS modules ==> dkms install --no-depmod openrazer-driver/3.7.0 -k 6.6.9-AMD-znver3 ==> dkms install --no-depmod nvidia/545.29.06 -k 6.6.9-AMD-znver3 ==> dkms install --no-depmod zenpower3/0.2.0 -k 6.6.9-AMD-znver3 ==> depmod 6.6.9-AMD-znver3 (4/6) Updating linux initcpios... ==> Building image from preset: /etc/mkinitcpio.d/linux-amd-znver3.preset: 'default' ==> Using configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-linux-amd-znver3 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-amd-znver3.img ==> Starting build: '6.6.9-AMD-znver3' -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [kms] -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [consolefont] ==> WARNING: consolefont: no font found in configuration -> Running build hook: [block] -> Running build hook: [filesystems] -> Running build hook: [fsck] ==> Generating module dependencies ==> Creating lzop-compressed initcpio image: '/boot/initramfs-linux-amd-znver3.img' ==> Image generation successful ==> Building image from preset: /etc/mkinitcpio.d/linux-amd-znver3.preset: 'fallback' ==> Using configuration file: '/etc/mkinitcpio.conf' -> -k /boot/vmlinuz-linux-amd-znver3 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-amd-znver3-fallback.img -S autodetect ==> Starting build: '6.6.9-AMD-znver3' -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [kms] ==> WARNING: Possibly missing firmware for module: 'ast' -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [consolefont] ==> WARNING: consolefont: no font found in configuration -> Running build hook: [block] ==> WARNING: Possibly missing firmware for module: 'aic94xx' ==> WARNING: Possibly missing firmware for module: 'bfa' ==> WARNING: Possibly missing firmware for module: 'qed' ==> WARNING: Possibly missing firmware for module: 'qla2xxx' ==> WARNING: Possibly missing firmware for module: 'qla1280' ==> WARNING: Possibly missing firmware for module: 'wd719x' -> Running build hook: [filesystems] -> Running build hook: [fsck] ==> Generating module dependencies ==> Creating lzop-compressed initcpio image: '/boot/initramfs-linux-amd-znver3-fallback.img' ==> Image generation successful (5/6) Refreshing PackageKit... (6/6) Signing EFI binaries... Generating EFI bundles.... File has already been signed /boot/EFI/BOOT/BOOTX64.EFI File has already been signed /boot/EFI/systemd/systemd-bootx64.efi File has already been signed /boot/shellx64.efi ✓ Signed /boot/vmlinuz-linux-amd-znver3 File has already been signed /boot/vmlinuz-linux-lts

Can you also confirm me if you are using mkinitcpio to make your kernels? can you tell me when your ramdisk of znver3 is created (ls -l)? can you check if the kernel install actually creates a new ramdisk?

Then it all looks good. I have no idea what your bootup needs more then. Everything looks good from my end. Perhaps force remove, reboot to other kernel, check mentioned dirs (boot, modules) if they dont contain any old znver3 files, clear pacman cached znver3 kernel, and then reinstall the kernel from the repo? because I am out of ideas for you..

Yes eggz, there are.

[mario@asus-arch ~]$ ls -lh /usr/lib/modules/6.6.9-AMD-znver3/ total 16M drwxr-xr-x 1 root root 324 ene 1 09:40 build drwxr-xr-x 1 root root 110 ene 1 09:40 kernel -rw-r--r-- 1 root root 1,1M ene 1 09:41 modules.alias -rw-r--r-- 1 root root 1,1M ene 1 09:41 modules.alias.bin -rw-r--r-- 1 root root 5,4K ene 1 08:54 modules.builtin -rw-r--r-- 1 root root 8,5K ene 1 09:41 modules.builtin.alias.bin -rw-r--r-- 1 root root 7,4K ene 1 09:41 modules.builtin.bin -rw-r--r-- 1 root root 45K ene 1 08:54 modules.builtin.modinfo -rw-r--r-- 1 root root 524K ene 1 09:41 modules.dep -rw-r--r-- 1 root root 678K ene 1 09:41 modules.dep.bin -rw-r--r-- 1 root root 453 ene 1 09:41 modules.devname -rw-r--r-- 1 root root 139K ene 1 08:54 modules.order -rw-r--r-- 1 root root 1,1K ene 1 09:41 modules.softdep -rw-r--r-- 1 root root 595K ene 1 09:41 modules.symbols -rw-r--r-- 1 root root 719K ene 1 09:41 modules.symbols.bin -rw-r--r-- 1 root root 17 ene 1 08:54 pkgbase drwxr-xr-x 1 root root 8 ene 1 09:40 updates -rw-r--r-- 1 root root 11M ene 1 08:54 vmlinuz [mario@asus-arch ~]$ date lun 01 ene 2024 13:47:06 -05 [mario@asus-arch ~]$

Hey Mario, I did the same tests on this kernel in the mean time and I also couldn't find anything wrong too

do you have a folder /usr/lib/modules/6.6.9-AMD-znver3/ when the kernel is installed?

Ok, my problem happend with this version. :p

Oh yeah my PKGBUILDS (I reused) def go back more than 4 years. Okay, I did not know that, good to know. I will use the simplified way soon after some more testing.

As for the diffrences, im not completely convinced everything in the core kernel is automaticly better. If I wanted to make a 1:1 copy, well, im not sure what my added value is here and you might aswell just start using the core kernel with my Kconfig. But I'll take a look at them anyway.

I use git instead of tarbals because my pipelines(build,test,aur,repo,...) are custom made and I would like to be able to uniformly (and transparantly) insert gitpatches/reverts inside them when I want to make modifications/patches in the kernel code. While using tarbals in the pipelines by some extra mechanisms is not impossible (by using some git overlay or something?), it gives me alot more work to redo big parts of the pipelines and I currently dont have the time for that, I'm sorry. If I wanted to run by you every detail of my pipeline and the pros and cons, we would be here discussing for days. Lets just say it's just a choice I have made and so far im sticking by it. If you want a fast install, use the repo, if you want all the details, use the aur git build way :-)

I should thank you as well for your effors, nice work and returning my feedbacks quickly.

Looks like they added those pacman hooks 4 years ago according to the git history of core/mkinitcpio. That's might be the reason too.

And I'd like to point out a few more things.

I noticed some dependency differences between your and core/linux's PKGBUILD files as you can see here, here, here and here. You might want to take a look at those too.

And may I ask is there any reason for using git instead of tarballs from Linux's CDN? It would be nice to check its hash values too.

thx