Raspberry Pi 3 - USB device connection okay but no data

Hi,

I am using USB temperature sensors on Raspberry Pi 2B at the moment. They are connected to a windows machine using virtualhere and a program on the windows computer reads the data coming from the sensors. From now on i am going to use RPi 3's instead of the second generation.
The problem that occurred is that the program on the windows computer (Fourtec DataSuite) can't read the USB sensors anymore. Even though they are shown as connected in vhui64.
Is it possible that something in the kernel/firmware on the Pi changed that stops virtuelhere from "sending" the actual data?

ps: It works perfectly fine on an old RPi2 B+ with Raspbian Wheezy. But doesn't on a Rpi3 with the newest Raspbian Jessie. The sensors are also working just fine when I plug them directly into the windows computer.

Thanks,
BallerNacken

#2

that sounds like a kernel bug to me. Did you install jessie from the raspberrypi.org website and did you do

sudo rpi-update

If you havent run rpi-update i think you should do that to get the latest stuff

#3

Yes it is up to date. I just installed the most current Wheezy version onto an SD card, updated and upgraded it in my Pi2 and put that SD card in the Pi3. It works now, so there seems definitely something in the Kernel that causes this issue.

#4

Ok thats good to know, Its weird how sometimes kernel bugs reappear...

#5

similar problem here with Jessie and RaspberryPi 3 ... No connection with LAN... WLAN works fine...
sudo rpi-update doesnt help
Downloaded newest image from raspberrypi.org from 2016-09-23 with pixel works fine again with LAN.

#6

I'm trying to use Dolphinbar with the RPI3 using VirtualHere, but the packets aren't being sent properly. Is using Wheezy with the RPI3 still the only working solution?

#8

Has anyone got any further with this?

I can confirm this is still bugged on Raspbian Jessie, also I tried OSMC (based on Debian Jessie) and same problems.

I saw another thread mentioning issues with "full speed" USB but - apart from this being an issue with Jessie (kernel 4?) - I haven't found anything further.

#10

I've played with the dwc_otg (USB driver) settings and found that only using setting:
dwc_otg.fiq_fsm_mask=0x3

Allows the Wii controller to work. In experimenting I found that using either WiFi or dwc_otg.speed=1 causes too much latency on the network for GameStream.

My environment:
Raspberry Pi 3
OSMC 2017.05-2 + script.luna-0.7.0-rc7.zip
Kernel - 4.9.29-5-osmc
VirtualHere v3.3.4
Ethernet connection
Maybush Dolphin Bar Wii Controller
(Windows 10 + GameStream)

My /boot/cmdline.txt:
root=/dev/mmcblk0p2 rootfstype=ext4 rootwait quiet osmcdev=rbp2 dwc_otg.fiq_fsm_mask=0x3

Now I just have to work out how to stop GameStream muting sound from Luna ..

#11

Thanks for the update timberr, that will be useful for others