Motorola M810 fun – pt 2
#### warning: this is going to be a semi-long post ####
first off, some drive specs:
187-Bug>IOI I/O Inquiry Status: CLUN DLUN CNTRL-TYPE DADDR DTYPE RM Inquiry-Data 0 10 VME187 1 $00 N SEAGATE ST39173N 6244 0 40 VME187 4 $01 Y ARCHIVE VIPER TDC 3800 =07: 0 50 VME187 5 $01 Y ARCHIVE Python 28388-XXX 5.AC
first bunch of problems:
while trying to use bug’s menu option i ran into this little winner:
187-Bug>MENU 1) Continue System Start Up 2) Select Alternate Boot Device 3) Go to System Debugger 4) Initiate Service Call 5) Display System Test Errors 6) Dump Memory to Tape Enter Menu #: 2 Alternate Boot Device (Controller,Drive,File): 0,0, Change it (Y/N)? N Continue System Start Up (Y/N)? N 1) Continue System Start Up 2) Select Alternate Boot Device 3) Go to System Debugger 4) Initiate Service Call 5) Display System Test Errors 6) Dump Memory to Tape Enter Menu #: 1 RAM PATS: Patterns.............................. Running ---> PASSED --Overrun Error--
now you have to take into consideration that it was running a bunch of tests and that this is a 33Mhz machine, so from entering the menu number to error point it takes roughly 7-10 minutes. not to bad though.
so i figured at this point that maybe the physical drive was just not mapped out so i decided to autoboot it with mappings to
clun 00 dlun 10 (phys drive):
187-Bug>MENU 1) Continue System Start Up 2) Select Alternate Boot Device 3) Go to System Debugger 4) Initiate Service Call 5) Display System Test Errors 6) Dump Memory to Tape Enter Menu #: 1 NCR IRQ: NCR 53C710 Interrupts.................. Running ---> PASSED Testing Complete Autoboot in progress... To abort hit <BREAK> Boot Logic Error Packet Status: 0300 Autoboot Failed
so at this point i went in to
ENV to change the
Auto Boot Controller LUN to 00 and to also change
Auto Boot Device LUN to 10.
Copyright Motorola Inc. 1988 - 1994, All Rights Reserved MVME187 Debugger/Diagnostics Release Version 2.2 - 01/14/94 COLD Start Local Memory Found =02000000 (&33554432) MPU Clock Speed =33Mhz Autoboot in progress... To abort hit <BREAK> Booting from: VME187, Controller 0, Drive 10 Loading: Operating System Volume: $00000000 IPL loaded at: $00FC0000 SVR4 Disk Boot Loader 940112 Boot: No V_ROOT tagged slice on device.
damn.. after some field stripping and investigating, i realized that the disk that was on this machine did not contain the operating system. hmm….. openbsd time!!!
so we now set this puppy up for netbooting making sure that we have a tftp server somewhere on the network:
187-Bug>NIOT Controller LUN =00? Device LUN =00? Node Control Memory Address =FFE10000? Client IP Address =0.0.0.0? 192.168.100.4 Server IP Address =0.0.0.0? 192.168.100.5 Subnet IP Address Mask =255.255.255.0? Broadcast IP Address =255.255.255.255? Gateway IP Address =0.0.0.0? Boot File Name ("NULL" for None) =? INSTALL.tftpboot Argument File Name ("NULL" for None) =? bsd.rd Boot File Load Address =001F0000? 00AF0000 Boot File Execution Address =001F0000? 00AF0000 Boot File Execution Delay =00000000? Boot File Length =00000000? Boot File Byte Offset =00000000? BOOTP/RARP Request Retry =00? TFTP/ARP Request Retry =00? Trace Character Buffer Address =00000000? BOOTP/RARP Request Control: Always/When-Needed (A/W)=W? BOOTP/RARP Reply Update Control: Yes/No (Y/N) =Y? Update Non-Volatile RAM (Y/N)? Y ERROR: Invalid Network Auto Boot Configuration Parameters Pointer (NVRAM) 187-Bug>NIOT;H Network Controllers/Nodes Available CLUN DLUN Name Address P-Address/H-Address 0 0 VME187 $FFF46000 192.168.100.4/08003E22C637
so now let us netboot this bad boy by issuing a
187-Bug>NBO 00 00 Network Booting from: VME187, Controller 0, Device 0 Loading: INSTALL.tftpboot Client IP Address = 192.168.100.4 Server IP Address = 192.168.100.5 Gateway IP Address = 0.0.0.0 Subnet IP Address Mask = 255.255.255.0 Boot File Name = INSTALL.tftpboot Argument File Name = bsd.rd Network Boot File load in progress... To abort hit <BREAK> Bytes Received =&24912, Bytes Loaded =&24912 Bytes/Second =&24912, Elapsed Time =1 Second(s) >> OpenBSD/mvme88k tftpboot [1.2]
now we just go about installing openbsd as usual.
more updates to come..
Leave a Reply