From owner-freebsd-current Mon Jun 5 04:23:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA19942 for current-outgoing; Mon, 5 Jun 1995 04:23:36 -0700 Received: from hq.icb.chel.su (icb-rich-gw.icb.chel.su [193.125.10.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA19790 ; Mon, 5 Jun 1995 04:20:59 -0700 Received: from localhost (babkin@localhost) by hq.icb.chel.su (8.6.5/8.6.5) id HAA14212; Tue, 30 May 1995 07:56:08 +0500 From: "Serge A. Babkin" Message-Id: <199505300256.HAA14212@hq.icb.chel.su> Subject: Re: ep and ie drivers conflict (?) To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Date: Tue, 30 May 1995 07:56:07 +0500 (GMT+0500) Cc: nnd@gw.itfs.nsk.su, current@FreeBSD.ORG In-Reply-To: <199505291517.IAA00401@freefall.cdrom.com> from "Justin T. Gibbs" at May 29, 95 08:17:29 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1002 Sender: current-owner@FreeBSD.ORG Precedence: bulk > >> It seems to me that problem is in 3COM's 'ELINK_ID_PORT' > >> or 'EP_ID_PORT' (0x100) which is used in both ep and ie > >> drivers. (Is it right that probe order of devices follows > >> their order in config file ?). > > > >The order of probing of ID_PORT may be any (as it looks to me). > >IMHO the problem is that the ie driver doesn't do any checks for > >manufacturer ID nor product ID and erroneuosly identifies 3c509 > >card as its (but i'm not shure about this diagnosys). > > It doesn't identify the 3c509 as an ie device, it just spams the > 3c509 and I guess the ep driver does not do enough to resurect it. Agreed. But did you applied the last patch I published ? It contains a change in the initialization procedure made by Steven E. Piette that should help (at least it allows to recover after DOS drivers). I can't try it because I have no -current now. Serge Babkin ! (babkin@hq.icb.chel.su) ! Headquarter of Joint Stock Commercial Bank "Chelindbank" ! Chelyabinsk, Russia