From blixt@hem.utfors.se Sun, 2 Sep 2001 09:21:23 +0200 Date: Sun, 2 Sep 2001 09:21:23 +0200 From: Lennart Blixt blixt@hem.utfors.se Subject: [tulip] 21143 TX problem 2.4.5 - 2.4.8 This is a multi-part message in MIME format. ------=_NextPart_000_0020_01C13390.A2598ED0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, up to 2.4.4, everything worked fine with my Compaq 5670 with a 21143 = embedded network card. But from 2.4.5 until 2.4.8, I get this in = /var/log messages. Aug 31 21:20:57 lux kernel: NETDEV WATCHDOG: eth0: transmit timed out Aug 31 21:20:57 lux kernel: eth0: 21140 transmit timed out, status = f0260000, SIA 000000c6 ffff0000 fffbff7f 8ff54008, resetting... What can I do to fix this? I=B4m not into compliling. Not yet, anyway. bregs --Lennart. ------=_NextPart_000_0020_01C13390.A2598ED0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

up to 2.4.4, everything worked fine with my Compaq = 5670 with=20 a 21143 embedded network card. But from 2.4.5 until 2.4.8, I get this in = /var/log messages.

Aug 31 21:20:57 lux kernel: NETDEV WATCHDOG: eth0: transmit timed = out

Aug 31 21:20:57 lux kernel: eth0: 21140 transmit timed out, status = f0260000,=20 SIA 000000c6 ffff0000 fffbff7f 8ff54008, resetting...

What can I do to fix this? I=B4m not into = compliling. Not yet,=20 anyway.

bregs

--Lennart.

------=_NextPart_000_0020_01C13390.A2598ED0-- From daniel.pfenniger@obs.unige.ch Mon, 03 Sep 2001 09:08:21 +0200 Date: Mon, 03 Sep 2001 09:08:21 +0200 From: Daniel Pfenniger daniel.pfenniger@obs.unige.ch Subject: [tulip] Re: 21143 TX problem 2.4.5 - 2.4.8 (Lennart Blixt) > Hi, > > up to 2.4.4, everything worked fine with my Compaq 5670 with a 21143 = > embedded network card. But from 2.4.5 until 2.4.8, I get this in = > /var/log messages. > > Aug 31 21:20:57 lux kernel: NETDEV WATCHDOG: eth0: transmit timed out > > Aug 31 21:20:57 lux kernel: eth0: 21140 transmit timed out, status = > f0260000, SIA 000000c6 ffff0000 fffbff7f 8ff54008, resetting... > > What can I do to fix this? I=B4m not into compliling. Not yet, anyway. > > bregs > > --Lennart. I experienced too that channel bonding for tulip driver wasn't working anymore since kernel 2.4.5. Removing the tulip driver directory in the kernelsource of 2.4.8 and replacing it with the 2.4.4 one solved the problem. Dan 같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같 Dr Daniel Pfenniger | Daniel.Pfenniger@obs.unige.ch Geneva Observatory, University of Geneva | tel: +41 (22) 755 2611 CH-1290 Sauverny, Switzerland | fax: +41 (22) 755 3983 같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같 From rjp@rjpsw.f2s.com Mon, 3 Sep 2001 12:59:08 -0400 Date: Mon, 3 Sep 2001 12:59:08 -0400 From: Ryan J Powers rjp@rjpsw.f2s.com Subject: [tulip] LinkSys LNE100TX v5 Info Hi, I was referred by those in #linpeople on OpenProjects. I'm trying to write drivers for my NIC for BeOS. I've never done anything with Linux drivers, so I can't simply reverse engineer the sources I have. Actually I lied. My friend is trying to write drivers for me. He's done it before, and I'd like to learn, but anyways. I'm told I need to know what the registers are, and how to initialize the ring buffers properly. I hope someone out there can help me, because I have no idea what that means, and I don't want to buy a new NIC. Thanks --ryan From michael.thaler@Physik.TU-Muenchen.DE Tue, 4 Sep 2001 14:21:12 +0200 Date: Tue, 4 Sep 2001 14:21:12 +0200 From: Michael Thaler michael.thaler@Physik.TU-Muenchen.DE Subject: [tulip] Problems with SMC EZ 10/100 Cardbus Card Hello! I have a SMC EZ 10/100 Cardbus Ethernet Card, Version SMC8034TX. I want to use the card with my Sony VAIO F212 (which is also known as Sony VAIO F104K). I am using debain unstable with kernel 2.4.9 and pcmcia-cs-version 3.1.28 which I compiled from the source with debian/rules binary-modules and installed the module with dpkg. I also have a noname NE2000 compatible 10 mbit ethernet card (no cardbus) which works just fine. I did not compile the pcmcia-drivers in the kernel. There are two drivers in /etc/pcmcia/config: card "SMC EZ 10/100 Fast Ethernet" manfid 0x01bf, 0x2220 bind "tulip_cb" card "SMC EZ 10/100 Fast Ethernet" manfid 0x01bf, 0x2225 bind "tulip_cb" When I insert my card, the computer makes 2 high beeps and everything seems to work fine. lsmod says: tulip_cb 32160 2 cb_enabler 2752 2 [tulip_cb] ds 6864 2 [cb_enabler] i82365 22480 2 pcmcia_core 42880 0 [cbenabler ds i82365] Here are the relevant parts from dmesg: ... PCI: Sharing IRQ 9 with 00:0a.0 Ricoh RL5C478 rev 80 PCI-to-CardBus at slot 00:0c, mem 0x10000000 host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 2/5] host opts [1]: [isa irq] [io 3/6/1] [mem 3/6/1] [pci irq 9] [lat 168/176] [bus 6/9] ISA irqs (default) = 3,4,5,7,10,11,12 PCI status changes cs: cb_alloc(bus 2): vendor 0x1011, device 0x0019 ROM image dump: image 0: 0x000000-0x0001ff, signature PCIR cs: cb_config(bus 2) cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x3c0-0x3df 0x4d0-0x4d7 cs: IO port probe 0x0230-0x032f: clean. cs: IO port probe 0x0338-0x0377: clean. cs: IO port probe 0x0380-0x0387: clean. cs: IO port probe 0x0390-0x0397: clean. cs: IO port probe 0x03a0-0x03bf: clean. cs: IO port probe 0x03e0-0x04cf: clean. cs: IO port probe 0x04d8-0x04ff: clean. cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0a00-0x0aff: clean. cs: IO port probe 0x0c00-0x0cff: clean. fn 0 bar 1: io 0x280-0x2ff fn 0 bar 2: mem 0x600c0000-0x600c03ff fn 0 rom: mem 0x60080000-0x600bffff irq 9 cs: cb_enable(bus 2) bridge io map 0 (flags 0x21): 0x280-0x2ff bridge mem map 0 (flags 0x1): 0x60080000-0x600c0fff tulip_attach(device 02: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 0x280, 00:E0:29:47:D4:54, IRQ 9. 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 3000 status 7809 advertising 00a1. eth0: Advertising 01e1 on PHY 1, previously advertising 00a1. eth0: Advertising 01e1 (to advertise is 01e1). Everything seems just fine as far as I understand that. But when I try to ping a computer in the network, I don't get any response. All packets are lost. I also got some warnings: Watchdog: NETDEV timeout (I hope I remember that right, its probably not literal). When I use my NE2000 compatible card in the same network environment everything works just fine. If I boot Win2000 on the same computer and use the SMC EZ 10/100 Cardbus Card with Win2000 everything works fine, too. So the card seems and the cables seem to be o.k. (I translate that from German) Windows shows me: SMC EZ-CardBus-10/100-Ethernet-Adapter (SMC8034) #2 PCI Bus 129, Device 0, Function 0 Resources: I/O-Range: FE80-FEFF Memoryrange: FFDFEC00-FFDFEFFF IRQ: 9 I would really appreciate any help or any hints how to track down the problems. I saw other people had the same problems. I read some of the mails in the archive, but I did not understand how to solve the problem. Greetings, Michael From janmag@online.no Wed, 5 Sep 2001 12:41:00 +0200 Date: Wed, 5 Sep 2001 12:41:00 +0200 From: Jan Egil Magelie janmag@online.no Subject: [tulip] Cpq Pressario and network problems This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C13608.048A5F20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi! I am having some problems with the setup on my cpq pressario. I am = running suse 7.2 and I have configured the network card. Everything looks fine, all the = logs reports no errors and it looks like the tcp/ip stack is fine, but = for some reason I cannot make any connection over the network. My question is, does this have something to do with the duplex of = the card or is there something else? Both my machines have 10/100 = network cards, and they both report running at 100Mbps, full duplex. After pinging my desktop machine, I do ifconfig and I see that there is = errors reported on Tx. I have sniffed the interface, but there doesn't seem to be any traffic = at all. Anybody got any similiar experinces, or tips on how I can attack this = problem. Jan Egil Magelie ------=_NextPart_000_0010_01C13608.048A5F20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi!
 
    I am having some = problems with=20 the setup on my cpq pressario. I am running suse 7.2
and I have configured the network card. = Everything=20 looks fine, all the logs reports no errors and it looks like the tcp/ip = stack is=20 fine, but for some reason I cannot make any connection over the=20 network.
 
    My question is, does = this have=20 something to do with the duplex of the card or is there something else? = Both my=20 machines have 10/100 network cards, and they both report running at = 100Mbps,=20 full duplex.
 
After pinging my desktop machine, I do = ifconfig and=20 I see that there is errors reported  on Tx.
I have sniffed the interface, but there = doesn't=20 seem to be any traffic at all.
 
Anybody got any similiar experinces, or = tips on how=20 I can attack this problem.
 
Jan Egil = Magelie
------=_NextPart_000_0010_01C13608.048A5F20-- From becker@scyld.com Wed, 5 Sep 2001 13:11:18 -0400 (EDT) Date: Wed, 5 Sep 2001 13:11:18 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Cpq Pressario and network problems On Wed, 5 Sep 2001, Jan Egil Magelie wrote: > I am having some problems with the setup on my cpq pressario. I am > running suse 7.2 and I have configured the network card. Everything > looks fine, all the logs reports no errors and it looks like the > tcp/ip stack is fine, but for some reason I cannot make any connection > over the network. What Presario? Which adapter (chip type)? Which driver version? What is the detection message? The output of tulip-diag -aem might also be necessary to suggest a fix. If you have a Conexant chip on a Presario 1700 series laptop, you will need driver version v0.92w or later. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From becker@scyld.com Wed, 5 Sep 2001 13:22:44 -0400 (EDT) Date: Wed, 5 Sep 2001 13:22:44 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] LinkSys LNE100TX v5 Info On Mon, 3 Sep 2001, Ryan J Powers wrote: > I was referred by those in #linpeople on OpenProjects. I'm trying > to write drivers for my NIC for BeOS. Note that the BeOS license conflicts with the GPL. If you use the Linux driver source, you may not distribute the resulting driver. > I've never done anything with > Linux drivers, so I can't simply reverse engineer the sources I have. > Actually I lied. My friend is trying to write drivers for me. He's done > it before, and I'd like to learn, but anyways. I'm told I need to know > what the registers are, and how to initialize the ring buffers properly. > I hope someone out there can help me, because I have no idea what that > means, and I don't want to buy a new NIC. That's a bad place to start. It takes a quite a bit of experience before you can reliably produce a working device driver. It's far easier to just buy hardware that works right now. For one thing, you'll need a working device driver to test the new one. The best databook to learn about the Tulip design is the 21140 Hardware Reference Manual. You'll have to settle for the slightly more complicated 21143 manual. Do a search at http://developer.intel.com Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From rjp@rjpsw.f2s.com Wed, 5 Sep 2001 14:34:07 -0400 Date: Wed, 5 Sep 2001 14:34:07 -0400 From: Ryan J Powers rjp@rjpsw.f2s.com Subject: [tulip] LinkSys LNE100TX v5 Info Thank you for the info. I didn't plan on distributing the driver at all. My friend has successfully written drivers for his NIC, and he was going to assist (do most of it) for my NIC if I could get the info he needed. I haven't yet looked, but what exactly is the 21140 and 21143? Are they data sheets for the chipset used? Thanks a bunch. Ryan On Wednesday, September 5, 2001, at 01:22 , Donald Becker wrote: > On Mon, 3 Sep 2001, Ryan J Powers wrote: > >> I was referred by those in #linpeople on OpenProjects. I'm trying >> to write drivers for my NIC for BeOS. > > Note that the BeOS license conflicts with the GPL. If you use the Linux > driver source, you may not distribute the resulting driver. > >> I've never done anything with >> Linux drivers, so I can't simply reverse engineer the sources I have. >> Actually I lied. My friend is trying to write drivers for me. He's done >> it before, and I'd like to learn, but anyways. I'm told I need to know >> what the registers are, and how to initialize the ring buffers >> properly. >> I hope someone out there can help me, because I have no idea what that >> means, and I don't want to buy a new NIC. > > That's a bad place to start. It takes a quite a bit of experience > before you can reliably produce a working device driver. It's far > easier to just buy hardware that works right now. For one thing, you'll > need a working device driver to test the new one. > > The best databook to learn about the Tulip design is the 21140 Hardware > Reference Manual. You'll have to settle for the slightly more > complicated 21143 manual. Do a search at http://developer.intel.com > > Donald Becker becker@scyld.com > Scyld Computing Corporation http://www.scyld.com > 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters > Annapolis MD 21403 410-990-9993 > From kenthunt@yahoo.com Wed, 5 Sep 2001 14:33:11 -0700 (PDT) Date: Wed, 5 Sep 2001 14:33:11 -0700 (PDT) From: Kent Hunt kenthunt@yahoo.com Subject: [tulip] Re: Conexant LANfinity Okay, What I'm doing recently since I recompile kernels very often is: 1. Have your kernel source in /usr/src/linux or wherever your distro says to put it and cd to that directory. 2. rm drivers/net/tulip/* removing the contents of the current 2.4 kernel drivers. 3. copy to drivers/net/tulip recent versions of kern_compat.h, pci-scan.c, pci-scan.h, and tulip.c. Cris Lameter put a tarball with these in http://lameter.com/kernel/tulip-0.92wax.tar.gz 4. Replace the Makefile that you find in the tarball with the following one: # # Makefile for the kernel LANfinity tulip device driver. # # The target object and module list name. obj-y := obj-n := obj-m := obj- := obj-$(CONFIG_TULIP) += tulip.o pci-scan.o include $(TOPDIR)/Rules.make 5. (Optional) If you do a lot of kernel compiles, make a kernel patch. I haven't seen much activity in the 2.4 kernel regarding the tulip driver so this patch helps a lot. You have now the source file completely embeded in your kernel. Just select the tulip driver as module (I haven't tried, maybe it will work compiled in as well) and recompile the kernel. See how red hatters to that. I use Debian. Install the new kernel and load the tulip module with "modprobe tulip" and then you should have your device ready for ifconfig and route setup. If everything goes right then the pciscan module should be automatically loaded because modprobe will compute the module dependencies. Kent --- Markus Trimmel wrote: > Hi Kent, > > I am not a Linux profesional like you. I have tried > to compile the tulip > module but I didnt get it to run. Could you send me > your module, maybe this > > I am near an hangup of my self, please help if you > can find time. > > I am using the kernel 2.4.2-2 on Redhat 7.1. > > Hopefully thanks for your help > > greetings > > Markus __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ From kmail@dolphinsearch.com Wed, 5 Sep 2001 14:58:08 -0700 Date: Wed, 5 Sep 2001 14:58:08 -0700 From: kmail kmail@dolphinsearch.com Subject: [tulip] unsubcribe unsubcribe From gbj@theforce.com.au Wed, 05 Sep 2001 22:17:58 +1000 Date: Wed, 05 Sep 2001 22:17:58 +1000 From: Grahame Jordan gbj@theforce.com.au Subject: [tulip] CNet Pro200 Hi, I have many CNET Pro200WL ethernet cards. Davicom DM9102 chipset. I am using the dmfe driver but unfortunately the performance is pitiful. Have tried setting to mode=1 ( Half duplex ) and mode=5 (full Duplex). The speed is about 0.25MBps. However if I use an intel eepro100 the speed is 10MBps. Does anyone know if this is a characteristic of the card or is it the driver? Will the tulip driver work with this card? The one out of the box does not. RH6.2. We are using kernel 2.2.16. Thanks Grahame Jordan From becker@scyld.com Thu, 6 Sep 2001 02:06:14 -0400 (EDT) Date: Thu, 6 Sep 2001 02:06:14 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] CNet Pro200 On Wed, 5 Sep 2001, Grahame Jordan wrote: > I have many CNET Pro200WL ethernet cards. Davicom DM9102 chipset. I am > using the dmfe driver but unfortunately the performance is pitiful. > Have tried setting to mode=1 ( Half duplex ) and mode=5 (full Duplex). > The speed is about 0.25MBps. However if I use an intel eepro100 the > speed is 10MBps. Are you getting any errors? Read the dmfe.c code. Pay particular attention to the packet CRC calculation. You'll see why I won't put that work-around into the regular Tulip driver. > Does anyone know if this is a characteristic of the card or is it the > driver? Will the tulip driver work with this card? The one out of the > box does not. RH6.2. We are using kernel 2.2.16. The v0.92 Tulip driver will work, just not very well. I recommend using the dmfe.c driver -- preferably a recent one. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From michael.thaler@Physik.TU-Muenchen.DE Thu, 6 Sep 2001 15:27:08 +0200 Date: Thu, 6 Sep 2001 15:27:08 +0200 From: Michael Thaler michael.thaler@Physik.TU-Muenchen.DE Subject: [tulip] Problems with SMC EZ 10/100 Cardbus Card Hello, I read the information about the tulip-driver on www.scyld.com/network, I tried to edit the /etc/pcmcia/config file and replaced the bind "tulip_cb" with bind "smc91c92_cs.o", but that did not work either. I also downloaded the tulip-diag program. I got the output: ./tulip-diag -fa: tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Digital DS21143 Tulip adapter at 0x280. Digital DS21143 Tulip chip registers at 0x280: 0x00: f8a08000 ffffffff ffffffff 00a41010 00a41210 f0660000 b20e2002 fbfffbff 0x40: e0000000 ffffcbf8 ffffffff 00000000 000000c6 ffff0000 fff80000 8ffb0000 Port selection is MII, 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 NWay status register is 000000c6. Internal autonegotiation state is 'Autonegotiation disabled'. ./tulip-diag -e: tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Digital DS21143 Tulip adapter at 0x280. Port selection is MII, 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 NWay status register is 000000c6. EEPROM 64 words, 6 address bits. PCI Subsystem IDs, vendor 10b8, device 8034. CardBus Information Structure at offset 0000003f. Ethernet MAC Station Address 00:E0:29:47:D4:54. EEPROM transceiver/media description table.Leaf node at offset 30, default media type 0800 (Autosense). 1 transceiver description blocks: Media MII, block type 3, length 21. MII interface PHY 0 (media type 11). 21143 MII initialization sequence is 2 words: 0886 0002. 21143 MII reset sequence is 2 words: 0886 0002. Media capabilities are 7800, advertising 01e1. Full-duplex map 5000, Threshold map 1800. No MII interrupt. MII PHY found at address 1, status 0x7809. MII PHY #1 transceiver registers: 3000 7809 0040 6212 00a1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 5000 e400 0000 0000 0000 0000 0600 0000 0036 0008 0f00 ff00 0036 4000 0000 000b. Internal autonegotiation state is 'Autonegotiation disabled'. I have no clue if this is o.k. or nor. How I mentioned before, the card works on the same computer on the same network with Win2000, so the card seems to be o.k. and everything works fine with a NE2000 card on the same computer and the same network. What else can I do to find this error? I looked through the tulip-mailing list archive and found other people having the same problems but they did nothing that helped for me. I read there is a debug=n with n=1,2,3,... option in the driver but I don't know how to load the driver with this option. Writing bind "tulip_cb debug=7" in /etc/pcmcia/config did not help. What else can I do? I am not an expert in Linux or programming and I really don't know why that card is not working. I would really appretiate some help. Greetings, Michael Thaler From becker@scyld.com Thu, 6 Sep 2001 11:26:42 -0400 (EDT) Date: Thu, 6 Sep 2001 11:26:42 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Problems with SMC EZ 10/100 Cardbus Card On Thu, 6 Sep 2001, Michael Thaler wrote: > I read the information about the tulip-driver on > www.scyld.com/network, I tried to edit the /etc/pcmcia/config file and > replaced the bind "tulip_cb" with bind "smc91c92_cs.o", but that did > not work either. What document suggested that you try the 91c92 driver? That's a driver for an old ISA/PCMCIA design, while you have a CardBus card. What driver were you attempting to use? What was the detection message? > I also downloaded the tulip-diag program. I got the output: > ./tulip-diag -fa: ... > Digital DS21143 Tulip chip registers at 0x280: > 0x00: f8a08000 ffffffff ffffffff 00a41010 00a41210 f0660000 b20e2002 > fbfffbff > 0x40: e0000000 ffffcbf8 ffffffff 00000000 000000c6 ffff0000 fff80000 > 8ffb0000 > Port selection is MII, half-duplex. ... > MII PHY #1 transceiver registers: > 3000 7809 0040 6212 00a1 0000 0000 0000 You don't have link beat. What is this machine connected to? (The "link partner".) > What else can I do to find this error? I looked through the > tulip-mailing list archive and found other people having the same > problems but they did nothing that helped for me. What problem do you have? Many different problems look alike, "doesn't work". All SMC CardBus cards are known to work with the Scyld released driver. The instructions are at http://www.scyld.com/network/updates.html Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From kwunderlich@yahoo.com Thu, 6 Sep 2001 10:37:18 -0700 (PDT) Date: Thu, 6 Sep 2001 10:37:18 -0700 (PDT) From: Kevin Wunderlich kwunderlich@yahoo.com Subject: [tulip] kernel 2.4.x I am currently using Red Hat 6.2 (kernel 2.2.14-5.0) and my Linksys LNE100TX(ver 4) card works great with the tulip driver that was provided by the driver disk that came with the nic. Recently I removed the Red Hat 6.2 installation and upgraded to Red Hat 7.1 (kernel 2.4.? - i dont remember exact version). I downloaded the latest version of the tulip driver from scyld.com and rebuilt the module as I had for Red Hat 6.2, but the latest version of the tulip driver was incompatible. So, I guess this question is directed at Donald, but are you currently working on making the tulip driver compatible with the 2.4.x kernel? I have looked at previous postings on several sites regarding this question, but have not found any information on this. I would like to upgrade to the new kernel without buying additional nic's if possible. Thanks in advance, Kevin __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com From becker@scyld.com Thu, 6 Sep 2001 15:12:00 -0400 (EDT) Date: Thu, 6 Sep 2001 15:12:00 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] kernel 2.4.x On Thu, 6 Sep 2001, Kevin Wunderlich wrote: > ... Recently I removed the Red > Hat 6.2 installation and upgraded to Red Hat 7.1 > (kernel 2.4.? - i dont remember exact version). I > downloaded the latest version of the tulip driver from > scyld.com and rebuilt the module as I had for Red Hat > 6.2, but the latest version of the tulip driver was > incompatible. So, I guess this question is directed > at Donald, but are you currently working on making the > tulip driver compatible with the 2.4.x kernel? Yes. The RPM is named ftp://www.scyld.com/pub/network/netdrivers-3.0-1.src.rpm If compiling individually, you'll need the updated driver and support files (e.g. 'kern-compat.h' v1.9). Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From meebert@yahoo.com Fri, 7 Sep 2001 08:12:33 -0700 (PDT) Date: Fri, 7 Sep 2001 08:12:33 -0700 (PDT) From: iS meebert@yahoo.com Subject: [tulip] delaying eth1... newbie help RE: Linksys Fast Ethernet v.4 (Lite-on chip) on RH6.1 (2.2.12-20) After downloading, compiling and installing the latest tulip, I get "delaying eth1 init... [FAILED]" I'm using a manual ip setup for now although eventually I'd like to use this card as a 10baseT half duplex cable modem (dhcp) card. I'm fairly new to linux and I'm not sure how to find a detailed error message that will tell me why the eth1 device won't start. I also have a 3COM/59x/eth0 installed which works fine. I've done everything I can think of, and read the whole ethernet HOWTO as well as the scydl tulip pages. Please help! Is ===== **The world is no nursery. - Sigmund Freud __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com From becker@scyld.com Fri, 7 Sep 2001 15:12:14 -0400 (EDT) Date: Fri, 7 Sep 2001 15:12:14 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] delaying eth1... newbie help On Fri, 7 Sep 2001, iS wrote: > RE: Linksys Fast Ethernet v.4 (Lite-on chip) on RH6.1 > (2.2.12-20) > > After downloading, compiling and installing the latest > tulip, I get "delaying eth1 init... [FAILED]" What is the detection message? (Run 'dmesg' to see...) > I'm using a manual ip setup for now although > eventually I'd like to use this card as a 10baseT half > duplex cable modem (dhcp) card. That implies that the driver is working. If so, you have an IP address configuration problem, or perhaps its as simple as not providing the correct module name in /etc/modules.conf. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From emperor@mesopotamia.com Sat, 8 Sep 2001 03:03:18 +0200 Date: Sat, 8 Sep 2001 03:03:18 +0200 From: Emperor of Mesopotamia emperor@mesopotamia.com Subject: [tulip] Cpq Pressario and network problems -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for all the help! After a lot of anguish I finally got it to work. Unfortunately I had to install RH7.1, but since I had really begun to use the machine yet this was a small loss. I had to remove the apm part of the pci-scan.c file before it would compile right. After that it was walk in the park. Jan Egil Magelie - ----- Original Message ----- From: "Donald Becker" To: "Jan Egil Magelie" Cc: Sent: Wednesday, September 05, 2001 7:11 PM Subject: Re: [tulip] Cpq Pressario and network problems > On Wed, 5 Sep 2001, Jan Egil Magelie wrote: > > > I am having some problems with the setup on my cpq pressario. I > > am running suse 7.2 and I have configured the network card. > > Everything looks fine, all the logs reports no errors and it > > looks like the tcp/ip stack is fine, but for some reason I cannot > > make any connection over the network. > > What Presario? Which adapter (chip type)? > Which driver version? > What is the detection message? > > The output of > tulip-diag -aem > might also be necessary to suggest a fix. > > If you have a Conexant chip on a Presario 1700 series laptop, you > will need driver version v0.92w or later. > > Donald Becker becker@scyld.com > Scyld Computing Corporation http://www.scyld.com > 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters > Annapolis MD 21403 410-990-9993 > > > _______________________________________________ > tulip mailing list, tulip@scyld.com > To change to digest mode or unsubscribe visit > http://www.scyld.com/mailman/listinfo/tulip > -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use iQA/AwUBO5lgRrJvsAEex0msEQIuxwCg7L9Z3Gb6cGqZ/L5nBOGUpm6QjA4AoP9U SgTMhdV9H9xSFgoqR89IalVG =N+bC -----END PGP SIGNATURE----- From goemon@anime.net Fri, 7 Sep 2001 19:09:29 -0700 (PDT) Date: Fri, 7 Sep 2001 19:09:29 -0700 (PDT) From: Dan Hollis goemon@anime.net Subject: [tulip] new linksys lne100tx rev 5.0 Picked up some linksys lne100tx cards from staples today. Linksys has released a new rev 5.0 replacing rev 4.1. They removed the rom socket (guess noone ever used it) and the wake-on-lan jumper. Linksys also appear to finally have got their own MAC vendor code 00:04:5A so they no longer have to use Runtop Inc's 00:20:78. linksys4.1: eth0: ADMtek Comet rev 17 at 0xe400, 00:20:78:0E:40:41, IRQ 5. linksys5.0: eth0: ADMtek Comet rev 17 at 0xe400, 00:04:5A:55:BE:F2, IRQ 5. The difference from lspci -vvxxx: --- linksys4.1 Fri Sep 7 11:54:07 2001 +++ linksys5.0 Fri Sep 7 11:54:15 2001 @@ -8,11 +8,11 @@ Region 1: Memory at e312b000 (32-bit, non-prefetchable) [size=1K] Expansion ROM at [disabled] [size=128K] Capabilities: [c0] Power Management version 2 - Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) - Status: D0 PME-Enable+ DSel=0 DScale=0 PME+ + Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=100mA PME(D0+,D1+,D2+,D3hot+,D3cold+) + Status: D0 PME-Enable+ DSel=0 DScale=0 PME- 00: 17 13 85 09 07 00 90 02 11 00 00 02 08 20 00 00 10: 01 e4 00 00 00 b0 12 e3 00 00 00 00 00 00 00 00 -20: 00 00 00 00 00 00 00 00 02 02 00 00 17 13 74 05 +20: 00 00 00 00 00 00 00 00 00 00 00 00 17 13 74 05 30: 00 00 00 00 c0 00 00 00 00 00 00 00 05 01 ff ff 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 @@ -22,7 +22,7 @@ 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -c0: 01 00 02 fe 00 81 00 00 00 00 00 00 00 00 00 00 +c0: 01 00 82 fe 00 01 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -Dan -- [-] Omae no subete no kichi wa ore no mono da. [-] From Stock_Tips@mindspring.com Sat, 8 Sep 2001 19:18:46 Date: Sat, 8 Sep 2001 19:18:46 From: Stock_Tips@mindspring.com Stock_Tips@mindspring.com Subject: [tulip] (no subject) ANALYST BUY RECOMMENDATION

URGENT BUY RECOMMENDATION!

ANALYST BUY RECOMMENDATION:
  Cal-Bay International Inc. (Symbol: CBYI)

A REGISTERED INVESTMENT ADVISOR just released an investment opinion RECOMMENDING Cal-Bay (CBYI):
...as a Speculative Long-Term BUY.
...will hit a price target of $2.00 by 2002 and $5.00 by 2003!
...achieve earnings growth of 200 to 250% in the next 2 years.
...achieve earnings of approximately 25� per share by 2003.

Click HERE for QUOTE, News & full Investment Report!

QUOTES FROM THE INVESTMENT ADVISORS:

  • "A positive long-term investment opportunity exists with CBYI."
  • "We anticipate that liquidity will increase as well as coverage by additional analysts."
  • "The company has developed a network of strategic alliances that are designed to assist the company in obtaining a DOMINANT MARKET SHARE."
  • The current market in which Cal-Bay operates is currently estimated to exceed $900 million. Estimates calling for $25 Billion in sales by the year 2003."
  • "We expect the company to achieve it's current goal of Nasdaq OTCBB listing by the 4th quarter of 2001. Once on the larger exchange, we anticipate that liquidity will increase."
  • "We anticipate earnings will grow at a more rapid pace than revenues as a result of expanding net margins as well as the reduction of certain overhead costs that can be eliminated as a result of the expected acquisitions."
    Click HERE for QUOTE, News & full Investment Report!

    OTHER REASONS TO OWN THE STOCK:

  • CBYI IS GROWING AT A RAPID RATE. EARNINGS PER SHARE IS INCREASING!
  • CBYI is one of the FASTEST growing companies in distributing environmental and safety equipment instruments.
  • CBYI is a profitable company, has NO DEBT and is on track to beat ALL earnings estimates.
  • CBYI has increased revenue of 50% annually!
  • CBYI is a fully reporting SEC compliant company that has been in business since 1976.
  • CBYI has an excellent management team with several EXCLUSIVE contracts and an IMPRESSIVE client list including: Anheuser-Busch, Chevron Refining, Mitsubishi Heavy Industries, GE-Energy & Environmental Research and the U.S. Air Force.
  • CBYI share price keeps going UP, UP, and UP!
    Click HERE for QUOTE, News & full Investment Report!

    RAPIDLY GROWING INDUSTRY.
    Hold on tight for the largest Oil and Natural Gas expansion in U.S. History. Demand for Energy is at its highest level putting tremendous pressure on Scientific & Technical Instrumentation companies like CBYI. There is rapid expansion in the energy industry with the need for more power plants and cheaper fuel. CBYI is a major benefactor of this growing need because it supplies specialized "Smell Technology" analyzers for industrial applications in Natural Gas production and transmission.

    Note: Quotes are not available on every Financial Websites. This will be corrected with the recent 10-SB filing.

    Click HERE to be PERMANENTLY REMOVED!

    * NOTE: ALL removes honored. ALL IP addresses are LOGGED!






























































































































































    • Certain statements contained in this news release may be forward-looking statements within the meaning of  The Private Securities Litigation Reform Act of 1995. These statements may be identified by such terms as "expect", "believe", "may", "will", and "intend" or similar terms. We are NOT a registered investment advisor or a broker dealer. This is NOT an offer to buy or sell securities. No recommendation that the securities of the companies profiled should be purchased, sold or held by individuals or entities that learn of the profiled companies. This is an independent electronic publication that was paid $27,000 in cash by a non-affiliated, third party consultant for the electronic dissemination of this company information. Be advised that investments in companies profiled are considered to be high-risk and use of the information provided is for reading purposes only. If anyone decides to act as an investor they are advised not to invest without the proper advisement from an attorney or a registered financial broker, if any party decides to participate as an investor then it will be that investor's sole risk. Be advised that the purchase of such high-risk securities may result in the loss of some or all of the investment. The profiled companies make no warranties or guarantees as to the accuracy or the completeness of the disclosure. Investors should not rely solely on the information presented. Rather, investors should use the information provided by the profiled companies as a starting point for doing additional independent research on the profiled companies in order to allow the investor to form his or her own opinion and decision regarding investing in the profiled companies. Factual statements made by the profiled companies are made as of the date stated and are subject to change without notice. The receipt of this information shall not create, under any circumstances, any implication that there has been no change in the affairs of the company profiled since the date of review. Investing in micro-cap securities is highly speculative and carries an extremely high degree of risk and uncertainties. For further details concerning these risks and uncertainties, see the SEC filings of CBYI including the company's most recent annual and quarterly reports. It is possible that an investor's entire investment may be lost or impaired due to the speculative nature of the companies profiled. The owners of this publication may already own free trading shares in CBYI and may immediately sell all or a portion of these shares into the open market at or about the time this report is published. Subsequently we may from time to time buy or sell shares of CBYI in the open market. All information provided on the profiled companies may include information provided by outside sources, such as research reports, public filings, web sites or computer databases. Copyright � 2001 From becker@scyld.com Sat, 8 Sep 2001 21:02:53 -0400 (EDT) Date: Sat, 8 Sep 2001 21:02:53 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Sorry about that spam slipping through We have been getting quite a lot of attempted spam. This one slipped past the filter. I've added all of *.kr to the filter list. (Note that the mail was directed specifically to the tulip list, with no filterable subject line. It claimed to be from mindspring.com, but it was actually from a spam host in Korea.) Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From meebert@yahoo.com Sun, 9 Sep 2001 18:10:11 -0700 (PDT) Date: Sun, 9 Sep 2001 18:10:11 -0700 (PDT) From: iS meebert@yahoo.com Subject: [tulip] media type verification I'm trying to force a 10baseT HALF Duplex setting, and need to know how to verify the setting I'm getting. ifconfig shows a variable called txqueuelen and the value is 100. is that what I'm looking for? I've tried all the media types I can think of (0,9,12) and none make a change to that or any other value that I can tell. Is ===== **The world is no nursery. - Sigmund Freud __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com From becker@scyld.com Sun, 9 Sep 2001 21:59:36 -0400 (EDT) Date: Sun, 9 Sep 2001 21:59:36 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] media type verification On Sun, 9 Sep 2001, iS wrote: > I'm trying to force a 10baseT HALF Duplex setting, and > need to know how to verify the setting I'm getting. What driver version? What is the detection message? > ifconfig shows a variable called txqueuelen and the > value is 100. is that what I'm looking for? No, that's a software queue length, unrelated to the device driver setting. > I've tried all the media types I can think of (0,9,12) > and none make a change to that or any other value that > I can tell. The correct setting depends on the transceiver types available on your specific card. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From MBlomenkamp@t-online.de Wed, 12 Sep 2001 14:48:06 +0200 Date: Wed, 12 Sep 2001 14:48:06 +0200 From: Marcus Blomenkamp MBlomenkamp@t-online.de Subject: [tulip] Can't get Accton EN1207 to work in 100MBit Hi. This probably has been asked a million times before, perhaps someone will help me (newbie) anyway. I've got this fairly old NIC (bought around 1998?) and I can get it to work in 10baseT-FDX and Coax (10base2?) but not in 100baseTx-FDX. cat /proc/pci says: Bus 0, device 13, function 0: Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 17). IRQ 12. Master Capable. Latency=32. I/O at 0xe800 [0xe87f]. Non-prefetchable 32 bit memory at 0xdd001000 [0xdd00107f]. I've tried these module options with no effort: options tulip options=0x33 # seen on a website options tulip options=[0..19] # tried every The MII diagnosis programs (mii-tool + tulip-diag) say, the card has no MII module and that the eeprom is an old style. On the rear of the card I have one coax and two tp-connectors named 10M and 100M. For diagnosis there are four LEDs (Traffic, Coax, Link OK, 100M). As peer I have a 3c59x through crossover-cable (also tried a switch yesterday). If I set the card options to what should be 100*, the 100M-LED lights. Then if I connect the cable to the 100M-connector, the LinkOK-LED stays off (same on peer). If I connect the cable to the 10M-port, the LinkOK-LED goes on with the 100M-LED still lighting. However the peer says we're still in 10er mode. Needless to say that transmission doesn't work :-( So what can be further done to get a positive result? I've made pictures of the card which I could post/send so someone perhaps recognizes the card. Sorry for the length of this posting... Marcus From becker@scyld.com Wed, 12 Sep 2001 10:30:35 -0400 (EDT) Date: Wed, 12 Sep 2001 10:30:35 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Can't get Accton EN1207 to work in 100MBit On Wed, 12 Sep 2001, Marcus Blomenkamp wrote: > Subject: [tulip] Can't get Accton EN1207 to work in 100MBit ... > This probably has been asked a million times before... Did you do a google search? > help me (newbie) anyway. I've got this fairly old NIC (bought around 1998?) > and I can get it to work in 10baseT-FDX and Coax (10base2?) but not in > 100baseTx-FDX. What driver version are you trying to use? What is the detection message? Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From MBlomenkamp@t-online.de Wed, 12 Sep 2001 17:39:16 +0200 Date: Wed, 12 Sep 2001 17:39:16 +0200 From: Marcus Blomenkamp MBlomenkamp@t-online.de Subject: [tulip] Can't get Accton EN1207 to work in 100MBit Am Mittwoch, 12. September 2001 16:30 schrieb Donald Becker: > Did you do a google search? Yepp, lots of results pointing to this mailing list. groups.google.com also showed mainly problems not solutions :-(. I thought, perhaps someone recalled a very simple solution or nogo-situation. > What driver version are you trying to use? > What is the detection message? > Oh, I forgot. Kernels 2.4.7 + 2.4.9 dmesg shows (after loading with options=4): Linux Tulip driver version 0.9.15-pre6 (July 2, 2001) PCI: Found IRQ 12 for device 00:0d.0 tulip0: Transceiver selection forced to 10baseT-FDX. tulip0: Old format EEPROM on 'Accton EN1207' board. Using substitute media control info. tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media 10base2 (#1) described by a 21140 non-MII (0) block. tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #2 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 100baseTx (#3) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. eth0: Digital DS21140 Tulip rev 17 at 0xe800, 00:00:E8:15:DA:BA, IRQ 12. eth0: Using user-specified media 10baseT-FDX. cu Marcus From becker@scyld.com Wed, 12 Sep 2001 11:57:27 -0400 (EDT) Date: Wed, 12 Sep 2001 11:57:27 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Can't get Accton EN1207 to work in 100MBit On Wed, 12 Sep 2001, Marcus Blomenkamp wrote: > Am Mittwoch, 12. September 2001 16:30 schrieb Donald Becker: > > Did you do a google search? > > Yepp, lots of results pointing to this mailing list. groups.google.com also > showed mainly problems not solutions :-(. I thought, perhaps someone recalled > a very simple solution or nogo-situation. Keep in mind that very few people post follow-ups after a problem is fixed. They almost always post repeat messages if the problem isn't fixed. This board did work with the Tulip driver. > > What driver version are you trying to use? > > What is the detection message? > Oh, I forgot. > Kernels 2.4.7 + 2.4.9 > dmesg shows (after loading with options=4): > Linux Tulip driver version 0.9.15-pre6 (July 2, 2001) You should send a bug report to Jeff Garzik. Does the board work with the v0.92 driver series? > tulip0: Transceiver selection forced to 10baseT-FDX. > tulip0: Old format EEPROM on 'Accton EN1207' board. Using substitute > media control info. I had to write a media table for the board, since it doesn't have one in the EEPROM. > tulip0: EEPROM default media type Autosense. > tulip0: Index #0 - Media 10base2 (#1) described by a 21140 non-MII (0) block. > tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block. > tulip0: Index #2 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) > block. > tulip0: Index #3 - Media 100baseTx (#3) described by a 21140 non-MII > (0) block. > tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) > block. > eth0: Digital DS21140 Tulip rev 17 at 0xe800, 00:00:E8:15:DA:BA, IRQ 12. > eth0: Using user-specified media 10baseT-FDX. I'm guessing that you are currently forcing the media type. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From MBlomenkamp@t-online.de Wed, 12 Sep 2001 18:39:28 +0200 Date: Wed, 12 Sep 2001 18:39:28 +0200 From: Marcus Blomenkamp MBlomenkamp@t-online.de Subject: [tulip] Can't get Accton EN1207 to work in 100MBit Am Mittwoch, 12. September 2001 17:57 schrieb Donald Becker: > Does the board work with the v0.92 driver series? Don't know - cant' load the module because 'depmod -ae' shows: [root@zwiebel net]# depmod -ae depmod: *** Unresolved symbols in /lib/modules/2.4.9/kernel/drivers/net/pci-scan.o depmod: apm_register_callback depmod: apm_unregister_callback i have apm support in my kernel (no module), but I cannot find the string 'apm_register_callback' in the source (*.c + *.h) of 2.4.9 :-( From becker@scyld.com Wed, 12 Sep 2001 13:59:25 -0400 (EDT) Date: Wed, 12 Sep 2001 13:59:25 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Can't get Accton EN1207 to work in 100MBit On Wed, 12 Sep 2001, Marcus Blomenkamp wrote: > Date: Wed, 12 Sep 2001 18:39:28 +0200 > From: Marcus Blomenkamp > To: Donald Becker > Cc: tulip@scyld.com > Subject: Re: [tulip] Can't get Accton EN1207 to work in 100MBit > > Am Mittwoch, 12. September 2001 17:57 schrieb Donald Becker: > > Does the board work with the v0.92 driver series? > > Don't know - cant' load the module because 'depmod -ae' shows: > > [root@zwiebel net]# depmod -ae > depmod: *** Unresolved symbols in > /lib/modules/2.4.9/kernel/drivers/net/pci-scan.o > depmod: apm_register_callback > depmod: apm_unregister_callback > > i have apm support in my kernel (no module), but I cannot find the string > 'apm_register_callback' in the source (*.c + *.h) of 2.4.9 :-( Replace all occurences of #if defined(CONFIG_APM) and #ifdef CONFIG_APM with #if defined(CONFIG_APM) && LINUX_VERSION_CODE < 0x20400 The power management interface changed in 2.4, but continued to use the same CONFIG_APM flag. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From MBlomenkamp@t-online.de Wed, 12 Sep 2001 18:13:02 +0200 Date: Wed, 12 Sep 2001 18:13:02 +0200 From: Marcus Blomenkamp MBlomenkamp@t-online.de Subject: [tulip] Can't get Accton EN1207 to work in 100MBit Am Mittwoch, 12. September 2001 17:57 schrieb Donald Becker: > You should send a bug report to Jeff Garzik. I'll keep that in mind. > Does the board work with the v0.92 driver series? Gonna try now. > I'm guessing that you are currently forcing the media type. Yes, i know it's unnecessary for this link because autoselection between Coax and 10M-TP works fine. That exactly the contra situation compared to other people. They have problems getting Coax to work. It's just a leftover from my module parameter testing. I suddenly had 100baseTx working for 10 minutes and then it vanished without any sign. Marcus From MBlomenkamp@t-online.de Thu, 13 Sep 2001 13:27:50 +0200 Date: Thu, 13 Sep 2001 13:27:50 +0200 From: Marcus Blomenkamp MBlomenkamp@t-online.de Subject: [tulip] Can't get Accton EN1207 to work in 100MBit Hi. Situation cleared up. Card was defect. Grrmpf. Marcus From mill@pedgr571.sn.umu.se Thu, 13 Sep 2001 13:34:42 +0200 Date: Thu, 13 Sep 2001 13:34:42 +0200 From: Olof Oberg mill@pedgr571.sn.umu.se Subject: [tulip] Cpq Presario problems Hi, I have been having problems getting the builtin NIC on my Compaq Presario to work properly since I got it (June), but the last week has been unbearable with network downtime several times a day. Currently used kernel that came with the distribution: Linux version 2.2.18 (root@fritz) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #1 Tue Feb 27 10:33:03 EST 2001 ... tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov eth0: Digital DS21143 Tulip rev 65 at 0x1400, 00:08:C7:63:8E:D8, IRQ 11. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block. eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block. The kernel starts spewing: eth0: Tx hung, 2163 vs. 2162. eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fff8ffff 8ff40000, resetting... eth0: transmit timed out, switching to 10baseT-FD media. eth0: Tx hung, 2174 vs. 2162. eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 fff8ffff 8ff40000, resetting... eth0: transmit timed out, switching to 10baseT-FD media. ... I have tried kernel 2.2.18, 2.2.19, 2.4.8, and 2.4.9 with the tulip driver from 2.4.4 (saw it mentioned somewhere that it might work better). I have put up the output from dmesg and tulip-diag at http://www.ludd.luth.se/~mill/tulip/ for the last week or so. This is what tulip-diag -aa -ee -mm -f said this last time: tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Digital DS21143 Tulip adapter at 0x1400. Digital DS21143 Tulip chip registers at 0x1400: 0x00: f8a08000 ffffffff ffffffff 0009d810 0009da10 f0260000 b3862002 fbfffbff 0x40: e0000000 fff583ff ffffffff 00000000 000000c6 ffff0000 fffbff7f 8ff50008 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 'Waiting for Tx to finish'. The transmit threshold is 128. The NWay status register is 000000c6. EEPROM 64 words, 6 address bits. PCI Subsystem IDs, vendor 0e11, device b0bb. CardBus Information Structure at offset 00000000. Ethernet MAC Station Address 00:08:C7:63:8E:D8. EEPROM transceiver/media description table. Leaf node at offset 30, default media type 0800 (Autosense). 2 transceiver description blocks: Media 10baseT, block type 2, length 6. Serial transceiver for 10baseT (media type 0). GP pin direction 08e1 GP pin data 0000. Media 10baseT-Full Duplex, block type 2, length 6. Serial transceiver for 10baseT-Full Duplex (media type 4). GP pin direction 08e1 GP pin data 0000. EEPROM contents (64 words): 0x00: 0e11 b0bb 0000 0000 0000 0000 0000 0000 0x08: 183f 0104 0800 63c7 d88e 1e00 0000 0800 0x10: 8602 0002 08e1 0000 0286 e104 0008 0000 0x18: 0000 0000 0000 0000 0000 0000 0000 0000 0x20: 0000 0000 0000 0000 0000 0000 0000 0000 0x28: 0000 0000 0000 0000 0000 0000 0000 0000 0x30: 0000 0000 0000 0000 0000 0000 0000 0000 0x38: 0000 0000 0000 0000 0000 0000 0000 ce45 ID block CRC 0x3f (vs. 0x3f). Full contents CRC 0xce45 (read as 0xce45). No MII transceivers found! Internal autonegotiation state is 'Autonegotiation disabled'. I have tried to unload-load the module, but after that the network is unreachable so I always have to reboot. Any help would be greatly appreciated. I have tried to use my D-Link DFE-530TX and 3COM 509, but neither is detected (the 3COM has served me since '95 in my old box). /mill -- ############################################################# # S-mail: Olof Oberg # mill@pedgr571.sn.umu.se # # Pedagoggr. 7A # mill@ludd.luth.se # # S-907 30 Umea # tdv94oog@cs.umu.se # # Phone: 090-197395 # http://pedgr571.sn.umu.se/~mill # ############################################################# From grim@undead.dhs.org Sat, 15 Sep 2001 23:23:25 -0400 Date: Sat, 15 Sep 2001 23:23:25 -0400 From: John Zielinski grim@undead.dhs.org Subject: [tulip] 21041 card broken I have a 21041 card made by Linksys which has a 10BT and 10B2 connectors on it. I upgraded my kernel from 2.4.3 to 2.4.9 and the card stopped working. The link light is on but it won't send or receive anything. I've tracked down the problem to kernel version 2.4.5. Everything works fine with 2.4.4 and earlier. Please let me know what other information you require. John From w006552@airmail.net 15 Sep 2001 23:48:45 -0500 Date: 15 Sep 2001 23:48:45 -0500 From: Brian Rogers w006552@airmail.net Subject: [tulip] Where can I get 21145 docs? I'm trying to help someone get their eOne built-in NIC working. It's a 21145-based NIC and I can no longer find the 21145 reference manual on Intel's site. It used to be available in PDF form at http://www.intel.com/design/network/manuals/ but they have changed their site and seem to have removed the 21145 documents. -- /* Brian Rogers, professional geek, coffee achiever */ From w006552@airmail.net 16 Sep 2001 02:25:34 -0500 Date: 16 Sep 2001 02:25:34 -0500 From: Brian Rogers w006552@airmail.net Subject: [tulip] Re: Where can I get 21145 docs? The file name is 28721101.pdf The title is "Intel(r) 21145 Phoneline/Ethernet LAN Controller Hardware Reference Manual". Last known URL: http://developer.intel.com/design/network/manuals/278211.htm Surprisingly, Google does not have a cached text version of this PDF. On Sat, 2001-09-15 at 23:48, Brian Rogers wrote: > I'm trying to help someone get their eOne built-in NIC working. It's a > 21145-based NIC and I can no longer find the 21145 reference manual on > Intel's site. It used to be available in PDF form at > http://www.intel.com/design/network/manuals/ but they have changed their > site and seem to have removed the 21145 documents. > -- /* Brian Rogers, professional geek, coffee achiever */ From al447923@mail.mty.itesm.mx Sun, 16 Sep 2001 12:05:06 -0500 Date: Sun, 16 Sep 2001 12:05:06 -0500 From: Jaime G. Almeida H. al447923@mail.mty.itesm.mx Subject: [tulip] Any luck using tulip with Conexant Combo 10/100 NIC/MODEM(Compaq Labtop) This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C13EA7.D2E88980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Has anybody had any luck bringing up the ethernet with tulip using a = Conexant Combo 10/100 NIC/Modem, usually installed on Compaq Laptops??? ------=_NextPart_000_0007_01C13EA7.D2E88980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Has anybody had any luck bringing up = the ethernet=20 with tulip using a Conexant Combo 10/100 NIC/Modem, usually installed on = Compaq=20 Laptops???
     
     
     
    ------=_NextPart_000_0007_01C13EA7.D2E88980-- From kenthunt@yahoo.com Mon, 17 Sep 2001 15:32:41 -0700 (PDT) Date: Mon, 17 Sep 2001 15:32:41 -0700 (PDT) From: Kent Hunt kenthunt@yahoo.com Subject: [tulip] Any luck using tulip with Conexant Combo 10/100 NIC/MODEM(Compaq Labtop) Yes. Read the mailing list and look for the LANfinity, Conexant keywords in the past two months or so. --- "Jaime G. Almeida H." wrote: > Has anybody had any luck bringing up the ethernet > with tulip using a Conexant Combo 10/100 NIC/Modem, > usually installed on Compaq Laptops??? > > > > __________________________________________________ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/ From jonni@gmx.co.uk Tue, 18 Sep 2001 21:40:52 +0200 (MEST) Date: Tue, 18 Sep 2001 21:40:52 +0200 (MEST) From: john wa jonni@gmx.co.uk Subject: [tulip] 2 KNE111TX cards don't work well together i've had some problems when using two identical cards together. i think maybe my problems may be my lack of skillz so any suggestions would be great. i had these two cards in an old p200 machine, working as a external cable link and my internal network. when i moved these to a new motherboard to work off a pii400 my problems started. i moved the hdd too and changed nothing, not even the (monolithic) kernel. on booting, my eth0 couldn't sort out the dhcp request. it tried but failed. eth1 came up as intended and my switch reckoned it was at 100baseTFD. i tried many things to get the DHCP working but failed. i could bring up the interface if i specified an IP address - there only seemed to be a problem with the DHCP stuff - which is done with PUMP, dhcp-client failed too :( then i pulled out one of the cards and replaced it with an SMC card which uses the 8139too driver. on first boot, eth0 (still a kne111 card) successfully got a DHCP lease and my SMC card came up on the internal network. again, i changed absolutely nothing on the hdd or any other settings. dhcp-client now works too. the cable modem on eth0 runs at 10baseT half duplex. i'm using a 2.4.6 kernel. thanks jw -- Sent through GMX FreeMail - http://www.gmx.net From spencerborland@hotmail.com Tue, 18 Sep 2001 19:56:33 -0400 Date: Tue, 18 Sep 2001 19:56:33 -0400 From: Spencer Borland spencerborland@hotmail.com Subject: [tulip] tulip compilation Hi, I'm having trouble compiling the tulip.c file for my linksys fast ethernet card. I'm compiling by doing the following: gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c tulip.c and get the following errors: In file included from /usr/include/linux/posix_types.h: 46, from /usr/include/linux/types.h: 4, from /usr/include/linux/string.h: 4, from tulip.c: 144: /usr/lib/gcc-lib/i586-pc-linux/2.95.2/include/asm/posix_types.h: 3: features.h: No such file or directory gcc: Compilation of header file requested I try commenting out the line in posix_types.h that includes features.h but gcc still complains "gcc: Compilation of header file requested" I tried searching for this features.h include file but couldn't find it. If anyone has any insight I would be very grateful. I'm running PowerLinux Server Site V6 Kernel version 2.2.14-3 gcc version 2.95.2 Thank you for your time! From becker@scyld.com Thu, 20 Sep 2001 17:11:28 -0400 (EDT) Date: Thu, 20 Sep 2001 17:11:28 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] Sorry about the new spam. There has been a major increase in the amount of spam and unrelated mail aimed at the scyld.com lists. We have kept most of it out, but some will occasionally slip through. Please keep in mind that some bogus mail will always get through on an unmoderated list. >Date: Wed, 20 Dec 2000 15:33:05 -0400 >From: "[ISO-8859-1] Gonzalo J. Camponovo H." >To: tulip@scyld.com >Subject: [tulip] bavaro ing camponovo FINAL > >------------------ Virus Warning Message (on webmail.cotas.com.bo) > >Found virus TROJ_SIRCAM.A in file bavaro ing camponovo FINAL.doc.lnk >The file is deleted. Darn... if only the source host hadn't filtered out the Sircam virus, we would have held the post for excessive length. The length restriction catches most Windows-oriented malicious mail. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From keith@jollygreen.com Thu, 20 Sep 2001 14:55:58 -0700 Date: Thu, 20 Sep 2001 14:55:58 -0700 From: Keith Anderson keith@jollygreen.com Subject: [tulip] ng_tulip driver Hello, I own a Netgear FA310TX rev D2 10/100 NIC and am currently having trouble getting any linux drivers to recognize the thing. I had it installed in a Red Hat (recent, not sure version) system with no problems, so I know the card WILL work. However, upon removing the card and trying to install it into a Debian (2.2r3 - potato) system I've been unable to find ANY driver combination that will make this card work - including the ng_tulip.o driver that came with the distribution (modified by Netgear!). Upon module load of ng_tulip.o, I get: --insmod ng_tulip debug=6-------- tulip.c:v0.89K.1 3/16/99 Originally written by becker@cesdis.gsfc.nasa.gov Driver modified by Netgear for FA310TX Netgear technical support: support@netgear.matrixx.net eth0: NETGEAR NGMC169 MAC at 0xfc00, 00 a0 cc d9 67 63, IRQ 10 eth0: Checking for MII transceivers... ---------- When I try to bring up the interface: --ifup eth0------- eth0: tulip_open() irq 10. eth0: NGMC169 PHY status is 201e078, CSR12 0020 media 10baseT. eth0: Done tulip_open(), CSR0 00004800, CSR5 02261000 CSR6 0122002. eth0: NGMC169 phy status 0201a078, CSR5 02261000. eth0: 10baseT link beat failed, CSR12 0030, CSR5 02261000, PHY 201a078. eth0: Changing NGMC169 configuration to half-duplix, CSR6 01860000. eth0: interrupt csr5=0x02671004 new csr5=0x02661000. eth0: interrupt csr5=0x02661000 new csr5=0x02661000. eth0: exiting interrupt, csr5=0x2661000 ---------- It'll then try with 100baseT and do the same thing, looping back and forth trying to find a link beat. Thing is, none of my other machines on this network have trouble finding link beat (running through CenterCOM 10/100 switch). I've tried a myriad of driver / version combinations to make this work - but I wonder about the lack of MII status reporting. According to all the mailing list info I've found thus far, the card (usually - apparently there are a WHOLE bunch of different cards all under the FA310 guise) should respond back with something along the lines of: eth0: MII transceiver found at MDIO address 1, config 0000 status 782d. And most of the troubleshooting info I can find for that driver/card have to do with the MII status and configuration. If it's not finding MII, then is my card just dead? Could I have been banging my head away at a coincidental problem? Jeez... Here's the system breakdown: debian 2.2r3 - FRESH from CD (kernel 2.2.19pre17) Pentium 100 - 64MB ======================================================== == GIANT Network Productions == == web hosting + web design + consulting == ======================================================== ++ 541 . 684 . 9798 http://www.jollygreen.com/ ++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From becker@scyld.com Fri, 21 Sep 2001 01:45:34 -0400 (EDT) Date: Fri, 21 Sep 2001 01:45:34 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] ng_tulip driver On Thu, 20 Sep 2001, Keith Anderson wrote: > I own a Netgear FA310TX rev D2 10/100 NIC and am currently having > trouble getting any linux drivers to recognize the thing. I had it > installed in a Red Hat (recent, not sure version) system with no > problems, so I know the card WILL work. However, upon removing the > card and trying to install it into a Debian (2.2r3 - potato) system > I've been unable to find ANY driver combination that will make this > card work - including the ng_tulip.o driver that came with the > distribution (modified by Netgear!). What driver versions have you tried? What does 'tulip-diag -aefm' report? Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From dkt@digitalme.com Sat, 22 Sep 2001 11:22:33 GMT Date: Sat, 22 Sep 2001 11:22:33 GMT From: Dung Patrick dkt@digitalme.com Subject: [tulip] geniue 21143 and tulip clones actually which one is better? From sanmukhe@onebox.com Sun, 23 Sep 2001 00:22:32 -0700 Date: Sun, 23 Sep 2001 00:22:32 -0700 From: Sandeep Mukherjee sanmukhe@onebox.com Subject: [tulip] Getting FFFFFFFF for CSR0 Hi, Trying to write a driver for ADMtek's AN983. Trying to read CSR0, as well as all other CSR's simply return value FFFFFFFF. Wonder what I am doing wrong. Sandeep __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com From art1@alloymail.com Sat, 22 Sep 2001 20:06:57 Date: Sat, 22 Sep 2001 20:06:57 From: art1@alloymail.com art1@alloymail.com Subject: [tulip] printer supplies **** VORTEX SUPPLIES **** YOUR LASER PRINTER TONER CARTRIDGE, COPIER AND FAX CARTRIDGE CONNECTION SAVE UP TO 30% FROM RETAIL ORDER BY PHONE:1-888-288-9043 ORDER BY FAX: 1-888-977-1577 E-MAIL REMOVAL LINE: 1-888-494-8597 UNIVERSITY AND/OR SCHOOL PURCHASE ORDERS WELCOME. (NO CREDIT APPROVAL REQUIRED) ALL OTHER PURCHASE ORDER REQUESTS REQUIRE CREDIT APPROVAL. PAY BY CHECK (C.O.D), CREDIT CARD OR PURCHASE ORDER (NET 30 DAYS). IF YOUR ORDER IS BY CREDIT CARD PLEASE LEAVE YOUR CREDIT CARD # PLUS EXPIRATION DATE. IF YOUR ORDER IS BY PURCHASE ORDER LEAVE YOUR SHIPPING/BILLING ADDRESSES AND YOUR P.O. NUMBER NOTE: WE DO NOT CARRY 1) XEROX, BROTHER, PANASONIC, FUJITSU PRODUCTS 2) HP DESKJETJET/INK JET OR BUBBLE JET CARTRIDGES 3) CANON BUBBLE JET CARTRIDGES 4) ANY OFFBRANDS BESIDES THE ONES LISTED BELOW. OUR NEW , LASER PRINTER TONER CARTRIDGE, PRICES ARE AS FOLLOWS: (PLEASE ORDER BY PAGE NUMBER AND/OR ITEM NUMBER) HEWLETT PACKARD: (ON PAGE 2) ITEM #1 LASERJET SERIES 4L,4P (74A)------------------------$44 ITEM #2 LASERJET SERIES 1100 (92A)-------------------------$44 ITEM #3 LASERJET SERIES 2 (95A)----------------------------$39 ITEM #4 LASERJET SERIES 2P (75A)---------------------------$54 ITEM #5 LASERJET SERIES 5P,6P,5MP, 6MP (3903A)---------- -$44 ITEM #6 LASERJET SERIES 5SI, 8000 (09A)--------------------$95 ITEM #7 LASERJET SERIES 2100, 2200 (96A)-------------------$74 ITEM #8 LASERJET SERIES 8100 (82X)-------------------------$115 ITEM #9 LASERJET SERIES 5L/6L (3906A)----------------------$39 ITEM #10 LASERJET SERIES 4V---------------------------------$95 ITEM #11 LASERJET SERIES 4000 (27X)--------------------------$79 ITEM #12 LASERJET SERIES 3SI/4SI (91A)-----------------------$54 ITEM #13 LASERJET SERIES 4, 4M, 5,5M-------------------------$49 ITEM #13A LASERJET SERIES 5000 (29X)-------------------------$125 ITEM #13B LASERJET SERIES 1200-------------------------------$59 HEWLETT PACKARD FAX (ON PAGE 2) ITEM #14 LASERFAX 500, 700 (FX1)----------$49 ITEM #15 LASERFAX 5000,7000 (FX2)--------$64 ITEM #16 LASERFAX (FX3)------------------$59 ITEM #17 LASERFAX (FX4)------------------$54 LEXMARK/IBM (ON PAGE 3) OPTRA 4019, 4029 HIGH YIELD---------------$89 OPTRA R, 4039, 4049 HIGH YIELD-----------$105 OPTRA E310.312 HIGH YIELD----------------$79 OPTRA E-----------------------------------$59 OPTRA N----------------------------------$115 OPTRA S----------------------------------$165 OPTRA T----------------------------------$195 EPSON (ON PAGE 4) ACTION LASER 7000,7500,8000,9000----------$105 ACTION LASER 1000,1500--------------------$105 CANON PRINTERS (ON PAGE 5) PLEASE CALL FOR MODELS AND UPDATED PRICES FOR CANON PRINTER CARTRIDGES PANASONIC (0N PAGE 7) NEC SERIES 2 MODELS 90 AND 95----------$105 APPLE (0N PAGE 8) LASER WRITER PRO 600 or 16/600------------------$49 LASER WRITER SELECT 300,320,360-----------------$74 LASER WRITER 300 AND 320------------------------$54 LASER WRITER NT, 2NT----------------------------$54 LASER WRITER 12/640-----------------------------$79 CANON FAX (ON PAGE 9) LASERCLASS 4000 (FX3)---------------------------$59 LASERCLASS 5000,6000,7000 (FX2)-----------------$54 LASERFAX 5000,7000 (FX2)------------------------$54 LASERFAX 8500,9000 (FX4)------------------------$54 CANON COPIERS (PAGE 10) PC 3, 6RE, 7 AND 11 (A30)---------------------$69 PC 300,320,700,720,760,900,910,920(E-40)------$89 90 DAY UNLIMITED WARRANTY INCLUDED ON ALL PRODUCTS. ALL TRADEMARKS AND BRAND NAMES LISTED ABOVE ARE PROPERTY OF THE RESPECTIVE HOLDERS AND USED FOR DESCRIPTIVE PURPOSES ONLY. From Ian.Marsh@northerngateway.ab.ca Tue, 25 Sep 2001 12:24:47 -0600 Date: Tue, 25 Sep 2001 12:24:47 -0600 From: Ian Marsh Ian.Marsh@northerngateway.ab.ca Subject: [tulip] DFE-570TX & Mandrake I've been trying to setup a 4-port DLink DFE-570TX with Mandrake Linux 8.0 (that's what I had kicking around). I've tried using every version of tulip for 0.92 to 1.1.8, but nothing seems to work. The card seems to configure properly, and each interface can ping itself, but nothing works past that. The interface cannot ping anything on the network, or be pinged. Running ifconfig shows all RX packets as dropped, and no TX packets at all. If I run tulip-diag, is says: Index #1: Found a Digital DS21143 Tulip adapter at 0xb000. Port selection is MII, half-duplex. The RX process state is 'Suspended -- no RX buffers'. The TX process state is 'Idle'. The transmit threshold is 128. Interrupt sources are pending! CSR5 is f06980c4. Tx out of buffers indication. Rx Done indication. Receiver out of buffers indication. The NWay status register is 000000c6. Internal autonegotiation state is 'Autonegatiation disabled'. Also, if I bring up a second eth(x) interface, the whole system stops responding. If anyone could shed some light on how to solve this, it would be greatly appreciated! Thanks, Ian Marsh Technical Assistant Onoway High School From greearb@candelatech.com Tue, 25 Sep 2001 12:51:20 -0700 Date: Tue, 25 Sep 2001 12:51:20 -0700 From: Ben Greear greearb@candelatech.com Subject: [tulip] DFE-570TX & Mandrake The kernel driver was busted untill about 2.4.8. Try a kernel after that and I think you'll have better luck... Ben Ian Marsh wrote: > > I've been trying to setup a 4-port DLink DFE-570TX with Mandrake Linux 8.0 (that's what I had kicking around). > > I've tried using every version of tulip for 0.92 to 1.1.8, but nothing seems to work. The card seems to configure properly, and each interface can ping itself, but nothing works past that. The interface cannot ping anything on the network, or be pinged. Running ifconfig shows all RX packets as dropped, and no TX packets at all. > > If I run tulip-diag, is says: > > Index #1: Found a Digital DS21143 Tulip adapter at 0xb000. > Port selection is MII, half-duplex. > The RX process state is 'Suspended -- no RX buffers'. > The TX process state is 'Idle'. > The transmit threshold is 128. > Interrupt sources are pending! CSR5 is f06980c4. > Tx out of buffers indication. > Rx Done indication. > Receiver out of buffers indication. > The NWay status register is 000000c6. > Internal autonegotiation state is 'Autonegatiation disabled'. > > Also, if I bring up a second eth(x) interface, the whole system stops responding. > > If anyone could shed some light on how to solve this, it would be greatly appreciated! > > Thanks, > > Ian Marsh > Technical Assistant > Onoway High School > > _______________________________________________ > tulip mailing list, tulip@scyld.com > To change to digest mode or unsubscribe visit > http://www.scyld.com/mailman/listinfo/tulip -- Ben Greear President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear From becker@scyld.com Tue, 25 Sep 2001 23:43:51 -0400 (EDT) Date: Tue, 25 Sep 2001 23:43:51 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] DFE-570TX & Mandrake On Tue, 25 Sep 2001, Ian Marsh wrote: > I've been trying to setup a 4-port DLink DFE-570TX with Mandrake Linux > 8.0 (that's what I had kicking around). ... > Index #1: Found a Digital DS21143 Tulip adapter at 0xb000. > Port selection is MII, half-duplex. > The RX process state is 'Suspended -- no RX buffers'. > The TX process state is 'Idle'. > The transmit threshold is 128. > Interrupt sources are pending! CSR5 is f06980c4. You have an interrupt mapping problem. This is related to the motherboard, BIOS, kernel version and if you are using "noapic". > Also, if I bring up a second eth(x) interface, the whole system stops > responding. Yup, IRQ mapping problem. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From jorge_aparicio@sekureit.com Wed, 26 Sep 2001 12:53:17 -0500 Date: Wed, 26 Sep 2001 12:53:17 -0500 From: Jorge E. Aparicio M. jorge_aparicio@sekureit.com Subject: [tulip] Conexant Combo 10/100 NIC Modem, kernel 2.2.19 problems This is a multi-part message in MIME format. ------=_NextPart_000_0011_01C1468A.3658B960 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everybody, I have already read carefully all of the archived messages about = Conexant Combo and tulip drivers for Compaq Presario. =20 I have a Compaq Presario XL366, with a Conexant Combo 10/100 NIC Modem = running RH 6.2, kernel 2.2.19. I have installed all of the stuff, and it seems that there is no = problem, the NIC is identified, even answers local pings, but I can not = make any connection over the network. Jan Egil Magelie reported this = same problem before, and he solved by installing RH 7.1, kernel 2.4.x . = At this point I have already installed an configured several servers: = BIND, APACHE-SSL, QMAIL, POP... and everything works fine locally, but = the external connections. I would not like to reinstall everything = again!!! Here you will find the information I have gathered: >From dmesg: Linux version 2.2.19 (root@quijote) (gcc version egcs-2.91.66 = 19990314/Linux (egcs-1.1.2 release)) #2 Tue Sep 25 10:24:53 CDT 2001 BIOS-provided physical RAM map: BIOS-e820: 0009f000 @ 00000000 (usable) BIOS-e820: 03ef0000 @ 00100000 (usable) ... PCI: PCI BIOS revision 2.10 entry at 0xfd9af 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 65536 bhash 65536) Initializing RT netlink socket ... apm: BIOS not found. .... VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 68k freed Adding Swap: 136072k swap-space (priority -1) maestro3: version 0.51 built at 10:34:32 Sep 25 2001 PCI: Enabling bus mastering for device 00:50 maestro3: Configuring Allegro found at IO 0x1800 IRQ 5 maestro3: subvendor id: 0x002e0e11 ac97_codec: AC97 Audio codec, vendor id1: 0x4583, id2: 0x8308 (Unknown) maestro3: 1 channels configured. maestro3: 1 maestros installed. tulip.c:v0.92w 7/9/2001 Written by Donald Becker http://www.scyld.com/network/tulip.html The PCI BIOS has not enabled the device at 0/72! Updating PCI command = 0003->0007. eth0: Conexant LANfinity rev 8 at 0xc4034000, 00:50:8B:AA:FA:F9, IRQ 9. eth0: Transceiver selection forced to 100baseTx. eth0: MII transceiver #1 config 1000 status 782d advertising 01e1. eth0: MII transceiver #0 config 2000 status 780d advertising 01e1. >From messages log: Sep 26 12:12:24 quijote kernel: tulip.c:v0.92w 7/9/2001 Written by = Donald Becker =20 Sep 26 12:12:24 quijote kernel: = http://www.scyld.com/network/tulip.html=20 Sep 26 12:12:24 quijote kernel: The PCI BIOS has not enabled the = device at 0/72! Updating PCI command 0003->0007.=20 Sep 26 12:12:24 quijote kernel: eth0: Conexant LANfinity rev 8 at = 0xc4034000, 00:50:8B:AA:FA:F9, IRQ 9.=20 Sep 26 12:12:24 quijote kernel: eth0: Transceiver selection forced to = 100baseTx.=20 Sep 26 12:12:24 quijote kernel: eth0: MII transceiver #1 config 1000 = status 782d advertising 01e1.=20 Sep 26 12:12:24 quijote kernel: eth0: MII transceiver #0 config 2000 = status 780d advertising 01e1.=20 >From tulip-diag -aemf (I had to use -p parameter because the adapter was = active) tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Conexant LANfinity adapter at 0x1400. Conexant LANfinity chip registers at 0x1400: 0x00: fff88000 ffffffff ffffffff 03db9000 03db9200 f4660000 f8e02002 = 7bffebef 0x40: fffe0000 fffc80e8 fffe0000 fffe0000 ffffffff ffffffff ffffffff = f7f9fec8 Extended registers: 80: cc660000 cbffebef f0000018 020400ef ffffffff 03db9270 03db9010 = 00000000 a0: ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 = 00000000 c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 = 00000000 e0: 00000000 00000000 00000000 00000000 ffffffff 00000000 00000000 = 00000000 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 unit is set to store-and-forward. EEPROM 256 words, 8 address bits. Conexant EEPROM format is undocumented. MII PHY found at address 1, status 0x780d. MII PHY found at address 0, status 0x780d. MII PHY #1 transceiver registers: 2000 780d 0022 1720 01e1 0000 0005 2001 2000 780d 0022 1720 01e1 0000 0005 2001 2000 780d 0022 1720 01e1 0000 0005 2001 0000 0000 0000 0029 01e1 2001 0000 8c08. MII PHY #0 transceiver registers: 2000 780d 0022 1720 01e1 0000 0005 2001 2000 780d 0022 1720 01e1 0000 0005 2001 2000 780d 0022 1720 01e1 0000 0005 2001 0000 0000 0000 0000 01e1 2001 0000 8c08. I would really appreciatte any suggestion... Best Regards, Jorge Aparicio ------=_NextPart_000_0011_01C1468A.3658B960 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi everybody,
     
    I have already read carefully all of = the archived=20 messages about Conexant Combo and tulip drivers for Compaq = Presario. =20
     
    I have a Compaq Presario XL366, with a = Conexant=20 Combo 10/100 NIC Modem running RH 6.2, kernel 2.2.19.
     
    I have installed all of the stuff, and = it seems=20 that there is no problem, the NIC is identified, even answers local = pings, but I=20 can not make any connection over the network.  Jan Egil Magelie = reported=20 this same problem before, and he solved by installing RH 7.1, kernel=20 2.4.x . 
     
    At this point I have already installed = an=20 configured several servers: BIND, APACHE-SSL, QMAIL, POP... and = everything works=20 fine locally, but the external connections.  I would not like to = reinstall=20 everything again!!!
     
    Here you will find the information I = have=20 gathered:
     
    From dmesg:
     
    Linux version 2.2.19 (root@quijote) (gcc version egcs-2.91.66 = 19990314/Linux (egcs-1.1.2 release)) #2 Tue Sep 25 10:24:53 CDT=20 2001
    BIOS-provided physical RAM map:
     BIOS-e820: 0009f000 @ = 00000000=20 (usable)
     BIOS-e820: 03ef0000 @ 00100000 = (usable)
    ...
    PCI: PCI BIOS revision 2.10 entry at=20 0xfd9af
    PCI: Using configuration type 1
    PCI: Probing PCI = hardware
    Linux=20 NET4.0 for Linux 2.2
    Based upon Swansea University Computer Society=20 NET3.039
    NET4: Unix domain sockets 1.0 for Linux NET4.0.
    NET4: = Linux=20 TCP/IP 1.0 for NET4.0
    IP Protocols: ICMP, UDP, TCP, IGMP
    TCP: Hash = tables=20 configured (ehash 65536 bhash 65536)
    Initializing RT netlink=20 socket
    ...
    apm: BIOS not = found.
    ....
     
    VFS: Mounted root (ext2 filesystem)=20 readonly.
    Freeing unused kernel memory: 68k freed
    Adding Swap: = 136072k=20 swap-space (priority -1)
    maestro3: version 0.51 built at 10:34:32 Sep = 25=20 2001
    PCI: Enabling bus mastering for device 00:50
    maestro3: = Configuring=20 Allegro found at IO 0x1800 IRQ 5
    maestro3:  subvendor id:=20 0x002e0e11
    ac97_codec: AC97 Audio codec, vendor id1: 0x4583, id2: = 0x8308=20 (Unknown)
    maestro3: 1 channels configured.
    maestro3: 1 maestros=20 installed.
    tulip.c:v0.92w 7/9/2001  Written by Donald Becker = <becker@scyld.com>
      http://www.scyld.com/net= work/tulip.html
     =20 The PCI BIOS has not enabled the device at 0/72!  Updating PCI = command=20 0003->0007.
    eth0: Conexant LANfinity rev 8 at 0xc4034000,=20 00:50:8B:AA:FA:F9, IRQ 9.
    eth0: Transceiver selection forced to=20 100baseTx.
    eth0:  MII transceiver #1 config 1000 status 782d = advertising=20 01e1.
    eth0:  MII transceiver #0 config 2000 status 780d = advertising=20 01e1.
     
    From messages log:
     
    Sep 26 12:12:24 quijote kernel: = tulip.c:v0.92w=20 7/9/2001  Written by Donald Becker <becker@scyld.com>
    Sep 26 = 12:12:24=20 quijote kernel:   http://www.scyld.com/net= work/tulip.html=20
    Sep 26 12:12:24 quijote kernel:   The PCI BIOS has not = enabled the=20 device at 0/72!  Updating PCI command 0003->0007.
    Sep 26 = 12:12:24=20 quijote kernel: eth0: Conexant LANfinity rev 8 at 0xc4034000, = 00:50:8B:AA:FA:F9,=20 IRQ 9.
    Sep 26 12:12:24 quijote kernel: eth0: Transceiver selection = forced to=20 100baseTx.
    Sep 26 12:12:24 quijote kernel: eth0:  MII = transceiver #1=20 config 1000 status 782d advertising 01e1.
    Sep 26 12:12:24 quijote = kernel:=20 eth0:  MII transceiver #0 config 2000 status 780d advertising 01e1. =
     
    From tulip-diag -aemf (I had to use -p = parameter=20 because the adapter was active)
     
    tulip-diag.c:v2.08 5/15/2001 Donald = Becker (becker@scyld.com)
     http://www.scyld.com/diag/i= ndex.html
    Index=20 #1: Found a Conexant LANfinity adapter at 0x1400.
    Conexant LANfinity = chip=20 registers at 0x1400:
     0x00: fff88000 ffffffff ffffffff 03db9000 = 03db9200=20 f4660000 f8e02002 7bffebef
     0x40: fffe0000 fffc80e8 fffe0000 = fffe0000=20 ffffffff ffffffff ffffffff f7f9fec8
     Extended = registers:
     80:=20 cc660000 cbffebef f0000018 020400ef ffffffff 03db9270 03db9010=20 00000000
     a0: ffffffff 00000000 00000000 00000000 00000000 = 00000000=20 00000000 00000000
     c0: 00000000 00000000 00000000 00000000 = 00000000=20 00000000 00000000 00000000
     e0: 00000000 00000000 00000000 = 00000000=20 ffffffff 00000000 00000000 00000000
     Port selection is = 10mpbs-serial,=20 half-duplex.
     Transmit started, Receive started, = half-duplex.
     =20 The Rx process state is 'Waiting for packets'.
      The Tx process = state is=20 'Idle'.
      The transmit unit is set to = store-and-forward.
    EEPROM 256=20 words, 8 address bits.
    Conexant EEPROM format is = undocumented.
     MII=20 PHY found at address 1, status 0x780d.
     MII PHY found at address = 0,=20 status 0x780d.
     MII PHY #1 transceiver = registers:
       2000=20 780d 0022 1720 01e1 0000 0005 2001
       2000 780d 0022 1720 = 01e1 0000=20 0005 2001
       2000 780d 0022 1720 01e1 0000 0005=20 2001
       0000 0000 0000 0029 01e1 2001 0000 = 8c08.
     MII PHY=20 #0 transceiver registers:
       2000 780d 0022 1720 01e1 0000 = 0005=20 2001
       2000 780d 0022 1720 01e1 0000 0005 = 2001
      =20 2000 780d 0022 1720 01e1 0000 0005 2001
       0000 0000 0000 = 0000 01e1=20 2001 0000 8c08.
     
    I would really appreciatte any=20 suggestion...
     
    Best Regards,
     
    Jorge = Aparicio
    ------=_NextPart_000_0011_01C1468A.3658B960-- From gnp@jollygreen.com Wed, 26 Sep 2001 14:02:22 -0700 Date: Wed, 26 Sep 2001 14:02:22 -0700 From: GIANT Network Productions gnp@jollygreen.com Subject: [tulip] ng_tulip driver >On Thu, 20 Sep 2001, Keith Anderson wrote: > > > I own a Netgear FA310TX rev D2 10/100 NIC and am currently having > > trouble getting any linux drivers to recognize the thing. I had it > > installed in a Red Hat (recent, not sure version) system with no > > problems, so I know the card WILL work. However, upon removing the > > card and trying to install it into a Debian (2.2r3 - potato) system > > I've been unable to find ANY driver combination that will make this > > card work - including the ng_tulip.o driver that came with the > > distribution (modified by Netgear!). > >What driver versions have you tried? ng_tulip - 0.89K.1 tulip - 0.91g-ppc old_tulip - 0.89H >What does 'tulip-diag -aefm' report? #tulip-diag -aefm tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Lite-On 82c168 PNIC adapter at 0xfc00 Lite-On 82c168 PNIC chip registers at 0xfc00: 0x00: 00004800 01ff0000 55555555 00dce810 00dcea10 02201100 01420000 00000000 0x40: 00000000 00006763 00dceac0 00dceac0 00000030 00000000 00000000 00000000 Extended registers: 80: 00000000 00000000 f0000000 f0000000 f0041385 f0041385 00000082 00000082 a0: 6f860000 6f860000 00dce810 00dce810 02866810 02866810 0201e078 0201e078 c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Port selection is 10mpbs-serial, half-duplex. Transmit stopped, Recieve stopped, half-duplex. The Rx process state is 'Stopped'. The Tx process state is 'Waiting for Tx to finish'. The transmit threshold is 72. A simplified EEPROM data table was found. The EEPROM does not contain transceiver control information. No MII transceivers found! The troubling bit is the lack of MII transceiver - I don't know if this is normal (or a problem with the driver) or if my card just went belly-up... Again - it worked once before in the same hardware setup running Red Hat. Hope this helps... ======================================================== == GIANT Network Productions == == web hosting + web design + consulting == ======================================================== ++ 541 . 684 . 9798 http://www.jollygreen.com/ ++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From becker@scyld.com Wed, 26 Sep 2001 22:48:49 -0400 (EDT) Date: Wed, 26 Sep 2001 22:48:49 -0400 (EDT) From: Donald Becker becker@scyld.com Subject: [tulip] ng_tulip driver On Wed, 26 Sep 2001, GIANT Network Productions wrote: > >On Thu, 20 Sep 2001, Keith Anderson wrote: > > > > > I own a Netgear FA310TX rev D2 10/100 NIC and am currently having > > > trouble getting any linux drivers to recognize the thing. I had it > > > installed in a Red Hat (recent, not sure version) system with no > > > problems, so I know the card WILL work. However, upon removing the > > > card and trying to install it into a Debian (2.2r3 - potato) system > > > I've been unable to find ANY driver combination that will make this > > > card work - including the ng_tulip.o driver that came with the > > > distribution (modified by Netgear!). > > > >What driver versions have you tried? > > ng_tulip - 0.89K.1 > tulip - 0.91g-ppc > old_tulip - 0.89H Those are all versions from over two years ago, and all have likely been modified from my release. Please try a 0.92 series driver. > >What does 'tulip-diag -aefm' report? > > #tulip-diag -aefm > Index #1: Found a Lite-On 82c168 PNIC adapter at 0xfc00 ... > The Tx process state is 'Waiting for Tx to finish'. There is a transceiver configuration problem. > No MII transceivers found! Some '168 boards used MII transceivers, but most of the early ones used SYM transceivers. > Port selection is 10mpbs-serial, half-duplex. The port setting is appropriate for a SYM/serial transceiver board. If the v0.92 drivers doesn't work (and I believe that it will), what is the transciever chip? Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 From dyret@o2.no Sun, 30 Sep 2001 00:01:35 +0200 Date: Sun, 30 Sep 2001 00:01:35 +0200 From: Marius Lindh dyret@o2.no Subject: [tulip] ana-6944 This is a multi-part message in MIME format. ------=_NextPart_000_0060_01C14943.1217CA30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello guys! I'm having some troubles with my adaptec ana-6944a/tx card using tulip = and 2.2.19. I get the card up running with all fourports, and are able = to define ips to all eth (eth0-eth3). But, the trouble is, that when I = use the differents ips, all of them are going to the eth i started = first. (Both in and out). Check out if they used the same mac address, = and it did (to different ip's). When I run ifconfig, the different ip = gots different mac-addreses.. Anyone got any good ideas? Please ;-) - Marius Lindh ------=_NextPart_000_0060_01C14943.1217CA30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hello guys!
     
    I'm having some troubles with my = adaptec=20 ana-6944a/tx card using tulip and 2.2.19. I get the card up running with = all=20 fourports, and are able to define ips to all eth (eth0-eth3). But, the = trouble=20 is, that when I use the differents ips, all of them are going to the eth = i=20 started first. (Both in and out). Check out if they used the same mac = address,=20 and it did (to different ip's). When I run ifconfig, the different ip = gots=20 different mac-addreses..
     
    Anyone got any good ideas? Please = ;-)
     
    - Marius = Lindh
    ------=_NextPart_000_0060_01C14943.1217CA30-- From greearb@candelatech.com Sat, 29 Sep 2001 15:19:39 -0700 Date: Sat, 29 Sep 2001 15:19:39 -0700 From: Ben Greear greearb@candelatech.com Subject: [tulip] ana-6944 > Marius Lindh wrote: > > Hello guys! > > I'm having some troubles with my adaptec ana-6944a/tx card using tulip and 2.2.19. I get the card up running with all fourports, and are able to define ips to all eth > (eth0-eth3). But, the trouble is, that when I use the differents ips, all of them are going to the eth i started first. (Both in and out). Check out if they used the same mac > address, and it did (to different ip's). When I run ifconfig, the different ip gots different mac-addreses.. > > Anyone got any good ideas? Please ;-) > > - Marius Lindh Try using ping with the -I option too specify the right port and see if that works. If it does, then you may need to turn on arp_filter and/or fix your routing... Ben -- Ben Greear President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear From dyret@o2.no Sun, 30 Sep 2001 00:29:16 +0200 Date: Sun, 30 Sep 2001 00:29:16 +0200 From: Marius Lindh dyret@o2.no Subject: [tulip] ana-6944 > > I'm having some troubles with my adaptec ana-6944a/tx card using tulip and 2.2.19. I get the card up running with all fourports, and are able to define ips to all eth > > (eth0-eth3). But, the trouble is, that when I use the differents ips, all of them are going to the eth i started first. (Both in and out). Check out if they used the same mac > > address, and it did (to different ip's). When I run ifconfig, the different ip gots different mac-addreses.. > > > > Anyone got any good ideas? Please ;-) > > > > - Marius Lindh > Try using ping with the -I option too specify the right port and see > if that works. If it does, then you may need to turn on arp_filter > and/or fix your routing... I have tryed this. i.e.: eth0 = 192.168.0.80 eth1 = 192.168.0.81 ping -I 192.168.0.80 192.168.0.100 and ping -I 192.168.0.81 192.168.0.100 are using the same ethernet interfaces.. If i'll do the pinging from 192.168.0.100 to 192.168.0.80 and 192.168.0.81 and run arp -a , i get the same mac-addresses on both 80 and 81... - Marius Lindh From greearb@candelatech.com Sat, 29 Sep 2001 15:36:51 -0700 Date: Sat, 29 Sep 2001 15:36:51 -0700 From: Ben Greear greearb@candelatech.com Subject: [tulip] ana-6944 Marius Lindh wrote: > > > > I'm having some troubles with my adaptec ana-6944a/tx card using tulip > and 2.2.19. I get the card up running with all fourports, and are able to > define ips to all eth > > > (eth0-eth3). But, the trouble is, that when I use the differents ips, > all of them are going to the eth i started first. (Both in and out). Check > out if they used the same mac > > > address, and it did (to different ip's). When I run ifconfig, the > different ip gots different mac-addreses.. > > > > > > Anyone got any good ideas? Please ;-) > > > > > > - Marius Lindh > > Try using ping with the -I option too specify the right port and see > > if that works. If it does, then you may need to turn on arp_filter > > and/or fix your routing... > I have tryed this. > > i.e.: > eth0 = 192.168.0.80 > eth1 = 192.168.0.81 > Try ping -I eth0 192.168.0.100 and ping -I eth1 192.168.0.100 Try turning on ARP filter: echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter You do realize you have two interfaces on the same subnet on the same machine, that is not a normal thing to do.... Ben > ping -I 192.168.0.80 192.168.0.100 > and > ping -I 192.168.0.81 192.168.0.100 > > are using the same ethernet interfaces.. If i'll do the pinging from > 192.168.0.100 to 192.168.0.80 and 192.168.0.81 and run arp -a , i get the > same mac-addresses on both 80 and 81... > > - Marius Lindh > > _______________________________________________ > tulip mailing list, tulip@scyld.com > To change to digest mode or unsubscribe visit > http://www.scyld.com/mailman/listinfo/tulip -- Ben Greear President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear From yangpababo@yahoo.com Sat, 29 Sep 2001 21:49:13 -0700 Date: Sat, 29 Sep 2001 21:49:13 -0700 From: yangpababo yangpababo@yahoo.com Subject: [tulip] compaq presario 1700xl4 hi, name's kim. i have presario 1700 with rh7.1, kernel version 2.4.2-3. been trying to make ethernet work for awhile,, still nothing. here's what tulip.diag -aem says; tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a Conexant LANfinity adapter at 0x1400. Conexant LANfinity chip registers at 0x1400: 0x00: fff84000 ffffffff ffffffff 00000000 00000000 f4008800 e00a0040 7bfe0000 0x40: fffe0000 fff080e8 fffe0000 fffe0000 ffffffff ffffffff ffffffff f7f9fec8 Extended registers: 80: cc008800 cbfe0000 f0000018 00000000 ffffffff 00000000 00000000 00000000 a0: ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 00000000 c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e0: 00000000 00000000 00000000 00000000 ffffffff 00000000 00000000 00000000 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. Interrupt sources are pending! CSR5 is f4008800. Timer expired indication. EEPROM 256 words, 8 address bits. Conexant EEPROM format is undocumented. MII PHY found at address 1, status 0x782d. MII PHY found at address 0, status 0x782d. MII PHY #1 transceiver registers: 1000 782d 0022 1720 01e1 0020 0004 2001 1000 782d 0022 1720 01e1 0020 0004 2001 1000 782d 0022 1720 01e1 0000 0004 2001 0000 0000 0000 0000 01e1 2001 0000 9c04. MII PHY #0 transceiver registers: 1000 782d 0022 1720 01e1 0020 0004 2001 1000 782d 0022 1720 01e1 0020 0004 2001 1000 782d 0022 1720 01e1 0000 0004 2001 0000 0000 0000 0000 01e1 2001 0000 9c04. so, tell me, what can i do other than banin' my head againt the wall??? thanks for your time and help and everything.... yangpa=babo _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com