View previous topic :: View next topic |
Author |
Message |
multix Apprentice
Joined: 28 Nov 2004 Posts: 240 Location: Italy
|
Posted: Wed Apr 10, 2013 6:48 pm Post subject: Wireless D-link DWL-G650M |
|
|
Hi,
I cannot et the mentioned card to work with standard kernel stuff. It is the version based on the Atheros chip (there are many 650 variations apparently)
D-Link DWL-G650M
iwconfig -> doesn't show up
dmesg:
[ 134.398115] pcmcia_socket pcmcia_socket1: pccard: CardBus card inserted into slot 1
[ 134.398147] pci 0000:07:00.0: [168c:0020] type 00 class 0x020000
[ 134.398178] pci 0000:07:00.0: reg 10: [mem 0x00000000-0x0001ffff]
[ 134.398289] pci 0000:07:00.0: BAR 0: assigned [mem 0xc8000000-0xc801ffff]
lspci:
07:00.0 Ethernet controller: Atheros Communications Inc. AR5513 802.11abg Wireless NIC (rev 01)
I hope I do not have to mess with ndsiwrapper crap? Reading around the net, this was the case years ago, but apparently some people got it to work without? With the many variations of the card, confusing.
Riccardo _________________ Unix is user friendly. It is only careful selecting its friends. |
|
Back to top |
|
|
dimko Apprentice
Joined: 12 Feb 2006 Posts: 194
|
Posted: Mon Apr 15, 2013 8:11 pm Post subject: got atheros myself |
|
|
Its pretty ancient. But it's off topic...
First of all, use ip utility
ip link - will give you nice output about all network devices available. It is also modern and much more intuitive. I used it for quite a while, hell no I am going back to arp/iwconfig etc.
third of all, show the driver information from lspci. lspci -v - should do the trick.
And no, ndiswrapper is not needed anymore.
And most importantly, please explain WHAT you actually want to do. _________________ Just a user. |
|
Back to top |
|
|
multix Apprentice
Joined: 28 Nov 2004 Posts: 240 Location: Italy
|
Posted: Tue Apr 16, 2013 9:50 pm Post subject: |
|
|
Why do you say old and off-topic? It is about kernel and hardware...
lspci -v[/quote]
Code: | 07:00.0 Ethernet controller: Atheros Communications Inc. AR5513 802.11abg Wireless NIC (rev 01)
Subsystem: D-Link System Inc DWL-G650M Super G MIMO Wireless Notebook Adapter
Flags: medium devsel, IRQ 11
Memory at c8000000 (32-bit, non-prefetchable) [disabled] [size=128K]
Capabilities: [44] Power Management version 2 |
I don't have installed, but is there a reasion ipconfig/iwconfig shouldn't they show it too? _________________ Unix is user friendly. It is only careful selecting its friends. |
|
Back to top |
|
|
dimko Apprentice
Joined: 12 Feb 2006 Posts: 194
|
Posted: Wed Apr 17, 2013 11:18 am Post subject: driver in use? |
|
|
I am sorry, i was sleepy and english is not my first language. Futher more, I suck at communicating Just at pretty much everything...
I did not refer to your problem. I referred to using IPutils package.
Did you cut lspci -v command output? its either line with driver in use is not there, either you don't use the driver...
Should be something like: "driver in use: ath9k" or something similar.
So irrelevant what you use ip or ipconfig or whatever, driver is not loaded, or so it appears to me. _________________ Just a user. |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Wed Apr 17, 2013 3:05 pm Post subject: |
|
|
multix ...
the reason for using more modern tools, like iproute2 (inplace of net-tools) and iw (in place of wireless-tools) is that these tools (at least the latter) work with the more recent cfg80211, iwconfig uses WEXT (wireless extensions) and so unless you have CONFIG_CFG80211_WEXT (the wext compatibilty layer for cfg80211) your interface won't show up in iwconfig's output.
It may be a case that the module isn't loaded/available (in which case you should enable CONFIG_ATH9K in the kernel) but its equally as likely that the module is loaded, but you don't see the interface as iwconfig expects the kernel to be using wireless extentions (or have the compatibility layer, so it seems like it does).
Code: | # awk '/(WEXT|(CFG|NL)80211)/' /usr/src/linux/.config |
So, enable pcmcia, ath9k, cfg80211 (if its not already), the wext compatibility layer (if you want to use wireless-tools, or other applications that still use wext) and rebuild, and install, the kernel.
You would then configure /etc/conf.d/net and wpa_supplicant.conf similar to the following:
/etc/conf.d/net
Code: | modules_<your_device_name>="!plug wpa_supplicant dhcpcd"
wpa_supplicant_<your_device_name>="-Dnl80211 -qq"
wpa_timeout_<your_device_name>="15"
config_<your_device_name>="dhcp"
dhcpcd_<your_device_name>="-t 10" |
/etc/wpa_supplicant/wpa_supplicant.conf
Code: | ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel
update_config=1
network={
ssid="<your_ap_name>"
proto=WPA2
auth_alg=OPEN
key_mgmt=WPA-PSK
group=CCMP TKIP
pairwise=CCMP TKIP
psk=<your_password>
} |
Code: | # ln -s /etc/init.d/net.lo /etc/init.d/net.<your_interface_name>
# rc-update add net.<your_interface_name> <runlevel> |
That should be all thats required for a basic setup using ath9k ...
HTH & best ... khay |
|
Back to top |
|
|
multix Apprentice
Joined: 28 Nov 2004 Posts: 240 Location: Italy
|
Posted: Wed Apr 17, 2013 11:44 pm Post subject: |
|
|
Hi, thanks for the informatin, but it appears that my kernel is arealdy correclty configured?
The wireless configuration, including extensions:
Code: |
awk '/(WEXT|(CFG|NL)80211)/' /usr/src/linux/.config
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_CFG80211=y
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
# CONFIG_CFG80211_DEFAULT_PS is not set
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
|
Code: |
awk '/CONFIG_ATH9K/' /usr/src/linux/.config
CONFIG_ATH9K_HW=y
CONFIG_ATH9K_COMMON=y
# CONFIG_ATH9K_BTCOEX_SUPPORT is not set
CONFIG_ATH9K=y
# CONFIG_ATH9K_PCI is not set
# CONFIG_ATH9K_AHB is not set
# CONFIG_ATH9K_DEBUGFS is not set
CONFIG_ATH9K_RATE_CONTROL=y
# CONFIG_ATH9K_HTC is not set
|
From what you write this should be enough, both for the card as well as for the extensions, right? Or do I need to set other of the ATH9K settings?
Thanks. R _________________ Unix is user friendly. It is only careful selecting its friends. |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Apr 18, 2013 12:37 am Post subject: |
|
|
multix ...
OK, I think I got misdirected by the mention of ath9k, the card isn't, but then I don't see it being listed as supported by ath5k, either. Other AR5513 cards were supported my madwifi but as you say there seems to be many of them. Your best bet is to try the ath5k driver, it is at least 5xxx chipset, still it may not work either.
best ... khay |
|
Back to top |
|
|
|