Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Problem with starting "rum-driver", Linksys WUSB54GC (Ralink RT2501USB): (5 Items)
   
Problem with starting "rum-driver", Linksys WUSB54GC (Ralink RT2501USB)  
Hi everybody!

I'm having troubles with getting the rum driver loading:


Starting on-board ethernet with TCP/IP stack...
Unable to load devn-rum.so: Library cannot be found

Library can't be found if I'm using io-pkt-v4, if I use io-pkt-v4-hc
I get "Unable to start "io-pkt-v4-hc" (2)"

I'm using 

io-pkt-v4 -v -d rum 

in the build file.

USB-Hardware is beeing detected (usb -vvv) : 

Vendor                     : 0x13b1 (Cisco-Linksys)
Product                    : 0x0020 (Compact Wireless-G USB Adapter)


We're using a OMAP3530 based Gumstix Overo Board.

Have you got any idea? Thanks in advance!

Florian

Re: Problem with starting "rum-driver", Linksys WUSB54GC (Ralink RT2501USB)  
I've discovered some strange behaviour.. while testing a few configurations, I got it partially working. For example if 
I use
ifconfig, I'm able to see the interface config once, I can't execute
the command a second time... same thing for ping on loopback
for example.


Starting USB OTG Host driver...
Path=0 - TI OMAP3 MMCHS
 target=0 lun=0     Direct-Access(0) - SD:2 SA02G Rev: 0.3
Unable to access "/dev/hd0" (2)
mount: Can't mount /fs (type dos)
mount: Possible reason: Invalid argument
Starting on-board ethernet with TCP/IP stack...
#
#
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
rum0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ssid ""
        powersave off
        address: 00:23:69:07:a4:9f
        media: IEEE802.11 autoselect
        status: no network
# ifconfig
sh: ifconfig: cannot execute - No such file or directory
#


All that with following build.file (attached)

It's pretty weird... I can't figure out why... what's so strange about it is following part:

	#######################################################################
	## MMC/SD driver 
	#######################################################################
	#display_msg Starting SD Filesystem...
	/proc/boot/devb-mmcsd-omap3 dos exe=all &
	waitfor /dev/hd0 5 &
	mount -t dos /dev/hd0t6 /fs

If  I use it this way... the rum driver will load and am able to run ifconfig once.

	#######################################################################
	## MMC/SD driver 
	#######################################################################
	display_msg Starting SD Filesystem...
	/proc/boot/devb-mmcsd-omap3 dos exe=all &
	waitfor /dev/hd0 5 &
	mount -t dos /dev/hd0t6 /fs

If I uncomment the upper line, it does not work:

Starting on-board ethernet with TCP/IP stack...
Unable to init devnp-rum.so: No such device or address

I feel like a retard :/ What going wrong here?



Attachment: Text omap3530.beagle.build 21.93 KB
Re: Problem with starting "rum-driver", Linksys WUSB54GC (Ralink RT2501USB)  
How can the SD/MCC Driver print line affect my network driver not to load / to load? 
Re: Problem with starting "rum-driver", Linksys WUSB54GC (Ralink RT2501USB)  
Alright, please forget almost everything I wrote before. Unfortunately I'm not able to delete or edit my previous posts.
 

I started new from an untouched BSP file. First off all, I made the USB OTG working, Wireless Dongle beeing detected on 
the bus (usb -vvv). I noticed, that when I tried to start the "rum" driver this time, that it produced a "device or 
address not found"-message... I've changed the startup a litte bit: Loading USB driver, and then made the whole thing 
wait for a few seconds, after that I started loading the "rum" and voila... the Wireless driver loaded. It seems that 
the USB Port didn't have enough time to fully initialize or something like that. 

But that didn't solve the whole problem yet. I'm still unable to use any network command twice. Once I've used it, it 
won't start anymore: sh: ifconfig: cannot execute - No such file or directory

I thought, that it is probably caused by the rum driver... so I've excluded everything and used a bare mininium and just
 started the TCP/IP stack without loading rum. And still, I'm only able to ping the loopback once, not a second time. 
Same thing for ifconfig, netstat, ping as mentioned... and so on.  
Re: Problem with starting "rum-driver", Linksys WUSB54GC (Ralink RT2501USB)  
Hi Florian,

I'll direct your attention to http://www.qnx.com/developers/docs/6.4.1/neutrino/utilities/m/mkifs.html#XIPvsCopy

Most likely you've got the binaries in your image set as "UIP" mode.  Fixing this is as easy as adding [data=copy] to 
the programs you want to be able to run more than once.

Hope this helps,

-Will