Moto-Too Build ----------------- Latest Rev. 28-Dec-2017 Moto-Too is an Ultra 5/10 (10) machine SN# 10501448. Moto-Too was un-dumpstered (obtained) in December 2006. It was manufactured in mid 1998. It is an Ultra SPARK IIi machine 333 MHz Open Boot 3.11 512 MB main memory Moto-Too has hostid: 80a03d48 as found Ethernet Hardware Address: 8:0:20:a0:3d:48 as found Philippe Disk 40 GB disk named Moto_Too_1 WD-400-BB Slice % Full Slice Cylinders Size Mount Function @ Build ----- ----------- ----- ----- -------- ------- 0 0-3854 7.50 / unix 1 3855-4369 1.00 swap - 2 0-19155 37.27 - 3 4370-6689 4.51 /home Xilinx 4 6690-13119 12.51 /home2 designs 5 13120-14769 3.21 /home3 Backup 6 14770-19155 8.53 /home4 Mentor The unix from the original Moto #2 disk looks like it was last patched or worked on 4-Sept-2009. Things that could/should be fixed: /etc/inet/inetd.conf is not current for Moto /etc/dt/config/Xservers removed the two -dev arguments that were needed for the 2 screens on the real Moto # on Moto_Too > fbconfig -list shows /dev/fbs/m640 > fbconfig -dev /dev/fbs/m640 -prconf shows 1280 x 1024 x 8 operation .login if for a given user this specifies operation with 2 monitors then it needs to be edited /etc/vfstab edit this so that all /home : /home4 mounts will come from c0t0d0s3 : c0t0d0s6 # remove all of /opt/staroffice7 and /optsuite7 # this save 3.5 GB in the slice 0 > cd /home5/opt > rm -r ./staroffice7 > rm -r ./starsuite7 # this gets the 4-Sept09 version of unix from Moto # down to about ?? GB I can not get the 40 GB disk from Philippe to boot under any condition when it has my cooked up unix from the real moto on slice 0. With this cooked unix from moto it crashes in various random ways during boot. I can get it to boot and run just fine with a build of unix from the CD-ROM but only if I have a second disk on the ATA cable with it. By itself it crashed during boot in various random ways. Tar over from the real moto #2 disk the following contents_bsxe.tar 6,272,321,024 contents_msdata.tar 8,315,392 contents_ustation.tar 56,956,928 contents_xilinx_52.tar 1,599,652,352 contents_xilinx_63.tar 1,910,325,760 Build these tars in slice 4 on the target disk and then restore them into their proper slices / directories on the target disk. All of this stuff comes from the real moto disk #2. Tom Disk 80 GB disk named Moto_Too_2 WD-800-JB Slice Cylinders Size Mount Function ----- ----------- ---- ----- -------- 0 0-3855 7.50 / unix 1 3856-4370 1.00 swap 2 0-38306 74.53 3 4371-6941 5.00 /home Xilinx 4 6942-14652 15.00 /home2 designs 5 14653-33157 36.00 /home3 Backup 6 33158-38306 10.02 /home4 Mentor 13-Jan-2012 Disk Status Moto_Too_0 s0 unix from CD-ROM with xemacs and acroread s4 unix cooked from the real Moto Moto_Too_1 s0 / unix from CD-ROM with xemacs and acroread s3 /home1 Xilinx 52, Xilinx 63, ustation s4 /home2 designs and edmunds s5 /home3 backup space s6 /home4 Mentor BSXE 7.5 Note/Recall that in slice 4 in a directory called "new designs" there is a Patch Cluster from September 2009. Tom Disk 120 GB disk named Moto_Too_3 WD-?? This disk was formatted: 7.5, 1.0, 111.79, 5.0, 15.0, 36.0, 10.0, 37.28 and I tried to nfsdump into its slice #4. This went well until it was almost complete and then it failed with errors of the type: pci@1f,0 /pci@1,1 /ide@3 /dad@1,0 (dad1) transport rejected (-2). Label the Moto_Too_3 disk as not working and give up on trying to use it. Install the Patch Cluster in the unix on disk Moto_Too_1 using the normal ./install_Cluster Before the install c0t0d0s0 had 2,079,633 used and after the patch cluster install 2,463,953 used. Setup user accounts with the normal: groupadd -g 151 d0users useradd -u 101 -g 151 -d /home2/edmunds -s /usr/bin/tcsh edmunds passwd username cr and let it prompt you. Disk 40 GB disk named Moto_Too_4 WD-400-BB Slice Slice Cylinders Size Mount Function ----- ----------- ----- ----- -------- 0 0-3854 7.50 / unix 1 3855-4369 1.00 swap 2 0-19145 37.25 3 4370-6689 4.51 /home Xilinx 4 6690-13119 12.51 /home2 designs 5 13120-14769 3.21 /home3 Backup 6 14770-19145 8.51 /home4 Mentor The build of disk Moto_Too_4 appeared to go OK and it has all contemporary ready to use patched unix and design stuff on it. Disk Moto_Too_4 was built using ufsdump copies from disk Moto_Too_1. Tom Disk 80 GB disk named Moto_Too_5 Maxtor 98196H8 Slice Slice Cylinders Size Mount Function ----- ----------- ----- ----- -------- 0 0-5140 10.50 / unix 1 5141-5655 1.00 swap 2 0-39233 76.33 3 5656-10796 10.00 /home Xilinx 4 10797-18507 15.00 /home2 designs 5 18508-33928 30.00 /home3 Backup 6 33929-39233 10.32 /home4 Mentor Disk 7.87 GB Moto_Too_6 IBM DHEA-3851 Slice Slice Cylinders Size Mount Function ----- ----------- ----- ----- -------- 0 0-9362 4.50 / unix 1 9363-11443 1.00 swap 2 0-16380 7.87 5 11444-16380 2.37 /home3 Backup On Moto-Too, before touching the NVRAM chip, at the OK prompt do a '.idprom' Format/Type: 1 80 Ethernet: 8 0 20 a0 3d 48 Date: 0 0 0 0 Serial: a0 3d 48 Checksum: a9 On Moto-Too, before touching the NVRAM chip, at the OK prompt do a 'printenv'. tpe-link-test? true scsi-indicator-id 7 keyboard-click? false keymap -blank- ttyb-rts-dtr-off false ttyb-ignore-cd true ttya-rts-dtr-off false ttya-ignore-cd true ttyb-mode 9600,8,n,1,- ttya-mode 9600,8,n,1,- pcia-probe-list 1,2,3,4 pcib-probe-list 1,2,3 mfg-mode off diag-level max #power-cycles 105 system-board-serial# -blank- system-board-date -blank- fcode-debug? false output-device screen input-device keyboard load-base 16384 boot-command boot auto-boot? true watchdo-reboot? false diag-file -blank- diag-device net boot-file -blank- boot-device disk:a disk:b net local-mac-address? false ansi-terminal? true screen-#columns 80 screen-#rows 34 silent-mode? false use-nvramrc? false security-mode none security-password -blank- security-#badlogins 0 oem-logo -blank- oem-logo? false oem-banner -blank- oem-banner? false hardware-revision -blank- last-hardware-update -blank- diag-switch? false Since the initial CD-ROM build it has been clear that Moto-Too did not really have the correct network setup. This was OK because it was not on the network - but I went ahead and fixed it up using the real Moto and Becane-Too as examples. I mostly just brought over the appropriate files from the real moto to fix things up. /etc/defaultdomain 1 line "pa.msu.edu" did not exist - bring it over /etc/defaultrouter 1 line "35.8.2.3" was OK /etc/hostname.hme0 1 line "moto" was OK /etc/nodename 1 line "moto" was OK /etc/resolv.conf 4 lines "domain pa.msu.edu" bring it over "nameserver 35.8.2.41" "nameserver 35.8.2.42" "nameserver 35.9.68.12" /etc/inet/hosts 2 lines "127.0.0.1 localhost" "35.9.71.13 moto.pa.msu.edu moto loghost" bring it over /etc/inet/netmasks 1 line "35.0.0.0 255.248.0.0" bring it over I also brought over from the real moto the file /etc/inet/inetd.conf i.e. the version that has everything turned off except what is actually needed to run the system. These things have been fixed only on disks moto-too-1 and moto-too-6. The monitor standards are from VESA Video Electronics Standards Association. The old conventional communications part about resolution and such is called EDID Extended Display Identification Data. Moto-Too has been running on disks moto-too-1 and moto-too-6. Moto-Too-1 supplies everything except for the /home3 backup. On 5-Feb-12 brought over to just disk moto-too-1 the complete current contents of /home2/designs/Drawings/ from the real moto. =================================================================== Changes to get Everything to Work as of 12-Feb-12 ----------------------------------- Set the 4 network files as described above. Slice #3 is now mounted as /home1 (instead of as /home). Thus I had to edit: /home1/Xilinx/Xilinx_52i/settings.csh to use /home1 /home1/Xilinx/Xilinx_63i/settings.csh to use /home1 /home1/ustation/ustation to use /home1 /home2/ /.cshrc a couple of refs to /home to /home1 May need to set the X Window resolution to fit the monitor: > fbconfig -prconfig # To see what is running and what is possible. > fbconfig -dev /dev/fbs/m640 -res 1280x1024x60 # Restart X to have this take effect. # This changes the file: /etc/openwin/server/etc/OWconfig May need fonts e.g.: xset fp+ /home2/Mentor_1999_Fonts/ For some reason the mgc_location_map file is pointing to 2006BSXE. Fix this at /home4/MentorGraphics/2007.5BSXE/MGC_HOME.ss5/etc/ mgc_location_map. This was done only on disk Moto_Too_1. =================================================================== Moto-Too Disk Collection Notes as of 23-Jan-2012 -------------------------------- Moto_Too_0 s0 has unix - non patched from cdrom 8 GB s7 has cooked unix from the real moto Moto_Too_1 s0 has good patched unix from cdrom 40 GB s3,s4,s5,s6 current 16-Jan-12 Moto_Too_2 s0 has good patched unix from cdrom 80 GB s3,s4,s5,s6 current 16-Jan-12 Moto_Too_3 "transport rejected" errors in s4 120 GB give up trying to use this disk for now Moto_Too_4 s0 has good patched unix from cdrom 40 GB s3,s4,s5,s6 current 16-Jan-12 Moto_Too_5 s0 has good patched unix from cdrom 80 GB s3,s4,s5,s6 current 16-Jan-12 Moto_Too_6 s0 has good patched unix from cdrom 8 GB NOTE: The design files were obtained from the real moto disk #2 which was the "user" disk on the real moto until 16-Nov-2010. =================================================================== Moto-Too NVRAM-Clock ---------------------- The bar-code sticker from Moto-Too's original NVRAM says, "A03D48". Recall that Moto-Too's original hostid: 80a03d48 This kind of implies that the "80" part is stored someplace else or else it is hardwired. The part type of Moto-Too's original NVRAM is: ST Micro M48T59Y-70PC1. It's probably from 9828. The pinout of the M48T59Y matches a MK48Z08 On the real Moto: > prtconf gives: Sun 4u architecture > prtconf -vp | grep idprom gives: idprom: 01830003.bacdce6a.05050711.cdce6a2d.ffffffff.ffffffff.ffffffff.ffffffff device_type: 'idprom' name: 'idprom' On Moto-Too-Too with its original NVRAM chip: > prtconf -vp | grep idprom gives: idprom: 01800800.20b08190.00000000.b08190a9.00000000.00000000.00000000.00000000 On Moto-Too write the nvram as follows: OK 1 0 mkp OK 83 1 mkp OK 8 2 mkp OK 0 3 mkp OK 20 4 mkp OK h# cd 5 mkp OK ce 6 mkp OK 6a 7 mkp OK 0 8 mkp OK 0 9 mkp OK 0 a mkp OK 0 b mkp OK h# cd c mkp OK ce d mkp OK 6a e mkp OK 0 f 0 do i idprom@ xor loop f mkp Note that the "h#" appears to be needed in front of the value "cd" only in order to force Open Boot to see the value "cd" as a hex number and not as a keyword. After this nvram work on Moto-Too, at the OK prompt do a '.idprom' Format/Type: 1 83 Ethernet: 8 0 20 cd ce 6a Date: 0 0 0 0 Serial: cd ce 6a Checksum: aa =================================================================== Moto_Too in 2150 Moto dies and Moto_Too comes to 2150 on about 25-Sept-2012 - Boot and set pw's - allow ssh forwarding of X pg 64, 65 of main book - install /opt/sfw/lib/firefox/ Moto running again, return Moto_Too to 231 11-Oct-2012 - While Moto_Too in 1200C copy its nvram 214 is set for $01020000 $01027fff 1st chip set first bank $01028000 $0102ffff 2nd chip set first bank bug> bm 01020000 01027fff 01028000 This appears to get everything but the clock stuff. Make 2 copies. Moto-Too-Too does boot from this NVRAM. =================================================================== Moto-Too-Too Notes --------------------- Sun Ultra 5 Date Built about 9915 384 MByte main memory 333 MHz UltraSpark IIi eithernet 8:0:20:b0:81:90 HostID 80b08190 hostname rrn booted sunos 5.7 1 disk Seagate ST39140A Medalist Pro 9140 9GB EIDE OpenBoot 3.15 Sun 4u architecture Moto-Too-Too work on 20-Oct-2012 - Pulled out disk Moto_Too_0 and Installed disk Moto_Too_4. Disk Moto_Too_0 is now in the 2150 spare storage box along with disks Moto_Too_2 and Moto_Too_5. For disk Moto_Too_4 to work it appeared to need a real 25 mil pitch cable, pin #20 cut on Moto-Too-Too's MB, and the drive set for Cable Select. - Moto-Too-Too has a double A powered rebuilt NVRAM. - Moto-Too-Too does boot OK, its date and clock apprear to be OK, it does not have the final edits mentioned above that are required for the: net, screen resolution, and lm server to work. It does not have a USB card. Moto-Too-Too work on early-Nov-2014 - In early Nov 2014 Moto_Too_Too was tried with the SUN dual cable LCD display from Chemistry. It fired up and worked OK. The scrap USB card found in Chemistry was tried but did not appear to be visible to the operating system. =================================================================== PATA Notes ------------ 80 wire cables started with Ultra-33 Cable Connectors: Blue Host Gray Slave middle Black Master Note that the terms Master and Slave are not in the ATA specification. The correct terms are Device 0 and Device 1. Pin #20 is the mechanical key. Blue Host Connector: The socket contact for header pin #34 is connected to Gnd inside the connector body but it is not attached to any wire in the cable. This grounded pin #34 tells the host that it has an 80 conductor cable and that a cable is plugged in. Gray Connector Device 1 (Slave): There is no connection at all to socket contact #28 (Cable_Select) in this connector. All 80 wire cable connectors have pin #20 blocked. There is no pin #20 in the header (but a few wackos use Vcc on pin #20). Wire #28 is not attached to anything in the middle Slave connector. Wire #28 does run from pin #28 in the Controller (aka Host) to pin #28 in the Master i.e. and end-to-end connection. Socket contact #34 in the Controller is grounded. There is no connection to wire #34 in the Controller connector. Wire #34 does run from socket contact #34 in the Master to socket contact #34 in the Slave. The Cable Select connector contact, i.e. #28, in the Master connector is grounded by its connection in the Host connector. The Cable Select connector contact, i.e. #28, in the Slave connector is floating. In this way the Cable Select signal is not an "Address Line" rather it is a "Geographic Address" signal. In the 80 wire cables the 40 additional wires are just grounded, i.e. there are ground lines between all possible signal lines. =================================================================== 28-Nov-2014 Work at Durand St on Moto_Too tryings Disks 7, 8, and 9. Note that the PCI USB card from Moto and now in Moto_Too is a Sun model 375-3140-05. I believe that the -05 may be the revision number and that the basic Sun model is 375-3140. The 375-3140 USB card has as its basic parts: TI type PCI 2250 PCI to PCI bridge TI type TSB43AB21 PCI to 1394 Firewire controller NEC type D72010 PCI to USB-2 controller The 375-3140 card appears to be from 2003 and made by the company, Smart Modular Technologies A Selectron Company. It has 5 USB ports and 3 Firewire parts. =================================================================== 29 and 30 November 2014 Currently in Rm 2150 there are Moto-Too backup disks 0, 2, and 5. Moto-Too disk 4 is currently in the machine Moto_Too_Too. Up until now there are been 6 Moto_Too disks which are summarized in an entry in this file from 23-Jan-2012. Working at Durand St I now have 3 more disks to try building. I will try building these disks using Moto_Too's running disk (i.e. Moto_Too_1) as the source for all: Unix, Xilinx, home2, and Mentor. These 3 "new" disks to try building are: Moto-Too_7 40 GB Maxtor DiamondMax Plus 8 from Sept 2005. Operated as Slave with CS Jumper installed. Total disk cylinders available: 19677 + 2 (reserved cylinders) Slice Flag Cylinders Size Mount Function ----- ---- ------------- ----- ------ -------- 0 wm 0 - 3854 7.50 / unix 1 wu 3855 - 4369 1.00 swap 2 wu 0 - 19676 38.28 3 wm 4370 - 6689 4.51 /home Xilinx 4 wm 6690 - 13119 12.51 /home2 designs 5 wm 13120 - 15179 4.01 /home3 Backup 6 wm 15180 - 19676 8.75 /home4 Mentor Moto-Too_8 80 GB Western Digital WD800 from Sept 2004. Operated as Slave with a Jumper to force Slave. Slice Cylinders Size Mount Function ----- ----------- ---- ------ -------- 0 0- 3855 7.50 / unix 1 3856- 4370 1.00 swap 2 0-38306 74.53 3 4371- 6941 5.00 /home Xilinx 4 6942-14652 15.00 /home2 designs 5 14653-33157 36.00 /home3 Backup 6 33158-38306 10.02 /home4 Mentor Moto-Too_9 80 GB Maxtor DiamondMax 80 98196H8 from Dec 2000. Operated as Slave with no Jumpers installed. The moto_too_9 disk made a lot of banging noise during the initial newfs of slice 4 or 5. The whole partition, newfs, fsck process was started over and ran without banging noise. After the ufsdump copies all slices were fsck'd again and appear to be OK. Still this is an very old disk. Slice Cylinders Size Mount Function ----- ----------- ---- ------ -------- 0 0- 4109 8.00 / unix 1 4110- 4624 1.00 swap 2 0-39233 76.33 3 4625- 8734 8.00 /home Xilinx 4 8735-19014 20.00 /home2 designs 5 19015-31864 25.00 /home3 Backup 6 31865-39233 14.34 /home4 Mentor Recall the basic setup for building Moto_Too disks: - Pull out the Slave which is currently Moto_Too_6. - Install the disk to be built as the Slave and worry about how to set its jumpers. - Recall that the Slave disk on Moto_Too is: c0t1d0s - Use the format program to format the disk to be built. Format will start out by searching for disks, e.g. c0t1d0 /pci@1f,0/pci@1,1/ide@3/dad@1,0 Then use the "partition" to setup the partition table. Use "partition" commands: 0:7, print, and label. Use "verify" to read the partition table from the disk. - Now put a file system on the slices that will have directory structures: > newfs /dev/rdsk/c0t1d0s0 > newfs /dev/rdsk/c0t1d0s3 > newfs /dev/rdsk/c0t1d0s4 > newfs /dev/rdsk/c0t1d0s5 > newfs /dev/rdsk/c0t1d0s6 - Now check the file system structure before going forward: > fsck /dev/rdsk/c0t1d0s0 > fsck /dev/rdsk/c0t1d0s3 > fsck /dev/rdsk/c0t1d0s4 > fsck /dev/rdsk/c0t1d0s5 > fsck /dev/rdsk/c0t1d0s6 - Now drop down to single user mode > init s - Now mount the slice that is to be written to at /home5, e.g. 3 > mount /dev/dsk/c0t1d0s3 /home5 - Now copy the files using ufsdump example for slice 3 > ufsdump 0f - /dev/rdsk/c0t1d0s3 | (cd /home5; ufsrestore xf -) at the end this will require answering "yes" twice. - Now unmount /home5 - Now loop over the above: mount, ufsdump, unmount through all of the slices that you need to copy which is typically: 0, 3, 4, 5, 6 - Now install the boot block on the Slave disk that you are building: > installboot /usr/platform/SUNW,Ultra-5_10/lib/fs/ufs/bootblk /dev/rdsk/c0t1d0s0 - Now edit as required the filename "label" in the slave disk root / directory which gives a "name" to this Moto_Too disk. - Note: once the slice 0 is copied to the disk that you are building in the single user mode then you may startup the full system (init 3), umount all of the slices that you need to copy, and have editable command line and up-arrow to make stepping through the various operation easier. All 3 of these Moto_Too disks 7,8,9 appear to have built OK. The running Moto_Too disk Moto_Too_1 was the source for all copies. There is now a script file in / that does most of this work except for the slice 0 copy. This is /my_45x_newfs_fsck_copy.sh =================================================================== 1 and 2 December 2014 Using the procedure and the /my_45x_newfs_fsck_copy.sh script described above re-build disks Moto_Too_2 and Moto_Too_4. This leaves only Moto-Too_0 and Moto_Too_5 that were not re-built during Nov Dec 2014. Moto_Too_2 is just one of the spare disks that is stored in room 2150. Moto_Too_4 is the disk that runs the machine Moto_Too_Too. Atfer re-build this disk had the proper /etc/vfstab file restored to it and it had a /reconfigure file put on it. Moto_Too_6 is the "backup" disk in the machine Moto_Too. It has just slices 0 and 5 on it, i.e. just unix and the backup directory. Re-build just slice 0 on it to give it a current copy of the operating system. As above, the running disk in the Moto_Too machine, i.e. disk Moto_Too_1, was the source for all copies to build these disks. Moto-Too Disk Collection Summary as of 2-Dec-2014 ---------------------------------- Moto_Too_0 s0 has unix - non patched from cdrom 8 GB s7 has cooked unix from the real moto Spare disk in Rm 2150. Moto_Too_1 s0 has good patched unix from cdrom 40 GB s3,s4,s5,s6 all current by definition. Running disk in machine Moto_Too. Moto_Too_2 All 5 sectors: s0, s3, s4, s5, s6 re-built in 80 GB Dec 2014 using disk Moto_Too_1 as the source. Spare disk in Rm 2150. Moto_Too_3 "transport rejected" errors in s4 120 GB give up trying to use this disk for now Moto_Too_4 All 5 sectors: s0, s3, s4, s5, s6 re-built in 40 GB Dec 2014 using disk Moto_Too_1 as the source. Running disk in machine Moto_Too_Too. Moto_Too_5 s0 has good patched unix from cdrom 80 GB s3,s4,s5,s6 current 16-Jan-12 Spare disk in Rm 2150. Moto_Too_6 sector s0 re-built on Dec 2014 8 GB using disk Moto_Too_1 as the source. Backup disk in machine Moto_Too. Moto_Too_7 All 5 sectors: s0, s3, s4, s5, s6 built in 40 GB Nov 2014 using disk Moto_Too_1 as the source. Spare disk in Rm 1200C. Moto_Too_8 All 5 sectors: s0, s3, s4, s5, s6 built in 80 GB Nov 2014 using disk Moto_Too_1 as the source. Spare disk in Rm 1200C. Moto_Too_9 All 5 sectors: s0, s3, s4, s5, s6 built in 80 GB Nov 2014 using disk Moto_Too_1 as the source. Spare disk in Rm 1200C. Also today I checked the backup batteries for the ID PROMs: Moto-Too 3.229 V Moto_Too_Too 3.100 V. =================================================================== 3-Dec-2014 For use in Rm 2150 I want to start up as little as possible in the inetd file and I want to make certain that sendmail is not running. So on both Moto_Too and on Moto_Too_Too do the following: - Install the minimum /etc/inet/inetd.conf file that comes from Moto. This is the 3-Jan_2012 version of Moto's /etc/inet/inetd.conf file. - Stop sendmail by making the following rename: /etc/rc2.d/S88_sendmail to /etc/rc2.d/not_S88sendmail =================================================================== 28-Dec-2017 moto_too moto_too_too log file desmo MGLM Last night I tried to start moto_too at Durand and it failed to boot. Still not clear what is wrong. It kind of looks like an IDPROM aka NVRAM problem but its backup battery checks OK with above 3 Volts. I guess it could be disk or power supply. Today I tried to boot moto_too_too and it started up OK. It looks like 18-May-2015 was the last time that it was used. It has early Hub design from the May 2015 era on it and a tar backup from that era. I checked the backup battery and it is 3.062 Volts but says use before 2016 so I should replace it soon. I'm editing the moto_too_build_log.txt on the real_moto to add the current work to this file. This file is from 3-Dec-2014 26,235 size and matches the file size on force www/scratch/ so I think that it is the correct final version. Today I tried to boot desmo and it failed to boot. It says: Incorrect Configuration CheckSum, Setting NVRAM Parameters to Default, Setting Diag Switch ? NVRAM Parameter to True, bla bla, IDPROM Contents are Invalid, Power ON Self Test Failed Cause NVRAM U13. It shows: Serial # 15707131 Enet Adrs df ff bf ef fe af Host ID fbefabfb. I did the procedure above "Moto-Too NVRAM-Clock" to put a little bit of rational ID stuff into the NVRAM and then at the OK prompt did a "boot disk" and the machine came up but it's clear that there is still a lot of bad incorrect stuff in the NVRAM. The last use of desmo appears to be at the end of October 2014 working on CMX. For becane, becane_too, real_moto I do not have backups for any of these NVRAMs and they are now all old enough for this to be a problem. In Rm 1200C there are disks 7, 8, 9 and one blank NVRAM (I assume it's blank, i.e. does not have an external battery). In 2150 I see disks 0,2,5 and maybe 6 more disks that may be good and thus could be built. Recall that the Flex License Server was updated in January 2016 so that all of my backup disks are out of date in this respect. ===================================================================