| 1 |
Having made some progress I thought I better answer my own post below for any |
| 2 |
Belkin users out there who would rather use Linux drivers: |
| 3 |
|
| 4 |
On Monday 23 October 2006 16:55, Mick wrote: |
| 5 |
> Also, this is what dmesg shows: |
| 6 |
> |
| 7 |
> ======================================= |
| 8 |
> ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) |
| 9 |
> Loading module: rt73usb - CVS (N/A) by http://rt2x00.serialmonkey.com. |
| 10 |
> wmaster0: Failed to select rate control algorithm |
| 11 |
> wmaster0: Failed to initialize rate control algorithm |
| 12 |
> rt73usb->rt73usb_alloc_dev: Error - Failed to initialize device. |
| 13 |
> rt73usb->rt73usb_probe: Error - Failed to allocate device. |
| 14 |
> usbcore: registered new driver rt73usb |
| 15 |
> ======================================= |
| 16 |
> |
| 17 |
> On Monday 23 October 2006 14:20, Mick wrote: |
| 18 |
> > Hi All, |
| 19 |
> > |
| 20 |
> > A friend gave me a Belkin F5D7050 USB wifi adaptor which I am struggling |
| 21 |
> > to get going. I checked the Wiki which describes how to use ndiswrapper |
| 22 |
> > but it also mentions that there are drivers in portage for this purpose. |
| 23 |
> > |
| 24 |
> > http://gentoo-wiki.com/Belkin_F5D7050 |
| 25 |
> > |
| 26 |
> > I opted for the latter, set the rt73usb USE flag and emerged the rt2x00 |
| 27 |
> > drivers. |
| 28 |
> > |
| 29 |
> > However I still cannot see my new device as a network interface. Can you |
| 30 |
> > help? |
| 31 |
> > |
| 32 |
> > Supporting info below: |
| 33 |
> > =============================================== |
| 34 |
> > Bus 002 Device 003: ID 050d:7050 Belkin Components F5D7050 ver 1000 WiFi |
| 35 |
> > Device Descriptor: |
| 36 |
> > bLength 18 |
| 37 |
> > bDescriptorType 1 |
| 38 |
> > bcdUSB 2.00 |
| 39 |
> > bDeviceClass 0 (Defined at Interface level) |
| 40 |
> > bDeviceSubClass 0 |
| 41 |
> > bDeviceProtocol 0 |
| 42 |
> > bMaxPacketSize0 64 |
| 43 |
> > idVendor 0x050d Belkin Components |
| 44 |
> > idProduct 0x7050 F5D7050 ver 1000 WiFi |
| 45 |
> > bcdDevice 0.01 |
| 46 |
> > iManufacturer 1 Belkin |
| 47 |
> > iProduct 2 Belkin 54g USB Network Adapter |
| 48 |
> > iSerial 0 |
| 49 |
> > bNumConfigurations 1 |
| 50 |
> > Configuration Descriptor: |
| 51 |
> > bLength 9 |
| 52 |
> > bDescriptorType 2 |
| 53 |
> > wTotalLength 32 |
| 54 |
> > bNumInterfaces 1 |
| 55 |
> > bConfigurationValue 1 |
| 56 |
> > iConfiguration 0 |
| 57 |
> > bmAttributes 0x80 |
| 58 |
> > MaxPower 300mA |
| 59 |
> > Interface Descriptor: |
| 60 |
> > bLength 9 |
| 61 |
> > bDescriptorType 4 |
| 62 |
> > bInterfaceNumber 0 |
| 63 |
> > bAlternateSetting 0 |
| 64 |
> > bNumEndpoints 2 |
| 65 |
> > bInterfaceClass 255 Vendor Specific Class |
| 66 |
> > bInterfaceSubClass 255 Vendor Specific Subclass |
| 67 |
> > bInterfaceProtocol 255 Vendor Specific Protocol |
| 68 |
> > iInterface 0 |
| 69 |
> > Endpoint Descriptor: |
| 70 |
> > bLength 7 |
| 71 |
> > bDescriptorType 5 |
| 72 |
> > bEndpointAddress 0x81 EP 1 IN |
| 73 |
> > bmAttributes 2 |
| 74 |
> > Transfer Type Bulk |
| 75 |
> > Synch Type None |
| 76 |
> > Usage Type Data |
| 77 |
> > wMaxPacketSize 0x0040 1x 64 bytes |
| 78 |
> > bInterval 0 |
| 79 |
> > Endpoint Descriptor: |
| 80 |
> > bLength 7 |
| 81 |
> > bDescriptorType 5 |
| 82 |
> > bEndpointAddress 0x01 EP 1 OUT |
| 83 |
> > bmAttributes 2 |
| 84 |
> > Transfer Type Bulk |
| 85 |
> > Synch Type None |
| 86 |
> > Usage Type Data |
| 87 |
> > wMaxPacketSize 0x0040 1x 64 bytes |
| 88 |
> > bInterval 0 |
| 89 |
> > Device Qualifier (for other device speed): |
| 90 |
> > bLength 10 |
| 91 |
> > bDescriptorType 6 |
| 92 |
> > bcdUSB 2.00 |
| 93 |
> > bDeviceClass 0 (Defined at Interface level) |
| 94 |
> > bDeviceSubClass 0 |
| 95 |
> > bDeviceProtocol 0 |
| 96 |
> > bMaxPacketSize0 64 |
| 97 |
> > bNumConfigurations 1 |
| 98 |
> > =============================================== |
| 99 |
> > |
| 100 |
> > =============================================== |
| 101 |
> > # ifconfig -a |
| 102 |
> > dummy0 Link encap:Ethernet HWaddr 3A:6B:52:36:4D:99 |
| 103 |
> > BROADCAST NOARP MTU:1500 Metric:1 |
| 104 |
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
| 105 |
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
| 106 |
> > collisions:0 txqueuelen:0 |
| 107 |
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
| 108 |
> > |
| 109 |
> > eth0 Link encap:Ethernet HWaddr 00:02:A5:B6:A1:8F |
| 110 |
> > UP BROADCAST MULTICAST MTU:1500 Metric:1 |
| 111 |
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
| 112 |
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
| 113 |
> > collisions:0 txqueuelen:1000 |
| 114 |
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
| 115 |
> > |
| 116 |
> > lo Link encap:Local Loopback |
| 117 |
> > inet addr:127.0.0.1 Mask:255.0.0.0 |
| 118 |
> > UP LOOPBACK RUNNING MTU:16436 Metric:1 |
| 119 |
> > RX packets:8 errors:0 dropped:0 overruns:0 frame:0 |
| 120 |
> > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 |
| 121 |
> > collisions:0 txqueuelen:0 |
| 122 |
> > RX bytes:400 (400.0 b) TX bytes:400 (400.0 b) |
| 123 |
> > =============================================== |
| 124 |
> > |
| 125 |
> > PS. The eth0 above is my NIC not the Belkin adaptor. |
| 126 |
|
| 127 |
There were two problems with the above set up, both module related: |
| 128 |
|
| 129 |
The rt73usb was not suitable for my chip. The 050d:7050 under lsusb is |
| 130 |
supposed to tell you that - but I only found conflicting and confusing info |
| 131 |
on Google. This is because Belkin changed the chip without changing the |
| 132 |
model number; its pot luck which chip you may end up with and therefore trial |
| 133 |
and error is required to find out the driver that works for your USB chip. |
| 134 |
|
| 135 |
So, I changed the USE flag for the next available (rt2500usb) and remerged |
| 136 |
net-wireless/rt2x00. This was a mistake. The new module conflicted with |
| 137 |
rt73usb which I could remove just by unmerging rt2x00. I had to unmerge |
| 138 |
rt2x00, manually delete all items under /lib/modules/2.6.17-gentoo-r8/rt2x00/ |
| 139 |
and then emerge rt2x00 with the right flag (rt2500usb). |
| 140 |
|
| 141 |
The next module problem had to do with rc80211_simple which rt2x00 requires to |
| 142 |
function properly. Once modprobed and entered it |
| 143 |
in /etc/modules.autoload.d/kernel-2.6 the adaptor showed up under iwconfig & |
| 144 |
ifconfig: |
| 145 |
======================================================== |
| 146 |
# iwconfig wlan0 |
| 147 |
wlan0 IEEE 802.11g ESSID:"3141 6404" |
| 148 |
Mode:Managed Frequency:2.442 GHz Access Point: 00:0F:CC:66:12:C8 |
| 149 |
RTS thr:off Fragment thr=2346 B |
| 150 |
Encryption key:off |
| 151 |
|
| 152 |
# ifconfig wlan0 |
| 153 |
wlan0 Link encap:Ethernet HWaddr 00:11:50:18:55:3F |
| 154 |
inet addr:192.168.1.38 Mask:255.255.255.0 |
| 155 |
UP NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 |
| 156 |
RX packets:12221 errors:0 dropped:0 overruns:0 frame:0 |
| 157 |
TX packets:9665 errors:0 dropped:0 overruns:0 carrier:0 |
| 158 |
collisions:0 txqueuelen:0 |
| 159 |
RX bytes:11445153 (10.9 Mb) TX bytes:1147251 (1.0 Mb) |
| 160 |
Base address:0xd000 |
| 161 |
======================================================== |
| 162 |
|
| 163 |
Thereafter, setting up a link in the init.d scripts is required: |
| 164 |
# cd /etc/init.d && ln -s net.wlan0 net.lo |
| 165 |
|
| 166 |
as well as configuring the /etc/conf.d/net for your access point, WEP key, |
| 167 |
etc. |
| 168 |
|
| 169 |
Plugging in the USB adaptor should now automatically load the necessary |
| 170 |
driver, connect to your access point, run dhcpcd and get you on the |
| 171 |
Internet - all on its own ;-) |
| 172 |
|
| 173 |
Some nuisances: briefly unplugging the USB adaptor should not cause much of a |
| 174 |
problem, plug it back in and you're in business. However, try running: |
| 175 |
# /etc/init.d/net.wlan0 restart |
| 176 |
and a major crash is on the cards. I haven't found a respectable way of |
| 177 |
shutting down the runaway processes and the ensuing kernel oops, (should file |
| 178 |
a bug soon). Also, the driver does not offer much of a clue on the speed of |
| 179 |
the connection therefore there is not much point in running kwifimanager. |
| 180 |
|
| 181 |
Other than that I have had no trouble with the connection in the first two |
| 182 |
days (only went down once). Don't know how it performs with the |
| 183 |
wpa_supplicant yet. That'll be my next challenge. |
| 184 |
-- |
| 185 |
Regards, |
| 186 |
Mick |
Archives