Belkin USB Wireless Stick F5D7051

[pytheas22]

ok, i dunno if my wireless adapter worked because my video card was screwed lol

What happened to your video exactly? Can you no longer log in?

The tutorial that you followed had you enable the intrepid-proposed repository, which contains non-stable software; this is likely what broke your video.

You could try booting into an older kernel to get your screen back. To do that, you would want to select one of the kernels towards the bottom of the list at the grub boot screen, which is the screen you see shortly after turning on your computer, after BIOS finishes but before Ubuntu starts loading (with the orange bar). You may need to press 'escape' to get into grub; if so, you should see a message on your screen that says something like 'Press escape now to enter boot menu'.

If an older kernel works, we can try to make your card work in ndiswrapper using it.

If an older kernel doesn't work, then your system is probably badly broken and you might want to consider reinstalling, then coming back here so we can make your wireless work.

You could also try applying the updates again to see if that will fix your system--the packages in intrepid-proposed are updated rapidly, and within a few days they might make your computer work again. To apply updates without being able to log in graphically, you would do this:

1. plug your computer into ethernet
2. once Ubuntu finishes loading, press control-alt-F2. This brings you to a command prompt.
3. log in on the command prompt, then run these commands:

sudo ifconfig eth0 up #bring up ethernet interface
sudo dhclient eth0 #request IP address
sudo apt-get update #update software package list
sudo apt-get upgrade #download and install updates

Then reboot by typing:

sudo reboot

and see if your video and/or wireless work again.

[Post Monkeh]

thanks for the reply.

i got it working again, i posted that message last night from it. yeah, i just immediately rebooted to the 27-9 kernel and removed the 27-11 one from my grub boot list for the time being. the screen was basically comprised of various multi coloured ubuntu symbols and would not even let me into a terminal using alt & f1-f6. think i'll wait a while before i try anymore unsupported kernels, i have to say though, i love how linux lets you go back to your previous settings, when i stuff windows up it's usually a lot harder to fix .

i have tried before (and failed miserably might i add) to use ndiswrapper) the computer basically would not load up after i used it, but then i may have been installing a few things at the same time like the proprietary driver for my ati hd3850 video card that i found out last night didn't work quite right either. i got it sorted by downloading the latest one from the amdati website. it may well have been the fact that the new kernal was trying to use a different version of that driver that screwed up my screen, but that's besides the point.

i'm not at home tonight, posting this from my laptop, but if i get a chance tomorrow night i might give ndiswrapper another try, i think i could manage to uninstall it now using the recovery terminal if it buggers anything up.

before, i got as far as actually installing the blkwgu (think that was it) driver from my cd by installing wine, installing the cd then copying the inf file from there. once i tried to reload the pc though it just refused to do anything, the whole system lagged, but i'm not sure if at that point ubuntu was maybe trying to use 2 drivers for my adapter.
the problem now seems to be that it isn't trying to use any.

i'll give it another blast tomorrow, cheers

[Post Monkeh]

lol just noticed the 27-11 kernel is now available as a supported update. i think i'll take the ati driver out before i update again on the main pc.

[pytheas22]

lol just noticed the 27-11 kernel is now available as a supported update. i think i'll take the ati driver out before i update again on the main pc.

Yes, I have 2.6.27-11 in updates today as well (and I don't have the testing repositories enabled). I would install that and see if it makes your card work. According to what I read, the rtl8187 driver in this latest kernel should support your card out-of-the-box, abrogating the need for all the ndiswrapper nonsense.

If, after installing the new kernel and rebooting, your wireless still seems not to work, make sure that the rtl8187 driver is inserted and that ndsiwrapper is not by typing:

sudo modprobe -r ndiswrapper
sudo modprobe rtl8187

If that still fails, please post the output of:

dmesg | grep -e wlan -e rtl
lsmod | grep rtl
lshw -C Network
sudo iwlist scan

[Post Monkeh]

strange. i managed to get round the video card problem by uninstalling it and going through an xorg & package repair.

adapter was recognised and i got connected to my network but i can't access the internet. can't ping my router ip either, although when i disconnect then reconnect the connection, i can ping 2, sometimes 3 packets, then i get a destination host unreachable.

will get the cable back in and post the results of those commands

[Post Monkeh]

will@will-desktop:~$ dmesg | grep -e wlan -e rtl
[   12.063600] rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage your
[   12.499016] phy0: hwaddr 00:1c:df:37:ce:4b, RTL8187BvE V0 + rtl8225z2
[   12.499049] usbcore: registered new interface driver rtl8187
[   40.563632] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   61.817264] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   62.016021] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   62.216024] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   62.416020] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[   74.617278] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   74.785278] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   74.984015] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   75.184017] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   75.384018] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[   87.405294] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   87.573296] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   87.772013] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   87.972016] wlan0: authenticate with AP 00:21:63:7a:66:f1
[   88.172015] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  100.021309] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  100.349310] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  100.548010] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  100.748016] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  100.948011] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  112.977203] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  113.305203] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  113.504016] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  113.704013] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  113.904016] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  124.149326] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  124.337328] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  124.536020] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  124.736021] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  124.936011] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  136.765215] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  137.093216] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  137.292015] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  137.492017] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  137.692012] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  149.717232] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  150.045233] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  150.244047] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  150.444014] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  150.644012] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  162.857249] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  163.021250] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  163.220017] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  163.420011] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  163.620010] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  175.657268] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  175.856020] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  176.056014] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  176.256020] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  196.437246] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  196.601248] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  196.805017] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  197.004015] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  197.204020] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  209.057261] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  209.389262] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  209.588015] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  209.788018] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  209.988011] wlan0: authentication with AP 00:21:63:7a:66:f1 timed out
[  222.009279] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  222.337279] wlan0: authenticate with AP 00:21:63:7a:66:f1
[  222.337294] wlan0: authenticated
[  222.337298] wlan0: associate with AP 00:21:63:7a:66:f1
[  222.343414] wlan0: RX AssocResp from 00:21:63:7a:66:f1 (capab=0x411 status=0 aid=1)
[  222.343421] wlan0: associated
[  222.343857] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  233.284006] wlan0: no IPv6 routers present
will@will-desktop:~$

will@will-desktop:~$ lsmod | grep rtl
rtl8187                53248  0 
mac80211              216820  1 rtl8187
eeprom_93cx6           10240  1 rtl8187
cfg80211               32392  2 rtl8187,mac80211
usbcore               149360  6 rtl8187,btusb,usbhid,ehci_hcd,uhci_hcd
will@will-desktop:~$

will@will-desktop:~$ lshw -C Network
WARNING: you should run this program as super-user.
  *-network               
       description: Ethernet interface
       product: L1 Gigabit Ethernet Adapter
       vendor: Attansic Technology Corp.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: b0
       serial: 00:22:15:61:fe:60
       width: 64 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical
       configuration: broadcast=yes driver=atl1 driverversion=2.1.3 firmware=N/A latency=0 module=atl1 multicast=yes
  *-network:0
       description: Wireless interface
       physical id: 1
       logical name: wlan0
       serial: 00:1c:df:37:ce:4b
       capabilities: ethernet physical wireless
       configuration: broadcast=yes ip=192.168.0.22 multicast=yes wireless=IEEE 802.11bg
  *-network:1 DISABLED
       description: Ethernet interface
       physical id: 2
       logical name: pan0
       serial: 0e:a0:95:67:c5:5e
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes
will@will-desktop:~$ sudo lshw -C network
[sudo] password for will: 
  *-network               
       description: Ethernet interface
       product: L1 Gigabit Ethernet Adapter
       vendor: Attansic Technology Corp.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: b0
       serial: 00:22:15:61:fe:60
       capacity: 1GB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=atl1 driverversion=2.1.3 firmware=N/A latency=0 link=no module=atl1 multicast=yes port=twisted pair
  *-network:0
       description: Wireless interface
       physical id: 1
       logical name: wlan0
       serial: 00:1c:df:37:ce:4b
       capabilities: ethernet physical wireless
       configuration: broadcast=yes ip=192.168.0.22 multicast=yes wireless=IEEE 802.11bg
  *-network:1 DISABLED
       description: Ethernet interface
       physical id: 2
       logical name: pan0
       serial: 0e:a0:95:67:c5:5e
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes
will@will-desktop:~$

will@will-desktop:~$ sudo iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wmaster0  Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 00:1F:9F:4E:1C:C5
                    ESSID:"BTHomeHub-02AA"
                    Mode:Master
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=32/100  Signal level:-55 dBm  
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:tsf=00000319dc37a9a1
                    Extra: Last beacon: 2332ms ago
          Cell 02 - Address: 00:1B:2F:45:C4:48
                    ESSID:"SKY05519"
                    Mode:Master
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=60/100  Signal level:-41 dBm  
                    Encryption key:on
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:tsf=000000027ee26c86
                    Extra: Last beacon: 2332ms ago
          Cell 03 - Address: 00:21:63:7A:66:F1
                    ESSID:"the oval"
                    Mode:Master
                    Channel:9
                    Frequency:2.452 GHz (Channel 9)
                    Quality=66/100  Signal level:-38 dBm  
                    Encryption key:on
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:tsf=000000004414e2ac
                    Extra: Last beacon: 580ms ago

pan0      Interface doesn't support scanning.

will@will-desktop:~$

they were all with my wireless adapter connected to my network (the oval) and the ethernet cable unplugged.

my ethernet stops working when my wireless is connected too, btw.

[pytheas22]

hmmm, it looks like the rtl8187 driver might have some association issues. Could you please connect wirelessly and post the output of these commands:

cat /etc/resolv.conf
ping -c 10 google.com
ping -c 10 74.125.67.100
time wget google.com

Also, if possible, it may be worth it to turn off security on your router just to see if that makes a difference. Which network is yours, by the way?

[Post Monkeh]

will@will-desktop:~$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.0.1
will@will-desktop:~$ ping -c 10 google.com
ping: unknown host google.com
will@will-desktop:~$ ping -c 10 74.125.67.100
PING 74.125.67.100 (74.125.67.100) 56(84) bytes of data.
From 192.168.0.22 icmp_seq=1 Destination Host Unreachable
From 192.168.0.22 icmp_seq=2 Destination Host Unreachable
From 192.168.0.22 icmp_seq=3 Destination Host Unreachable
From 192.168.0.22 icmp_seq=5 Destination Host Unreachable
From 192.168.0.22 icmp_seq=6 Destination Host Unreachable
From 192.168.0.22 icmp_seq=7 Destination Host Unreachable
From 192.168.0.22 icmp_seq=8 Destination Host Unreachable
From 192.168.0.22 icmp_seq=9 Destination Host Unreachable
From 192.168.0.22 icmp_seq=10 Destination Host Unreachable

--- 74.125.67.100 ping statistics ---
10 packets transmitted, 0 received, +9 errors, 100% packet loss, time 9021ms
, pipe 3
will@will-desktop:~$ time wget google.com
--2009-01-29 17:52:44--  http://google.com/
Resolving google.com... failed: Name or service not known.
wget: unable to resolve host address `google.com'

real	0m20.060s
user	0m0.000s
sys	0m0.004s
will@will-desktop:~$

i'm connected to the oval.

couldn't connect without encryption, i couldn't leave it off too long because the rest of the house were using the network too, but it just wouldn't connect.

[pytheas22]

That's strange. What happens if you try to ping your router:

ping -c 10 192.168.0.1

Also, does your connectivity improve if you run these commands:

sudo dhclient -r eth0
sudo ifconfig eth0 down

before connecting?

[Post Monkeh]

like i said, if i ping my router, i get a host unreachable message. if i disconnect/reconnect the wireless, i can ping maybe 3 packets then it starts dropping.


btw, i got this

will@will-desktop:~$ ping -c 10 74.125.67.100
PING 74.125.67.100 (74.125.67.100) 56(84) bytes of data.

--- 74.125.67.100 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9013ms

will@will-desktop:~$ sudo ifconfig eth0 up
[sudo] password for will: 
will@will-desktop:~$ ping -c 10 74.125.67.100
PING 74.125.67.100 (74.125.67.100) 56(84) bytes of data.
64 bytes from 74.125.67.100: icmp_seq=1 ttl=238 time=144 ms
64 bytes from 74.125.67.100: icmp_seq=2 ttl=238 time=131 ms
64 bytes from 74.125.67.100: icmp_seq=3 ttl=238 time=130 ms
64 bytes from 74.125.67.100: icmp_seq=4 ttl=238 time=142 ms
64 bytes from 74.125.67.100: icmp_seq=5 ttl=238 time=134 ms
64 bytes from 74.125.67.100: icmp_seq=6 ttl=238 time=135 ms
64 bytes from 74.125.67.100: icmp_seq=7 ttl=238 time=132 ms
64 bytes from 74.125.67.100: icmp_seq=8 ttl=238 time=129 ms
64 bytes from 74.125.67.100: icmp_seq=9 ttl=238 time=133 ms
64 bytes from 74.125.67.100: icmp_seq=10 ttl=238 time=129 ms

--- 74.125.67.100 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9042ms
rtt min/avg/max/mdev = 129.989/134.424/144.396/4.863 ms
will@will-desktop:~$ ping -c 10 74.125.67.100
PING 74.125.67.100 (74.125.67.100) 56(84) bytes of data.
64 bytes from 74.125.67.100: icmp_seq=1 ttl=238 time=131 ms
64 bytes from 74.125.67.100: icmp_seq=2 ttl=238 time=129 ms
64 bytes from 74.125.67.100: icmp_seq=3 ttl=238 time=135 ms
64 bytes from 74.125.67.100: icmp_seq=4 ttl=238 time=129 ms
64 bytes from 74.125.67.100: icmp_seq=5 ttl=238 time=130 ms
64 bytes from 74.125.67.100: icmp_seq=6 ttl=238 time=136 ms
64 bytes from 74.125.67.100: icmp_seq=7 ttl=238 time=130 ms
64 bytes from 74.125.67.100: icmp_seq=8 ttl=238 time=130 ms
64 bytes from 74.125.67.100: icmp_seq=9 ttl=238 time=130 ms
64 bytes from 74.125.67.100: icmp_seq=10 ttl=238 time=130 ms

--- 74.125.67.100 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9047ms
rtt min/avg/max/mdev = 129.392/131.647/136.675/2.431 ms
will@will-desktop:~$

when i tried it after connecting my cable and BEFORE switching off my wireless.

i still couldn't ping my router.