new kernel problems with pcmcia and initrd
I just recompiled my kernel and the PCMCIA does not appear to be loading. It is important that I use initrd for the root file system and that PCMCIA be built into the kernel instead of module since it is a laptop and the nic is not onboard. Where have I missed my PCMCIA step and how do I set it up as built into the kernel and not a module? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
new kernel problems with pcmcia and initrd
I just recompiled my kernel and the PCMCIA does not appear to be loading. It is important that I use initrd for the root file system and that PCMCIA be built into the kernel instead of module since it is a laptop and the nic is not onboard. Where have I missed my PCMCIA step and how do I set it up as built into the kernel and not a module? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new kernel problems with pcmcia and initrd
On Tue, 1 Apr 2003 11:05:11 -0800 Kris P.- Mother Lode Internet Tech Support [EMAIL PROTECTED] wrote: I just recompiled my kernel and the PCMCIA does not appear to be loading. It is important that I use initrd for the root file system and that PCMCIA be built into the kernel instead of module since it is a laptop and the nic is not onboard. Where have I missed my PCMCIA step and how do I set it up as built into the kernel and not a module? It isn't necessary to use initrd at all, even if you have PCMCIA. Neither is it necessary to compile PCMCIA support into the kernel. initrd is for the kernel to get modules before the root filesystem is mounted. PCMCIA support is normally started after the root filesystem is mounted, so it doesn't need to be in initrd, even if you use one. Have a look here for The Debian Way of compiling your kernel (see the advanced topics section for the scoop on making and using the latest pcmcia-cs modules): http://newbiedoc.sourceforge.net/system/kernel-pkg.html Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new kernel problems with pcmcia and initrd
I have already read this document. Sorry for the confusion. I am trying to mount my partition completely read only so that I can one day burn it to a cd. I was under the impression I had to use initrd to have the root filesystem boot onto a ram drive. If there is a another way to make a system completly readonly and have root mount on a read-only please let me know. On Tue, 1 Apr 2003 11:05:11 -0800 Kris P.- Mother Lode Internet Tech Support [EMAIL PROTECTED] wrote: I just recompiled my kernel and the PCMCIA does not appear to be loading. It is important that I use initrd for the root file system and that PCMCIA be built into the kernel instead of module since it is a laptop and the nic is not onboard. Where have I missed my PCMCIA step and how do I set it up as built into the kernel and not a module? It isn't necessary to use initrd at all, even if you have PCMCIA. Neither is it necessary to compile PCMCIA support into the kernel. initrd is for the kernel to get modules before the root filesystem is mounted. PCMCIA support is normally started after the root filesystem is mounted, so it doesn't need to be in initrd, even if you use one. Have a look here for The Debian Way of compiling your kernel (see the advanced topics section for the scoop on making and using the latest pcmcia-cs modules): http://newbiedoc.sourceforge.net/system/kernel-pkg.html Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New kernel problems
At 07:53 09-08-99 -0500, Paul Miller wrote: I usually see this error when IDE support has not been compiled in the kernel. So I'd make sure that in the Block Devices section you have 'Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support' 'Include IDE/ATA-2 DISK support' set to yes. Right on! Thanks a bundle, Paul! Dan. --- This is what we do. This is who we are. Hail Eris! -- Kallisti -- All Hail Discordia!
New kernel problems
I'm using slink, and need to recompile the kernel. This is on a computer where LILO won't install, so I have to boot off a floppy. Ran 'make menuconfig', and double-checked that Second extended fs support was not compiled as a module. In the Makefile, I set : ROOT_DEV = /dev/hdb3 Ran make-kpkg kernel_image. I then executed: dpkg -i kernel-image-2.2.6_1.00_i386.deb directing it to make a boot . I get this error on restart: VFS: Cannot open root device 03:43 Kernel panic: VFS: Unable to mount root fs on 03:43 I'm not exactly sure how to troubleshoot this. Any advice? --- This is what we do. This is who we are. Hail Eris! -- Kallisti -- All Hail Discordia!
Re: New kernel problems
Daniel Lesage wrote: VFS: Cannot open root device 03:43 Kernel panic: VFS: Unable to mount root fs on 03:43 I'm not exactly sure how to troubleshoot this. Any advice? I usually see this error when IDE support has not been compiled in the kernel. So I'd make sure that in the Block Devices section you have 'Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support' 'Include IDE/ATA-2 DISK support' set to yes. Hope this helps -- Paul Miller [EMAIL PROTECTED] Where do all the bits go when the computer is done with them?
Re: New kernel problems
VFS: Cannot open root device 03:43 Kernel panic: VFS: Unable to mount root fs on 03:43 I'm not exactly sure how to troubleshoot this. Any advice? I usually see this error when IDE support has not been compiled in the kernel. So I'd make sure that in the Block Devices section you have 'Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support' 'Include IDE/ATA-2 DISK support' set to yes. Nope... it as long as I can read the signs, the IDE device was found, so the problem seems to be that the e2sf (second extended file system) was either left aside or created as a module during the krenel creation... Run make menuconfig again and check this out in the ¨filesystems¨ part... the second extended filesystem MUST be created as part of the kernel (otherwise, how would the kernel open the e2fs filesystem to read the modules? ;-) Guilherme Zahn
Re: New kernel problems
On Mon, 9 Aug 1999, Guilherme Soares Zahn wrote: VFS: Cannot open root device 03:43 Kernel panic: VFS: Unable to mount root fs on 03:43 I'm not exactly sure how to troubleshoot this. Any advice? I usually see this error when IDE support has not been compiled in the kernel. So I'd make sure that in the Block Devices section you have 'Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support' 'Include IDE/ATA-2 DISK support' set to yes. Nope... it as long as I can read the signs, the IDE device was found, so the problem seems to be that the e2sf (second extended file system) was either left aside or created as a module during the krenel creation... Run make menuconfig again and check this out in the ¨filesystems¨ part... the second extended filesystem MUST be created as part of the kernel (otherwise, how would the kernel open the e2fs filesystem to read the modules? ;-) This is the mistake I made the first time around. I then rebuilt the kernel with e2fs built-in, but got the same error message. I'll try Paul's suggestion tonight, though. Dan.
