LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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 09-24-2005, 02:59 AM   #1
Mike Davies
Member
 
Registered: Jul 2004
Distribution: Custom Linux 3.1/Busybox. Fedora 19, Raspberry Pi
Posts: 94

Rep: Reputation: 15
Do I need wlan0 ?


I'm having problems getting a PCMCIA wireless card to work, and I'm getting desperate, as Iíve wasted weeks on this.

The system has been built from scratch and consists of Kernel 2.4.31, pcmcia-cs-2.3.7, wireless_tools.28.

I do not have a wlan0 device. Do I really need one ? I think I read somewhere that it was obsolete and eth0 was good enough. If I need a wlan0 device, what are the major minor numbers and what driver do I need ?

Cardmgr sees the card, identifies it, and loads these modules.

# lsmod
Module Size Used by Not tainted
orinoco_cs 4240 1
orinoco 33560 0 [orinoco_cs]
hermes 5444 0 [orinoco_cs orinoco]
ds 6868 2 [orinoco_cs]
i82365 13296 2
pcmcia_core 36512 0 [orinoco_cs ds i82365]

The problem is, that if I try pinging another PC on the network I get errors and the driver resets the link, e.g.

Sep 24 01:08:34 rhobert user.info kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 24 01:08:34 rhobert user.warn kernel: eth0: Tx timeout! ALLOCFID=0129, TXCOMPLFID=0128, EVSTAT=800b
Sep 24 01:08:34 rhobert user.debug kernel: orinoco_lock() called with hw_unavailable (dev=c1ae4800)
Sep 24 01:08:35 rhobert user.info kernel: eth0: New link status: Connected (0001)

Can anyone help me with this ? Please ?

Mike
 
Old 09-24-2005, 10:56 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
No you don't need a wlan0, that is just a convention, not a requirement. Frequently wireless cards are called eth, ath or a few others. Using eth0 should be fine.

From what you've posted, its not clear if you have configured your wireless card or gotten (or assigned) and IP address to it. Could you elaborate on how you try to get your card running?
 
Old 09-24-2005, 01:44 PM   #3
Mike Davies
Member
 
Registered: Jul 2004
Distribution: Custom Linux 3.1/Busybox. Fedora 19, Raspberry Pi
Posts: 94

Original Poster
Rep: Reputation: 15
I have a network thatís up and running, and Iíve just put an access point on it. The network is running on 192.168.1.*, and the access point acts as a bridge into 10.1.10.*

The PCMCIA card is hardwired to be 10.1.10.5.

The access point can see the wireless card as the MAC address of the PCMCIA card appears in the connected stations list. The PCMCIA card can see the access point.

Iím not quite sure what you want to know.

Iím using the standard scripts and config files from pcmcia-cs-2.3.7 and wireless-tools Ė modified slightly so Iíve got hardwired i/p numbers. Cardmgr detects and loads up the drivers OK

Iíve set up a default gateway so that all traffic goes out through eth0

The interface looks a bit like this (after a few pings) Ö

# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:01:36:0D:96:9D
inet addr:10.1.10.5 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:17 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1140 (1.1 KiB)
Interrupt:3 Base address:0x100

# iwconfig eth0
eth0 IEEE 802.11-DS ESSID:"wzynet" Nickname:"rhobert"
Mode:Managed Frequency:2.457 GHz Access Point: 00:40:33:AF:F6:2B
Bit Rate:2 Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry min limit:8 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=92/92 Signal level=5/153 Noise level=117/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Mike
 
Old 09-24-2005, 04:05 PM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
OK, thanks for the added info. There is one bit from your description that bothers me however:


Quote:
Iíve set up a default gateway so that all traffic goes out through eth0
Could you explain how you did this? I don't think that you need to force traffic through any particular interface unless you are running several interfaces.
 
Old 09-25-2005, 06:30 AM   #5
Mike Davies
Member
 
Registered: Jul 2004
Distribution: Custom Linux 3.1/Busybox. Fedora 19, Raspberry Pi
Posts: 94

Original Poster
Rep: Reputation: 15
It's part of /etc/pcmcia/network.opts

I end up with a routing table that looks like...

# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.1.10.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 10.1.10.1 0.0.0.0 UG 1 0 0 eth0
#

Hmmm. I acknowledge there may be a routing problem here, because I don't have a 10.1.10.1 on the network, but unless I'm being stupid, that's not the immediate problem. I'm getting TX errors on the PCMCIA card, that's what I'd like to fix.

Mike
 
Old 09-26-2005, 08:43 AM   #6
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
My knowledge of PCMCIA inner workings is more than a little limited. However I did a bit of googling on the error message "orinoco_lock() called with hw_unavailable" and found a lot of discussions but no solid answers. This message has a link to a PCMCIA how to that might be helpful. I also saw a couple of discussions around various firmware versions. Most had to do with using WPA_supplicant, but still trying some different firmware may be in order.
 
Old 09-26-2005, 02:20 PM   #7
Mike Davies
Member
 
Registered: Jul 2004
Distribution: Custom Linux 3.1/Busybox. Fedora 19, Raspberry Pi
Posts: 94

Original Poster
Rep: Reputation: 15
Thanks for the reply.

In the interlude I've tried the wlan-ng drivers. I still get timeout errors but in a different module.

I think it is time for Plan "Z" - a different PCMCIA card.
 
  


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
what is wlan0:9 ? dlocalized Linux - Wireless Networking 1 07-03-2005 02:57 PM
dhclient wlan0 - wlan0: not found nickleus Linux - Networking 1 05-10-2005 10:06 PM
wlan0 there - but not there? karaite Linux - Wireless Networking 9 11-02-2004 02:38 PM
wlan0 Patbuzz86 Linux - Wireless Networking 8 04-28-2004 03:45 PM
Broadcom wireless with ndiswrapper: ifconfig wlan0 works; ifup wlan0 fails orangechicken Linux - Wireless Networking 2 04-17-2004 06:39 PM


All times are GMT -5. The time now is 10:33 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration