| View previous topic :: View next topic |
| Author |
Message |
amigabill
n00b
Joined: 05 May 2003
Posts: 59
|
 Posted: Sat Jan 07, 2006 10:35 pm Post subject: Dlink DWL-AG660 help needed |
 |
|
I've got a Dlink DWL-660 wireless-A/G card for PCMCIA slot on my laptop, but am having trouble getting it to work. It's a hardware rev A1 and firmwre rev 1.29 per the label.
I've got the PCMCIA slot enabled now, and lights on the card blink when /etc/init.d/net.ath0 start is attempted, but it fails. I've emerged wirelesstools and madwifi-driver/tools but emerge -s madwifi afterward shows neither of the two madwifi items are installed. lsmod does show
ath_pci 55080 0
ath_rate_onoe 8528 1 ath_pci
wlan 104788 3 ath_pci,ath_rate_onoe
ath_hal 170096 2 ath_pci
are all present.
I've got PCMCIA enabled in kernel using the yenta driver as a module, which lsmod says is also present:
yenta_socket 24268 3
rsrc_nonstatic 11264 1 yenta_socket
pcmcia 34520 2
pcmcia_core 35804 3 yenta_socket,rsrc_nonstatic,pcmcia
and lspci does find this card:
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
Here's my entried for /etc/conf.d/net for my wireless card:
config_ath0=( "192.168.1.19 netmask 255.255.255.0 broadcast 192.168.1.255" )
routes_ath0=(
"default gw 192.168.1.1"
)
and my /etc/conf.d/wireless file settings are
| Code: | essid_ath0="billnet"
channel_ath0="4"
key_billnet="1234-1234-1234-1234-1234-1234-12 enc open"
preferred_aps_ath0=( "billnet" ) |
I've also tried restriced for key_billnet as well as the key alone without enc or anything else. They WEP key value above is of course not my real one. I use WEP as that's all my Windows laptop settings offer.
This gives be the following init.d start error:
| Code: | laptop ~ # /etc/init.d/net.ath0 start
* Starting ath0
* Configuring wireless network for ath0
* ath0 does not support scanning
* You either need to set a preferred_aps list in /etc/conf.d/wireless
* preferred_aps=( "ESSID1" "ESSID2" )
* and set associate_order_ath0="forcepreferred"
* or set associate_order_ath0="forcepreferredonly"
* or hardcode the ESSID to "any" and let the driver find an Access
* Point
* essid_ath0="any"
* or configure defaulting to Ad-Hoc when Managed fails
* adhoc_essid_ath0="WLAN"
* or hardcode the ESSID against the interface (not recommended)
* essid_ath0="ESSID"
* Failed to configure wireless for ath0 !! |
Trying to start it again gives a shorter error each time until reboot:
| Code: | laptop ~ # /etc/init.d/net.ath0 start
* Caching service dependencies ... ok
* Starting ath0
* Configuring wireless network for ath0
* ath0 does not support setting keys
* or the parameter "mac_key_billnet" or "key_billnet" is incorrect
* Failed to configure wireless for ath0 !! |
I have since edited my wireless file to add these, hinted by the initial error output:
| Code: | preferred_aps=( "billnet" )
associate_order_ath0="forcepreferred" |
but that didn't do any good.
I've changed things to allow using ANY SSID, and things got better but it still didn't come up. The card's lights blink quite a bit before error out:
| Code: | laptop init.d # /etc/init.d/net.ath0 start
* Starting ath0
* Configuring wireless network for ath0
* Failed to configure wireless for ath0 !! |
Any ideas? Madwifi's compatibility list says this thing should work... |
|
| Back to top |
|
 |
The_P
Apprentice
Joined: 13 Mar 2004
Posts: 248
|
| Posted: Sun Jan 08, 2006 4:46 pm Post subject: |
|
|
| I have an idea what it could be. Can you please post the output of iwconfig and the version of madwifi driver you have installed. Possibly the version of madwifi driver you have installed is not compatible with the wireless extentions in the kernel. |
|
| Back to top |
|
|
amigabill
n00b
Joined: 05 May 2003
Posts: 59
|
| Posted: Sun Jan 08, 2006 6:49 pm Post subject: |
|
|
| The_P wrote: | | I have an idea what it could be. Can you please post the output of iwconfig and the version of madwifi driver you have installed. Possibly the version of madwifi driver you have installed is not compatible with the wireless extentions in the kernel. |
I've also since discovered the wlan_wep module needs loaded and have done that, but still no usable connection, but it does seem to get a little further with my own router now, when it had previously only connected to some anonymous neighbor's wide-open router and barfed on my WEP attempts for my own.
iwconfig says:
| Code: | laptop bill # iwconfig
lo no wireless extensions.
sit0 no wireless extensions.
eth0 no wireless extensions.
Warning: Driver for device ath0 has been compiled with version 19
of Wireless Extension, while this program supports up to version 17.
Some things may be broken...
ath0 IEEE 802.11g ESSID:"billnet" Nickname:"billnet"
Mode:Managed Frequency:2.427 GHz Access Point: 00:12:17:32:11:F1
Bit Rate:36 Mb/s Tx-Power:50 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:1234-1234-1234-1234-1234-1234-12 Security mode:open
Power Management:off
Link Quality=45/94 Signal level=-50 dBm Noise level=-95 dBm
Rx invalid nwid:3 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0 |
Yes, there is a note about different versions up there. I have gentoo-sources kernel 2.6.14-r5.
And for Madwifi version I assume it is 0.1_pre20051111 the current masked version in portage, but emerge is does say that no version is currently installed for either the driver or the tools. I've got am AMD64 laptop, and have both madwifi items in /etc/portage/package.keywords and /etc/portage/package.unmask both. emerging them does appear to go through the normal process.
Eh, sorry, slight correction to that. esearch madwifi indicates NO version is installed, but emerge -s madwifi DOES show that the current masked 0.1_pre20051111 versions of both driver and tools are currently installed.
On a related topic, I seem to have issues with connecting via wired ethernet when the Dlink card is present. I can ifconfig down/up and get talking to my router again when that happens, but DNS is dead and won't even try to look up names in this state. If I reboot with the Dlink card not plugged in, then DNS works with wires ethernet again. Is there someplace I can learn how to have the two connections coexist a bit more peacefully once the wireless is actually working? |
|
| Back to top |
|
|
The_P
Apprentice
Joined: 13 Mar 2004
Posts: 248
|
| Posted: Sun Jan 08, 2006 8:34 pm Post subject: |
|
|
You have this warning message I thought you have. I can't believe that this are modules compiled from the version of madwifi you said I think they are much older. Do you have reasons to use the hard masked drivers? I'm using 0.1_pre20050420. This are the newest keyworded drivers in portage for my system. I don't know if this is diffrent on your system because I'm using x86 and not amd64.
I said I had this warning too when I wanted to set up my wireless connection but this was a few months ago and the versions where diffrent. I could solve it by using newer madwifi drivers. This means in my case I added net-wireless/madwifi-driver ~x86 to package.keywords.
Is it possible that your /usr/src/linux link isn't pointing to the correct sources? I don't know if this is important but kernel modules are built during installation of madwifi-driver so I think it could be important.
I would rebuild the madwifi driver in the newest keyworded version and then look for the warning. I don't know if your problems have to do with this warning but it could be. |
|
| Back to top |
|
|
cabbagewalker
n00b
Joined: 09 Feb 2004
Posts: 61
Location: Nottingham, UK
|
| Posted: Sun Jan 08, 2006 10:54 pm Post subject: |
|
|
Hello amigabill
| Quote: | ath0 IEEE 802.11g ESSID:"billnet" Nickname:"billnet"
Mode:Managed Frequency:2.427 GHz Access Point: 00:12:17:32:11:F1
|
because the access point has a mac address and isn't blank then it looks as if your laptop is connecting O/K wireless-wise, and it may be your routing which is not correct. What is the output of
|
|
| Back to top |
|
|
amigabill
n00b
Joined: 05 May 2003
Posts: 59
|
| Posted: Mon Jan 09, 2006 1:58 am Post subject: |
|
|
| cabbagewalker wrote: | Hello amigabill
| Quote: | ath0 IEEE 802.11g ESSID:"billnet" Nickname:"billnet"
Mode:Managed Frequency:2.427 GHz Access Point: 00:12:17:32:11:F1
|
because the access point has a mac address and isn't blank then it looks as if your laptop is connecting O/K wireless-wise, and it may be your routing which is not correct. What is the output of
|
OK, I booted with the card removed and wired ethernet plugged in, and started the wireless card later.
| Code: | laptop bill # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 |
| Code: | laptop bill # ifconfig
ath0 Link encap:Ethernet HWaddr 00:0D:88:BE:93:63
inet addr:192.168.1.19 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20d:88ff:febe:9363/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:98 dropped:0 overruns:0 frame:98
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:42 (42.0 b) TX bytes:88 (88.0 b)
Interrupt:177 Memory:ffffc200001e0000-ffffc200001f0000
eth0 Link encap:Ethernet HWaddr 00:11:D8:F1:5A:A4
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:d8ff:fef1:5aa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:789 errors:0 dropped:0 overruns:0 frame:0
TX packets:864 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:505014 (493.1 Kb) TX bytes:139911 (136.6 Kb)
Interrupt:193
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:300 (300.0 b) TX bytes:300 (300.0 b) |
|
|
| Back to top |
|
|
cabbagewalker
n00b
Joined: 09 Feb 2004
Posts: 61
Location: Nottingham, UK
|
| Posted: Wed Jan 11, 2006 9:27 pm Post subject: |
|
|
| Quote: | laptop bill # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
|
To me it looks as if you have two default routes, eth0 and ath0. They may be conflicting. Do a
This should get rid of the eth0 route and leave ath0 with the only default route. |
|
| Back to top |
|
|
|
Networking & Security
