The other my Vero 5 popped up a notification for an update. After installing it, my remote no longer works and my library is empty.
I use a remote MySQL to coordinate two Vero boxes that load videos from a CIFS share so the empty library happens when there are network issues.
Restarting the ‘mediacenter’ service after a cold boot brings back my library, but the remote is still dead. Holding Home/OK causes the blue light to flash for a while, but it never pairs.
Last night another update popped up so I installed that, but it didn’t fix anything.
To summarize:
- From cold boot my library is empty, but
sudo systemctl restart mediacenter brings it back
- My Vero remote does not work and will not re-pair
- Other remotes like CEC and network-based (e.g., iOS apps) work
The only errors I can find in dmesg output is:
[ 11.597608] CIFS VFS: Error connecting to socket. Aborting operation.
[ 11.615500] CIFS VFS: Error connecting to socket. Aborting operation.
[ 11.637164] CIFS VFS: Error connecting to socket. Aborting operation.
[ 11.718244] CIFS VFS: Error connecting to socket. Aborting operation.
[ 11.749973] CIFS VFS: Error connecting to socket. Aborting operation.
That generates a bunch of “Unable to open database: kodi_video75 [2002](Can’t connect to MySQL server on ‘x.x.x.x’ (101))” errors in the logs after the cold boot, before restarting the mediacenter service.
Here is the specific build info, etc:
====================== UNAME =================== 0wwkXuO5
Linux verotvroom 4.9.269-80-osmc #1 SMP PREEMPT Sun Mar 2 14:02:42 UTC 2025 aarch64 GNU/Linux
---------------------- UNAME END --------------- 0wwkXuO5
====================== cmdline =================== 0wwYYuO5
console=ttyS0,921600 earlycon=aml-uart,0xfe07a000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 logo=osd0,loaded,0x7f800000 vout=1080p60hz,enable hdmitx=,444,8bit hdmimode=1080p60hz cvbsmode=576cvbs osmc.root_wants_resize= mac=94:cc:04:60:08:9a systemd.unified_cgroup_hierarchy=0 root=/dev/osmcroot rootfstype=ext4 quiet console=tty0 osmcdev=vero5
---------------------- cmdline END --------------- 0wwYYuO5
====================== Debian version =================== m4ls932a
11.11
---------------------- Debian version END --------------- m4ls932a
====================== OSMC Build Information =================== ps9k90Ws
OSMC filesystem assembled on jenkins at Mon 07 Aug 2023 03:24:13 PM UTC using Debootstrap version 1.0.123+deb11u1
---------------------- OSMC Build Information END --------------- ps9k90Ws
I have no idea where else to look for debugging info.
Try enabling wait for network on boot.
Otherwise this suggests a connectivity error.
Thanks, re-enabling “wait for network” fixed the library-on-boot issue!
The remote still doesn’t work — anything I can do to debug that further?
Have you tried a cold boot instead of reboots?
Yes, I put in a fresh battery in the remote and I’ve unplugged the Vero and waited a minute and plugged it back in several times.
The proximate cause was installing the update (or the ensuing reboot) because I used the remote to click “ok” to install the update. When it came back up after the update the remote didn’t work and hasn’t since. As far as I know the Vero hadn’t been rebooted for several months.
When Kodi firsts loads I see a mouse cursor in the upper-left corner that I haven’t noticed before (not that I’ve ever looked that closely). It disappears after a few seconds.
Do you have any other USB devices attached to the Vero?
Yes:
- Plugging a keyboard into the (black) USB2 hole works.
- Plugging a keyboard into the (blue) USB3 hole does not work.
I replaced two Vero 4Ks with two Vero 5s so I also have two old remotes and USB dongles lying around.
I tried every combination of USB dongle/hole/remote from the 4Ks on the 5, but none worked. If there is a way to un/re-pair those from the dongles I can give that go.
Here is the dmesg output from all the plugging/unplugging of keyboard and dongles:
[ 2510.054242] usb 1-2: new high-speed USB device number 2 using xhci-hcd
[ 2510.225394] usb 1-2: New USB device found, idVendor=05e3, idProduct=0608
[ 2510.225404] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2510.225409] usb 1-2: Product: USB2.0 Hub
[ 2510.257756] hub 1-2:1.0: USB hub found
[ 2510.260895] hub 1-2:1.0: 4 ports detected
[ 2510.574353] usb 1-2.4: new low-speed USB device number 3 using xhci-hcd
[ 2510.719276] usb 1-2.4: New USB device found, idVendor=04d9, idProduct=2013
[ 2510.719283] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2510.719286] usb 1-2.4: Product: USB Keyboard
[ 2510.719289] usb 1-2.4: Manufacturer:
[ 2510.745956] input: USB Keyboard as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2.4/1-2.4:1.0/0003:04D9:2013.0001/input/input9
[ 2510.815782] hid-generic 0003:04D9:2013.0001: input,hidraw0: USB HID v1.00 Keyboard [ USB Keyboard] on usb-xhci-hcd.0.auto-2.4/input0
[ 2510.828478] input: USB Keyboard as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2.4/1-2.4:1.1/0003:04D9:2013.0002/input/input10
[ 2510.894964] hid-generic 0003:04D9:2013.0002: input,hidraw1: USB HID v1.00 Device [ USB Keyboard] on usb-xhci-hcd.0.auto-2.4/input1
[ 2518.973625] usb 1-2: USB disconnect, device number 2
[ 2518.973637] usb 1-2.4: USB disconnect, device number 3
[ 2608.835860] usb 1-2: new low-speed USB device number 4 using xhci-hcd
[ 2609.014186] usb 1-2: New USB device found, idVendor=2017, idProduct=1688
[ 2609.014196] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2609.014201] usb 1-2: Product: USB Keyboard Mouse
[ 2609.014206] usb 1-2: Manufacturer: OSMC Remote Controller
[ 2609.024447] input: OSMC Remote Controller USB Keyboard Mouse as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.0/0003:2017:1688.0003/input/input11
[ 2609.086526] hid-generic 0003:2017:1688.0003: input,hidraw0: USB HID v1.10 Keyboard [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input0
[ 2609.095496] input: OSMC Remote Controller USB Keyboard Mouse as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.1/0003:2017:1688.0004/input/input12
[ 2609.156401] hid-generic 0003:2017:1688.0004: input,hidraw1: USB HID v1.10 Mouse [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input1
[ 2638.184902] usb 1-2: USB disconnect, device number 4
[ 2674.606988] usb 1-2: new low-speed USB device number 5 using xhci-hcd
[ 2674.785188] usb 1-2: New USB device found, idVendor=2017, idProduct=1688
[ 2674.785198] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2674.785203] usb 1-2: Product: USB Keyboard Mouse
[ 2674.785208] usb 1-2: Manufacturer: OSMC Remote Controller
[ 2674.800581] input: OSMC Remote Controller USB Keyboard Mouse as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.0/0003:2017:1688.0005/input/input13
[ 2674.867717] hid-generic 0003:2017:1688.0005: input,hidraw0: USB HID v1.10 Keyboard [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input0
[ 2674.876692] input: OSMC Remote Controller USB Keyboard Mouse as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.1/0003:2017:1688.0006/input/input14
[ 2674.937444] hid-generic 0003:2017:1688.0006: input,hidraw1: USB HID v1.10 Mouse [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input1
[ 2683.592475] usb 1-2: USB disconnect, device number 5
[ 2729.448002] usb 1-2: new low-speed USB device number 6 using xhci-hcd
[ 2729.625904] usb 1-2: New USB device found, idVendor=2017, idProduct=1688
[ 2729.625913] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2729.625919] usb 1-2: Product: USB Keyboard Mouse
[ 2729.625923] usb 1-2: Manufacturer: OSMC Remote Controller
[ 2729.640496] input: OSMC Remote Controller USB Keyboard Mouse as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.0/0003:2017:1688.0007/input/input15
[ 2729.709782] hid-generic 0003:2017:1688.0007: input,hidraw0: USB HID v1.10 Keyboard [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input0
[ 2729.719373] input: OSMC Remote Controller USB Keyboard Mouse as /devices/platform/fde00000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.1/0003:2017:1688.0008/input/input16
[ 2729.789038] hid-generic 0003:2017:1688.0008: input,hidraw1: USB HID v1.10 Mouse [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input1
[ 2739.615360] usb 1-2: USB disconnect, device number 6
Sorry – what I mean is have you been regularly using the USB ports?
The internal USB port is USB2.0 and not USB 3.0 (no real need to use USB 3.0), so that is surprising
The 4K/4K+ remote dongle won’t work with a V remote.
Ah, no, nothing plugged into the USB ports. Just power, HDMI and Ethernet.
To be clear: I have the dongles and the remotes from the 4K, so I was plugging the dongles from the 4K into the 5 and trying the remotes from the 4K that were paired with those dongles.
Right. That should work from a cold boot.
Ok, thanks, Vero 4K remote + dongle indeed works with Vero 5 from a cold boot.
Ideally I’d like to get the Vero 5 remote working again some day so we can still use the Vero 4K with a remote. But at least for now I don’t have to peck at my phone or use the stupid TV remote on the “main” Vero 5!
I tried the old Vero 4k remote + dongle too and I have regained the use of the remote!
I also noticed that seams that only one usb port is working. I say that because as I plug the dongle in the working port I see logs in dmesg, in the other one dmesg remain silent.
I can confirm, the port marked “OK” works with a keyboard and the 4k dongle on my Vero 5, but the port marked “Don’t Work” does not.
Hi same issue,
USB2 port works, USB3 port does not work.
I did not notice before, but it is not related to match update, because I did clean installation and in the USB3 port USB flash drive with Vero V image did not work so I had to use USB2 port, where installation USB worked.
Also my third party remote controller with dongle works in the USB2 port and does not work in the USB3 port.
Just dropping by to the whole ‘remote not working after the March update’ thing. The remote was working before the update, because I used it to start the update. Currently got a keyboard plugged into the socket marked ‘ok’ on the above diagram. Many boots done, cold boots, unplugging, re plugging. Anyway, logs as requested https://paste.osmc.tv/ufaveranam
