No Video on new device

Hi,

for my first try with PiKVM, i bought a Geekworm PiKVM A3 Kit on Amazon ( Amazon.de ) without being aware of not having bought a “real” PiKVM.

The Kit contains a HAT, a HDMI IN Daugherboard and an OLED display on a third PCB.. The device boots up just fine, I can log into the web interface, I can ssh into the device, and v4l2-ctl -d /dev/kvmd-video –all shows the data of the signal that comes in via the HDMI in port. And, when I change the resolution of the notebook delivering the HDMI picture, v4l2-ctl’s output changes accordingly.

This is for me the sign that the hardware is in order and - most important - the ribbon cable between the Pi and the HDMI in daugterboard is correctly installed. Right?

However, the stream window stays dark. The title says “WebRTC H.264 - No signal / 1920x1080 / 0 kbps / 0 vps dynamic”. The resolution is correct and matches what the notebook is putting out (at 50 Hz). Tried with different browsers including a naked firefox and chromium.

The log repeats:

Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => ================================================================================
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.149 ] -- Using V4L2 device: /dev/kvmd-video
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.149 ] -- CAP: Using capture type: single-planar
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.149 ] -- CAP: Using input channel: 0
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.166 ] -- CAP: Detected DV-timings: 1920x1080p50.00, pixclk=148500000, vsync=45, hsync=720
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.209 ] -- CAP: Using resolution: 1920x1080
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.210 ] -- CAP: Using format: RGB24
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.210 ] -- CAP: Using format swap: RGB24 -> BGR24
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.210 ] -- CAP: Querying HW FPS changing is not supported
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.210 ] -- CAP: Using IO method: MMAP
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.239 ] -- CAP: Requested 5 device buffers, got 5
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.251 ] -- CAP: Capturing started
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.251 ] -- Using JPEG quality: 80%
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.251 ] -- Creating pool JPEG with 3 workers ...
Aug 23 14:20:26 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2208.253 ] -- Capturing ...
Aug 23 14:20:27 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- ERROR [2209.254 ] -- CAP: Device select() timeout
Aug 23 14:20:27 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2209.354 ] -- Destroying workers pool JPEG ...
Aug 23 14:20:27 pikvm kvmd[572]: kvmd.apps.kvmd.streamer INFO --- => -- INFO [2209.389 ] -- CAP: Capturing stopped

What am I doing wrong? I would appreciate any hints.

Greetings, Marc

Hi Marc, and welcome to our forum.

We would love to help, but unfortunately we can’t reproduce your problem on our hardware, so it looks like it’s something specific for Geekworm. Perhaps you can get better traction with their support.

Cheers,
Nick

I thought this was the support forum for the open source software, and hoped that the developers would be able to give some debugging advice. Am I wrong here?

Greetings, Marc

Not quite. This is the support forum for open source software (kvmd) running on particular hardware. Your problem does not look like it’s just software related, that’s why I suggested you try to contact the manufacturer of your device.

Thank you for setting me staight on this. I have in the mean time noticed that I was using a V4 image on V3 hardware, because I thought that the V3/V4 were refering to software releases. They don’t, they refer to the hardware version they support, and my device is a V3. With the correct software image, everything works fine. Thank you for helping and your patience.