You are not logged in.

#1 2012-10-01 13:28:23

Syl
Member
Registered: 2009-06-24
Posts: 34

[Solved] USB Wireless Adapter issue

Hello All,

Background : I'm in (my very first) installation process of Arch. I do not have an easy access to wire ethernet connection (need to bother my neighbour). I could install the core system (via ethernet), and now I'm stock to this point since yesterday : 3.9 Configure the network / 3.9.2 Wireless (https://wiki.archlinux.org/index.php/Be … Wireless_2). I'm writing this from another computer.
edit: even tough I'm in the installation process, as this is an network issue, I posted it here.

USB Wifi Adapter : D-Link DWA-160 A2

Current situation :
lsusb can see the device

#lsusb
Bus 001 Device 003: ID 2001*3c1a D-Link Corp.

Carl9170-fw was installed (removed and reinstalled again) (https://aur.archlinux.org/packages.php?ID=44102)

#pacman -Qm
carl9170-fw 1.9.6-1

https://wiki.archlinux.org/index.php/Wi … p#carl9170

wiki.archlinux.org wrote:

carl9170 is the 802.11n USB driver with GPLv2 firmware for Atheros USB AR9170 devices. It supports these devices. The firmware is not yet part of the linux-firmware package; it is available in the AUR (carl9170-fw). The driver is a part of the Linux kernel v2.6.37 and higher.
In order to use this driver, the following older driver modules must be blacklisted: arusb_lnx ar9170usb

I understand that the driver is already included in the kernel (and therefore it does need to be installed), nevertheless the firmware has to be installed (done).
I did blacklisted these 2 modules.
I did rmmod theme as well.

Now, I resume that I resume the installation (restart of the computer and mounting the partition + arch-chroot). If got the following results:

#rmmod arusb_lnx
Error: Module arusb_lnx is not currently loaded
#rmmod ar9170usb
Error: Module ar9170usb is not currently loaded
#modproble -r arusb_lnx
#modproble -r ar9170usb


I don't understand the following. It's link the system does not see the module:

#modinfo carl9170
ERROR: Module alias carl9170 not found
#lsmod | grep carl

But for another module (fan in the example), it gives me the following result:

#lsmod | grep fan
fan              2426  0
#modinfo fan
ERROR: Module alias fan not found

For me it is illogical, it is because I'm still in the installation process?


iwconfig and ip link do not see any wireless adapter:

#iwconfig
eth0     no wireless extensions.
lo         no wireless extensions.
#ip link
1:  lo: (..........................)
2.  eth0:  (.................)

I did remove and add again carl9170 module, but it does not work:

#rmmod carl9170
Error: Module carl9170 is not currently loaded
#modprobe -r carl9170
#modprobe carl9170
#iwconfig
eth0     no wireless extensions.
lo         no wireless extensions.



I do not know what to do from here.
If I cannot get this adapter working, I have few days for change it.

Many thanks for your help :-)

Last edited by Syl (2012-10-11 12:57:38)


広島のお好み焼きおたくです

Offline

#2 2012-10-01 19:34:16

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: [Solved] USB Wireless Adapter issue

What you do is correct, but I am not sure you have the correct driver.
Here, modinfo ar9170 gives

$ modinfo carl9170
filename:       /lib/modules/3.5.4-1-ARCH/kernel/drivers/net/wireless/ath/carl9170/carl9170.ko.gz
alias:          arusb_lnx
alias:          ar9170usb
firmware:       carl9170-1.fw
description:    Atheros AR9170 802.11n USB wireless
license:        GPL
author:         Christian Lamparter <chunkeey@googlemail.com>
author:         Johannes Berg <johannes@sipsolutions.net>
version:        1:1.9.4
srcversion:     0AC1E2F4DC92028880C3283
alias:          usb:v1B75p9170d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1668p1200d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v057Cp8402d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v057Cp8401d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0409p02B4d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0409p0249d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v04BBp093Fd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v2019p5304d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083ApF522d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CDEp0027d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CDEp0026d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CDEp0023d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0586p3417d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1435p0326d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1435p0804d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0ACEp1221d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0846p9001d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0846p9010d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0846p9040d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3A0Fd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3A09d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C10d*dc*dsc*dp*ic*isc*ip*
alias:          usb:vCACEp0300d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CF3p1011d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CF3p1010d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CF3p1002d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CF3p1001d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0CF3p9170d*dc*dsc*dp*ic*isc*ip*
depends:        usbcore,mac80211,ath,cfg80211
intree:         Y
vermagic:       3.5.4-1-ARCH SMP preempt mod_unload modversions 686 
parm:           nohwcrypt:Disable hardware crypto offload. (bool)
parm:           noht:Disable MPDU aggregation. (int)

One thing you will note, is that the device ID you quote is not listed as alias. (It is also not on the linuxwireless page for D-Link/carl9170)
A google on it then brings me this: http://bernaerts.dyndns.org/linux/229-u … a160-revb2
where that device ID is listed and linked to a totally different driver ..

Maybe your device is DWA160-rev B2 and not DWA160-rev A2?

I don't know about your modinfo problem, must be due to the installation still.
Btw, "rmmod" and "modprobe -r" do the same thing (only one needed) -  the latter is preferred.

Offline

#3 2012-10-03 14:06:00

Syl
Member
Registered: 2009-06-24
Posts: 34

Re: [Solved] USB Wireless Adapter issue

Thanks a lot Strike0!
Indeed, my adapter is version B2 and not A2.
I did not notice it, since the website where I bought it said it is version A2 ....

So I'll try to install the firmware and driver from Ralink, as explained in the article you posted.

I'll keep you updated.

Greet help, cheers !

:-)


広島のお好み焼きおたくです

Offline

#4 2012-10-05 08:44:17

Syl
Member
Registered: 2009-06-24
Posts: 34

Re: [Solved] USB Wireless Adapter issue

Hello,

I could install the firmware and driver as explained in the above link.
Straight away, the wifi adapter was working ;-)
Thanks a lot.


I have now a problem to get the connection working fine at start up.

My conf is quite basic I assume:

# more /etc/network.d/ra0-NEUF_A520
CONNECTION='wireless'
DESCRIPTION='Automatically generated profile by wifi-menu'
INTERFACE='ra0'
SECURITY='wpa'
ESSID=NEUF_A520
IP='dhcp'
KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxx



# more /etc/rc.conf
DAEMONS=(syslog-ng network crond net-auto-wireless)



# more /etc/network.d/interfacesra0
### https://bbs.archlinux.org/viewtopic.php?pid=940669
WPA_DRIVER='wext'


Here are the dhcpd logs at startup;

###  At start up

Oct  5 10:15:50 purelight dhcpcd[325]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:15:50 purelight dhcpcd[325]: ra0: rebinding lease of 
192.168.1.88
Oct  5 10:15:51 purelight dhcpcd[325]: eth0: waiting for carrier
Oct  5 10:15:54 purelight dhcpcd[325]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:15:55 purelight dhcpcd[325]: ra0: broadcasting for a lease
Oct  5 10:15:58 purelight dhcpcd[325]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:16:02 purelight dhcpcd[325]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:16:02 purelight dhcpcd[325]: ra0: no IPv6 Routers available
Oct  5 10:16:20 purelight dhcpcd[325]: forked to background, child pid 
351
Oct  5 10:16:21 purelight dhcpcd[351]: ra0: carrier lost
Oct  5 10:16:21 purelight wpa_actiond[474]: Starting wpa_actiond session 
for interface 'ra0'
Oct  5 10:16:26 purelight kernel: [   41.723372] ===>rt_ioctl_giwscan. 
3(3) BSS returned, data->length = 531
Oct  5 10:16:26 purelight kernel: [   41.723679] 
==>rt_ioctl_siwfreq::SIOCSIWFREQ(Channel=11)
Oct  5 10:16:27 purelight dhcpcd[351]: ra0: carrier acquired
Oct  5 10:16:27 purelight wpa_actiond[474]: Interface 'ra0' connected to 
network 'NEUF_A520'
Oct  5 10:16:27 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:16:27 purelight dhcpcd[351]: ra0: rebinding lease of 
192.168.1.88
Oct  5 10:16:27 purelight dhcpcd[351]: ra0: NAK: address in use from 
192.168.1.1
Oct  5 10:16:27 purelight dhcpcd[513]: sending commands to master dhcpcd 
process
Oct  5 10:16:27 purelight dhcpcd[351]: control command: dhcpcd[513]: 
sending commands to master dhcpcd process
dhcpcd -qL -t 10 -K ra0
Oct  5 10:16:28 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:16:28 purelight dhcpcd[351]: ra0: broadcasting for a lease
Oct  5 10:16:32 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:16:36 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:16:40 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:16:40 purelight dhcpcd[351]: ra0: no IPv6 Routers available



Then, I have to remove and add again the driver to get it working:

#### put the interface down
# ip link set ra0 down
Oct  5 10:28:59 purelight kernel: [  793.852286] ERROR!!! RTMPSetTimer 
failed, Halt in Progress!
Oct  5 10:28:59 purelight kernel: [  793.928032] ---> 
RTMPFreeTxRxRingMemory
Oct  5 10:28:59 purelight kernel: [  793.928068] <--- 
RTMPFreeTxRxRingMemory
Oct  5 10:28:59 purelight dhcpcd[351]: ra0: carrier lost
####  unload the driver
# modprobe -r rt5572sta
Oct  5 10:30:42 purelight dhcpcd[351]: ra0: removing interface
Oct  5 10:30:42 purelight kernel: [  897.656693] rtusb exit --->
Oct  5 10:30:42 purelight kernel: [  897.656701] rtusb_exit():retval of 
get module mutex=0!
Oct  5 10:30:42 purelight kernel: [  897.656705] usbcore: deregistering 
interface driver rt2870
Oct  5 10:30:42 purelight kernel: [  897.656731] rtusb_disconnect: 
unregister usbnet usb-0000:00:1d.7-2
Oct  5 10:30:42 purelight kernel: [  897.656736] RtmpOSNetDevDetach(): 
RtmpOSNetDeviceDetach(), dev->name=ra0!
Oct  5 10:30:42 purelight kernel: [  897.673377]  RTUSB disconnect 
successfully
Oct  5 10:30:42 purelight kernel: [  897.673426] <--- rtusb exit
###  load the driver again
# modprobe rt5572sta
Oct  5 10:31:28 purelight kernel: [  943.752106] rtusb init rt2870 --->
Oct  5 10:31:28 purelight kernel: [  943.752369] 
Oct  5 10:31:28 purelight kernel: [  943.752369] 
Oct  5 10:31:28 purelight kernel: [  943.752369] === pAd = 
ffffc90010d01000, size = 596832 ===
Oct  5 10:31:28 purelight kernel: [  943.752369] 
Oct  5 10:31:28 purelight kernel: [  943.752446] <-- 
RTMPAllocAdapterBlock, Status=0
Oct  5 10:31:28 purelight kernel: [  943.752775] NVM is EFUSE
Oct  5 10:31:28 purelight kernel: [  943.753240] usbcore: registered new 
interface driver rt2870
Oct  5 10:31:28 purelight kernel: [  943.754410] RtmpAsicLoadFirmware: 
ver 21/21, sum cdf7/cdf7, mac cdf72100
Oct  5 10:31:28 purelight kernel: [  943.754592] NICLoadFirmware: 
firmware loaded already
Oct  5 10:31:28 purelight kernel: [  943.760784] <-- 
RTMPAllocTxRxRingMemory, Status=0
Oct  5 10:31:28 purelight kernel: [  943.761102] RTMP_TimerListAdd: add 
timer obj ffffc90010d4ac88!
Oct  5 10:31:28 purelight kernel: [  943.761109] RTMP_TimerListAdd: add 
timer obj ffffc90010d4ad00!
Oct  5 10:31:28 purelight kernel: [  943.761112] RTMP_TimerListAdd: add 
timer obj ffffc90010d4ad78!
Oct  5 10:31:28 purelight kernel: [  943.761115] RTMP_TimerListAdd: add 
timer obj ffffc90010d4ac10!
Oct  5 10:31:28 purelight kernel: [  943.761118] RTMP_TimerListAdd: add 
timer obj ffffc90010d4aaa8!
Oct  5 10:31:28 purelight kernel: [  943.761121] RTMP_TimerListAdd: add 
timer obj ffffc90010d4ab20!
Oct  5 10:31:28 purelight kernel: [  943.761124] RTMP_TimerListAdd: add 
timer obj ffffc90010d14b90!
Oct  5 10:31:28 purelight kernel: [  943.761127] RTMP_TimerListAdd: add 
timer obj ffffc90010d03a00!
Oct  5 10:31:28 purelight kernel: [  943.761130] RTMP_TimerListAdd: add 
timer obj ffffc90010d03a80!
Oct  5 10:31:28 purelight kernel: [  943.761133] RTMP_TimerListAdd: add 
timer obj ffffc90010d14d20!
Oct  5 10:31:28 purelight kernel: [  943.761136] RTMP_TimerListAdd: add 
timer obj ffffc90010d14aa0!
Oct  5 10:31:28 purelight kernel: [  943.761140] RTMP_TimerListAdd: add 
timer obj ffffc90010d14ca0!
Oct  5 10:31:28 purelight kernel: [  943.762777] -->RTUSBVenderReset
Oct  5 10:31:28 purelight kernel: [  943.762903] <--RTUSBVenderReset
Oct  5 10:31:29 purelight kernel: [  943.997667] BBP_R254 = 80
Oct  5 10:31:29 purelight kernel: [  944.193843] Key1Str is Invalid key 
length(0) or Type(0)
Oct  5 10:31:29 purelight kernel: [  944.193867] Key2Str is Invalid key 
length(0) or Type(0)
Oct  5 10:31:29 purelight kernel: [  944.193889] Key3Str is Invalid key 
length(0) or Type(0)
Oct  5 10:31:29 purelight kernel: [  944.193911] Key4Str is Invalid key 
length(0) or Type(0)
Oct  5 10:31:29 purelight kernel: [  944.194331] 1. Phy Mode = 5
Oct  5 10:31:29 purelight kernel: [  944.194334] 2. Phy Mode = 5
Oct  5 10:31:29 purelight kernel: [  944.194337] NVM is Efuse and its 
size =3c[3c0-3fb] 
Oct  5 10:31:29 purelight kernel: [  944.222800] Power = 1011
Oct  5 10:31:29 purelight kernel: [  944.222804] Power2 = 1212
Oct  5 10:31:29 purelight kernel: [  944.224176] Power = f10
Oct  5 10:31:29 purelight kernel: [  944.224182] Power2 = 1112
Oct  5 10:31:29 purelight kernel: [  944.225547] Power = e0f
Oct  5 10:31:29 purelight kernel: [  944.225551] Power2 = 1111
Oct  5 10:31:29 purelight kernel: [  944.226800] Power = d0e
Oct  5 10:31:29 purelight kernel: [  944.226804] Power2 = 1011
Oct  5 10:31:29 purelight kernel: [  944.228174] Power = c0c
Oct  5 10:31:29 purelight kernel: [  944.228179] Power2 = 1010
Oct  5 10:31:29 purelight kernel: [  944.229422] Power = b0b
Oct  5 10:31:29 purelight kernel: [  944.229426] Power2 = f10
Oct  5 10:31:29 purelight kernel: [  944.283302] 3. Phy Mode = 5
Oct  5 10:31:29 purelight kernel: [  944.283309] AntCfgInit: 
primary/secondary ant 0/1
Oct  5 10:31:29 purelight kernel: [  944.283309] bAutoTxAgcG = 1
Oct  5 10:31:29 purelight kernel: [  944.315928] ---> 
InitFrequencyCalibration
Oct  5 10:31:29 purelight kernel: [  944.318055] 
InitFrequencyCalibration: frequency offset in the EEPROM = 18
Oct  5 10:31:29 purelight kernel: [  944.318060] <--- 
InitFrequencyCalibration
Oct  5 10:31:29 purelight kernel: [  944.318080] RTMPSetPhyMode: channel 
is out of range, use first channel=1 
Oct  5 10:31:29 purelight kernel: [  944.321928] MCS Set = ff ff 00 00 
01
Oct  5 10:31:29 purelight kernel: [  944.332585] <==== rt28xx_init, 
Status=0
Oct  5 10:31:29 purelight kernel: [  944.334055] 0x1300 = 00064300
Oct  5 10:31:29 purelight dhcpcd[351]: ra0: waiting for carrier
Oct  5 10:31:29 purelight dhcpcd[351]: ra0: carrier acquired
Oct  5 10:31:29 purelight dhcpcd[351]: ra0: carrier lost
Oct  5 10:31:29 purelight dhcpcd[351]: ra0: waiting for carrier
Oct  5 10:31:35 purelight kernel: [  950.805296] ===>rt_ioctl_giwscan. 
3(3) BSS returned, data->length = 531
Oct  5 10:31:35 purelight kernel: [  950.805490] 
==>rt_ioctl_siwfreq::SIOCSIWFREQ(Channel=11)
Oct  5 10:31:36 purelight dhcpcd[351]: ra0: carrier acquired
Oct  5 10:31:36 purelight wpa_actiond[474]: Interface 'ra0' connected to 
network 'NEUF_A520'
Oct  5 10:31:36 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:31:36 purelight dhcpcd[351]: ra0: broadcasting for a lease
Oct  5 10:31:36 purelight dhcpcd[680]: sending commands to master dhcpcd 
process
Oct  5 10:31:36 purelight dhcpcd[351]: control command: dhcpcd[680]: 
sending commands to master dhcpcd process
Oct  5 10:31:36 purelight dhcpcd[351]: control command: dhcpcd -qL -t 10 
-K ra0
Oct  5 10:31:36 purelight dhcpcd[351]: ra0: offered 192.168.1.88 from 
192.168.1.1
Oct  5 10:31:36 purelight dhcpcd[351]: ra0: acknowledged 192.168.1.88 
from 192.168.1.1
Oct  5 10:31:36 purelight dhcpcd[351]: ra0: checking for 192.168.1.88
Oct  5 10:31:40 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:31:41 purelight dhcpcd[351]: ra0: leased 192.168.1.88 for 
86400 seconds
Oct  5 10:31:44 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:31:48 purelight dhcpcd[351]: ra0: sending IPv6 Router 
Solicitation
Oct  5 10:31:48 purelight dhcpcd[351]: ra0: no IPv6 Routers available


If i do not unload/reload the driver I have no way to get the wirless connection working, ever though it looks up already at start up.
I've been checking around, but couldn't get to a proper solution.

Thanks for your help.

Last edited by Syl (2012-10-11 12:45:54)


広島のお好み焼きおたくです

Offline

#5 2012-10-05 22:55:14

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: [Solved] USB Wireless Adapter issue

Okay, sounds great ! Definetely not the easiest adapter to setup .. But hey, this time I definetely pass your thanks on the creators of that howto for the chip. Seems brand-new, one would hope Ralink improves the driver soon-ish - looks quite a pita given all those changes.

In any case, glad to read you got it working!
What I don't understand yet is when your auto-connection problem starts.
The first dhcp log looks just fine. Did that not work?
Or is it failing to re-connect after it has been connected?

How I understand it for now you have to reload the driver to re-connect but it works automatically at boot?
Please clarify, thanks.

Two ideas in any case, as I find it likely will be the driver creating the problems:
1. Read up on https://wiki.archlinux.org/index.php/Netcfg
You are basically using it already from the information in the wiki about net-auto-wireless. The netcfg scripts allow you pre-/post-connection hooks/commands. In the worst case you would have to reload the driver in one of those.
2. Check lsmod for wireless drivers that may be conflicting.

Offline

#6 2012-10-06 09:05:07

Syl
Member
Registered: 2009-06-24
Posts: 34

Re: [Solved] USB Wireless Adapter issue

Yes, this adapter is quite a headache... And the creator of this how-to is brillant to get working this driver with all those changes ... most respect!

During the start-up auto-connection I do get an IP address, and there is no error or disconnection that are logged on in /var/log/messages.
But I just noticed that in /var/log/errors I got the following :

Oct  6 11:00:53 purelight dhcpcd[313]: ra0: sendmsg: Cannot assign requested address
Oct  6 11:01:23 purelight dhcpcd[313]: timed out
Oct  6 11:01:23 purelight /usr/sbin/crond[365]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory


if I correlate both logs, it looks like (error ar in bold):

Oct  6 11:00:52 purelight kernel: [    5.787100] 0x1300 = 00064300
Oct  6 11:00:53 purelight dhcpcd[313]: ra0: sending IPv6 Router Solicitation
Oct  6 11:00:53 purelight dhcpcd[313]: ra0: rebinding lease of 192.168.1.88
Oct  6 11:00:53 purelight dhcpcd[313]: eth0: waiting for carrier
[b]Oct  6 11:00:53 purelight dhcpcd[313]: ra0: sendmsg: Cannot assign requested address[/b]
Oct  6 11:00:57 purelight dhcpcd[313]: ra0: sending IPv6 Router Solicitation
Oct  6 11:00:58 purelight dhcpcd[313]: ra0: broadcasting for a lease
Oct  6 11:01:01 purelight dhcpcd[313]: ra0: sending IPv6 Router Solicitation
Oct  6 11:01:05 purelight dhcpcd[313]: ra0: sending IPv6 Router Solicitation
Oct  6 11:01:05 purelight dhcpcd[313]: ra0: no IPv6 Routers available
Oct  6 11:01:23 purelight dhcpcd[313]: forked to background, child pid 339
Oct  6 11:01:23 purelight dhcpcd[339]: ra0: carrier lost
Oct  6 11:01:23 purelight wpa_actiond[460]: Starting wpa_actiond session for interface 'ra0'
[b]Oct  6 11:01:23 purelight dhcpcd[313]: timed out[/b]
Oct  6 11:01:28 purelight kernel: [   41.743328] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 531
Oct  6 11:01:28 purelight kernel: [   41.743702] ==>rt_ioctl_siwfreq::SIOCSIWFREQ(Channel=11)
Oct  6 11:01:29 purelight dhcpcd[339]: ra0: carrier acquired
Oct  6 11:01:29 purelight wpa_actiond[460]: Interface 'ra0' connected to network 'NEUF_A520'
Oct  6 11:01:29 purelight dhcpcd[339]: ra0: sending IPv6 Router Solicitation
Oct  6 11:01:29 purelight dhcpcd[339]: ra0: rebinding lease of 192.168.1.88
Oct  6 11:01:29 purelight dhcpcd[339]: ra0: NAK: address in use from 192.168.1.1
Oct  6 11:01:29 purelight dhcpcd[502]: sending commands to master dhcpcd process
Oct  6 11:01:29 purelight dhcpcd[339]: control command: dhcpcd[502]: sending commands to master dhcpcd process
dhcpcd -qL -t 10 -K ra0
Oct  6 11:01:30 purelight dhcpcd[339]: ra0: sending IPv6 Router Solicitation
Oct  6 11:01:30 purelight dhcpcd[339]: ra0: broadcasting for a lease
Oct  6 11:01:34 purelight dhcpcd[339]: ra0: sending IPv6 Router Solicitation
Oct  6 11:01:38 purelight dhcpcd[339]: ra0: sending IPv6 Router Solicitation
Oct  6 11:01:42 purelight dhcpcd[339]: ra0: sending IPv6 Router Solicitation
Oct  6 11:01:42 purelight dhcpcd[339]: ra0: no IPv6 Routers available

So, to me it looks like that even though there is a dhcp timeout, I do finally get an address ip at the end, and no other particular error. Thus, I assume that at this point the connection should work.

Then, if I straight away ping the internet dhcp server, I got an error (for me, this shows that the connection is actually not working):

#            ping 192.168.1.1
connect: Network is unreachable


Once I put down the interface and unload/reload the driver it's working:

# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=9.79 ms





I do not see any other wireless drivers with lsmod. Just in case, I post the output:

#             lsmod
Module                  Size  Used by
rt5572sta             773693  1 
snd_hda_codec_realtek    59152  1 
snd_hda_intel          25700  0 
snd_hda_codec          97432  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               6300  1 snd_hda_codec
snd_pcm                74926  2 snd_hda_codec,snd_hda_intel
snd_page_alloc          7217  2 snd_pcm,snd_hda_intel
snd_timer              18966  1 snd_pcm
i915                  473038  2 
snd                    60021  6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
video                  11308  1 i915
soundcore               5442  1 snd
i2c_algo_bit            5391  1 i915
drm_kms_helper         32749  1 i915
drm                   220804  3 i915,drm_kms_helper
iTCO_wdt                5989  0 
iTCO_vendor_support     1929  1 iTCO_wdt
microcode              12377  0 
lpc_ich                10545  0 
mfd_core                2833  1 lpc_ich
i2c_i801                8212  0 
ppdev                   5902  0 
parport_pc             30669  0 
intel_agp              11096  1 i915
parport                31395  2 ppdev,parport_pc
i2c_core               20508  5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
acpi_cpufreq            5933  0 
mperf                   1267  1 acpi_cpufreq
intel_gtt              14478  3 i915,intel_agp
coretemp                6006  0 
psmouse                71557  0 
pcspkr                  1899  0 
processor              27015  1 acpi_cpufreq
sky2                   49283  0 
serio_raw               4689  0 
fan                     2426  0 
button                  4502  1 i915
thermal                 7959  0 
evdev                  10266  5 
ext4                  438999  3 
crc16                   1359  1 ext4
jbd2                   78720  1 ext4
mbcache                 5977  1 ext4
hid_generic             1113  0 
usbhid                 36812  0 
hid                    85608  2 hid_generic,usbhid
sd_mod                 29271  5 
pata_acpi               3408  0 
ata_generic             3327  0 
uhci_hcd               23404  0 
ata_piix               23160  4 
libata                167675  3 pata_acpi,ata_generic,ata_piix
scsi_mod              133152  2 libata,sd_mod
ehci_hcd               41058  0 
usbcore               147434  4 uhci_hcd,ehci_hcd,usbhid,rt5572sta
usb_common               954  1 usbcore



I'll check about netcfg.
Thank you very much for your help!

:-)

Last edited by Syl (2012-10-11 12:46:20)


広島のお好み焼きおたくです

Offline

#7 2012-10-06 19:36:02

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: [Solved] USB Wireless Adapter issue

I don't see any conflicting modules either.
The sympton you describe about 192.168.1.1 not being reachable makes the problem clearer.

What happens when you remove the daemons (net-auto-wireless and network - network should not be in there anyway if you use the netcfg scripts) and initiate the connection manually (isee how here) ?
Does that work without unloading the module then or is it the same as with net-auto-wireless?

Also now that you have the module working, check modinfo for any parameters / options it may give you to try out.

Please, when posting long code output use the [ code ] tag, that gives scrollbars on the box so that the threads don't get endless long.

Offline

#8 2012-10-11 12:57:11

Syl
Member
Registered: 2009-06-24
Posts: 34

Re: [Solved] USB Wireless Adapter issue

Alright, so it seems that it was the deamon network which mess up the things around.
After I get off network deamon from /etc/rc.conf, the connection was working correctly during the start-up!!


Thanks a lot for your kindly help Strike   wink


広島のお好み焼きおたくです

Offline

#9 2012-10-12 18:34:01

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: [Solved] USB Wireless Adapter issue

Awesome & your welcome of course. Great you en[ code ]ed the output up there also.

Offline

Board footer

Powered by FluxBB