Syslinux - Aug 2005 - Help me with my memory

Okay, now, before 3.10 is finalized... what bug reports am I still 
forgetting?

	-hpa

H. Peter Anvin wrote:
> Okay, now, before 3.10 is finalized... what bug reports am I still 
> forgetting?
>
>     -hpa

on the nice-to-have list:

global APPEND, that is suplemented, not overridden by label-specific 
APPENDs,
We have APPEND - to clear existing.

bash-style \
line wraps.

I reported a while back (6/08) that I was seeing spurious additions to 
the bood-line.
Im not seeing it now, but it could be Im just not tickling it properly.

subject: unknown boot options on kernel command line.
heres an excerpt:

b4 extending: (the last bit is truncated)

Jun  4 06:31:05 truck kernel: Kernel command line: 
BOOT_IMAGE=vmlinuz-2.6.12-rc5-mm2-soekris-v1 console=ttyS0,115200n81 
root=/dev/nfs nfsroot=192.168.42.1:/nfshost/truck 
nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 
panic=5 initrd=initrd-2.6.12-rc5-mm2-soekris-v1.img kgdbwai

Jun  4 07:33:58 truck kernel: Kernel command line: 
console=ttyS0,115200n81 root=/dev/nfs 
nfsroot=192.168.42.1:/nfshost/truck 
nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 
panic=5 initrd=initrd-2.6.12-rc5-mm2-soekris-v1.img 
BOOT_IMAGE=vmlinuz-2.6.12-rc5-mm2-soekris-v1 2.6.12-

after the patch, the pieces are complete.

Jun  8 13:16:51 truck kernel: Kernel command line: 
console=ttyS0,115200n81 root=/dev/nfs 
nfsroot=192.168.42.1:/nfshost/truck 
nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 
panic=5 initrd=initrd-2.6.12-rc6-mm1-soekris-v1.img 
BOOT_IMAGE=vmlinuz-2.6.12-rc6-mm1-soekris-v1 2.6.12-rc6-mm1-soekris-v1
Jun  8 13:16:51 truck kernel: Unknown boot option 
`2.6.12-rc6-mm1-soekris-v1': ignoring

what Im wondering about is the last parameter, after the BOOT_IMAGE= part.
why is it there ?


switching to IPAPPEND 1, I get this:

Kernel command line: console=ttyS0,115200n81 root=/dev/nfs 
nfsroot=192.168.42.1:/nfshost/truck 
nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 
panic=5 initrd=initrd-2.6.12-rc6-mm1-soekris-v1.img 
BOOT_IMAGE=vmlinuz-2.6.12-rc6-mm1-soekris-v1 
ip=192.168.42.100:192.168.42.1:10.0.0.1:255.255.255.0 
2.6.12-rc6-mm1-soekris-v1
Unknown boot option `2.6.12-rc6-mm1-soekris-v1': ignoring

the ip= I expect, but again that trailing argument is there.
same for the following, with IPAPPEND 2

Kernel command line: console=ttyS0,115200n81 root=/dev/nfs 
nfsroot=192.168.42.1:/nfshost/truck 
nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 
panic=5 initrd=initrd-2.6.12-rc6-mm1-soekris-v1.img 
BOOT_IMAGE=vmlinuz-2.6.12-rc6-mm1-soekris-v1 BOOTIF=01-00-00-24-c2-46-c8 
2.6.12-rc6-mm1-soekris-v1
Unknown boot option `2.6.12-rc6-mm1-soekris-v1': ignoring


the extra option appears regularly.
Note also: in the 1st example, the BOOT_IMAGE occurs
very early in the command-line, so there may be a couple things going on.

What about the memdisk bugs regarding dos images while booting USB on 
IBM machines?
Any chance of looking deeper into the problem?

Quinn

H. Peter Anvin wrote:
> Okay, now, before 3.10 is finalized... what bug reports am I still 
> forgetting?
>
>     -hpa
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>

H. Peter Anvin wrote:
> Quinn wrote:
>
>> What about the memdisk bugs regarding dos images while booting USB on 
>> IBM machines?
>> Any chance of looking deeper into the problem?
>
>
> Could you please try 3.10-pre21 and see if it helps?
>
>     -hpa
>
Sorry, still no difference.  Any chance it could print out debugging 
output to see what values
are different compared to other hardware?  I have access to both IBM and 
Dell machines that
can boot USB keys - so far Dell machines work memdisk dos images, but 
IBM machines don't.

Quinn