I had the same problem on my R10000 O2 (the resource shortage message). 
  I worked arround it by plugging in a 3com 3c905 network card into the 
(single) spare pci slot.  Then I boot via dhcp/tftp with the onboard 
ethernet controller (the one not supported by netbsd), and swap the 
cable to the 3com afterwards.  I can then install from ftp instead of 
cdrom.  That appears to solve the problem.

Ie the problem is with the scsi cdrom and not the scsi disk, or that is 
what I think.

This whole process was a lot of fun, and the old Data General dumb 
terminal saw a lot of action on Friday :-)  Never thought I'd work on 
one of these green screens again...

Unfortunately I botched something up during the install process and now 
it can't boot because /sbin/init is missing.  will retry later.

Cheers,
Izak

Jose R.Rey wrote:
> 
> El 23/11/2003, a las 5:22, Christopher SEKIYA escribió:
> 
>> On Sun, Nov 23, 2003 at 05:17:36AM +0100, Jose R.Rey wrote:
>>
>>> I installed from netboot to get GENERIC kernel, and use the CD to  
>>> install
>>> the sets,
>>
>>
>> Why didn't you boot from the CD?
> 
> 
> when i try to boot from the CD burned from the last snapshot iso image,
> a really ugly kernel message appear :(
> 
> BEGIN
> 
> System Maintenance Menu
> 
> 1) Start System
> 2) Install System Software
> 3) Run Diagnostics
> 4) Recover System
> 5) Enter Command Monitor
> 
> Option? 5
> Command Monitor.  Type "exit" to return to the menu.
>  > boot -f pci(0)scsi(0)cdrom(4)rdisk(0)partition(8)ip3xboot
> 46624+416 entry: 0x80002000
> 
> NetBSD/sgimips 1.6ZF Bootstrap, Revision 1.2
> (wileyc@izu, Thu Nov 20 14:15:56 JST 2003)
> 
> devopen: pci(0)scsi(0)cdrom(4)rdisk(0)partition(0) type scsi file ip3x
> 8265808+294092=0x829f80
> 
> Exception: <vector=Normal>
> Status register: 0x34010082<CU1,CU0,FR,DE,IPL=8,KX,MODE=KERNEL>
> Cause register: 0x8008<CE=0,IP8,EXC=RMISS>
> Exception PC: 0x8000b61c, Exception RA: 0x80002300
> Read TLB miss exception, bad address: 0x0
>   Saved user regs in hex (&gpda 0x810617d8, &_regs 0x810619d8):
>   arg: 81070000 8000d6e8 0 2
>   tmp: 81070000 a13fa678 a13faa78 0 0 a13fab68 7 810540a0
>   sve: 81070000 4015fa0c 0 4618fbd8 0 4047cfc7 0 3ebf5e51
>   t8 81070000 t9 0 at 0 v0 402003f7 v1 0 k1 8000d6e8
>   gp 81070000 fp 0 sp 0 ra 0
> 
> PANIC: Unexpected exception
> 
> [Press reset or ENTER to restart.]
> 
> EOF
> 
> 
>>
>>> yes, the NIC is not detected, this is the reason that i have not  tested
>>> with NFS export
>>
>>
>> The on-board NIC is not yet supported.  You must use a PCI NIC (fxp,  
>> rtk, and
>> url via USB are well-tested).
>>
>> Until I work out this weird ahc problem, you should probably fetch 
>> the  sets
>> via the PCI network interface.
>>
>> -- Chris
>>     GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)
>>
> ------------------------------------------------------------------------ 
> ------
> Microsoft: A donde quieres ir hoy?
> Linux: A donde quieres ir mañana?
> FreeBSD: Chicos, vais a venir o que?
> OpenBSD: Hey tios, os dejasteis algunos agujeros aqui!!
> ------------------------------------------------------------------------ 
> ------
> 
> 


-- 
Man who speeds in town reaches red traffic light first.

------------------------------------------------------------------------
Izak Burger                                  Email: iburger@cs.sun.ac.za
Homepage: http://www.cs.sun.ac.za/~iburger/  Tel: +27 21 808 4863

Please avoid sending me Word attachments.
See http://www.cs.sun.ac.za/~iburger/noword.html