OpenBSD/mvme68k

OpenBSD/mvme68k runs on a large subset of Motorola's 680x0-based VME motherboard family.

There is currently no maintainer for the mvme68k port.

Table of contents

• History of the port
• Current status
• Project list
• Supported hardware
• Getting and installing OpenBSD/mvme68k
• Hardware details

History:

This port was primarily done by Theo de Raadt in 1995 as a contract to Willowglen Singapore. An earlier port to the MVME147 by Chuck Cranor based on Paul Mackerras' old DA30 code (and using hardware donated by Jonathan Levine at Theo's request) provided a solid development platform.

Bizzarely, Dale Rahn, working for Motorola back then, also independently wrote a port to the MVME147. For most kernel parts, both their ports were analyzed but more code was written from scratch by Theo, or based on the hp300 code.

Dale helped significantly during the porting to the 68040 models and wrote most of the code specific to the MVME167 model. Later, Steve Murphree continued work and made the MVME177 work, as well as adding support for more VME devices.

Current status:

Currently, all the boards listed in the supported hardware section below boot multi-user, and support enough of the on-board devices to be generally usable.

OpenBSD/mvme68k is able to run sun3 SunOS binaries via the COMPAT_SUNOS kernel option. Thus, the MVME177 board is probably the fastest machine capable of running SunOS m68k binaries!

As none of the mvme68k boards have graphics devices, and none of the Motorola VME frame buffers are currently supported, there are no X Window System servers available. However, a complete set of X clients and utilities is available, allowing OpenBSD/mvme68k machines to behave as X11 font servers, or run X clients on remote display.

Project list (in no particular order):

• Support MVME172.
• Support MVME135 and MVME136.
• Support MVME165.
• Work on unsupported device cards (MVME327, MVME374...)

Supported hardware:

Supported processor boards

• MVME147 (68030)
  All the on-board devices are supported, except for the parallel port.
• MVME162 (68040)
  Almost all the on-board devices are supported, with the following exceptions:
  • VME bus support is untested
  • Parity and ECC memory are not supported (but memory works just fine!)
  • Flash driver not working
  • IP module driver untested
• MVME167 (68040)
  Works as well as the MVME162, and the parallel port is not supported.
• MVME177 (68060)
  Works as well as the MVME167.

Other models may work already (MVME165, MVME166, for example).

Supported extension boards

• MVME328: SCSI controller (vs)
• MVME376: VME Lance ethernet (le)

Getting and installing OpenBSD/mvme68k:

The latest supported OpenBSD/mvme68k release is OpenBSD 4.1. Here are the OpenBSD/mvme68k 4.1 installation instructions .

Snapshots are made available from time to time, in this location as well as in a few mirrors. Here are the OpenBSD/mvme68k snapshot installation instructions as well.

Hardware details:

As VME hardware is quite uncommon in the average retail place, this section is here to satisfy the well-founded curiosity about the mvme68k hardware.

This picture is a MVME162 processor board, with the on-board ethernet and SCSI controller options, one IndustryPack module, and a memory extension.

This is a boot log of an MVME177 system.

OpenBSD 3.2-current (GENERIC) #5: Mon Dec 23 01:49:09 GMT 2002
    miod@bioue.gentiane.org:/usr/src/sys/arch/mvme68k/compile/GENERIC
Motorola  MVME177-011: 60MHz MC68060 CPU+MMU+FPU, 8k on-chip physical I/D caches
real mem = 33554432
avail mem = 27525120 (6720 pages)
using 409 buffers containing 1675264 bytes of memory
mainbus0 (root)
pcctwo0 at mainbus0 addr 0xfff00000: rev 0
clock0 at pcctwo0 ipl 5
cl0 at pcctwo0 offset 0x45000 ipl 3: console
vme0 at pcctwo0 offset 0x40000: system controller
vme0: using BUG parameters
vme0: 1phys 0x02000000-0xefff0000 to VME 0x02000000-0xefff0000
vme0: 2phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
vme0: 3phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
vme0: 4phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
vme0: vme to cpu irq level 1:1
vmes0 at vme0
vmel0 at vme0
ie0 at pcctwo0 offset 0x46000 ipl 1: address 08:00:3e:26:3f:69
ssh0 at pcctwo0 offset 0x47000 ipl 2: version 2 target 7
scsibus0 at ssh0: 8 targets
ssh0: target 0 now synchronous, period=100ns, offset=8
sd0 at scsibus0 targ 0 lun 0: <COMPAQPC, DCAS-32160, S65A> SCSI2 0/direct fixed
sd0: 2006MB, 8188 cyl, 3 head, 167 sec, 512 bytes/sec, 4110000 sec total
memc0 at pcctwo0 offset 0x43000: MEMC040 rev 1
nvram0 at pcctwo0 offset 0xc0000: MK48T08 len 8192
sram0 at mainbus0 addr 0xffe00000: len 131072
boot device: sd0
root on sd0a
rootdev=0x400 rrootdev=0x800 rawdev=0x802
Automatic boot in progress: starting file system checks.
/dev/rsd0a: file system is clean; not checking
/dev/rsd0d: file system is clean; not checking
/dev/rsd0e: file system is clean; not checking
/dev/rsd0f: file system is clean; not checking
/dev/rsd0g: file system is clean; not checking
/dev/rsd0h: file system is clean; not checking
/dev/rsd0i: file system is clean; not checking
setting tty flags
ddb.console: 0 -> 1
kern.splassert: 0 -> 2
starting network
add net default: gateway 10.0.1.101
starting system logger
starting rpc daemons: portmap ypbind rdate timed.
savecore: no core dump
checking quotas: done.
building ps databases: kvm dev.
clearing /tmp
starting pre-securelevel daemons:.
setting kernel security level: kern.securelevel: 0 -> 1
preserving editor files
creating runtime link editor directory cache.
starting network daemons: sendmail inetd sshd.
starting local daemons:.
standard daemons: cron.
Thu Dec 26 18:07:08 GMT 2002

OpenBSD/mvme68k (bioue.gentiane.org) (console)

login: