You are not logged in.
Pages: 1
Hi
According to this documentation i have to run linux-mainline-um5606 AUR package
I managed to compile and install kernel with:
makepkg -s MAKEFLAGS="-j$(nproc)"
sudo pacman -U linux-mainline-um5606-1:6.13rc3-1-x86_64.pkg.tar.zst
sudo pacman -U linux-mainline-um5606-headers-1:6.13rc3-1-x86_64.pkg.tar.zst But now my .img is just chilling in /boot:
ls /boot -la
drwxr-xr-x 4 root root 4096 1970-01-01 .
drwxr-xr-x 1 root root 142 12-19 18:56 ..
-rwxr-xr-x 1 root root 153600 12-10 20:35 amd-ucode.img
drwxr-xr-x 5 root root 4096 12-19 18:57 EFI
-rwxr-xr-x 1 root root 136401558 12-20 15:21 initramfs-linux-mainline-um5606-fallback.img
-rwxr-xr-x 1 root root 49066032 12-20 15:21 initramfs-linux-mainline-um5606.img
drwxr-xr-x 4 root root 4096 12-20 15:26 loader
-rwxr-xr-x 1 root root 13738496 12-19 18:56 vmlinuz-linux
-rwxr-xr-x 1 root root 13771264 12-20 15:21 vmlinuz-linux-mainline-um5606and my current kernel is still old one:
uname -r
6.12.4-arch1-1I have direct EFI loading (no grub). My EFI configurator sees only .efi files that doesn't exist for my custom kernel..
Could you please help mi what step i'm missing? I feel like i'm 95% done and it's just a matter of switching something, but i can't find anything useful on the internet.
Offline
Offline
I've seen this, but it's really black magic for me
efibootmgr --create \
--disk /dev/nvme0n1 --part 1 \
--label "EFISTUB Arch" \
--loader /vmlinuz-linux-lts \
--unicode 'root=UUID=01a40dd8-28f0-4636-be1e-aeed60c98095 resume=UUID=2d877d5d-4ca1-4d46-a3d6-b6ee94cbbd78 rw rootflags=subvol=@ loglevel=3 quiet initrd=\initramfs-linux-lts.img'in this example:
--part 1 is nvme0n1p1 or nvme0n1p2?
--loader should be just /vmlinuz, /BOOT/vmlinuz, /EFI/BOOT/vmlinuz, \EFI\BOOT vmlinuz or which one?
--unicode
- is root uuid uuid of disk or disk type?
- what is resume?
-initdir - the same as --loader?
Sorry for stupid questions. I'm not doing this because i am bored, i'm doing this in order to have sound in my laptop
Offline
How did you do it the first time? For the kernel you've been running?
Offline
--disk /dev/nvme0n1 --part 1 is nvme0n1p1
--loader /vmlinuz-linux-lts is the kernel binary for linux-lts assuming /boot is the ESP https://wiki.archlinux.org/title/Persis … ng#by-uuid
'root=UUID=01a40dd8-28f0-4636-be1e-aeed60c98095 initrd=\initramfs-linux-lts.img' mount the filesystem with the UUID 01a40dd8-28f0-4636-be1e-aeed60c98095 as root use initramfs-linux-lts.img as the initial ramdisk.
Edit:
Also you have confirmed the audio issue is still present with linux 6.12? The advice you reference predates the 6.12 release.
Last edited by loqs (2024-12-20 15:58:08)
Offline
How did you do it the first time? For the kernel you've been running?
archinstall ![]()
Also you have confirmed the audio issue is still present with linux 6.12? The advice you reference predates the 6.12 release.
Earlier you could make it with some hacks/manual configuration in pulse audio, now i wanted to make it clean.
After finding (i belive) correct uuid i have issue that
/sbin/init
does not exist.
I'll be back when this is merged to main kernel and working (probably early 2026), for now it's back to windown.
I only have 10 years experience as software dev, i'm too dumb for this sh*t.
Thanks for all the help but i got flashbacks of all of the previous attempts - although it's nice to not have to read nouveau for once.
edit: if anyone has similar issue, this is what i managed to get to:
sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Arch8" --loader /vmlinuz-linux-mainline-um5606 --unicode 'root=UUID=ff4b2e60-d6a0-4aba-bc39-89f2a8d765df rw initrd=\initramfs-linux-mainline-um5606.img'
where uuid is p2 from command posted by loqs
Last edited by matesz (2024-12-20 17:09:21)
Offline
I'll be back when this is merged to main kernel and working (probably early 2026), for now it's back to windown.
https://aur.archlinux.org/packages/linu … ine-um5606 is as of writing mainline 6.13-rc3 plus a patch for AMD NPU (Neural Processing Unit). Unless the lack of NPU patch is causing your system's audio issue then you will only have to wait a few weeks for the 6.13 release rather than a year. If there are required kernel config changes then someone would need to make a request for those against the linux package after the 6.13 release.
Offline
Pages: 1