On Thu, 2003-07-24 at 17:23, Colin Watson wrote: > On Thu, Jul 24, 2003 at 08:52:52AM -0500, Drew Scott Daniels wrote: > > On 23 Jul 2003, Shri Shrikumar wrote: > > > On Wed, 2003-07-23 at 16:45, Drew Scott Daniels wrote: > > > > With the kernel image from a disk (2.4.20-bf2.4) and the root > > > > device set to /dev/hda1 my "computer" boots up fine. With newer > > > > 2.4 kernel images (kernel-image-2.4-386, kernel-image-2.4.21-1-386 > > > > kernel-image-2.4.21-2-386) I can't seem to boot. > > > > > > > > I've tried: > > > > root=/dev/hda1 > > > > root=/dev/ide/host0/bus0/target0/lun0/part1 > > > > root=/dev/discs/disc0/part1 > > > > > > > > I tried these with and without the devfsd package installed and > > > > there didn't seem to be a difference. > > > > > > What filesystem is on your root and does the new kernel have > > > built-in support for it ? I dont think having a module is adequate > > > since the kernel wont be able to access the filesystem to load the > > > module > > > > ext2. I would hope that the Debian distributed kernel would have built > > in support for ext2. > > It may well expect you to use an initrd for that. > > -- > Colin Watson [EMAIL PROTECTED] >
If my memory serves me right the packaged debian 2.4 kernels (except the instelation disk kernel) all or most use an initrd. The ones I installed did, but I didn't use a stock kernel in a long time. This requires adding an initrd line to lilo or whatever bootmanager you use. I think its a boot option. If I remeber correctly when you install the kernel it gives you a message concerning what you need to do to get it working. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
