Martin Kreiner
2003-Jan-28 13:14 UTC
[syslinux] syslinux append / command line problems kernel 2.4.19
hi, command-line parsing for kernels >= 2.4.19 doesn't work for me very well. i testet up to syslinux-2.01-pre3 and lines like APPEND nfsroot=192.168.168.1:/nfsboot ip=192.168.168.202:192.168.168.1:192.168.168.1:255.255.255.0:thin1 have no effect. bootmessage like: ... zone(2): 0 pages. Kernel command line: Initializing CPU#0 ... even passing the command line parameters at the syslinux boot prompt have no effect and do not reach the kernel. some keywords like vga=ask do work, but do not appear when doing a "cat /proc/cmdline". whith kernel 2.4.18 everything works fine. i guess it's because of the changes in linux/init/* hope to see a working patch soon m.kreiner p.s. haven't tested newer kernels > 2.4.19, but i guess it will be the same problem
H. Peter Anvin
2003-Jan-28 17:55 UTC
[syslinux] syslinux append / command line problems kernel 2.4.19
Martin Kreiner wrote:> hi, > > command-line parsing for kernels >= 2.4.19 doesn't work for me very > well. i testet up to syslinux-2.01-pre3 and lines like > > APPEND nfsroot=192.168.168.1:/nfsboot > ip=192.168.168.202:192.168.168.1:192.168.168.1:255.255.255.0:thin1 > > have no effect. bootmessage like: > > ... > zone(2): 0 pages. > Kernel command line: > Initializing CPU#0 > ... > > even passing the command line parameters at the syslinux boot prompt > have no effect and do not reach the kernel. some keywords like vga=ask > do work, but do not appear when doing a "cat /proc/cmdline". > whith kernel 2.4.18 everything works fine. i guess it's because of the > changes in linux/init/* > > hope to see a working patch soon > > m.kreiner > > p.s. haven't tested newer kernels > 2.4.19, but i guess it will be the > same problem >Please test the latest kernel. This sounds like a (very serious) kernel bug. -hpa