arzon
What's in a name?
Arzon is a river from Auvergne, ending up feeding the Loire river.
History
Autumn 2000: I drove to Germany to pick mvme88k hardware, to work on the (then)
dying OpenBSD port to this architecture: a bunch of large (and heavy) MVME188
systems, and a MVME187 system.
The MVME187 board was not supposed to be part of the lot, but I raised the issue that, as OpenBSD was not running reliably on the MVME188 yet, I needed a MVME187 system to use as a starting point.
So after collecting all the MVME188 gear, we drove to one guy's own place, and he went to his own machine room, logged on a terminal, halted the operating system, powered down a small VME rack, carefully removed a MVME187 board from it, and gave it to me.
This was a 25MHz MVME187 board with 32MB of memory, and this is the board I did most of the initial mvme88k renovation work on.
Then I eventually have been able to replace it with a 33MHz board, and switched to a 64MB memory board. Once the MVME197 support became stable enough, I downgraded it back to 32MB, in order to use the precious 64MB board on a MVME177 system instead.
The MVME187 board was not supposed to be part of the lot, but I raised the issue that, as OpenBSD was not running reliably on the MVME188 yet, I needed a MVME187 system to use as a starting point.
So after collecting all the MVME188 gear, we drove to one guy's own place, and he went to his own machine room, logged on a terminal, halted the operating system, powered down a small VME rack, carefully removed a MVME187 board from it, and gave it to me.
This was a 25MHz MVME187 board with 32MB of memory, and this is the board I did most of the initial mvme88k renovation work on.
Then I eventually have been able to replace it with a 33MHz board, and switched to a 64MB memory board. Once the MVME197 support became stable enough, I downgraded it back to 32MB, in order to use the precious 64MB board on a MVME177 system instead.
Usage
This board, either as a 25MHz or a 33MHz system, has been the main
OpenBSD/mvme88k development and build system until the end of the year 2007,
when MVME197 systems took over.
In the early days, it would be installed in a small 3-slot VME backplane, as can be seen in the pictures from 2005 and earlier. The power supply of the backplane had to be repaired once, but on its second failure, the damage was too painful to fix, so I had to put this board in the main VME rack, which I was rebuilding at the same time.
In the early days, it would be installed in a small 3-slot VME backplane, as can be seen in the pictures from 2005 and earlier. The power supply of the backplane had to be repaired once, but on its second failure, the damage was too painful to fix, so I had to put this board in the main VME rack, which I was rebuilding at the same time.
dmesg
Here is a recent dmesg from that system:
[ using 209375 bytes of bsd a.out 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
OpenBSD 5.2 (GENERIC) #697: Sat Aug 4 21:05:30 GMT 2012
root@arzon.gentiane.org:/usr/src/sys/arch/mvme88k/compile/GENERIC
real mem = 33554432 (32MB)
avail mem = 29704192 (28MB)
mainbus0 at root: Motorola MVME187, 33MHz
cpu0: M88100 rev 0xb, 2 CMMU
cpu0: M88200 (16K) rev 0x9, full Icache, M88200 (16K) rev 0x9, full Dcache
pcctwo0 at mainbus0 addr 0xfff00000: rev 0
memc0 at pcctwo0 offset 0x43000: MCECC rev 0
nvram0 at pcctwo0 offset 0xc0000: MK48T08
cl0 at pcctwo0 offset 0x45000 ipl 3: console
osiop0 at pcctwo0 offset 0x47000 ipl 2: NCR53C710 rev 0, 66MHz
scsibus0 at osiop0: 8 targets, initiator 7
osiop0: target 0 now using 8 bit 10 MHz 8 REQ/ACK offset xfers
sd0 at scsibus0 targ 0 lun 0: <SAMSUNG, WN34324U (gm030), 0105> SCSI2 0/direct fixed serial.SAMSUNG_WN34324U_(gm030)_
sd0: 4120MB, 512 bytes/sector, 8438976 sectors
osiop0: target 1 now using 8 bit 10 MHz 8 REQ/ACK offset xfers
sd1 at scsibus0 targ 1 lun 0: <QUANTUM, FIREBALL_TM3200S, 300X> SCSI2 0/direct fixed serial.QUANTUM_FIREBALL_TM3200S395631860290
sd1: 3067MB, 512 bytes/sector, 6281856 sectors
vme0 at pcctwo0 offset 0x40000
vme0: using BUG parameters
vme0: 1phys 0x02000000-0xefff0000 to VME 0x02000000-0xefff0000
vme0: 2phys 0xff000000-0xff7f0000 to VME 0xff000000-0xff7f0000
vme0: vme to cpu irq level 1:1
vmes0 at vme0
vmel0 at vme0
ie0 at pcctwo0 offset 0x46000 ipl 3: address 08:00:3e:21:7c:74
sram0 at mainbus0 addr 0xffe00000: 128KB
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
boot device: sd0
root on sd0a (8279d652738da9b3.a) swap on sd0b dump on sd0b