On 5/27/06, Pavel Cahyna <pavel@netbsd.org> wrote:
> On Sat, May 27, 2006 at 09:07:48PM +0100, Chavdar Ivanov wrote:
> > On 5/27/06, Pavel Cahyna <pavel@netbsd.org> wrote:
> > >On Sat, May 27, 2006 at 01:13:12PM +0100, Chavdar Ivanov wrote:
> > >> Hi,
> > >>
> > >> It seems if one has
> > ...
> > >> 12117      1 netstat  exit(0x1)
> > >> .....
> > >>
> > >> Obviously with no ksyms in the kernel, it cannot open /dev/ksyms and
> > >> carries on it's work.
> > >>
> > >> Any ideas?
> > >>
> > >> (BTW this is -current from yesterday, i386).
> > >
> > >- did it work before yesterday?
> > >
> > >- do you have "options MULTIBOOT"?
> > Yes, that is necessary now AFAIU:
> > ...
> > options         MULTIBOOT       # Multiboot support (see multiboot(8))
> > options         MULTIBOOT_SYMTAB_SPACE=3D1048576
> > ...
>
> Thanks. Did it work before? Or is it your first kernel built with
> MULTIBOOT?
>
> Another question, do you use grub from pkgsrc? Which version?
>
> BTW I think grub should be able to (somehow) boot a kernel without
> MULTIBOOT.

Well, Quentin's remark earlier was spot on I think. The same kernel
works just fine if loaded by the same grub (from pkgsrc -
grub-0.97nb5) if I use the chainloader option:
....
title NetBSD-chain
root (hd0,2,a)       # NetBSD on 3rd MBR partition of 1st IDE disk
chainloader +1         (* effectively this means the partition has
been loaded directly with no                      reference to grub's
netbsd knowledge *)

title NetBSD
root (hd0,2,a)
kernel /netbsd console=3Dpc root=3Dwd0a (* this is the problematic bit,
may be other options will result in working configuration *).
...

The second section is the default, and it is apparently causing the
problem, although I find it extraordinary that a kernel loader should
present such a problem - I would expect it either to work, or not, but
not to result in obscure (or not so...) problems much further down the
line.

It's kinda interesting why, although obviously it can easily be avoided.

>
> Pavel
>

Chavdar