Darren Crane <[EMAIL PROTECTED]> writes:
[...]
> 2) After the install, I can not boot the system from milo. I can no
> longer do a "ls sda1:", I get...
> %
> %
>
> I don't know what that means. I was able to boot with the following...
>
> milo> boot scd0:/boot/v.gz root=/dev/sda1
>
> But this is not an excellent long term solution. Any ideas why the milo
> that easily booted redhat 6.0 and 6.2 will not boot Mandrake 7.0?
> And why it can no longer ls the fiesystem?
if i remember right, the pb is milo not handling current ext2.
here is a quote from Stefan van der Eijk:
> > > All the milo's don't see andything on sdc2 with mandrake installed
> > > ("ls sdc2:/" gives nothing, "ls sdc2:/boot/ gives "path component
> > > is not a directory"). With RH6.1 I can list the files in
> > > the directories...
> >
> > And you set ext2 on these partitions from a Mandrake installer?
> > And they are using something like e2fsprogs-1.18 or e2fsprogs-1.17?
> > I think that I may know what this can be.
> >
> > New 'mke2fs' creates file systems with 'sparse superblock' and, above
> > some size limit (don't remember now precisely) with 4096 blocks. You
> > can see these parameters with 'tune2fs -l <device>'. As milos are
> > usually based on older kernels they do not know how to read such file
> > systems. 'aboot' may have the same problems. Thus ext2 partition on
> > which your kernel lives should be created with '-b 1024 -O none'. Red
> > Hat installer is aware about this. "Filesystem features" can be
> > changed with tune2fs but to change a block size one has to reformat.
> >
> > Drop your kernel on a FAT partition with milo and this should solve
> > that as it will be the readable to milo. On x86 lilo does not suffer
> > as a boot code does not know anything about file systems at all.
> > It loads from absolute disk locations.
This mail could hold the key to why milo can't see anything on the
"mandrake formatted drive".
