From owner-freebsd-hackers Mon Aug 7 4:44:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 9EC6737BD89; Mon, 7 Aug 2000 04:44:39 -0700 (PDT) (envelope-from kts.org!hm@worker.thw-IP.NET) Received: from localhost (2561 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Mon, 7 Aug 2000 13:44:37 +0200 (CEST) (Smail-3.2.0.111 2000-Feb-17 #12 built 2000-May-16) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 8427E52CED; Mon, 7 Aug 2000 13:37:03 +0200 (CEST) Received: by bert.kts.org (Postfix, from userid 100) id B38461F1C; Mon, 7 Aug 2000 13:36:57 +0200 (CEST) Subject: Re: 3Com 10/100 Mini PCI Ethernet In-Reply-To: <200008070920.CAA02797@mass.osd.bsdi.com> from Mike Smith at "Aug 7, 2000 2:20:13 am" To: msmith@FreeBSD.ORG (Mike Smith) Date: Mon, 7 Aug 2000 13:36:57 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1602 Message-Id: <20000807113657.B38461F1C@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I think the ep driver (which does some funny things to the eeprom) managed > > to overwrite part of the eeprom so that the xl driver failed to recognize > > the card. I then tried to add it to the vx driver (at that point i think > > i started to know what i did) which failed too, so i wrote a subroutine > > to display the eeprom contents which (because i did not understood the > > the OP and SubOP command fields before running it) finally erased the > > eeprom contents to 0xffff in all locations (which now prevents the card > > from being initialized by the BIOS - has anybody an idea how to revive > > such a PCI card ????). > > You would need to write the original EEPROM contents back into the > EEPROM, after manually configuring it. Very difficult. Am i right assuming that pciconf is the right tool for this (manually configuring) job ? > > Do i understand you right in that you would do a fresh start with this > > card using the xl driver ? I'm a bit concerned about again accidentially > > overwriting the eeprom, its an _expensive_ card ... ;-) > > That's correct. The xl driver is not likely to trash the eeprom, > although I'm quite surprised that the 'ep' driver did. > > What possessed you to start with an ISA-only driver when the device is so > clearly a PCI device? It was the device ID 0x6055 in the ep driver which is identical to the device ID in the Mini PCI version. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message