Data General Logo

AViiON Logo


AV300

AV300 Series Front
AV300 Series Internals
AV300 Series Rear

AV400 multiuser diskless

We gone and done it.
Booting inen()
Local Ethernet address is 8:0:1B:xx:xx:xx
Local Internet address is 192.168.1.155, or C0A8019B hex.
Trying server at 192.168.1.1, or C0A80101 hex for TFTP transfer.
>> OpenBSD/mvme88k netboot 1.1
device: le0 attached to 08:00:1b:xx:xx:xx
boot: client IP address: 192.168.1.155
boot: client name: AViiON.
root addr=192.168.1.1 path=/home/exports/av400/root
1908736+73728+269520+[71928+88116]=0x24ce00
[memsize: 27ffffc 27dfffc]
CPU0 is associated to 2 MC88200 CMMUs
CPU1 is associated to 2 MC88200 CMMUs
[ no symbol table formats found ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2006 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 3.9-current (GENERIC) #1: Tue May 16 22:12:56 GMT 2006
    miod@xxx.xxx:/usr/src/sys/arch/aviion/compile/GENERIC
real mem  = 41938944
avail mem = 33697792 (8227 pages)
using 537 buffers containing 2199552 bytes of memory
bootpath: 'inen()' dev 0 unit 0 part 0
mainbus0 (root): AV400 or compatible, cpuid 0x7908
cpu0: M88100 rev 0xb, 2 CMMU
cpu0: M88200 (16K) rev 0x9, full Icache, M88200 (16K) rev 0x9, full Dcache
syscon0 at mainbus0 addr 0xfff00000
nvram0 at syscon0 offset 0x80000 ipl 0: MK48T02
dart0 at syscon0 offset 0x82000 ipl 3: console
dart1 at syscon0 offset 0x82c00 ipl 3
le0 at syscon0 offset 0x8c000 ipl 1: address 08:00:1b:xx:xx:xx
le0: 32 receive buffers, 8 transmit buffers
vme0 at syscon0 offset 0x85000 ipl 0
vme0: A32 10000000-7fffffff
vme0: A32 90000000-fdffffff
vme0: A24 00000000-00ffffff
vme0: A16 00000000-0000ffff
le1 at vme0 a16 0x4000 a32 0x55900000 ipl 1: address 00:00:77:xx:xx:xx
le1: 128 receive buffers, 32 transmit buffers
boot device: le0
/dev/ksyms: Symbol table not valid.
nfs_boot: using network interface 'le0'
nfs_boot: client_addr=192.168.1.155
nfs_boot: server_addr=192.168.1.1 hostname=AViiON.
root on 192.168.1.1:/home/exports/av400/root
swap on 192.168.1.1:/home/exports/av400/swap
Automatic boot in progress: starting file system checks.
setting tty flags
ddb.console: 0 -> 1
kern.splassert: 0 -> 2
starting network
starting system logger
starting initial daemons:.
swapctl: adding 192.168.1.1:/home/exports/av400/swap as swap device at priority 0
savecore: no core dump (no dumpdev)
checking quotas: done.
building ps databases: kvmkvm_mkdb: can't open /dev/ksyms
 dev.
clearing /tmp
starting pre-securelevel daemons:.
setting kernel security level: kern.securelevel: 0 -> 1
creating runtime link editor directory cache.
preserving editor files
starting network daemons: sendmail inetd.
starting local daemons:.
standard daemons: cron.
Fri May 19 19:54:38 EDT 2006

OpenBSD/aviion (AViiON.) (console)

login: root
Password:
Last login: Fri May 19 19:49:56 on console
OpenBSD 3.9-current (GENERIC) #1: Tue May 16 22:12:56 GMT 2006

Welcome to OpenBSD: The proactively secure Unix-like operating system.

Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code.  With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.

Terminal type? [unknown] vt100
# uname -a
OpenBSD AViiON. 3.9 GENERIC#1 aviion

OpenBSD/dg88k now OpenBSD/aviion

AV400 almost multiuser!

[PROM banner at 0x27ff4c4: ]
CPU0 is associated to 2 MC88200 CMMUs
CPU1 is associated to 2 MC88200 CMMUs
[ no symbol table formats found ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org

OpenBSD 3.9-current (AV400) #65: Sun May  7 22:26:59 GMT 2006
    miod@xxx.xxx:/usr/src/sys/arch/dg88k/compile/AV400
real mem  = 41943040
avail mem = 34910208 (8523 pages)
using 537 buffers containing 2199552 bytes of memory
[Boot device information: args 0x27ff37c (inen()) dev 0 unit 0 part 0]
mainbus0 (root): , cpuid 0x7908
cpu0: M88100 rev 0xb, 2 CMMU
cpu0: M88200 (16K) rev 0x9, full Icache, M88200 (16K) rev 0x9, full Dcache
syscon0 at mainbus0 addr 0xfff00000
nvram0 at syscon0 offset 0x80000 ipl 0: MK48T02
dart0 at syscon0 offset 0x82000 ipl 3: console
le0 at syscon0 offset 0x8c000 ipl 1: address 08:00:1b:xx:xx:xx
le0: 32 receive buffers, 8 transmit buffers
vme0 at syscon0 offset 0x85000 ipl 0
vme0: A32 10000000-7fffffff
vme0: A32 90000000-fdffffff
vme0: A24 fe000000-feffffff
vme0: A16 ffff0000-ffffffff
boot device: unknown
root device :

HAWK VME jumper settings

This is supposed to mean:

NOVRAM replaced and apparently working

I ordered an M48T02-200PC1 from DigiKey and it appears to do the trick. We'll see if it keeps time and system settings soon.

More on NVRAM battery

OK, this is new to me. Apparently you only see the NVBATLOW warning if you use a serial console. It flashes before the graphics console is initialized, and it gets overwritten by the scm testing screen. So you only get a few seconds to see it's there before it disappears. That's pretty silly.

Update

Apparently the NOVRAM completely erased itself from being dead so long, or removing the frame buffer fixed the glitch because my system is booting DG/UX multiuser again.

More cleanup

I've broken out the scans of the manuals into a separate page to make this one a little less unweildy.

Dead NOVRAM :(

Well it seems that the NOVRAM/NVRAM on my AV410 has finally died. Rendering my system unbootable.
If you see the error:

Initializing [XX Megabytes]
WARNING: 10000201, Type any key to continue.

Or the operating system tells you:

Creating /dev ....
From JP 1: No driver registered to support System Console.
The operating system has detected a serious error and halted.
"DG/UX R4.11MU03 halt code 30000002"

then your NOVRAM battery is likely dead or corrupt. Luckily I have a backup of it from before it died posted here, so hopefully I can restore it once I get ahold of an M48T02.

The full part number from the board is MK48T02B-25

More information on this:

History of DG/UX

  1. DG/UX Release 5.4 - June, 1991
  2. DG/UX Release 5.4.1 - February, 1992
  3. DG/UX Release 5.4.2 - August, 1992
  4. DG/UX 5.4 Release 2.01 - March, 1993
  5. DG/UX 5.4 Release 2.10 - July, 1993
  6. DG/UX 5.4 Release 3.00 - January, 1994
  7. DG/UX 5.4 Release 3.10 - July, 1994
  8. DG/UX 5.4 Release 4.00 & DSO Release 4.00 - January, 1995
  9. DG/UX Release 4.10 & DSO Release 4.10 - August, 1995
  10. DG/UX Release 4.11 - December, 1995
  11. ...
  12. DG/UX Release 4.11MU06 - June, 1999

Data from unpublished DG manual 093-701087-09 Installing the DG/UX System
NOTE: This list is incomplete.

Pictures of my AV410

Other stuff

I should take this opportunity to say, that doing what I am doing in the above picture, running the system - AV Diagnostics system excerciser no less - without the covers on is not thermally a good idea for this or any AViiON system. While the small AViiON's don't make a whole lot of heat, you definitely risk baking your disks, any VME devices and/or the power supply. By the way, even my small AV410 tower has a 300 watt power supply. Make sure your fans are all working as there is no air speed or rotation detection on the AVxxx or 4xxx models. I ended up replacing the metal fans with a slightly lower airflow but much quieter 120 mm Panaflows.

Typical SCSI IDs

Note about the AViiON SCM and drive motor control

It appears that the SCM cannot and does not send start motor commands to a device you are trying to boot. So if you have the ME jumper set on a seagate drive, your drive will not spin and will not be bootable! Your best bet is to set the DS jumper (Seagate) so that the drive spins up a few seconds after power comes on.

The operating system does send start unit, so if you boot from another drive or off the network, the kernel will spin the disk up. This is somewhat odd behavior but what can I say. Machines that netboot typically have a smallish disk for local swap with motor control enabled so that they won't spin until the operating system requests them.

Device names

General booting syntax

The scm syntax is something like this:
boot sd(insc(),0)root:/dgux.AV410 -3

Network booting

At least on the AV400, it uses RARP and TFTP to load the initial kernel. bootpd/bootparams/RPC-something is probably needed later on for DG/UX to mount it's root file system.

To boot over the network you just use boot inen(). The extended syntax for booting from disk will not work.