beth@batcomputer.tn.cornell.edu (Beth Elias) (01/10/89)
Does anyone know of any software or hardware weirdness that would keep our MtXinu kernel on a Micro-Vax II from recognizing our new delqa board? We already have a deqna that configures just dandy, but the delqa is never seen. We have already done the obvious, switched addresses, plugged both into the correct network, had the board swapped for another. The result is that the hardware checks out fine and we are left with the thought that the delqa does not do it's deqna emulation good enough for the deqna driver to recognize it. We need both boards 'cuz we gotta be a gateway... Any ideas or thought would be appreciated. Thanks. Beth Elias beth@tcgould.tn.cornell.edu
pat@orac.pgh.pa.us (Pat Barron) (01/12/89)
In article <7139@batcomputer.tn.cornell.edu> beth@batcomputer.tn.cornell.edu (Beth Elias) writes: > >Does anyone know of any software or hardware weirdness >that would keep our MtXinu kernel on a Micro-Vax II >from recognizing our new delqa board? It turns out that the DELQA takes longer to self-test than the DEQNA. The probe routine hangs out for a while, but not quite long enough. Eventually, it decides that the board is either not there or dead, and it doesn't configure. Some time later the device comes ready, but by that time the kernel has already given up. I'm told that you run into similar problems when you try to use a DELUA with the DEUNA driver. I had this exact same problem when I tried to use a DELQA in my MicroVAX Internet gateway. I have fixed the qe driver so that it can talk to the DELQA, and can send diffs to people who need them. --Pat. -- Pat Barron Internet: pat@orac.pgh.pa.us - or - orac!pat@gateway.sei.cmu.edu UUCP: ...!uunet!apexepa!sei!orac!pat - or - ...!pitt!darth!orac!pat