Think I have a similar problem to the one that is in this thread https://www.virtualhere.com/node/570 I have a mini WiFi router onto which I have installed OpenWRT and successfully been able to run vhusbdmipsel and I have the same symptoms as previous mentioned thread. when i run the usb server with the usb attached then alls fine but if I unplugg and then plug in again then it doesnt work. Below is some of the lines of the log read:
Dec 29 14:32:54 OpenWrt kern.info kernel: [ 3990.690000] usb 1-1: USB disconnect, device number 5
Dec 29 14:32:58 OpenWrt kern.info kernel: [ 3995.180000] usb 1-1: new high-speed USB device number 6 using ehci-platform
Dec 29 14:32:59 OpenWrt kern.info kernel: [ 3995.400000] scsi4 : usb-storage 1-1:1.0
Dec 29 14:32:59 OpenWrt user.err vhusbdmipsel74kc[2300]: Error 13 opening device (/tmp/bus_usb_001_006) file descriptor, Permission denied
Dec 29 14:33:00 OpenWrt kern.notice kernel: [ 3996.780000] scsi 4:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 0 CCS
Dec 29 14:33:00 OpenWrt kern.notice kernel: [ 3996.810000] sd 4:0:0:0: [sda] 15820800 512-byte logical blocks: (8.10 GB/7.54 GiB)
Dec 29 14:33:00 OpenWrt kern.notice kernel: [ 3996.830000] sd 4:0:0:0: [sda] Write Protect is off
Dec 29 14:33:00 OpenWrt kern.debug kernel: [ 3996.840000] sd 4:0:0:0: [sda] Mode Sense: 43 00 00 00
Dec 29 14:33:00 OpenWrt kern.err kernel: [ 3996.840000] sd 4:0:0:0: [sda] No Caching mode page present
Dec 29 14:33:00 OpenWrt kern.err kernel: [ 3996.850000] sd 4:0:0:0: [sda] Assuming drive cache: write through
Dec 29 14:33:00 OpenWrt kern.err kernel: [ 3996.870000] sd 4:0:0:0: [sda] No Caching mode page present
Dec 29 14:33:00 OpenWrt kern.err kernel: [ 3996.880000] sd 4:0:0:0: [sda] Assuming drive cache: write through
Dec 29 14:33:00 OpenWrt kern.info kernel: [ 3996.900000] sda: sda1
Dec 29 14:33:00 OpenWrt kern.err kernel: [ 3996.910000] sd 4:0:0:0: [sda] No Caching mode page present
Dec 29 14:33:00 OpenWrt kern.err kernel: [ 3996.920000] sd 4:0:0:0: [sda] Assuming drive cache: write through
Dec 29 14:33:00 OpenWrt kern.notice kernel: [ 3996.930000] sd 4:0:0:0: [sda] Attached SCSI removable disk
root@OpenWrt:/tmp#
So my initial guess is that it might be the same problem as before regarding the timing, so is there a way that I can tell VH to wait until the openwrt have finished initialising the usb to see if that works better?
Kind Regards
.
can you run uname -a and send me the output,
you should be using lede because openwrt has been abandoned, so all updates are done in the lede project instead, and the kernel is better there
this is the output: Linux
this is the output: Linux OpenWrt 3.7.5 #9 Sun Dec 29 19:16:08 UTC 2013 mips GNU/Linux
I'll do a google search for Lede, reason I used openwrt is because my wifi dongle is an unamed china thing which is called A5-V11 and there were some others that had successfully put openwrt on there so I had some instructions which was crucial as I havent worked a lot with Linux before
.
I think you should put lede on it first
https://lede-project.org/toh/hwdata/other/other_a5-v11
seems like its supported at the moment , then try again
Brilliant, it seems to be
Brilliant, it seems to be working, now I just need to figure a way to copy the vhusbdmipsel file from usb upon start and then run it :)
Internet Present
Does the virtualhere server need to be connected to the internet to be able to secure a connection to a client? I have lede running and copied the vhusbdmipsel into the tmp folder, started the server and it connects fine to my computer. Unplugged the network cable connected another computer to the same wifi started usb client on that computer hooked up a camera to the wifi router and the computer seems to almost find it but not quite. Gave up, got back to the first computer to check if it would work there wouldnt connect there either, connected the network cable to the router so it got internetconnection then it instantly connected to the server on the computer..
.
No , doesnt require any internet connection. You should check logread on the server and the system messages on the client for hints as to the problem.