GRUB 0.5.97 doesn't handle kernel parameters

[tschweikle]

Hi!

GRUB 0.5.97 seems to not handle kernel parameters given on the kernel line to a
linux kernel:

fdisk -l:
Disk /dev/sda: 255 heads, 63 sectors, 1232 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1   *         2       129   1028128+   b  Win95 FAT32
/dev/sda2           130      1232   8859847+   f  Win95 Ext'd (LBA)
/dev/sda3             1         1      8001   83  Linux
/dev/sda5           130       426   2385621    b  Win95 FAT32
/dev/sda6           427      1232   6474163+   b  Win95 FAT32

Partition table entries are not in disk order

Disk /dev/sdc: 255 heads, 63 sectors, 4492 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sdc1             1         1      8001   83  Linux
/dev/sdc2             2       129   1028160    7  HPFS/NTFS
/dev/sdc3           258      4492  34017637+   f  Win95 Ext'd (LBA)
/dev/sdc4           130       257   1028160    7  HPFS/NTFS
/dev/sdc5           258       576   2562336   83  Linux
/dev/sdc6           577       609    265041   82  Linux swap
/dev/sdc7           610       928   2562336   83  Linux
/dev/sdc8           929      1948   8193118+  83  Linux
/dev/sdc9          1949      4492  20434648+   b  Win95 FAT32

Partition table entries are not in disk order

Linux completely resides on sdc. Trying to boot with GRUB:

root (hd1,0)
kernel /vmlinuz initrd=/initrd root=/dev/sdc5 vga=7
initrd /initrd

seems to load kernel and initrd correctly.
Booting with 'boot' now leads to a kernel panic. Initrd isn't found and thus
the SCSI driver is missing and /dev/sdc5 couldn't be mounted. GRUB 0.5.95
didn't had any problem.

I have checked geometry given by GRUB and fdisk. There the same.

I saw some changes in how GRUB 0.5.97 handles kernel parameters and an initrd.
Maybe there is an error somewhere? Or did I overlook some change loading kernel
and initrd?

BTW: an older LILO version hadn't have problems, but a newer on has too. It
just shows L 01 01 01 01 01 01 01 ... looping forever. Only resetting the
system helps.

--
Thomas