Post by Joerg BehrensPost by f***@gmail.comwe are getting close...both of my MSC displays say P0M2...and Btw...is
Now change the ID from the lower module :)
Post by f***@gmail.comthere some dip switches underneath the MSC cover...I found a POD
reference manual on the XS international website that talks about
diagnostic dip switches...plus from the link you gave me...does the
Origin 2000 also have a Master/Slave switch somewhere...??
No.
regards
Joerg
--
TakeNet GmbH, Geschaeftsfuehrer Wolfgang Meier
97080 Wuerzburg Tel: +49 931 903-2243
Alfred-Nobel-Straße 20 Fax: +49 931 903-3025
HRB Wuerzburg 6940 http://www.takenet.de
you know i forgot to tell you that i haven't been able to get a POD
prompt, any more, i seem to get a lot of boot messages coming out of
the alternate console port on the bottom back of the o2000, but no
input prompt for the POD...even after i do a NMI from the MSC
panel.....i'm not sure how i lost the prompt...it was there with the
initial "promlog" messages i first got.....here is a summary of how i
got into this mess...
My problem was that I needed to get a good CDROM on the bottom module
that had the system disk...dks0d1...
so I swapped the MSC w/Good CDROM from the TOP(module 2) to the
BOTTOM(module 1)....
But the Rack didn't come up...I didn't even get the console
output....the thing was working fine...I just wanted to use the good
CDROM from module2, but I couldn't figure a way to see the SCSI at the
top...I tried the alternate console (both consoles are from the MMSC
in the back of the rack)...but nothing showed on the VT100
terminal...so my contract customer said swap them...
Well, after this didn't work...I tried just removing the CDROM from
the MSC, and putting the original MSCs back where they were...TOP-MSC/
w Bad CDROM...BOTTOM -MSC/w Good CDROM.
The bottom module(1) is configured as the system disk location, of
course, SCSI-0, and the top module (2) is SCSI-12, etc..or that
doesn't matter, just more info for you...Now, with the MSCs in their
original locations, I get stuff on the console connection that says
"promlog: FLASH can not program a 0 to a 1" several of these from
copying FLASH Prom to memory..?? and then after some more memory
inits...I get an ALERT about the "boards in a module don't have the
same moduleids...globally change the moduleids from the MSC"...now it
goes into the Power On Diagnostic mode with the "POD>" prompt.....
At the POD I type "?" and get the list of commands, and notice the
"why" command...typing that gets a message about a Reset switch or
button being activated, and yes I did use a paper clip to push the
Reset button when my first swap as above got nothing on the console
terminal...now, I, of course have been powering down, and I would
figure that doing that puts everything back in some non-reset
state...???!!!
Well, at this point I decide to reconnect the CDROMs back as
original...TOP-MSC w/GoodCDROM and BOTTOM-MSC w/BadCDROM...and I get
the same messages..."promlog....ALERT...POD>"...Now, I try the
"module" command, and I some how end up changing the bottom module to
number 2...now I got both the top and bottom modules assigned as
2...the MMSC-Display confirms that with 2 module selections, both with
the number 2...
thanks again,
ken
8-(