My /dev/hda primary partition, like many of you no doubt, is vfat with
windoze on it. I have found that if I build a kernel (2.4.x) without
including fat and vfat IN the kernel, then I get the "kernel panic, cannot
mount root fs" message. This has happened to me several times lately and in
each case, I go to the filesystems portion of xconfig and see that fat and
vfat are modules instead of built in. I change this and all is subsequently
well.
My drive sequencing never changes (no /dev/hda to /dev/hd<something else>).
On Saturday 31 March 2001 07:24, Don wrote:
> On Saturday 31 March 2001 09:12, you wrote:
> > On Friday 30 March 2001 19:15, you wrote:
> > > Anyone have any ideas where I might be going wrong here:
> >
> >----------------------- snip ------------------------
> >
> > > Bob Silva
> > > bob @bravenet.com
> >
> > The 2.4 kernel was built with those awful devices in mind--the
> > controllers that put disks just anywhere. So kernel 2.4 is looking for
> > /dev/hda and it has relocated /dev/hde there! The result is that grub or
> > lilo is misdirecting the kernel to a (now nonexistent) /dev/hdex root.
> > The incompatibility does not stop there--/etc/fstab has all the wrong
> > mount points since they all point to /dev/hde which is now /dev/hda.
> > With a 2.4 install and running, it seems to work except for
> >
> > Of course it all works with windows. This hardware was not built with
> > linux in mind.
> >
> > Civileme
>
> For My dual processor board here is what the lilo.conf file looks like.
> Maybe you can get some idea from this example. Linux smp is being run from
> hdf drive, and booted from the hde mbr partition.
[...]
--
Against stupidity, the gods themselves contend in vain.
