Thanks Brian:

That did the trick.

So the question is why does taking out the kernel debugger cause the booter
to hang?

I will investigate when I have time, does any one already know?

James

-----Original Message-----
From: Brian Gregor [mailto:bgregor@BUPHY.bu.edu]
Sent: Thursday, May 17, 2001 5:09 AM
To: James Kliegel
Subject: Re: Problems compiling a 1.5 kernel for a Mac IIsi



Leave the kernel debugger (option DDB, I think) enabled in the
kernel if you've taken it out.  On my LCIII it hangs at the same
point in the booting process without the DDB option.  It'll
increase the kernel size a little.

Hope this helps!


-brian

On Tue, 15 May 2001, James Kliegel wrote:

> Hello All:
>
> As a newbie I am trying one of everything and crashing and burning every
> other step. All part of the adventure. But if a kind soul wouldn't mind
> imparting some of their hard earned wisdom I would be most appreciative
8-).
>
> Lately I tried to compile my own kernel and install it, as a prelude to
> messing about with the code. I copied the GENERIC configuration file and
> made what seemed to be appropriate changes. After an ~20 hour compile (and
> one or two false starts, forgetting to select CODA files) I had a kernel.
> When attempting to boot it the booter gets to the "and I sez to him"
point,
> where the normal boot commandeers the screen and starts spewing NetBSD
boot
> messages, and freezes. Hmmm. After some wrestling I recovered the previous
> kernel and am back up and running.
>
> So some questions:
>
> What would cause that kind of freezing behavior in booting a kernel that
had
> compiled "successfully", or at least with no errors or warnings?
>
> Where can I find a complete list of config file options, information about
> what they do, and a "recommended settings list" for a Mac IIsi with 64M
ram,
> SCSI devices (disk, cdrom, zip), mc68882 fpu, and a nubus Ethernet card?
>
> I have been using a GENERICSBC 1.5 kernel, and that is working relatively
> fine. However after the kernel swapping incident described above I started
> getting a new error messages on boot:
>
> WSCONSCFG: WSDISPLAYIO_ADDSCREEN: cannot allocate memory
> WSCONSCFG: WSDISPLAYIO_ADDSCREEN: cannot allocate memory
> WSCONSCFG: WSDISPLAYIO_ADDSCREEN: cannot allocate memory
> WSCONSCFG: WSDISPLAYIO_ADDSCREEN: cannot allocate memory
> WSCONSCFG: WSDISPLAYIO_ADDSCREEN: cannot allocate memory
> WSCONSCFG: WSMUXADD_DEVICE: invalid argument
>
> What would cause this?
>
> Also on an unrelated topic how can I ftp NetBSD packages. I am not up on
the
> net yet, and even if I were my slow modem/ISP would preclude downloading
> large (> 1-2K . . . kidding 8-) files. So I want to ftp tarballs at work
and
> copy them to a zip to take home. I tried to ftp from ftp.netbsd.org and
some
> of the mirrors but could not get it to work. That is the sites seemed to
be
> dead, or dead slow, and would not even return the README, or package
> index.html. What is the recommended method to get packages other than
doing
> a make in /usr/pkgsrc and automagically downloading from the net?
>
> Thanks very much in advance.
>
> James
>