Hi Bruce et al.,


 > I have a powerbook 540 and first it boots macos.
Nothing unusual here ;)

 > Once booted, I set the date
Here start the error count...

 >(because I'm too lazy to rip the whole thing apart
 > to replace the PRAM bat)
Here is the main error...

 > but then I turn on ethertalk.  If I
 > don't turn on ethertalk I don't have an ethernet interface in
 > NetBSD.
You do not need to do that if only you replace the PRAM Battery.

 > My guess is that since it's a powerbook it does not
 > turn on the ethernet by default.
Wrong guess...

Change the PRAM battery and you don't need anymore to set the date _NOR_ to turn 
on EtherTalk.

PRAM stands for Protected RAM (call it Parameter RAM if you prefer): some 
informations are saved in the PRAM: the date, the Network hardware connexion 
type, the color depth (0 ... 32 bits), startup disk (I think) etc.

Each time the computer is shut down, these parameters are maintained by the 
(PRAM) Battery. If this battery is out of service, you loose your values and at 
the next cold restart, the computer uses the (low) defaults: Network default 
hardware is set to LocalTalk, black and white video, clock start at january 1st, 
1904 (this is for pre-OSX) and so on.

Hot restart doesn't suffer from this mechanism: you still have your settings 
(that is one reason why some Control Panel changes applies only after a cold start).

BTW: I think that the default value is AppleTalk = ON.

HTH,

Emile


Happy New Year to everybody there.

Bruce ONeel wrote:

> Hi,
> 
> Thanks, but my boot sequence is a bit complex :-)
> 
> I have a powerbook 540 and first it boots macos.  Once booted I 
> set the date (because I'm too lazy to rip the whole thing apart
> to replace the PRAM bat) but then I turn on ethertalk.  If I 
> don't turn on ethertalk I don't have an ethernet interface in
> NetBSD.  My guess is that since it's a powerbook it does not
> turn on the ethernet by default.
> 
> Then I start the NetBSD booter, unplug the ethernet cable, and
> boot NetBSD.  I plug the ethernet cable back in once I have a login
> prompt and things are fine.
> 
> If I don't unplug the ethernet cable, and/or wait too long I frequently,
> though not always, get a crash.  This problem has been around
> for 1.5.3, 1.6, and 1.6.1.
> 
> In my case though turning off appletalk didn't solve the problem.
> 
> Cheers
> 
> bruce
> 
> Bob Nestor <rnestor@augustmail.com> wrote:
> 
>>Date: Sun, 11 Jan 2004 17:37:37 -0600
>>From: Bob Nestor <rnestor@augustmail.com>
>>Subject: Re: fpu trap with current from 2 Jan
>>To: David Rogers <davidrogers23@earthlink.net>
>>Cc: Bruce ONeel <edoneel@sdf.lonestar.org>, port-mac68k@netbsd.org
>>content-length: 870
>>
>>On Jan 11, 2004, at 12:46 PM, David Rogers wrote:
>>
>>
>>>I've been getting something very similar right after it lists 
>>>available memory.  It says Kernel Illegal Instruction Trap.  I have a 
>>>IIci with a Daystar Turbo 040 installed so maybe there's more than 
>>>just FPU problems.  Not sure though.
>>>
>>>Here is the dump:
>>>trap type 2, code = 0x0, v = 0x0
>>>kernel program counter = 0x1258e
>>>
>>>pid = 0, lid = 1, pc = 0001258E, ps = 2704, sfc = 1, dfc = 1
>>>
>>>dreg: 00000000 00000001 0011A290 00004AA0 8004002E FEE00020 00000000 
>>>00000000
>>>areg: 00153790 001B9E9C 0006A7B8 00123B68 00153940 01DF1698 001B9F60 
>>>FFFFCFFC
>>>
>>>Hope this helps.  Anyone else having problems?
>>
>>Did you happen to leave AppleTalk enabled in MacOS before you booted 
>>into NetBSD?
>>
>>That seemed to cause the problem for me.  Disabling AppleTalk before 
>>booting made the problem go away.
>>
>>-bob
> 
>