From owner-freebsd-hackers Wed Aug 2 23:21:19 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 E8E8E37B717; Wed, 2 Aug 2000 23:21:14 -0700 (PDT) (envelope-from kts.org!hm@worker.thw-IP.NET) Received: from localhost (2786 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 ; Thu, 3 Aug 2000 08:21:13 +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 A32C052B91; Thu, 3 Aug 2000 08:21:06 +0200 (CEST) Received: by bert.kts.org (Postfix, from userid 100) id 18BD31F1C; Thu, 3 Aug 2000 08:21:02 +0200 (CEST) Subject: Re: 3Com 10/100 Mini PCI Ethernet In-Reply-To: <200008022321.QAA01219@mass.osd.bsdi.com> from Mike Smith at "Aug 2, 2000 4:21:49 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Thu, 3 Aug 2000 08:21:02 +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: 1827 Message-Id: <20000803062102.18BD31F1C@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'm looking for docs for the Mini PCI card in the subject, it has the 3Com > > part/product no. 3CN3AV1556. It is a 10/100 ethernet 56k modem combo card > > built into an HP laptop. > > Have you tried booting FreeBSD on this system yet? If so, does the 'xl' > driver pick it up? If not, can you send the output of 'pciconf -l', as > it may just require a new PCI ID in the driver. Yes, i first tried the ep driver, then the xl and then the vx by adding the chip id (0x6055) to the probe routine. 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 ????). Anyway, i paid my "Lehrgeld" (money for learning ?) and i'm currently waiting for an exchange card. Someone from the Linux-camp wrote a vortex diagnostics program which displays the eeprom and register contents of those cards, i ported that in the meantime to be at least able to get a snapshot of the good eeprom contents. 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 ... ;-) 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