I humbly retract my earlier statement and eat my hat. I can confirm that something is not right. For some reason, the crc32c module is getting left out of the initrd, and btrfs module needs this module to work.
The reason why I didn't have this problem at home, was because I explicitly install crc32c by adding it to mkinitcpio.conf's MODULE array. This is a workaround. Another is to use the fallback initrd for the time being.
I don't have time right now to bisect the commit that caused this regression, but if you want to open a bug report and post a link to it here, I'll see if I can help out getting this fixed. Cheers.
Search Criteria
Package Details: linux-mainline-headers 6.13rc4-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/linux-mainline.git (read-only, click to copy) |
|---|---|
| Package Base: | linux-mainline |
| Description: | Headers and scripts for building modules for the Linux Mainline kernel |
| Upstream URL: | https://kernel.org/ |
| Licenses: | GPL-2.0-only |
| Submitter: | miffe |
| Maintainer: | miffe |
| Last Packager: | miffe |
| Votes: | 281 |
| Popularity: | 3.95 |
| First Submitted: | 2011-07-22 06:50 (UTC) |
| Last Updated: | 2024-12-23 04:14 (UTC) |
Dependencies (16)
- pahole (pahole-gitAUR)
- bc (bc-ghAUR) (make)
- cpio (cpio-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- graphviz (make)
- imagemagick (imagemagick-gitAUR, imagemagick-full-gitAUR, imagemagick-fullAUR) (make)
- libelf (elfutils-gitAUR) (make)
- pahole (pahole-gitAUR) (make)
- perl (perl-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-sphinx (python-sphinx-gitAUR) (make)
- python-yaml (python-yaml-gitAUR) (make)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
- texlive-latexextra (texlive-installerAUR, texlive-fullAUR, texlive-dummyAUR) (make)
- xz (xz-gitAUR) (make)
Required by (0)
Sources (2)
WorMzy commented on 2014-02-25 17:49 (UTC)
Det commented on 2014-02-25 09:13 (UTC)
Congrats on the 100th vote for the 2nd time.
WorMzy commented on 2014-02-24 22:59 (UTC)
Still no problem here, and I've not noticed anything on the btrfs mailing list.. Personally, I think it's a problem with your setup. If I get chance, I'll try the mainline kernel on my non-raid btrfs work PC tomorrow and see if that has any problems.
kleinph commented on 2014-02-24 22:53 (UTC)
The same problem occurs with the rc4. Should I file a bug upstream?
miffe commented on 2014-02-24 12:23 (UTC)
linux-mainline 3.14rc4-1:
- New upstream release
kleinph commented on 2014-02-19 17:11 (UTC)
Ok then I will wait for the next RC and try again.
cbowman57 commented on 2014-02-19 16:11 (UTC)
Pretty sure the btrfs problems are coming from upstream & it's development issue.
kleinph commented on 2014-02-19 15:22 (UTC)
Thanks, but that doesn't seem to be the problem. Both have kernel 3.14.0-1-mainline.
WorMzy commented on 2014-02-19 15:05 (UTC)
Depending on how you have your system set up, there's a chance that the kernel or the initrd images can become desynchronised, so you have a newer kernel and an older initrd, or vice versa. You don't get a "no initrd or kernel" error, because the old initrd or kernel is still present.
Checking the kernel and the initrds on the ESP would help identify if this is the problem, e.g.:
lsinitcpio -a /boot/EFI/arch/initramfs-linux-mainline.img | grep Kernel
file /boot/EFI/arch/vmlinux-linux-mainline
Pinned Comments
miffe commented on 2020-01-30 21:44 (UTC)
Repository here