>----- Original Message ----- >From: Brock Nanson [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Date: Fri, 12 Jul 2002 06:55:52 -0700 >Subject: Re: [leaf-user] eth1:Tx timeout! Resetting card > > >----- Original Message ----- >From: "Taewoon.Goo" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Cc: <[EMAIL PROTECTED]> >Sent: Friday, July 12, 2002 2:57 AM >Subject: Re:Re: [leaf-user] eth1:Tx timeout! Resetting card > > >| >| >----- Original Message ----- >| >From: Brock Nanson [EMAIL PROTECTED] >| >To: [EMAIL PROTECTED] >| >Cc: [EMAIL PROTECTED] >| >Date: Tue, 9 Jul 2002 21:15:23 -0700 >| >Subject: Re: [leaf-user] eth1:Tx timeout! Resetting card >| > >| >| Date: Wed, 10 Jul 2002 09:17:54 +0900 (KST) >| >| From: "Taewoon.Goo" <[EMAIL PROTECTED]> >| >| Subject: Re:RE: [leaf-user] eth1:Tx timeout! Resetting card >| >| To: [EMAIL PROTECTED] >| >| cc: [EMAIL PROTECTED] >| >| Organization: >| >| >| >| >| >| >----- Original Message ----- >| >| >From: Brock Nanson [EMAIL PROTECTED] >| >| >To: [EMAIL PROTECTED] >| >| >Cc: [EMAIL PROTECTED] >| >| >Date: Tue, 9 Jul 2002 08:31:47 -0700 >| >| >Subject: RE: [leaf-user] eth1:Tx timeout! Resetting card >| >| > >| >| >> > Date: Sun, 7 Jul 2002 08:07:54 +0900 (KST) >| >| >> > From: "Taewoon.Goo" <[EMAIL PROTECTED]> >| >| >> > To: [EMAIL PROTECTED] >| >| >> > Organization: >| >| >> > Subject: [leaf-user] eth1:Tx timeout! Resetting card.. >| >| >> > >| >| >> > Hi, I'm having some trouble making a wireless gateway or router, >and >| >| >> need some help. >| >| >> > when I ping to 192.168.0.2(my second pc), Bering puts this message >| >| >> repeatedly >| >| >> > "eth1:Tx timeout! Resetting card" >| >| >> > >| >| >> > what it means and what should i do? >| >| >> > >| >| >> > Thanks >| >| >> > >| >| >> > ah, my setup is as follows.. >| >| >> > >| >| >> > <hardware> >| >| >> > eth0 -- realtek 8139 pci >| >| >> > eth1 -- lucent orinoco 11mbit 802.11b card in a ricoh rl5c475 >| >| >> pci-pcmcia adapter. >| >| >> > >| >| >> > <software> >| >| >> > bering 1.0 rc2 + pcmcia.lrp,wireless.lrp,libm.lrp >| >| >> > >| >| > >| >| >You don't mention if you have wireutil.lrp on your system. You >probably >| >| >should. Also, some choice extracts from your logs would be helpful. >| >| >I'm going to guess that the card isn't coming up during boot properly >at >| >| >all. >| >| > >| >| >Brock >| >| > >| >| > >| >| >| >| As you say, I added wireutil.lrp on my system. But nothing changed. >| >| >| >| In redhat7.3, same error message is occured, but it is doing well as a >| >gateway. >| >| ping and masquerading is ok. >| >| error messages are "eth1:Tx error status 4(FID=01E2)" at boot time, and >| >"eth1: >| >| Tx error status 1(FID=017E), eth1:Tx error status 1(FID=0xxx)" at ping >| >time continually. >| >| >| >| my logs in /var/log/ is changed. >| >| >| >| "syslog" for example >| >| >| >| ## before i ping to 192.168.0.2 >| >| >| > >| ><giant hack> >| > >| >| Jul 10 08:39:21 firewall kernel: 8139too Fast Ethernet driver 0.9.24 >| >| Jul 10 08:39:21 firewall kernel: PCI: Found IRQ 11 for device 00:10.0 >| >| Jul 10 08:39:21 firewall kernel: PCI: Sharing IRQ 11 with 00:07.2 >| >| Jul 10 08:39:21 firewall kernel: PCI: Sharing IRQ 11 with 00:07.3 >| >| Jul 10 08:39:21 firewall kernel: eth0: RealTek RTL8139 Fast Ethernet at >| >0xd8821000, 00:c0:26:73:51:8d, IRQ 11 >| >| Jul 10 08:39:21 firewall kernel: eth0: Identified 8139 chip type >| >'RTL-8139C' >| >| Jul 10 08:39:21 firewall kernel: eth0: Setting half-duplex based on >| >auto-negotiated partner ability 0000. >| >| Jul 10 08:39:21 firewall kernel: Linux PCMCIA Card Services 3.1.33 >| >| Jul 10 08:39:21 firewall kernel: kernel build: 2.4.18 #9 Sun Apr 7 >| >13:54:58 CEST 2002 >| >| Jul 10 08:39:21 firewall kernel: options: [pci] [cardbus] >| >| Jul 10 08:39:21 firewall kernel: Intel ISA/PCI/CardBus PCIC probe: >| >| Jul 10 08:39:21 firewall kernel: PCI: Found IRQ 9 for device 00:0e.0 >| >| Jul 10 08:39:21 firewall kernel: Ricoh RL5C475 rev 80 PCI-to-CardBus >at >| >slot 00:0e, mem 0xdb003000 >| >| Jul 10 08:39:21 firewall kernel: host opts [0]: [isa irq] [io >3/6/1] >| >[mem 3/6/1] [pci irq 9] [lat 32/176] [bus 2/5] >| >| Jul 10 08:39:21 firewall kernel: ISA irqs (default) = 3,4,5,7,14,15 >| >PCI status changes >| >| Jul 10 08:39:21 firewall cardmgr[699]: watching 1 sockets >| >| Jul 10 08:39:21 firewall cardmgr[700]: starting, version is 3.1.33 >| >| Jul 10 08:39:21 firewall cardmgr[700]: socket 0: Intersil PRISM2 11 >Mbps >| >Wireless Adapter >| >| Jul 10 08:39:21 firewall kernel: cs: memory probe >0xa0000000-0xa0ffffff: >| >clean. >| >| Jul 10 08:39:21 firewall cardmgr[700]: executing: 'insmod >| >/lib/modules/2.4.18/pcmcia/hermes.o' >| >| Jul 10 08:39:21 firewall kernel: hermes.c: 16 Jan 2002 David Gibson >| ><[EMAIL PROTECTED]> >| >| Jul 10 08:39:21 firewall cardmgr[700]: + Using >| >/lib/modules/2.4.18/pcmcia/hermes.o >| >| Jul 10 08:39:21 firewall cardmgr[700]: executing: 'insmod >| >/lib/modules/2.4.18/pcmcia/orinoco.o' >| >| Jul 10 08:39:21 firewall kernel: orinoco.c 0.09b (David Gibson >| ><[EMAIL PROTECTED]> and others) >| >| Jul 10 08:39:21 firewall cardmgr[700]: + Using >| >/lib/modules/2.4.18/pcmcia/orinoco.o >| >| Jul 10 08:39:21 firewall cardmgr[700]: executing: 'insmod >| >/lib/modules/2.4.18/pcmcia/orinoco_cs.o' >| >| Jul 10 08:39:21 firewall kernel: orinoco_cs.c 0.09b (David Gibson >| ><[EMAIL PROTECTED]> and others) >| >| Jul 10 08:39:21 firewall cardmgr[700]: + Using >| >/lib/modules/2.4.18/pcmcia/orinoco_cs.o >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0100-0x04ff: >| >excluding 0x170-0x177 0x1f0-0x1f7 0x220-0x22f 0x370-0x37f 0x388-0x38f >| >0x3c0-0x3df 0x3f0-0x3ff 0x4d0-0x4d7 >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0178-0x01ef: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x01f8-0x021f: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0230-0x036f: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0380-0x0387: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0390-0x03bf: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x03e0-0x03ef: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0400-0x04cf: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x04d8-0x04ff: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0800-0x08ff: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0a00-0x0aff: >clean. >| >| Jul 10 08:39:21 firewall kernel: cs: IO port probe 0x0c00-0x0cff: >clean. >| >| Jul 10 08:39:21 firewall kernel: eth1: Station identity >| >001f:0001:0007:001c >| >| Jul 10 08:39:21 firewall kernel: eth1: Looks like a Lucent/Agere >firmware >| >version 7.28 >| >| Jul 10 08:39:21 firewall kernel: eth1: Ad-hoc demo mode supported >| >| Jul 10 08:39:21 firewall kernel: eth1: IEEE standard IBSS ad-hoc mode >| >supported >| >| Jul 10 08:39:21 firewall kernel: eth1: WEP supported, 104-bit key >| >| Jul 10 08:39:21 firewall kernel: eth1: MAC address 00:02:2D:2E:5D:C0 >| >| Jul 10 08:39:21 firewall kernel: eth1: Station name "HERMES I" >| >| Jul 10 08:39:21 firewall kernel: eth1: ready >| >| Jul 10 08:39:21 firewall kernel: eth1: index 0x01: Vcc 5.0, irq 3, io >| >0x0100-0x013f >| >| Jul 10 08:39:21 firewall cardmgr[700]: executing: './network start >eth1' >| >| Jul 10 08:39:23 firewall root: Shorewall Started >| >| Jul 10 08:39:23 firewall /usr/sbin/cron[1649]: (CRON) INFO (pidfile fd >= >| >3) >| >| Jul 10 08:39:23 firewall /usr/sbin/cron[1650]: (CRON) STARTUP (fork ok) >| >| Jul 10 08:40:17 firewall kernel: VFS: Disk change detected on device >| >fd(2,0) >| >| >| >| ## end >| >| >| >| and after ping added some snippets after last log line >| >| like this.. >| >| ..... >| >| ..... >| >| Jul 10 08:39:23 firewall root: Shorewall Started >| >| Jul 10 08:39:23 firewall /usr/sbin/cron[1649]: (CRON) INFO (pidfile fd >= >| >3) >| >| Jul 10 08:39:23 firewall /usr/sbin/cron[1650]: (CRON) STARTUP (fork ok) >| >| Jul 10 08:40:17 firewall kernel: VFS: Disk change detected on device >| >fd(2,0) >| >| (this) >| >| Jul 10 08:41:06 firewall kernel: NETDEV WATCHDOG: eth1: transmit timed >out >| >| Jul 10 08:41:06 firewall kernel: eth1: Tx timeout! Resetting card. >| >| Jul 10 08:41:14 firewall kernel: NETDEV WATCHDOG: eth1: transmit timed >out >| >| Jul 10 08:41:14 firewall kernel: eth1: Tx timeout! Resetting card. >| >| Jul 10 08:41:22 firewall kernel: NETDEV WATCHDOG: eth1: transmit timed >out >| >| Jul 10 08:41:22 firewall kernel: eth1: Tx timeout! Resetting card. >| >| Jul 10 08:41:30 firewall kernel: NETDEV WATCHDOG: eth1: transmit timed >out >| >| Jul 10 08:41:30 firewall kernel: eth1: Tx timeout! Resetting card. >| >| Jul 10 08:41:38 firewall kernel: NETDEV WATCHDOG: eth1: transmit timed >out >| >| Jul 10 08:41:38 firewall kernel: eth1: Tx timeout! Resetting card. >| >| >| >| >| >| thanks for your constant concern.. >| > >| >Hi, >| > >| >Now what I find interesting is this from my log, using an ISA-PCMCIA >adapter >| >(Ricoh) and a Lucent silver card: >| > >| >Jul 9 13:33:51 firewall kernel: kernel build: 2.4.18 #9 Sun Apr 7 >| >13:54:58 CEST 2002 >| >Jul 9 13:33:51 firewall kernel: options: [pci] [cardbus] >| >Jul 9 13:33:51 firewall kernel: Intel ISA/PCI/CardBus PCIC probe: >| >Jul 9 13:33:51 firewall kernel: Ricoh RF5C296/396 rev 00 ISA-to-PCMCIA >at >| >port 0x3e0 ofs 0x00 >| >Jul 9 13:33:51 firewall kernel: host opts [0]: none >| >Jul 9 13:33:51 firewall kernel: ISA irqs (scanned) = 3,4,5,7 polling >| >interval = 1000 ms >| >Jul 9 13:33:51 firewall cardmgr[8506]: watching 1 sockets >| >Jul 9 13:33:51 firewall cardmgr[8507]: starting, version is 3.1.33 >| >Jul 9 13:33:52 firewall cardmgr[8507]: socket 0: Lucent Technologies >| >Wavelan/IEEE >| > >| >Notice that cardmgr detects that I have a Lucent card in the socket. >Your >| >log shows: >| > >| >Jul 10 08:39:21 firewall cardmgr[700]: socket 0: Intersil PRISM2 11 Mbps >| >Wireless Adapter >| > >| >The Lucent is NOT a PRISM2 card. The orinoco_cs driver will work with >many >| >PRISM2 cards, but I think what this suggests is that the >/etc/pcmcia/config >| >file is being checked and the wrong card is found. I don't know if that >is >| >causing your problem, but who knows ;-). I had my configuration miss my >| >card at first too, so I deleted all the extra entries from the file... >| >didn't need the other stuff anyway as I won't be using other cards. It >| >eventually settled on using the right entry. >| > >| >| Yes, my redhat7.3 box also tells "socket 0: Lucent Technologies >Wavelan/IEEE" >| so i comment PRISM2 part in 'hermes.conf' file. in my case 'config' don't >appected anything. >| Finally, my bering log is also "socket 0: Lucent Technologies >Wavelan/IEEE", >| but same result.. >| >| >I've pasted in stuff I snipped prematurely from the original post: >| > >| >> #/etc/pcmcia/network.opts >| >> >| >> case "$ADDRESS" in >| >> >| >> *,*,*,*) >| >> INFO="sample Wireless" >| >> IPADDR="192.168.0.1" >| >> NETMASK="255.255.255.0" >| >> NETWORK="192.168.0.0" >| >> BROADCAST="192.168.0.255 >| >> >| >> ;; >| >> >| >> esac >| >> >| >> #/etc/pcmcia/wireless.opts >| >> >| >> case "$ADDRESS" in >| >> >| >> *,*,*,*) >| >> INFO="Orinoco" >| >> MODE="Ad-Hoc" >| >> CHANNEL="10" >| >> RATE="11M" >| >> ESSID="test" >| >> IWCONFIG="nick HOME" >| >> ;; >| >> esac >| > >| >I don't have a network.opts file... did you have one installed >automatically >| >with RC2 or did you port some of this stuff from a 'regular' linux box? >| >These entries are serving the same purpose, but I *think* wireless.opts >will >| >take precedence. >| >| You are right! >| I deleted my 'network.opts'. >| >| > >| >What does executing 'iwconfig' tell you? >| > >| <redhat7.3> >| eth1 IEEE 802.11-DS ESSID:"workgroup" Nickname:"HOME" >| Mode:Ad-Hoc Frequency:2.457GHz Cell: 02:02:2D:2E:5D:C0 >| Bit Rate=2Mb/s Tx-Power=15 dBm Sensitivity:1/3 >| Retry limit:4 RTS thr:off Fragment thr:off >| Encryption key:off >| Power Management period:100ms mode:All packets received >| Link Quality:0 Signal level:0 Noise level:0 >| Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >| Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >| <Bering rc2> >| eth1 IEEE 802.11-DS ESSID:"workgroup" Nickname:"hermes" >| Mode:Ad-Hoc Frequency:2.457GHz Cell: 02:02:2D:2E:5D:C0 >| Bit Rate:2Mb/s Tx-Power=15 dBm Sensitivity:1/3 >| Retry limit:4 RTS thr:off Fragment thr:off >| Encryption key:off >| Power Management period:100ms mode:All packets received >| Link Quality:0 Signal level:0 Noise level:0 >| Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >| Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >| >| >| >| >I'm about out of ideas... hopefully someone that knows what they're doing >| >will jump in and tell us where I'm wrong ;-) >| > >| >Brock >| > >| > >| > >| >| What about different modules? >| >| #lsmod >| <Bering> >| orinoco_cs(2),orinoco(0),hermes(0),ds(1),i82365(1),pcmcia_core(0) >| >| <Redhat> >| orinoco_cs(1),orinoco(0),hermes(0),ds(1),yenta_socket(1),pcmcia_core(0) >| >| I suspect these modules (i82365, yenta_socket) but unfortunately, i don't >know >| what they do. >| >| thanks. > >Hi, > >The modules that are different suggest you have a different pcmcia adapter >card in the redhat box. Is that the case? If the redhat box isn't a >laptop, I think you should try swapping the adapter cards. You will need >the yenta module of course, but that should be around Jacques site >somewhere. > >The adapter cards can be the most troublesome part of the equation. I >couldn't get my PCI adapter going properly until I added the parameter >PCIC_OPTS="irq_mode=0" to the /etc/default/pcmcia file. However, I don't >think this is your problem as this change was needed to make the TI chipset >work. Different symptoms also. >
It works!! PCIC_OPTS="irq_mode=0" is the key! yes, I have an orinoco and that is not(maybe) the TI chipset, but it works anyway.. And another important thing is that I don't know what it means. Could you explain to me the meaning of that? >One last thing that causes me to wonder... why does the nick 'hermes' show >up in your iwconfig results when your wireless.opts shows 'home'? Does this >suggest the wrong file is still being read? The ESSID is also different... >'workgroup' and 'test'. The channel is correct however, based on the >frequency iwconfig indicates. > I'm sorry for that confusing thing. These 'workgroup' and 'hermes' are just test trying for my win98 config. My mind dims for a moment.. >Ad-Hoc mode on the orinoco cards changed with the firmware. You should be >sure that they all have up to date firmware, or at least the same firmware! >I'd suggest going to the newest just to eliminate that possibility. Can I >assume you hear two high beeps on boot, and not a high then low? > I have heard always two high beeps on boot. >Are you confident that your firewall rules are OK, so that if the card was >actually working before the time out errors, you'd know? You could check >your logs for any blocked packet messages resulting from the pings. > >If you do 'svi pcmcia restart' after the boot, does anything change? > >Brock > I realy realy appreciate your help, Brock! ------------------------------------------------- DreamWiz Free Mail @ http://www.dreamwiz.com/ DreamSearch Click the world!!! http://search.dreamwiz.com/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
