jdp@PacBell.COM (Jerry D. Pierce) (12/17/89)
I'm trying to get a Computone ATvantage 4 port board to work in a Compaq 386/20e system running Interactive 2.0.2 with 2 meg of ram. (Yeah, I know, more ram is forthcoming...) The interactive system is up and running just fine, so I run shutdown to bring the machine down quietly. I pop open the cover and install the computone board (jumper set to int 15) put everything back together and power it up. I run sysadm installpkg and pop the Computone driver disk into the drive (drivers 4.31) and it complains that int 15 is already in use. Great. I take it all back apart and try setting the jumpers to the next position and removing the Computone drivers and re-installing them. No complaints this time, the box reboots, it tells me that the boards are successfully initialized... However, once a getty is respawning, it CANNOT be killed. I can edit the inittab and change the entry to off and then do an init q which has no affect, I can even do a kill -9 PID and it won't die... Anybody have any suggestions?? Jerry Pierce pacbell!pbhyf!jdp PS: Yes, the Computone driver disk says it's for the Interactive version of UNIX...
larry@nstar.UUCP (Larry Snyder) (12/17/89)
> However, once a getty is respawning, it CANNOT be killed. I can > edit the inittab and change the entry to off and then do an init q > which has no affect, I can even do a kill -9 PID and it won't die... > > Yes, the Computone driver disk says it's for the Interactive > version of UNIX... What version of firmware in the AT8? There were problems on the older boards with some of the firmware which required that the boards be sent back to Computone for hardware modifications. -- Larry Snyder, Northern Star Communications, Notre Dame, IN uucp: root@nstar -or- ...!iuvax!ndmath!nstar!root
stewart@netxcom.DHL.COM (John Stewart) (12/22/89)
In article <6585@pbhyf.PacBell.COM> jdp@PacBell.COM (Jerry D. Pierce) writes: >However, once a getty is respawning, it CANNOT be killed. I can >edit the inittab and change the entry to off and then do an init q >which has no affect, I can even do a kill -9 PID and it won't die... Often such behavior is due to a call to sleep() in the driver which is not followed by a check to see if the wakeup was due to an interrupt. In such a case, an interrupt will wake up the driver, which will determine that the resource it is waiting for is not yet available and then just go back to sleep. -- John Stewart, Effective Computing, Inc., (202) 232-5470 stewart@ecompin.UUCP at NetExpress Communications, Inc., (703) 749-2796 stewart@netxcom.iad-nxe.global-mis.dhl.com