Search Criteria
Package Details: linux-amd-znver3 6.13.v.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-amd-znver3.git (read-only, click to copy) |
---|---|
Package Base: | linux-amd-znver3 |
Description: | Linux kernel aimed at the znver3 AMD Ryzen CPU based hardware |
Upstream URL: | https://www.kernel.org/ |
Licenses: | GPL2 |
Submitter: | None |
Maintainer: | None |
Last Packager: | bebna |
Votes: | 10 |
Popularity: | 0.014479 |
First Submitted: | 2023-05-04 15:47 (UTC) |
Last Updated: | 2025-02-16 11:21 (UTC) |
Dependencies (14)
- coreutils (coreutils-gitAUR, coreutils-uutilsAUR, coreutils-selinuxAUR, coreutils-uutils-symlinkAUR)
- kmod (kmod-gitAUR)
- linux-firmware (linux-libre-firmwareAUR, linux-firmware-uncompressedAUR, linux-firmware-gitAUR)
- lzop
- bc (bc-ghAUR) (make)
- docbook-xsl (make)
- gcc (gcc-gitAUR, gccrs-gitAUR, gcc11AUR, gcc-snapshotAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- inetutils (inetutils-gitAUR) (make)
- kmod (kmod-gitAUR) (make)
- libelf (elfutils-gitAUR) (make)
- lzop (make)
- xmlto (xmlto-gitAUR) (make)
- crda (wireless-regdb) (optional) – to set the correct wireless channels of your country
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 Next › Last »
onurmercury commented on 2024-01-01 19:50 (UTC) (edited on 2024-01-01 19:52 (UTC) by onurmercury)
ofc it's all up to you and not so big deal but i think forcing lzop via .preset is not ideal. it just takes away the global compression control of
mkinicpio.conf
.Mario156090 commented on 2024-01-01 19:40 (UTC)
Aparently only were a installation problem because now works perfectly.
[mario@asus-arch ~]$ uname -r 6.6.9-AMD-znver3 [mario@asus-arch ~]$ ^C [mario@asus-arch ~]$
<deleted-account> commented on 2024-01-01 19:37 (UTC)
@mario good to hear because I was all out of ideas..
Mario156090 commented on 2024-01-01 19:36 (UTC)
Well, after reinstall it's booted correctly.
<deleted-account> commented on 2024-01-01 19:19 (UTC)
I will keep the preset file since it forces lzop compression, which is sometimes faster than zstd, especially in reading ==> (just like I do in the internal kernel)
these kernels were using lzop far before the arch kernels switched to zstd, and I havent been convinced by their performance after some testing to do some switching myself.
The other two are indeed interesting (although the move of the systemmap to headers seems a bit trivial to me), ill have a look at it soon.
onurmercury commented on 2024-01-01 19:12 (UTC)
yep i don't have any problems with 6.6.9 update. it works like a charm.
<deleted-account> commented on 2024-01-01 19:08 (UTC)
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) ?
onurmercury commented on 2024-01-01 19:01 (UTC) (edited on 2024-01-01 19:11 (UTC) by onurmercury)
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.
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.
Mario156090 commented on 2024-01-01 19:00 (UTC)
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
<deleted-account> commented on 2024-01-01 18:53 (UTC)
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?
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 Next › Last »