Re: compiling a kernel from kernel.org [SOLVED]
Hey, Thx everybody for your quick answers and friendly help. You were right. I removed all Xen options from the kernel config and linux-image-2.6.32-rc5_20091016-2_amd64.deb has been built. Installing it with dpkg -i ... worked fine. The only problem to be solved was the initrd. it has NOT been generated by dpkg during the installation. so I generated it using mkinitramfs -c -k 2.6.32-rc5. worked fine. update-grub - worked fine as well. Finally I can use KMS with my radeon 4670 :) Greetings Gregor Galwas On Tue, 20 Oct 2009 21:34:53 +0200, Manoj Srivastava sriva...@ieee.org wrote: Hi, Well, firstly, if you are going to be using the buildpackage target, instead of the far faster kernel_image target, you should either configure /etc/kernel-pkg.conf, adding your name and email, and have that in a keyring your gpg knows about, or pass the --us and --uc arguments on the command line. I think, unless you know what you are doing, try first with kernel_image target. Next, you seem to have Xen options turned on in your config, and thus make-kpkg is trying to create a xenu-linux image. This is undergoing some development, so if you want Xen images, please get the 12.024 version of kernel-package from Sid. If you are just trying to build a normal kernel, redo your .config not to have Xen stuff in it. manoj -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: compiling a kernel from kernel.org [SOLVED]
Gregor Galwas wrote: Hey, Thx everybody for your quick answers and friendly help. You were right. I removed all Xen options from the kernel config and linux-image-2.6.32-rc5_20091016-2_amd64.deb has been built. Installing it with dpkg -i ... worked fine. The only problem to be solved was the initrd. it has NOT been generated by dpkg during the installation. so I generated it using mkinitramfs -c -k 2.6.32-rc5. worked fine. update-grub - worked fine as well. Finally I can use KMS with my radeon 4670 :) Greetings Gregor Galwas Hi, regarding the initrd, you need to copy over to /etc/kernel/* the relevant scripts from /usr/share/kernel-package/examples/etc/kernel/* (look for initramfs or yaird if you use it). It will save you the mkinitramfs step. Also have a look at /usr/share/kernel-package/examples/etc/sample.kernel-img.conf to trigger links creation and such. Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: compiling a kernel from kernel.org [SOLVED]
On Wed, Oct 21 2009, Gregor Galwas wrote:
The only problem to be solved was the initrd. it has NOT been
generated by dpkg during the installation.
so I generated it using mkinitramfs -c -k 2.6.32-rc5. worked
fine. update-grub - worked fine as well.
,[ Manual page make-kpkg(1) ]
| --initrd
| If make-kpkg is generating a kernel-image package, arrange to
| convey to the hook scripts run from the post installation
| maintainer scripts that this image requires an initrd, and that
| the initrd generation hook scripts should not short circuit
| early. Without this option, the example initramfs hook scripts
| bundled in with kernel-package will take no action on
| installation. The same effect can be achieved by setting the
| environment variable INITRD to any non empty value. Please note
| that unless there are hook scripts in /etc/kernel or added into
| the hook script parameter of /etc/kernel-img.conf. no initrd
| will be created (the bundled in example scripts are just
| examples -- user action is required before anything happens).
`
,[ /usr/share/doc/kernel-package/README.gz ]
| gotchas. Note that you will have to arrange for the actual
| initrd creation to take place by installing a script like
| /usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/yaird
| or, alternately,
| /usr/share/kernel-package/examples/etc/kernel/post{inst,rm}.d/initramfs
| into the corresponding directories /etc/kernel/post{inst,rm}.d,
| since the kernel-postinst does not arrange for the initramfs
| creator to be called. You can thus select your own;
| initramfs-tools or yaird.
|
| Let me repeat:
| Since nothing is created automatically. you need to provide a hook
| script for things to happen when you install the kernel image
| package. The user provides such scripts. For example, to invoke
| mkinitramfs, I did:
| --8---cut here---start-8---
| cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/yaird \
| /etc/kernel/postinst.d/
| cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/yaird \
| /etc/kernel/postrm.d/
| --8---cut here---end---8---
|
| Or, alternately, you could do:
| --8---cut here---start-8---
| cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \
| /etc/kernel/postinst.d/
| cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \
| /etc/kernel/postrm.d/
| --8---cut here---end---8---
|
| These scripts above to nothing unless the corresponding
| packages are installed (initramfs-tools or yaird), so you could
| potentially cp both over -- as long as you never install both yaird
| and initramfs-tools at the same time.
|
| To run grub, I have in /etc/kernel-img.conf:
| --8---cut here---start-8---
| postinst_hook = update-grub
| postrm_hook = update-grub
| --8---cut here---end---8---
|
| You can look at other example in the examples directory:
| /usr/share/kernel-package/examples/ to see if there are other example
| script you want to cp into /etc/kernel -- and you can create your own
| scripts.
|
| For example, if you use linux-headers-* packages to compile third
| party modules so that you do not have to keep the sources directory
| around, you might be interested in:
| --8---cut here---start-8---
| /etc/kernel/header_postinst.d/link
| /etc/kernel/header_postrm.d/link
| /etc/kernel/header_prerm.d/link
| /etc/kernel/postinst.d/force-build-link
| /etc/kernel/postrm.d/force-build-link
| --8---cut here---end---8---
|
| These scripts will try to make sure that the symlink
| /lib/modules/$VERSION/build
| is sane -- that is points to the header packages whether you install
| the image packages first, or the header packages first -- and takes
| care of cleanup when either of the packages are installed.
`
Perhaps people who maintain FAQ's on this list add the above?
manoj
--
Some people have a great ambition: to build something that will last, at
least until they've finished building it.
Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
compiling a kernel from kernel.org
hello, in the new last days I've been trying to compile a recent kernel from kernel.org I fetched a kernel from http://www.kernel.org/ mainline: 2.6.32-rc5 2009-10-16 [Full Source] http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.32-rc5.tar.bz2 unpacked it using tar xjvf linux-2.6.32-rc5.tar.bz2 -C /usr/src linked : ln -s /usr/src/linux-2.6.32-rc5.tar.bz2 /usr/src/linux cp /boot/config-`uname -r` /usr/src/linux/.config make oldconfig then I started building the packages with make-kpkg buildpackage --revision 20091016 --initrd it started compiling it and it ended after a loinger time with : make[1]: Leaving directory `/usr/src/linux-2.6.32-rc5' dpkg-genchanges -b -mUnknown Kernel Package Maintainer unkn...@unconfigured.in.etc.kernel-pkg.conf ../linux-source-2.6.32-rc5_20091016_amd64.changes dpkg-genchanges: warning: package linux-image-2.6.32-rc5 in control file but not in files list dpkg-genchanges: warning: package linux-image-2.6.32-rc5-dbg in control file but not in files list dpkg-genchanges: warning: package linux-uml-2.6.32-rc5 in control file but not in files list dpkg-genchanges: warning: package linux-xen0-2.6.32-rc5 in control file but not in files list dpkg-genchanges: binary-only upload - not including any source code signfile linux-source-2.6.32-rc5_20091016_amd64.changes gpg: skipped Unknown Kernel Package Maintainer: secret key not available gpg: [stdin]: clearsign failed: secret key not available dpkg-buildpackage: binary only upload (no source included) dpkg-buildpackage: warning: Failed to sign .changes file make: *** [debian/stamp/build/buildpackage] Error 1 following packages have been created in /usr/src: linux-doc-2.6.32-rc5_20091016_all.deb linux-headers-2.6.32-rc5_20091016_amd64.deb linux-headers-2.6.32-rc5_2.6.32-rc5-10.00.Custom_amd64.deb linux-manual-2.6.32-rc5_20091016_all.deb linux-source-2.6.32-rc5_20091016_all.deb linux-source-2.6.32-rc5_20091016_amd64.changes linux-xenu-2.6.32-rc5_20091016_amd64.deb linux-xenu-2.6.32-rc5_2.6.32-rc5-10.00.Custom_amd64.deb ok, so far - it looked good even thouigh that xenu part annoyed me somehow. when I treid to install linux-xenu-2.6.32-rc5_20091016_amd64.deb I got: pegasos:/usr/src# dpkg -i linux-xenu-2.6.32-rc5_20091016_amd64.deb Selecting previously deselected package linux-xenu-2.6.32-rc5. (Reading database ... 215220 files and directories currently installed.) Unpacking linux-xenu-2.6.32-rc5 (from linux-xenu-2.6.32-rc5_20091016_amd64.deb) ... Done. Setting up linux-xenu-2.6.32-rc5 (20091016) ... Internal Error: Could not find image (/boot/vmlinuz-2.6.32-rc5) dpkg: error processing linux-xenu-2.6.32-rc5 (--install): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: linux-xenu-2.6.32-rc5 Obviously something is badly wrong then. I am using Debian Unstable with kernel 2.6.31 (Linux pegasos 2.6.31-trunk-amd64 #1 SMP Mon Oct 12 23:36:11 UTC 2009 x86_64 GNU/Linux) and Grub2 anyone has an idea whats wrong here? Or am I doing it completely wrong? Thx for reading at least... Gregor Galwas -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: compiling a kernel from kernel.org
Hi, Well, firstly, if you are going to be using the buildpackage target, instead of the far faster kernel_image target, you should either configure /etc/kernel-pkg.conf, adding your name and email, and have that in a keyring your gpg knows about, or pass the --us and --uc arguments on the command line. I think, unless you know what you are doing, try first with kernel_image target. Next, you seem to have Xen options turned on in your config, and thus make-kpkg is trying to create a xenu-linux image. This is undergoing some development, so if you want Xen images, please get the 12.024 version of kernel-package from Sid. If you are just trying to build a normal kernel, redo your .config not to have Xen stuff in it. manoj -- This is an unauthorized cybernetic announcement. Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
