Alan Hourihane | 3 Apr 15:11 2007
Picon

ipl5: spurious interrupt

Hello,

I've been getting this message "ipl5: spurious interrupt" on my Cube with 
NeXTStep,
and I think it's a serial port problem, but I thought about trying NetBSD to 
see if
it can help me pinpoint the problem.

Has anyone here seen this before ??

Thanks,

Alan. 

Alan Hourihane | 3 Apr 16:46 2007
Picon

unknown binary format when booting NetBSD

I'm trying to boot the NetBSD kernel on my cube and it comes back with
"unknown binary format" even though I've gunzip'ed to my tftpboot location.

I've tried the netbsd-GENERIC kernels from 2.0.2 and 3.1 now.

Has anyone any idea what I'm doing wrong ?

Thanks,

Alan. 

Darrin B.Jewell | 4 Apr 07:13 2007
Picon

Re: unknown binary format when booting NetBSD

"Alan Hourihane" <alan_hourihane <at> hotmail.com> writes:

> I'm trying to boot the NetBSD kernel on my cube and it comes back with
> "unknown binary format" even though I've gunzip'ed to my tftpboot location.
>
> I've tried the netbsd-GENERIC kernels from 2.0.2 and 3.1 now.
>
> Has anyone any idea what I'm doing wrong ?
>
> Thanks,
>
> Alan. 

Hm.  You possibly need to load the bootloader first via tftp instead
of the kernel.

Darrin

Alan Hourihane | 4 Apr 09:44 2007
Picon

Re: unknown binary format when booting NetBSD

"Darrin B.Jewell" <dbj <at> netbsd.org> wrote in message 
news:qq8xd8oh6h.fsf <at> Cardenio.zlz.net...
> "Alan Hourihane" <alan_hourihane <at> hotmail.com> writes:
>
>> I'm trying to boot the NetBSD kernel on my cube and it comes back with
>> "unknown binary format" even though I've gunzip'ed to my tftpboot 
>> location.
>>
>> I've tried the netbsd-GENERIC kernels from 2.0.2 and 3.1 now.
>>
>> Has anyone any idea what I'm doing wrong ?
>>
>> Thanks,
>>
>> Alan.
>
> Hm.  You possibly need to load the bootloader first via tftp instead
> of the kernel.

That makes sense. It works now, but the documentation is wrong.

Alan. 

Jaime Fournier | 22 Apr 02:26 2007
Picon

Success on 4Beta2 on netbooting

Thought I would drop a note saying that
netbooting seems to be working properly.
Previously I had not been able to netboot anything past 1.6.2
without my slab timing out.
The dmesg is included.

Setup was standard tftp/bootp/nfs with the following settings on the 
server:

----------------dhcpd.conf------------------------
         host next {
                 hardware ethernet 00:00:0f:00:e1:91;
                 fixed-address 214.53.13.181;
                 filename "/next";
                 option root-path "/boot/next";
                 server-name="214.53.13.183";
                 next-server 214.53.13.183;
         }

--------------------------------------------------

On the NeXT Slab I ran the
ben()netbsd
And off it seems to work very well.

Thanks.

Jaime Fournier
ober <at> netbsd.org
(Continue reading)


Gmane