> Message: 6 > From: "Brad Fritz" <[EMAIL PROTECTED]> > To: Homer Parker <[EMAIL PROTECTED]>, > Samuel Abreu <[EMAIL PROTECTED]> > cc: [EMAIL PROTECTED] > Subject: Re: [leaf-user] Strange error in netcs1!?!?! > Date: Fri, 02 Aug 2002 12:53:01 -0500 > > > On Fri, 02 Aug 2002 10:47:31 CDT Homer Parker wrote: > > > On Thu, 01 Aug 2002 18:45:36 -0300 Samuel Abreu > > <[EMAIL PROTECTED]> wrote.... > > > > Begin Quote: > > > > > Using wisp, in AAEON SBC, with one orinoco card, im getting the > > > message: > > > > > > Aug 1 15:34:50 10.50.1.10 kernel: netcs1: Tx error, status 1 > > > (FID=016A) > > > > > > Some times, and the client are saying that theyr network is slow! > > > =/// > > > > > > The FID=XXXX always change... > > > > > > What is that??? =) > > > > > > > If you find an answer, please let me know as well... > I've got two out > > that give those errors, one complains it is slow, the other > doesn't... > > I'm going to be installing a larger antenna on the one > complaining to > > see if that clears up the speed issue.. The one complaining shows a > > 16db connection, the one not complaining shows 33... 16 *should* be > > enough, they're only getting a 128k feed, but.... > > I also have problems with my orinoco cards: > > On my Bering RC2 firewall with Orinoco Silver card with nightly > syslog rotation: > # grep -c "eth5: Tx error, status 1 (FID=" /var/log/syslog > 2187 > > My setup is: > Linux Kernel Card Services 3.1.22 > Vadem VG-469 ISA-to-PCMCIA at port 0x3e2 ofs 0x00 > pcmcia-cs 3.1.33 > Lucent/Orinoco/Agere Silver card: manfid: 0x0156, 0x0002 > orinoco.c, orinoco_cs.c v0.09b > Lucent/Agere firmware version 6.16 (if reported correctly, > might be 8.10) > Using WEP in Ad-Hoc Mode > Communicating with one identical card using firmware v8.10 and > orinoco.c 0.11b with kernel pcmcia drivers in 2.4.19-pre10 > and a second SMC 2632W using the prism2_cs.o module in > wlan-ng 0.1.13. > > I started trying to fix it a few weeks ago, but after making > it worse with new drivers (probably because I botched the > compilation or config), I decided to leave it alone until I > have more time to experiment. > > If you haven't already, you may want to check out the > [EMAIL PROTECTED] archives[1] and the pcmcia-cs > mailing list archives[2]. > > David Gibson, the author of the orinoco drivers, is active on > the former. The postings I have seen give me the impression > that the orinoco.o/orinoco_cs.o driver is not very stable > yet and that Dave is still trying to work out some of the > bugs. IIRC, there is even a fairly long thread between David > and someone working on ARM patches that seems to discuss the > same problem the three of us are having. > > I can't justify moving it up to the top of my priority list > right now, but I would be happy to provide any details you > need from my setup to help you isolate and fix the problem. > Good luck finding a solution and please let us all know if succeed. > > --Brad > > [1] http://lists.samba.org/pipermail/wireless/ > [2] http://sourceforge.net/forum/?group_id=2405
What a strange coincidence! I've been running Bering RC2 for several months now with Lucent Silver cards without any problems. I recently built a similar box for a friend who has two wireless clients in his house and immediate neighborhood. The ones in the house have been working fine (the box has not been rebooted since it went in a month ago) and I finally got around to dealing with the more distant client last night, using external antennas at the Bering box and remote client. I established a path with my laptop and an antenna, then spent some time getting a Raylink PCI-PCMCIA adapter to go in the intended client. (if anyone cares, the windows driver in '98 is broken - you need the raylink version installed before the card goes in and Windows tries to install its own!) This card uses the TI chipset (1211?) and has been used in a Bering box previously without issue. The path is reasonable, given that I've used far worse on really long hops! Orinoco was reporting an 11mbit connection, sometimes dropping to 5.5 in one direction only. When I finally got the client up and running, the connection looked good - nice and fast to his msn.com home page (not my first choice for a home page, but who am I to judge ;-). But after that, the performance dropped through the floor. The same errors you guys have reported showed up on the Bering box. However, swapping the wireless card and using the same antenna, my laptop could surf just fine, using either Linux or Win98! I don't know how, or even if it's possible, but it seems like the client is causing the error. All the cards involved have been upgraded to 8.10. With two completely separate installs, I have never seen this error until last night, with this latest machine. It's an Athlon 1400 running Win98SE, with the Raylink PCI-PCMCIA adapter. I also noticed that pinging the client from the Bering box (or the other way for that matter) resulted in packet losses of 10-15%. I didn't have time to try this with my laptop at the same location to compare (I'm kicking myself now!). I won't be able to go back and poke around again for about a week unfortunately. As it was an entirely unexpected problem, discovered when I should really have been asleep in bed, I'm afraid I didn't trouble shoot it in a really logical way! Does anything I've reported trigger anything with you guys? Brock ------------------------------------------------------- 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
