In general, if you're compiling your own kernel, you don't need initrd, so you could use the custom kernel PKGBUILD - it's on the wiki here.
Just make sure you compile support for your disk controller and root filesystem into the kernel i.e. not as modules.
I did consider a custom kernel, but I like the initrd style because I will be using encrypted filesystem shortly.
I would also like to keep my kernel as similar (to produce) as the stock ARCH kernel.
Thanks!
Jacob
]]>btw, You can also use the "kernel_version" parameter w/ mkinitrd to force it to any version.
Worked like a charm!
Thanks!
Jacob
]]>You're right, mkinitrd should support non "-ARCH" kernels.
Try revision 1.38 from CVS:
http://cvs.archlinux.org/cgi-bin/viewcv … d/mkinitrd
Just make sure you compile support for your disk controller and root filesystem into the kernel i.e. not as modules.
]]>CONFIG_LOCALVERSION=""
back to:
CONFIG_LOCALVERSION="-ARCH"
it builds without error.
Jacob
]]>I modify the "config" file accordingly, then re-md5sum it. And added that sum to the PKGBUILD file and run makepkg in /var/abs/kernels/kernel26/ and after much downloading and patching I get the following error close to the end of the makepkg process:
Checking Input...
Building full initrd for Arch standard kernel
(includes all possible modules)
Setting up Parameters...
ERROR: /var/abs/kernels/kernel26/pkg/lib/modules/2.6.14-ARCH does not exist!
==> ERROR: Build Failed. Aborting...
[root@k kernel26]#
It seems to be looking for the very directory based on the LOCALVERSION which I've commented out in the "config" file:
CONFIG_LOCALVERSION=""
Somewhere (and not in the PKGBUILD) it seems, that the "-ARCH" is being appended to the makepkg process...
Any ideas on how I can get around this, so that my kernel isn't branded?
Jacob
P.S. This must be recent as kernel 2.6.13.4 didn't have this problem.
-> I also tried changing the line inside PKGBUILD:
_kernver="${basekernel}${CONFIG_LOCALVERSION}"
--to--
_kernver="${basekernel}"
...no help