From owner-freebsd-bugs Sat Apr 12 17:20:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA04252 for bugs-outgoing; Sat, 12 Apr 1997 17:20:05 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA04238; Sat, 12 Apr 1997 17:20:01 -0700 (PDT) Date: Sat, 12 Apr 1997 17:20:01 -0700 (PDT) Message-Id: <199704130020.RAA04238@freefall.freebsd.org> To: freebsd-bugs Cc: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: bin/3230: Unable to resolve dev conflict between ed0 and seagate scsi device Reply-To: j@uriah.heep.sax.de (J Wunsch) Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/3230; it has been noted by GNATS. From: j@uriah.heep.sax.de (J Wunsch) To: Robert_Batten@Candle.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/3230: Unable to resolve dev conflict between ed0 and seagate scsi device Date: Sun, 13 Apr 1997 02:01:50 +0200 As Robert_Batten@Candle.com wrote: (Please break long lines.) > >Description: > Using the -c option on boot I attempted to resolve a device conflict > between ed0 and the seagate sea0 device. Even though there appears > to be no conflict ( i.e io base 280 irq 3 mmaddr 0d8000) for ed0 is > not conflicting with sea0), the conf flag persists. Worse still, the > problem disables my nic with edo:device timeout!!! Are you sure the conflict is against the sea0 driver? Judging from the use of irq3, i would rather suspect a conflict with the sio1 device. If this is not the case, please post the exact configuration as you tried it (i.e., the settings of all the drivers you haven't disabled). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)