American Yellow Pages Inc.

From web@Bigwabbit.net Thu May 2 15:35:00 2002 From: web@Bigwabbit.net (Dor S.) Date: Thu May 2 14:35:00 2002 Subject: [vortex] Help me :( Message-ID: <001f01c1f208$00b497a0$0200a8c0@dor> Hello, I emailed my "story" yesterday to "3c509" mailing list by they sent me here. Anyway, I have a Linux box that is doing masq... it shares my cables connection with the home lan. I've got 2 network cards, a 3com 3com 905B and a RealTek 8139. Few months ago when I had first set it up, i've had problems and used the 3com driver that is offered on 3com.com and it worked ok, now I installed SuSE 8.0 which wouldn't let me install the driver from 3com.com, and is using scyld.com's driver. And again, I have this weird problem that when i'm doing the masq everything is slower than when I used the old driver from 3com.com or when I connect the cable modem directly to my computer. Some info: i'm using iptables to do the masq, the 3com NIC is connected to the cable modem, and the RealTek to a hub which the rest of the computers are connected to it. Please help me I dunno what to do :( Maybe I just have something misconfigured? If I wouldn't have that fixed soon, I guess i'll just go back to the old Linux distro I used and install the 3com.com driver which worked fine. Thanks in advance! :) -Dor From submissions@americasbusinessdirectory.com Fri May 3 02:58:00 2002 From: submissions@americasbusinessdirectory.com (American Yellow Pages, Inc.) Date: Fri May 3 01:58:00 2002 Subject: [vortex] Urgent: Verification Message-ID: American Yellow Pages Inc.

American

Yellow Pages

American Yellow Pages Inc.

Submissions Department

P.O. Box 803515

Dallas, TX 75380-3515

Please Handle Immediately

Customer Service: 1-800-343-4662

Time to Review your American Yellow Pages Listing.
Click Here.

This E-Mail is Intended for U.S. Businesses Only.
American Yellow Pages lists virtually all U.S. Businesses in its Directories.
There is no charge for your basic listing in the American Yellow Pages Directory.
This Mail is Intended to let you Review, Modify or Remove the Information
we have on file or listed in our Directories.

If you feel you received this message in error or do not want to be contacted further at this address,
click here and we will remove this e-mail address from this review process in the future.

click to report

spam or abuse

From ruben@its.blacklisted.nl Fri May 3 17:15:01 2002 From: ruben@its.blacklisted.nl (ruben@its.blacklisted.nl) Date: Fri May 3 16:15:01 2002 Subject: [vortex] Re: Help me :( In-Reply-To: <001f01c1f208$00b497a0$0200a8c0@dor> References: <001f01c1f208$00b497a0$0200a8c0@dor> Message-ID: <20020503201355.2185.qmail@its.blacklisted.nl> Dor S. writes: > And again, I have this weird problem that when i'm doing the masq > everything is slower than when I used the old driver from 3com.com or > when I connect the cable modem directly to my computer. How do you mean slower? What is slow? "Everything" could be, euh, well, everything. Can you explain what happens? -- Ruben From web@Bigwabbit.net Fri May 3 17:56:00 2002 From: web@Bigwabbit.net (Dor S.) Date: Fri May 3 16:56:00 2002 Subject: [vortex] Re: Help me :( References: <001f01c1f208$00b497a0$0200a8c0@dor> <20020503201355.2185.qmail@its.blacklisted.nl> Message-ID: <002201c1f2e4$ed28bda0$4aa2b3d4@dor> Mostly downloads! They sometimes are half fast then when I download with the modem connected directly ----- Original Message ----- From: To: Cc: "Dor S." Sent: Friday, May 03, 2002 11:13 PM Subject: [vortex] Re: Help me :( > Dor S. writes: > > And again, I have this weird problem that when i'm doing the masq > > everything is slower than when I used the old driver from 3com.com or > > when I connect the cable modem directly to my computer. > > How do you mean slower? What is slow? "Everything" could be, euh, well, > everything. Can you explain what happens? > > -- > > Ruben > _______________________________________________ > vortex mailing list > vortex@scyld.com > http://www.scyld.com/mailman/listinfo/vortex From Donovan_Carthew/systec@healthsystems.co.za Fri May 10 02:39:00 2002 From: Donovan_Carthew/systec@healthsystems.co.za (Donovan_Carthew/systec@healthsystems.co.za) Date: Fri May 10 01:39:00 2002 Subject: [vortex] 3c59x.c Message-ID: Hi I've got a 3com 900B EtherLink card running (kernel 2.4.10-4GB). I was just wondering if you could tell me if 10base2 is supported. I've had a hell of a time trying to get it working with coax... UTP works fine. Thanks, Donovan From becker@scyld.com Fri May 10 13:02:02 2002 From: becker@scyld.com (Donald Becker) Date: Fri May 10 12:02:02 2002 Subject: [vortex] 3c59x.c In-Reply-To: Message-ID: On Fri, 10 May 2002 Donovan_Carthew/systec@healthsystems.co.za wrote: > I've got a 3com 900B EtherLink card running (kernel 2.4.10-4GB). I was just > wondering if you could tell me if 10base2 is supported. Yes, it is. Coax media cannot be automatically detected and must be specified in the EEPROM or as a module option. http://www.scyld.com/network/vortex.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 Daliang.Wen@abrandnewworld.se Tue May 14 08:32:00 2002 From: Daliang.Wen@abrandnewworld.se (Daliang Wen) Date: Tue May 14 07:32:00 2002 Subject: [vortex] problem with mini-pci card Message-ID: <03D9677DE88E3B478963DB2330DB23D51F59FF@mail.abrandnewworld.se> Hi all, Just join the mailing list. I have a problem with 3com's Mini-PCI card on Linux 2.2.19. I have a linux box (Linux 2.2.19brfw i586) working as a bridge with 2 ethernet interface. One is an integrated Inter EEPRO 100 ethernet controller which works fine. The other one is the 3com's Mini-PCI (3CN3AC1556B) which doesn't work at all. Here is the log message after I set the debug option to 6 and "ifconfig eth1 up" (eth0 is the Intel card): >From "/proc/device": Bus 0, device 15, function 0: Ethernet controller: 3Com Unknown device (rev 32). Vendor id=10b7. Device id=6056. Medium devsel. IRQ 10. Master Capable. Latency=80. Min Gnt=10.Max Lat=10. I/O at 0x1400 [0x1401]. Non-prefetchable 32 bit memory at 0xfea01400 [0xfea01400]. Non-prefetchable 32 bit memory at 0xfea01000 [0xfea01000]. >From /var/log/messages: May 14 09:51:41 Wilma kernel: 3c59x.c 18Feb01 Donald Becker and others http://www.scyld.com/network/vortex.html May 14 09:51:41 Wilma kernel: eth1: 3Com 3c556B Laptop Hurricane at 0x1400, 00:04:76:4d:d8:3c, IRQ 10 May 14 09:51:41 Wilma kernel: eth1: CardBus functions mapped fea01000->c481f000 (PCMCIA committee brain-damage). May 14 09:51:41 Wilma kernel: Internal config register is 80600040, transceivers 0x40. May 14 09:51:41 Wilma kernel: 8K byte-wide RAM 5:3 Rx:Tx split, MII interface. May 14 09:51:41 Wilma kernel: MII transceiver found at address 0, status 7849. May 14 09:51:41 Wilma kernel: Enabling bus-master transmits and whole-frame receives. May 14 09:51:55 Wilma kernel: eth1: Initial media type MII. May 14 09:51:55 Wilma kernel: eth1: MII #0 status 7849, link partner capability 0001, setting half-duplex. May 14 09:51:55 Wilma kernel: eth1: vortex_open() InternalConfig 80600040. May 14 09:51:55 Wilma kernel: eth1: vortex_open() irq 10 media status 8080. May 14 09:51:55 Wilma kernel: eth1: Filling in the Rx ring. May 14 09:51:58 Wilma kernel: eth1: Media selection timer tick happened, MII. May 14 09:51:58 Wilma kernel: eth1: MII transceiver has status 7849. May 14 09:51:58 Wilma kernel: eth1: Media selection timer finished, MII. May 14 09:52:13 Wilma kernel: eth1: Setting promiscuous mode. May 14 09:52:13 Wilma kernel: device eth1 entered promiscuous mode May 14 09:52:13 Wilma kernel: br0: port 2(eth1) entering listening state May 14 09:52:28 Wilma kernel: br0: port 2(eth1) entering learning state May 14 09:52:43 Wilma kernel: br0: port 2(eth1) entering forwarding state May 14 09:52:43 Wilma kernel: br0: topology change detected, propagating May 14 09:52:44 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 0. May 14 09:52:44 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 1. May 14 09:52:45 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 2. May 14 09:52:45 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 3. May 14 09:52:47 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 4. May 14 09:52:47 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 5. May 14 09:52:47 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 6. May 14 09:52:47 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 7. May 14 09:52:48 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 8. May 14 09:52:48 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 9. May 14 09:52:49 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 10. May 14 09:52:50 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 11. May 14 09:52:50 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 12. May 14 09:52:51 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 13. May 14 09:52:51 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 14. May 14 09:52:51 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 15. May 14 09:52:58 Wilma kernel: eth1: Media selection timer tick happened, MII. May 14 09:52:58 Wilma kernel: eth1: MII transceiver has status 7849. May 14 09:52:58 Wilma kernel: eth1: Media selection timer finished, MII. May 14 09:52:58 Wilma kernel: eth1: transmit timed out, tx_status 00 status e201. May 14 09:52:58 Wilma kernel: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? May 14 09:52:58 Wilma kernel: eth1: interrupt, status e201, latency 255, cur_rx 0, dirty_rx 0 May 14 09:52:58 Wilma kernel: eth1: In interrupt loop, status e201. May 14 09:52:58 Wilma kernel: eth1: exiting interrupt, status e000. May 14 09:52:58 Wilma kernel: Flags; bus-master 1, full 0; dirty 16 current 16. May 14 09:52:58 Wilma kernel: Transmit list 00000000 vs. c365e200. May 14 09:52:58 Wilma kernel: 0: @c365e200 length 80000072 status 00010072 May 14 09:52:58 Wilma kernel: 1: @c365e210 length 80000062 status 00010062 May 14 09:52:58 Wilma kernel: 2: @c365e220 length 8000003c status 0001003c May 14 09:52:58 Wilma kernel: 3: @c365e230 length 8000003c status 0001003c May 14 09:52:58 Wilma kernel: 4: @c365e240 length 8000003c status 0001003c May 14 09:52:58 Wilma kernel: 5: @c365e250 length 80000040 status 00010040 May 14 09:52:58 Wilma kernel: 6: @c365e260 length 8000003c status 0001003c May 14 09:52:58 Wilma kernel: 7: @c365e270 length 80000062 status 00010062 May 14 09:52:58 Wilma kernel: 8: @c365e280 length 80000040 status 00010040 May 14 09:52:58 Wilma kernel: 9: @c365e290 length 80000040 status 00010040 May 14 09:52:58 Wilma kernel: 10: @c365e2a0 length 8000003c status 0001003c May 14 09:52:58 Wilma kernel: 11: @c365e2b0 length 8000006d status 0001006d May 14 09:52:58 Wilma kernel: 12: @c365e2c0 length 80000071 status 00010071 May 14 09:52:58 Wilma kernel: 13: @c365e2d0 length 8000003c status 0001003c May 14 09:52:58 Wilma kernel: 14: @c365e2e0 length 80000062 status 80010062 May 14 09:52:58 Wilma kernel: 15: @c365e2f0 length 8000006d status 8001006d May 14 09:52:58 Wilma kernel: eth1: Resetting the Tx ring pointer. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 16. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 17. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 18. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 19. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 20. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 21. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 22. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 23. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 24. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 25. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 26. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 27. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 28. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 29. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 30. May 14 09:52:58 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 31. May 14 09:53:08 Wilma kernel: eth1: transmit timed out, tx_status 00 status e281. May 14 09:53:08 Wilma kernel: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? May 14 09:53:08 Wilma kernel: eth1: interrupt, status e281, latency 255, cur_rx 0, dirty_rx 0 May 14 09:53:08 Wilma kernel: eth1: In interrupt loop, status e281. May 14 09:53:08 Wilma kernel: eth1: Updating stats. May 14 09:53:08 Wilma kernel: eth1: exiting interrupt, status e000. May 14 09:53:08 Wilma kernel: Flags; bus-master 1, full 0; dirty 32 current 32. May 14 09:53:08 Wilma kernel: Transmit list 00000000 vs. c365e200. May 14 09:53:08 Wilma kernel: 0: @c365e200 length 8000003c status 0001003c May 14 09:53:08 Wilma kernel: 1: @c365e210 length 80000072 status 00010072 May 14 09:53:08 Wilma kernel: 2: @c365e220 length 80000040 status 00010040 May 14 09:53:08 Wilma kernel: 3: @c365e230 length 8000003c status 0001003c May 14 09:53:08 Wilma kernel: 4: @c365e240 length 80000071 status 00010071 May 14 09:53:08 Wilma kernel: 5: @c365e250 length 8000006e status 0001006e May 14 09:53:08 Wilma kernel: 6: @c365e260 length 80000071 status 00010071 May 14 09:53:08 Wilma kernel: 7: @c365e270 length 8000003c status 0001003c May 14 09:53:08 Wilma kernel: 8: @c365e280 length 80000040 status 00010040 May 14 09:53:08 Wilma kernel: 9: @c365e290 length 8000003c status 0001003c May 14 09:53:08 Wilma kernel: 10: @c365e2a0 length 80000082 status 00010082 May 14 09:53:08 Wilma kernel: 11: @c365e2b0 length 80000040 status 00010040 May 14 09:53:08 Wilma kernel: 12: @c365e2c0 length 8000003c status 0001003c May 14 09:53:08 Wilma kernel: 13: @c365e2d0 length 8000003c status 0001003c May 14 09:53:08 Wilma kernel: 14: @c365e2e0 length 80000040 status 80010040 May 14 09:53:08 Wilma kernel: 15: @c365e2f0 length 80000040 status 80010040 May 14 09:53:08 Wilma kernel: eth1: Resetting the Tx ring pointer. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 32. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 33. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 34. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 35. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 36. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 37. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 38. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 39. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 40. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 41. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 42. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 43. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 44. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 45. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 46. May 14 09:53:08 Wilma kernel: eth1: Trying to send a boomerang packet, Tx index 47. >From "ifconfig eth1": bash# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:04:76:4D:D8:3C BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:3 dropped:0 overruns:0 carrier:75 collisions:0 txqueuelen:100 Interrupt:10 Base address:0x1400 ============================= bash# ./mii-diag -v eth1 mii-diag.c:v2.03 11/5/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Basic mode control register 0x3000: Auto-negotiation enabled. Basic mode status register 0x7849 ... 7849. Link status: not established. This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT. Able to perform Auto-negotiation, negotiation not complete. End of basic transceiver information. MII PHY #0 transceiver registers: 3000 7849 0022 561b 01e1 0001 0004 2001 ffff ffff ffff ffff ffff ffff ffff ffff 01c0 0000 0000 8020 4f02 0304 0026 0000 0000 bfbf 0000 ffff ffff ffff ffff ffff. Basic mode control register 0x3000: Auto-negotiation enabled. Basic mode status register 0x7849 ... 7849. Link status: not established. Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT. Able to perform Auto-negotiation, negotiation not complete. Vendor ID is 00:08:95:--:--:--, model 33 rev. 11. Vendor/Part: AdHoc Technology AH101LF. I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT Advertising no additional info pages. IEEE 802.3 CSMA/CD protocol. Link partner capability is 0001:. Negotiation did not complete. TDK format vendor-specific registers 16..18 are 0x01c0 0x0000 0x0000 Link polarity is detected as normal. Auto-negotiation complete, 10Mbps half duplex. Rx link in fail state, PLL locked. No new link status events. ============================ Any idea? Thanks in advance. Regards. /Daliang From fred-m@crl.hitachi.co.jp Tue May 14 09:38:00 2002 From: fred-m@crl.hitachi.co.jp (Fred Maciel) Date: Tue May 14 08:38:00 2002 Subject: [vortex] problem with mini-pci card References: <03D9677DE88E3B478963DB2330DB23D51F59FF@mail.abrandnewworld.se> Message-ID: <005101c1fb44$18ccd6f0$6b139085@crl8.crl.hitachi.co.jp> Hi, > Just join the mailing list. I have a problem with 3com's Mini-PCI card on Linux 2.2.19. > > I have a linux box (Linux 2.2.19brfw i586) working as a bridge with 2 ethernet interface. One is an integrated Inter EEPRO 100 ethernet controller which works fine. The other one is the 3com's Mini-PCI (3CN3AC1556B) which doesn't work at all. Hmm, let me see if I understood that correctly. The Intel EEPRO 100 is an *internal* adapter that came with your laptop, right? Then later you bought and added the 3Com mini-pci adapter, right? Regards, Fred Maciel. From Daliang.Wen@abrandnewworld.se Tue May 14 10:00:06 2002 From: Daliang.Wen@abrandnewworld.se (Daliang Wen) Date: Tue May 14 09:00:06 2002 Subject: [vortex] problem with mini-pci card Message-ID: <03D9677DE88E3B478963DB2330DB23D548B6BB@mail.abrandnewworld.se> Yepp, That's correct. -----Original Message----- From: Fred Maciel [mailto:fred-m@crl.hitachi.co.jp] Sent: den 14 maj 2002 14:19 To: vortex@scyld.com Subject: Re: [vortex] problem with mini-pci card Hi, > Just join the mailing list. I have a problem with 3com's Mini-PCI card on Linux 2.2.19. > > I have a linux box (Linux 2.2.19brfw i586) working as a bridge with 2 ethernet interface. One is an integrated Inter EEPRO 100 ethernet controller which works fine. The other one is the 3com's Mini-PCI (3CN3AC1556B) which doesn't work at all. Hmm, let me see if I understood that correctly. The Intel EEPRO 100 is an *internal* adapter that came with your laptop, right? Then later you bought and added the 3Com mini-pci adapter, right? Regards, Fred Maciel. _______________________________________________ vortex mailing list vortex@scyld.com http://www.scyld.com/mailman/listinfo/vortex From becker@scyld.com Wed May 15 13:47:01 2002 From: becker@scyld.com (Donald Becker) Date: Wed May 15 12:47:01 2002 Subject: [vortex] problem with mini-pci card In-Reply-To: <03D9677DE88E3B478963DB2330DB23D51F59FF@mail.abrandnewworld.se> Message-ID: On Tue, 14 May 2002, Daliang Wen wrote: > I have a linux box (Linux 2.2.19brfw i586) working as a bridge with 2 What modifications have been made to that kernel? > controller which works fine. The other one is the 3com's Mini-PCI > (3CN3AC1556B) which doesn't work at all. ... > Bus 0, device 15, function 0: > Vendor id=10b7. Device id=6056. ... > >From /var/log/messages: > May 14 09:51:41 Wilma kernel: 3c59x.c 18Feb01 Donald Becker and others http://www.scyld.com/network/vortex.html > May 14 09:51:41 Wilma kernel: eth1: 3Com 3c556B Laptop Hurricane at 0x1400, 00:04:76:4d:d8:3c, IRQ 10 > May 14 09:51:41 Wilma kernel: eth1: CardBus functions mapped fea01000->c481f000 (PCMCIA committee brain-damage). > May 14 09:51:41 Wilma kernel: Internal config register is 80600040, transceivers 0x40. > May 14 09:51:41 Wilma kernel: 8K byte-wide RAM 5:3 Rx:Tx split, MII interface. Hmmm, I'm not certain that this should be MII rather than NWay. > May 14 09:51:41 Wilma kernel: MII transceiver found at address 0, status 7849. ..and there is no link beat detected. > May 14 09:52:58 Wilma kernel: eth1: MII transceiver has status 7849. If you actually have link beat on the cable (and you should verify that), the driver you are using might have the incorrect attributes for this device type. Try adding the following flags to the detection table: INVERT_LED_PWR | MII_XCVR_PWR The final list might look like: IS_TORNADO|HAS_NWAY|EEPROM_8BIT|HAS_CB_FNS|INVERT_LED_PWR|MII_XCVR_PWR, }, > May 14 09:52:58 Wilma kernel: eth1: transmit timed out, tx_status 00 status e201. > May 14 09:52:58 Wilma kernel: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? This is a different problem -- interrupts are not getting through. This might be solved by passing 'noapic' as a the kernel option. -- 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 a.brooks@zfree.co.nz Sat May 18 00:30:02 2002 From: a.brooks@zfree.co.nz (a.brooks@zfree.co.nz) Date: Fri May 17 23:30:02 2002 Subject: [vortex] driver problem? Message-ID: <3ce5ca8a.67a7.0@zfree.co.nz> Hi I think there is a problem with something here I have a 3c905b and i'm running a network to my 10mb adsl router(hub) - straight through cable and getting lots of RX errors compared to another card davicom(dmfe.c driver) where I get no errors and only about 4 collisions for the same amount of data. I'm using the driver that came with 2.4.10 kernel 3c59x.c, I think the last update on it was july 2001. Should there even be collisions? eth0 Link encap:Ethernet HWaddr 00:10:4B:1A:C8:2A inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15208 errors:32 dropped:0 overruns:0 frame:64 TX packets:14995 errors:0 dropped:0 overruns:0 carrier:0 collisions:40 txqueuelen:100 RX bytes:20892712 (19.9 Mb) TX bytes:1102268 (1.0 Mb) Interrupt:10 Base address:0xdc00 __________________________________________________ Advertise with ZFREE - to find out more click below http://www.zfree.co.nz/about-us/advert.html From becker@scyld.com Sat May 18 14:24:02 2002 From: becker@scyld.com (Donald Becker) Date: Sat May 18 13:24:02 2002 Subject: [vortex] Re: driver problem? In-Reply-To: <3ce5ca8a.67a7.0@zfree.co.nz> Message-ID: On Sat, 18 May 2002 a.brooks@zfree.co.nz wrote: > Hi I think there is a problem with something here I have a 3c905b and > i'm running a network to my 10mb adsl router(hub) - straight through > cable and getting lots of RX errors compared to another card > davicom(dmfe.c driver) where I get no errors and only about 4 > collisions for the same amount of data. I'm using the driver that came > with 2.4.10 kernel 3c59x.c, I think the last update on it was july > 2001. Should there even be collisions? Yes, there should be collisions if it is a half duplex link. The Davicom chip is a bad one to compare against. Some versions of the chip don't detect CRC errors in packets. The driver tries to work around this by (painfully) calculating the CRC itself in some cases. Still, in most networks you shouldn't be seeing CRC errors. These are likely some other error. Are you seeing error messages in the logs? > RX packets:15208 errors:32 dropped:0 overruns:0 frame:64 > TX packets:14995 errors:0 dropped:0 overruns:0 carrier:0 > collisions:40 txqueuelen:100 -- 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 felipewd@terra.com.br Wed May 22 14:28:00 2002 From: felipewd@terra.com.br (Felipe W. Damasio) Date: Wed May 22 13:28:00 2002 Subject: [vortex] 3c59x MTU changing support Message-ID: Hi, I saw a "FIXME" on 3c59x driver and before I start to work on this, I was wondering if anyone is working on supporting MTU changing on the 3c59x driver. If so, need some help? According to Ben Greear some people have submitted patches for this already, but he was not sure the problem was completely solved. Thanks. Felipe. From syn@mp3.org Sat May 25 15:56:00 2002 From: syn@mp3.org (syn) Date: Sat May 25 14:56:00 2002 Subject: [vortex] frame errors under 2.4.18 with 3c900B Message-ID: <001601c2041d$d3c12b50$0200a8c0@xp> Hello all, I have a 3c900B which has worked fine in windows for years with no frame errors at all. I recently installed the NIC under mandrake linux with the following variations in driver/kernels: default mandrake kernel with 3c59x as a module 2.4.18 compiled from source kernel with 3c59x as both kernel and module 2.4.18 compiled from source kernel with 3c59x in kernel All give me the same problem.. frame errors. While the number of errors is low, it does cause a problem with I am uploading and downloading at the same time. (It kills my download speeds). my 3c900 connects to my ADSL RTU and the 8139 I have in the box connects to my LAN subnet. The 8139 in this box and that seems to work fine with no errors of any kind. An example: RX packets:167472 errors:1165 dropped:0 overruns:0 frame:1165 TX packets:115634 errors:0 dropped:0 overruns:0 carrier:0 They are also showing up under /proc/net/dev I have tried the most recent testing driver as a module as well with no difference in results. Since the nic works fine with no errors under windows there must be a driver or resource problem under linux. I wouldn't care except for the fact that I can no longer get acceptable performance out of my connection while uploading and downloading at the same time. While my upload speed remains great the download speeds will suffer hugely as soon as I start sending data. If you need more info please let me know and I would be happy to provide. here's some info that you may or may not want: lspci: 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3112 00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b112 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) 00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) 00:0c.0 Ethernet controller: 3Com Corporation 3c900B-TPO [Etherlink XL TPO] (rev 04) 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 lspci -v: 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at dc00 [size=256] Memory at e4400000 (32-bit, non-prefetchable) [size=256] Expansion ROM at [disabled] [size=64K] 00:0c.0 Ethernet controller: 3Com Corporation 3c900B-TPO [Etherlink XL TPO] (rev 04) Subsystem: 3Com Corporation 3C900B-TPO Etherlink XL TPO 10Mb Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e000 [size=128] Memory at e4401000 (32-bit, non-prefetchable) [size=128] Expansion ROM at [disabled] [size=128K] Capabilities: [dc] Power Management version 1 mii-tool: eth1: 10 Mbit, full duplex, link ok product info: vendor 00:00:00, model 0 rev 0 basic mode: 10 Mbit, full duplex basic status: link ok capabilities: 10baseT-FD 10baseT-HD advertising: 10baseT-FD link partner: 10baseT-HD no kernel errors or warnings. p.s. I have tried with and without the 8139 present and it makes no difference From akpm@zip.com.au Sat May 25 17:57:04 2002 From: akpm@zip.com.au (Andrew Morton) Date: Sat May 25 16:57:04 2002 Subject: [vortex] frame errors under 2.4.18 with 3c900B References: <001601c2041d$d3c12b50$0200a8c0@xp> Message-ID: <3CEFFB86.9851B663@zip.com.au> syn wrote: > > ... > mii-tool: > eth1: 10 Mbit, full duplex, link ok > product info: vendor 00:00:00, model 0 rev 0 > basic mode: 10 Mbit, full duplex > basic status: link ok > capabilities: 10baseT-FD 10baseT-HD > advertising: 10baseT-FD > link partner: 10baseT-HD The NIC is running at full-duplex against a half-duplex link partner. Please do: ifdown eth0 rmmod 3c59x modprobe 3c59x debug=7 ifup eth0 sleep 45 and send the log output. From hvx@cryptnet.de Mon May 27 15:42:01 2002 From: hvx@cryptnet.de (Markus Melms) Date: Mon May 27 14:42:01 2002 Subject: [vortex] WakeOnLan with 3c905C-TX Message-ID: <20020527204136.7f21c9f0.hvx@cryptnet.de> Hi, im trying to get wake-on-lan to work with the 3com 905C-TX card und linux kernel 2.4.18. It used to work some time ago with win95, so its probably a software problem. When the system is powered off the LED doesnt light any more and the system doesnt boot up when executing etherwake.. Below is some output and I would be happy to provide even more when needet. Thanks for any help, Markus joe:~# ./pciconfig -#7 -M pci-config.c:v2.02 1/8/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Device #7 at bus 0 device/function 9/0. 920010b7 02100007 02000074 00002008 0000e401 e7000000 00000000 00000000 00000000 00000000 00000000 100010b7 e6000000 000000dc 00000000 0a0a010b 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 fe020001 b7004000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Base Address 0: I/O at 0000e400. Base Address 1: Memory at e7000000. Extended capabilities, first structure at offset 0xdc. Extended PCI capability type 1 at 0xdc, next 0. Power management entry ver. 2: Capabilities fe02, Ctrl 4000, Event b700. Power state D0. joe:~# ./vortex-diag -a vortex-diag.c:v2.06 4/18/2002 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xe400. The Vortex chip may be active, so FIFO registers will not be read. To see all register values use the '-f' flag. Initial window 7, registers values by window: Window 0: 0000 0000 0000 0000 0000 00bf ffff 0000. Window 1: FIFO FIFO 0700 0000 0000 007f 0000 2000. Window 2: 5000 66da bdc2 0000 0000 0000 0052 4000. Window 3: 0000 0380 05ea 0020 000a 0800 0800 6000. Window 4: 0000 0000 0000 0cfa 0001 8880 2000 8000. Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000. Window 6: 0000 0000 0000 c500 2000 3f62 2f88 c000. Window 7: 0000 0000 0000 0000 0000 0000 0000 e000. Vortex chip registers at 0xe400 0xE410: **FIFO** 00000000 0000005b *STATUS* 0xE420: 00000020 00000000 00080000 00000004 0xE430: 00000000 47b0b850 012cc130 00080004 Indication enable is 06c6, interrupt enable is 06ce. No interrupt sources are pending. Transceiver/media interfaces available: 100baseTx 10baseT. Transceiver type in use: Autonegotiate. MAC settings: full-duplex. Station address set to 00:50:da:66:c2:bd. Configuration options 0052. joe:~# dmesg --cut--- PCI: Found IRQ 11 for device 00:09.0 PCI: Sharing IRQ 11 with 00:07.2 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 00:09.0: 3Com PCI 3c905C Tornado at 0xe400. Vers LK1.1.16 --cut--- From bubeck@think-at-work.de Mon May 27 16:09:00 2002 From: bubeck@think-at-work.de (Dr.Tilmann Bubeck) Date: Mon May 27 15:09:00 2002 Subject: [vortex] WakeOnLan with 3c905C-TX In-Reply-To: <20020527204136.7f21c9f0.hvx@cryptnet.de> References: <20020527204136.7f21c9f0.hvx@cryptnet.de> Message-ID: <20020527210833.34599904.bubeck@think-at-work.de> Markus, Have you entered options 3c59x enable_wol=1 into /etc/modules.conf to enable WOL? Till On Mon, 27 May 2002 20:41:36 +0200 Markus Melms wrote: > Hi, > > im trying to get wake-on-lan to work with the 3com 905C-TX card und > linux kernel 2.4.18. > It used to work some time ago with win95, so its probably a software > problem. When the system is powered off the LED doesnt light any more > and the system doesnt boot up when executing etherwake.. > > Below is some output and I would be happy to provide even more when > needet. Thanks for any help, > Markus > > joe:~# ./pciconfig -#7 -M > pci-config.c:v2.02 1/8/2001 Donald Becker (becker@scyld.com) > http://www.scyld.com/diag/index.html > Device #7 at bus 0 device/function 9/0. > 920010b7 02100007 02000074 00002008 0000e401 e7000000 00000000 > 00000000 00000000 00000000 00000000 100010b7 e6000000 000000dc > 00000000 0a0a010b 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 fe020001 > b7004000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 Base Address 0: I/O at 0000e400. > Base Address 1: Memory at e7000000. > Extended capabilities, first structure at offset 0xdc. > Extended PCI capability type 1 at 0xdc, next 0. > Power management entry ver. 2: Capabilities fe02, Ctrl 4000, Event > b700. Power state D0. > > joe:~# ./vortex-diag -a > vortex-diag.c:v2.06 4/18/2002 Donald Becker (becker@scyld.com) > http://www.scyld.com/diag/index.html > Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xe400. > The Vortex chip may be active, so FIFO registers will not be read. > To see all register values use the '-f' flag. > Initial window 7, registers values by window: > Window 0: 0000 0000 0000 0000 0000 00bf ffff 0000. > Window 1: FIFO FIFO 0700 0000 0000 007f 0000 2000. > Window 2: 5000 66da bdc2 0000 0000 0000 0052 4000. > Window 3: 0000 0380 05ea 0020 000a 0800 0800 6000. > Window 4: 0000 0000 0000 0cfa 0001 8880 2000 8000. > Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000. > Window 6: 0000 0000 0000 c500 2000 3f62 2f88 c000. > Window 7: 0000 0000 0000 0000 0000 0000 0000 e000. > Vortex chip registers at 0xe400 > 0xE410: **FIFO** 00000000 0000005b *STATUS* > 0xE420: 00000020 00000000 00080000 00000004 > 0xE430: 00000000 47b0b850 012cc130 00080004 > Indication enable is 06c6, interrupt enable is 06ce. > No interrupt sources are pending. > Transceiver/media interfaces available: 100baseTx 10baseT. > Transceiver type in use: Autonegotiate. > MAC settings: full-duplex. > Station address set to 00:50:da:66:c2:bd. > Configuration options 0052. > > joe:~# dmesg > --cut--- > PCI: Found IRQ 11 for device 00:09.0 > PCI: Sharing IRQ 11 with 00:07.2 > 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html > 00:09.0: 3Com PCI 3c905C Tornado at 0xe400. Vers LK1.1.16 > --cut--- > _______________________________________________ > vortex mailing list > vortex@scyld.com > http://www.scyld.com/mailman/listinfo/vortex -- +-------+-------------------------------------------------------------+ | | dr. tilmann bubeck reinform medien- und | | rein | informationstechnologie AG | | form | cell.: +49 (172) 8 84 29 72 koenigstrasse 80 | | AG | fax : +49 (711) 7 22 77 34 70173 stuttgart / germany | | | email: t.bubeck@reinform.de http://www.reinform.de | +-------+----------------------------------------------(in gruendung)-+ From hvx@cryptnet.de Mon May 27 16:37:01 2002 From: hvx@cryptnet.de (Markus Melms) Date: Mon May 27 15:37:01 2002 Subject: [vortex] WakeOnLan with 3c905C-TX In-Reply-To: <20020527210833.34599904.bubeck@think-at-work.de> References: <20020527204136.7f21c9f0.hvx@cryptnet.de> <20020527210833.34599904.bubeck@think-at-work.de> Message-ID: <20020527213645.33ad725a.hvx@cryptnet.de> No I have not, but my driver is directly in the kernel and I dont load it as a module. Can I put this option somewhere else ? Thanks Markus On Mon, 27 May 2002 21:08:33 +0200 "Dr.Tilmann Bubeck" wrote: > Markus, > > Have you entered > > options 3c59x enable_wol=1 > > into /etc/modules.conf to enable WOL? > > Till > > > > > On Mon, 27 May 2002 20:41:36 +0200 > Markus Melms wrote: > > > Hi, > > > > im trying to get wake-on-lan to work with the 3com 905C-TX card und > > linux kernel 2.4.18. > > It used to work some time ago with win95, so its probably a software > > problem. When the system is powered off the LED doesnt light any more > > and the system doesnt boot up when executing etherwake.. > > > > Below is some output and I would be happy to provide even more when > > needet. Thanks for any help, > > Markus > > > > joe:~# ./pciconfig -#7 -M > > pci-config.c:v2.02 1/8/2001 Donald Becker (becker@scyld.com) > > http://www.scyld.com/diag/index.html > > Device #7 at bus 0 device/function 9/0. > > 920010b7 02100007 02000074 00002008 0000e401 e7000000 00000000 > > 00000000 00000000 00000000 00000000 100010b7 e6000000 000000dc > > 00000000 0a0a010b 00000000 00000000 00000000 00000000 00000000 > > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > > 00000000 00000000 00000000 00000000 00000000 00000000 fe020001 > > b7004000 00000000 00000000 00000000 00000000 00000000 00000000 > > 00000000 Base Address 0: I/O at 0000e400. > > Base Address 1: Memory at e7000000. > > Extended capabilities, first structure at offset 0xdc. > > Extended PCI capability type 1 at 0xdc, next 0. > > Power management entry ver. 2: Capabilities fe02, Ctrl 4000, Event > > b700. Power state D0. > > > > joe:~# ./vortex-diag -a > > vortex-diag.c:v2.06 4/18/2002 Donald Becker (becker@scyld.com) > > http://www.scyld.com/diag/index.html > > Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xe400. > > The Vortex chip may be active, so FIFO registers will not be read. > > To see all register values use the '-f' flag. > > Initial window 7, registers values by window: > > Window 0: 0000 0000 0000 0000 0000 00bf ffff 0000. > > Window 1: FIFO FIFO 0700 0000 0000 007f 0000 2000. > > Window 2: 5000 66da bdc2 0000 0000 0000 0052 4000. > > Window 3: 0000 0380 05ea 0020 000a 0800 0800 6000. > > Window 4: 0000 0000 0000 0cfa 0001 8880 2000 8000. > > Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000. > > Window 6: 0000 0000 0000 c500 2000 3f62 2f88 c000. > > Window 7: 0000 0000 0000 0000 0000 0000 0000 e000. > > Vortex chip registers at 0xe400 > > 0xE410: **FIFO** 00000000 0000005b *STATUS* > > 0xE420: 00000020 00000000 00080000 00000004 > > 0xE430: 00000000 47b0b850 012cc130 00080004 > > Indication enable is 06c6, interrupt enable is 06ce. > > No interrupt sources are pending. > > Transceiver/media interfaces available: 100baseTx 10baseT. > > Transceiver type in use: Autonegotiate. > > MAC settings: full-duplex. > > Station address set to 00:50:da:66:c2:bd. > > Configuration options 0052. > > > > joe:~# dmesg > > --cut--- > > PCI: Found IRQ 11 for device 00:09.0 > > PCI: Sharing IRQ 11 with 00:07.2 > > 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html > > 00:09.0: 3Com PCI 3c905C Tornado at 0xe400. Vers LK1.1.16 > > --cut--- > > _______________________________________________ > > vortex mailing list > > vortex@scyld.com > > http://www.scyld.com/mailman/listinfo/vortex > > > -- > +-------+-------------------------------------------------------------+ > | | dr. tilmann bubeck reinform medien- und | > | rein | informationstechnologie AG | > | form | cell.: +49 (172) 8 84 29 72 koenigstrasse 80 | > | AG | fax : +49 (711) 7 22 77 34 70173 stuttgart / germany | > | | email: t.bubeck@reinform.de http://www.reinform.de | > +-------+----------------------------------------------(in gruendung)-+ From bryan@Virginia.EDU Wed May 29 18:35:01 2002 From: bryan@Virginia.EDU (Bryan K. Wright) Date: Wed May 29 17:35:01 2002 Subject: [vortex] 3c905c hangs w/ "transmit timed out" Message-ID: <200205292134.g4TLYfN09882@ayesha.phys.Virginia.EDU> Hi folks, I have a couple of small clusters made of Linux boxes with Asus A7V266-e motherboards and 3c905c network cards. Every few days, I find that one or more of the machines has lost network connectivity. When this happens, the machine acts as if the network driver is hung, and keeps spitting out the message: eth0: transmit timed out, tx_status 00 status e000 The only solution is to reboot. I've tried several different versions of the network driver, with the same results. Currently I'm using: "3c59x.c:v0.99V 1/28/2002 Donald Becker, becker@scyld.com" I've also tried several different kernels, including 2.2.14, 2.2.15, 2.2.16 and 2.2.19, with the same results. These motherboards are based on the VIA chipset, and I know there are some PCI latency problems with this, so I've also tried playing around with the latencies a little. For example: #"open up" the PCI bus by allowing fairly long bursts for all devices, # increasing performance setpci -v -d '*:*' latency_timer=b0 #maximize latency timer for network cards, allowing them to transmit #more data per burst, preventing buffer over/underrun conditions: setpci -v -s 00:0f.0 latency_timer=ff (stolen from http://www-106.ibm.com/developerworks/linux/library/l-hw2) This didn't make any difference either. The hangs appear to be associated with high network traffic. We have several other small clusters based on different motherboards and older 3c509 cards, and these don't have this problem. Uptimes for nodes in the other clusters are typically on the order of a year. I'd appreciate any suggestions. Since network cards are so cheap now, I'm considering just scrapping the 3c905s and replacing them with something else. Thanks, Bryan -- =============================================================================== Bryan Wright |"If you take cranberries and stew them like Physics Department | applesauce, they taste much more like prunes University of Virginia | than rhubarb does." -- Groucho Charlottesville, VA 22901 | (434) 924-7218 | bryan@virginia.edu ===============================================================================