digi problem
So here's one for you in the old farts of computing club (I think you have to be around 30 to qualify for this club, but I could be wrong).
This weekend (details will be glossed over) we had a complete system melt down. After adding the two new hard drives (hgaving them added, actually, as I didn't do the raid configuration on the grounds that I know next to nothing about raidding hard drives) we reinstalled linux (redhat 9.0) and restored as much as possible from backup. So far so good.
We have 3 C/CON digi ports that link the system to our wyse 50 dumb terminals (we have around 30 of these terminals). We added the correct driver (DGAP Driver for Linux ver. 1.1-1, src.rpm version, I nbelieve, which is in 40002347_a.src.rpm). When we got this up and running (it's working on almost all terminals) we found five terminals that weren't recieving a login for some reason (not getting the getty, not being identified by the driver, whatever).
I was tyhinking maybe they had been in a bad place when the driver was set up and that it just hadn't found them, so it didn't know to send a getty there, but this morning a terminal that was working just fine yesterday (and for half of this morning) stopped working. it went blank and now will not give a login either.
I've done some switching to eliminate the problem being from the terminals and I strongly suspect that it's not a line problem (we're having that looked at soon, but since one of them just stopped working I think it's reasonable to assume it's not).
Anyone have a good idea here? I'm all out. I have been able to trace one of hte defunct lines, but I can't figure out what to do with that. I don't even know how the C/CONs track these ports (for the record all three C/CONs are daisy chained together and feed through one serial port on our server).
Anyone? Anyone at all?
This weekend (details will be glossed over) we had a complete system melt down. After adding the two new hard drives (hgaving them added, actually, as I didn't do the raid configuration on the grounds that I know next to nothing about raidding hard drives) we reinstalled linux (redhat 9.0) and restored as much as possible from backup. So far so good.
We have 3 C/CON digi ports that link the system to our wyse 50 dumb terminals (we have around 30 of these terminals). We added the correct driver (DGAP Driver for Linux ver. 1.1-1, src.rpm version, I nbelieve, which is in 40002347_a.src.rpm). When we got this up and running (it's working on almost all terminals) we found five terminals that weren't recieving a login for some reason (not getting the getty, not being identified by the driver, whatever).
I was tyhinking maybe they had been in a bad place when the driver was set up and that it just hadn't found them, so it didn't know to send a getty there, but this morning a terminal that was working just fine yesterday (and for half of this morning) stopped working. it went blank and now will not give a login either.
I've done some switching to eliminate the problem being from the terminals and I strongly suspect that it's not a line problem (we're having that looked at soon, but since one of them just stopped working I think it's reasonable to assume it's not).
Anyone have a good idea here? I'm all out. I have been able to trace one of hte defunct lines, but I can't figure out what to do with that. I don't even know how the C/CONs track these ports (for the record all three C/CONs are daisy chained together and feed through one serial port on our server).
Anyone? Anyone at all?
