Hallo Miod,
thank you for your answer. I got further this time with the last
snapshot as from July 19.
However I hit another problem: I have an Insite Floptical drive
installed and system hangs on its initialization. I'm not sure if it's a
hardware or software problem. If I pull out the drive, everything seems
to go smooth.
Here is a boot log with Floptical drive installed:
>> bootp()bootecoff bootp()bsd.rd.IP22
Setting $netaddr to 192.168.28.42 (from server )
Obtaining bootecoff from server
38752+208+2080 entry: 0x880020f0
OpenBSD/sgi-IP22 ARCBios boot version 1.2
arg 0: bootp()bootecoff
arg 1: bootp()bsd.rd.IP22
arg 2: ConsoleIn=serial(0)
arg 3: ConsoleOut=serial(0)
arg 4: SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
arg 5: OSLoader=sash
arg 6: OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
arg 7: OSLoadFilename=/unix
Boot: bootp()bsd.rd.IP22
Setting $netaddr to 192.168.28.42 (from server )
Obtaining bsd.rd.IP22 from server
Setting $netaddr to 192.168.28.42 (from server )
Obtaining bsd.rd.IP22 from server
7122000+904192 [91Setting $netaddr to 192.168.28.42 (from server )
Obtaining bsd.rd.IP22 from server
+125520+71859]=0x7d7ef8
ARCS32 Firmware Version 1.10
Found SGI-IP22, setting up.
Initial setup done, switching console.
[ using 198312 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2012 OpenBSD. All rights reserved.
http://www.OpenBSD.org
uvm_km_kmem_grow: grown to 0xc000000008000000
OpenBSD 5.1-current (RAMDISK-IP22) #33: Wed Jun 13 00:16:05 MDT 2012
[email protected]:/sys/arch/sgi/compile/RAMDISK-IP22
real mem = 134217728 (128MB)
rsvd mem = 802816 (1MB)
avail mem = 123797504 (118MB)
mainbus0 at root: Indigo2
cpu0 at mainbus0: MIPS R4400 CPU rev 3.0 250 MHz, R4010 FPC rev 0.0
cpu0: cache L1-I 16KB D 16KB direct, L2 2048KB direct
clock0 at mainbus0: ticker on int5 using count register
int0 at mainbus0 addr 0x1fbd9000
imc0 at mainbus0: revision 3
gio0 at imc0
impact0 at gio0 addr 0x1f000000: MG10 Impact
impact0: device has not been setup by firmware!
hpc0 at gio0 addr 0x1fb80000: SGI HPC3 (onboard)
zs0 at hpc0 offset 0x00059830 irq 29: 85230
zstty0 at zs0 channel 1: console
zstty1 at zs0 channel 0
pckbc0 at hpc0 offset 0x00059840 irq 28
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0
sq0 at hpc0 offset 0x00054000 irq 3: Seeq 80c03, address 08:00:69:09:8d:df
wdsc0 at hpc0 offset 0x00044000 irq 1: WD33C93B, 20.0 MHz, burst DMA
wdsc0: microcode revision 0x0d, fast SCSI
scsibus0 at wdsc0: 8 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SGI, QUANTUM XP34300, S89C> SCSI2
0/direct fixed serial.SGI_QUANTUM_XP34300_CX53541129
sd0: 4303MB, 512 bytes/sector, 8813870 sectors
sd1 at scsibus0 targ 2 lun 0: <INSITE, I325VM *F, 0387> SCSI1 0/direct
removable
probe(wdsc0:2:1): wdsc0: timed out; asr=0x00 [acb 0xc000000002838000
(flags 0x1, dleft 24)], <state 1, nexus 0x0, resid 24, msg(q 0,o
0)>probe(wdsc0:2:1): ABORT in timeout: csr=0x85, asr=0x00
probe(wdsc0:2:1): wdsc0: timed out; asr=0x00 [acb 0xc000000002838000
(flags 0x41, dleft 24)], <state 1, nexus 0x0, resid 24, msg(q 0,o
0)>probe(wdsc0:2:1): ABORT in timeout: csr=0x85, asr=0x00
And here is a boot log without Floptical drive:
>> bootp()bootecoff bootp()bsd.rd.IP22
Setting $netaddr to 192.168.28.42 (from server )
Obtaining bootecoff from server
38752+208+2080 entry: 0x880020f0
OpenBSD/sgi-IP22 ARCBios boot version 1.2
arg 0: bootp()bootecoff
arg 1: bootp()bsd.rd.IP22
arg 2: ConsoleIn=serial(0)
arg 3: ConsoleOut=serial(0)
arg 4: SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
arg 5: OSLoader=sash
arg 6: OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
arg 7: OSLoadFilename=/unix
Boot: bootp()bsd.rd.IP22
Setting $netaddr to 192.168.28.42 (from server )
Obtaining bsd.rd.IP22 from server
Setting $netaddr to 192.168.28.42 (from server )
Obtaining bsd.rd.IP22 from server
7122000+904192 [91Setting $netaddr to 192.168.28.42 (from server )
Obtaining bsd.rd.IP22 from server
+125520+71859]=0x7d7ef8
ARCS32 Firmware Version 1.10
Found SGI-IP22, setting up.
Initial setup done, switching console.
[ using 198312 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2012 OpenBSD. All rights reserved.
http://www.OpenBSD.org
uvm_km_kmem_grow: grown to 0xc000000008000000
OpenBSD 5.1-current (RAMDISK-IP22) #33: Wed Jun 13 00:16:05 MDT 2012
[email protected]:/sys/arch/sgi/compile/RAMDISK-IP22
real mem = 134217728 (128MB)
rsvd mem = 802816 (1MB)
avail mem = 123797504 (118MB)
mainbus0 at root: Indigo2
cpu0 at mainbus0: MIPS R4400 CPU rev 3.0 250 MHz, R4010 FPC rev 0.0
cpu0: cache L1-I 16KB D 16KB direct, L2 2048KB direct
clock0 at mainbus0: ticker on int5 using count register
int0 at mainbus0 addr 0x1fbd9000
imc0 at mainbus0: revision 3
gio0 at imc0
impact0 at gio0 addr 0x1f000000: MG10 Impact
impact0: device has not been setup by firmware!
hpc0 at gio0 addr 0x1fb80000: SGI HPC3 (onboard)
zs0 at hpc0 offset 0x00059830 irq 29: 85230
zstty0 at zs0 channel 1: console
zstty1 at zs0 channel 0
pckbc0 at hpc0 offset 0x00059840 irq 28
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0
sq0 at hpc0 offset 0x00054000 irq 3: Seeq 80c03, address 08:00:69:09:8d:df
wdsc0 at hpc0 offset 0x00044000 irq 1: WD33C93B, 20.0 MHz, burst DMA
wdsc0: microcode revision 0x0d, fast SCSI
scsibus0 at wdsc0: 8 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SGI, QUANTUM XP34300, S89C> SCSI2
0/direct fixed serial.SGI_QUANTUM_XP34300_CX53541129
sd0: 4303MB, 512 bytes/sector, 8813870 sectors
wdsc1 at hpc0 offset 0x0004c000 irq 2: WD33C93B, 20.0 MHz, burst DMA
wdsc1: microcode revision 0x0d, fast SCSI
scsibus1 at wdsc1: 8 targets, initiator 0
haltwo at hpc0 offset 0x00058000 irq 12 not configured
pione at hpc0 offset 0x00059800 irq 5 not configured
panel at hpc0 offset 0x00059850 irq 9 not configured
dsclock0 at hpc0 offset 0x00060000
eisa0 at imc0 irq 27
boot device: sd0
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T
Welcome to the OpenBSD/sgi 5.1 installation program.
(I)nstall, (U)pgrade or (S)hell?
If you are interested in debuging this issue, I would be glad to support
you as I can.
wbr,
Dimitri Sokolyuk
