Re: ksyms broken by multiboot in NetBSD 5?

[Klaus Heinz <k.heinz%janzehn.kh-22.de@localhost>]

Julio Merino wrote:

> Could you try again with a -current kernel in the E3 partition please?
>  I remember fixing an issue like this not too long ago, so it'd be a
> matter of just pulling up that change.

I did that and the result lead to me installing a fresh NetBSD 5.0.1 on
some spare machine (without extended partitions or raidframe) and
testing boot/multiboot in boot.cfg.

Contents of /boot.cfg:
  menu=:boot netbsd
  menu=:multiboot netbsd
  menu=:boot netbsd-current-20100106 
  menu=:multiboot netbsd-current-20100106

Results:

- If I use 'boot' to boot the kernel /dev/ksyms works as expected
  (tested with 'dd').

- If I use 'multiboot' the kernel does not know the boot or root
  device and asks for them (as if I had specified '-a').
  Adding 'root=wd0a' to the multiboot lines lets the kernel find its
  boot/root device automatically.
  /dev/ksyms does not work (dd if=/dev/ksyms of=/dev/null)

It appears as if multiboot breaks /dev/ksyms even in the most basic
case for both NetBSD 5.0.1 and NetBSD-current (5.99.23 from today). 

Is it intended behaviour, that using multiboot _requires_ the 'root='
parameter? The multiboot(8) man page says that "It should not be needed
because the kernel tries its best to guess which is the root partition".


ciao
     Klaus