Need help w Belkin F5D8053v6 usb adapter

flashl · 11-05-2009, 01:11 PM

Have read and followed many instructions but still unable to install wireless driver.

During boot have errors:
ndiswrapper version 1.54 loaded (smp=yes, preempt=no)
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMRegisterMiniportDriver'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMIndicateReceiveNetBufferLists'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMDeregisterMiniportDriver'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisFreeNetBufferListPool'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferListPool'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisFreeMdl'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferAndNetBufferList'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisAllocateMdl'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMSetMiniportAttributes'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMSendNetBufferListsComplete'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMOidRequestComplete'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisOpenConfigurationEx'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisQueueIoWorkItem'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMIndicateStatusEx'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisAllocateMemoryWithTagPriority'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisAllocateIoWorkItem'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisFreeIoWorkItem'
ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisFreeNetBufferList'
ndiswrapper (import:242): unknown symbol: WDFLDR.SYS:'WdfVersionBind'
ndiswrapper (import:242): unknown symbol: WDFLDR.SYS:'WdfVersionUnbind'
ndiswrapper (load_sys_files:206): couldn't prepare driver 'net8192su'
ndiswrapper (load_wrap_driver:108): couldn't load driver net8192su; check system log for messages from 'loadndisdriver'
usbcore: registered new interface driver ndiswrapper

Running FC11, kernel 2.6.30.9-90.fc11.i586 #1 SMP Sat Oct 17 11:09:52 EDT 2009 i686 i686 i386 GNU/Linux.

sudo lsusb:
Bus 002 Device 007: ID 056a:0015 Wacom Co., Ltd
Bus 002 Device 006: ID 03f0:4f11 Hewlett-Packard OfficeJet 5600 (USBHUB)
Bus 002 Device 004: ID 1058:1100 Western Digital Technologies, Inc.
Bus 002 Device 005: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Bus 005 Device 002: ID 066b:2206 Linksys, Inc. USB Ethernet [pegasus]
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 050d:815f Belkin Components
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

sudo ndiswrapper -l
net8192su : driver installed
device (050D:815F) present

ls /etc/ndiswrapper/net8192su:
050D:815F.F.conf 0BDA:8171.F.conf 0BDA:8172.F.conf 0BDA:8173.F.conf 0BDA:8174.F.conf net8192su.inf rtl8192su.sys

NOTE: The symbol references and errors in dmesg are from the file rtl8192su.sys

ls modprobe.d/:
blacklist-berry_charge.conf blacklist.conf blacklist-visor.conf dist.conf dist-oss.conf floppy-pnp.conf local.conf ndiswrapper.conf

cat modprobe.d/ndiswrapper.con:
install usb:v050Dp815Fd*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper

How do I solve the dmesg complaints?

Drakeo · 11-05-2009, 05:18 PM

read this and stop using the ndiswrapper

Quote:

http://blog.delgurth.com/2008/08/17/...53-and-ubuntu/

flashl · 11-06-2009, 06:16 PM

Problem in instructions start here: Anyway, so far about using ndiswrapper. Recently ralink released a new version of it’s native linux driver, 1.3.1.0 which can be found https://ralinktech.com/ralink/Home/Support/Linux.html

Page no longer exists

cookdl · 11-08-2009, 03:49 PM

hi i had a belkin usb wireless receiver and it was a total damn pain in the ass u brought a D-link one from pc world it said linex compatible on the box and plugged in and worked straight off contact me and il email u a pic of mine if u wana find one

jastonas · 12-08-2009, 04:23 AM

Quote:

Originally Posted by Drakeo

read this and stop using the ndiswrapper

This Post is for a different chip. The Belkin v1-v5 have the rt2870 while the v6 has the rtl8192su chip.
I have v6 too and cant get it to work

flashl · 12-10-2009, 11:28 AM

Found ralink linux rt2870 driver here: http://download.driverscollection.co....3.0.0.tar.bz2

Haven't been able to get it to compile yet.

flashl · 12-12-2009, 03:19 PM

I finally had a breakthrough and now able to load 'net8192su' driver via ndiswrapper. Meaning, the system will bring up the wlan0 device at boot. However, although the system brings up the wlan0 interface it is not configured with information in '/etc//sysconfig/networking/devices/ifcfg-wlan0' which assigns ssid, ipaddr, etc. There are no obvious complaints in boot.log or messages.log.

A simple 'ifdown wlan0' and 'ifup wlan0' corrects this, but, efforts to use iwconfig wlan0 to set parameters essid, ap, mode, etc. fails. Each use of iwconfig generate a complaint from netplugd "netplugd: wlan0: ignoring event". A google for this complaint is not generated any workable solutions.

cat ifcfg-wlan0
# NDIS Wrapper Configuration: Belkin
DEVICE=wlan0
ONBOOT=yes
BOOTPROTO=none
TYPE=Wireless
MODE=Managed
SSID=mynet
USERCTL=yes
RATE=auto
NICK=wlan0
NM_CONTROLLED=yes
IPV6INIT=no
ESSID="mynet"
DEFROUTE=yes
NAME="System mynet (wlan0)"
UUID=
NETMASK=255.255.255.0
DNS1=127.0.0.1
IPADDR=10.0.2.26
PREFIX=24
DOMAIN=home.lan
HWADDR=00:XX:XX:XX:XX:XX
CHANNEL=11
SECURITYMODE=restricted
DEFAULTKEY=1
-------------------------
iwlist wlan0 scanning finds ap.
-------------------------
wlan0 Scan completed :
Cell 01 - Address: XX:XX:XX:XX:XX:XX
ESSID:"mynet
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Encryption key

n
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:bcn_int=100
Extra:atim=0

iwconfig wlan0 parameters: mode managed essid mynet channel 11 ap 00:XX:XX:XX:XX:XX
--------------------------
iwconfig wlan0
wlan0 IEEE 802.11g ESSID

ff/any Nickname:"minime.home.lan"
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=0/3
RTS thr

ff Fragment thr

ff
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security mode:restricted
Power Management

ff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
--------------------------
ifconfig:
wlan0 Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX
inet addr:10.0.2.26 Bcast:10.0.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

What should I check next?

Drakeo · 12-13-2009, 11:48 AM

there is hope. The real problem is using a prebuilt kernel and modules by the distro.
So if I was you I would down load the FC11 2.6.30 or above. configure kernel and enable and buld the module RT2870 chipset which is located in my kernel /usr/src/linux-2.6.31.3/drivers/net/wireless/rt2x00 I noticed the new ubuntu does not have it in there kernel unless you get there full source. The fc11 stock configuration does not have it enabled or built.
if you love your system like it is. then make sure you have a full source and develepment libraries installed. you must build up your modules and make sure you have a backup kernel to boot.

Quote:

SOFTWARE REQUIREMENTS

Compiling and running the 2.6.xx kernels requires up-to-date
versions of various software packages. Consult
Documentation/Changes for the minimum version numbers required
and how to get updates for these packages. Beware that using
excessively old versions of these packages can cause indirect
errors that are very difficult to track down, so don't assume that
you can just update packages when obvious problems arise during
build or operation.

BUILD directory for the kernel:

When compiling the kernel all output files will per default be
stored together with the kernel source code.
Using the option "make O=output/dir" allow you to specify an alternate
place for the output files (including .config).
Example:
kernel source code: /usr/src/linux-2.6.N
build directory: /home/name/build/kernel

To configure and build the kernel use:
cd /usr/src/linux-2.6.N
make O=/home/name/build/kernel menuconfig
make O=/home/name/build/kernel
sudo make O=/home/name/build/kernel modules_install install

Please note: If the 'O=output/dir' option is used then it must be
used for all invocations of make.

That all said you understand to build out side of the source.
My short cut. cd /usr/src/linux-uname make mrproper
now copy your /boot/your-kernel config. to /usr/src/linux-uname and rename -->.config

Quote:

what I do is make xconfig the screen will then display the kernels configuration editor at the top left you can load the yes dot .config file. now navigate to the modules you want to build. Now save the files and do a make oldconfig this will then ask you to configure things as the kernel changes it branches. If you are building for the same kernel that is running skip make install
you will do a make then a make modules_install

after it is done. your enabled hardware and the driver is in the modules.
at boot with the device in it should be usable.

Quote:

I would suggest since it is imposible to know all of the distros and My luck with FC11 is limited. to build your own custom kernel and update the software around it.
This way in the future as new hardware is supported by the kernel you have a real good config that can be revised as the kernel changes with make oldconfig.

it is not always good to use tjhe newest kernel out the latest stable kernels work great but older drivers are written in different GCC versions.
right now the 2.6.29.6 has been debuged very well.
good luck linux is for you to change do not wait for some one to change it.Note

Quote:

If using NVIDIA proprietary drivers you will have to reinstall them after booting up your new modules.

flashl · 12-15-2009, 09:39 AM

Thanks for detailed response. While focused on the struggle to bring this card up don't know why it never occurred to me to build the kernel. I have nearly complied literally everything else.

And, failure to build kernel may explain why after I successfully made 'kernel/drivers/net/wireless/rt2870sta.ko' which appears in modprobe but somehow the rt2870 device is still unavailable.

Now, I am off to making backups and then start with the building.