From owner-freebsd-hackers Mon Aug 7 2: 8:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id 5D37D37BD8D for ; Mon, 7 Aug 2000 02:08:54 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id CAA02797; Mon, 7 Aug 2000 02:20:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008070920.CAA02797@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hm@kts.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3Com 10/100 Mini PCI Ethernet In-reply-to: Your message of "Thu, 03 Aug 2000 08:21:02 +0200." <20000803062102.18BD31F1C@bert.kts.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 02:20:13 -0700 From: Mike Smith 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 ????). You would need to write the original EEPROM contents back into the EEPROM, after manually configuring it. Very difficult. > 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? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message