Re: Panic - Kernel 2.6.14.4
On Wed, Dec 28, 2005 at 04:09:44PM -0500, Austin Denyer wrote: [skip] As an aside to this, when doing a regular 'make' you can specify the number of simultaneous jobs with the -j option (great for smp systems). Not only for SMP, usage of CONCURRENCY_LEVEL=8 on uniprocessor system also greatly reduces bulding time. -- With best regards, Oleg Gritsinevich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Panic - Kernel 2.6.14.4
On Wed, Dec 28, 2005 at 02:50:02PM -0600, Russ Cook wrote: [skip] that was the problem. I did not use the --initrd flag when compiling the kernel. As an aside, is it inherently necessary to use initrd? If No it is not necessary, but usage of initrd is widely adopted practice. the appropriate disk driver is compiled into the kernel (not as a module) can the kernel be compiled and loaded successfully without initrd? It can but also you have to compile into the kernel a driver of root filesystem. P.S. Note: on recent kernels mkinitrd may fail to create initrd image. You have to use yaird in this case. apt-cache show yaird -- With best regards, Oleg Gritsinevich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Panic - Kernel 2.6.14.4
Oleg Gritsinevich wrote: On Mon, Dec 26, 2005 at 05:13:01PM -0600, Russ Cook wrote: I'm running a stock 2.6.12 kernel (2.6.12-1-amd64-k8-smp) on an ASUS A8N32-SLI Deluxe motherboard. Processor is AMD64 4800 dual core, with 4 MB ram. I'm trying to compile and install kernel 2.6.14.4. To start, I copied the same .config file from the 2.6.12 kernel, went through the usual make-kpkg clean, menuconfig, kernel-image process, changing nothing in the .config file. After installing using dpkg -i and rebooting, I get a kernel panic because VFS can't mount the root partition (hda1). I'm using Grub. The 2.6.12 kernel boots fine, and I used the same .config file. My hard disk is a Maxtor ATA. Can anyone offer pointers to check? I don't understand why one should boot, and the other won't. I'll be happy to send .config file on request. Check for existence and contents of initrd.img corresponding to your new kernel. that was the problem. I did not use the --initrd flag when compiling the kernel. As an aside, is it inherently necessary to use initrd? If the appropriate disk driver is compiled into the kernel (not as a module) can the kernel be compiled and loaded successfully without initrd? thanks much, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Panic - Kernel 2.6.14.4
On Wed, 28 Dec 2005 14:50:02 -0600 Russ Cook [EMAIL PROTECTED] wrote: I'm running a stock 2.6.12 kernel (2.6.12-1-amd64-k8-smp) on an ASUS A8N32-SLI Deluxe motherboard. Processor is AMD64 4800 dual core, with 4 MB ram. I'm trying to compile and install kernel 2.6.14.4. To start, I copied the same .config file from the 2.6.12 kernel, went through the usual make-kpkg clean, menuconfig, kernel-image process, changing nothing in the .config file. After installing using dpkg -i and rebooting, I get a kernel panic because VFS can't mount the root partition (hda1). I'm using Grub. The 2.6.12 kernel boots fine, and I used the same .config file. My hard disk is a Maxtor ATA. Can anyone offer pointers to check? I don't understand why one should boot, and the other won't. I'll be happy to send .config file on request. As an aside to this, when doing a regular 'make' you can specify the number of simultaneous jobs with the -j option (great for smp systems). I have not found any similar option for make-kpkg. Does anyone know if such an option exists for make-kpkg? Regards, Ozz. pgpZcBztKfrHi.pgp Description: PGP signature
Re: Panic - Kernel 2.6.14.4
On Mon, Dec 26, 2005 at 05:13:01PM -0600, Russ Cook wrote: I'm running a stock 2.6.12 kernel (2.6.12-1-amd64-k8-smp) on an ASUS A8N32-SLI Deluxe motherboard. Processor is AMD64 4800 dual core, with 4 MB ram. I'm trying to compile and install kernel 2.6.14.4. To start, I copied the same .config file from the 2.6.12 kernel, went through the usual make-kpkg clean, menuconfig, kernel-image process, changing nothing in the .config file. After installing using dpkg -i and rebooting, I get a kernel panic because VFS can't mount the root partition (hda1). I'm using Grub. The 2.6.12 kernel boots fine, and I used the same .config file. My hard disk is a Maxtor ATA. Can anyone offer pointers to check? I don't understand why one should boot, and the other won't. I'll be happy to send .config file on request. Check for existence and contents of initrd.img corresponding to your new kernel. -- With best regards, Oleg Gritsinevich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Panic - Kernel 2.6.14.4
I'm running a stock 2.6.12 kernel (2.6.12-1-amd64-k8-smp) on an ASUS A8N32-SLI Deluxe motherboard. Processor is AMD64 4800 dual core, with 4 MB ram. I'm trying to compile and install kernel 2.6.14.4. To start, I copied the same .config file from the 2.6.12 kernel, went through the usual make-kpkg clean, menuconfig, kernel-image process, changing nothing in the .config file. After installing using dpkg -i and rebooting, I get a kernel panic because VFS can't mount the root partition (hda1). I'm using Grub. The 2.6.12 kernel boots fine, and I used the same .config file. My hard disk is a Maxtor ATA. Can anyone offer pointers to check? I don't understand why one should boot, and the other won't. I'll be happy to send .config file on request. Thanks much, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
