make-kpkg fails writing to weird directories on dual or multi core processors
Hi I have using make-kpkg successfully on my amd64 dual core system until about a month ago. I did the following: installed debian testing amd64 apt-get install kernel-package make g++ gcc build-essentail libncurses5-dev linux-source-2.6.32 and any other files I needed to build a kernel I invoked make-kpkg make-kpkg --initrd --revision custom1.0 --append-to-version custom1.0 kernel_image kernel_headers ( I did not set the CONCURRENCY_LEVEL although I did try it with values 2 and 3 and I still get the same error below) The compile is fine until the package building starts. Check the errors below, where does the _-live1.0_ come from? I did not type this in. I have tried uninstalling all the packages and reinstalling them, using standard kernels to boot from and custom kernels but nothing works. However it works fine on my laptop which has a centrino 1.5GHz single cpu. I also tried kernel-package version 12.033, 12.032 and the one that came with lenny. Problem remains the same. exec make -f /usr/share/kernel-package/ruleset/minimal.mk debian DEBIAN_REVISION=custom1.0 APPEND_TO_VERSION=custom1.0 V=1 INITRD=YES == making target debian/stamp/conf/minimal_debian [new prereqs: ]== This is kernel package version . test -d debian || mkdir debian test ! -e stamp-building || rm -f stamp-building WARNING: Couldn't open directory /usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0: No such file or directory FATAL: Could not open /usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0/modules.dep.temp for writing: No such file or directory make[2]: *** [_modinst_post] Error 1 make[2]: Leaving directory `/mnt/linux/src/linux-source-2.6.26' make[1]: *** [debian/stamp/install/linux-image-] Error 2 make[1]: Leaving directory `/mnt/linux/src/linux-source-2.6.26' make: *** [kernel_image] Error 2 Any help would be appreciated. Thanks, Rob Key
Re: make-kpkg fails writing to weird directories on dual or multi core processors
Hi Here it fails again. this is version 12.033 instead of 12.032 I downloaded kernel--package-12.033.tar.gz invoke like this CONCURRENCY_LEVEL=3 make-kpkg --initrd --append-to-version dickhead1.0 kernel_image kernel_headers All done in /usr/src/linux-source-2.6.32. I am running kernel vmlinuz-2.6.32-custom1.0 and this is the error WARNING: Couldn't open directory /usr/src/linux-source-2.6.32/debian/linux-image-/lib/modules/2.6.32-custom1.0: No such file or directory FATAL: Could not open /usr/src/linux-source-2.6.32/debian/linux-image-/lib/modules/2.6.32-custom1.0/modules.dep.temp for writing: No such file or directory make[2]: *** [_modinst_post] Error 1 make[2]: Leaving directory `/usr/src/linux-source-2.6.32' make[1]: *** [debian/stamp/install/linux-image-] Error 2 make[1]: Leaving directory `/usr/src/linux-source-2.6.32' make: *** [kernel_image] Error 2 Again why is it wanting to write to lib/modules/2.6.32-custom1.0 when my appendage is _dickhead1.0_ ? Some where make-kpkg has done a `uname -r` which would produce 2.6.32-custom1.0 on my computer? This is very frustrating. I purged all packages and reinstalled them all including source. Please help. thanks, Rob Key
Re: custom kernel boot problem: can't access tty
SOLUTION: to can't access tty; job control turned off Apologies for answering my own post, but this seems to be a problem many people have had. For some reason (there could be many) the boot kernel can't mount the root file system and hence cannot find all devices and tools to run the login. In my case booting a custom kernel there were no modules for squashfs and unionfs so those file systems which include the root could not be moutned. Installed squashfs-source and unionfs-source, build the kernel the build the extra modules for squashfs and unionfs with make install. Kernel must be built first as squashfs and uniofs make needs the build from /lib/modules/kernel-version/build. Ran update-initramfs -u -k custom kernel version to make the initrd. Rebuilt the compressed file system. Now linux boots and runs live from a USB memory stick with a custom kernel. Hope this helps others with the same problem. Cheers, Rob Key Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
custom kernel boot problem: can't access tty
Hi, I compiled a debian custom kernel 2.6.18 to boot a USB flash drive. The stock kernels work perfectly, but my custom kernel mounts the root fs and then gives the error message: /bin/sh Can't access tty; Job control stopped The booting process stops. The console , tty devices are all there, stock kernel works perfectly what is wrong? Thanks Rob Key Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
