[solved] custom 2.6.32 package - no mkinitcpio happening

sultanoswing · 2010-01-02 21:15:10

I've been rolling custom kernels for a year or so without major problems using the abs kernel26 [core] package.

Noticing kernel 2.6.32.2-2 has come out, I used and modded the pkgbuild as usual, using the default supplied config, except for a few usual changes (processor to Athlon64 and cutting out the chaff of other hardware etc).

Problem: when I pacman -U the resultant kernel26-custom-2.6.32.2-2-i686.pkg.tar.gz package it simply 'installs', without

Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img

and thus isn't generating the required img, ramdisk etc.

Whaddup with that?

Last edited by sultanoswing (2010-01-04 03:38:36)

ngoonee · 2010-01-02 22:35:55

your kernel26-custom.install file handles that.

sultanoswing · 2010-01-02 23:22:25

ngoonee wrote:

your kernel26-custom.install file handles that.

Never had to mess with or create that file before, previously relying on the included kernel26.install file. I did try adding "KERNEL_NAME=kernel26-custom" (as I've set it in PKGBUILD) to the kernel26.install file, since the NAME variable was blank. Will see what happens this compile.

[EDIT] Curious. The compiled kernel26-custom tar.gz file is only 368 bytes. Methinks the kernel26 [core] compile package is b0rked.

Last edited by sultanoswing (2010-01-03 02:53:01)

hungerfish · 2010-01-03 07:03:07

Hmm, this maybe have nothing todo with the packaging.
I've been trying to build my custom kernel ,2.6.32-2, and I am also unable to build the initcpio file.
This is vanilla , from kernel.org !

I just compile my kernel 'normal-way', so I do

make && make modules_install

After that I do

mkinitcpio -k 2.6.32-MYKERN2 -g /boot/mykern2.img

This gives my a very small file

-rw-r--r-- 1 root root 239K Jan  3 08:05 mykern2.img

The output is
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
find: `/lib/modules/2.6.32-MYKERN2': No such file or directory
find: `/lib/modules/2.6.32-MYKERN2': No such file or directory
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Parsing hook [keymap]
:: Generating image '/boot/mykern2.img'...lzma: Adjusted LZMA1 dictionary size from 64 MiB to 35 MiB to not exceed the memory usage limit of 401 MiB
SUCCESS

With just 2.6.32 I did not have this problem.

Last edited by hungerfish (2010-01-03 07:03:49)

sultanoswing · 2010-01-03 07:23:28

Good to see I'm not the only one (you understand )

If someone more knowledgeable chimes in, perhaps we're looking at a regression that ought to be filed.

ngoonee · 2010-01-03 09:29:46

methinks the both of you are doing something wrong, sorry to say. Compiling custom kernels is something done by quite a number of people, its not a dark corner of the distro. What PKGBUILD are you using?

sultanoswing · 2010-01-03 09:41:39

ngoonee wrote:

methinks the both of you are doing something wrong, sorry to say. Compiling custom kernels is something done by quite a number of people, its not a dark corner of the distro. What PKGBUILD are you using?

Well something's changed since 2.6.31, and it's nothing I've done (I think!).

I'm using all the files (PKGBUILD, config, config.x86_64, kernel26.install, kernel26.preset) straight from a freshly synced ABS: /var/abs/core/kernel26

Other than uncommenting out a couple of lines in PKGBUILD to set the custom kernel name:

# $Id: PKGBUILD 61813 2009-12-26 08:43:16Z tpowa $
# Maintainer: Tobias Powalowski <tpowa@archlinux.org>
# Maintainer: Thomas Baechler <thomas@archlinux.org>
pkgbase="kernel26"
# pkgname=('kernel26' 'kernel26-firmware' 'kernel26-headers') # Build stock -ARCH kernel
pkgname=kernel26-custom       # Build kernel with a different name
_kernelname=${pkgname#kernel26}
_basekernel=2.6.32
pkgver=${_basekernel}.2
pkgrel=2

and uncommenting make menuconfig:

  #make menuconfig # CLI menu for configuration

and changing a few fairly standard options via menuconfig such as processor type, I haven't done anything radically complicated or anything I haven't done with multiple previous successful builds. Curious!

Last edited by sultanoswing (2010-01-03 09:43:13)

ngoonee · 2010-01-03 11:07:00

The change since 2.6.31 is the splitting of our kernel26 package into 3. I have not played with that PKGBUILD, since my custom kernels all still follow the old way. Shouldn't the kernel26.install file be renamed to kernel26-custom.install, since you're building the kernel26-custom package? Check in the ./pkg directory after your makepkg, it should show you the contents of a kernel (boot, etc, lib directories) and a ./pkg/.INSTALL file which actually handles the mkinitcpio.

hungerfish · 2010-01-03 14:53:23

As mentioned above, I'm using the kernel from kernel.org.
It builds and boots fine, just initcpio file is garbled, so mkinitcpio is doing something wrong, or messing up, I don't know.
It worked fine for 2.6.32 , just not for 2.6.32-2.

I know that there was some testing/changing going on in that area, due to problems related to early-KMS and the radeon module, as its firmware wasn't handled correctly. Maybe some script got jacked up in the process. Also I'm using mkinitcpio from testing.

Last edited by hungerfish (2010-01-03 15:00:36)

sultanoswing · 2010-01-03 20:50:32

Well I'm out of ideas. I'll be interested to see if anyone else is able to sucessfully compile a custom kernel using the ABS method from the 2.6.32.2-2 kernel26 [core] PKGBUILD to confirm or refute this potential bug.

I hope it gets fixed soon, whatever the issue is.

Last edited by sultanoswing (2010-01-03 21:21:47)

owain · 2010-01-04 00:23:13

sultanoswing wrote:

Well I'm out of ideas. I'll be interested to see if anyone else is able to sucessfully compile a custom kernel using the ABS method from the 2.6.32.2-2 kernel26 [core] PKGBUILD to confirm or refute this potential bug.

I've had success with dblue's solution here, and join them in wanting to know if this was the 'right' way to do it.

sultanoswing · 2010-01-04 03:40:25

owain wrote:

sultanoswing wrote:
Well I'm out of ideas. I'll be interested to see if anyone else is able to sucessfully compile a custom kernel using the ABS method from the 2.6.32.2-2 kernel26 [core] PKGBUILD to confirm or refute this potential bug.
I've had success with dblue's solution here, and join them in wanting to know if this was the 'right' way to do it.

Yeah that worked, many thanks. It's a little bit of extra editing, but logical enough.

I've marked this as solved, but I still think the official kernel26 PKGBUILD needs a tweak to reflect the changes made.

tuxfusion · 2010-01-24 00:07:35

Thx for investigating !
imho , the wiki needs an update to reflect this "spliting".
http://wiki.archlinux.org/index.php/Cus … n_with_ABS

Arch Linux

#1 2010-01-02 21:15:10

[solved] custom 2.6.32 package - no mkinitcpio happening

#2 2010-01-02 22:35:55

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#3 2010-01-02 23:22:25

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#4 2010-01-03 07:03:07

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#5 2010-01-03 07:23:28

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#6 2010-01-03 09:29:46

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#7 2010-01-03 09:41:39

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#8 2010-01-03 11:07:00

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#9 2010-01-03 14:53:23

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#10 2010-01-03 20:50:32

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#11 2010-01-04 00:23:13

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#12 2010-01-04 03:40:25

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

#13 2010-01-24 00:07:35

Re: [solved] custom 2.6.32 package - no mkinitcpio happening

Board footer