Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!pipex!unipalm!uknet!cf-cm!news From: spedpr@thor.cf.ac.uk (Paul Richards) Newsgroups: comp.unix.bsd Subject: Lance query Message-ID: <12764.9210021637@thor.cf.ac.uk> Date: 2 Oct 92 16:37:34 GMT Sender: news@cm.cf.ac.uk (Network News System) Organization: University of Wales College at Cardiff Lines: 35 X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway I've been getting a number of is1:reset errors from the isolink driver and the cause is due to the lance stopping its transmitter. Specifically, in the interrupt routine the transmitter-on (TXON) bit of the lance is checked and if it isn't set then a reset occurs. What I want to know is: under what circumstances does the lance clear this bit, supposedly indicating that the transmitter has been switched off? I can get this to happen consistently when running a X graphics package as a client on one machine, displaying to a server on another, with 386bsd in between acting as a router. Strang thing is I get these reset errors on the server side card but not on the client side card! Why would one card behave like this and not the other since they're both handling these X packets. In fact the client side card is connected to the rest of the world so it's a LOT busier but it doesn't give me any hassle. Anyway, if someone can explain why the lance does this I'll track down the cause myself. Although I wrote the isolink driver I took most of the lance code from other lance based drivers so I don't know a lot about the lance's behaviour. Is anyone else getting errors with this driver? Does anyone else even have an isolink card or am I the only one in an university that only allows isolink cards to be used! -- Paul Richards at Cardiff university, UK. spedpr@uk.ac.cf.thor Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk UUCP: spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr +++