Commands seem to cut out after a few minutes (Win11 PC, Pi4, G29 wheel)

Submitted by law on #1

Hi, I am using virtualhere server on a Raspberry Pi4 and the client on my Windows 11 PC and it works great.....for a few minutes, then the server appears to stop sending input commands to the client and it no longer works. The virtualhere client on the windows 11 PC still shows the Pi as a server and still shows the G29 wheel as 'in use'. To get it going again, I have to disconnect it in the virtualhere client and re-select 'use this device'. When this happens, I can see my inputs are working again within the logitech g hub software but it quickly stops again after a few seconds/button presses. 

When I first set it up to play, I plug my Logitech G29 wheel + pedals into the Pi, then the server and the G29 show up on the client as expected. I then select 'use this device' and it switches to 'in use'. At this point, the G29 now shows as expected within the logitech g hub software as if it was directly plugged into the PC. It is then that I get a few minutes of playing time before I experience the behavior at the top of this post.

Is this a known issue? and if so are there any suggestions on what I could try to resolve it?

  • I am using the trial version of virtualhere as the G29 is the only device I need to use it with
  • I am using the generic linux arm version of the vitrualhere server - I did try the pi4 version but it wouldn't work under the trial
  • my Pi is up to date
  • my network is fully hardwired and gigabit
  • my virtualhere client and server are likely very up to date as I only installed them a few days ago
  • I use sunshine as my streaming server on the Windows 11 PC and the Moonlight client for it
  • I have also purchased the steam version of virtualhere from the steam store and tested this with steamlink (instead of sunshine/moonlight+VH server/client) but get similar behaviour (though its easier for me to debug when running outside of steam)

Here is what my VH server logs are looking like during this behaviour. (Within this log time frame, I had also set the g29 to un-use/in-use a few times after it cuts out.)
 

Oct 22 13:56:17 raspberrypi4 vhusbdarm[482]: 192.168.0.41 connected as connection 1 (Standard TCP)
Oct 22 13:56:39 raspberrypi4 vhusbdarm[482]: Found Full speed device [046d:c260] "Logitech, G29 Driving Force Racing Wheel" at address 113
Oct 22 13:57:15 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c260
Oct 22 13:57:15 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c260] BOUND to connection 1
Oct 22 13:57:15 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c260
Oct 22 14:22:43 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c260] SURPRISE UNBOUND from connection 1
Oct 22 14:22:43 raspberrypi4 vhusbdarm[482]: Unmanaging device 113 [046d:c260]
Oct 22 14:22:44 raspberrypi4 vhusbdarm[482]: Found Full speed device [046d:c24f] "Logitech, G29 Driving Force Racing Wheel" at address 113
Oct 22 14:27:52 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:27:52 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c24f] BOUND to connection 1
Oct 22 14:27:52 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:27:57 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:27:57 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:27:58 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:27:58 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:30 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:30 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:32 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:32 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:53 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:54 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:29:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:08 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:08 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:12 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:12 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:12 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:12 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:13 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:13 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:13 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:16 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:16 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:21 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:21 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:27 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:27 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:32 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:32 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:34 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:35 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:36 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:36 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:38 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:38 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:39 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:39 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:40 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:40 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:40 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:41 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:42 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:42 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:43 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:43 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:44 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:44 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:45 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:45 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:48 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:48 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:49 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:50 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:50 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:52 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:52 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:53 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:54 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:54 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:54 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:56 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:56 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:56 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:56 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:59 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:30:59 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:02 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:02 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:04 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:04 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:06 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:06 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:07 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:07 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:08 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:08 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:11 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:11 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:13 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:13 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:15 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:15 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:16 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:16 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:19 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:19 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:21 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:22 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:24 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:24 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:26 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:26 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:27 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:27 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:30 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:30 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:30 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:30 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:31 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:31 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:32 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:32 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:33 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:33 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:34 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:34 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:35 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:35 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:36 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:36 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:38 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:38 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:39 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:39 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:41 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:41 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:42 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:42 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:44 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:44 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:46 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:46 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:49 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:49 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:50 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:50 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:52 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:52 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:53 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:53 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:56 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:56 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:58 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:31:58 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:00 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:00 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:02 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:02 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:04 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:04 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:05 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:05 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:06 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:06 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:07 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:07 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:09 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:09 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:09 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:09 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:10 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:10 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:10 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:10 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:12 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:12 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:15 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:15 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:16 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:16 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:17 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:17 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:19 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:19 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:21 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:21 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:22 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:22 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:22 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:22 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:24 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:24 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:24 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:24 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:25 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:26 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:26 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:27 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:27 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:28 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:28 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:28 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:28 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:29 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:31 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:31 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:33 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:33 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:34 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:34 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:34 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:34 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:35 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:35 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:36 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:36 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:38 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:38 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:40 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:40 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:41 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:41 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:41 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:42 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:42 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:32:42 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:35:55 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c24f] UNBOUND from connection 1
Oct 22 14:35:57 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:35:57 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c24f] BOUND to connection 1
Oct 22 14:35:57 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:03 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:03 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:04 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:04 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:07 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:07 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:09 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:09 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:35 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c24f] UNBOUND from connection 1
Oct 22 14:36:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:37 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c24f] BOUND to connection 1
Oct 22 14:36:37 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:43 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:43 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:44 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:44 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:46 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:46 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:47 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:48 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:48 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:49 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:49 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:49 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:49 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:50 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:50 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:51 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:53 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:53 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:54 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:54 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:55 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:58 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:58 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:59 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:36:59 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:01 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:10 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c24f] UNBOUND from connection 1
Oct 22 14:37:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:14 raspberrypi4 vhusbdarm[482]: Device 113 [046d:c24f] BOUND to connection 1
Oct 22 14:37:14 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:18 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:19 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:19 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:20 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
Oct 22 14:37:23 raspberrypi4 vhusbdarm[482]: Executed "" for onReset.046d.c24f
  

Submitted by law on Mon, 2023/10/23 - 00:44

#2

So after a bit more digging, specifically against the 'surprise unbound' log, I found a possible similar issue: https://www.virtualhere.com/node/2710

So I am just trying this custom event handler now:

onReset.$VENDOR_ID$.$PRODUCT_ID$=

I will report back with results/observations.

I also ran dmesg as also suggested but there is a lot going on here (and I also have a logitech keyboard and mouse which adds to the log confusion) but here are the bits I think relate to the G29 wheel:

[  729.775485] logitech-hidpp-device 0003:046D:4054.0004: HID++ 4.5 device connected.
[  734.224156] logitech-hidpp-device 0003:046D:4023.0003: HID++ 2.0 device connected.
[ 1347.801009] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
[ 1347.935529] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c260, bcdDevice=89.00
[ 1347.935550] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1347.935566] usb 1-1.3: Product: G29 Driving Force Racing Wheel
[ 1347.935582] usb 1-1.3: Manufacturer: Logitech
[ 1788.994479] cxd2880: cxd2880_set_frontend: sys:3 freq:498000000 bw:8
[ 1790.020783] cxd2880: cxd2880_set_frontend: tune result 0
[ 1824.995231] cxd2880: cxd2880_set_frontend: sys:3 freq:594000000 bw:8
[ 1826.020834] cxd2880: cxd2880_set_frontend: tune result 0
[ 1860.995510] cxd2880: cxd2880_set_frontend: sys:3 freq:522000000 bw:8
[ 1862.021583] cxd2880: cxd2880_set_frontend: tune result 0
[ 1896.995947] cxd2880: cxd2880_set_frontend: sys:16 freq:474167000 bw:8
[ 1898.028664] cxd2880: cxd2880_set_frontend: tune result 0
[ 1932.996577] cxd2880: cxd2880_set_frontend: sys:3 freq:570000000 bw:8
[ 1934.029170] cxd2880: cxd2880_set_frontend: tune result 0
[ 2911.909589] usb 1-1.3: USB disconnect, device number 4
[ 2912.364909] usb 1-1.3: new full-speed USB device number 5 using xhci_hcd
[ 2912.501590] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c24f, bcdDevice=89.00
[ 2912.501615] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2912.501631] usb 1-1.3: Product: G29 Driving Force Racing Wheel
[ 2912.501646] usb 1-1.3: Manufacturer: Logitech
[ 4222.082285] v3d fec00000.v3d: MMU error from client L2T (0) at 0xb761000, pte invalid
 


 

 

 

Submitted by law on Mon, 2023/10/23 - 01:07

#3

Unfortunately the custom event handler didn't resolve the issue.

It looks like this post is pretty much exactly what I am experiencing and with a G29 too:

https://www.virtualhere.com/node/3376

It suggests checking the client stats for latency readings - I don't think mine is latency issues as its fine when it briefly works otherwise it just completely stops (as opposed to slow to respond). For me, the readings from usb hubs > about > statistics are consistently between 2ms and 5ms with occasional peaks to around 8ms so I think this is ok (and well below 20ms). The readings were the same when I reset the device to try it when it works and also after it had frozen up.

 

Submitted by Michael on Mon, 2023/10/23 - 08:03

#4

Can you try putting a separately powered USB hub between the wheel and the pi if possible.

Submitted by law on Tue, 2023/10/24 - 22:04

#5

I tried using a separately powered usb hub but although the G29 still shows up in the VH client, it does not send any commands through. I can see the G29 in the Logitech G Hub software but all buttons are unresponsive. The hub I tried is an old USB 2.0 hub (D-Link DUB-H7 same as this: https://www.alphr.com/components/26578/d-link-review/). I can purchase a newer USB 3.0 hub if you think it is worth a shot? 

I also tried a regular unpowered hub too just in case but that experienced the same issues as the original post.

Submitted by Michael on Wed, 2023/10/25 - 07:29

#6

No i dont think a usb 3 would make a difference. I dont know the issue unfortunately. 

Submitted by jonshaw199 on Sun, 2024/12/08 - 18:48

#7

I am experiencing the same issue as you. The wheel seems to work for a few moments and then stops working on the remote machine, even though it shows up in the list of devices in Virtualhere Client. 

  • Pi4 w/ Raspbian Bullseye and Steamlink (latest); I am using the integrated Virtualhere Server for Steamlink
  • Windows 11 PC w/ Steam and Virtualhere Client
  • G29 wheel/pedals/shifter, but maybe a new version or something; it's brand new. People suggest switching it to "PS3" mode (switch behind steering wheel) but this one only has "PC", "PS4", and "PS5" modes.

Some things I've tried:

  • Plugging wheel directly into windows gaming PC, bypassing virtualhere altogether, just to make sure everything works
  • Plugging wheel directly into Pi instead of using USB extension
  • Adding custom event handler
  • Switching between all 3 modes on the wheel: "PC", "PS4", and "PS5"

Submitted by Michael on Mon, 2024/12/09 - 07:58

#8

I dont know what the problem is with the G29

Submitted by jonshaw199 on Mon, 2024/12/09 - 16:50

#9

I understand, don't mean to kick a dead horse, just thought it was worth adding my 2 cents in case it keeps coming up. I'm trying to investigate but my linux knowledge is limited. Also, I'm using "virtualhere for steam link" so I'm not sure what my options are for debugging or where to look for logs.

A couple other things worth noting:

  • I tried to test this using other operating systems (Raspian Bookworm, MacOS, and Ubuntu) but Virtualhere is hidden for lack of a better term and I dont know why. It only shows up and works for me when using Raspian Bullseye.
  • I used oversteer to test the G29 inputs in Raspian and everything worked as expected.

Submitted by Michael on Tue, 2024/12/10 - 07:57

#10

I tried to test this using other operating systems (Raspian Bookworm, MacOS, and Ubuntu) but Virtualhere is hidden for lack of a better term and I dont know why. It only shows up and works for me when using Raspian Bullseye

Uninstall the virtualhere spp for steamlink and download and run the virtualhere server and client from this website. 

Im thinking it might not be appearing because by default "Auto-Find" is turned off in the virtualhere client for steamlink so it doesnt search for vh servers on the network automatically.

Turn on Auto-Find in the client by right clicking USB Servers and checking Auto-Find and the servers should automatically appear. 

Then you can try on different platforms. Let me know how it goes.

 

Submitted by jonshaw199 on Tue, 2024/12/10 - 13:54

#11

I didn't know about the trial version. I quickly gave it a try after work and initial testing suggests that the G29 is working properly now. It no longer "cuts out". 

A couple notes:

  • I started with installing virthualhere server on the laptop running Ubuntu rather than the Pi running Raspberry Pi OS. This is better for me, and it worked. I will try with a Pi too. 
  • I installed virtualhere client on the windows PC and turned on auto-find. I'm a bit confused though, are you suggesting auto-find would mainly help when using the virtualhere server that is integrated into steam link? I'm using the standalone server now. The issue I was having before is virtualhere server was totally missing from the steamlink settings menu.
  • I kept the G29 in "PC" mode rather than "PS4" or "PS5".

Will report back when I get more info. Thank you!

Submitted by jonshaw199 on Tue, 2024/12/10 - 16:26

#12

I did a bit more testing. TLDR, this did not work on the Pi, but it did on the laptop (previous comment). I installed the latest version of Raspberry Pi OS (Bookworm) on my Pi4. Then I installed Virtualhere Server and Steamlink. Like before, Virtualhere did not show in the Steamlink settings menu, even though I enabled "auto-find USB servers" on the client (not sure if I understood that part correctly). But that didn't matter because I was already running Virtualhere Server independently from Steamlink per your suggestion. I then tried to play a game, but the same issue happened like before where the wheel appeared to work for a few seconds but then it would just stop responding. In summary, it seems like it works on an intel laptop running Ubuntu but not a Pi4 running Pi OS for whatever that's worth. I managed to grab a few logs, not sure if they're the right ones:

Server:

Dec 09 21:32:53 jon-pi4-2 vhusbdarm64[1313]: >>> Starting VirtualHere USB Server v4.7.2 (Built: Nov 27 2024, 08:19:03)<<<
Dec 09 21:32:53 jon-pi4-2 vhusbdarm64[1313]: Creating default configuration /usr/local/etc/virtualhere/config.ini
Dec 09 21:32:53 jon-pi4-2 vhusbdarm64[1314]: Server licensed to=unlicensed max_devices=1
Dec 09 21:32:53 jon-pi4-2 vhusbdarm64[1314]: Using large URB's
Dec 09 21:32:53 jon-pi4-2 vhusbdarm64[1314]: Listening on all network interfaces at TCP port 7575
Dec 09 21:32:53 jon-pi4-2 avahi-daemon[451]: Loading service file /services/vhusbd.service.
Dec 09 21:32:53 jon-pi4-2 vhusbdarm64[1314]: Found Full speed device [046d:c52b] "Logitech, USB Receiver" at address 113                       <--- Wireless keyboard?
Dec 09 21:32:53 jon-pi4-2 vhusbdarm64[1314]: Found High speed device [2109:3431] "0x2109, USB2.0 Hub" at address 11
Dec 09 21:32:54 jon-pi4-2 avahi-daemon[451]: Service "VirtualHere USB Sharing" (/services/vhusbd.service) successfully established.
Dec 09 21:33:19 jon-pi4-2 vhusbdarm64[1314]: 10.199.1.3 connected as connection 1 (Standard TCP)
Dec 09 21:33:44 jon-pi4-2 vhusbdarm64[1314]: Found Full speed device [046d:c24f] "Logitech, G29 Driving Force Racing Wheel" at address 112
Dec 09 21:35:00 jon-pi4-2 vhusbdarm64[1314]: Executed "" for onReset.046d.c24f
Dec 09 21:35:00 jon-pi4-2 vhusbdarm64[1314]: Device 112 [046d:c24f] BOUND to connection 1
Dec 09 21:35:00 jon-pi4-2 vhusbdarm64[1314]: Executed "" for onReset.046d.c24f
Dec 09 21:43:30 jon-pi4-2 vhusbdarm64[1314]: Executed "" for onReset.046d.c24f                                                            <--- Unplugged the G29 here?
Dec 09 21:43:30 jon-pi4-2 vhusbdarm64[1314]: Device 112 [046d:c24f] SURPRISE UNBOUND from connection 1
Dec 09 21:43:30 jon-pi4-2 vhusbdarm64[1314]: Unmanaging device 112 [046d:c24f] 

Client:

2024-12-09 19:11:27 INFO  :VirtualHere Client 5.8.0 starting (Compiled: Nov 26 2024 16:39:51)
2024-12-09 19:11:27 INFO  :Client OS is Windows 11 (build 22631), 64-bit edition
2024-12-09 19:11:27 INFO  :Using config at C:\Users\jonsh\AppData\Roaming\vhui.ini
2024-12-09 19:11:27 INFO  :IPC available at \\.\pipe\vhclient
2024-12-09 19:11:51 INFO  :Auto-find (Bonjour) on
2024-12-09 19:11:51 INFO  :Auto-find (Bonjour SSL) on
2024-12-09 19:15:05 INFO  :Drivers are old, they will be upgraded
2024-12-09 19:15:09 INFO  :Connected to the VirtualHere Client Driver (Version 2)
2024-12-09 21:27:11 INFO  :Server ping timeout, shutting down connection 1...
2024-12-09 21:27:11 INFO  :Connection 1 socket closed (rx)
2024-12-09 21:55:56 INFO  :Server ping timeout, shutting down connection 2...
2024-12-09 21:55:56 INFO  :Connection 2 socket closed (rx)

For context, I tested the VirtualHere Server with the laptop first, then tried with the Pi shortly after that. The client logs are not very verbose, I wonder if I can get more logs elsewhere. I got these by clicking on "System Messages".

Submitted by Michael on Tue, 2024/12/10 - 16:46

#13

Whenever the log shows SURPRISE UNBOUND it means that the usb device itself disconnected and it wasnt virtualhere or pulling the plug.

Do you have a pi5 to test? I suspect that works ok, the pi4 has some hardware limitations which were fixed in the pi5 hardware regarding USB. Specifically the RP1 chip is significantly better and than the old via chip they used to use. 

Submitted by jonshaw199 on Tue, 2024/12/10 - 18:02

#14

Interesting. Don't have a pi5 yet but will try when I get one. I appreciate all the help, the wife and kids love it.