From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1197fc15c9c040aca74cd7c935c01bfa@plan9.bell-labs.com> From: jmk@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] Has anyone got a 2114x ethernet card working under 4th Edition? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-ubtmcgbqgrunutrblrawncikng" Date: Mon, 8 Jul 2002 21:49:26 -0400 Topicbox-Message-UUID: c5ffd406-eaca-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-ubtmcgbqgrunutrblrawncikng Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Ether2114x.c has a facility similar to the 'fixup' code in the linux driver, look for the 'leaf21140' table. If you can compile the kernel with the 'DEBUG' flag on in the driver and bring the system up with the duff card as ether1, the debug messages on the console and the contents of the device 'ifstats' file (will give the SROM contents) would aid in patching the driver. --upas-ubtmcgbqgrunutrblrawncikng Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Mon Jul 8 20:59:15 EDT 2002 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Mon Jul 8 20:59:14 EDT 2002 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 19715199B3; Mon, 8 Jul 2002 20:59:07 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 45189199B3 for <9fans@cse.psu.edu>; Mon, 8 Jul 2002 20:58:39 -0400 (EDT) Received: from cg938416a (pcp085155pcs.arnysm01.nj.comcast.net [68.46.96.100]) by mtaout02.icomcast.net (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 13 2002)) with SMTP id <0GYY00B7OIPE9J@mtaout02.icomcast.net> for 9fans@cse.psu.edu; Mon, 08 Jul 2002 20:58:27 -0400 (EDT) From: John DeGood Subject: Re: [9fans] Has anyone got a 2114x ethernet card working under 4th Edition? To: 9fans@cse.psu.edu Message-id: <010901c226e3$b3f1dfc0$1b02a8c0@arnysm01.nj.comcast.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <005101c1fa80$94ab59a0$0100a8c0@landra.org> Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Mon, 08 Jul 2002 20:58:12 -0400 > From: "Russ Cox" > > What does > > pci > > print? The line I care about is the one > where the second field begins 02., as in > the three marked below. I know this is an old thread, but I just ran into this problem today with an SMC 9332DST card and thought my experience might help others. The broken detection message was: #l0: 2114x: 0 Mbps port 0xfc80 irq 10 c0f401000000 Note that the speed and EA are both bogus. Here's the interesting part: I tried a newer variant of the card, an SMC 9332BDT, and it works perfectly with the 2114x driver. The output from "pci" for *both* cards is identical: 0.15.0: 02.00.00 1011/0009 10 0:0000fc81 128 1:ffbefc00 128 The Tulip chips on the 2 cards have the following markings: 9332DST (doesn't work with 2114x driver): 21140 / DC1010BA / 21-40673-01 9332BDT (works with 2114x driver): 21140-AE / DC1064B / 21-43864-03 I suspect transceiver or EEPROM differences may be the significant driver issue in the case of these 2 cards rather than the variant of Tulip chip. FWIW, I note that Don Becker's Tulip driver for Linux has an entry in "eeprom_fixups[]" for the (broken in Plan 9) 9332DST, while I don't see anything similar in ether2114x.c John --upas-ubtmcgbqgrunutrblrawncikng--