Package: src:linux Version: 4.0.2-1 Severity: important Dear Maintainer,
I have the following — probably not so common — configuration:
- libreboot BIOS (a deblobed coreboot) with a GRUB2 payload
- root is BTRFS, with rootflags=subvol=@
Since I don't want to flash a new payload onto the BIOS chip at each
kernel upgrade, I'm using the following static grub.cfg:
linux /@/vmlinuz root=UUID=[…] rootflags=subvol=@ resume=UUID=[…] ro
initrd /@/initrd.img
This used to work great until 3.16.0. However my system no longer boots
since the 4.0.0 upgrade, due to the symlink /initrd.img now having an
absolute target: since GRUB doesn't understand BTRFS subvolumes, it
needs to be pointed to /@/boot/initrd.img-4.0.0-1-686-pae somehow.
Of course the quickfix on my side is to edit the GRUB script to load
‘initrd /@/boot/initrd.img-4.0.0-1-686-pae’ instead, but it would be
nice to make /initrd.img's target relative again in the post-install
script (/vmlinuz doesn't have this problem by the way).
Cheers,
--
Guilhem.
-- Package-specific info:
** Version:
Linux version 4.0.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version
4.9.2 (Debian 4.9.2-16) ) #1 SMP Debian 4.0.2-1 (2015-05-11)
** Command line:
BOOT_IMAGE=/@/vmlinuz root=UUID=a17c2310-b308-4dd0-8cef-a7f8ca750081
rootflags=subvol=@ resume=UUID=102accd9-30dd-4081-8a7f-a1310ad9a1ee ro
** Not tainted
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 4.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- debconf information excluded
signature.asc
Description: Digital signature
