At 2:42 PM -0400 23/5/14, Cory Smelosky wrote:
Is it possible to have SYSGEN do an autoconfigure again?
If you run it from the beginning (not using saved answers), yes.
--
Jean-Yves Bernier
On Fri, 23 May 2014, Cory Smelosky wrote:
Is it possible to have SYSGEN do an autoconfigure again? I'd love to not have to rely on my incorrect answers. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Fri, 23 May 2014, Dave McGuire wrote:
WOOHOO!! Great work, man!
Thanks!
Next I'm going to pop in a DHV11 and re-SYSGEN.
-Dave
On 05/23/2014 02:06 PM, Cory Smelosky wrote:
On Fri, 23 May 2014, Cory Smelosky wrote:
I did it!
3 x 64kbit x 1 DRAM chips bad, disabled half the board:
boot [1,54]rsx11m
XDT: 66
XDT>g
RSX-11M-PLUS V4.3 BL66
sav /wb
RSX-11M-PLUS V4.3 BL66 256.KW System:"MINDY "
RED DU:=SY:
RED DU:=LB:
RED DU:=SP:
MOU DU:"RSX11MPBL66"
@DU:[1,2]STARTUP
A lot of my problem was XDT user error. Whoops.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
WOOHOO!! Great work, man!
-Dave
On 05/23/2014 02:06 PM, Cory Smelosky wrote:
On Fri, 23 May 2014, Cory Smelosky wrote:
I did it!
3 x 64kbit x 1 DRAM chips bad, disabled half the board:
boot [1,54]rsx11m
XDT: 66
XDT>g
RSX-11M-PLUS V4.3 BL66
sav /wb
RSX-11M-PLUS V4.3 BL66 256.KW System:"MINDY "
RED DU:=SY:
RED DU:=LB:
RED DU:=SP:
MOU DU:"RSX11MPBL66"
@DU:[1,2]STARTUP
A lot of my problem was XDT user error. Whoops.
--
Dave McGuire, AK4HZ
New Kensington, PA
On Fri, 23 May 2014, Cory Smelosky wrote:
I did it!
3 x 64kbit x 1 DRAM chips bad, disabled half the board:
boot [1,54]rsx11m
XDT: 66
XDT>g
RSX-11M-PLUS V4.3 BL66
sav /wb
RSX-11M-PLUS V4.3 BL66 256.KW System:"MINDY "
RED DU:=SY:
RED DU:=LB:
RED DU:=SP:
MOU DU:"RSX11MPBL66"
@DU:[1,2]STARTUP
A lot of my problem was XDT user error. Whoops.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Cleaning the board had no effect. Went back to the other one.
I identified a failing row of chips and tried swapping some around bit after awhile anything above 128KW became glitchy. (I'll clean contacts tomorrow)
Also...it seems I had a bad DELQA on the bus which probably wasn't helping.
Sent from mobile device that advertises itself for no good reason
On 22 May 2014, at 09:33, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 15:06, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
:-)
So, what is the status now? It don't work?
DMA works fine! However other tests and SCSI FIFO does not.
Hmm. Ok.
I assume you have CPU in slot 1, and memory in slot 2. Slot 3 is also Q/CD,
Yeah.
and after that (if I remember right) you have Q/Q slots. Have you tried minimizing the config to just the minimum required to test the machine?
Yeah. I also wiped down the board a bit...it gave ECC errors before even doing memory access this time.
Putting the project on hold until the board dries. (It's the board i'm 98% sure, the behaviour is different enough to not indicate any other boards. Either it'll work after this...or it'll look really damn clean!)
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 15:06, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
:-)
So, what is the status now? It don't work?
DMA works fine! However other tests and SCSI FIFO does not.
Hmm. Ok.
I assume you have CPU in slot 1, and memory in slot 2. Slot 3 is also Q/CD,
Yeah.
and after that (if I remember right) you have Q/Q slots. Have you tried minimizing the config to just the minimum required to test the machine?
Yeah. I also wiped down the board a bit...it gave ECC errors before even doing memory access this time.
Putting the project on hold until the board dries. (It's the board i'm 98% sure, the behaviour is different enough to not indicate any other boards. Either it'll work after this...or it'll look really damn clean!)
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-22 15:06, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
:-)
So, what is the status now? It don't work?
DMA works fine! However other tests and SCSI FIFO does not.
Hmm. Ok.
I assume you have CPU in slot 1, and memory in slot 2. Slot 3 is also Q/CD, and after that (if I remember right) you have Q/Q slots. Have you tried minimizing the config to just the minimum required to test the machine?
Johnny
On Thu, 22 May 2014, Johnny Billquist wrote:
:-)
So, what is the status now? It don't work?
DMA works fine! However other tests and SCSI FIFO does not.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-22 15:02, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 14:57, Johnny Billquist wrote:
On 2014-05-22 14:52, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
With the board in I can get to ODT...but:
QBUS BUS CONTROLLER TEST#1.......................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
QBUS BUS CONTROLLER TEST#2.......................... PASSED
QBUS BUS CONTROLLER TEST#3.......................... PASSED
QBUS SINGLE WORD DMA TEST........................... PASSED
QBUS TO FIFO DMA TEST............................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
I think the red ECC error light is on, too but the system IS halted.
That sounds bad. What backplane is this sitting in now? And I think the
PMI memory board actually do some internal diagnostics already at power
on, so an error light on is probably not a good sign...
By the way, I hope/assume that you also configured it to start at
address 0...
I have. Took me a bit to figure out which DIP switch position meant
"on" and which meant "off".
:-)
So, what is the status now? It don't work?
Johnny
On Thu, 22 May 2014, Cory Smelosky wrote:
I have. Took me a bit to figure out which DIP switch position meant "on" and which meant "off".
Damn. With it set to address 0 the ECC error light comes on when I try to do the SCSI diagnostics. Looks like a bit of this board is consistently bad, too. :(
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 14:57, Johnny Billquist wrote:
On 2014-05-22 14:52, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
With the board in I can get to ODT...but:
QBUS BUS CONTROLLER TEST#1.......................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
QBUS BUS CONTROLLER TEST#2.......................... PASSED
QBUS BUS CONTROLLER TEST#3.......................... PASSED
QBUS SINGLE WORD DMA TEST........................... PASSED
QBUS TO FIFO DMA TEST............................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
I think the red ECC error light is on, too but the system IS halted.
That sounds bad. What backplane is this sitting in now? And I think the
PMI memory board actually do some internal diagnostics already at power
on, so an error light on is probably not a good sign...
By the way, I hope/assume that you also configured it to start at address 0...
I have. Took me a bit to figure out which DIP switch position meant "on" and which meant "off".
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
In any cluster all nodes minus one must be routers, L1 or L2. The Nth node may be an end node. That's what I remember....
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jordi Guillaumes i Pons
Verzonden: donderdag 22 mei 2014 11:10
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] DECNET Cluster alias and simh
El 22/05/2014, a les 9.27, Kari Uusim ki <uusimaki at exdecfinland.org> va escriure:
For the DECnet cluster alias you need (at least) one routing node (L1) or a router.
Does any of the cluster nodes have routing enabled?
I hqve a L1 router and an area router in the same LAN. Is that enough, or should I enable routing in one of the cluster members?
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 2014-05-22 14:57, Johnny Billquist wrote:
On 2014-05-22 14:52, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
With the board in I can get to ODT...but:
QBUS BUS CONTROLLER TEST#1.......................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
QBUS BUS CONTROLLER TEST#2.......................... PASSED
QBUS BUS CONTROLLER TEST#3.......................... PASSED
QBUS SINGLE WORD DMA TEST........................... PASSED
QBUS TO FIFO DMA TEST............................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
I think the red ECC error light is on, too but the system IS halted.
That sounds bad. What backplane is this sitting in now? And I think the
PMI memory board actually do some internal diagnostics already at power
on, so an error light on is probably not a good sign...
By the way, I hope/assume that you also configured it to start at address 0...
Johnny
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 14:52, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
With the board in I can get to ODT...but:
QBUS BUS CONTROLLER TEST#1.......................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
QBUS BUS CONTROLLER TEST#2.......................... PASSED
QBUS BUS CONTROLLER TEST#3.......................... PASSED
QBUS SINGLE WORD DMA TEST........................... PASSED
QBUS TO FIFO DMA TEST............................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
I think the red ECC error light is on, too but the system IS halted.
That sounds bad. What backplane is this sitting in now? And I think the PMI memory board actually do some internal diagnostics already at power on, so an error light on is probably not a good sign...
Still the BA123.
Turns out the light came on when I tried to read invalid memory. ;)
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-22 14:52, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
With the board in I can get to ODT...but:
QBUS BUS CONTROLLER TEST#1.......................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
QBUS BUS CONTROLLER TEST#2.......................... PASSED
QBUS BUS CONTROLLER TEST#3.......................... PASSED
QBUS SINGLE WORD DMA TEST........................... PASSED
QBUS TO FIFO DMA TEST............................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST
MEMORY.
I think the red ECC error light is on, too but the system IS halted.
That sounds bad. What backplane is this sitting in now? And I think the PMI memory board actually do some internal diagnostics already at power on, so an error light on is probably not a good sign...
Johnny
On Thu, 22 May 2014, Cory Smelosky wrote:
With the board in I can get to ODT...but:
QBUS BUS CONTROLLER TEST#1.......................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST MEMORY.
QBUS BUS CONTROLLER TEST#2.......................... PASSED
QBUS BUS CONTROLLER TEST#3.......................... PASSED
QBUS SINGLE WORD DMA TEST........................... PASSED
QBUS TO FIFO DMA TEST............................... FAILED
*** FAILED DUE TO UNINITIALIZED Q-BUS MAP, DMA FAILURE OR NON-EXIST MEMORY.
I think the red ECC error light is on, too but the system IS halted.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 22 May 2014, Johnny Billquist wrote:
Yup!
Nice.
Yeah.
Did you know that those memory boards work just fine as normal Qbus
memory boards? :-)
THAT I did not know! Looks like I have a spare.
Indeed. Those memories are funny. If you put them in an 11/83, they either act as Qbus memory or PMI memory, depending on if you place them before or after the CPU. And that makes a speed difference...
Cool.
Of course, for all other type of systems, you'll have to place them after the CPU.
Yeah. ;)
There's that 16K board...I could adjust the memory offsets.
Ugh! 16K is not much...
Nope...but MAYBE just enough to fit the lower bits of the executive?
Maybe. But I think that PMI memory is a better option. :-)
Yup. ;)
M8637.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-22 14:27, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 14:20, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
I've never seen a board with the ability to disable parity...
It's a clearpoint board. Technically it's just disabling the parity
circuitry CSR.
The "***EXEC PARITY ERROR STOP***" message is when you get a parity
error in the memory where the kernel resides.
RSX can deal with memory errors in other parts of the memory, by just
making that memory unavailable for programs to use. But it cannot do
this with the parts that the kernel use, so then it panics instead.
Ahh. Damn. I'd be okay if the only other memory board I had spare
wasn't PMI.
PMI? As the the PMI memory boards for the 11/83?
Yup!
Nice.
Did you know that those memory boards work just fine as normal Qbus
memory boards? :-)
THAT I did not know! Looks like I have a spare.
Indeed. Those memories are funny. If you put them in an 11/83, they either act as Qbus memory or PMI memory, depending on if you place them before or after the CPU. And that makes a speed difference...
Of course, for all other type of systems, you'll have to place them after the CPU.
There's that 16K board...I could adjust the memory offsets.
Ugh! 16K is not much...
Nope...but MAYBE just enough to fit the lower bits of the executive?
Maybe. But I think that PMI memory is a better option. :-)
Johnny
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 14:20, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
I've never seen a board with the ability to disable parity...
It's a clearpoint board. Technically it's just disabling the parity
circuitry CSR.
The "***EXEC PARITY ERROR STOP***" message is when you get a parity
error in the memory where the kernel resides.
RSX can deal with memory errors in other parts of the memory, by just
making that memory unavailable for programs to use. But it cannot do
this with the parts that the kernel use, so then it panics instead.
Ahh. Damn. I'd be okay if the only other memory board I had spare
wasn't PMI.
PMI? As the the PMI memory boards for the 11/83?
Yup!
Did you know that those memory boards work just fine as normal Qbus memory boards? :-)
THAT I did not know! Looks like I have a spare.
There's that 16K board...I could adjust the memory offsets.
Ugh! 16K is not much...
Nope...but MAYBE just enough to fit the lower bits of the executive?
First bugcheck is essentially an illegal instruction in kernel mode.
(Error code=110 is illegal instruction, while facility=300 means the
executive.)
Ahh.
No idea why you got that one, though, unless it was a fallout of bad memory...
Could very be fallout of bad memory.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-22 14:22, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
With parity disabled and RSTS/E:
https://ghostbin.com/paste/ksd3c a bad ~50K? I can disable everything
above 512kByte which is...i forget how many words.
512Kbytes is 256Kword. :-)
Ahh.
But it's not clear that the address are in Kwords...
It's a 1M board...so it's either at the very upper end of memory or in
the middle.
Unfortunately it is before the halfway point, so you'd have to disable more than half the memory...
(If it isn't close to the total end...)
Johnny
On 2014-05-22 14:20, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
I've never seen a board with the ability to disable parity...
It's a clearpoint board. Technically it's just disabling the parity
circuitry CSR.
The "***EXEC PARITY ERROR STOP***" message is when you get a parity
error in the memory where the kernel resides.
RSX can deal with memory errors in other parts of the memory, by just
making that memory unavailable for programs to use. But it cannot do
this with the parts that the kernel use, so then it panics instead.
Ahh. Damn. I'd be okay if the only other memory board I had spare
wasn't PMI.
PMI? As the the PMI memory boards for the 11/83?
Did you know that those memory boards work just fine as normal Qbus memory boards? :-)
There's that 16K board...I could adjust the memory offsets.
Ugh! 16K is not much...
First bugcheck is essentially an illegal instruction in kernel mode.
(Error code=110 is illegal instruction, while facility=300 means the
executive.)
Ahh.
No idea why you got that one, though, unless it was a fallout of bad memory...
Johnny
On Thu, 22 May 2014, Johnny Billquist wrote:
With parity disabled and RSTS/E:
https://ghostbin.com/paste/ksd3c a bad ~50K? I can disable everything
above 512kByte which is...i forget how many words.
512Kbytes is 256Kword. :-)
Ahh.
But it's not clear that the address are in Kwords...
It's a 1M board...so it's either at the very upper end of memory or in the middle.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
