own kernel

3 posts / 0 new
Last post
#1 Wed, 2015-03-18 13:42
ch3mik
  • ch3mik's picture
  • Offline
  • Last seen: 3 years 1 week ago
  • Joined: 2014-04-05

Hello, I have computer with 40 cpus ( 2x E5-2680 ). Alpine kernel is configured with NR_CPUS=32

I have diskless instalation - I am booting from flash, saving configuration with 'lba ci'

I need to make own kernel for more CPUs.

I make alpine instalation in chroot and I am able making my own packages with abuild command.

I try to recompile alpine original kernel (for testing, with the same .config), I replace original kernel
with my kernel and alpine boots normally.

But If I make any change in kernel .config, alpine doesn't boot with this kernel. Kernel is loaded but initrd cannot be started.

I try make new initrd (with 'mkinitfs 3.10.44-1-grsec', I copied new modules in /lib/modules/3.10.44-1-grsec). It makes for me
new initrd - grsec.gz.

But alpine cannot boot with new kernel and new initrd, it ends with kernel panic.

Can you tell what I am making wrong? Or what is the right way for instaling new kernel?

Thank you for help

Wed, 2015-03-18 19:01
AmatCoder
  • AmatCoder's picture
  • Offline
  • Last seen: 1 year 4 months ago
  • Joined: 2013-10-18

As far as I know, you need mkinitfs to generate a initramfs image for Alpine.
You can install it with "apk add mkinitfs"

See http://git.alpinelinux.org/cgit/mkinitfs/tree

Wed, 2015-03-18 19:28 (Reply to #2)
ch3mik
  • ch3mik's picture
  • Offline
  • Last seen: 3 years 1 week ago
  • Joined: 2014-04-05

Yes, I have mkinitfs installed and new initrd created (file grsec.gz). I used modules from my new kernel (although I make only change in CONFIG_NR_CPUS, which
- I thing - don't affects kernel modules).
But new kernel doesn't boot. When I am booting with new grsec.gz, boot ends with kernel panic (Unable to mount root fs on unknown-block(0,0)).
New kernel doesn't boot neither with original grsec.gz

Log in or register to post comments