LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 06-25-2003, 10:27 PM   #1
mi6
Member
 
Registered: Jun 2003
Distribution: Fedora 9 64bit, RHEL 4.6
Posts: 96

Rep: Reputation: 15
wireless pci card troubleshooting


I am using an MA311 with the orinoco_pci drivers, version .13e. I am getting alot of this message in my log:

Error -110 writing Tx descriptor to BAP

If I enable 64bit (I haven't tried 128 bit yet) WEP, it will cause the card to "lock" making me rmmod and modprobe the orinoco_pci module. This only happens under heavy use, ie: iso downloading and such. But it happens with or without WEP, it just seems a tad more common with WEP. I will admit that my signal quality isn't the best (24/92) but it does work with "other" OSes just fine

I also tried the wlan-ng drivers but found them harder to install and configure. I had similar results with them as well.

Does anyone know a preferable driver for the MA311? I will try the wlan-ng's if someone has had better luck with them, but for now, I am out of ideas for my wireless net.
 
Old 06-25-2003, 11:42 PM   #2
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Rep: Reputation: 30
I have used wireless nics on linux in the past, and have had a similar problem with the orinoco drivers. They are still very much under active development, and I found that after updating the drivers, problems such as the sudden lockup were solved.

Get the latest stable from here , and your problems may be solved.

Goodluck,
Andrew

Last edited by andrew001; 06-25-2003 at 11:44 PM.
 
Old 06-25-2003, 11:53 PM   #3
mi6
Member
 
Registered: Jun 2003
Distribution: Fedora 9 64bit, RHEL 4.6
Posts: 96

Original Poster
Rep: Reputation: 15
well, at the moment I am using 13e's aren't they the newest?

I switched to wlan-ng's (again) and have been having much better success with them.
 
Old 06-26-2003, 12:12 AM   #4
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 72
The 110 issue has been more or less knocked out with the switch to the .13 series, e is stable, heck that's how I'm typing this. .13b or c I think is what made it into 2.4.21, but compiling the drivers seperately is really clean, there's a link to the source in my links section in my profile.

Cheers,

Finegan
 
Old 06-26-2003, 01:50 PM   #5
mi6
Member
 
Registered: Jun 2003
Distribution: Fedora 9 64bit, RHEL 4.6
Posts: 96

Original Poster
Rep: Reputation: 15
hmm...I wonder why the .13e's don't like me?

So far the only luck I have had is with wlan-ng. I have had them up for 12+ hours and downloaded about 350 MB's. I couldn't download a kernel without the 13e's barfing MAD 110's!

I like the setup of the orinoco_pci better than the way wlan-ng handles it, so I would rather use them. Plus it makes my kernel boot tidier
 
Old 06-26-2003, 02:08 PM   #6
andrew001
Member
 
Registered: Nov 2002
Distribution: Slackware 9.0
Posts: 321

Rep: Reputation: 30
Hey, whatever works the best with your hardware, go for it!
 
Old 06-26-2003, 04:31 PM   #7
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 72
You might want to try the host_ap drivers, they handle ibss and bss (er... ad-hoc and managed), just as well, they USE the kernel api, so "iwconfig" and the like work on them, and when your bored you can config the card up to be an access point.


Cheers,

Finegan
 
Old 06-26-2003, 07:02 PM   #8
mi6
Member
 
Registered: Jun 2003
Distribution: Fedora 9 64bit, RHEL 4.6
Posts: 96

Original Poster
Rep: Reputation: 15
host_ap eh? that truly sounds interesting....I didn't know my card could function as an AP!

thanks
 
Old 07-30-2003, 08:42 AM   #9
ashleyfrazer
LQ Newbie
 
Registered: Feb 2001
Location: London
Distribution: Red Hat Linux 9.0
Posts: 23

Rep: Reputation: 15
Hi
I am having the same problem with the Orinoco drivers in RH9. Can you tell me

1) How to tell which version of the driver is running now?
2) I managed to download the latest 13e version (and by following the instructions compile it etc)
3) tried to download the wlan stuff - but I am running an Athlon kernel and RH9 out of the box. There seems to be a problem with the files (the MD5 doesn't match).


Thanks

Ash

Last edited by ashleyfrazer; 07-30-2003 at 10:49 AM.
 
Old 08-22-2003, 04:48 AM   #10
LinuxRacr
Member
 
Registered: Jun 2002
Distribution: CentOS 5.3
Posts: 50

Rep: Reputation: 15
I'm having this issue now...

This is happening to me now with my Lucent Technologies Orinoco 11Mbit/s SILVER card. Mad -110 errors. I am running Redhat 9. How do I find out what version of the drivers I have?
 
Old 08-24-2003, 11:29 AM   #11
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 72
You're running RH 9, so... kernel 2.4.20, that means version .11b, that's strange though, this error is specific to firmware in the prism series. You have an orinoco... What's the chunk of the command:

dmesg

at the very end, right after you load the card?

Cheers,

Finegan
 
Old 08-26-2003, 10:33 AM   #12
LinuxRacr
Member
 
Registered: Jun 2002
Distribution: CentOS 5.3
Posts: 50

Rep: Reputation: 15
I updated the driver, and the messages are gone. I now have this message:
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument.

Determining IP information for eth1...PING 192.168.2.1 (192.168.2.1)
56(84) bytes of data.

--- 192.168.2.1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3999ms , pipe 3 failed.


1. I still have the 1st error message...

2. It looks like it reached out for some DHCP action while I was at my friend's house (Neither error came up till I accually got home), and remembered the stats. The problem we had while at my friend's house was that we were getting no DNS info. Any idea why?

Would the command: dhcpcd -H be needed in this case? If so, I'll try once I'm near an access point again..

 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
PCI Wireless card johndoe0028 Linux - Wireless Networking 1 11-03-2005 02:51 AM
Wireless PCI Card KF1 Linux - Hardware 1 04-30-2005 07:30 AM
Wireless PCI Card Harriskaver Linux - Wireless Networking 24 04-05-2005 04:18 PM
desktop wireless card (PCI) and wireless router recommendations lobo78 Linux - Wireless Networking 1 04-30-2004 10:27 PM
Wireless Network card DHCP wont get address debugging and troubleshooting help uuplunkeruu Linux - Wireless Networking 2 03-27-2004 04:08 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 07:35 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration