[solved]! Getting wicd to work with wireless

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

I tried to get wicd working a few weeks ago, but the thread sorta ran out of steam. I have wicd installed, and can modprobe the driver for my wireless, but wicd shows "no wireless networks found," even though iwconfig shows :

wlan0 IEEE 802.11bg Mode:Managed Frequency:2.462 GHz
Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

DONAHUE · Posted: Sun Apr 10, 2011 1:19 am Post subject:

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

I took the liberty of opening a pastebin and copying everything to two different pastebin pages. The first shows output down to the two 'awk' commands.
http://pastebin.com/mGXjyzVU

The second shows the results of trying to get the files using nano. /etc/wpa_supplicant/wpa_supplicant.conf showed an empty file.
http://pastebin.com/bTh1KHnk

I should ad that all of this was done while the computer was connected by ehternet cable.

DONAHUE · Posted: Sun Apr 10, 2011 2:21 am Post subject:

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 050d:7050 Belkin Components F5D7050 Wireless G Adapter v1000/v2000 [Intersil ISL3887]
localhost pottzie # ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132
localhost pottzie # iwlist scan
lo Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Interface doesn't support scanning : Network is down

DONAHUE · Posted: Sun Apr 10, 2011 4:04 am Post subject:

probably you've heard this before, but the kernel is not loading a driver and/or firmware that is correct for the chipset in the dongle.
It looks like you have it built, but let's try: Edit menuconfig to:

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

No change as far as iwlist scan and iwlan0 up.
http://paste.pocoo.org/show/368839/

DONAHUE · Posted: Sun Apr 10, 2011 5:27 am Post subject:

dmesg says firmware problem:

cach0rr0 · Posted: Sun Apr 10, 2011 6:10 am Post subject:

i think part of the issue here may be that there are two drivers in the kernel which support his card, and he has both of them enabled in the kernel

namely, these two:

DONAHUE · Posted: Sun Apr 10, 2011 6:54 am Post subject:

the point of my Sat Apr 09, 2011 11:04 pm was to go straight p54usb isl3887usb. Based on lsusb result: Bus 001 Device 005: ID 050d:7050 Belkin Components F5D7050 Wireless G Adapter v1000/v2000 [Intersil ISL3887]

lets try, tediously so as to see each event:

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

Went with recompiling the kernel as the first step. After rebooting:
localhost pottzie # modprobe -r rt2500usb
FATAL: Module rt2500usb not found.
localhost pottzie # modprobe -r rt73usb
FATAL: Module rt73usb not found.
localhost pottzie # modprobe -r rt2x00usb
FATAL: Module rt2x00usb not found.
localhost pottzie # modprobe -r rt2x00lib
FATAL: Module rt2x00lib not found.
localhost pottzie # modprobe -r p54common
FATAL: Module p54common is in use.
localhost pottzie # modprobe -r p54usb
localhost pottzie # modprobe p54common
localhost pottzie # modprobe p54usb

Going for a reboot and see what else shows up.
Nope, no change. Again, all this was run while connected with the cable.
localhost pottzie # ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:09:79:ab:28
inet addr:10.10.10.110 Bcast:10.10.10.255 Mask:255.255.255.0
inet6 addr: fe80::211:9ff:fe79:ab28/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1265 errors:0 dropped:0 overruns:0 frame:0
TX packets:1169 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1258377 (1.2 MiB) TX bytes:177373 (173.2 KiB)
Interrupt:22 Base address:0x8000

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:400 (400.0 B) TX bytes:400 (400.0 B)

localhost pottzie # ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device
localhost pottzie # iwlist scan
lo Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

DONAHUE · Posted: Sun Apr 10, 2011 5:08 pm Post subject:

FRrom the dmesg:

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

Nope. Stubborn as a mule.
localhost pottzie # mv /lib/firmware/isl3887usb /lib/firmware/isl3887usb.bak
localhost pottzie # mv /lib/firmware/isl3890 /lib/firmware/isl3887usb
localhost pottzie # modprobe -r p54usb
localhost pottzie # modprobe p54usb
localhost pottzie # ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:09:79:ab:28
inet addr:10.10.10.110 Bcast:10.10.10.255 Mask:255.255.255.0
inet6 addr: fe80::211:9ff:fe79:ab28/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:109704 errors:0 dropped:0 overruns:0 frame:0
TX packets:81118 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:152980871 (145.8 MiB) TX bytes:7385483 (7.0 MiB)
Interrupt:22 Base address:0x8000

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:400 (400.0 B) TX bytes:400 (400.0 B)

localhost pottzie # ifconfig up wlan0
SIOCSIFADDR: No such device
up: ERROR while getting interface flags: No such device
localhost pottzie # iwlist scan
lo Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

DONAHUE · Posted: Sun Apr 10, 2011 5:27 pm Post subject:

Next try: a newer, .25 vice .24, firmware individually for your (nominally) chipset.

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

Still stays the same.
localhost pottzie # modprobe -r p54usb
localhost pottzie # modprobe p54usb
localhost pottzie # ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:09:79:ab:28
inet addr:10.10.10.110 Bcast:10.10.10.255 Mask:255.255.255.0
inet6 addr: fe80::211:9ff:fe79:ab28/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:115070 errors:0 dropped:0 overruns:0 frame:0
TX packets:85942 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:158821925 (151.4 MiB) TX bytes:7987233 (7.6 MiB)
Interrupt:22 Base address:0x8000

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:400 (400.0 B) TX bytes:400 (400.0 B)

localhost pottzie # ifconfig up wlan0
SIOCSIFADDR: No such device
up: ERROR while getting interface flags: No such device
localhost pottzie # iwlist scan
lo Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

DONAHUE · Posted: Sun Apr 10, 2011 5:58 pm Post subject:

try a reboot to recycle p54common

this setup seems to be the best chance
_________________
Defund the FCC.

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

After reboot,
" ifconfig up wlan0
SIOCSIFADDR: No such device
up: ERROR while getting interface flags: No such device"

DONAHUE · Posted: Sun Apr 10, 2011 6:18 pm Post subject:

Either Belkin is electronically misidentifying the chipset, or a minor variation has not been picked up by the linux firmware packagers, or I do not know what's up (true).
see if the label on the dongle yields info:[quote] b) Identifying via FCC ID for the device. Most devices using radio frequencies usually have stickers/imprints identifying their rights for use. Most of these stickers/imprints will have FCC ID labelling on it which usually goes by the words "FCC ID: XXXXXXXXXXXX". The FCC has a website for one to enquire more information specifically for that device and this is also where it comes in handy for the alternative platform users whom wants to find out what sort of chipset is inside the device, etc without having to physically pull the device apart/open.

USB owners/users will find such labels on the physical device itself. It is normally a sticker that is on the outside of the physical device rather than the inside. Once the sticker/label has been found you will need to copy that information and enter it in onto FCC website: https://fjallfoss.fcc.gov/oetcf/eas/reports/GenericSearch.cfm . Once the information has been entered in click "submit" and click on "detail" when the site presents a table. If your device has more than one entry in the table, look for the entry that has the words "original equipment" printed on the same line as "detail" and then click on "detail". Upon the next table presented by the site click on "internal photos", this word maybe slightly varied (i.e. shortened, capitalised) but the meaning should be the same. The site will then prompt you a pdf file in which you will need to examine the photos on the various pages and to see which chipset you have. USB second generation owners/users may find their device internal photos denoted as GW3887 printed on the physical chip itself.

Actually the government failed (surprise) to produce a result for a dongle I have. A google for FCC ID NOI W423B however did identify my chipset.
_________________
Defund the FCC.

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

Maybe I need another brand of wireless receiver! I saw that section on the page you linked to, and thought that was going a ways over the top.
Just for kicks, I happen to have three of those Belkins, thanks to Ebay. So I plugged all three in and ran lsusb to see what happens.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 050d:7050 Belkin Components F5D7050 Wireless G Adapter v1000/v2000 [Intersil ISL3887]
Bus 001 Device 004: ID 050d:7050 Belkin Components F5D7050 Wireless G Adapter v1000/v2000 [Intersil ISL3887]
Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 006: ID 050d:705a Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2573]

But ifconfig and ifconfig up wlan0 still show SIOCSIFADDR: No such device

Glad I'm connected by a hardwire.

DONAHUE · Posted: Sun Apr 10, 2011 6:40 pm Post subject:

you can try menuconfig for no prism only ralink drivers instead for the rt2573:

DONAHUE · Posted: Sun Apr 10, 2011 7:17 pm Post subject:

trying ubuntu or system rescue cd 2.0.1 or newer might be fun. (cable unplugged)
_________________
Defund the FCC.

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

Okay, I'm booted into an Ubuntu 64bit live cd, and posting this via wireless. I did a quick search to see which module was making the wireless work, looks like:

cfg80211 170293 2 rt2x00lib,mac80211

DONAHUE · Posted: Sun Apr 10, 2011 10:43 pm Post subject:

this is with the one that claims rt2573 installed?

cfg80211 is being used by rt2x00lib and mac80211 , no sign of rt73?

could you post results of

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

I just restarted the computer with the Ubuntu live cd and went with "Try Ubuntu." Then connected using Ubuntu's wireless/ Network Manager. What I listed was what showed up when I ran lsmod.
root@ubuntu:/home/ubuntu# lsmod
Module Size Used by
binfmt_misc 7984 1
dm_crypt 13381 0
lp 10201 0
snd_intel8x0 31307 2
snd_ac97_codec 125227 1 snd_intel8x0
ac97_bus 1474 1 snd_ac97_codec
snd_pcm 89104 2 snd_intel8x0,snd_ac97_codec
arc4 1497 2
rt73usb 24308 0
crc_itu_t 1739 1 rt73usb
snd_seq_midi 5932 0
snd_rawmidi 22207 1 snd_seq_midi
rt2500usb 19651 0
rt2x00usb 11316 2 rt73usb,rt2500usb
snd_seq_midi_event 7291 1 snd_seq_midi
rt2x00lib 31575 3 rt73usb,rt2500usb,rt2x00usb
snd_seq 57512 2 snd_seq_midi,snd_seq_midi_event
led_class 3393 1 rt2x00lib
mac80211 266657 2 rt2x00usb,rt2x00lib
snd_timer 23850 2 snd_pcm,snd_seq
snd_seq_device 6912 3 snd_seq_midi,snd_rawmidi,snd_seq
ppdev 6804 0
snd 64117 11 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
psmouse 62080 0
parport_pc 30086 1
edac_core 46822 0
cfg80211 170293 2 rt2x00lib,mac80211
soundcore 1240 1 snd
serio_raw 4910 0
parport 37032 3 lp,ppdev,parport_pc
edac_mce_amd 9387 0
shpchp 34910 0
i2c_nforce2 6155 0
k8temp 4064 0
snd_page_alloc 8588 2 snd_intel8x0,snd_pcm
squashfs 27681 1
aufs 179029 4367
nls_cp437 6375 1
isofs 34218 1
dm_raid45 75026 0
xor 4709 1 dm_raid45
btrfs 506518 0
zlib_deflate 21866 1 btrfs
crc32c 3007 1
libcrc32c 1268 1 btrfs
nouveau 568848 2
ttm 68212 1 nouveau
drm_kms_helper 32836 1 nouveau
drm 206161 4 nouveau,ttm,drm_kms_helper
i2c_algo_bit 6208 1 nouveau
floppy 65299 0
sata_nv 23770 1
pata_amd 12050 1
forcedeth 55649 0
ramzswap 11551 0
lzo_compress 2349 1 ramzswap
root@ubuntu:/home/ubuntu#

pottzie · Guru Joined: 06 Nov 2010 Posts: 314

I spaced out the dmesg tail. Sorry.
http://pastebin.com/t1K9px5S