Arch Linux

tam1138

Member

Registered: 2007-09-10

Posts: 238

custom kernel package fails to boot

Hi there --

I built a custom kernel package with the intent of getting access to all the fancy systemtap debug info, but it seems to have gone horribly wrong.  Here is what I did:

- I updated my ABS tree (sudo abs update)
- I copied /var/abs/core/linux to my home directory
- I edited config.x86_64, adding CONFIG_DEBUG_INFO=y and CONFIG_DEBUG_INFO_REDUCED=n
- I updated the checksums with makepkg -g and vim
- I built the package with makepkg --skippgpchecks because I'm too lazy to import Linus' key

This resulted in three packages: linux-debug, linux-debug-headers, and linux-debug-docs, all version 4.2.2-1.  I install all these packages with pacman -U.

I then reviewed my refind configuration (I don't use a bootloader, it all goes straight to EFI).  /boot/refind_linux.conf had two uncommented lines, one for default and one for fallback:

    "Boot with defaults" "cryptdevice=/dev/disk/by-partuuid/<partition uuid>:root:allow-discards root=/dev/mapper/root ro initrd=\initramfs-linux.img"
    "Boot with fallback" "cryptdevice=/dev/disk/by-partuuid/<partition uuid>:root:allow-discards root=/dev/mapper/root ro initrd=\initramfs-linux-fallback.img"

I duplicated these two lines, changing the initrd paths to be "initramfs-linux-debug.img" and "initramfs-linux-debug-fallback.img", both of which exist in the filesystem.

When I rebooted, refind showed me two options for Linux where it had only showed one in the past, which seemed promising.  I selected the one labeled "linux-debug" and was shortly thereafter informed that the kernel could not find either the cryptdevice partition or /dev/mapper/root.  I powered the machine off, booted, and selected the "normal" linux (ie, not the failing linux-debug) and it booted fine, using the cryptdevice that linux-debug failed to find.  I feel like I missed some really basic configuration step in building the kernel.

Any advice/pointers are most appreciated.  I can gather any and all other information you think might come in handy.  Thanks in advance!

References:
- https://wiki.archlinux.org/index.php/Ke … ild_System
- https://wiki.archlinux.org/index.php/SystemTap

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: custom kernel package fails to boot

Hm. What happens when you run 'mkinitcpio -P', do all 4 images get generated without problems (the -fallback firmware warnings are expected)?

---

1000

tam1138

Member

Registered: 2007-09-10

Posts: 238

Re: custom kernel package fails to boot

Yep.  I ran "sudo mkinitcpio -P" and I got double the output I normally get: once for the stock kernel and once for the custom one.  The output for the stock kernel looks the same as it always does (though I don't have a copy handy to compare it to explicitly, but there's nothing obviously untoward going on there) and the output for the custom kernel looks the same as for the stock one, albeit with the filenames changed.