Re: [patch] grub incorrectly identifies ext3 as fat

[rubisher]

Hello Felix,

Felix Zielcke wrote:
> Am Samstag, den 31.10.2009, 02:44 -0400 schrieb Andrew Clausen:
> > Hi,
> >
> > 2009/10/30 Robert Millan <address@hidden>:
> > > > What about probing in the boot-loader?
> > > It's too late then.  grub-install needs to know which filesystem module has
> > > to be included in core.img.
> > What if the core.img contains modules for 2 or more file systems?
>
> That only happens if you use grub-install with --modules or you directly
> create it with grub-mkimage.
> By default there's just one module and there only needs to be one.
> The one to access /boot/grub.
> It doestn't make sense to include more then one fs module into core.img
> With grub.efi the situation seems to be different though. But IMO it's a
> bug there.
To boot my debian installation on an ibm p5 lpar, I am trying to install grub2 
i.e. working with grub-ieee1275.
I try first to rebuild grub-1.97~beta4 but it was failing.
I finaly find out that I can build and boot grub2 (only) with another gcc 
optimization option (-O0 in place of default -Os).

But it still failed to boot the linux kernel after grub-install:
1/ here is the chrooted mount points:
/dev/sdb6 on /mnt/NewInst type ext3 (rw)
/dev/sdb3 on /mnt/NewInst/boot type ext3 (rw)
/dev/sdb1 on /mnt/NewInst/boot/grub type vfat (rw)
/dev/mapper/p5tst001vg-var on /mnt/NewInst/var type ext3 (rw)

ps: /mnt/NewInst/boot/grub have to be a mount point for grub-install;
if it wasn't: # grub-install hd1
/boot/grub must be a mount point.
and must be a fat16 (or iirc hfs) for ofs

2/ a typical menu entry:
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.30-2-powerpc64" {
        insmod ext2
        set root=(hd1,3)
        search --no-floppy --fs-uuid --set 16ef0754-c845-46e9-a948-b9669ee68329
        linux   /vmlinux-2.6.30-2-powerpc64 
root=UUID=3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed ro  quiet
        initrd  /initrd.img-2.6.30-2-powerpc64
}

and at the grub sh prompt, ls doesn't report any disk?

Even thought: # more /boot/grub/device.map
(hd0)   /dev/sda
(hd1)   /dev/sdb

Could it be for the reason you explained above?

I am worry of it because when I copy vmlinux-2.6.30-2-powerpc64 and initrd.img-2.6.30-2-powerpc64 in the 
/mnt/NewInst/boot/grub fs and this simple menuentry:
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.30-2-powerpc64" {
        linux   /vmlinux-2.6.30-2-powerpc64 root=UUID=3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed ro sysrq=1 insmod=sym53c8xx 
insmod=ipr quiet
        initrd  /initrd.img-2.6.30-2-powerpc64
}

the debian installation finaly boot fine ;<)
The problem is that this vfat fs afaik must be < then 24Mb and btw couldn't contained more then one kernel image (and its 
initrd), though.

Tia for further advise,
        J.