Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Belkin USB Wireless Dongle
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Sun Mar 04, 2012 9:33 pm    Post subject: Reply with quote

Hello,

this is my first post to the forum, so sorry if I do something wrong.
My specific question is: I have Gentoo installed 3.1-6 and trying to make Belkin f7d2102 n300 wireless adapter work on it.
The adapter in question seems to require rtl8192cu driver, which I also compiled as a module, but it was of no avail.
Then I installed ndiswrapper, installed the manufacturer's *.inf files with its help. Now issuing
Code:
ndiswrapper -l
outputs
Code:
net8192cu : driver installed, device (050d:2103) present
But issuing
Code:
ifconfig -a
or
Code:
lspci
does not somewhow say anything about the belkin card.
Code:
lsusb
does recognize
Code:
"Belkin component"
What should I do now? I'm new to Gentoo.

Thanks!
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Sun Mar 04, 2012 10:02 pm    Post subject: Reply with quote

That thing should work with the kernel rtl8192cu driver. If I were you, I'd try to get that working instead of playing with ndiswrapper.

Just a guess... did you install linux-firmware?
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Sun Mar 04, 2012 10:15 pm    Post subject: Reply with quote

Thanks for your reply. I did emerge linux-firmware just now, there were no errors at least during emerge. Still no luck, modprobing rtl8192cu does load the module, but ifconfig yileds nothing of Belkin....
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 32452
Location: 56N 3W

PostPosted: Sun Mar 04, 2012 10:23 pm    Post subject: Reply with quote

Sigma Kappa,

Welcome to Gentoo.

You have a different wireless dongle to the one in the thread you posted in so your problem deserves its own thread.

ndiswrapper should be your backstop, native kernel dirvers are normally better.

Grepping the kernel source codes for your device ID, produces no relevant hits, so its unlikely ther is a kernel driver.
There may be an out of kernel driver though.

Several sites claim it needs the Realtek RTL8192CU driver, which is worth a try.
Thats Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter in the kernel. MAke it <M> not <*>.
If its built in, it will fail to load the firmware.

It also needs firmware, which is not distributed with the kernel
You can get the firmware with
Code:
emerge sys-kernel/linux-firmware
which will also install it in the right place.

When you load the kernel module, or plug the device in, it should appear in
Code:
ifconfig -a

Setup is covered in the Gentoo handbook
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 32452
Location: 56N 3W

PostPosted: Sun Mar 04, 2012 10:25 pm    Post subject: Reply with quote

Sigma Kappa,

You should see an new network interface in ifconfig -a.
It should be eother ethX or wlanY

IF its not shown, what does dmesg show ?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
BillWho
Veteran
Veteran


Joined: 03 Mar 2012
Posts: 1600
Location: US

PostPosted: Mon Mar 05, 2012 12:41 am    Post subject: did you try udevadm monitor --udev ? Reply with quote

It seems like you did everything right except for using ndiswrapper. As a long shot here is anything recognized in that usb port? Try udevadm monitor --udev and you should get output similar to this.

root@gentoo-ws490 linux # udevadm monitor --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV [1330906648.432669] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8 (usb)
UDEV [1330906648.432968] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0 (usb)
UDEV [1330906648.433804] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy1 (ieee80211)
UDEV [1330906648.434028] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/leds/rt2800usb-phy1::radio (leds)
UDEV [1330906648.434125] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy1/rfkill1 (rfkill)
UDEV [1330906648.434361] change /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/ieee80211/phy1/rfkill1 (rfkill)
UDEV [1330906648.434487] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/leds/rt2800usb-phy1::quality (leds)
UDEV [1330906648.434570] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/leds/rt2800usb-phy1::assoc (leds)
UDEV [1330906648.444152] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan0 (net)
UDEV [1330906648.445091] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan0/queues/rx-0 (queues)
UDEV [1330906648.445120] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan0/queues/tx-1 (queues)
UDEV [1330906648.445136] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan0/queues/tx-2 (queues)
UDEV [1330906648.445151] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan0/queues/tx-0 (queues)
UDEV [1330906648.445280] add /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/net/wlan0/queues/tx-3 (queues)

Also use ifconfig -a when checking for wlan0. When I hot-plugged this device it didn't show with plain ifconcig. It won't connect yet, but it should show.

Another thing is what are you using for the wireless manager, wicd, networkmanager or wpa_supplicant. I used wpa_supplicant as it was stated as the preferred.

One last thought here is there any files(s) that you might need from the cd or the manufacturers web site? I had to copy RT2870STA.dat to /etc/Wireless/RT2870STA/RT2870STA.dat. This threw me for a few hours when setting mine up the other day. I didn't thing it was necessary, but apparently it was the last piece of the puzzle. Once copied over restarting net.wlan0 it kicked right up. This is the one that I installed http://www.newegg.com/Product/Product.aspx?Item=N82E16833320040&Tpk=Asus%20USB-N13

Good Luck :wink:
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 6:46 am    Post subject: Reply with quote

Code:

[  118.740458] usb 1-4: default language 0x0409
[  118.741094] usb 1-4: udev 5, busnum 1, minor = 4
[  118.741100] usb 1-4: New USB device found, idVendor=050d, idProduct=2103
[  118.741106] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  118.741112] usb 1-4: Product: Belkin Wireless Adapter
[  118.741116] usb 1-4: Manufacturer: Realtek
[  118.741120] usb 1-4: SerialNumber: 00e04c000001
[  118.741232] usb 1-4: usb_probe_device
[  118.741237] usb 1-4: configuration #1 chosen from 1 choice
[  118.741824] usb 1-4: adding 1-4:1.0 (config #1, interface 0)
[  118.741938] drivers/usb/core/inode.c: creating file '005'

Included only the relevant part of dmesg. RTL modules were indeed the <M> ones -- I have to modprobe them in order to see in lsmod. firmware was emerged successfully. udev just hangs -- not output at all. And ifconfig -a doesn't show the Belkin thing. All it shows is eth0 and wlan0, which are the network card and the native wlan card (now dead, that's another story).

Thanks again.
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Mon Mar 05, 2012 9:22 am    Post subject: Reply with quote

Are you sure wlan0 is the dead native card? It could be if you still have modules for it, which would make me ask why?

And post the full dmesg. Not directly here, use pastebin.
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 10:20 am    Post subject: Reply with quote

Yes, quite sure wlan0 is the dead card -- "ifconfig wlan0 up" yields "<...>due to RF-Kill", and we found out that the native wlan thing has burnt out.
Aha, so I need to recompile the kernel without the support for the native but now useless one? Makes perfect sense. I'll post the complete dmesg after
recompiling the kernel.
Back to top
View user's profile Send private message
BillWho
Veteran
Veteran


Joined: 03 Mar 2012
Posts: 1600
Location: US

PostPosted: Mon Mar 05, 2012 2:12 pm    Post subject: Reply with quote

Sigma Kappa wrote:
Code:


udev just hangs -- not output at all. And ifconfig -a doesn't show the Belkin thing.


What you need to do is plug the dongle in or remove it and plug it back in to get output from udevadm.

As far as the modules loading, /etc/init.d/net.lo will take care of that in the _load_modules() function.

Have you setup the symlink for net.wlan0 or net.wlan1 if you already have a built in and added it to the default runlevel ? You can check /etc/runlevels/default or just enter rc-update.
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 5:24 pm    Post subject: Reply with quote

dmesg's output is here. net.wlan0 is pointing to net.lo. Now I compiled the kernel without the dead card's Atheros drivers, now ifconfig -a doesn't show even that. udev's output:
Code:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [1330968238.108465] remove   /devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0 (usb)
UDEV  [1330968238.109331] remove   /devices/pci0000:00/0000:00:12.2/usb1/1-3 (usb)
UDEV  [1330968243.047891] add      /devices/pci0000:00/0000:00:12.2/usb1/1-3 (usb)
UDEV  [1330968243.050022] add      /devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0 (usb)
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Mon Mar 05, 2012 5:49 pm    Post subject: Reply with quote

Is that the full dmesg? After plugging in the device? It shows that the driver does not react at all.

Oh, I see it now. I checked for id 2103 in my kernel tree, but I have 3.3-rc here!

One idea. After you've loaded the module, run this as root:
Code:
echo -n "050d 2103" > /sys/bus/usb/drivers/rtl8192cu/new_id

If it doesn't work, you'll need to upgrade to the 3.3-rc kernel.

And something else... are you completely sure the Atheros card is dead and not just having it's radio turned off? That rf-kill message says exactly that - the radio is off.


Last edited by Gusar on Mon Mar 05, 2012 5:59 pm; edited 1 time in total
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 5:59 pm    Post subject: Reply with quote

After issuing the echo thing the terminal doesn't even react to Ctrl+C :) So do I go for upgrade? My kernel is 3.1-6.
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Mon Mar 05, 2012 6:02 pm    Post subject: Reply with quote

Yeah, upgrade to at least 3.2, then maybe the command will work. But with 3.3-rc6 it should work without any special commands.

And in case you didn't see it, I edited my previous post as you were writing your reply, added a question.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 32452
Location: 56N 3W

PostPosted: Mon Mar 05, 2012 6:29 pm    Post subject: Reply with quote

Sigma Kappa,

Sigma Kappa wrote:
ifconfig wlan0 up" yields "<...>due to RF-Kill

Means that the wifi card radio transmitter is switched off - either by a hardware switch on your PC or by a software controlled switch.
If you want to investigate that, your need RF Kill Support in your kernel and the rfkill package. Oh, and you need your Atheros drivers again.

Your dmesg shows
Code:
[  296.417323] usbcore: registered new interface driver rtl8192cu
and it looks like that was due to you modprobing the kernel module.

You have
Code:
 [    0.201044] usbcore: registered new interface driver usbfs
which helps debug. Plug in your USB wifi dongle then post the content of /proc/bus/usb/devices
This will show your entire USB device tree.

Plugging in the dongle should also be shown in dmesg as the USB system reacta to the event, something like
Code:
[ 3259.192087] usb 2-4: new high speed USB device number 3 using ehci_hcd
[ 3259.668103] usb 2-4: reset high speed USB device number 3 using ehci_hcd
[ 3260.130726] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 3260.131094] Registered led device: rt73usb-phy0::radio
[ 3260.131129] Registered led device: rt73usb-phy0::assoc
[ 3260.131162] Registered led device: rt73usb-phy0::quality
[ 3260.132294] usbcore: registered new interface driver rt73usb
[ 3260.248282] udevd[2813]: renamed network interface wlan0 to wlan1
Thats a different device to your own but te USB subsystem goes through the same steps.

Your device will eventually show up as wlan1, not wlan0 too as the system will remember the dead device by its MAC address.
You either need to fix that by deleting the entry from /etc/udev/rules.d/70-persistent-net.rules or live with it and create a /etc/init.d/net.wlan1 symlink.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 6:35 pm    Post subject: Reply with quote

As the the native card: we checked it with Ubuntu live CD, and it didn't react to that. The button is showing red, on it was working it would show blue. So not sure about some internal thing flipped off... As to the kernel update, mine was gentoo-sources, have to go for git-sources-3.3_rc6 it seems.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 32452
Location: 56N 3W

PostPosted: Mon Mar 05, 2012 6:45 pm    Post subject: Reply with quote

Sigma Kappa,

What about the other stuff I asked for?

gentoo-sources should be fine.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 6:47 pm    Post subject: Reply with quote

As to the rfkill package, I remember doing that, the result was "hard blocked" or something... Now the USB dongle: /proc/usb/bus/devices, and dmesg's output.
gentoo-sources: issuing eselect ernel list shows only gentoo-3.1-6, not 3.3.
I also did
Code:
ln -s /etc/init.d/net.lo /etc/init.d/net.wlan1, rc-update add net.wlan1 default


Last edited by Sigma Kappa on Mon Mar 05, 2012 7:08 pm; edited 1 time in total
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Mon Mar 05, 2012 7:07 pm    Post subject: Reply with quote

Sigma Kappa wrote:
As to the rfkill package, I remember doing that, the result was "hard blocked" or something...

Yep, that means exactly what it says - hard blocked. The laptop must have a physical switch or a keyboard combination for the wifi. Flick that, check again with "rfkill list".

For the Belkin dongle, you'll need to upgrade the kernel, there's no other way. If eselect doesn't work, just manually adjust the /usr/src/linux symlink to point to the 3.3-rc6 source.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 32452
Location: 56N 3W

PostPosted: Mon Mar 05, 2012 7:36 pm    Post subject: Reply with quote

Sigma Kappa,

Your USB dongle as connected, shares an EHCI root hub with your webcam.
Your webcam and the usb dongle both need 500mA each but the root hub is only allowed to provide 500mA total.
It may well have shut down because of the overcurrent condition.

The overcurrent condition may reset if you unplug both devices or it may take a power off cycle.

Try again without your webcam connected or split your devices between the two EHCI root hubs.

If you want to see exactly what I'm looking at
Code:
emerge usbview


usbview:
Belkin Wireless Adapter
Manufacturer: Realtek
...
   MaxPower Needed: 500mA

hp webcam
Manufacturer: KYE Systems
...
   MaxPower Needed: 500mA


Note a few netbooks/laptops do not implement overload protection on their USB ports.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 7:44 pm    Post subject: Reply with quote

Honestly and truly hp webcam is built-in, so it is not using USB port. And yes, I tried usbview and it shows hp webcam and Belkin in Red. Now how to switch the webcam off? EHCI thing doesn't ring a bell, sorry... And one more thing: how do I point to 3.3_rc6?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 32452
Location: 56N 3W

PostPosted: Mon Mar 05, 2012 7:56 pm    Post subject: Reply with quote

Sigma Kappa,

The HP Webcam is using USB - even if its internal and its on one of your USB EHCI root hubs.
The red means that no loaded driver has claimed the device but as I say, that may be because of the overcurrent condition.

Try each USB port in turn and see if you can separate the dongle and webcam. If not, its very likely that your system does not follow the USB standard for supplying power to peripherial devices.

To point to 3.3_rc6 go into the /usr/src directory.
Remove the linux symbolic link
Make a new link with
Code:
ln -s <real_name> linux
where <real_name> is the name of the directory holding 3.3_rc6
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Mon Mar 05, 2012 8:01 pm    Post subject: Reply with quote

Sigma Kappa wrote:
Honestly and truly hp webcam is built-in, so it is not using USB port.

It is. Even built-in devices are connected to a bus. They have to be, how else are they going to communicate to the rest of the machine. The webcam is usually connected to the usb bus.

Sigma Kappa wrote:
how do I point to 3.3_rc6?

Symlink creation is one of the basics of using the commandline. It's something you should figure out on your own. In general it's
Code:
ln -s target name
where "target" is what you want the symlink to point to and "name" is the name of the symlink. In this case, you need a "linux -> linux-3.3-rc6" symlink.
Back to top
View user's profile Send private message
Sigma Kappa
n00b
n00b


Joined: 04 Mar 2012
Posts: 45

PostPosted: Mon Mar 05, 2012 8:07 pm    Post subject: Reply with quote

Thank you, fellows. About symlink my actual question was where do I get the *full* name of 3.3_rc6 in the first place, because all the how-tos work on gentoo-source :) And I seemed to have succeeded to separate the two: now only the webcam is red, but no wifi still... So the next recursion level is to upgrade the kernel... OK, will go for it.
Back to top
View user's profile Send private message
BillWho
Veteran
Veteran


Joined: 03 Mar 2012
Posts: 1600
Location: US

PostPosted: Mon Mar 05, 2012 8:31 pm    Post subject: Reply with quote

equery l -p sys-kernel/git-sources or eix sys-kernel/git-sources will show you the list of available sources. Since you're interested in 3.3_rc6 simply emerge sys-kernel/git-sources and you'll get the latest which is 3.3_rc6
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum