From agibson@ptm.com Mon, 31 Jul 2000 17:40:24 -0400 Date: Mon, 31 Jul 2000 17:40:24 -0400 From: agibson@ptm.com agibson@ptm.com Subject: [tulip] starfire bring down and up interface problem I apologize ahead of time, as I realize this is the tulip list, but starfire does not have a list and tulip is the closest list to it. With the pci-scan and starfire(starfire.c:v0.15 4/07/2000) module loaded, and then bring up eth1(first interface of starfire), everything works fine. If I then ifdown and then ifup the eth1 interface, the starfire driver does not seem to be able to send outgoing packets but thinks it does according to tcpdump on that same system. ping from the system with the starfire driver(10.10.15.10) # tcpdump -n -i eth1 (tcpdump running on 10.10.15.10) 16:40:48.247496 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:49.247476 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:50.247654 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:51.247478 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:52.247485 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:53.280676 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:54.277485 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:55.277476 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) a seperate ping initiated from the remote system(10.10.15.1) # tcpdump -n -i eth1 (tcpdump running on 10.10.15.10) 16:41:17.082389 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:17.082476 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) 16:41:18.512809 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:18.512878 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) 16:41:19.514154 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:19.514221 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) 16:41:20.515417 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:20.515484 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) NOTE: The system with the starfire driver shows that the packets are transmitting(see trace above, the light on the starfire card blinks), but the remote system never gets the packets. I verified this running windump on the remote system. STARFIRE DEBUG LEVEL AT 7: SUCCESSFUL PING BEFORE BRINGING THE INTERFACE DOWN Jul 31 14:06:34 agibson2 kernel: eth1: Tx #38 slot 6 b1010062 0f03cd82. Jul 31 14:06:34 agibson2 kernel: eth1: Transmit frame #39 queued in slot 7. Jul 31 14:06:34 agibson2 kernel: eth1: Interrupt status 9001. Jul 31 14:06:34 agibson2 kernel: eth1: Tx Consumer index is 7. Jul 31 14:06:34 agibson2 kernel: eth1: Tx completion entry 38 is 8f000030. Jul 31 14:06:34 agibson2 kernel: eth1: Interrupt status 0000. Jul 31 14:06:34 agibson2 kernel: eth1: exiting interrupt, status=0x0000. Jul 31 14:06:34 agibson2 kernel: eth1: Interrupt status 8101. Jul 31 14:06:34 agibson2 kernel: netdev_rx() status of 17 was 60110062. Jul 31 14:06:34 agibson2 kernel: netdev_rx() normal Rx pkt length 98, bogus_cnt 255. Jul 31 14:06:34 agibson2 kernel: Rx data 00:00:d1:ed:7f:b5 00:20:af:dd:ef:5f 0800 69.0.0.84. Jul 31 14:06:34 agibson2 kernel: exiting netdev_rx() status of 18 was 00000000 0. Jul 31 14:06:34 agibson2 kernel: eth1: Tx Consumer index is 7. Jul 31 14:06:34 agibson2 kernel: eth1: Interrupt status 0000. Jul 31 14:06:34 agibson2 kernel: eth1: exiting interrupt, status=0x0000. (INTERFACE BROUGHT DOWN AND BACK UP HERE) Jul 31 14:06:35 agibson2 kernel: eth1: Shutting down ethercard, status was Int 0000. Jul 31 14:06:35 agibson2 kernel: eth1: Queue pointers were Tx 39 / 39, Rx 18 / 18. Jul 31 14:06:35 agibson2 kernel: Jul 31 14:06:35 agibson2 kernel: Tx ring at 01d75000: Jul 31 14:06:35 agibson2 kernel: #0 desc. b1010062 0f03cd82 -> 00000000. Jul 31 14:06:35 agibson2 kernel: #1 desc. b1010062 0f03cd82 -> 00000000. Jul 31 14:06:35 agibson2 kernel: #2 desc. b1010062 0f03cd82 -> 00000000. Jul 31 14:06:35 agibson2 kernel: #3 desc. b1010062 0f03cd82 -> 00000000. Jul 31 14:06:35 agibson2 kernel: #4 desc. b1010062 0f03cd82 -> 00000000. Jul 31 14:06:35 agibson2 kernel: #5 desc. b1010062 0f03cd82 -> 00000000. Jul 31 14:06:35 agibson2 kernel: #6 desc. b1010062 0f03cd82 -> 00000000. Jul 31 14:06:35 agibson2 kernel: #7 desc. b101006e 0f03cc62 -> 00000000. Jul 31 14:06:35 agibson2 kernel: Rx ring at 01a91000 -> c1bf6000: Jul 31 14:06:35 agibson2 kernel: #0 desc. 0e9a7011 -> 00000000 Jul 31 14:06:35 agibson2 kernel: #1 desc. 0f50a011 -> 00000000 Jul 31 14:06:35 agibson2 kernel: #2 desc. 0f285011 -> 00000000 Jul 31 14:06:35 agibson2 kernel: #3 desc. 0f284011 -> 00000000 Jul 31 14:06:35 agibson2 kernel: #4 desc. 08cba811 -> 00000000 Jul 31 14:06:35 agibson2 kernel: #5 desc. 08ff3011 -> 00000000 Jul 31 14:06:35 agibson2 kernel: #6 desc. 08ec9011 -> 00000000 Jul 31 14:06:35 agibson2 kernel: #7 desc. 0f50a811 -> 00000000 Jul 31 14:06:40 agibson2 last message repeated 2 times Jul 31 14:06:41 agibson2 kernel: eth1: netdev_open() irq 7. Jul 31 14:06:41 agibson2 kernel: eth1: Filling in the station address. Jul 31 14:06:41 agibson2 kernel: eth1: Setting the Rx and Tx modes. Jul 31 14:06:41 agibson2 kernel: eth1: Done netdev_open(). Jul 31 14:06:42 agibson2 kernel: eth1: Tx #0 slot 0 b101002a 0ffc4dc2. Jul 31 14:06:42 agibson2 kernel: eth1: Transmit frame #1 queued in slot 1. Jul 31 14:06:42 agibson2 kernel: eth1: Interrupt status 9001. Jul 31 14:06:42 agibson2 kernel: eth1: Tx Consumer index is 1. Jul 31 14:06:42 agibson2 kernel: eth1: Tx completion entry 0 is 86dc0000. Jul 31 14:06:42 agibson2 kernel: eth1: Interrupt status 0000. Jul 31 14:06:42 agibson2 kernel: eth1: exiting interrupt, status=0x0000. Jul 31 14:06:43 agibson2 kernel: eth1: Tx #1 slot 1 b101002a 0f2a6e62. Jul 31 14:06:43 agibson2 kernel: eth1: Transmit frame #2 queued in slot 2. Jul 31 14:06:43 agibson2 kernel: eth1: Interrupt status 9001. Jul 31 14:06:43 agibson2 kernel: eth1: Tx Consumer index is 2. Jul 31 14:06:43 agibson2 kernel: eth1: Tx completion entry 1 is 99360008. Jul 31 14:06:43 agibson2 kernel: eth1: Interrupt status 0000. Jul 31 14:06:43 agibson2 kernel: eth1: exiting interrupt, status=0x0000. Jul 31 14:06:44 agibson2 kernel: eth1: Tx #2 slot 2 b101002a 0ffc4dc2. Jul 31 14:06:44 agibson2 kernel: eth1: Transmit frame #3 queued in slot 3. Jul 31 14:06:44 agibson2 kernel: eth1: Interrupt status 9001. Jul 31 14:06:44 agibson2 kernel: eth1: Tx Consumer index is 3. Jul 31 14:06:44 agibson2 kernel: eth1: Tx completion entry 2 is 8c020010. Jul 31 14:06:44 agibson2 kernel: eth1: Interrupt status 0000. Jul 31 14:06:44 agibson2 kernel: eth1: exiting interrupt, status=0x0000. AFTER STARFIRE INTERFACE IS BROUGHT DOWN AND BACK UP ping from the system with the starfire driver(10.10.15.10) # tcpdump -n -i eth1 (tcpdump running on 10.10.15.10) 16:40:48.247496 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:49.247476 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:50.247654 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:51.247478 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:52.247485 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:53.280676 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:54.277485 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) 16:40:55.277476 > arp who-has 10.10.15.1 tell 10.10.15.10 (0:0:d1:ed:7f:b5) ping from the remote system(10.10.15.1) # tcpdump -n -i eth1 (tcpdump running on 10.10.15.10) 16:41:17.082389 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:17.082476 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) 16:41:18.512809 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:18.512878 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) 16:41:19.514154 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:19.514221 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) 16:41:20.515417 B arp who-has 10.10.15.10 tell 10.10.15.1 16:41:20.515484 > arp reply 10.10.15.10 (0:0:d1:ed:7f:b5) is-at 0:0:d1:ed:7f:b5 (0:20:af:dd:ef:5f) NOTE: The system with the starfire driver shows that the packets are transmitting(see trace above, the light on the starfire card blinks), but the remote system never gets the packets. The only way to fix it is to remove the module while the interface is down, reinsert the module, and then bring the interface up again. If I ever need to bring the interface down and back up again, the same problem will appear. I have tested the same sequence with a regular 3com 3c905 and did not see any problems. Is there a known issue with bringing down and back up the interface with the starfire drivers? Any information would be appreciated. Redhat6.2 kernel 2.2.16 Adam From becker@scyld.com Mon, 31 Jul 2000 18:15:41 -0400 (EDT) Date: Mon, 31 Jul 2000 18:15:41 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] starfire bring down and up interface problem On Mon, 31 Jul 2000 agibson@ptm.com wrote: > I apologize ahead of time, as I realize this is the tulip list, but > starfire does not have a list and tulip is the closest list to it. > > With the pci-scan and starfire(starfire.c:v0.15 4/07/2000) module loaded, > and then bring up eth1(first interface of starfire), everything works > fine. If I then ifdown and then ifup the eth1 interface, the starfire > driver does not seem to be able to send outgoing packets but thinks it > does according to tcpdump on that same system. This was a bug with the station address and Rx filter configuration. The card was actually in promiscuous mode with the old version! It's fixed in the test version: ftp://www.scyld.com/pub/network/test/starfire.c Please send a report -- I want to move this to "released" status ASAP! Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf Clusters / Linux Installations Annapolis MD 21403 From agibson@ptm.com Mon, 31 Jul 2000 18:41:56 -0400 Date: Mon, 31 Jul 2000 18:41:56 -0400 From: agibson@ptm.com agibson@ptm.com Subject: [tulip] starfire bring down and up interface problem Thanks. This test version fixed the ifdown/ifup issue. I have flooded the interface with everything I could find to throw at it(packet wise) and it still works after ifdown/ifup. Adam On Mon, Jul 31, 2000 at 06:15:41PM -0400, Donald Becker wrote: > On Mon, 31 Jul 2000 agibson@ptm.com wrote: > > > I apologize ahead of time, as I realize this is the tulip list, but > > starfire does not have a list and tulip is the closest list to it. > > > > With the pci-scan and starfire(starfire.c:v0.15 4/07/2000) module loaded, > > and then bring up eth1(first interface of starfire), everything works > > fine. If I then ifdown and then ifup the eth1 interface, the starfire > > driver does not seem to be able to send outgoing packets but thinks it > > does according to tcpdump on that same system. > > This was a bug with the station address and Rx filter configuration. > The card was actually in promiscuous mode with the old version! > > It's fixed in the test version: > ftp://www.scyld.com/pub/network/test/starfire.c > > Please send a report -- I want to move this to "released" status ASAP! > > > Donald Becker becker@scyld.com > Scyld Computing Corporation http://www.scyld.com > 410 Severn Ave. Suite 210 Beowulf Clusters / Linux Installations > Annapolis MD 21403 > > > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip -- NOTE: my email address has changed to agibson@ptm.com please update this information in your address book From becker@scyld.com Wed, 2 Aug 2000 13:21:20 -0400 (EDT) Date: Wed, 2 Aug 2000 13:21:20 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Re: tulip.c vs ANA6944TX On Wed, 2 Aug 2000, Christopher E. Brown wrote: > To: linux-tulip@beowulf.org, linux-tulip-bug@beowulf.org, > linux-kernel@vger.rutgers.edu, linux-net@vger.rutgers.edu You should limit this to linux-tulip or linux-tulip-bug (aliases for tulip@scyld.com and tulip-bug@scyld.com), unless it's a problem with the pre-2.4 code in which case linux-kernel@vger.rutgers.edu is appropriate. > Subject: tulip.c vs ANA6944TX I no longer have access to one of these (they moved to Michigan with a large cluster), but the versions I had worked fine in previous tests. > I have a very strange issue with the tulip 21140 based > ANA6944TX quad 10/100 ethernet card. We were using the cards for some > time, but as of late 1999 they stopped working with most MBs they were > tried with, in one case with 2 identical Tyan S1590S boards, same rec, > bios, setting, CPU and cards 1 worked one didn't. That's very curious. > Symptoms are, board inits fine, no errors, everything looks correct, > but NWAY autoneg does not function, sometimes port will be usable in > 10Mbit HD, sometime repeated resets with tulip-diag will cause port to This is caused by the transceiver initial setting. > eth0: Advertising 01e1 on PHY 1, previously advertising 0101. This has the transceiver only advertising 100baseTx-HD at power-up! The transceiver's pins are normally wired so that it advertises all capabilities. Please try running 'mii-diag' from http://www.scyld.com/diag/index.html Reset the transciver, and check its state mii-diag eth0 -R; mii-diag eth0 Advertise everything, and check the state mii-diag eth0 -A 0x01e1; mii-diag eth0 > function for a short period. With some mainboards, ports 1 and 3 or 2 > and 4 will function, but erraticly. Passing options= params to This is likely caused by a IRQ mapping bug common in x86 BIOSes. PCI Chips behind a bus bridge are marked having different IRQs, even though they are all mapped to the same IRQ. The driver source has details, and the work-around. > tulip.o does nothing. Attempting to pass traffic after configuring an > interface results in (IIRC) neighbor table overflow messages Yup, that's not a very informative message. No my fault. > tulip.c:v0.92 4/17/2000 Written by Donald Becker > http://www.scyld.com/network/tulip.html > eth0: Digital DS21140 Tulip rev 34 at 0xc4853f80, 00:00:D1:1F:1E:34, IRQ 10. > eth0: EEPROM default media type Autosense. > eth0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. > eth0: MII transceiver #1 config 3100 status 7849 advertising 0101. > eth0: Advertising 01e1 on PHY 1, previously advertising 0101. This is the previously mentioned problem with the bogus initial type advertising. > mii-diag.c:v1.07 10/14/99 Donald Becker (becker@cesdis.gsfc.nasa.gov) > MII PHY #1 transceiver registers: > 3100 7849 2000 5c01 01e1 0000 0010 0000 .. > Basic mode status register 0x7849 ... 7849. > Link status: not established. No link beat. Try the reset above. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf Clusters / Linux Installations Annapolis MD 21403 From cbrown@denalics.net Wed, 2 Aug 2000 12:04:37 -0800 (AKDT) Date: Wed, 2 Aug 2000 12:04:37 -0800 (AKDT) From: Christopher E. Brown cbrown@denalics.net Subject: [tulip] Re: tulip.c vs ANA6944TX On Wed, 2 Aug 2000, Donald Becker wrote: > On Wed, 2 Aug 2000, Christopher E. Brown wrote: > > Subject: tulip.c vs ANA6944TX > > I no longer have access to one of these (they moved to Michigan with a large > cluster), but the versions I had worked fine in previous tests. These are REV C cards, seem to have come out in early to mid 1998 - EOL > > I have a very strange issue with the tulip 21140 based > > ANA6944TX quad 10/100 ethernet card. We were using the cards for some > > time, but as of late 1999 they stopped working with most MBs they were > > tried with, in one case with 2 identical Tyan S1590S boards, same rec, > > bios, setting, CPU and cards 1 worked one didn't. > > That's very curious. I think the earlier units were Rev A and Rev B. Cannot verify as I no longer have them. > > Symptoms are, board inits fine, no errors, everything looks correct, > > but NWAY autoneg does not function, sometimes port will be usable in > > 10Mbit HD, sometime repeated resets with tulip-diag will cause port to > > This is caused by the transceiver initial setting. > > eth0: Advertising 01e1 on PHY 1, previously advertising 0101. > This has the transceiver only advertising 100baseTx-HD at power-up! > The transceiver's pins are normally wired so that it advertises all > capabilities. > > Please try running 'mii-diag' from > http://www.scyld.com/diag/index.html > > Reset the transciver, and check its state > mii-diag eth0 -R; mii-diag eth0 > Advertise everything, and check the state > mii-diag eth0 -A 0x01e1; mii-diag eth0 > > > function for a short period. With some mainboards, ports 1 and 3 or 2 > > and 4 will function, but erraticly. Passing options= params to I have tulip-diag and mii-diag from said location. Have used both -r and -R, sometimes, after multiple resets and cable plug/unplug, it will report as an MII and and interface will go live. > This is likely caused by a IRQ mapping bug common in x86 BIOSes. > PCI Chips behind a bus bridge are marked having different IRQs, even though > they are all mapped to the same IRQ. > The driver source has details, and the work-around. I was under the impression the Rev A cards did this, but the Rev C and *maybe* Rev B cards do not hardwire the IRQs to that of the first iface. > > tulip.o does nothing. Attempting to pass traffic after configuring an > > interface results in (IIRC) neighbor table overflow messages > > Yup, that's not a very informative message. No my fault. I know, just trying to include everything while going into my 38th hour at work. > > tulip.c:v0.92 4/17/2000 Written by Donald Becker > > http://www.scyld.com/network/tulip.html > > eth0: Digital DS21140 Tulip rev 34 at 0xc4853f80, 00:00:D1:1F:1E:34, IRQ 10. > > eth0: EEPROM default media type Autosense. > > eth0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. > > eth0: MII transceiver #1 config 3100 status 7849 advertising 0101. > > eth0: Advertising 01e1 on PHY 1, previously advertising 0101. > > This is the previously mentioned problem with the bogus initial type > advertising. > > > mii-diag.c:v1.07 10/14/99 Donald Becker (becker@cesdis.gsfc.nasa.gov) > > MII PHY #1 transceiver registers: > > 3100 7849 2000 5c01 01e1 0000 0010 0000 > .. > > Basic mode status register 0x7849 ... 7849. > > Link status: not established. > > No link beat. Try the reset above. Have done so, mentioned above. No option or attempt with the tools results in a workable card. My understanding is that IRQ handing changed between revs, and that the A, B, and C rev cards all use slightly differend models of MII transciever. If you wanted to tackel this I should be able to loan you a Rev C ANA6944TX for at least a couple of months. --- As folks might have suspected, not much survives except roaches, and they don't carry large enough packets fast enough... --About the Internet and nuclear war. From thebs@theseus.com Thu, 3 Aug 2000 18:36:29 -0400 Date: Thu, 3 Aug 2000 18:36:29 -0400 From: Bryan -TheBS- Smith thebs@theseus.com Subject: [tulip] Linksys LNE100TX Version 4.1 hits the shelves ... any comments? Linksys LNE100TX Version 4.1 hits the shelves ... any comments? I just bought (4) LNE100TX Version 4.1 NIC cards. Have no idea what chipset is on-board. Linksys' site seems to have the same attitude (no info on Version 4.1, only 4.0). /proc filesystem keeps talking about an "Ethernet card with an unknown chipset". I tried tulip.c v0.91g-ppc to no avail (wouldn't load). I'm running kernels 2.2.16-8 (from RedHat Rawhide) and also tried 2.2.16-8.Ext3.4 (from VALinux). I also went ahead and downloaded Donald Becker's new "Netdriver package 2.0" with tulip.c v0.92 (and the required scan-pci and other modules) and installed it. FYI, the URL is: http://www.scyld.com/network/updates.html Still wasn't a go. I'm going to try the test v0.92h driver tomorrow. Another thing, the new card requires PCI 2.1 and I'm unsure whether or not my old test system is PCI 2.1-compliant (old i440FX chipset -- anyone know if i440FX supports 2.1?). I'm going to try it in a newer system tomorrow (VIA Pro/133A). Just wondering if anyone has any info on these new Version 4.1 cards? Hopefully they will work with Windows NT 4.0, but if I know NIC vendors, new cards are usually Windows 9x only (pisses me off). -- TheBS -- Bryan "TheBS" Smith CONTACT INFO *********************************************************** Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com) Email: mailto:thebs@theseus.com,b.j.smith@ieee.org Legal: http://www.SmithConcepts.com/legal.html From becker@scyld.com Fri, 4 Aug 2000 12:25:06 -0400 (EDT) Date: Fri, 4 Aug 2000 12:25:06 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Linksys LNE100TX Version 4.1 hits the shelves ... any comments? On Thu, 3 Aug 2000, Bryan -TheBS- Smith wrote: > Linksys LNE100TX Version 4.1 hits the shelves ... any comments? > > I just bought (4) LNE100TX Version 4.1 NIC cards. Have no idea what > chipset is on-board. Linksys' site seems to have the same attitude > (no info on Version 4.1, only 4.0). The 4.0 board use a ADMtek Centaur. The new NC200 boards use a ADMtek Comet. The Centaur/Comet support has been in the tulip driver since autumn '99. > /proc filesystem keeps talking about an "Ethernet card with an > unknown chipset". What was the exact PCI vendor and device ID? > I tried tulip.c v0.91g-ppc to no avail (wouldn't > load). I'm running kernels 2.2.16-8 (from RedHat Rawhide) and > also tried 2.2.16-8.Ext3.4 (from VALinux). I wouldn't expect the older 91g driver to work with even the 4.0 cards. > Another thing, the new card requires PCI 2.1 and I'm unsure whether > or not my old test system is PCI 2.1-compliant (old i440FX > chipset -- anyone know if i440FX supports 2.1?). I'm going to try > it in a newer system tomorrow (VIA Pro/133A). The 440FX isn't even PCI 2.0, but it was a good chipset and should work with most current PCI devices. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From cyber@phix-it.com Fri, 4 Aug 2000 17:09:16 -0400 (EDT) Date: Fri, 4 Aug 2000 17:09:16 -0400 (EDT) From: Chris Leavoy cyber@phix-it.com Subject: [tulip] odd bug in tulip driver The switch, and network cards lights report that they are using 100baseTx-FD. As for the drivers. i have no idea what is going on. The card is a Network Everywhere NC100 v2 (linksys) Below is an output of tulip-diag, notice that the driver is using half-duplex when it should be using full duplex (according to the switch and network card lights) tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xec00. Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex. Transmit started, Receive started, half-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 128. The Comet MAC registers are 01782000 ffff6b15 filter 8000000000000000. Below is an output of mii-diag, i have no idea what is going on here. mii-diag Using the default interface 'eth0'. Basic registers of MII PHY #1: 0000 0000 0000 0000 0000 0000 0000 ffff. Basic mode control register 0x0000: Auto-negotiation disabled, with Speed fixed at 10 mbps, half-duplex. Basic mode status register 0x0000 ... 0000. Link status: not established. Link partner information information is not exchanged when in fixed speed mode. Below is a cut from /proc/pci, the output is odd. Bus 0, device 3, function 0: Ethernet controller: Unknown vendor Unknown device (rev 17). Vendor id=1317. Device id=985. Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=64. Min Gnt=255.Max Lat=255. I/O at 0xec00 [0xec01]. Non-prefetchable 32 bit memory at 0xffaffc00 [0xffaffc00]. i did a series of tests... On the first test, (an ftp upload to the box with the tulip based card) the following messages were recorded in syslog kernel: eth0: Too much work during an interrupt, csr5=0xfc674050. kernel: eth0: Re-enabling interrupts, fc6fc855. kernel: eth0: Too much work during an interrupt, csr5=0xfc674050. kernel: eth0: Re-enabling interrupts, fc67c855. kernel: eth0: Too much work during an interrupt, csr5=0xfc69c0d0. kernel: eth0: Restarted Rx at 291103 / 291103. kernel: eth0: Re-enabling interrupts, fc67c855. kernel: eth0: Too much work during an interrupt, csr5=0xfc69c0d0. kernel: eth0: Restarted Rx at 291135 / 291135. kernel: eth0: Re-enabling interrupts, fc67c855. at this point, little was able to reach the box. so i restarted the interface (ifconfig eth0 down ; ifconfig eth0 up) and it started working again. I did this 10 times, and each time the same thing happened. After that, i performed a similar series of tests, transfering files from the box. and again, i got the same results as the first tests. I have tried this very same network card in my windows machine, and it operates just fine. Is this a bug in the tulip driver or is there something else wrong with my setup? Is anyone else having similar problems? Thanks, Chris Leavoy From lmulcahy@nyx.net Sat, 5 Aug 2000 13:56:14 -0600 (MDT) Date: Sat, 5 Aug 2000 13:56:14 -0600 (MDT) From: Larry Mulcahy lmulcahy@nyx.net Subject: [tulip] Linksys 10/100 Etherfast hangs Linux I have a Linksys Etherfast 10/100 LAN card. My OS is Red Hat 6.2. I have installed the updated drivers according to http://www.scyld.com/network/updates.html#rpm. Symptom is, the card and driver appear to be configured and working. I can ping other hosts on the LAN. However, if I try a large file transfer (288 MB), the transfer begins, then my system locks up and must be rebooted with the reset button. Possibly a buffer overrun? I'm a bit curious why the card is coming up 10bT. It's plugged into a 10/100 autosensing hub, and my other Linux box (the one I'm trying to do the file transfer from) comes up at 100bT. I have these line in /etc/conf.modules: alias eth0 tulip options tulip debug=6 These messages appear in /var/log/messages as the system boots up and after: Aug 5 11:36:58 ambient ifup: Determining IP information for eth0... Aug 5 11:36:59 ambient network: Bringing up interface eth0 succeeded Aug 5 11:37:06 ambient kernel: eth0: Lite-On PNIC-II rev 37 at 0xd08f0000, 00:A0:CC:E4:30:B2, IRQ 11. Aug 5 11:37:06 ambient kernel: eth0: N-Way autonegotiation status 45e1d0cc, 10baseT. Aug 5 11:38:02 ambient kernel: eth0: N-Way autonegotiation status 45e1d0cc, 10baseT. Aug 5 11:39:02 ambient kernel: eth0: N-Way autonegotiation status 45e1d0cc, 10baseT. Aug 5 11:40:02 ambient kernel: eth0: N-Way autonegotiation status 45e1d0cc, 10baseT. Aug 5 11:41:02 ambient kernel: eth0: N-Way autonegotiation status 45e1d0cc, 10baseT. Aug 5 11:42:02 ambient kernel: eth0: N-Way autonegotiation status 45e1d0cc, 10baseT. Aug 5 11:53:02 ambient kernel: eth0: N-Way autonegotiation status 45e1d0cc, 10baseT. Here's the output of 'ifconfig -a': eth0 Link encap:Ethernet HWaddr 00:A0:CC:E4:30:B2 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Here's the output of tulip-diag: tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Lite-On PNIC-II adapter at 0xe800. Port selection is 10mpbs-serial, half-duplex. Transmit started, Receive started, half-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 72. The NWay status register is 45e1d0cc. The current PNIC-II MAC address is 00:a0:cc:e4:30:b2 (a000a000 e4ccb230). The current PNIC-II WOL address is 00:a0:cc:e4:30:b2. Internal autonegotiation state is 'Negotiation complete'. Use '-a' or '-aa' to show device registers, '-e' to show EEPROM contents, -ee for parsed contents, or '-m' or '-mm' to show MII management registers. tulip-diag -a: tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Lite-On PNIC-II adapter at 0xe800. * A potential Tulip chip has been found, but it appears to be active. * Either shutdown the network, or use the '-f' flag to see all values. Port selection is 10mpbs-serial, half-duplex. Transmit started, Receive started, half-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 72. The NWay status register is 45e1d0cc. The current PNIC-II MAC address is 00:a0:cc:e4:30:b2 (a000a000 e4ccb230). The current PNIC-II WOL address is 00:a0:cc:e4:30:b2. tulip-diag -e: tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Lite-On PNIC-II adapter at 0xe800. Port selection is 10mpbs-serial, half-duplex. Transmit started, Receive started, half-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 72. The NWay status register is 45e1d0cc. The current PNIC-II MAC address is 00:a0:cc:e4:30:b2 (a000a000 e4ccb230). The current PNIC-II WOL address is 00:a0:cc:e4:30:b2. EEPROM size is 6. Ethernet MAC Station Address 00:a0:cc:e4:30:b2. Wake-On-LAN ID bytes a0:00:e4:cc:b2:30. PCI Subsystem IDs Vendor 11ad Device 01c0 Internal autonegotiation state is 'Negotiation complete'. tulip-diag -m: tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Lite-On PNIC-II adapter at 0xe800. Port selection is 10mpbs-serial, half-duplex. Transmit started, Receive started, half-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 72. The NWay status register is 45e1d0cc. The current PNIC-II MAC address is 00:a0:cc:e4:30:b2 (a000a000 e4ccb230). The current PNIC-II WOL address is 00:a0:cc:e4:30:b2. No MII transceivers found! Internal autonegotiation state is 'Negotiation complete'. Here's what cat /proc/pci shows. Note that both the LinkSys card and my Matrox graphics card have IRQ 11, however they are on a separate bus (Bus 1 = the AGP slot). PCI devices found: Bus 0, device 0, function 0: Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 3). Medium devsel. Fast back-to-back capable. Master Capable. Latency=16. Prefetchable 32 bit memory at 0xe0000000 [0xe0000008]. Bus 0, device 1, function 0: PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0). Medium devsel. Master Capable. No bursts. Min Gnt=12. Bus 0, device 7, function 0: ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 65). Medium devsel. Master Capable. No bursts. Bus 0, device 7, function 1: IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6). Medium devsel. Fast back-to-back capable. Master Capable. Latency=64. I/O at 0xe000 [0xe001]. Bus 0, device 7, function 3: Bridge: VIA Technologies VT 82C586B Apollo ACPI (rev 16). Medium devsel. Fast back-to-back capable. Bus 0, device 8, function 0: Ethernet controller: LiteOn Unknown device (rev 37). Vendor id=11ad. Device id=c115. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. Min Gnt=8.Max Lat=56. I/O at 0xe800 [0xe801]. Non-prefetchable 32 bit memory at 0xeb001000 [0xeb001000]. Bus 0, device 10, function 0: SCSI storage controller: Adaptec AIC-7871 (rev 0). Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=64. Min Gnt=8.Max Lat=8. I/O at 0xec00 [0xec01]. Non-prefetchable 32 bit memory at 0xeb000000 [0xeb000000]. Bus 1, device 0, function 0: VGA compatible controller: Matrox Millennium II AGP (rev 0). Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe8000000 [0xe8000008]. Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000]. Non-prefetchable 32 bit memory at 0xe5000000 [0xe5000000]. -- Larry Mulcahy lmulcahy@nyx.net lmulcahy@frii.com http://www.nyx.net/~lmulcahy/ http://www.geocities.com/Area51/Zone/9653/ PGP key at http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0xE6F89645 "I like Linux, but I don't have any part of my body pierced." Roland Latour From jalvarez@silverlink.net Sat, 5 Aug 2000 17:31:37 -0700 Date: Sat, 5 Aug 2000 17:31:37 -0700 From: Jim Alvarez jalvarez@silverlink.net Subject: [tulip] Linksys 100tx 4.1 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01BFFF03.01FCE940 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm trying to install this card in a Mandrake 7.0 system. I can get it = to see load. cat pci says Ethernet controller: Unknown vendor Unknown = Device Vendor is=3D1317 Device id=3D985. I have another Linksys 100tx = card I purchase sometime back. It installed perfectly with the verison = tulip that came with Mandrake 7.0. I'm added a secnod card for a router = for my DSL line. I downloaded the newest version of tulip.c and tried to compile it using = "gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall = -Wstrict-prototypes -O6 -c tulip.c '[ -f = /usr/include/linux/modversions.h ] && echo -DMODVERSIONS`=20 which I got from the Linksys readme.=20 This will not compile. It ends with an error; kern_compat.h:164 parse error before '0' kern_compat.h:168 warning: parameter names (without types) in function = declaration kern_compat.h168 conflicting types for 'mark_bh' /usr/include/asm/softirq.h:101: previous declaration of 'mark_bh' kern_compat.h:168:warning data definition has no type or storage class kern_compat.h:168: parse error before '}' gcc.cologcc: Internal complier error: program cc1 got fatal signal 11 What should I be doing to make this work are is it even possible. The = Linksys box is marked "tested with Linux" ------=_NextPart_000_0007_01BFFF03.01FCE940 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm trying to install this card in a = Mandrake 7.0=20 system. I can get it to see load. cat pci says Ethernet controller: = Unknown=20 vendor Unknown Device Vendor is=3D1317 Device id=3D985. I have another = Linksys 100tx=20 card I purchase sometime back. It = installed=20 perfectly with the verison tulip that came with Mandrake 7.0. I'm added = a secnod=20 card for a router for my DSL line.
 
I downloaded the newest version of = tulip.c and=20 tried to compile it using
 
"gcc -DMODULE -D__KERNEL__=20 -I/usr/src/linux/net/inet -Wall -Wstrict-prototypes -O6 -c = tulip.c '[=20 -f /usr/include/linux/modversions.h ] && echo=20 -DMODVERSIONS` 
 
which I got from the Linksys readme. =
 
This will not compile. It ends with an=20 error;
 
kern_compat.h:164 parse error before=20 '0'
kern_compat.h:168 warning: parameter = names (without=20 types) in function declaration
kern_compat.h168 conflicting types for=20 'mark_bh'
/usr/include/asm/softirq.h:101: = previous=20 declaration of 'mark_bh'
kern_compat.h:168:warning data = definition has no=20 type or storage class
kern_compat.h:168: parse error before=20 '}'
gcc.cologcc: Internal complier error: = program cc1=20 got fatal signal 11
 
What should I be doing to make this = work are is it=20 even possible. The Linksys box is marked "tested with = Linux"
 
------=_NextPart_000_0007_01BFFF03.01FCE940-- From thebs@theseus.com Fri, 4 Aug 2000 17:32:32 -0400 Date: Fri, 4 Aug 2000 17:32:32 -0400 From: Bryan -TheBS- Smith thebs@theseus.com Subject: [tulip] McQullian hacked 0.91g-ppc tulip.c driver for AN985 chipset -- WAS: Linksys LNE100TX Version 4.1 Re: Linksys LNE100TX Version 4.1 hits the shelves ... any comments? <- Hacked 0.91g-ppc driver On Fri, 04 Aug 2000, Donald Becker wrote: > The 4.0 board use a ADMtek Centaur. The new NC200 boards use a ADMtek Comet. > The Centaur/Comet support has been in the tulip driver since autumn '99. Is that your v0.92 driver in your Netdriver 2.0 package (with scan-pci, etc...)? I tried the v0.92 on that older system to no avail, although I was going to try the v0.92h test version next (but it could be me as I did everything via RPM commands). > What was the exact PCI vendor and device ID? Here's the /proc/pci entry (from a Apollo "694X" Pro/133A chipset): Bus 0, device 16, function 0: Ethernet controller: Unknown vendor Unknown device (rev 17). Vendor id=1317. Device id=985. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=32. Min Gnt=255.Max Lat=255. I/O at 0xdc00 [0xdc01]. Non-prefetchable 32 bit memory at 0xd9000000 [0xd9000000]. I take it Vendor id 1317 is ADMtek, and the 985 is the Centaur. > I wouldn't expect the older 91g driver to work with even the 4.0 cards. Yeah, I've pretty much tried to always get 2.0, but they're scarce now. The 0.91g[-ppc] drivers report "busy/unavailable" or some other message when I modprobe/insmod on Version 4.1 NIC-equiped systems. > The 440FX isn't even PCI 2.0, but it was a good chipset and > should work with most current PCI devices. Ack, I've always had issues. Not so much because of the chipset, but the combination of PCI cards. Although I definately want to get to playing with your Netdriver 2.0 setup, for now, I am using Jim McQuillan's (mailto:jam@McQuil.com) hacked 0.91g-ppc driver. He merged some blocks from the existing AN981 section code with some others and it works fine for me. I guess it was just an identification issue? Don't know if Jim posted his hacked 0.91g-ppc driver to the list before, but I will post it (~30KB gzip'ed) to the list for the archives if he hasn't. Thanx everyone for your help! -- TheBS -- Bryan "TheBS" Smith CONTACT INFO *********************************************************** Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com) Email: mailto:thebs@theseus.com,b.j.smith@ieee.org Legal: http://www.SmithConcepts.com/legal.html From becker@scyld.com Sun, 6 Aug 2000 19:17:42 -0400 (EDT) Date: Sun, 6 Aug 2000 19:17:42 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Re: McQullian hacked 0.91g-ppc tulip.c driver for AN985 chipset -- WAS: Linksys LNE100TX Version 4.1 On Fri, 4 Aug 2000, Bryan -TheBS- Smith wrote: > Re: Linksys LNE100TX Version 4.1 hits the shelves ... any comments? <- Hacked 0.91g-ppc driver > Ethernet controller: Unknown vendor Unknown device (rev 17). > Vendor id=1317. Device id=985. That's a Centaur/P. (The PCI version. The CardBus Centaur/C is 0x1985.) It should be detected by and work with the v92 driver, although there are a few tweaks in the latest test version. > Although I definately want to get to playing with your Netdriver > 2.0 setup, for now, I am using Jim McQuillan's > (mailto:jam@McQuil.com) hacked 0.91g-ppc driver. He merged some > blocks from the existing AN981 section code with some others and it > works fine for me. I guess it was just an identification issue? No! It's more than just an identification issue. The Comet/Centaur chip isn't exactly like other tulip-like chips. (Not that any of them are like the others.) Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From jalvarez@silverlink.net Sun, 6 Aug 2000 16:13:20 -0700 Date: Sun, 6 Aug 2000 16:13:20 -0700 From: Jim Alvarez jalvarez@silverlink.net Subject: [tulip] Linksys 100tx 4.1 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01BFFFC1.3C9A9D40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm trying to install this card in a Mandrake 7.0 system. I can get it = to see load. cat pci says Ethernet controller: Unknown vendor Unknown = Device Vendor is=3D1317 Device id=3D985. I have another Linksys 100tx = card I purchase sometime back. It installed perfectly with the verison = tulip that came with Mandrake 7.0. I'm added a secnod card for a router = for my DSL line. =20 I downloaded the newest version of tulip.c and tried to compile it using = =20 "gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall = -Wstrict-prototypes -O6 -c tulip.c '[ -f = /usr/include/linux/modversions.h ] && echo -DMODVERSIONS`=20 =20 which I got from the Linksys readme.=20 =20 This will not compile. It ends with an error; =20 kern_compat.h:164 parse error before '0' kern_compat.h:168 warning: parameter names (without types) in function = declaration kern_compat.h168 conflicting types for 'mark_bh' /usr/include/asm/softirq.h:101: previous declaration of 'mark_bh' kern_compat.h:168:warning data definition has no type or storage class kern_compat.h:168: parse error before '}' gcc.cologcc: Internal complier error: program cc1 got fatal signal 11 =20 What should I be doing to make this work or is it even possible. The = Linksys box is marked "tested with Linux" =20 ------=_NextPart_000_0007_01BFFFC1.3C9A9D40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm trying to install this card in a = Mandrake 7.0=20 system. I can get it to see load. cat pci says Ethernet controller: = Unknown=20 vendor Unknown Device Vendor is=3D1317 Device id=3D985. I have another = Linksys 100tx=20 card I purchase sometime back. It installed perfectly with the verison = tulip=20 that came with Mandrake 7.0. I'm added a secnod card for a router for my = DSL=20 line.
 
I downloaded the newest version of tulip.c and tried = to=20 compile it using
 
"gcc -DMODULE -D__KERNEL__=20 -I/usr/src/linux/net/inet -Wall -Wstrict-prototypes -O6 -c tulip.c '[ -f = /usr/include/linux/modversions.h ] && echo -DMODVERSIONS`=20
 
which I got from the Linksys readme.
 
This = will not=20 compile. It ends with an error;
 
kern_compat.h:164 parse = error=20 before '0'
kern_compat.h:168 warning: parameter names (without types) = in=20 function declaration
kern_compat.h168 conflicting types for=20 'mark_bh'
/usr/include/asm/softirq.h:101: previous declaration of=20 'mark_bh'
kern_compat.h:168:warning data definition has no type or = storage=20 class
kern_compat.h:168: parse error before '}'
gcc.cologcc: = Internal=20 complier error: program cc1 got fatal signal 11
 
What should = I be=20 doing to make this work or is it even possible. The Linksys box is = marked=20 "tested with Linux"
 
------=_NextPart_000_0007_01BFFFC1.3C9A9D40-- From b.j.smith@ieee.org Sun, 06 Aug 2000 20:15:46 -0400 Date: Sun, 06 Aug 2000 20:15:46 -0400 From: Bryan J. Smith b.j.smith@ieee.org Subject: [tulip] Re: McQullian hacked 0.91g-ppc tulip.c driver for AN985 chipset --WAS: Linksys LNE100TX Version 4.1 Donald Becker wrote: > No! It's more than just an identification issue. The Comet/Centaur chip > isn't exactly like other tulip-like chips. (Not that any of them are like > the others.) Hmmm, better? worse? How the CPU utilization (i.e. would you use this in a server)? Thanx in advance Don ... -- TheBS -- Bryan "TheBS" Smith, Engineer CONTACT INFO *********************************************************** Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com) Email: mailto:b.j.smith@ieee.org,thebs@theseus.com Legal: http://www.SmithConcepts.com/legal.html From becker@scyld.com Mon, 7 Aug 2000 00:23:25 -0400 (EDT) Date: Mon, 7 Aug 2000 00:23:25 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Re: McQullian hacked 0.91g-ppc tulip.c driver for AN985 chipset --WAS: Linksys LNE100TX Version 4.1 On Sun, 6 Aug 2000, Bryan J. Smith wrote: > > No! It's more than just an identification issue. The Comet/Centaur chip > > isn't exactly like other tulip-like chips. (Not that any of them are like > > the others.) > > Hmmm, better? worse? How the CPU utilization (i.e. would you use > this in a server)? We are using them in our test cluster. They should be nominally about the same as a real Tulip: - Recieved frames must be put into aligned buffers, which mis-aligns the IP header. - There is no UDP/TCP/IP checksumming on the chip The differences are in the media selection and EEPROM layout. An advantage of a single-chip implementation is that is only one type of transceiver connection to test against, unlike the 21140 and 21143 which had hundreds of variations. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From chris_bangun@bigpond.com Mon, 7 Aug 2000 17:27:50 +1000 Date: Mon, 7 Aug 2000 17:27:50 +1000 From: Christopher Bangun chris_bangun@bigpond.com Subject: [tulip] tulip driver for ANA 62044 This is a multi-part message in MIME format. ------=_NextPart_000_00A5_01C00094.CFD3ADD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Does anyone have ever used the tulip driver for quad ethernet adaptec ( = ANA 62044 ) on redhat linux 6.2, i386? Please advice what product of = quad ethernet that tulip driver can support. Regards, Christopher B ------=_NextPart_000_00A5_01C00094.CFD3ADD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Does anyone have ever used the tulip=20 driver for quad ethernet adaptec ( ANA 62044 ) on redhat linux 6.2, = i386?=20 Please advice what product of quad ethernet that tulip driver can=20 support.
 
 
 
Regards,
 
Christopher = B
------=_NextPart_000_00A5_01C00094.CFD3ADD0-- From ksiadaczka@sympatico.ca Mon, 07 Aug 2000 11:59:19 -0400 Date: Mon, 07 Aug 2000 11:59:19 -0400 From: Claude Siadaczka ksiadaczka@sympatico.ca Subject: [tulip] Tulip compile problems Hello Everyone: I have a major problem I cannot solve. I try and compile the tulip.c driver or the pci-scan.c driver and I run into the following problem. It will not compile and gives me errors something like this: /.../.../modversions.h: linux/modules/serial.ver: no such file or directory /.../.../modversions.h: linux/modules/slhc.ver no such file or directory /.../.../modversions.h: linux/modules/vfatfs.ver no such file or directory /.../.../modversions.h: linux/modules/ppp.ver no such file or directory /.../.../modversions.h: linux/modules/nls.ver no such file or directory /.../.../modversions.h: linux/modules/netsyms.ver no such file or directory I finally end up with about 30 of exactly these types of errors. Anyway I do not compile with the gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c tulip.c command. I searched the whole web and cannot find anything on this topic. Claudius. Thanks. From me@ame.de Mon, 07 Aug 2000 19:03:39 +0200 Date: Mon, 07 Aug 2000 19:03:39 +0200 From: Matthias Eichler me@ame.de Subject: [tulip] Probs with D-Link DFE-570TX Hi List, we have a lot of problems with the D-Link DFE-570TX NIC. This card uses the tulip-driver and is working well so far. Unfortunately under haevy load the CRC errors and Collissions are raising too high. But forcing the card to 100MBit-FD failed. Does anybody knows how to force this card to 100MBTX-FD?!? Thx, Matthias Eichler +======================================================================+ = AME Aigner Media & Entertainment GmbH <> Multimedia - Radio & TV = ======================================================================== == Bavariaring 8 Matthias E I C H L E R == == D-80336 Muenchen Technical Supervisor == == == == Tel:[+49] 089-427 05 #330 eMail: me@ame.de == == Fax:[+49] 089-427 05 #400 http://ame.de == ======================================================================== = www.NetRadio.de - www.StreaMobil.de - www.netNewsLetter.de = +======================================================================+ From bricc@gte.net Mon, 07 Aug 2000 22:35:19 -0400 Date: Mon, 07 Aug 2000 22:35:19 -0400 From: root bricc@gte.net Subject: [tulip] Linksys LNE100TX v4.1 RPM Compile Problem I'm relatively new to Linux, so I really appreciate any help that you may have to offer. Anyway, I am running RedHat 6.2 and I cannot seem to get my Linksys LNE100TX NIC to work. When attempting to use the tulip.c driver that was standard with RH6.2, I get a "device is busy" message. So, I am attempting to upgrade to the latest version of tulip.c. I've attempted use both the RPM format as well as the stand alone module, but I get errors on all sides. When attempting to use the RPM, I get to the rpm -bb command and it fails with the following message: "make: *** no rule to make target `/usr/src/linux/drivers/net/8390.h' , needed by `ne2k-pci.o'. Stop. Bad exit status from /var/tmp/rpm-tmp.xxxxx" When attempting to compile tulip.c alone I get all kinds of warning messages, but no tulip.o file. Thanks for your help, Brian Hanks From randy.l.phillips@worldnet.att.net Mon, 07 Aug 2000 22:52:16 -0600 Date: Mon, 07 Aug 2000 22:52:16 -0600 From: Randy Phillips randy.l.phillips@worldnet.att.net Subject: [tulip] Linksys EtherFast v4 10/100 PCI unresolved symbols I am trying to use the tulip (v0.92h) driver as a module along with pci-scan.
The os is RedHat 6.1 (2.2.12-20).
The source compiles with no errors.
insmod pci-scan.o (which I do before tulip) has no problems but insmod tulip.o reports:

./tulip.o: unresolved symbol eth_copy_and_sum_R560538ed
./tulip.o: unresolved symbol eth_type_trans_R8c9421e3
./tulip.o: unresolved symbol netif_rx_R6b90c897
./tulip.o: unresolved symbol dev_close_R62c49c1e
./tulip.o: unresolved symbol __kfree_skb_R048975be
./tulip.o: unresolved symbol init_etherdev_Re5166df1
./tulip.o: unresolved symbol alloc_skb_R74818d15
./tulip.o: unresolved symbol unregister_netdev_R6600a37d
./tulip.o: unresolved symbol skb_over_panic_R3f363246

Any suggestions would be greatly appreciated.
 From becker@scyld.com Tue, 8 Aug 2000 00:17:58 -0400 (EDT) Date: Tue, 8 Aug 2000 00:17:58 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Linksys EtherFast v4 10/100 PCI unresolved symbols On Mon, 7 Aug 2000, Randy Phillips wrote: > I am trying to use the tulip (v0.92h) driver as a module along with > pci-scan. > The os is RedHat 6.1 (2.2.12-20). > The source compiles with no errors. > insmod pci-scan.o (which I do before tulip) has no problems but insmod > tulip.o reports: > > ./tulip.o: unresolved symbol eth_copy_and_sum_R560538ed > ./tulip.o: unresolved symbol eth_type_trans_R8c9421e3 Kernel version mismatch. Check that you are loading the module you expect to. Note the difference between: insmod tulip # loads a module from /lib/modules/*/net/tulip.o insmod tulip.o # loads the module ./tulip.o Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From bricc@gte.net Tue, 8 Aug 2000 07:55:48 -0400 Date: Tue, 8 Aug 2000 07:55:48 -0400 From: Brian Hanks bricc@gte.net Subject: [tulip] Linksys LNE100TX Driver Problems This is a multi-part message in MIME format. ------=_NextPart_000_0107_01C0010E.10607260 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I apologize for my previous message where my user name showed up as=20 "root". I had just set up the machine and did not change all of the = necessary=20 Netscape Mail setttings. Please let me know if you need more details. Below is my previous = message: I'm relatively new to Linux, so I really appreciate any help that you may have to offer. Anyway, I am running RedHat 6.2 and I cannot seem to get my Linksys LNE100TX NIC to work. When attempting to use the tulip.c driver that was standard with RH6.2, I get a "device is busy" message. So, I am attempting to upgrade to the latest version of tulip.c. I've attempted use both the RPM format as well as the stand alone module, but I get errors on all sides. When attempting to use the RPM, I get to the rpm -bb command and it fails with the following message: "make: *** no rule to make target `/usr/src/linux/drivers/net/8390.h' , needed by `ne2k-pci.o'. Stop. Bad exit status from /var/tmp/rpm-tmp.xxxxx" When attempting to compile tulip.c alone I get all kinds of warning messages, but no tulip.o file. Thanks for your help, Brian Hanks ------=_NextPart_000_0107_01C0010E.10607260 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I apologize for my previous message where my = user name=20 showed up as
"root".  I had just set up the machine and = did not=20 change all of the necessary
Netscape Mail setttings.
 
Please let me know if you need more = details.  Below=20 is my previous message:
 
 
I'm relatively new to Linux, so I really = appreciate any=20 help that you
may have to offer.

Anyway, I am running RedHat = 6.2 and I=20 cannot seem to get my Linksys
LNE100TX NIC to work.  When = attempting to=20 use the tulip.c driver that
was standard with RH6.2, I get a "device = is busy"=20 message.  So, I am
attempting to upgrade to the latest version = of=20 tulip.c.  I've attempted
use both the RPM format as well as the = stand=20 alone module, but I get
errors on all sides.

When attempting = to use=20 the RPM, I get to the rpm -bb command and it
fails with the following = message:
"make: *** no rule to make target=20 `/usr/src/linux/drivers/net/8390.h' ,
needed by `ne2k-pci.o'. = Stop.
Bad=20 exit status from /var/tmp/rpm-tmp.xxxxx"

When attempting to = compile=20 tulip.c alone I get all kinds of warning
messages, but no tulip.o=20 file.

Thanks for your help,
Brian = Hanks
------=_NextPart_000_0107_01C0010E.10607260-- From jpschewe@eggplant.mtu.net 08 Aug 2000 07:54:15 -0500 Date: 08 Aug 2000 07:54:15 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Linksys LNE100TX Driver Problems Do you have the kernel headers installed? Look in /usr/src/linux and see if there's anything there. You'll needa kernel-headers rpm for that. "Brian Hanks" writes: > > I'm relatively new to Linux, so I really appreciate any help that you > may have to offer. > Anyway, I am running RedHat 6.2 and I cannot seem to get my Linksys > LNE100TX NIC to work.  When attempting to use the tulip.c driver that > was standard with RH6.2, I get a "device is busy" message.  So, I am > attempting to upgrade to the latest version of tulip.c.  I've attempted > use both the RPM format as well as the stand alone module, but I get > errors on all sides. > When attempting to use the RPM, I get to the rpm -bb command and it > fails with the following message: > "make: *** no rule to make target `/usr/src/linux/drivers/net/8390.h' , > needed by `ne2k-pci.o'. Stop. > Bad exit status from /var/tmp/rpm-tmp.xxxxx" > When attempting to compile tulip.c alone I get all kinds of warning > messages, but no tulip.o file. > Thanks for your help, > Brian Hanks > -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From thebs@theseus.com Tue, 8 Aug 2000 09:17:20 -0400 Date: Tue, 8 Aug 2000 09:17:20 -0400 From: Bryan -TheBS- Smith thebs@theseus.com Subject: [tulip] Re: Linksys LNE100TX Driver Problems <- Possible issue On Tue, 08 Aug 2000, Brian Hanks wrote: > When attempting to use the RPM, I get to the rpm -bb command and it > fails with the following message: > "make: *** no rule to make target `/usr/src/linux/drivers/net/8390.h' , > needed by `ne2k-pci.o'. Stop. > Bad exit status from /var/tmp/rpm-tmp.xxxxx" > > When attempting to compile tulip.c alone I get all kinds of warning > messages, but no tulip.o file. Some kernels (notably recent RedHat kernel RPMs) expect the asm and linux include files to be in /usr/include to compile. Type: cd /usr/include ln -s ../src/linux/include/asm . ln -s ../src/linux/include/linux . To setup symlinks to your kernel's include files. [ Not sure if there is your issue or not ] -- TheBS -- Bryan "TheBS" Smith CONTACT INFO *********************************************************** Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com) Email: mailto:thebs@theseus.com,b.j.smith@ieee.org Legal: http://www.SmithConcepts.com/legal.html From kaos@ocs.com.au Tue, 08 Aug 2000 23:57:17 +1000 Date: Tue, 08 Aug 2000 23:57:17 +1000 From: Keith Owens kaos@ocs.com.au Subject: [tulip] Re: Linksys LNE100TX Driver Problems <- Possible issue On Tue, 8 Aug 2000 09:17:20 -0400, Bryan -TheBS- Smith wrote: >Some kernels (notably recent RedHat kernel RPMs) expect the asm and >linux include files to be in /usr/include to compile. Type: > > cd /usr/include > ln -s ../src/linux/include/asm . > ln -s ../src/linux/include/linux . You realize that Linus is going to come round to your place and make you use Windows now? There has just been a big argument about these symlinks on l-k and Linus says "NO WAY". /usr/include/asm and /usr/include/linux have to exist but they should not be symlinks to any old kernel. They should be real directories containing the headers that glibc was built with. It is the only way to avoid random compile problems when the kernel changes. The symlinks were needed years ago but not with current glibc. If your distribution does not ship real /usr/include/asm and /usr/include/linux directories, complain to your distributor. Don't compound the problem by adding the obsolete symlinks. Linus has spoken. From Andreas.Schrimpf@Physik.Uni-Marburg.DE Tue, 08 Aug 2000 16:18:34 +0200 Date: Tue, 08 Aug 2000 16:18:34 +0200 From: Dr. Andreas Schrimpf Andreas.Schrimpf@Physik.Uni-Marburg.DE Subject: [tulip] Problems with ANA6944A 4port card This is a multi-part message in MIME format. --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, I am fighting since two weeks to get the Adaptec 4port NIC ANA6944A/TX running with SuSE Linux 6.4. The problems: 1) With only the Adaptec card in the computer everyone of the 4 ports will run, if I deactivate the others, but never all 4 are working all together. In the later case somehow networking seems to be routed to the first port, sometimes to the first and to the last (checked by "netstat -aiu" and disconnecting the twisted pair cables) even though all 4 ports (MAC addresses) have a separat IP address which I used for ftp and ping tests. 2) Including a 3Com 900b card leeds to a re-routing to this port and a noticeable drop in performance. The configuration: mainboard: ASUS PSB-S rev 1.03 Adaptec ANA6944A/TX 4port NIC, no FAB 1683707-00 REV C with following chip numbers: label on one chip: ANA-6944A/TX 1697400 A 9940 4 * digital 21140-AF, 21-43864-04 DEC 1996, DC1064C S 9918 JL5234 4 * MS9939AD DP83840AVCE 4 * ES9928AD DP83223V For test-configuration: 3Com 900b-Combo network connection to a catalyst switch with fixed port configuration, i.e. 4 times 100 MHz, full duplex and for testing (3Com 900b Combo) 10 MHz, half duplex. Drivers are compiled as modules, I got the latest driver-update package. Status of the machine: I copied several status messages. The machine was booted with the 3Com card as eth0, and eht1 and eth4 activated. You will find: file "raid" contains a copy of "/etc/modules" and "/var/log/messages" file "ifconfig_tab" the answer of "ifconfig" file "rout_tab" the answer of "route" files "proc_int, .._io, .._pci" the answers of "cat /proc/interrups", "cat /proc/ioports" and "cat /proc/pci" file "tulip_diag-ee" the answer of "tulip-diag -ee" files "mii-diag_ethx" the answers of "mii-diag ethx" with x=1,2,3,4 I hope, someone can give me some hints to get the card working fine. Best Andreas -- ---------------------------------------------------------------------- Priv. Doz. Dr. Andreas Schrimpf Philipps-Universität Marburg Fachbereich Physik Mainzer Gasse 33 D-35032 Marburg Tel: 49-(0)6421-28-21338 Fax: 49-(0)6421-28-27076 EMail: Andreas.Schrimpf@Physik.Uni-Marburg.DE ---------------------------------------------------------------------- --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="raid" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="raid" /etc/modules alias eth0 3c90x options 3c90x media_select=3 alias eth1 tulip alias eth2 tulip alias eth3 tulip alias eth4 tulip options tulip debug=2 options=14,14,14,14 full_duplex=1,1,1,1 /var/log/messages Aug 8 08:31:10 pcraid kernel: 3Com 3c90x Version 1.0.0i 1999 --------------------------------- Aug 8 08:31:10 pcraid kernel: tulip.c:v0.92 4/17/2000 Written by Donald Becker Aug 8 08:31:10 pcraid kernel: http://www.scyld.com/network/tulip.html Aug 8 08:31:10 pcraid kernel: eth1: Digital DS21140 Tulip rev 34 at 0xd003c000, 00:00:D1:1E:96:AD, IRQ 11. Aug 8 08:31:10 pcraid kernel: eth1: EEPROM default media type Autosense. Aug 8 08:31:10 pcraid kernel: eth1: MII interface PHY 0, setup/reset sequences 1/1 long, capabilities 78 00. Aug 8 08:31:10 pcraid kernel: eth1: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. Aug 8 08:31:10 pcraid kernel: eth1: Using media type MII, CSR12 is 00. Aug 8 08:31:10 pcraid kernel: eth1: MII transceiver #1 config 3100 status 7849 advertising 0101. Aug 8 08:31:10 pcraid kernel: eth1: Advertising 0100 on PHY 1, previously advertising 0101. Aug 8 08:31:10 pcraid kernel: eth2: Digital DS21140 Tulip rev 34 at 0xd003e000, EEPROM not present, 00:00:D1:1E:96:AE, IRQ 11. Aug 8 08:31:10 pcraid kernel: eth2: Controller 1 of multiport board. Aug 8 08:31:10 pcraid kernel: eth2: EEPROM default media type Autosense. Aug 8 08:31:10 pcraid kernel: eth2: MII interface PHY 0, setup/reset sequences 1/1 long, capabilities 78 00. Aug 8 08:31:10 pcraid kernel: eth2: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. Aug 8 08:31:10 pcraid kernel: eth2: Using media type MII, CSR12 is 00. Aug 8 08:31:10 pcraid kernel: eth2: MII transceiver #1 config 3100 status 7849 advertising 0101. Aug 8 08:31:10 pcraid kernel: eth2: Advertising 0100 on PHY 1, previously advertising 0101. Aug 8 08:31:10 pcraid kernel: eth3: Digital DS21140 Tulip rev 34 at 0xd0040000, EEPROM not present, 00:00:D1:1E:96:AF, IRQ 11. Aug 8 08:31:10 pcraid kernel: eth3: Controller 2 of multiport board. Aug 8 08:31:10 pcraid kernel: eth3: EEPROM default media type Autosense. Aug 8 08:31:10 pcraid kernel: eth3: MII interface PHY 0, setup/reset sequences 1/1 long, capabilities 78 00. Aug 8 08:31:10 pcraid kernel: eth3: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. Aug 8 08:31:10 pcraid kernel: eth3: Using media type MII, CSR12 is 00. Aug 8 08:31:10 pcraid kernel: eth3: MII transceiver #1 config 3100 status 7849 advertising 0101. Aug 8 08:31:10 pcraid kernel: eth3: Advertising 0100 on PHY 1, previously advertising 0101. Aug 8 08:31:10 pcraid kernel: eth4: Digital DS21140 Tulip rev 34 at 0xd0042000, EEPROM not present, 00:00:D1:1E:96:B0, IRQ 11. Aug 8 08:31:10 pcraid kernel: eth4: Controller 3 of multiport board. Aug 8 08:31:10 pcraid kernel: eth4: EEPROM default media type Autosense. Aug 8 08:31:10 pcraid kernel: eth4: MII interface PHY 0, setup/reset sequences 1/1 long, capabilities 78 00. Aug 8 08:31:10 pcraid kernel: eth4: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. Aug 8 08:31:10 pcraid kernel: eth4: Using media type MII, CSR12 is 00. Aug 8 08:31:10 pcraid kernel: eth4: MII transceiver #1 config 3100 status 7849 advertising 0101. Aug 8 08:31:10 pcraid kernel: eth4: Advertising 0100 on PHY 1, previously advertising 0101. ---------------------------- Aug 8 08:31:10 pcraid kernel: eth1: tulip_open() irq 11. Aug 8 08:31:10 pcraid kernel: eth1: Using user-specified media MII 100baseTx-FDX. Aug 8 08:31:10 pcraid kernel: eth1: Advertising 0100 on MII 1. Aug 8 08:31:10 pcraid kernel: eth1: Using media type MII, CSR12 is 00. Aug 8 08:31:10 pcraid kernel: eth4: tulip_open() irq 11. Aug 8 08:31:10 pcraid kernel: eth4: Using user-specified media MII 100baseTx-FDX. Aug 8 08:31:10 pcraid kernel: eth4: Advertising 0100 on MII 1. Aug 8 08:31:10 pcraid kernel: eth4: Using media type MII, CSR12 is 00. ------------------ --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="ifconfig_tab" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ifconfig_tab" eth0 Link encap:Ethernet HWaddr 00:10:5A:3C:2A:A0 inet addr:137.248.131.137 Bcast:137.248.131.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1 RX packets:18019 errors:4040 dropped:0 overruns:0 frame:4040 TX packets:8241 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:10 Base address:0xb000 eth1 Link encap:Ethernet HWaddr 00:00:D1:1E:96:AD inet addr:137.248.131.202 Bcast:137.248.131.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0xc000 eth4 Link encap:Ethernet HWaddr 00:00:D1:1E:96:B0 inet addr:137.248.131.205 Bcast:137.248.131.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:414 errors:0 dropped:0 overruns:0 frame:0 TX packets:414 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="route_tab" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="route_tab" Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 137.248.131.0 * 255.255.255.0 U 0 0 0 eth0 137.248.131.0 * 255.255.255.0 U 0 0 0 eth1 137.248.131.0 * 255.255.255.0 U 0 0 0 eth4 loopback * 255.0.0.0 U 0 0 0 lo default cirz070423.HRZ. 0.0.0.0 UG 0 0 0 eth0 --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="proc_int" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="proc_int" CPU0 0: 410454 XT-PIC timer 1: 2 XT-PIC keyboard 2: 0 XT-PIC cascade 5: 3506 XT-PIC aic7xxx 8: 2 XT-PIC rtc 10: 25703 XT-PIC eth0 11: 8 XT-PIC eth1, eth4 12: 0 XT-PIC PS/2 Mouse 13: 1 XT-PIC fpu 15: 45 XT-PIC aic7xxx NMI: 0 --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="proc_io" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="proc_io" 0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 02f8-02ff : serial(auto) 03c0-03df : vga+ 03f8-03ff : serial(auto) b000-b07f : 3Com EtherLink PCI NIC b400-b4fe : aic7xxx d000-d0fe : aic7xxx d003c000-d003c07f : eth1 d003e000-d003e07f : eth2 d0040000-d004007f : eth3 d0042000-d004207f : eth4 --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="proc_pci" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="proc_pci" PCI devices found: Bus 0, device 0, function 0: Host bridge: Intel 440BX - 82443BX Host (rev 3). Medium devsel. Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe4000000 [0xe4000008]. Bus 0, device 1, function 0: PCI bridge: Intel 440BX - 82443BX AGP (rev 3). Medium devsel. Master Capable. Latency=64. Min Gnt=128. Bus 0, device 4, function 0: ISA bridge: Intel 82371AB PIIX4 ISA (rev 2). Medium devsel. Fast back-to-back capable. Master Capable. No bursts. Bus 0, device 4, function 1: IDE interface: Intel 82371AB PIIX4 IDE (rev 1). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. I/O at 0xd800 [0xd801]. Bus 0, device 4, function 2: USB Controller: Intel 82371AB PIIX4 USB (rev 1). Medium devsel. Fast back-to-back capable. IRQ 5. Master Capable. Latency=32. I/O at 0xd400 [0xd401]. Bus 0, device 4, function 3: Bridge: Intel 82371AB PIIX4 ACPI (rev 2). Medium devsel. Fast back-to-back capable. Bus 0, device 6, function 0: SCSI storage controller: Adaptec AIC-7890/1 (rev 0). Medium devsel. Fast back-to-back capable. BIST capable. IRQ 5. Master Capable. Latency=32. Min Gnt=39.Max Lat=25. I/O at 0xd000 [0xd001]. Non-prefetchable 64 bit memory at 0xe3000000 [0xe3000004]. Bus 0, device 9, function 0: VGA compatible controller: ATI Mach64 GT (Rage II) (rev 154). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. Min Gnt=8. Non-prefetchable 32 bit memory at 0xe2000000 [0xe2000000]. I/O at 0xb800 [0xb801]. Non-prefetchable 32 bit memory at 0xe1800000 [0xe1800000]. Bus 0, device 10, function 0: SCSI storage controller: Adaptec AHA-2940U2 (rev 0). Medium devsel. Fast back-to-back capable. BIST capable. IRQ 15. Master Capable. Latency=32. Min Gnt=39.Max Lat=25. I/O at 0xb400 [0xb401]. Non-prefetchable 64 bit memory at 0xe1000000 [0xe1000004]. Bus 0, device 11, function 0: Ethernet controller: 3Com Unknown device (rev 4). Vendor id=10b7. Device id=9005. Medium devsel. IRQ 10. Master Capable. Latency=32. Min Gnt=10.Max Lat=48. I/O at 0xb000 [0xb001]. Non-prefetchable 32 bit memory at 0xe0800000 [0xe0800000]. Bus 0, device 12, function 0: PCI bridge: DEC DC21152 (rev 3). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. Min Gnt=4. Bus 2, device 4, function 0: Ethernet controller: DEC DC21140 (rev 34). Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=32. Min Gnt=20.Max Lat=40. I/O at 0xa800 [0xa801]. Non-prefetchable 32 bit memory at 0xe0000000 [0xe0000000]. Bus 2, device 5, function 0: Ethernet controller: DEC DC21140 (rev 34). Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=20.Max Lat=40. I/O at 0xa400 [0xa401]. Non-prefetchable 32 bit memory at 0xdf800000 [0xdf800000]. Bus 2, device 6, function 0: Ethernet controller: DEC DC21140 (rev 34). Medium devsel. Fast back-to-back capable. IRQ 15. Master Capable. Latency=32. Min Gnt=20.Max Lat=40. I/O at 0xa000 [0xa001]. Non-prefetchable 32 bit memory at 0xdf000000 [0xdf000000]. Bus 2, device 7, function 0: Ethernet controller: DEC DC21140 (rev 34). Medium devsel. Fast back-to-back capable. IRQ 5. Master Capable. Latency=32. Min Gnt=20.Max Lat=40. I/O at 0x9800 [0x9801]. Non-prefetchable 32 bit memory at 0xde800000 [0xde800000]. --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="tulip_diag-ee" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="tulip_diag-ee" tulip-diag.c:v1.19 10/2/99 Donald Becker (becker@cesdis.gsfc.nasa.gov) Index #1: Found a Digital DS21140 Tulip adapter at 0xa800. Port selection is MII, full-duplex. Transmit started, Receive started, full-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 128. EEPROM size is 6. PCI Subsystem IDs, vendor 1109, device 2400. CardBus Information Structure at offset 00000000. Ethernet MAC Station Address 00:00:D1:1E:96:AD. EEPROM transceiver/media description for the Digital DS21140 Tulip chip. Leaf node at offset 40, default media type 0800 (Autosense). CSR12 direction setting bits 0x3f. 1 transceiver description blocks: Media MII, block type 1, length 14. MII interface PHY 0 (media type 11). 21140 MII Reset sequence is 2 words: 01 00. 21140 MII initialization sequence is 1 words: 00. Media capabilities are 7800, advertising 01e1. Full-duplex map 5000, Threshold map 1800. EEPROM contents: 1109 2400 0000 0000 0000 0000 0000 0000 0005 0403 0000 1ed1 ad96 2804 0500 0028 2806 0700 0028 0000 0800 013f 018e 0100 0200 0001 7800 01e0 5000 1800 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0724 c1a2 ID block CRC 0x05 (vs. 0x05). Full contents CRC 0xc1a2 (read as 0xc1a2). MII PHY found at address 1, status 0x7849. MII PHY #1 transceiver registers: 3100 7849 2000 5c01 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00a0 0000 0000 0001 8060 8020 0c61 0000 1000 a3b9 0084 4205 001b. Index #2: Found a Digital DS21140 Tulip adapter at 0xa400. Port selection is 10mpbs-serial, half-duplex. Transmit stopped, Receive stopped, half-duplex. The Rx process state is 'Stopped'. The Tx process state is 'Stopped'. The transmit threshold is 72. EEPROM size is 8. WARNING: The EEPROM is missing or erased! This interface is missing the EEPROM. This is likely the non-primary interface on a multiport board. EEPROM contents: ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ID block CRC 0xfa (vs. 0xff). Full contents CRC 0x6a15 (read as 0xffff). MII PHY found at address 1, status 0x7849. MII PHY #1 transceiver registers: 3100 7849 2000 5c01 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 8060 8020 0c61 0000 1800 a3b9 0084 4e05 001b. Index #3: Found a Digital DS21140 Tulip adapter at 0xa000. Port selection is 10mpbs-serial, half-duplex. Transmit stopped, Receive stopped, half-duplex. The Rx process state is 'Stopped'. The Tx process state is 'Stopped'. The transmit threshold is 72. EEPROM size is 8. WARNING: The EEPROM is missing or erased! This interface is missing the EEPROM. This is likely the non-primary interface on a multiport board. EEPROM contents: ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ID block CRC 0xfa (vs. 0xff). Full contents CRC 0x6a15 (read as 0xffff). MII PHY found at address 1, status 0x7849. MII PHY #1 transceiver registers: 3100 7849 2000 5c01 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 8060 8020 0c61 0000 1800 a3b9 0083 5405 001b. Index #4: Found a Digital DS21140 Tulip adapter at 0x9800. Port selection is MII, full-duplex. Transmit started, Receive started, full-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 128. EEPROM size is 8. WARNING: The EEPROM is missing or erased! This interface is missing the EEPROM. This is likely the non-primary interface on a multiport board. EEPROM contents: ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ID block CRC 0xfa (vs. 0xff). Full contents CRC 0x6a15 (read as 0xffff). MII PHY found at address 1, status 0x7849. MII PHY #1 transceiver registers: 3100 7849 2000 5c01 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 8060 8020 0c61 0000 1800 a3b9 0083 4a05 001b. --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="mii-diag_eth1" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mii-diag_eth1" Basic registers of MII PHY #1: 3100 7849 2000 5c01 0100 0000 0000 0000. Basic mode control register 0x3100: Auto-negotiation enabled. Basic mode status register 0x7849 ... 7849. Link status: not established. --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="mii-diag_eth2" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mii-diag_eth2" Basic registers of MII PHY #1: 3100 7849 2000 5c01 0100 0000 0000 0000. Basic mode control register 0x3100: Auto-negotiation enabled. Basic mode status register 0x7849 ... 7849. Link status: not established. --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="mii-diag_eth3" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mii-diag_eth3" Basic registers of MII PHY #1: 3100 7849 2000 5c01 0100 0000 0000 0000. Basic mode control register 0x3100: Auto-negotiation enabled. Basic mode status register 0x7849 ... 7849. Link status: not established. --------------37518063FB642CD7E570967C Content-Type: text/plain; charset=us-ascii; name="mii-diag_eth4" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mii-diag_eth4" Basic registers of MII PHY #1: 3100 7849 2000 5c01 0100 0000 0000 0000. Basic mode control register 0x3100: Auto-negotiation enabled. Basic mode status register 0x7849 ... 7849. Link status: not established. --------------37518063FB642CD7E570967C-- From thebs@theseus.com Tue, 8 Aug 2000 10:59:21 -0400 Date: Tue, 8 Aug 2000 10:59:21 -0400 From: Bryan -TheBS- Smith thebs@theseus.com Subject: [tulip] Re: Linksys LNE100TX Driver Problems <- Possible issue On Tue, 08 Aug 2000, Keith Owens wrote: > You realize that Linus is going to come round to your place > and make you use Windows now? No! God no! Please, please, please, I beg forgiveness! [ I'm serious, I never use Windows -- not for the past 12/24 (work/home) months, at least, and very little for the 4 years before that! ] > There has just been a big argument about these symlinks on l-k and > Linus says "NO WAY". /usr/include/asm and /usr/include/linux have to > exist but they should not be symlinks to any old kernel. They should > be real directories containing the headers that glibc was built with. > It is the only way to avoid random compile problems when the kernel > changes. Ahhh. Thank you for that insight. > The symlinks were needed years ago but not with current glibc. If your > distribution does not ship real /usr/include/asm and /usr/include/linux > directories, complain to your distributor. Don't compound the problem > by adding the obsolete symlinks. Linus has spoken. That would explain why I haven't had any issues with the latest Rawhide RPMs (kernel-2.2.16-8) from RedHat, even though I don't have the symlinks. Again, thanx for the heads-up! -- TheBS -- Bryan "TheBS" Smith CONTACT INFO *********************************************************** Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com) Email: mailto:thebs@theseus.com,b.j.smith@ieee.org Legal: http://www.SmithConcepts.com/legal.html From becker@scyld.com Tue, 8 Aug 2000 11:48:14 -0400 (EDT) Date: Tue, 8 Aug 2000 11:48:14 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Re: Linksys LNE100TX Driver Problems <- Possible issue On Tue, 8 Aug 2000, Keith Owens wrote: > > ln -s ../src/linux/include/asm . > > ln -s ../src/linux/include/linux . > > You realize that Linus is going to come round to your place and make > you use Windows now? > > There has just been a big argument about these symlinks on l-k and > Linus says "NO WAY". /usr/include/asm and /usr/include/linux have to Not everyone agreed with Linus on this point, at least not with the current state of affairs. He did not consider all of the issues, and was not identifying the distinct uses of the kernel header files. Some are published interfaces, while others are internal cruft. One example is when a new kernel supports new ioctl() calls. A program can test for missing calls on older kernels, but without the proper constants and structures in the header files it must have local copies of everything. OTOH, there is a lot of bogus cruft that should never have been been in *.h files in the first place. Quick rules: If only one file needs the symbolic constant, don't put it in a header file If a constant is only needed in one place, a symbolic name is likely bogus. Much of /usr/src/linux/include is really ugly, and should never been seen by user code. Check out or . Wait at least two hours after eating. > exist but they should not be symlinks to any old kernel. They should > be real directories containing the headers that glibc was built with. > It is the only way to avoid random compile problems when the kernel > changes. A good point of not having the links is that it's a obvious which structures and variables are interface layers and should not change. IMNSHO, the proper solution is to not to mix the different uses of header files. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From bbales@kscable.com Tue, 08 Aug 2000 15:07:57 -0500 Date: Tue, 08 Aug 2000 15:07:57 -0500 From: Bruce Bales bbales@kscable.com Subject: [tulip] Netgear FA310TX rev D2 NIC I'm new to Linux. Can't find any messages with my problem I have a Netgear FA310TX rev D2 ethernet board with LC82C169C chip (not LC82C168c). Netgear says board is based on DEC 21040 (tulip). Also have an ISA NE2000 card in same machine. Running Mandrake 7.1 ISA board sets up fine with cable modem. Switch cable to Netgear PCI board and change configuration to DHCP for it and Linux looks at it for 60 seconds (Bringing up eth0) then says OK. But it didn't DHCP an address. And won't ping except 127.0.0.1. Mandrake has tulip.c:v0.91g-ppc 7/16/99. Netgear says to get the latest tulipdriver - 0.90Q. I assume 0.91G should be OK, but it doesn't work on this card or another in another machine. They won't ping others or each other. Is there a revised driver? Have part of dmesg, proc pci and ifconfig below. Would appreciate any help. Have been struggling with this for weeks. Bruce Bales _________________________________________________ part of dmesg follows: Linux version 2.2.15-4mdksecure (chmou@kenobi.mandrakesoft.com) (gcc version 2.95.3 19991030 PCI: PCI BIOS revision 2.10 entry at 0xfb180 PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP TCP: Hash tables configured (ehash 32768 bhash 32768) Initializing RT netlink socket tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov eth0: Lite-On 82c168 PNIC rev 32 at 0x6000, 00:A0:CC:5C:AB:35, IRQ 10. eth0: MII transceiver #1 config 3000 status 782d advertising 01e1. ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov) NE*000 ethercard probe at 0x280: 00 00 21 69 7b 86 eth1: NE2000 found at 0x280, using IRQ 11. ============================================== part of proc pci: PCI devices found: Bus 0, device 15, function 0: Ethernet controller: LiteOn LNE100TX (rev 32). Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. I/O at 0x6000 [0x6001]. Non-prefetchable 32 bit memory at 0xf0410000 [0xf0410000]. ======================================================= ifconfig: eth0 Link encap:Ethernet HWaddr 00:A0:CC:5C:AB:35 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:8 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:10 Base address:0x6000 eth1 Link encap:Ethernet HWaddr 00:00:21:69:7B:86 inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0x280 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 From cro@nca.asu.edu Tue, 08 Aug 2000 13:20:25 -0700 Date: Tue, 08 Aug 2000 13:20:25 -0700 From: C. R. Oldham cro@nca.asu.edu Subject: [tulip] Netgear FA310TX rev D2 NIC Bruce Bales wrote: > Switch cable to Netgear PCI board and change configuration to > DHCP for it and Linux looks at it for 60 seconds (Bringing up eth0) then > says OK. But it didn't DHCP an address. And won't ping except > 127.0.0.1. Are you sure your cablemodem isn't locked to the MAC address of the NE2000 card? -- / Charles (C. R.) Oldham | NCA Commission on Schools \ / Director of Technology | Arizona State University \ / "cro at nca dot asu dot edu" | V:480/965-8703 F:480/965-9423 \ | http://www.nca.asu.edu/ | From x@philstone.com Tue, 08 Aug 2000 13:32:21 -0700 Date: Tue, 08 Aug 2000 13:32:21 -0700 From: Christopher Smith x@philstone.com Subject: [tulip] Netgear FA310TX rev D2 NIC This problem likely has to do with the cable modem, and not the adaptor. Frequently cable modems are locked on to the MAC address of a specific adaptor. Alternatively, you need to restart the cable modem to get it to change the MAC address which it's looking for. If you still think the problem is with the software, I'd suggest trying to get it working on a standard ethernet environment. If that works, then you know the problem is with regards to using the cable modem. --On Tuesday, August 08, 2000 3:07 PM -0500 Bruce Bales wrote: > I'm new to Linux. Can't find any messages with my problem > > I have a Netgear FA310TX rev D2 ethernet board with LC82C169C chip (not > LC82C168c). Netgear says > board is based on DEC 21040 (tulip). Also have an ISA NE2000 card in > same machine. Running Mandrake 7.1 ISA board sets up fine with cable > modem. Switch cable to Netgear PCI board and change configuration to > DHCP for it and Linux looks at it for 60 seconds (Bringing up eth0) then > says OK. But it didn't DHCP an address. And won't ping except > 127.0.0.1. > --Chris From killerwrath@yahoo.com Tue, 8 Aug 2000 13:47:49 -0700 (PDT) Date: Tue, 8 Aug 2000 13:47:49 -0700 (PDT) From: Killer Wrath killerwrath@yahoo.com Subject: [tulip] Re: Tulip compile problems > I have a major problem I cannot solve. I try and compile the tulip.c > driver or the pci-scan.c driver and I run into the following problem. > It will not compile and gives me errors something like this: > > /.../.../modversions.h: linux/modules/serial.ver: no such file or > directory I had the same problem, but I have a solution that will work with the Corel distribution of Linux. Use the following list of commands in order, and then you'll be all set (*'s equal the linux version number, in my case it was 2.2.14): cd /usr/src tar zxpvf kernel-source-* ln -s kernel-source-* linux rm -rf /usr/include/asm ln -s /usr/src/linux/include/asm /usr/include/asm rm -rf /usr/include/linux ln -s /usr/src/linux/include/linux /usr/include/linux cd linux cp /boot /config-* .config make oldconfig make dep Finally build pci-scan and copy pci-scan.o to your /lib/modules/*/pcmcia directory and then build tulip and copy tulip.o to your /lib/modules/*/net directory. ===== INFORMATION SUPERHIGHWAY = Interactive Network For Organizing, Retrieving, Manipulating, Accessing and Transferring Information On National systems, Unleashing Practically Every Rebellious Human Intelligence, Gratifying Hackers, Wise-asses and Yahoos. --from http://megadodo.com/articles/6R46.html __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ From becker@scyld.com Tue, 8 Aug 2000 18:08:43 -0400 (EDT) Date: Tue, 8 Aug 2000 18:08:43 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Netgear FA310TX rev D2 NIC On Tue, 8 Aug 2000, Bruce Bales wrote: > Date: Tue, 08 Aug 2000 15:07:57 -0500 > From: Bruce Bales > To: tulip@scyld.com > Subject: [tulip] Netgear FA310TX rev D2 NIC > > I'm new to Linux. Can't find any messages with my problem > > I have a Netgear FA310TX rev D2 ethernet board with LC82C169C chip (not > LC82C168c). Netgear says > board is based on DEC 21040 (tulip). No, it's a LiteOn chip that has a data transfer engine with Tulip-format descriptors, but the transceiver section isn't at all like the 21040. > says OK. But it didn't DHCP an address. And won't ping except > 127.0.0.1. > > Mandrake has tulip.c:v0.91g-ppc 7/16/99. The unmodified 91g-ppc should work with the PNIC, but Mandrake might has a modified version. You might try v92 http://www.scyld.com/network/tulip.html ftp://www.scyld.com/pub/network/tulip.c just to try an alternate version. But I suspect some other problem. > tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov > eth0: Lite-On 82c168 PNIC rev 32 at 0x6000, 00:A0:CC:5C:AB:35, IRQ 10. > eth0: MII transceiver #1 config 3000 status 782d advertising 01e1. This looks normal. Check /proc/interrupts to verify that you are getting interrupts. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From jgarzik@mandrakesoft.com Tue, 08 Aug 2000 19:05:08 -0400 Date: Tue, 08 Aug 2000 19:05:08 -0400 From: Jeff Garzik jgarzik@mandrakesoft.com Subject: [tulip] Netgear FA310TX rev D2 NIC Donald Becker wrote: > The unmodified 91g-ppc should work with the PNIC, but Mandrake might has a > modified version. We ship unmodified 2.2.x kernel tulip driver (and old_tulip as well). As far as the PNIC goes, bug reports for the PNIC and 2.2.x kernel continue to pop up so there are still some unresolved issues. >From my own testing, of all the tulip drivers out there, including NetGear's own driver, Donald's v92 tulip works the best with PNIC. However... even v92 and v92h work poorly with my two test NetGear FA310TX boards. Symptoms include 66.6% packet loss during a ping, and oops under any sort of load on both 10bT and 100bT networks. Jeff -- Jeff Garzik | Building 1024 | Andre the Giant has a posse. MandrakeSoft, Inc. | From jpschewe@eggplant.mtu.net 08 Aug 2000 21:29:02 -0500 Date: 08 Aug 2000 21:29:02 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Linksys LNE100TX version 4.0 (more information) Ok. I've done a little bit of testing here to see how I can get this card to work. I'm trying to connect it to a Linksys 10/100 switch. Linux can find the card, but the activity light blinks like mad and Linux complains about Recieve errors. So apparently the tulip driver under Linux isn't working quite right with the autonegotion, a known problem. I can't figure out how to force the card to 100 full duplex, so I'm trying the card in other systems. The card works fine in Windows 95, which probably isn't very helpful here. However I do have FreeBSD 3.2 up on a system as well and the card happens to work fine with it. Since Linux and FreeBSD are both open source I don't suppose someone that knows more about the driver internals than me, should be most everyone, could look at the FreeBSD driver and figure out what's wrong with the Linux one. It's using the "DEC/Intel 21143 (and clones) PCI fast ethernet card" driver, according to the setup program. -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From thebs@theseus.com Wed, 9 Aug 2000 09:18:09 -0400 Date: Wed, 9 Aug 2000 09:18:09 -0400 From: Bryan -TheBS- Smith thebs@theseus.com Subject: [tulip] Re: Linksys LNE100TX version 4.0 (more information) On Tue, 08 Aug 2000, Jon Schewe wrote: > I can't figure out how to force the card to 100 full duplex, > so I'm trying the card in other systems. Every tulip.c driver I've seen is well documented on these settings. Otherwise, hit the Tulip page: http://www.scyld.com/network/tulip.html The options are there. -- TheBS -- Bryan "TheBS" Smith CONTACT INFO *********************************************************** Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com) Email: mailto:thebs@theseus.com,b.j.smith@ieee.org Legal: http://www.SmithConcepts.com/legal.html From jpschewe@eggplant.mtu.net 09 Aug 2000 08:50:17 -0500 Date: 09 Aug 2000 08:50:17 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Re: Linksys LNE100TX version 4.0 (more information) Bryan -TheBS- Smith writes: > On Tue, 08 Aug 2000, Jon Schewe wrote: > > I can't figure out how to force the card to 100 full duplex, > > so I'm trying the card in other systems. > > Every tulip.c driver I've seen is well documented on these settings. > > Otherwise, hit the Tulip page: > http://www.scyld.com/network/tulip.html > > The options are there. You mean insmod tulip options=3 full_duplex=1 debug=6? Even when I do that the tuilp-diag utility shows I'm in half duplex, no matter what I put in there. -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From treinertson@uswest.net Wed, 09 Aug 2000 12:28:11 -0500 Date: Wed, 09 Aug 2000 12:28:11 -0500 From: Tom Reinertson treinertson@uswest.net Subject: [tulip] Problem with LinkSys PCMPC200 --------------2DA62FA637362915C766D763 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi All, I just picked up a LinkSys PCMPC200, the 32-bit cardbus ethernet card and installed it on my ThinkPad 570E running Caldera OpenLinux 2.4 (kernel 2.2.14). I have several questions I hope someone may be able to help me with. 1) I downloaded the source rpm and followed the instructions in updates.html. The rpm placed the modules in /lib/modules/2.2.14/net but when I started pcmcia the log showed the following messages: Aug 9 08:43:12 parkcity kernel: Linux PCMCIA Card Services 3.1.8 Aug 9 08:43:12 parkcity kernel: kernel build: 2.2.14 #1 SMP Thu Feb 10 20:08:45 CET 2000 Aug 9 08:43:12 parkcity kernel: options: [pci] [cardbus] Aug 9 08:43:12 parkcity kernel: Intel PCIC probe: Aug 9 08:43:12 parkcity kernel: TI 1450 PCI-to-CardBus at bus 0 slot 2, mem 0x50000000, 2 sockets Aug 9 08:43:12 parkcity kernel: host opts [0]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 2/4] Aug 9 08:43:12 parkcity kernel: host opts [1]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 5/7] Aug 9 08:43:12 parkcity kernel: ISA irqs (scanned) = 3,4,5,7,9,10 status change on irq 10 Aug 9 08:43:12 parkcity cardmgr[452]: starting, version is 3.1.8 Aug 9 08:43:12 parkcity cardmgr[452]: watching 2 sockets Aug 9 08:43:12 parkcity kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x104f 0x15e8-0x15ef Aug 9 08:43:12 parkcity kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7 Aug 9 08:43:12 parkcity kernel: cs: IO port probe 0x0a00-0x0aff: clean. Aug 9 08:43:12 parkcity kernel: cs: cb_alloc(bus 2): vendor 0x13d1, device 0xab02 Aug 9 08:43:12 parkcity cardmgr[452]: initializing socket 0 Aug 9 08:43:12 parkcity cardmgr[452]: unsupported card in socket 0 Aug 9 08:43:13 parkcity cardmgr[452]: product info: "CardBus", "Fast Ethernet", "V1.0", "" Aug 9 08:43:13 parkcity cardmgr[452]: manfid: 0x13d1, 0xab02 function: 6 (network) Aug 9 08:43:13 parkcity cardmgr[452]: exiting I noticed that /etc/pcmcia/config.opts had not been modified by the rpm so I added the lines suggested by updates.html: device "tulip" class "network" module "cb_enabler", "pci-scan", "cb_shim", "tulip" card "Linksys EtherFast 10/100" manfid 0x0149, 0x0231 bind "tulip" card "Linksys EtherFast 10/100 v2.0" manfid 0x0149, 0xc2ab bind "tulip" card "Linksys EtherFast PCM200" manfid 0x13d1, 0xab03 bind "tulip" with an additional line to reflect the different manfid in my log: card "Linksys EtherFast PCM200" manfid 0x13d1, 0xab02 bind "tulip" When I modify /etc/pcmcia/config.opts I now get a different error: Aug 9 08:59:17 parkcity kernel: Linux PCMCIA Card Services 3.1.8 Aug 9 08:59:17 parkcity kernel: kernel build: 2.2.14 #1 SMP Thu Feb 10 20:08:45 CET 2000 Aug 9 08:59:17 parkcity kernel: options: [pci] [cardbus] Aug 9 08:59:17 parkcity kernel: Intel PCIC probe: Aug 9 08:59:17 parkcity kernel: TI 1450 PCI-to-CardBus at bus 0 slot 2, mem 0x50000000, 2 sockets Aug 9 08:59:17 parkcity kernel: host opts [0]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 2/4] Aug 9 08:59:17 parkcity kernel: host opts [1]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 5/7] Aug 9 08:59:17 parkcity kernel: ISA irqs (scanned) = 3,4,5,7,9,10 status change on irq 10 Aug 9 08:59:17 parkcity cardmgr[759]: starting, version is 3.1.8 Aug 9 08:59:17 parkcity cardmgr[759]: watching 2 sockets Aug 9 08:59:17 parkcity kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x104f 0x15e8-0x15ef Aug 9 08:59:17 parkcity kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7 Aug 9 08:59:17 parkcity kernel: cs: IO port probe 0x0a00-0x0aff: clean. Aug 9 08:59:17 parkcity kernel: cs: cb_alloc(bus 2): vendor 0x13d1, device 0xab02 Aug 9 08:59:17 parkcity cardmgr[759]: initializing socket 0 Aug 9 08:59:17 parkcity cardmgr[759]: socket 0: Linksys EtherFast PCM200 Aug 9 08:59:17 parkcity cardmgr[759]: executing: 'insmod /lib/modules/2.2.14/pcmcia/cb_enabler.o' Aug 9 08:59:18 parkcity cardmgr[759]: module /lib/modules/2.2.14/pcmcia/pci-scan.o not available Aug 9 08:59:18 parkcity cardmgr[759]: module /lib/modules/2.2.14/pcmcia/cb_shim.o not available Aug 9 08:59:18 parkcity cardmgr[759]: module /lib/modules/2.2.14/pcmcia/tulip.o not available Aug 9 08:59:19 parkcity cardmgr[759]: get dev info on socket 0 failed: Resource temporarily unavailable Aug 9 08:59:19 parkcity cardmgr[759]: exiting It seems that the rpm put the drivers in /lib/modules/2.2.14/net but the pcmcia code is looking in pcmcia/. So I followed the instructions in updates.html for installing individual drivers and dowloaded tulip.c, pci-scan.c, pci-scan.h, kern_compat.h and Makefile and put them all into /usr/local/src/tulip/. When I run 'make' I get the following errors: gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -I/usr/src/linux/include -DMODVERSIONS -c -o pci-scan.o pci-scan.c In file included from pci-scan.c:62: kern_compat.h:164: parse error before `0' kern_compat.h:168: warning: type defaults to `int' in declaration of `mark_bh' kern_compat.h:168: warning: parameter names (without types) in function declaration kern_compat.h:168: warning: data definition has no type or storage class kern_compat.h:168: parse error before `}' make: *** [pci-scan.o] Error 1 Now I'm stuck. I don't really know what to try next. I would greatly appreciate any help anyone can offer. Thanks. Tom --------------2DA62FA637362915C766D763 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi All,

I just picked up a LinkSys PCMPC200, the 32-bit cardbus ethernet card and installed it on my ThinkPad 570E running Caldera OpenLinux 2.4 (kernel 2.2.14).  I have several questions I hope someone may be able to help me with.

1) I downloaded the source rpm and followed the instructions in updates.html.  The rpm placed the modules in /lib/modules/2.2.14/net but when I started pcmcia the log showed the following messages:

Aug  9 08:43:12 parkcity kernel: Linux PCMCIA Card Services 3.1.8
Aug  9 08:43:12 parkcity kernel:   kernel build: 2.2.14 #1 SMP Thu Feb 10 20:08:45 CET 2000
Aug  9 08:43:12 parkcity kernel:   options:  [pci] [cardbus]
Aug  9 08:43:12 parkcity kernel: Intel PCIC probe:
Aug  9 08:43:12 parkcity kernel:   TI 1450 PCI-to-CardBus at bus 0 slot 2, mem 0x50000000, 2 sockets
Aug  9 08:43:12 parkcity kernel:     host opts [0]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 2/4]
Aug  9 08:43:12 parkcity kernel:     host opts [1]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 5/7]
Aug  9 08:43:12 parkcity kernel:     ISA irqs (scanned) = 3,4,5,7,9,10 status change on irq 10
Aug  9 08:43:12 parkcity cardmgr[452]: starting, version is 3.1.8
Aug  9 08:43:12 parkcity cardmgr[452]: watching 2 sockets
Aug  9 08:43:12 parkcity kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x104f 0x15e8-0x15ef
Aug  9 08:43:12 parkcity kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7
Aug  9 08:43:12 parkcity kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug  9 08:43:12 parkcity kernel: cs: cb_alloc(bus 2): vendor 0x13d1, device 0xab02
Aug  9 08:43:12 parkcity cardmgr[452]: initializing socket 0
Aug  9 08:43:12 parkcity cardmgr[452]: unsupported card in socket 0
Aug  9 08:43:13 parkcity cardmgr[452]:   product info: "CardBus", "Fast Ethernet", "V1.0", ""
Aug  9 08:43:13 parkcity cardmgr[452]:   manfid: 0x13d1, 0xab02  function: 6 (network)
Aug  9 08:43:13 parkcity cardmgr[452]: exiting

I noticed that /etc/pcmcia/config.opts had not been modified by the rpm so I added the lines suggested by updates.html:

device "tulip" class "network" module "cb_enabler", "pci-scan", "cb_shim", "tulip"
card "Linksys EtherFast 10/100"        manfid 0x0149, 0x0231  bind "tulip"
card "Linksys EtherFast 10/100 v2.0"   manfid 0x0149, 0xc2ab  bind "tulip"
card "Linksys EtherFast PCM200"        manfid 0x13d1, 0xab03  bind "tulip"

with an additional line to reflect the different manfid in my log:

card "Linksys EtherFast PCM200"        manfid 0x13d1, 0xab02  bind "tulip"

When I modify /etc/pcmcia/config.opts I now get a different error:

Aug  9 08:59:17 parkcity kernel: Linux PCMCIA Card Services 3.1.8
Aug  9 08:59:17 parkcity kernel:   kernel build: 2.2.14 #1 SMP Thu Feb 10 20:08:45 CET 2000
Aug  9 08:59:17 parkcity kernel:   options:  [pci] [cardbus]
Aug  9 08:59:17 parkcity kernel: Intel PCIC probe:
Aug  9 08:59:17 parkcity kernel:   TI 1450 PCI-to-CardBus at bus 0 slot 2, mem 0x50000000, 2 sockets
Aug  9 08:59:17 parkcity kernel:     host opts [0]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 2/4]
Aug  9 08:59:17 parkcity kernel:     host opts [1]: [pwr save] [serial pci & irq] [no pci irq] [lat 64/176] [bus 5/7]
Aug  9 08:59:17 parkcity kernel:     ISA irqs (scanned) = 3,4,5,7,9,10 status change on irq 10
Aug  9 08:59:17 parkcity cardmgr[759]: starting, version is 3.1.8
Aug  9 08:59:17 parkcity cardmgr[759]: watching 2 sockets
Aug  9 08:59:17 parkcity kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x104f 0x15e8-0x15ef
Aug  9 08:59:17 parkcity kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x4d0-0x4d7
Aug  9 08:59:17 parkcity kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug  9 08:59:17 parkcity kernel: cs: cb_alloc(bus 2): vendor 0x13d1, device 0xab02
Aug  9 08:59:17 parkcity cardmgr[759]: initializing socket 0
Aug  9 08:59:17 parkcity cardmgr[759]: socket 0: Linksys EtherFast PCM200
Aug  9 08:59:17 parkcity cardmgr[759]: executing: 'insmod /lib/modules/2.2.14/pcmcia/cb_enabler.o'
Aug  9 08:59:18 parkcity cardmgr[759]: module /lib/modules/2.2.14/pcmcia/pci-scan.o not available
Aug  9 08:59:18 parkcity cardmgr[759]: module /lib/modules/2.2.14/pcmcia/cb_shim.o not available
Aug  9 08:59:18 parkcity cardmgr[759]: module /lib/modules/2.2.14/pcmcia/tulip.o not available
Aug  9 08:59:19 parkcity cardmgr[759]: get dev info on socket 0 failed: Resource temporarily unavailable
Aug  9 08:59:19 parkcity cardmgr[759]: exiting

It seems that the rpm put the drivers in /lib/modules/2.2.14/net but the pcmcia code is looking in pcmcia/.  So I followed the instructions in updates.html for installing individual drivers and dowloaded tulip.c, pci-scan.c, pci-scan.h, kern_compat.h and Makefile and put them all into /usr/local/src/tulip/.  When I run 'make' I get the following errors:

gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -I/usr/src/linux/include -DMODVERSIONS   -c -o pci-scan.o pci-scan.c
In file included from pci-scan.c:62:
kern_compat.h:164: parse error before `0'
kern_compat.h:168: warning: type defaults to `int' in declaration of `mark_bh'
kern_compat.h:168: warning: parameter names (without types) in function declaration
kern_compat.h:168: warning: data definition has no type or storage class
kern_compat.h:168: parse error before `}'
make: *** [pci-scan.o] Error 1

Now I'm stuck.  I don't really know what to try next.  I would greatly appreciate any help anyone can offer.

Thanks.

Tom
  --------------2DA62FA637362915C766D763-- From becker@scyld.com Wed, 9 Aug 2000 14:29:34 -0400 (EDT) Date: Wed, 9 Aug 2000 14:29:34 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Problem with LinkSys PCMPC200 On Wed, 9 Aug 2000, Tom Reinertson wrote: > I just picked up a LinkSys PCMPC200, the 32-bit cardbus ethernet card ... > Aug 9 08:43:12 parkcity cardmgr[452]: unsupported card in socket 0 > Aug 9 08:43:13 parkcity cardmgr[452]: product info: "CardBus", "Fast > Ethernet", "V1.0", "" > Aug 9 08:43:13 parkcity cardmgr[452]: manfid: 0x13d1, 0xab02 A new ID. What is the version number on the card? Curiously the new ID is lower than the old > When I modify /etc/pcmcia/config.opts I now get a different error: > ... > Aug 9 08:59:18 parkcity cardmgr[759]: module > /lib/modules/2.2.14/pcmcia/pci-scan.o not available ... > It seems that the rpm put the drivers in /lib/modules/2.2.14/net but the > pcmcia code is looking in pcmcia/. So I followed the instructions in Grrrr... the module loading should be using 'modprobe pci-scan', not 'insmod pcmcia/pci-scan'. I believe that David Hinds' new version fixes this buglet. Until then hack in a work-around by making a symbolic link cd /lib/modules/2.2.14/pcmcia ln -s ../net/pci-scan.o . ln -s ../net/cb_shim.o . ln -s ../net/3c59x.o . ln -s ../net/eepro100.o . ln -s ../net/epic100.o . ln -s ../net/rtl8139.o . ln -s ../net/tulip.o . ln -s ../net/via-rhine.o . Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From bricc@gte.net Thu, 10 Aug 2000 09:30:24 -0400 Date: Thu, 10 Aug 2000 09:30:24 -0400 From: Brian Hanks bricc@gte.net Subject: [tulip] Tulip Working!!! Diagnostics Utility Problem I have managed to get the tulip driver working, so my system is recognizing the LNE100TX v4. Thanks for all of your help. I have also compiled mii-diag.c and the tulip-diag.c programs, but I cannot get them to execute. Despite being able to see the files and having verified their permissions, I keep getting a "bash: mii-diag: command not found" message. I'm sure this is something stupid because I am really new at this, but I'm at a loss. Thanks again for you help during this learning period. From palspf@earthlink.com Thu, 10 Aug 2000 20:48:22 -0500 Date: Thu, 10 Aug 2000 20:48:22 -0500 From: Paul Pals palspf@earthlink.com Subject: [tulip] LNE100tx v4.1 and mandrake 7.1 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0030C.52BA3600 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Has anyone out there been able to configure this LAN card with mandrake = 7.1. I am having nothing but problems. I am relatively new at Linux = and I hope someone can tell me what to do. Please = help!steve_pals@hotmail.com ------=_NextPart_000_0007_01C0030C.52BA3600 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Has anyone out there been able to configure this LAN = card with=20 mandrake 7.1.  I am having nothing but problems.  I am = relatively new=20 at Linux and I hope someone can tell me what to do.  Please help!steve_pals@hotmail.com
------=_NextPart_000_0007_01C0030C.52BA3600-- From markgray@iago.nac.net 10 Aug 2000 22:20:03 -0400 Date: 10 Aug 2000 22:20:03 -0400 From: Mark Gray markgray@iago.nac.net Subject: [tulip] Tulip Working!!! Diagnostics Utility Problem Brian Hanks writes: > I have managed to get the tulip driver working, so my system is > recognizing the LNE100TX v4. Thanks for all of your help. > > I have also compiled mii-diag.c and the tulip-diag.c programs, but I > cannot get them to execute. Despite being able to see the files and > having verified their permissions, I keep getting a "bash: mii-diag: > command not found" message. > > I'm sure this is something stupid because I am really new at this, but > I'm at a loss. The current directory is not in your PATH -- either add it to the end of your path or execute the command like so: ./mii-diag From markgray@iago.nac.net 10 Aug 2000 22:27:37 -0400 Date: 10 Aug 2000 22:27:37 -0400 From: Mark Gray markgray@iago.nac.net Subject: [tulip] LNE100tx v4.1 and mandrake 7.1 "Paul Pals" writes: > Has anyone out there been able to configure this LAN card with > mandrake 7.1. I am having nothing but problems. I am relatively > new at Linux and I hope someone can tell me what to do. Please > help! This card will not work with the stock driver included with the kernel (even the latest 2.2.16 or 2.4.0 kernel) You need to download, compile, and install the latest driver. See: http://www.scyld.com/network/updates.html and http://www.scyld.com/network/tulip.html for instructions. (How you managed to find this mailing list without having tried the latest driver is beyond me, but I take it that you did -- if I am wrong I apologize for making that assumption.) > steve_pals@hotmail.com From jpschewe@eggplant.mtu.net 10 Aug 2000 22:17:30 -0500 Date: 10 Aug 2000 22:17:30 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Tulip Working!!! Diagnostics Utility Problem Brian Hanks writes: > I have managed to get the tulip driver working, so my system is > recognizing the LNE100TX v4. Thanks for all of your help. > > I have also compiled mii-diag.c and the tulip-diag.c programs, but I > cannot get them to execute. Despite being able to see the files and > having verified their permissions, I keep getting a "bash: mii-diag: > command not found" message. . is not usually in your path so do ./mii-diag Note that I've gotten Linux to recognize my LNE100TX v4 card as well, but it won't autonegotiate correctly on a 10/100 full duplex switch. Let me know if you get this to work. -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From x@philstone.com Fri, 11 Aug 2000 14:40:49 -0700 Date: Fri, 11 Aug 2000 14:40:49 -0700 From: Christopher Smith x@philstone.com Subject: [tulip] Linksys LNE100TX version 4.0 (more information) Does the 2.4preX driver work? --Chris --On Tuesday, August 08, 2000 9:29 PM -0500 Jon Schewe wrote: > Ok. I've done a little bit of testing here to see how I can get this > card to work. I'm trying to connect it to a Linksys 10/100 switch. > Linux can find the card, but the activity light blinks like mad and Linux > complains about Recieve errors. So apparently the tulip driver under > Linux isn't working quite right with the autonegotion, a known problem. > I can't figure out how to force the card to 100 full duplex, so I'm > trying the card in other systems. The card works fine in Windows 95, > which probably isn't very helpful here. However I do have FreeBSD 3.2 up > on a system as well and the card happens to work fine with it. Since > Linux and FreeBSD are both open source I don't suppose someone that knows > more about the driver internals than me, should be most everyone, could > look at the FreeBSD driver and figure out what's wrong with the Linux > one. It's using the "DEC/Intel 21143 (and clones) PCI fast ethernet > card" driver, according to the setup program. > > -- > Jon Schewe > http://eggplant.mtu.net/~jpschewe > jpschewe@eggplant.mtu.net > > > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip From eric@thelin.org Fri, 11 Aug 2000 15:48:34 -0700 (MST) Date: Fri, 11 Aug 2000 15:48:34 -0700 (MST) From: Eric Thelin eric@thelin.org Subject: [tulip] Netgear FA310TX rev D2 NIC On Tue, 8 Aug 2000, Donald Becker wrote: > On Tue, 8 Aug 2000, Bruce Bales wrote: > > I have a Netgear FA310TX rev D2 ethernet board with LC82C169C chip (not > > LC82C168c). Netgear says > > board is based on DEC 21040 (tulip). > > No, it's a LiteOn chip that has a data transfer engine with Tulip-format > descriptors, but the transceiver section isn't at all like the 21040. I have this problem too where the card just seems to hang after heavy use I have seen it on 100 BaseT Full Duplex, 100 BaseT Half Duplex. I just checked and I am using the same rev D2. I also periodicly see problems where the fastest transfers I can get between two identical cards is about 150K/s. And that is on a 100Mb switch running full duplex. If the original thoughts about the problem being in the trancever detection would it solve or even improve the situation to force the media type to MII 100baseFx-FDX or something like that? I haven't tried the .92 version of the driver yet. I was trying to just copy the file over the .91 version in /usr/src/linux/drivers/net/ but then my kernel wouldn't compile. I am going to try using it as a module and see if that makes any difference. I am using 2.2.16 by the way. Any ideas? I have also heard that the tulip drivers are no longer as well supported as others. Is there any truth to this? Is it just these Netgear cards? Or is this just a bug in an active project and nothing to be concerned about once it is fixed? I hope this is the case and someone can find a solution soon as I have put these cards in almost every computer on my network. Eric Eric Thelin erict@aztechbiz.com AZtechBiz.com: Where Arizona Does Tech Business Voice: 480-377-6743 Fax: 480-377-6755 From dinn@blend.twistedpair.ca Fri, 11 Aug 2000 19:57:34 -0300 Date: Fri, 11 Aug 2000 19:57:34 -0300 From: Michael 'Moose' Dinn dinn@blend.twistedpair.ca Subject: [tulip] Netgear FA310TX rev D2 NIC > I have this problem too where the card just seems to hang after heavy > use I have seen it on 100 BaseT Full Duplex, 100 BaseT Half Duplex. I I've seen this too, but only on cheap-quality motherboards. All of the machines we have in house running Linux (~20 of them) use ASUS or FIC motherboards and Netgear D2 cards, and we've never seen the problem arise before on any of them. A customer machine was having the problem until his motherboard was replaced... -- Michael 'Moose' Dinn, Twisted Pair Network Consulting Incorporated dinn@moose.to // 902 423 4700 (voice) // 902 423 8407 (fax) "Duct tape is like the force. It has a light side, a dark side, and holds the universe together." From jpschewe@eggplant.mtu.net 11 Aug 2000 18:20:15 -0500 Date: 11 Aug 2000 18:20:15 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Linksys LNE100TX version 4.0 (more information) I don't have a 2.4preX kernel installed, I'm using 2.2.16 SMP. I do have the new 2.0 drivers installed from the tulip web site though. Are the 2.4preX drivers any different than the ones on the tulip website? Christopher Smith writes: > Does the 2.4preX driver work? > > --Chris > > --On Tuesday, August 08, 2000 9:29 PM -0500 Jon Schewe > wrote: > > > Ok. I've done a little bit of testing here to see how I can get this > > card to work. I'm trying to connect it to a Linksys 10/100 switch. > > Linux can find the card, but the activity light blinks like mad and Linux > > complains about Recieve errors. So apparently the tulip driver under > > Linux isn't working quite right with the autonegotion, a known problem. > > I can't figure out how to force the card to 100 full duplex, so I'm > > trying the card in other systems. The card works fine in Windows 95, > > which probably isn't very helpful here. However I do have FreeBSD 3.2 up > > on a system as well and the card happens to work fine with it. Since > > Linux and FreeBSD are both open source I don't suppose someone that knows > > more about the driver internals than me, should be most everyone, could > > look at the FreeBSD driver and figure out what's wrong with the Linux > > one. It's using the "DEC/Intel 21143 (and clones) PCI fast ethernet > > card" driver, according to the setup program. > > > > -- > > Jon Schewe > > http://eggplant.mtu.net/~jpschewe > > jpschewe@eggplant.mtu.net > > > > > > _______________________________________________ > > tulip mailing list > > tulip@scyld.com > > http://www.scyld.com/mailman/listinfo/tulip > > > > > > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From eric@generation-i.com Fri, 11 Aug 2000 17:18:28 -0700 (MST) Date: Fri, 11 Aug 2000 17:18:28 -0700 (MST) From: Eric Thelin eric@generation-i.com Subject: [tulip] Netgear FA310TX rev D2 NIC On Fri, 11 Aug 2000, Michael 'Moose' Dinn wrote: > > I have this problem too where the card just seems to hang after heavy > > use I have seen it on 100 BaseT Full Duplex, 100 BaseT Half Duplex. I > > > I've seen this too, but only on cheap-quality motherboards. All of the > machines we have in house running Linux (~20 of them) use ASUS or FIC > motherboards and Netgear D2 cards, and we've never seen the problem arise > before on any of them. > > A customer machine was having the problem until his motherboard was > replaced... In my case the motherboards are either Gigabyte or FIC. Both have exhibited the network freezes. The FIC boards are using the VIA mvp3 chipset and the Gigabyte boards are using the ALI Aladdin V. So it doesn't seem to be based on the motherboard of the chipset. Eric Eric Thelin erict@aztechbiz.com AZtechBiz.com: Where Arizona Does Tech Business Voice: 480-377-6743 Fax: 480-377-6755 From becker@scyld.com Sat, 12 Aug 2000 02:03:25 -0400 (EDT) Date: Sat, 12 Aug 2000 02:03:25 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Netgear FA310TX rev D2 NIC On Fri, 11 Aug 2000, Eric Thelin wrote: > On Tue, 8 Aug 2000, Donald Becker wrote: > > On Tue, 8 Aug 2000, Bruce Bales wrote: > > > I have a Netgear FA310TX rev D2 ethernet board with LC82C169C chip (not > > > LC82C168c). Netgear says > > > board is based on DEC 21040 (tulip). > > > > No, it's a LiteOn chip that has a data transfer engine with Tulip-format > > descriptors, but the transceiver section isn't at all like the 21040. > > I have this problem too where the card just seems to hang after heavy ... > haven't tried the .92 version of the driver yet. I was trying to just You should try v0.92, although the usual difficult is with media selection, not data transfer. The v92 driver adds better PCI bus error reporting. > I have also heard that the tulip drivers are no longer as well supported > as others. We support the tulip driver in Scyld driver set. Those changes make it into the kernel on an ad hoc basis. I didn't want the situation to end up this way, but that's the Way Things Are. > Is there any truth to this? Is it just these Netgear cards? The claim is that the LiteOn is very sensitive to PCI bus timing that doesn't meet the spec. On some motherboard the Rx FIFO loses sync with the data transfer engine, and packets are occasionally dropped. I have not been able to reproduce this reported problem. There is a very ugly hack in the BSD driver that is supposed to work around this packet corrupion, but I'm not going put in such obviously sleazy and risky code without being certain that the error exists and knowing the work-around is valid and does not result in corrupted data. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From steved@writeme.com Sat, 12 Aug 2000 21:32:22 +1000 Date: Sat, 12 Aug 2000 21:32:22 +1000 From: Steve Dalton steved@writeme.com Subject: [tulip] Netgear 510 Cardbus PCMCIA Help! I have had no sucess getting this card working under Redhat 6.2 for weeks now. I have updated my network and pcmcia drivers to the latest versions (pcmcia 3.1.19 & netdriver 2.0), and this doesn't seem to have made the blindest difference! I have searched the net and tried everything that has been suggested. The card looks ok until I actually try and bring the ethernet interface up, then I get the continual message eth0: Tx hung 9 vs 0 I have attached the output from dmesg, lsmod and the tulip diagnosis tool. One question that has confused me a little. lsmod tells me that I am using the tulip_cb module for my card - which lives in the pcmcia package. How is this connected to the tulip.o module in the network package??? Does it use the tulip.o module or does it implement it's own driver? I found the documentation on this pretty confusing and would appreciate it if someone would explain. Many thanks in advance. Steve dmesg ===== cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019 cs: cb_config(bus 32) fn 0 bar 1: io 0x100-0x17f fn 0 bar 2: mem 0x600c0000-0x600c03ff fn 0 rom: mem 0x60080000-0x600bffff irq 3 cs: cb_enable(bus 32) bridge io map 0 (flags 0x21): 0x100-0x17f bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff tulip_attach(device 20:00.0) tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) eth0: Digital DS21143 Tulip rev 65 at 0x100, 00:10:7A:15:AD:5A, IRQ 3. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. eth0: MII transceiver #1 config 1000 status 7849 advertising 01e1. eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. eth0: Tx hung, 11 vs. 0. lsmod ==== Module Size Used by tulip_cb 32596 2 cb_enabler 2376 2 [tulip_cb] ds 6280 1 [cb_enabler] i82365 21668 1 pcmcia_core 44128 0 [cb_enabler ds i82365] lockd 31496 1 (autoclean) sunrpc 53028 1 (autoclean) [lockd] nls_iso8859-1 2240 1 (autoclean) nls_cp437 3748 1 (autoclean) vfat 9244 1 (autoclean) fat 30432 1 (autoclean) [vfat] tulip_diag ======== tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Digital DS21143 Tulip adapter at 0x100. Port selection is MII, full-duplex. Transmit started, Receive started, full-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 128. Interrupt sources are pending! CSR5 is f0678006. Tx complete indication. Tx out of buffers indication. The NWay status register is 000000c6. EEPROM size is 8. PCI Subsystem IDs, vendor 1385, device 2100. CardBus Information Structure at offset 00005002. Ethernet MAC Station Address 00:10:7A:15:AD:5A. EEPROM transceiver/media description for the Digital DS21143 Tulip chip. Leaf node at offset 30, default media type 0800 (Autosense). 1 transceiver description blocks: Media MII, block type 3, length 13. MII interface PHY 0 (media type 11). 21143 MII initialization sequence is 0 words:. 21143 MII reset sequence is 0 words:. Media capabilities are 7800, advertising 01e1. Full-duplex map 5000, Threshold map 1800. No MII interrupt. MII PHY found at address 1, status 0x786d. MII PHY #1 transceiver registers: 1000 786d 0043 7421 01e1 45e1 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0230 0087 0000 0000 0000 0000 c4c8 0700 0000 0421 2010 2000 0000 0000 0000 0000. Internal autonegotiation state is 'Autonegotiation disabled'. ______________________________________ Steve Dalton Sydney, Australia http://members.dingoblue.net.au/~groundhog From becker@scyld.com Sat, 12 Aug 2000 08:05:12 -0400 (EDT) Date: Sat, 12 Aug 2000 08:05:12 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Netgear 510 Cardbus PCMCIA On Sat, 12 Aug 2000, Steve Dalton wrote: > Subject: [tulip] Netgear 510 Cardbus PCMCIA > I have had no sucess getting this card working under Redhat 6.2 for weeks > now. I have updated my network and pcmcia drivers to the latest versions > (pcmcia 3.1.19 & netdriver 2.0), and this doesn't seem to have made the ... > One question that has confused me a little. lsmod tells me that I am using > the tulip_cb module for my card - which lives in the pcmcia package. How is > this connected to the tulip.o module in the network package??? Does it use You aren't using the updated Tulip driver. You must use the new PCMCIA table in http://www.scyld.com/network/updates.html > Index #1: Found a Digital DS21143 Tulip adapter at 0x100. > Interrupt sources are pending! CSR5 is f0678006. > Tx complete indication. > Tx out of buffers indication. The real problem is that the driver isn't getting interrupts. This likely means that the PCMCIA package isn't configured properly. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From steved@writeme.com Sun, 13 Aug 2000 11:39:51 +1000 Date: Sun, 13 Aug 2000 11:39:51 +1000 From: Steve Dalton steved@writeme.com Subject: [tulip] Netgear 510 Cardbus PCMCIA Thanks for the info, I added the PCMCIA table from the webpage and also added the line card "NetGear FA510C Fast Ethernet Cardbus Card" manfid 0x9513, 0x0081 bind "tulip" as my card is not listed. However, now I am getting the message in dmesg: cs: could not allocate 4K memory for CardBus socket 0 Any Ideas? Many Thanks Steve ______________________________________ Steve Dalton Sydney, Australia http://members.dingoblue.net.au/~groundhog ----- Original Message ----- From: Donald Becker To: Steve Dalton Cc: Sent: Saturday, August 12, 2000 10:05 PM Subject: Re: [tulip] Netgear 510 Cardbus PCMCIA > On Sat, 12 Aug 2000, Steve Dalton wrote: > > > Subject: [tulip] Netgear 510 Cardbus PCMCIA > > I have had no sucess getting this card working under Redhat 6.2 for weeks > > now. I have updated my network and pcmcia drivers to the latest versions > > (pcmcia 3.1.19 & netdriver 2.0), and this doesn't seem to have made the > ... > > One question that has confused me a little. lsmod tells me that I am using > > the tulip_cb module for my card - which lives in the pcmcia package. How is > > this connected to the tulip.o module in the network package??? Does it use > > You aren't using the updated Tulip driver. > You must use the new PCMCIA table in > http://www.scyld.com/network/updates.html > > > Index #1: Found a Digital DS21143 Tulip adapter at 0x100. > > Interrupt sources are pending! CSR5 is f0678006. > > Tx complete indication. > > Tx out of buffers indication. > > The real problem is that the driver isn't getting interrupts. > This likely means that the PCMCIA package isn't configured properly. > > Donald Becker becker@scyld.com > Scyld Computing Corporation http://www.scyld.com > 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution > Annapolis MD 21403 > From steved@writeme.com Sun, 13 Aug 2000 16:21:10 +1000 Date: Sun, 13 Aug 2000 16:21:10 +1000 From: Steve Dalton steved@writeme.com Subject: [tulip] Netgear 510 Cardbus PCMCIA OK, I figured out what I was doing wrong. The latest tulip driver is now being used, using tulip.o, cb_shim.o etc rather than tulib_cb.o. The card looks like it comes up, but I still get the same problem with Tx Hung 11 vs 0. I am using the latest (3.1.19) version of the pcmcia package. Is this method of using the tulip module tested with this version of PCMCIA - is it worth going to an older version? Steve ______________________________________ Steve Dalton Sydney, Australia http://members.dingoblue.net.au/~groundhog ----- Original Message ----- From: Steve Dalton To: Sent: Sunday, August 13, 2000 11:39 AM Subject: Re: [tulip] Netgear 510 Cardbus PCMCIA > Thanks for the info, > > I added the PCMCIA table from the webpage and also added the line > > card "NetGear FA510C Fast Ethernet Cardbus Card" manfid 0x9513, 0x0081 bind > "tulip" > > as my card is not listed. > > However, now I am getting the message in dmesg: > cs: could not allocate 4K memory for CardBus socket 0 > > Any Ideas? > Many Thanks > Steve > > ______________________________________ > Steve Dalton > Sydney, Australia > http://members.dingoblue.net.au/~groundhog > ----- Original Message ----- > From: Donald Becker > To: Steve Dalton > Cc: > Sent: Saturday, August 12, 2000 10:05 PM > Subject: Re: [tulip] Netgear 510 Cardbus PCMCIA > > > > On Sat, 12 Aug 2000, Steve Dalton wrote: > > > > > Subject: [tulip] Netgear 510 Cardbus PCMCIA > > > I have had no sucess getting this card working under Redhat 6.2 for > weeks > > > now. I have updated my network and pcmcia drivers to the latest versions > > > (pcmcia 3.1.19 & netdriver 2.0), and this doesn't seem to have made the > > ... > > > One question that has confused me a little. lsmod tells me that I am > using > > > the tulip_cb module for my card - which lives in the pcmcia package. How > is > > > this connected to the tulip.o module in the network package??? Does it > use > > > > You aren't using the updated Tulip driver. > > You must use the new PCMCIA table in > > http://www.scyld.com/network/updates.html > > > > > Index #1: Found a Digital DS21143 Tulip adapter at 0x100. > > > Interrupt sources are pending! CSR5 is f0678006. > > > Tx complete indication. > > > Tx out of buffers indication. > > > > The real problem is that the driver isn't getting interrupts. > > This likely means that the PCMCIA package isn't configured properly. > > > > Donald Becker becker@scyld.com > > Scyld Computing Corporation http://www.scyld.com > > 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution > > Annapolis MD 21403 > > > From j47@pacbell.net Mon, 14 Aug 2000 16:26:49 -0700 Date: Mon, 14 Aug 2000 16:26:49 -0700 From: Jim Fennacy j47@pacbell.net Subject: [tulip] spec-helper not found. I am running Mandrake 7.1, with ALL packages installed, with a (new) LinkSys LNE100TX 4.1 NIC. I just downloaded ftp://ftp.scyld.com/pub/network/netdriver-2.0.src.rpm from http://www.scyld.com/network/updates.html and am trying to build the RPM: rpm -i netdriver-2.0.src.rpm cd /usr/src/RPM rpm -bb SPECS/netdriver.spec Compilation completes successfully. I get the following error after compilation: /var/tmp/rpm-tmp.xxxxx: /usr/share/spec-helper/spec-helper: No such file or directory Bad exit status from /var/tmp/rpm-tmp.xxxxx (%install) I cannot find ANY information about spec-helper on Mandrake's site. Neither can I find any info about it on the Applications CD. TIA - Jim. From ademetriojr@yahoo.com Mon, 14 Aug 2000 21:04:40 -0700 (PDT) Date: Mon, 14 Aug 2000 21:04:40 -0700 (PDT) From: Altair Demetrio Jr. ademetriojr@yahoo.com Subject: [tulip] Network Everywhere Fast Ethernet (NC100 v2) Can anyone tell me where to get the driver for the "Network Everywhere Fast Ethernet (NC100 v2)" and how to set it up. I tried to use LinkSys LNE100XT. I had no problem compiling it but I had several errors when recompiling the kernel with the following command: # make modules Thanks A. Demetrio Jr. __________________________________________________ Do You Yahoo!? Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ From x@xman.org Mon, 14 Aug 2000 21:48:41 -0700 Date: Mon, 14 Aug 2000 21:48:41 -0700 From: Christopher Smith x@xman.org Subject: [tulip] Linksys LNE100TX version 4.0 (more information) --On Friday, August 11, 2000 6:20 PM -0500 Jon Schewe wrote: > I don't have a 2.4preX kernel installed, I'm using 2.2.16 SMP. I do have > the new 2.0 drivers installed from the tulip web site though. Are the > 2.4preX drivers any different than the ones on the tulip website? They're very different. Different maintainer. --Chris From jpschewe@eggplant.mtu.net 14 Aug 2000 23:59:28 -0500 Date: 14 Aug 2000 23:59:28 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Linksys LNE100TX version 4.0 (more information) Christopher Smith writes: > --On Friday, August 11, 2000 6:20 PM -0500 Jon Schewe > wrote: > > I don't have a 2.4preX kernel installed, I'm using 2.2.16 SMP. I do have > > the new 2.0 drivers installed from the tulip web site though. Are the > > 2.4preX drivers any different than the ones on the tulip website? > > They're very different. Different maintainer. Ok, I'll give it a try. Where do I find them? Also can I run them under a 2.2.16 kernel? -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From x@xman.org Mon, 14 Aug 2000 21:58:46 -0700 Date: Mon, 14 Aug 2000 21:58:46 -0700 From: Christopher Smith x@xman.org Subject: [tulip] Linksys LNE100TX version 4.0 (more information) --On Monday, August 14, 2000 11:59 PM -0500 Jon Schewe wrote: > Christopher Smith writes: >> --On Friday, August 11, 2000 6:20 PM -0500 Jon Schewe >> wrote: >> > I don't have a 2.4preX kernel installed, I'm using 2.2.16 SMP. I do >> > have the new 2.0 drivers installed from the tulip web site though. >> > Are the 2.4preX drivers any different than the ones on the tulip >> > website? >> >> They're very different. Different maintainer. > > Ok, I'll give it a try. Where do I find them? Also can I run them under > a 2.2.16 kernel? They are standard with the 2.4preX kernel. If you aren't confident about setting up 2.4 I wouldn't bother, as it's not worth the stress. On average, the scyld drivers seem to work better. --Chris From jpschewe@eggplant.mtu.net 15 Aug 2000 00:10:56 -0500 Date: 15 Aug 2000 00:10:56 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Linksys LNE100TX version 4.0 (more information) Christopher Smith writes: > --On Monday, August 14, 2000 11:59 PM -0500 Jon Schewe > wrote: > > Christopher Smith writes: > >> --On Friday, August 11, 2000 6:20 PM -0500 Jon Schewe > >> wrote: > >> > I don't have a 2.4preX kernel installed, I'm using 2.2.16 SMP. I do > >> > have the new 2.0 drivers installed from the tulip web site though. > >> > Are the 2.4preX drivers any different than the ones on the tulip > >> > website? > >> > >> They're very different. Different maintainer. > > > > Ok, I'll give it a try. Where do I find them? Also can I run them under > > a 2.2.16 kernel? > > They are standard with the 2.4preX kernel. If you aren't confident about > setting up 2.4 I wouldn't bother, as it's not worth the stress. On average, > the scyld drivers seem to work better. Well so far the scyld drivers haven't worked for me because of the bug with autonegotiation problems. If you say the 2.4preX kernel drivers aren't any better I doubt they'll work then, unless they're closer to the FreeBSD drivers. -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From ademetriojr@yahoo.com Tue, 15 Aug 2000 00:12:08 -0700 (PDT) Date: Tue, 15 Aug 2000 00:12:08 -0700 (PDT) From: Altair Demetrio Jr. ademetriojr@yahoo.com Subject: [tulip] device or resource busy? When I boot up Linux I see this message: /lib/modules/kernel_version/net/tulip.o: init_module: Device or resource busy What should I do? A. Demetrio Jr. __________________________________________________ Do You Yahoo!? Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ From markgray@iago.nac.net 15 Aug 2000 03:33:55 -0400 Date: 15 Aug 2000 03:33:55 -0400 From: Mark Gray markgray@iago.nac.net Subject: [tulip] device or resource busy? "Altair Demetrio Jr." writes: > When I boot up Linux I see this message: > > /lib/modules/kernel_version/net/tulip.o: init_module: > Device or resource busy > > What should I do? This is the error message I got when trying to use the stock tulip drivers with a newer card (a LinkSys LNE100TX Version 4.1) -- upgrade to the latest driver from scyld: http://www.scyld.com/network/updates.html http://www.scyld.com/network/tulip.html ftp://ftp.scyld.com/pub/network/netdriver-2.0-3.src.rpm If this is not the case, give more information (card type, kernel version, distribution version ... etc. etc.) Hope this helps. From jpschewe@eggplant.mtu.net 15 Aug 2000 08:28:30 -0500 Date: 15 Aug 2000 08:28:30 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Linksys LNE100TX version 4.0 (more information) Christopher Smith writes: > --On Monday, August 14, 2000 11:59 PM -0500 Jon Schewe > wrote: > > Christopher Smith writes: > >> --On Friday, August 11, 2000 6:20 PM -0500 Jon Schewe > >> wrote: > >> > I don't have a 2.4preX kernel installed, I'm using 2.2.16 SMP. I do > >> > have the new 2.0 drivers installed from the tulip web site though. > >> > Are the 2.4preX drivers any different than the ones on the tulip > >> > website? > >> > >> They're very different. Different maintainer. > > > > Ok, I'll give it a try. Where do I find them? Also can I run them under > > a 2.2.16 kernel? > > They are standard with the 2.4preX kernel. If you aren't confident about > setting up 2.4 I wouldn't bother, as it's not worth the stress. On average, > the scyld drivers seem to work better. I grabbed 2.4.0-test6 and poked around the tulip driver a bit and the web address that it points to is a page that says it's been moved and that reloads to the scyld page. -- Jon Schewe http://eggplant.mtu.net/~jpschewe jpschewe@eggplant.mtu.net From j47@pacbell.net Tue, 15 Aug 2000 07:41:31 -0700 Date: Tue, 15 Aug 2000 07:41:31 -0700 From: Jim Fennacy j47@pacbell.net Subject: [tulip] Help installing driver on Mandrake 7.1 I am running Mandrake 7.1, with ALL packages installed, with a (new) LinkSys LNE100TX 4.1 NIC. I just downloaded ftp://ftp.scyld.com/pub/network/netdriver-2.0.src.rpm from http://www.scyld.com/network/updates.html and am trying to build the RPM: rpm -i netdriver-2.0.src.rpm cd /usr/src/RPM rpm -bb SPECS/netdriver.spec Compilation completes successfully. I get the following error after compilation: /var/tmp/rpm-tmp.xxxxx: /usr/share/spec-helper/spec-helper: No such file or directory Bad exit status from /var/tmp/rpm-tmp.xxxxx (%install) I cannot find ANY information about spec-helper on Mandrake's site. Neither can I find any info about it on the Applications CD. What to do? TIA - Jim. From a@superbruger.dk Wed, 16 Aug 2000 01:58:10 GMT Date: Wed, 16 Aug 2000 01:58:10 GMT From: a@superbruger.dk a@superbruger.dk Subject: [tulip] Tulip or Realtek driver for Accton EN1207D-TX ?? Seemingly, Accton has changed the chip on their adapter to a Realtek 8139 clone, while the product name remains unchanged. I have bought and returned a few Accton EN1207D-TX cards when I discovered that they contained a chip called MPX EN5038A and not DEC 21x4x . Expecting that this might be a DEC compatible chip, I downloaded a driver from www.accton.com.tw. Thedriver is called en1207.c and is contained in a zip file ( 1207dlinux.zip ). The source code file reveals the following: /* rtl8139.c: A RealTek RTL8129/8139 Fast Ethernet driver for Linux. */ /* Written 1997-1998 by Donald Becker. This software may be used and distributed according to the terms of the GNU Public License, incorporated herein by reference. All other rights reserved. This driver is for boards based on the RTL8129 and RTL8139 PCI ethernet chips. The author may be reached as becker@CESDIS.gsfc.nasa.gov, or C/O Center of Excellence in Space Data and Information Sciences Code 930.5, Goddard Space Flight Center, Greenbelt MD 20771 Support and updates available at http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html Twister-tuning code contributed by Kinston . */ static const char *version = "rtl8139.c:v0.99B 4/7/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html\n"; .... Well, I sure don't know much about drivers, but this is NOT a tulip driver. I think it is a customized Realtek driver, and hence I conclude that the Accton EN1207 network adapter contains a rtl 8139 compatible chip. I assume that a rtl8139 driver can not be used with a DEC 21x4x based network adapter, with or without customization. So I arrest my case, concluding that Accton has abandoned the DEC 21x4x and is now using a Realtek 8139 clone on this adapter. This is problematic, since all Linux documentation states that this net. adapter should use a tulip driver. If my conclusions are correct, the documentation should be corrected as soon as possible. All my net. adapters are based on Realtek chips and I have stuck to that until I experienced problems that may be due to the fact that the rtl8139 driver is not yet stable. Therefore I need a net. adapter with a stable driver such as tulip or x4x5 (are they really stable ? ) . :-> Why buy Realtek whel you can buy a clone for twice the price ! :-> Using this information, the staff at the local computerstore has decided that there is no reason to sell an Accton adapter that is basically a 8139 clone, when they also can sell a 8139 based no_name adapter at half the price. Then my question to you folks at the Tulip mailing list: Is there an affordable 10/100 Mbit (no Intel no 3Com) network adapter, which has a STABLE driver for Linux. Sincerely, Anna Amandsen, Denmark. From f8163@csx.com Tue, 15 Aug 2000 22:19:25 -0400 (EDT) Date: Tue, 15 Aug 2000 22:19:25 -0400 (EDT) From: Mark Neill MIDTIER f8163@csx.com Subject: [tulip] Tulip or Realtek driver for Accton EN1207D-TX ?? You're right, the EN1207 (and other 12XX chips) are RTL8139 chips, as I found out in my HP system.... As far as stability, I have no problems with my RTL card...it's running as the inside interface on a 3-computer network connected to my cablemodem at home, and I have yet to have a problem with it after 2 months of pounding on it. --Mark Mark Neill Enterprise Backup & UNIX Administrator CSX Technology Mark_Neill@csx.com On Wed, 16 Aug 2000 a@superbruger.dk wrote: > Seemingly, Accton has changed the chip on their adapter to a Realtek 8139 > clone, while the product name remains unchanged. I have bought and returned > a few Accton EN1207D-TX cards when I discovered that they contained a chip > called MPX EN5038A and not DEC 21x4x . Expecting that this might be a DEC > compatible chip, I downloaded a driver from www.accton.com.tw. Thedriver > is called en1207.c and is contained in a zip file ( 1207dlinux.zip ). > > The source code file reveals the following: > > /* rtl8139.c: A RealTek RTL8129/8139 Fast Ethernet driver for Linux. */ > /* > Written 1997-1998 by Donald Becker. > > This software may be used and distributed according to the terms > of the GNU Public License, incorporated herein by reference. > All other rights reserved. > > This driver is for boards based on the RTL8129 and RTL8139 PCI ethernet > > chips. > > The author may be reached as becker@CESDIS.gsfc.nasa.gov, or C/O > Center of Excellence in Space Data and Information Sciences > Code 930.5, Goddard Space Flight Center, Greenbelt MD 20771 > > Support and updates available at > http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html > > Twister-tuning code contributed by Kinston . > */ > > static const char *version = > "rtl8139.c:v0.99B 4/7/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html\n"; > > > .... > > > Well, I sure don't know much about drivers, but this is NOT a tulip driver. > I think it is a customized Realtek driver, and hence I conclude that the > Accton EN1207 network adapter contains a rtl 8139 compatible chip. > > I assume that a rtl8139 driver can not be used with a DEC 21x4x based network > adapter, with or without customization. > > So I arrest my case, concluding that Accton has abandoned the DEC 21x4x and > is now using a Realtek 8139 clone on this adapter. > > This is problematic, since all Linux documentation states that this net. > adapter should use a tulip driver. > If my conclusions are correct, the documentation should be corrected as soon > as possible. > > All my net. adapters are based on Realtek chips and I have stuck to that > until I experienced problems that may be due to the fact that the rtl8139 > driver is not yet stable. Therefore I need a net. adapter with a stable driver > such as tulip or x4x5 (are they really stable ? ) . > > :-> > Why buy Realtek whel you can buy a clone for twice the price ! > :-> > > Using this information, the staff at the local computerstore has decided > that there is no reason to sell an > Accton adapter that is basically a 8139 clone, when they also can sell a > 8139 based no_name adapter at half the price. > > Then my question to you folks at the Tulip mailing list: > Is there an affordable 10/100 Mbit (no Intel no 3Com) network adapter, which > has a STABLE driver for Linux. > > > Sincerely, Anna Amandsen, Denmark. > > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip > From a.lewin@ic.ac.uk Wed, 16 Aug 2000 14:25:19 +0100 Date: Wed, 16 Aug 2000 14:25:19 +0100 From: Lewin, A a.lewin@ic.ac.uk Subject: [tulip] tulip-diag on linux/PPC Hi, just a quick note to ask - has anyone successfully compiled Donald Becker's tulip-diag.c (ftp://ftp.scyld.com/pub/diag/tulip-diag.c) for PPC architecture? I ask because I am having trouble doing it! I suspect stupidity. More details will probably follow as I am tearing my hair out over a LiteOn PNIC card... cheers, Adam. From lech.szychowski@pse.pl Wed, 16 Aug 2000 16:01:09 +0200 Date: Wed, 16 Aug 2000 16:01:09 +0200 From: Lech Szychowski lech.szychowski@pse.pl Subject: [tulip] Re: tulip.c vs ANA6944TX > > To: linux-tulip@beowulf.org, linux-tulip-bug@beowulf.org, > > linux-kernel@vger.rutgers.edu, linux-net@vger.rutgers.edu > > You should limit this to linux-tulip or linux-tulip-bug (aliases for > tulip@scyld.com and tulip-bug@scyld.com), unless it's a problem with the > pre-2.4 code in which case linux-kernel@vger.rutgers.edu is appropriate. My ANA6944TX stopped working int 2.4pre somewhere between test1pre3 and test3. Replacing the whole ./drivers/net/tulip directory with the one from test1pre3 (version 0.9.4.3), as suggested by Jeff Garzik, brings the network back to life. Any clues? -- Leszek. -- lech7@pse.pl 2:480/33.7 -- REAL programmers use INTEGERS -- -- speaking just for myself... From ademetriojr@yahoo.com Thu, 17 Aug 2000 11:26:17 -0700 (PDT) Date: Thu, 17 Aug 2000 11:26:17 -0700 (PDT) From: Altair Demetrio Jr. ademetriojr@yahoo.com Subject: [tulip] tulip device id? How is the "Network Everywhere Fast Ethernet (NC100 v2)" identified by the kernel configuration? What is its name? A. Demetrio Jr. __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ From Ed@RGTravel.com Thu, 17 Aug 2000 15:50:14 -0600 Date: Thu, 17 Aug 2000 15:50:14 -0600 From: Ed Heron Ed@RGTravel.com Subject: [tulip] multiple lne100tx's I'm trying to put multiple lne100tx's into my "new Linux router". I've got slackware 7.1 (kernel 2.2.16) and I compiled the tulip driver into the kernel. The first one worked pretty well. When I put the second one in, it appeared to work until I hooked another computer to the new segment. I then looked at the following information. It appears to have a problem seeing the EEPROM on the second card and mis-identifies the IRQ. Any suggestions? The messages from kernel: Aug 17 10:57:09 new kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov Aug 17 10:57:09 new kernel: eth0: Lite-On PNIC-II rev 37 at 0xe800, 00:A0:CC:34:E3:50, IRQ 11. Aug 17 10:57:09 new kernel: eth1: Lite-On PNIC-II rev 37 at 0xec00, EEPROM not present, 00:A0:CC:34:E3:51, IRQ 11. when I cat /proc/pci, I get: Bus 0, device 8, function 0: Ethernet controller: LiteOn Unknown device (rev 37). Vendor id=11ad. Device id=c115. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. Min Gnt=8.Max Lat=56. I/O at 0xe800 [0xe801]. Non-prefetchable 32 bit memory at 0xea001000 [0xea001000]. Bus 0, device 9, function 0: Ethernet controller: LiteOn Unknown device (rev 37). Vendor id=11ad. Device id=c115. Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=64. Min Gnt=8.Max Lat=56. I/O at 0xec00 [0xec01]. Non-prefetchable 32 bit memory at 0xea000000 [0xea000000]. After I configure the interfaces, I run ifconfig and get: eth0 Link encap:Ethernet HWaddr 00:A0:CC:34:E3:50 inet addr:192.168.201.17 Bcast:192.168.201.255 Mask:255.255.255.0 IPX/Ethernet 802.3 addr:6A40C901:00A0CC34E350 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21681 errors:0 dropped:0 overruns:0 frame:0 TX packets:8989 errors:1 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0xe800 eth1 Link encap:Ethernet HWaddr 00:A0:CC:34:E3:51 inet addr:192.168.203.1 Bcast:192.168.203.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:1832 dropped:1477572811 overruns:0 frame:0 TX packets:0 errors:2004 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0xec00 when I run tulip-diag, I get: tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Lite-On PNIC-II adapter at 0xe800. Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex. Transmit started, Receive started, full-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 256. The NWay status register is 000000cc. The current PNIC-II MAC address is 00:a0:cc:34:e3:50 (a000a000 34cc50e3). The current PNIC-II WOL address is 00:a0:cc:34:e3:50. Internal autonegotiation state is 'Autonegotiation disabled'. Index #2: Found a Lite-On PNIC-II adapter at 0xec00. Port selection is 100mbps-SYM/PCS 100baseTx scrambler, full-duplex. Transmit started, Receive started, full-duplex. The Rx process state is 'Transferring Rx frame into memory'. The Tx process state is 'Closing Tx descriptor'. PCI bus error!: Unknown 7. The transmit unit is set to store-and-forward. Interrupt sources are pending! CSR5 is ffffffff. Tx done indication. Tx complete indication. Tx out of buffers indication. Transmit Jabber indication. Link passed indication. Tx FIFO Underflow indication. Rx Done indication. Receiver out of buffers indication. Receiver stopped indication. Receiver jabber indication. Link changed indication. Timer expired indication. Link failed indication. PCI bus error indication. Early Rx indication. The NWay status register is ffffffff. The current PNIC-II MAC address is ff:ff:ff:ff:ff:ff (ffffffff ffffffff). The current PNIC-II WOL address is ff:ff:ff:ff:ff:ff. Internal autonegotiation state is 'Autonegotiation disabled'. Use '-a' or '-aa' to show device registers, '-e' to show EEPROM contents, -ee for parsed contents, or '-m' or '-mm' to show MII management registers. From MSmith@webtonetech.com Fri, 18 Aug 2000 10:57:29 -0400 Date: Fri, 18 Aug 2000 10:57:29 -0400 From: Michael Smith MSmith@webtonetech.com Subject: [tulip] Compilation of tulip.c with Redhat Pinstripe Beta I have one of those new Linksys LNE100TX v4.1 cards(could be probelmatic) and I just pulled down the tulip.c file from the test area. I am getting the following errors when attempting to compile the test tulip.c file. Any ideas on how to resolve them. I am using the compilation parameters from the Linksys home page.... In file included from /usr/include/asm/hardirq.h:7, from /usr/include/linux/interrupt.h:46, from tulip.c:149: /usr/include/linux/irq.h:53: requested alignment is not a constant In file included from /usr/include/linux/interrupt.h:46, from tulip.c:149: /usr/include/asm/hardirq.h:13: requested alignment is not a constant In file included from tulip.c:149: /usr/include/linux/interrupt.h:153: requested alignment is not a constant In file included from tulip.c:151: /usr/include/linux/netdevice.h:151: requested alignment is not a constant In file included from tulip.c:151: /usr/include/linux/netdevice.h:448: requested alignment is not a constant tulip.c: In function `tulip_open': tulip.c:1460: structure has no member named `tbusy' tulip.c:1461: structure has no member named `start' tulip.c: In function `tulip_start_xmit': tulip.c:2565: structure has no member named `tbusy' tulip.c:2598: structure has no member named `tbusy' tulip.c: In function `tulip_interrupt': tulip.c:2617: structure has no member named `interrupt' tulip.c:2621: structure has no member named `interrupt' tulip.c:2702: structure has no member named `tbusy' tulip.c:2706: structure has no member named `tbusy' tulip.c:2707: `NET_BH' undeclared (first use in this function) tulip.c:2707: (Each undeclared identifier is reported only once tulip.c:2707: for each function it appears in.) tulip.c:2796: structure has no member named `interrupt' tulip.c: In function `tulip_close': tulip.c:2942: structure has no member named `start' tulip.c:2943: structure has no member named `tbusy' tulip.c: In function `tulip_get_stats': tulip.c:2982: structure has no member named `start' tulip.c: In function `set_rx_mode': tulip.c:3225: structure has no member named `tbusy' Michael A. Smith From becker@scyld.com Thu, 17 Aug 2000 19:48:35 -0400 (EDT) Date: Thu, 17 Aug 2000 19:48:35 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] multiple lne100tx's On Thu, 17 Aug 2000, Ed Heron wrote: > Aug 17 10:57:09 new kernel: eth0: Lite-On PNIC-II rev 37 at 0xe800, > 00:A0:CC:34:E3:50, IRQ 11. > Aug 17 10:57:09 new kernel: eth1: Lite-On PNIC-II rev 37 at 0xec00, EEPROM > not present, 00:A0:CC:34:E3:51, IRQ 11. This card isn't working correctly. > Index #2: Found a Lite-On PNIC-II adapter at 0xec00. ... > Interrupt sources are pending! CSR5 is ffffffff. Check that it's fully inserted into the PCI slot. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From paulr@optimation.com.au Mon, 21 Aug 2000 15:12:42 +1000 Date: Mon, 21 Aug 2000 15:12:42 +1000 From: Paul Rosham paulr@optimation.com.au Subject: [tulip] Compaq/Digital DE504-BA Support Does the tulip driver support this card well? thanks, -- Paul Rosham paulr@optimation.com.au Principal Consultant Optimation Software Engineering Pty Ltd Level 9 West, 608 St Kilda Rd, Melbourne VIC 3004, Australia Tel: +61 3 9525 2111 Fax: +61 3 9521 1733 From murray@pa.dec.com Mon, 21 Aug 2000 00:27:35 -0700 Date: Mon, 21 Aug 2000 00:27:35 -0700 From: Hal Murray murray@pa.dec.com Subject: [tulip] Compaq/Digital DE504-BA Support > Does the tulip driver support this card well? I'm pretty sure that the DE504-BA looks to software just like 4 DE500-BA behind a PCI-PCI bridge. I've always been able to get them to work, but it might take some fiddling. Note that the DE500-BA is significantly different from the DE500-AA. (21143 vs 21140.) From poly@mail.sisna.com Mon, 21 Aug 2000 15:41:02 -0600 Date: Mon, 21 Aug 2000 15:41:02 -0600 From: Poly poly@mail.sisna.com Subject: [tulip] Linksys Network Card not working Hi Zhu, I had a hard time with this setting, but at the end, it was very simple and it is working really well. Here is what I can about it now: 1. First, check out your version of the Linksys LNE 100 TX card. There are many version, and what follows applies to Version 2 of the card, the one that I have. I did not try other versions, so I really cannot say much about them. 2. Use Red Hat 6.2 preferably because the driver in 6.2 works well with the card. If you are using 6.1 or 6.0, you might have to download the driver and compile it. I won't really advise that. 3. I was doing all this for practice at home, and I have only 2 PCs. Therefore, there was no gateway, and no need for one, so when I was entering the network parameters, I left the gateway part blank. 4. For a long time, netconf was telling me that my card was active while in fact it wasn't. The problem was, there was no IRQ assigned. You know that from doing cat /var/log/messages | grep eth0 on a fresh install. If it gives a value for IRQ other than 0, you don't need to touch the BIOS. To get the system to assign an IRQ to the card, I had to make a change in the BIOS: While the computer is starting and showing that blue HP screen, type F1. (Most computers show you a starting screen with type F1 to enter setup. Instead, that systems just show the HP screen. That is really stupid). In the BIOS, there is a screen where it says OS=... I changed that from Windows to Other. I think that was the most important part. I hope this helps. Otherwise, when I get home, I can get more details about the BIOS, and the network parameters for you. Thanks. Poly. ---------- Original Message ---------------------------------- From: Yanglong Zhu Date: Fri, 18 Aug 2000 22:33:41 -0700 >Hi Poly, > >I have exactly the same problem as yours on the same model of computer (as described in your message below). I wander what did you do to resolve the Linksys card problem? Or have you solved the issue yet? >Could enlighten me on the issue? > >Thanks > >Yanglong Zhu > >Poly wrote: > >> Dear Tulip List Members, >> >> I am hoping that someone can help me with the following: >> >> I have a Lynksys LNE 100 TX Fast Ethernet Adaptor (Version 2 with >> WakeUp-On-Line feature) on my PC, an HP 6640C, which has a >> AMD K6-2/500MHz 3DNow Processor. I have set it up as a Dual Boot, >> Windows98 or Linux, Red Hat 6.2. >> >> As a Windows Machine, there is no problem, and it talks well with my >> other machine, an old Pentium 166 with Windows95. >> >> When it boots as Linux Machine, the Red Hat 6.2 recognises the Network Card, uses tulip.c for it, and correctly sets the I/O 1400-14ff. But it does not work. When I do the ifconfig command, it says: >> SIOCSIFFLAGS: Resource Temporary Unavailable. >> It did not make much sense to try route, but I did and it also said: >> SIOCADDRT: Network is down. >> >> My question is, what to do now? I will be very grateful for any answer. >> I read as much as I could understand on the problem, and also checked my system. Below is more information that I found useful, on the IRQs and in the /var/log/messages. Thanks very much for the help. >> Poly. Please read on... >> >> In /var/log/messages, I found the following suspicious lines: >> The PCI BIOS has not enabled the device at 0/96 >> updating PCI Command 0083 to 0087 >> tulip.c :v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov >> eth0: Lite-on PNIC-II rev 37 at 0x1400, 00:A0:CC >> :37:95:B8, IRQ 0 >> >> Below is the Interrupt Request from Red Hat Information >> IRQ CPUO >> 0 51951 XT-PIC timer >> 1 36 XT-PIC keyboard >> 2 0 XT-PIC cascade >> 8 1 XT-PIC rtc >> 12 6684 XT-PIC PS/2 Mouse >> 13 0 XT-PIC fpu >> 14 100231 XT-PIC ide0 >> 15 3348 XT-PIC ide1 >> NMI 0 >> >> >From cat /proc/pci I found: >> IRQ 9 VGA Adapter >> IRQ 11 USB >> >> Also from some other file: >> IRQ 4 ttyS00 at 0x03f8 >> >> On the Windows98 side, the IRQs are as follows: >> 00 Timer >> 01 Keyboard >> 02 Programmable Interrupt Control >> 03 Com2 >> 04 Com1 >> 06 Standard Floppy >> 07 Printer Port LPT1 >> 08 System CMOS/Real Time Clock >> 09 ACPI IRQ Holder for PCI IRQ Steering >> 09 Linksys LNE 100TX Fast Ethernet Adaptor >> 09 SiS 530 (VGA Adaptor) >> 10 ACPI IRQ Holder for PCI IRQ Steering >> 10 Conexant PCI Modem Emulator >> 10 Master Riptide PCI Audio Device >> 11 ACPI IRQ Holder for PCI IRQ Steering >> 11 ACPI IRQ Holder for PCI IRQ Steering - again >> 11 SiS 7001 PCI to USB Open Host Controller >> 11 SCI IRQ used by ACPI bus >> 12 PS/2 compatible Mouse Port >> 14 SiS 5513 Dual PCI IDE Controller >> 14 Primary IDE Dual FIFO >> 15 SiS 5513 Dual PCI IDE Controller >> 15 Secondary IDE Controller Dual FIFO >> >> Thanks again. >> >> >> >> _______________________________________________ >> tulip mailing list >> tulip@scyld.com >> http://www.scyld.com/mailman/listinfo/tulip > > From david.ogborn@utoronto.ca Fri, 25 Aug 2000 00:42:26 CDT Date: Fri, 25 Aug 2000 00:42:26 CDT From: David Ogborn david.ogborn@utoronto.ca Subject: [tulip] MX98715 AEC Problems Hello, I'm having some problems getting an MX98715-AEC based NIC to work with kernel version 2.2.16 and tulip driver version 0.92k (from the .../test/ directory at the scyld.com website). Looking back through the archives of this list, I see that similar problems were encountered by a few back in October/November of 1999, but the thread seems to have dissappeared. Any help people can offer to the problem described below would be greatly appreciated! In brief, when hooked to a 10Mbaud hub, I have no problems with the card. When I instead connect it to my Terayon cable modem (connected to the Internet), which I gather is some sort of 100MBaud device, it has trouble receiving packets. In more detail: #insmod pci-scan #insmod tulip debug=6 tulip.c:v0.92k 8/14/2000 Written by Donald Becker http://www.scyld.com/network/tulip.html eth0: Macronix 98715 PMAC rev 37 at 0xc100e000, 00:80:C6:F1:EA:71, IRQ 11. #ifconfig eth0 netmask up eth0: tulip_open() irq 11. eth0: Done tulip_open(), CSR0 fff88000, CSR5 e4520000, CSR6 01a82202. eth0: interrupt csr5=0xe4670005 new csr5=0xe4660000. eth0: exiting interrupt, csr5=0xe4660000. ..(last two lines repeated 4 more times)... eth0: MXIC negotiation status 000050ca ..(this last line recurs every minute or so without user intervention)... ..(the results of #ifconfig and #route are as they should be)... #ping -c 1 ..(ping transmits 1 packet, none are received in return)... ..(but I can see on the cable modem lights that a send was followed by a receive)... eth0: interrupt csr5=0xe4670004 new csr5=0xe4660000. eth0: exiting interrupt, csr5=0xe4660000. eth0: interrupt csr5=0xe4670040 new csr5=0xe4660000. In tulip_rx(), entry 0 00400328. eth0: In tulip_rx(), entry 0 00400328. eth0: exiting interrupt, csr5=0xe4660000. eth0: interrupt csr5=0xe4670004 new csr5=0xe4660000. eth0: exiting interrupt, csr5=0xe4660000. #tulip-diag tulip-diag.c:v2.03... .. found ... adapter at 0x1000. Port selection is 10mbps-serial 100baseTx scrambler, full-duplex. Transmit started, receive started, full duplex. .Rx... waiting for packets.. .Tx... idle... the transmit unit is set to store and forward. Thanks in advance for any help! sincerely, David Ogborn Toronto, Canada. From henri.sack@wanadoo.fr Fri, 25 Aug 2000 09:16:34 +0200 Date: Fri, 25 Aug 2000 09:16:34 +0200 From: Henri Sack henri.sack@wanadoo.fr Subject: [tulip] Problem with tulip on Compaq Presario 1800 Bridging up eth0 card fail with my computer with the following message: Aug 25 08:29:47 presario kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov Aug 25 08:29:47 presario kernel: eth0: Digital DS21143 Tulip rev 65 at 0xfc00, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11. Aug 25 08:29:47 presario kernel: eth0: Missing EEPROM, this interface may not work correctly! Aug 25 08:29:47 presario kernel: eth0: Tx hung, 10 vs. 0. Aug 25 08:29:47 presario kernel: eth0: 21140 transmit timed out, status ffffffff, SIA ffffffff ffffffff ffffffff ffffffff, resetting... Aug 25 08:29:47 presario kernel: eth0: Tx hung, 11 vs. 0. Aug 25 08:29:47 presario kernel: eth0: 21140 transmit timed out, status ffffffff, SIA ffffffff ffffffff ffffffff ffffffff, resetting... Aug 25 08:29:47 presario kernel: eth0: Tx hung, 11 vs. 0. Aug 25 08:29:47 presario kernel: eth0: 21140 transmit timed out, status ffffffff, SIA ffffffff ffffffff ffffffff ffffffff, resetting... Aug 25 08:29:47 presario kernel: eth0: Tx hung, 12 vs. 0. Aug 25 08:29:47 presario kernel: eth0: 21140 transmit timed out, status ffffffff, SIA ffffffff ffffffff ffffffff ffffffff, resetting... How could I overcome this problem ? Regards Henri From becker@scyld.com Fri, 25 Aug 2000 10:33:23 -0400 (EDT) Date: Fri, 25 Aug 2000 10:33:23 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Problem with tulip on Compaq Presario 1800 On Fri, 25 Aug 2000, Henri Sack wrote: > Subject: [tulip] Problem with tulip on Compaq Presario 1800 Is this a laptop or desktop? > Bridging up eth0 card fail with my computer with the following message: > > Aug 25 08:29:47 presario kernel: tulip.c:v0.91g-ppc 7/16/99 > becker@cesdis.gsfc.nasa.gov > Aug 25 08:29:47 presario kernel: eth0: Digital DS21143 Tulip rev 65 at > 0xfc00, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11. > Aug 25 08:29:47 presario kernel: eth0: Missing EEPROM, this interface may > not work correctly! ... > Aug 25 08:29:47 presario kernel: eth0: 21140 transmit timed out, status > ffffffff, SIA ffffffff ffffffff ffffffff ffffffff, resetting... The chip isn't activated. I suspect that it's a PCI power management issue == the chip is likely in ACPI D3 state. This typically occurs when the machine is warm booted from Windows. You can verify this with the pci-config program from http://www.scyld.com/diag/index.html A solution is to use the updated driver and pci-scan support. The pci-scan code configures the PCI power management registers. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From david@kalifornia.com Fri, 25 Aug 2000 09:28:19 -0700 Date: Fri, 25 Aug 2000 09:28:19 -0700 From: David Ford david@kalifornia.com Subject: [tulip] Problem with tulip on Compaq Presario 1800 This is a multi-part message in MIME format. --------------9A353C7CDA68F6AA931BC2C8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This is a laptop. I have one. It has a built in i82557 (eepro100) card. btw, there was a problem with tulips and 2.4 a few weeks ago, I would suggest Henri update to 2.4.0-test7 final if he is indeed using 2.4. Donald Becker wrote: > On Fri, 25 Aug 2000, Henri Sack wrote: > > > Subject: [tulip] Problem with tulip on Compaq Presario 1800 > > Is this a laptop or desktop? -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." --------------9A353C7CDA68F6AA931BC2C8 Content-Type: text/x-vcard; charset=us-ascii; name="david.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for David Ford Content-Disposition: attachment; filename="david.vcf" begin:vcard n:Ford;David x-mozilla-html:TRUE org: adr:;;;;;; version:2.1 email;internet:david@kalifornia.com title:Blue Labs Developer x-mozilla-cpt:;-12480 fn:David Ford end:vcard --------------9A353C7CDA68F6AA931BC2C8-- From jeremy@xxedgexx.com Fri, 25 Aug 2000 21:09:18 -0400 (EDT) Date: Fri, 25 Aug 2000 21:09:18 -0400 (EDT) From: Jeremy Hansen jeremy@xxedgexx.com Subject: [tulip] why does tulip ignore my kernel options? I havew tulip built into my kernel. It's a dual port card and I want it to initialize using the first port at eth1 and the second port as eth2. So, I'm passing these paramters: ether=0,0,0,eth1 ether=0,0,0x3080,eth2 but it refuses to listen. It still initializes the card as eth0 and eth1. I have a eepro also in the machine, but it is not compiled into the kernel. My goal is this: eth0 eepro eth1 tulip eth2 tulip Any help would be appreciated. -jeremy http://www.xxedgexx.com * jeremy@xxedgexx.com ---------------------------------------------- From KevinSCarr@aol.com Sat, 26 Aug 2000 00:14:23 EDT Date: Sat, 26 Aug 2000 00:14:23 EDT From: KevinSCarr@aol.com KevinSCarr@aol.com Subject: [tulip] Tulip: PCI Fatal Bus Error I have been trying to set up a LinkSys Network Everywhere 10/100 Ethernet Card. Model NC100 Version 2.0. After building the Binary files, and installing them, I get the following error: eth0: PCI Fatal Bus Error, fc67e050 The following is what I get from an ifconfig command: eth0 Link encap:Ethernet HWaddr 00:00:78:02:F3:98 inet addr:192.161.21.1 Bcast:192.161.21.255 Mask:255.255.255.0 UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:10 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:42 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 Thanks for any help in advance. Scott From becker@scyld.com Sat, 26 Aug 2000 00:54:19 -0400 (EDT) Date: Sat, 26 Aug 2000 00:54:19 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] why does tulip ignore my kernel options? On Fri, 25 Aug 2000, Jeremy Hansen wrote: > I havew tulip built into my kernel. It's a dual port card and I want it > to initialize using the first port at eth1 and the second port as eth2. > > So, I'm passing these paramters: > > ether=0,0,0,eth1 ether=0,0,0x3080,eth2 > > but it refuses to listen. It still initializes the card as eth0 and eth1. The Ethernet interface names are assigned in order. With some kernels the following might work: ether=0,-1,eth0 ether=0,0,0,eth1 Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From becker@scyld.com Sat, 26 Aug 2000 01:01:40 -0400 (EDT) Date: Sat, 26 Aug 2000 01:01:40 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Tulip: PCI Fatal Bus Error On Sat, 26 Aug 2000 KevinSCarr@aol.com wrote: > I have been trying to set up a LinkSys Network Everywhere 10/100 Ethernet > Card. Model NC100 Version 2.0. > > After building the Binary files, and installing them, I get the following > error: > eth0: PCI Fatal Bus Error, fc67e050 Yup, that's a PCI bus errors. It's one of bit 27:25 error type 000 parity error 001 master abort 010 target abort So it's probably a parity error. Try moving the card to a different PCI slot. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From henri.sack@wanadoo.fr Sat, 26 Aug 2000 10:03:52 +0200 Date: Sat, 26 Aug 2000 10:03:52 +0200 From: Henri Sack henri.sack@wanadoo.fr Subject: [tulip] Problem with tulip on Compaq Presario 1800 This is a multi-part message in MIME format. ------=_NextPart_000_0004_01C00F44.F04DD7C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Thanks for your answer. It is actually a laptop. When Donald is talking about 2.4 I assume it is the linux kernel. Well I am using 2.2.15 with Mandrake 7.0 linux. Any suggestion ? -----Message d'origine----- De : david@nifty.Blue-Labs.org [mailto:david@nifty.Blue-Labs.org]De la part de David Ford Envoyé : vendredi 25 août 2000 17:28 À : Donald Becker; Henri Sack; tulip@scyld.com Objet : Re: [tulip] Problem with tulip on Compaq Presario 1800 This is a laptop. I have one. It has a built in i82557 (eepro100) card. btw, there was a problem with tulips and 2.4 a few weeks ago, I would suggest Henri update to 2.4.0-test7 final if he is indeed using 2.4. Donald Becker wrote: > On Fri, 25 Aug 2000, Henri Sack wrote: > > > Subject: [tulip] Problem with tulip on Compaq Presario 1800 > > Is this a laptop or desktop? -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." ------=_NextPart_000_0004_01C00F44.F04DD7C0 Content-Type: text/x-vcard; name="david.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="david.vcf" begin:vcard n:Ford;David x-mozilla-html:TRUE org: adr:;;;;;; version:2.1 email;internet:david@kalifornia.com title:Blue Labs Developer x-mozilla-cpt:;-12480 fn:David Ford end:vcard ------=_NextPart_000_0004_01C00F44.F04DD7C0-- From dubbeld@zeelandnet.nl Sat, 26 Aug 2000 13:46:41 +0200 Date: Sat, 26 Aug 2000 13:46:41 +0200 From: Marco Dubbeld dubbeld@zeelandnet.nl Subject: [tulip] (no subject) When I insert my Linkport TX32 card, cardmgr reports in messages: cardmgr[9623]: initializing socket 0 cardmgr[9623]: socket 0: Compex LinkPort/TX32A kernel: cs: cb_alloc(bus 32): vendor 0x10ec, device 0x8138 cardmgr[9623]: executing: 'modprobe cb_enabler' cardmgr[9623]: executing: 'modprobe tulip_cb 10baseT debu kernel: fn 0 bar 1: io 0xa00-0xaff kernel: fn 0 bar 2: mem 0x60001000-0x600011ff kernel: irq 11 kernel: tulip_attach(device 20:00.0) kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasord) kernel: eth0: Digital DS21143 Tulip rev 16 at 0xa00, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11. kernel: eth0: Missing EEPROM, this interface may not work correctly! cardmgr[9623]: executing: './network start eth0' kernel: eth0: Tx hung, 11 vs. 0. kernel: eth0: 21140 transmit timed out, status 0801fbfc, SIA 0000000f 00000000 00000018 58fab388, resetting... And then the interface doesn't work. What can I do? Thanks. -- Marco Dubbeld Davinci Techniek Tel. nr: +31 11 862 9847 Fax. nr: +31 20 871 3830 Fax. nr: +1 917 477 6457 email: dubbeld@zeelandnet.nl From j.msadoques@worldnet.att.net Sat, 26 Aug 2000 07:54:53 -0400 Date: Sat, 26 Aug 2000 07:54:53 -0400 From: Jason M'Sadoques j.msadoques@worldnet.att.net Subject: [tulip] Yet another LNE100TX problem I just purchased a Linksys EtherFast 10/100 with the LNE100TX version 4.1 chip. I'm running RedHat 6.2, Kernel 2.2.14. I have determined that I need the latest version of the tulip.c driver. I have downloaded these four files: tulip.c, pci-scan.c, pci-scan.h, kern_compat.h. When I compile with the command given at the end of tulip.c: gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c tulip.c, I get hundreds of errors, like the following: In file included from /usr/include/linux/string.h:37, from tulip.c:143: /usr/include/asm/string.h:50: parse error before `size_t' /usr/include/asm/string.h: In function `strncpy': /usr/include/asm/string.h:51: number of arguments doesn't match prototype /usr/include/linux/string.h:13: prototype declaration /usr/include/asm/string.h:65: `src' undeclared (first use in this function) /usr/include/asm/string.h:65: (Each undeclared identifier is reported only once /usr/include/asm/string.h:65: for each function it appears in.) /usr/include/asm/string.h:65: `dest' undeclared (first use in this function) /usr/include/asm/string.h:65: `count' undeclared (first use in this function) /usr/include/asm/string.h:67: warning: control reaches end of non-void function /usr/include/asm/string.h: At top level: . . . etc. The same goes for compiling pci-scan.c. My linux and asm directories are symbolically linked into /usr/include. I did not do this, it appears that these symbolic links are owned by the kernel-headers-2.2.14 rpm. I ran rpm -V kernel-headers, and the files are exactly as they were installed originally. My compiler is gcc 2.95. So the question is: what do I need to do to get tulip.c to compile on my system? Jason M'Sadoques From j47@pacbell.net Sat, 26 Aug 2000 09:19:59 -0700 Date: Sat, 26 Aug 2000 09:19:59 -0700 From: Jim Fennacy j47@pacbell.net Subject: [tulip] Yet another LNE100TX problem I have the same card and have gotten to work with Mandrake 7.1 (kernel 2.2.15). I'm not an expert on this but here's what I see from what you wrote: 1. The compile command is right, but you need to specify the location of the include files with the -I directive: gcc -I/usr/src/linux/include -DMODULE -Wall -Wstrict-prototypes -O6 -c tulip.c 2. The easier way to do what you're trying to do is to download netdriver-2.0.src.rpm from www.scyld.com/network/updates.html. The instructions will compile all the drivers available and install them in the correct location. Jim. Jason M'Sadoques wrote: > I just purchased a Linksys EtherFast 10/100 with the LNE100TX version > 4.1 chip. I'm running RedHat 6.2, Kernel 2.2.14. I have determined that > I need the latest version of the tulip.c driver. I have downloaded these > four files: tulip.c, pci-scan.c, pci-scan.h, kern_compat.h. When I > compile with the command given at the end of tulip.c: gcc -DMODULE -Wall > -Wstrict-prototypes -O6 -c tulip.c, I get hundreds of errors, like the > following: > In file included from /usr/include/linux/string.h:37, > from tulip.c:143: > /usr/include/asm/string.h:50: parse error before `size_t' > /usr/include/asm/string.h: In function `strncpy': > /usr/include/asm/string.h:51: number of arguments doesn't match > prototype > /usr/include/linux/string.h:13: prototype declaration > /usr/include/asm/string.h:65: `src' undeclared (first use in this > function) > /usr/include/asm/string.h:65: (Each undeclared identifier is reported > only once > /usr/include/asm/string.h:65: for each function it appears in.) > /usr/include/asm/string.h:65: `dest' undeclared (first use in this > function) > /usr/include/asm/string.h:65: `count' undeclared (first use in this > function) > /usr/include/asm/string.h:67: warning: control reaches end of non-void > function > /usr/include/asm/string.h: At top level: > . > . > . > etc. > > The same goes for compiling pci-scan.c. > > My linux and asm directories are symbolically linked into /usr/include. > I did not do this, it appears that these symbolic links are owned by the > kernel-headers-2.2.14 rpm. I ran rpm -V kernel-headers, and the files > are exactly as they were installed originally. My compiler is gcc 2.95. > So the question is: what do I need to do to get tulip.c to compile on my > system? > > Jason M'Sadoques > > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip From fred1@inebraska.com Sat, 26 Aug 2000 21:23:45 -0500 Date: Sat, 26 Aug 2000 21:23:45 -0500 From: Gary Dolan fred1@inebraska.com Subject: [tulip] Tulip driver; IRQ not assigned Gentlemen I'm trying to use a Linksys LNE100TX card in a linux box. The diagnostic program for the tulip driver says that an interrupt has not been assigned, and that the PCI BIOS needs to be changed. I have disabled the PnP OS feature, but still no help. The BIOS is AmiBIOS and on W98 the card is assigned IRQ 11, and works fine. What other setting can/ must be changed? From MSmith@webtonetech.com Sun, 27 Aug 2000 21:04:01 -0400 Date: Sun, 27 Aug 2000 21:04:01 -0400 From: Michael Smith MSmith@webtonetech.com Subject: [tulip] Tulip driver; IRQ not assigned Try allocating IRQ11 in your BIOS to that cards(the LNE100TX) PCI slot. That should resolve this problem. -----Original Message----- From: Gary Dolan To: tulip@scyld.com Sent: 8/26/00 10:23 PM Subject: [tulip] Tulip driver; IRQ not assigned Gentlemen I'm trying to use a Linksys LNE100TX card in a linux box. The diagnostic program for the tulip driver says that an interrupt has not been assigned, and that the PCI BIOS needs to be changed. I have disabled the PnP OS feature, but still no help. The BIOS is AmiBIOS and on W98 the card is assigned IRQ 11, and works fine. What other setting can/ must be changed? _______________________________________________ tulip mailing list tulip@scyld.com http://www.scyld.com/mailman/listinfo/tulip From gregturp@home.com Mon, 28 Aug 2000 01:14:07 -0600 Date: Mon, 28 Aug 2000 01:14:07 -0600 From: Greg Turpin gregturp@home.com Subject: [tulip] Linksys problems - non typical This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C0108D.43B2D340 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Okay fellas, I've recently purchased a Linksys 10/100 EtherFast network card. Of course, it works fine with my Win98 system....but, that's only because the drivers were included. I've spent the last couple of days desperately trying to get this puppy working with my default SuSE 6.4 installation - to no avail. I download the entire netdrivers tarball and get a few insmod unresolved symbol errors. These errors are different from any of the other errors that I've been able to find in the tulip mailing list archives. I know it's not a pci-scan.o problem, because I run lsmod and find it in my loaded modules. here is the output from 'depmod -ae': depmod: *** Unresolved symbols in /lib/modules/2.2.14/net/tulip.o depmod: __global_cli depmod: __global_save_flags depmod: __global_restore_flags=20 I know that I'm just missing a driver or something. Has anyone seen these unresolved symbols before who might be able to lead me down the right path? Thanks for any assistance, Greg a;lksdjf;lksajfd;lksajdflksdjf :wq ------=_NextPart_000_001F_01C0108D.43B2D340 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Okay fellas,
 
    I've recently = purchased a=20 Linksys 10/100 EtherFast
network card.  Of course, it works = fine with=20 my Win98
system....but, that's only because the = drivers=20 were
included.
    I've spent the last = couple of=20 days desperately
trying to get this puppy working with = my=20 default
SuSE 6.4 installation - to no = avail.
 
     I download the = entire=20 netdrivers tarball and get
a few insmod unresolved symbol = errors. =20 These
errors are different from any of the = other=20 errors
that I've been able to find in the = tulip mailing=20 list
archives.  I know it's not a = pci-scan.o=20 problem, because
I run lsmod and find it in my loaded=20 modules.
 
here is the output from 'depmod = -ae':
 
depmod: *** Unresolved symbols in=20 /lib/modules/2.2.14/net/tulip.o
depmod:     &= nbsp;  =20 __global_cli
depmod:        =20 __global_save_flags
depmod:       &= nbsp;__global_restore_flags 
 
I know that I'm just missing a driver = or something.=20 Has
anyone seen these unresolved symbols before who might
be able = to lead=20 me down the right path?
 
Thanks for any assistance,
 
    = Greg
   =20 a;lksdjf;lksajfd;lksajdflksdjf
:wq
 
 
------=_NextPart_000_001F_01C0108D.43B2D340-- From danci@server.kibla.org Mon, 28 Aug 2000 11:13:39 +0200 (CEST) Date: Mon, 28 Aug 2000 11:13:39 +0200 (CEST) From: Danilo Godec danci@server.kibla.org Subject: [tulip] Linksys problems - non typical On Mon, 28 Aug 2000, Greg Turpin wrote: > here is the output from 'depmod -ae': > > depmod: *** Unresolved symbols in /lib/modules/2.2.14/net/tulip.o > depmod: __global_cli > depmod: __global_save_flags > depmod: __global_restore_flags Quote from http://www.scyld.com/network/tulip.html: "When updating a single driver you will need to build pci-scan.o along with the specific driver.o file. This means that in addition to the driver.c file, you must download pci-scan.c, pci-scan.h, and kern_compat.h." Probably, this is what you need to do... D. From kohel@maths.usyd.edu.au Mon, 28 Aug 2000 13:55:52 -0700 Date: Mon, 28 Aug 2000 13:55:52 -0700 From: David R. Kohel kohel@maths.usyd.edu.au Subject: [tulip] Linksys card recognition? Hi, I just obtained a Linksys LNE100TX card; no eth0 line appear in the boot sequence. I find that the entry in /proc/pci is Bus 0, device 14, function 0: Ethernet controller: Unknown vendor Unknown device (rev 17). Vendor id=1317. Device id=985. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=32. Min Gnt=255.Max Lat=255. I/O at 0xe000 [0xe001]. Non-prefetchable 32 bit memory at 0xd5810000 [0xd5810000]. That is, it doesn't appear to pick up the chip LNE100TX or any other identifier. Thereafter 'insmod tulip.o' gives an error message saying that the device is busy. This is my first time to use a PCI card; any advice on forcing the card to be recognized would be greatly appreciated. I'm running a Debian system with kernel 2.2.15. --David From jvalkiunas@ChicagoJava.com Mon, 28 Aug 2000 16:16:00 +0000 (CST) Date: Mon, 28 Aug 2000 16:16:00 +0000 (CST) From: Jonas P. Valkiunas jvalkiunas@ChicagoJava.com Subject: [tulip] Linksys NC100 v2.0 Transmit time out I've perused through the last few months of the scyld and other lists regarding the new Linksys NC100 v2.0 problem, but cannot find my specific problem. Both srpm and individual tulip.c files compile without a problem, but as soon as I try to ping any ip (other than my own), I get the error: "eth0: Transmit timed out, status fc67c057, CSR120000000 resetting..." I have tried using both versions tulip.c:v0.92k 8/14/00 and 0.92i (Donald Becker), but both produce the same error. lspci show the already list mentioned Bridgecom ID, while logs show the ADMtek Comet, rev 17, using IRQ11. other interesting notes from lspci: " 00:1f.3 SMBus Intel Corporation 82801AA 82810 Chipset SMBus (rev02) Subsystem: Intel Corporation: Unknown device 2413 Flags: medium devsel, IRQ 11 I/O ports at efa0 01:05.0 Ethernet controller: Bridgecom, Inc: Unkown device 0985 (rev11) Subsystem: Bridgecom, Inc: Unknown device 0570 Flags: bus master, medium devsel, latency 64 IRQ 11 I/O ports at d800 Memory at ffcffc00 (32 bit, non-prefetchable) Expansion ROM at ffcc0000 [disabled] Capabilities: [0] Power Management version 1" This is a Red Hat 6.2 box running on a celeron 533 in a Tyan S2054 Tomcat i810 motherboard. Has anybody seen this time out problem (happening on 2 identical boxes)? Sorry for the naivete...PnP disabled in BIOS and kernel, PCI enabled in kernel. At first thought of an IRQ conflict (at 11), but could not change the nic's IRQ through BIOS (PCI). Any help tips, etc. MUCH appreciated! Thanks, -Jonas From becker@scyld.com Mon, 28 Aug 2000 18:19:37 -0400 (EDT) Date: Mon, 28 Aug 2000 18:19:37 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Linksys card recognition? On Mon, 28 Aug 2000, David R. Kohel wrote: > I just obtained a Linksys LNE100TX card; no eth0 line appear in the > boot sequence. I find that the entry in /proc/pci is > > Ethernet controller: Unknown vendor Unknown device (rev 17). > Vendor id=1317. Device id=985. ADMtek Comet/Centaur You'll need the new tulip driver version to work with this chip. http://www.scyld.com/network/tulip.html ftp://www.scyld.com/pub/network/tulip.c Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From becker@scyld.com Mon, 28 Aug 2000 18:27:50 -0400 (EDT) Date: Mon, 28 Aug 2000 18:27:50 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Linksys NC100 v2.0 Transmit time out On Mon, 28 Aug 2000, Jonas P. Valkiunas wrote: > > I've perused through the last few months of the scyld and other lists > regarding the new Linksys NC100 v2.0 problem, but cannot find my specific > problem. Both srpm and individual tulip.c files compile without a > problem, but as soon as I try to ping any ip (other than my own), I get > the error: > > "eth0: Transmit timed out, status fc67c057, CSR120000000 resetting..." IRQ conflict -- the chip is trying to raise an interrupt, and nothing is happening. Run 'tulip-diag' to verify. > lspci show the already list mentioned Bridgecom ID, while logs show the ADMtek Comet, rev 17, using IRQ11. > > other interesting notes from lspci: > " > 00:1f.3 SMBus Intel Corporation 82801AA 82810 Chipset SMBus (rev02) > Subsystem: Intel Corporation: Unknown device 2413 > Flags: medium devsel, IRQ 11 > I/O ports at efa0 If the BIOS is using the SMBus for something unknown to the OS, that might prevent interrupts from being delivered. Another possible conflict is the USB controller, if the BIOS is doing PS/2 keyboard emulation. > This is a Red Hat 6.2 box running on a celeron 533 in a Tyan S2054 Tomcat > i810 motherboard. Has anybody seen this time out problem (happening on 2 > identical boxes)? Sorry for the naivete...PnP disabled in BIOS and > kernel, PCI enabled in kernel. At first thought of an IRQ conflict (at > 11), but could not change the nic's IRQ through BIOS (PCI). Any help > tips, etc. MUCH appreciated! Try the LILO option "noapic". Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From IHogan@mbsnav.com Mon, 28 Aug 2000 16:29:37 -0600 Date: Mon, 28 Aug 2000 16:29:37 -0600 From: Ian Hogan IHogan@mbsnav.com Subject: [tulip] 2.2.15 kernel help needed Hi, I'm hoping someone here might be able to help. I've tried several lists to no avail. I'm running Linux Mandrake 7.0 (I think kernel version 2.2.16). I'm trying to compile the driver for a NetGeat FA311, which is natsemi.c. I've downloaded all the other files it looks like I need (pci-scan.c, pci-scan.h, kern_compat.h), and am using the instructions at the end of the source code (gcc -DMODULE -Wall -Wstrict-prototypes -O6 etc etc....). My problem is that when I attempt to compile, I get about 400 lines of compiler error codes, which makes me think my gcc environment is not setup properly. The first few errors deal with string.h, regarding undeclared variables, variables being de-referenced, sizes not being set, and various things not matching prototypes. It gives errors on several other included files, such as coda.h. If it would be helpful, I can grab the errors next time and send them. Any help would be much appreciated. There is no makefile included in this process, and I'm (clearly) not much of a C/C++ expert. Any ideas? ian From jason@topic.com.au Tue, 29 Aug 2000 09:48:24 +1100 Date: Tue, 29 Aug 2000 09:48:24 +1100 From: Jason Thomas jason@topic.com.au Subject: [tulip] 2.2.15 kernel help needed --Izn7cH1Com+I3R9J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It sounds like you need the header files for your currently running kernel, not the glibc headers. On Mon, Aug 28, 2000 at 04:29:37PM -0600, Ian Hogan wrote: >=20 > Hi, >=20 > I'm hoping someone here might be able to help. I've tried several lists to > no avail. >=20 > I'm running Linux Mandrake 7.0 (I think kernel version 2.2.16). I'm trying > to compile the driver for a NetGeat FA311, which is natsemi.c. I've > downloaded all the other files it looks like I need (pci-scan.c, pci-scan= h, > kern_compat.h), and am using the instructions at the end of the source co= de > (gcc -DMODULE -Wall -Wstrict-prototypes -O6 etc etc....). >=20 > My problem is that when I attempt to compile, I get about 400 lines of > compiler error codes, which makes me think my gcc environment is not setup > properly. The first few errors deal with string.h, regarding undeclared > variables, variables being de-referenced, sizes not being set, and various > things not matching prototypes. It gives errors on several other included > files, such as coda.h. If it would be helpful, I can grab the errors next > time and send them. >=20 > Any help would be much appreciated. There is no makefile included in this > process, and I'm (clearly) not much of a C/C++ expert. Any ideas? >=20 > ian > =20 >=20 >=20 > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip --=20 Jason Thomas Phone: +61 2 6257 7111 System Administrator - UID 0 Fax: +61 2 6257 7311 tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81 1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/ --Izn7cH1Com+I3R9J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5quw47cYwRJJSiL4RAsLtAJ9NdFbylhc8yk5k5ImitnXbg7zq3QCfSw4Z AgfJ/xLsXlOOVYbvELq7qj4= =p45a -----END PGP SIGNATURE----- --Izn7cH1Com+I3R9J-- From shochat@acm.org Mon, 28 Aug 2000 18:51:58 -0400 Date: Mon, 28 Aug 2000 18:51:58 -0400 From: David Shochat shochat@acm.org Subject: [tulip] Linksys card recognition? I have the same card you have. It is working fine and my /proc/pci shows pretty much exactly the same thing as yours for it: Bus 1, device 10, function 0: Ethernet controller: Unknown vendor Unknown device (rev 17). Vendor id=1317. Device id=985. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. Min Gnt=255.Max Lat=255. I/O at 0xd800 [0xd801]. Non-prefetchable 32 bit memory at 0xff8ff800 [0xff8ff800]. Note that LNE100TX is just the card model number, not the chip. According to what I see in my syslog from boot: Aug 28 17:58:45 h kernel: tulip.c:v0.92 4/17/2000 Written by Donald Becker Aug 28 17:58:45 h kernel: http://www.scyld.com/network/tulip.html Aug 28 17:58:45 h kernel: eth1: ADMtek Comet rev 17 at 0xc805e800, 00:20:78:18:08:26, IRQ 11. I would say the driver thinks the chip is ADMtek Comet. "David R. Kohel" wrote: > > Hi, > > I just obtained a Linksys LNE100TX card; no eth0 line appear in the > boot sequence. I find that the entry in /proc/pci is > > Bus 0, device 14, function 0: > Ethernet controller: Unknown vendor Unknown device (rev 17). > Vendor id=1317. Device id=985. > Medium devsel. Fast back-to-back capable. IRQ 11. Master > Capable. Latency=32. Min Gnt=255.Max Lat=255. > I/O at 0xe000 [0xe001]. > Non-prefetchable 32 bit memory at 0xd5810000 [0xd5810000]. > > That is, it doesn't appear to pick up the chip LNE100TX or any other > identifier. Thereafter 'insmod tulip.o' gives an error message saying > that the device is busy. > > This is my first time to use a PCI card; any advice on forcing the > card to be recognized would be greatly appreciated. I'm running > a Debian system with kernel 2.2.15. > > --David > > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip From jvalkiunas@ChicagoJava.com Mon, 28 Aug 2000 17:52:38 +0000 (CST) Date: Mon, 28 Aug 2000 17:52:38 +0000 (CST) From: Jonas P. Valkiunas jvalkiunas@ChicagoJava.com Subject: [tulip] Linksys NC100 v2.0 Transmit time out 1st, thanks for the quick reply! I suspected an IRQ conflict from lspci, but a cat of /proc/interrupts shows no problems. Ran tulip-diag which looks like its waiting for an interrupt... (Interrupt sources are pending! CSR5 is fc674054. here's some output: [root@mors /root]# cat /proc/interrupts CPU0 0: 303496 XT-PIC timer 1: 2961 XT-PIC keyboard 2: 0 XT-PIC cascade 6: 162 XT-PIC floppy 8: 1 XT-PIC rtc 10: 0 XT-PIC eth0 12: 1665 XT-PIC PS/2 Mouse 13: 1 XT-PIC fpu 14: 89751 XT-PIC ide0 15: 7 XT-PIC ide1 NMI: 0 [root@mors /root]# /usr/src/redhat/SOURCES/tulip-diag -a tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xd800. * A potential Tulip chip has been found, but it appears to be active. * Either shutdown the network, or use the '-f' flag to see all values. Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex. Transmit started, Receive started, half-duplex. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 128. Interrupt sources are pending! CSR5 is fc674054. Tx out of buffers indication. Link passed indication. Rx Done indication. Early Rx indication. The Comet MAC registers are 03782000 ffff1809 filter 8000000000000000. Messing around in BIOS changed eth0 to an IRQ of 10, but still the same problem. If this is an IRQ problem anybody been working with the Tyan i810 (got this one from the linuxstore.com)? Or else any other suggestions, tips etc? The nic is on a riser in a 2U rack mount case. I wonder if the nic is competing for an IRQ with the riser...? Thanks in advance, -Jonas On Mon, 28 Aug 2000 Donald Becker wrote: > On Mon, 28 Aug 2000, Jonas P. Valkiunas wrote: > > > > > I've perused through the last few months of the scyld and other lists > > regarding the new Linksys NC100 v2.0 problem, but cannot find my specific > > problem. Both srpm and individual tulip.c files compile without a > > problem, but as soon as I try to ping any ip (other than my own), I get > > the error: > > > > "eth0: Transmit timed out, status fc67c057, CSR120000000 resetting..." > > IRQ conflict -- the chip is trying to raise an interrupt, and nothing is > happening. > > Run 'tulip-diag' to verify. > > > > lspci show the already list mentioned Bridgecom ID, while logs show the ADMtek Comet, > > rev 17, using IRQ11. > > > > other interesting notes from lspci: > > " > > 00:1f.3 SMBus Intel Corporation 82801AA 82810 Chipset SMBus (rev02) > > Subsystem: Intel Corporation: Unknown device 2413 > > Flags: medium devsel, IRQ 11 > > I/O ports at efa0 > > If the BIOS is using the SMBus for something unknown to the OS, that might > prevent interrupts from being delivered. > > Another possible conflict is the USB controller, if the BIOS is doing PS/2 > keyboard emulation. > > > This is a Red Hat 6.2 box running on a celeron 533 in a Tyan S2054 Tomcat > > i810 motherboard. Has anybody seen this time out problem (happening on 2 > > identical boxes)? Sorry for the naivete...PnP disabled in BIOS and > > kernel, PCI enabled in kernel. At first thought of an IRQ conflict (at > > 11), but could not change the nic's IRQ through BIOS (PCI). Any help > > tips, etc. MUCH appreciated! > > Try the LILO option "noapic". > > Donald Becker becker@scyld.com > Scyld Computing Corporation http://www.scyld.com > 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution > Annapolis MD 21403 > From becker@scyld.com Mon, 28 Aug 2000 20:09:24 -0400 (EDT) Date: Mon, 28 Aug 2000 20:09:24 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Linksys NC100 v2.0 Transmit time out On Mon, 28 Aug 2000, Jonas P. Valkiunas wrote: > I suspected an IRQ conflict from lspci, but a cat of /proc/interrupts > shows no problems. Ran tulip-diag which looks like its waiting for an > interrupt... (Interrupt sources are pending! CSR5 is fc674054. here's > some output: ... > 10: 0 XT-PIC eth0 This shows the problem: no interrupts are getting through. Your interrupt count remains at zero. > Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xd800. .... > Interrupt sources are pending! CSR5 is fc674054. > Messing around in BIOS changed eth0 to an IRQ of 10, but still the same > problem. If this is an IRQ problem anybody been working with the Tyan > i810 (got this one from the linuxstore.com)? Or else any other > suggestions, tips etc? The nic is on a riser in a 2U rack mount case. I > wonder if the nic is competing for an IRQ with the riser...? The riser might be mis-routing the INT line. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From jpschewe@eggplant.mtu.net 28 Aug 2000 19:54:56 -0500 Date: 28 Aug 2000 19:54:56 -0500 From: Jon Schewe jpschewe@eggplant.mtu.net Subject: [tulip] Linksys card recognition? Of course unless something has changed recently you can't use hte card on a 10/100 switch, works fine on a 10Mpbs hub though. David Shochat writes: > I have the same card you have. It is working fine and my /proc/pci shows > pretty much exactly the same thing as yours for it: > > Bus 1, device 10, function 0: > Ethernet controller: Unknown vendor Unknown device (rev 17). > Vendor id=1317. Device id=985. > Medium devsel. Fast back-to-back capable. IRQ 11. Master > Capable. Latency=64. Min Gnt=255.Max Lat=255. > I/O at 0xd800 [0xd801]. > Non-prefetchable 32 bit memory at 0xff8ff800 [0xff8ff800]. > > Note that LNE100TX is just the card model number, not the chip. > According to what I see in my syslog from boot: > > Aug 28 17:58:45 h kernel: tulip.c:v0.92 4/17/2000 Written by Donald > Becker > Aug 28 17:58:45 h kernel: http://www.scyld.com/network/tulip.html > Aug 28 17:58:45 h kernel: eth1: ADMtek Comet rev 17 at 0xc805e800, > 00:20:78:18:08:26, IRQ 11. > > I would say the driver thinks the chip is ADMtek Comet. > > "David R. Kohel" wrote: > > > > Hi, > > > > I just obtained a Linksys LNE100TX card; no eth0 line appear in the > > boot sequence. I find that the entry in /proc/pci is > > > > Bus 0, device 14, function 0: > > Ethernet controller: Unknown vendor Unknown device (rev 17). > > Vendor id=1317. Device id=985. > > Medium devsel. Fast back-to-back capable. IRQ 11. Master > > Capable. Latency=32. Min Gnt=255.Max Lat=255. > > I/O at 0xe000 [0xe001]. > > Non-prefetchable 32 bit memory at 0xd5810000 [0xd5810000]. > > > > That is, it doesn't appear to pick up the chip LNE100TX or any other > > identifier. Thereafter 'insmod tulip.o' gives an error message saying > > that the device is busy. > > > > This is my first time to use a PCI card; any advice on forcing the > > card to be recognized would be greatly appreciated. I'm running > > a Debian system with kernel 2.2.15. > > > > --David > > > > _______________________________________________ > > tulip mailing list > > tulip@scyld.com > > http://www.scyld.com/mailman/listinfo/tulip > > _______________________________________________ > tulip mailing list > tulip@scyld.com > http://www.scyld.com/mailman/listinfo/tulip -- Jon Schewe | http://eggplant.mtu.net/~jpschewe For I am convinced that neither death nor life, neither angels nor demons, neither the present nor the future, nor any powers, neither height nor depth, nor anything else in all creation, will be able to separate us from the love of God that is in Christ Jesus our Lord. - Romans 8:38-39 From KevinSCarr@aol.com Tue, 29 Aug 2000 00:06:20 EDT Date: Tue, 29 Aug 2000 00:06:20 EDT From: KevinSCarr@aol.com KevinSCarr@aol.com Subject: [tulip] Tulip: PCI Fatal Bus Error Thanks for the quick response. It turns out that the problem was with the card. It was a Network Everywhere Fast Ethernet 10/100. I put a EtherFast 10/100 Linksys Card in the same slot and it was recognized without problems. Thanks again Scott Carr Software Engineer Dialogic Communications Corporation From mjj@frogdream.com 29 Aug 2000 20:31:17 +1100 Date: 29 Aug 2000 20:31:17 +1100 From: Matt Jackson mjj@frogdream.com Subject: [tulip] Re: 2.2.15 kernel help needed Ian Hogan writes: > Hi, > > I'm hoping someone here might be able to help. I've tried several lists to > no avail. > > I'm running Linux Mandrake 7.0 (I think kernel version 2.2.16). I'm trying > to compile the driver for a NetGeat FA311, which is natsemi.c. I've > downloaded all the other files it looks like I need (pci-scan.c, pci-scan.h, > kern_compat.h), and am using the instructions at the end of the source code > (gcc -DMODULE -Wall -Wstrict-prototypes -O6 etc etc....). Try gcc -c -I/usr/src/linux/include -D__KERNEL__ -DMODULE -Wall -Wstrict-prototypes -O6 natsemi.c Not necessarily a Tulip question but ... Under 2.4.0-test7 where the natsemi driver is included I get lots of the following in my logs: Warning: kfree_skb on hard IRQ c0185ab0 What can be done ? I compiled the driver into the kernel rather than using a module. -- Matt Jackson | "The world is a book, and those who mjj-tulip@frogdream.com | don't travel read only one page." http://www.frogdream.com | - St Augustine From dkramer@Interelate.com Tue, 29 Aug 2000 11:19:42 -0500 Date: Tue, 29 Aug 2000 11:19:42 -0500 From: David Kramer dkramer@Interelate.com Subject: [tulip] Which Kernel Version match which Tulip. pci-scan, and kern_compat versions? Which Kernel versions use which versions of Tulip, pci-scan,and kern_compat. I am currently running Linux Kernel 2.2.14-12 and receive errors when testing the pci-scan.o Apparently it is looking for a different version of the pci-scan.h version .05. I guess pci-scan was compiled for the wrong version of pci-scan.h. I can only find version 1.0 of this file. Is there a specfic kernel I should be running inorder to get the proper files to compile and install on the Kernel? I am trying to install Linksys' Etherfast 10/100 card on a RedHat distribution. Thanks, David Kramer From fschmuck@lcch.org Tue, 29 Aug 2000 14:58:29 -0400 Date: Tue, 29 Aug 2000 14:58:29 -0400 From: Frank Schmuck, CFO fschmuck@lcch.org Subject: [tulip] Tulip and SMP I have a LNX100TX LinkSys Ethernet card. The tulip driver runs fine under standard kernel but will not recognize the card under SMP. Any ideas? Thanks Frank J. Schmuck, Chief Financial Officer Lee County Community Hospital Pennington Gap, VA e-mail: fschmuck@lcch.org -----Original Message----- From: David Kramer [mailto:dkramer@Interelate.com] Sent: Tuesday, August 29, 2000 12:20 PM To: 'tulip@scyld.com' Subject: [tulip] Which Kernel Version match which Tulip. pci-scan, and kern_compat versions? Which Kernel versions use which versions of Tulip, pci-scan,and kern_compat. I am currently running Linux Kernel 2.2.14-12 and receive errors when testing the pci-scan.o Apparently it is looking for a different version of the pci-scan.h version .05. I guess pci-scan was compiled for the wrong version of pci-scan.h. I can only find version 1.0 of this file. Is there a specfic kernel I should be running inorder to get the proper files to compile and install on the Kernel? I am trying to install Linksys' Etherfast 10/100 card on a RedHat distribution. Thanks, David Kramer _______________________________________________ tulip mailing list tulip@scyld.com http://www.scyld.com/mailman/listinfo/tulip From khendric@BluTie_linux.MLB.ESID.NorthGrum.com Tue, 29 Aug 2000 17:45:01 -0400 Date: Tue, 29 Aug 2000 17:45:01 -0400 From: Kenneth J. Hendrickson khendric@BluTie_linux.MLB.ESID.NorthGrum.com Subject: [tulip] TBD Tulip Developers and Users: I just bought four LinkSys 100Mbps ethernet interfaces. One is a PCMCIA, and works flawlessly. The other three are PCI cards, and fail. According to the LinkSys web site, the PCI cards are brand new (chipset) hardware as of August 2000. (They have new Windows drivers.) I'm using version 0.93 of the tulip driver with the 2.2.17 kernel, Debian distribution. Here are the error messages: # insmod tulip Using /lib/modules/2.2.17/net/tulip.o /lib/modules/2.2.17/net/tulip.o: init_module: Device or resource busy Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters This happens with both the tulip driver, and also the de4x5 driver. # insmod de4x5 Using /lib/modules/2.2.17/net/de4x5.o /lib/modules/2.2.17/net/de4x5.o: init_module: Device or resource busy Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters It's obvious (from this error message) that the driver doesn't recognize the card when it probes for it. I've already downloaded kern_compat.h, pci-scan.c, pci-scan.h, tulip.c, and test/tulip.c but now it's almost 5am, and I have to sleep. :-( I haven't played with any of the fresh source yet. Please advise. I'd like to help make the driver work. Thank you, Ken Hendrickson From shochat@acm.org Tue, 29 Aug 2000 19:18:04 -0400 Date: Tue, 29 Aug 2000 19:18:04 -0400 From: David Shochat shochat@acm.org Subject: [tulip] Which Kernel Version match which Tulip. pci-scan, and kern_compatversions? David Kramer wrote: > > Which Kernel versions use which versions of Tulip, pci-scan,and kern_compat. > I am currently running Linux Kernel 2.2.14-12 and receive errors when > testing the pci-scan.o Apparently it is looking for a different version of > the pci-scan.h version .05. I guess pci-scan was compiled for the wrong > version of pci-scan.h. I can only find version 1.0 of this file. Is there > a specfic kernel I should be running inorder to get the proper files to > compile and install on the Kernel? I am trying to install Linksys' > Etherfast 10/100 card on a RedHat distribution. > I can offer a couple of data points. I have tulip source files as follows: kern_compat.h: $Revision: 1.5 $ $Date: 2000/07/05 16:23:25 $ pci-scan.h: version 1.00 $Version$ $Date: 2000/04/08 05:04:26 $ pci-scan.c: "pci-scan.c:v1.00 4/15/2000 Donald Becker " tulip.c: "tulip.c:v0.92 4/17/2000 Written by Donald Becker \n"; These are simply the versions that were on the scyld ftp site when I went looking for them. Using these, the code compiled without error under a RedHat 6.2 system with original 2.2.14-5 kernel and also on one with the kernel upgraded to 2.2.16-3 (compiled kernel and source all obtained from RedHat rpm's). I have two Linksys EtherFast 10/100 model LNE100TX version 4.0 cards, one in each of the above machines and they are working fine with this tulip driver. They would not work at all with the tulip.o that came with those 2 kernels. -- David From geofstro@monaco.mc Wed, 30 Aug 2000 10:42:45 +0200 Date: Wed, 30 Aug 2000 10:42:45 +0200 From: geofstro@monaco.mc geofstro@monaco.mc Subject: [tulip] tulip and SMP I also have a problem with SMP support. My board supports SMP so I need to run that version of the kernel. If I compile tulip.c using the standard compile command I get the error, "compiled for Linux 2.2.14 but you're running Linux 2.2.14-SMP. I tried compiling using SMP options that I found from another web-site; but I still got the above error as a result of insmod. Does it work with SMP? If so I think it would be useful if there were an SMP compile instruction at the bottom of the source file to correctly compile the SMP version. Please advise. Thanks Geoff Armstrong From peterc@brosystems.com Wed, 30 Aug 2000 14:26:18 +0100 Date: Wed, 30 Aug 2000 14:26:18 +0100 From: peterc peterc@brosystems.com Subject: [tulip] D-Link DFE 570tx install problem Hi I hope you will be able to help me with this. I am currently trying to install mandrake 7.1 onto a machine with 2 DFE570tx (4 port) cards on board. The O/S install seems to work fine. I reboot the machine and that goes ok as well the system comes back up and binds eth0 ,eth1 ,eth2 ,eth3 to the correct IP addresses. However when I look in the /var/log/messages file I get an error saying... kernel: eth0: media is unconnected, link down or incompatable connection. do I need to build and install a tulip driver or should it already be part of my kernel ? Or is there something else that I am doing wrong ? Thankyou for your help. Peter Church From becker@scyld.com Wed, 30 Aug 2000 10:33:47 -0400 (EDT) Date: Wed, 30 Aug 2000 10:33:47 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] D-Link DFE 570tx install problem On Wed, 30 Aug 2000, peterc wrote: > I hope you will be able to help me with this. I am currently trying to > install > mandrake 7.1 onto a machine with 2 DFE570tx (4 port) cards on board. The O/S > install seems to work fine. I reboot the machine and that goes ok as well > the system comes back up and binds eth0 ,eth1 ,eth2 ,eth3 to the correct IP > addresses. However when I look in the /var/log/messages file I get an error > saying... > > kernel: eth0: media is unconnected, link down or incompatable connection. > > do I need to build and install a tulip driver or should it already be part > of my kernel ? > Or is there something else that I am doing wrong ? What driver are you using? What is the detection message? You should be using the Tulip driver, not the de4x5 driver. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From adam@rtg.com Wed, 30 Aug 2000 15:22:42 -0700 (PDT) Date: Wed, 30 Aug 2000 15:22:42 -0700 (PDT) From: Adam Goldman adam@rtg.com Subject: [tulip] dfe-570tx hangs at ifconfig I'm experiencing system hangs when bringing up the interfaces of D-Link DFE-570TX quad Tulip cards. If the interfaces are ifconfig'd in a specific order, the machine will lock hard. Some orders of ifconfig'ing avoid hanging the machine, but subsequent network traffic will hang the system. No error messages are displayed, the machine just goes unresponsive as soon as the ifconfig command is issued. I have tried both an Asus P3B-F and a Tyan S1857 motherboard, with similar results. Both are based on the BX chipset. I have tried two different DFE-570TX cards; the problem occurs with both of them. I have also tried replacing the DFE-570TX cards with Kingston KNE100TX single-port Tulip cards, and was not able to reproduce the hang between two of them, but since I only have two of the KNE100TX cards, it's possible that they too would cause the hang if there were four of them. The sequence to reproduce the hang depends on the motherboard and what set of cards are in the machine. For instance, with the P3B-F board and one DFE-570TX card in PCI slot 1, the sequence "ifconfig eth0 up; ifconfig eth1 up" causes a hang. On the other hand, on the S1857 motherboard, with the DFE-570TX in PCI slot 3, that sequence does not provoke a hang, but the sequence "ifconfig eth0 up; ifconfig eth3 up" does. Although I could not reproduce a hang with two of the KNE100TX cards, I was able to reproduce a hang between a KNE100TX and a DFE-570TX. This was with the S1857 motherboard, the DFE-570TX in PCI slot 3, and the KNE100TX in PCI slot 4. The KNE100TX was eth0 and the DFE-570TX was eth1-4. The sequence "ifconfig eth3 up; ifconfig eth0 up" induced a hang. All tests were done under Linux 2.2.16 with the "2.2.16combo" errata patch from www.linux.org.uk and patches to the initrd and linuxrc code. Other than the network cards, the only cards in the machines under test were AGP video cards. Version "0.92 4/17/2000" and 0.89H of the Tulip driver displayed this problem, as well as v0.544 of the de4x5 driver. Does anyone have any idea what might be going wrong here? I would like to get this machine working as soon as possible and would appreciate any suggestions as to how to resolve or further investigate this problem. -- Adam Goldman From nmoran6@mediaone.net Wed, 30 Aug 2000 18:20:18 -0500 Date: Wed, 30 Aug 2000 18:20:18 -0500 From: nmoran6@mediaone.net nmoran6@mediaone.net Subject: [tulip] Linksys 10/100 network everywhere pci card Hi. I have not been on this list long, but have seen a post about the Linksys Network Everywhere Card being the problem and that everything worked great after the person placed a Fast Ethernet 10/100 in his computer. I would like to know if the Linksys 10/100 Network Everywhere PCI card works with the tulip driver. I havent been able to play around with it on Linux yet because Windows, as usual decided to go haywire. Thank You. Niklas Moran From becker@scyld.com Thu, 31 Aug 2000 00:16:08 -0400 (EDT) Date: Thu, 31 Aug 2000 00:16:08 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Linksys 10/100 network everywhere pci card On Wed, 30 Aug 2000 nmoran6@mediaone.net wrote: > I have not been on this list long, but have seen a post about the > Linksys Network Everywhere Card being the problem and that > everything worked great after the person placed a Fast Ethernet > 10/100 in his computer. I would like to know if the Linksys 10/100 > Network Everywhere PCI card works with the tulip driver. I havent > been able to play around with it on Linux yet because Windows, as > usual decided to go haywire. The new Linksys cards use ADMtek Comet or Centaur chips. You'll need a recent Tulip driver to work with these chips. http://www.scyld.com/network/tulip.html ftp://www.scyld.com/pub/network/tulip.c With some cards, if you have a full duplex connection you may need the latest driver: ftp://www.scyld.com/pub/network/test/tulip.c Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From toby@earth.li Thu, 31 Aug 2000 12:18:25 +0100 Date: Thu, 31 Aug 2000 12:18:25 +0100 From: Toby Jaffey toby@earth.li Subject: [tulip] tulip and SMP On Wed, Aug 30, 2000 at 10:42:45AM +0200, geofstro@monaco.mc wrote: > I also have a problem with SMP support. My board supports SMP so I need > to run that version of the kernel. > If I compile tulip.c using the standard compile command I get the error, > "compiled for Linux 2.2.14 but you're running Linux 2.2.14-SMP. > I tried compiling using SMP options that I found from another web-site; > but I still got the above error as a result of insmod. > Does it work with SMP? I use an LNE100TX with my dual Celeron (Abit BP6) board. I've never had any problems. I always compile with -D__SMP__ tulip.c 0.90f had an SMP compile example, SMP-compile-command: "gcc -D__SMP__ -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall -Wstrict-prototypes -O6 -c tulip.c `[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS` -- ___ ___ (o o) Hey! It compiles! Ship it! (o o) ( V ) ( V ) /--m-m-----------------------www.nott.ac.uk/~psystrj-------------------m-m--\ From toby@earth.li Thu, 31 Aug 2000 12:15:18 +0100 Date: Thu, 31 Aug 2000 12:15:18 +0100 From: Toby Jaffey toby@earth.li Subject: [tulip] Yet another LNE100TX problem On Sat, Aug 26, 2000 at 07:54:53AM -0400, Jason M'Sadoques wrote: > I just purchased a Linksys EtherFast 10/100 with the LNE100TX version > 4.1 chip. I'm running RedHat 6.2, Kernel 2.2.14. I have determined that > I need the latest version of the tulip.c driver. I have downloaded these > four files: tulip.c, pci-scan.c, pci-scan.h, kern_compat.h. When I > compile with the command given at the end of tulip.c: gcc -DMODULE -Wall > -Wstrict-prototypes -O6 -c tulip.c, I get hundreds of errors, like the > following: > In file included from /usr/include/linux/string.h:37, > from tulip.c:143: [snip] > My compiler is gcc 2.95. I had the same problem with 2.95 > So the question is: what do I need to do to get tulip.c to compile on my > system? gcc 2.72 works for me. -- (o_ | Toby Jaffey : www.nott.ac.uk/~psystrj/ //\ | "For non-deterministic read 'Inhabited by pixies.'" V_/_ | From fschmuck@chartertn.net Thu, 31 Aug 2000 08:01:37 -0400 Date: Thu, 31 Aug 2000 08:01:37 -0400 From: Frank J. Schmuck fschmuck@chartertn.net Subject: [tulip] tulip and SMP Toby Could you attach the compiled tulip.o file that works with SMP? I also have a BP6 and LNX100TX. Thanks Frank -----Original Message----- From: tulip-admin@scyld.com [mailto:tulip-admin@scyld.com]On Behalf Of Toby Jaffey Sent: Thursday, August 31, 2000 7:18 AM To: tulip@scyld.com Subject: Re: [tulip] tulip and SMP On Wed, Aug 30, 2000 at 10:42:45AM +0200, geofstro@monaco.mc wrote: > I also have a problem with SMP support. My board supports SMP so I need > to run that version of the kernel. > If I compile tulip.c using the standard compile command I get the error, > "compiled for Linux 2.2.14 but you're running Linux 2.2.14-SMP. > I tried compiling using SMP options that I found from another web-site; > but I still got the above error as a result of insmod. > Does it work with SMP? I use an LNE100TX with my dual Celeron (Abit BP6) board. I've never had any problems. I always compile with -D__SMP__ tulip.c 0.90f had an SMP compile example, SMP-compile-command: "gcc -D__SMP__ -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall -Wstrict-prototypes -O6 -c tulip.c `[ -f /usr/include/linux/modversions.h ] && echo -DMODVERSIONS` -- ___ ___ (o o) Hey! It compiles! Ship it! (o o) ( V ) ( V ) /--m-m-----------------------www.nott.ac.uk/~psystrj-------------------m-m-- \ _______________________________________________ tulip mailing list tulip@scyld.com http://www.scyld.com/mailman/listinfo/tulip From toby@earth.li Thu, 31 Aug 2000 13:15:05 +0100 Date: Thu, 31 Aug 2000 13:15:05 +0100 From: Toby Jaffey toby@earth.li Subject: [tulip] tulip and SMP On Thu, Aug 31, 2000 at 08:01:37AM -0400, Frank J. Schmuck wrote: > Toby > Could you attach the compiled tulip.o file that works with SMP? I also have > a BP6 and LNX100TX. No, sorry. As I understand, kernel modules are dependent on your kernel version. Just compile it. -- www.nott.ac.uk/~psystrj ..::::::::::::::::::::::::::::::::::::::::::::::::. /\_./o__ ....:::::::::' "Ummm, Trouble with grammar have I! ':::: (/^/(_^~' ''::::: Yes!" -Yoda- :::: ___.(_.)____ '::::::::::::::::::::::::::::::::::::::::::::::::::: From becker@scyld.com Thu, 31 Aug 2000 10:43:41 -0400 (EDT) Date: Thu, 31 Aug 2000 10:43:41 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] tulip and SMP On Wed, 30 Aug 2000 geofstro@monaco.mc wrote: > I also have a problem with SMP support. My board supports SMP so I need > to run that version of the kernel. > > If I compile tulip.c using the standard compile command I get the error, > "compiled for Linux 2.2.14 but you're running Linux 2.2.14-SMP. To repeat the previous articles: This is not a compiler or driver problem. It's a configuration problem with your installation. The message means that you compiled the module for a different kernel than kernel you are currently running. It was likely compiled against the uniprocessor kernel header files in your distribution. You are running the SMP kernel from your distribution, which has a different set of generated header files. Change the symbolic link /usr/include/linux to point to the correct set of header files. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution Annapolis MD 21403 From peterc@brosystems.com Thu, 31 Aug 2000 18:33:27 +0100 Date: Thu, 31 Aug 2000 18:33:27 +0100 From: peter church peterc@brosystems.com Subject: [tulip] D-Link DFE 570tx install problem Donald Becker wrote: > On Wed, 30 Aug 2000, peterc wrote: > > > I hope you will be able to help me with this. I am currently trying to > > install > > mandrake 7.1 onto a machine with 2 DFE570tx (4 port) cards on board. The O/S > > install seems to work fine. I reboot the machine and that goes ok as well > > the system comes back up and binds eth0 ,eth1 ,eth2 ,eth3 to the correct IP > > addresses. However when I look in the /var/log/messages file I get an error > > saying... > > > > kernel: eth0: media is unconnected, link down or incompatable connection. > > > > do I need to build and install a tulip driver or should it already be part > > of my kernel ? > > Or is there something else that I am doing wrong ? > > What driver are you using? > What is the detection message? > > You should be using the Tulip driver, not the de4x5 driver. > Donald Becker becker@scyld.com > Scyld Computing Corporation http://www.scyld.com > 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution > Annapolis MD 21403 Hi Thankyou for coming back to me on this at the moment the mandrake seems to be loading the de4x5. when I try to configure the tulip that is on the 7.0 disk it fails to load ! however the problem seemed to be that the card would not detect the base 10 hub that I was using to test the setup ! If I use a cross-cable and connect between the ports it works ok I will get the tulip code from the site and let you know how it goes thanks again Peter From brian@heptane.eng.yale.edu Thu, 31 Aug 2000 14:27:51 -0400 (EDT) Date: Thu, 31 Aug 2000 14:27:51 -0400 (EDT) From: Brian brian@heptane.eng.yale.edu Subject: [tulip] Q: Unresolved symbols w/ LNE100TX v4.1 insmod? Hi guys, I've compiled the latest version of the tulip driver (compilation is fine), but upon trying to insert it, I get a kernel version mismatch in that I have the errors: unresolved symbol init_etherdev_R4468631d unresolved symbol eth_type_trans_R6e012c3d .... .. Where should these symbols link to, and what's the best way to resolve this? (I saw a similar question on the archives, but I'm quite sure I'm trying to insert my newly compiled tulip.o, not the one in /usr/lib/modules...) I really appreciate your help! Thanks! - Brian