On Thu, 24 Feb 2000, Mike Smith wrote:
> > > I'd hazard a guess that the presence of modules is causing the kernel
> > > linker to run and pull all the sysctl hooks for modules it's finding.
> > > I'm probably wrong, just a guess.
> ...
> > I'll go look up cold usage, and see if it necessarily
On Thu, 24 Feb 2000, Mike Smith wrote:
> > It seems Mike Smith wrote:
> > > That's possible; it may be that the kernel linker is calling something
> > > before you expect it to be called.
> >
> > Well, its rather that the delayed probe rutine I register with
> > config_intrhook_establish() is
I can reliably reproduce this problem with the following lines in
/boot/loader.conf.local
splash_bmp_load="YES"
bitmap_name="/boot/earth.bmp"
bitmap_load="YES"
I have the same VESA and splash screen options in my kernel now
(sources cvsup'ed yesterday) that I did on the system pr
On Thu, 24 Feb 2000, Soren Schmidt wrote:
> It seems Mike Smith wrote:
> > > Forgive me if I'm beating a dead horse... I'm still having the following
> > > problem if I load any modules from /boot/loader.conf:
> >
> > I've reproduced this here, and narrowed it down to Soren's ATA megacommit
> >
