Skip to content
Just have got the pikvm-a8 | Geekworm

Just have got the pikvm-a8


  • biuld it based on the howto video

    but it is not working.

    the video is not detcted.

    is there a way to show if the capture device is working.

    the other cracy thing is the pacakge looked used when i got it from amazon.

    it looks like the X630 HDMI to CSI-2 has a problem the led on the device in always red.

    wfg

    Mario



  • [ 12.974083] mc: Linux media interface: v0.10 [ 13.013149] videodev: Linux video capture interface: v2.00 [ 13.036612] i2c_dev: i2c /dev entries driver [ 13.046317] systemd-journald[250]: Received client request to flush runtime journal. [ 13.073233] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. [ 13.412943] iproc-rng200 fe104000.rng: hwrng registered [ 13.423072] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 13.424252] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 13.439046] rpivid_hevc: module is from the staging directory, the quality is unknown, you have been warned. [ 13.452426] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 13.461081] rpivid feb10000.codec: Device registered as /dev/video19 [ 13.480241] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. [ 13.481385] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. [ 13.509980] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned. [ 13.531466] bcm2835-codec bcm2835-codec: Device registered as /dev/video10 [ 13.539112] bcm2835-codec bcm2835-codec: Loaded V4L2 decode [ 13.547165] bcm2835-codec bcm2835-codec: Device registered as /dev/video11 [ 13.547769] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13 [ 13.559119] bcm2835-codec bcm2835-codec: Loaded V4L2 encode [ 13.568152] i2c i2c-22: Added multiplexed i2c bus 0 [ 13.577728] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14 [ 13.585705] bcm2835-codec bcm2835-codec: Device registered as /dev/video12 [ 13.596403] bcm2835-codec bcm2835-codec: Loaded V4L2 isp [ 13.599153] i2c 10-000f: Fixing up cyclic dependency with fe801000.csi [ 13.612228] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15 [ 13.613832] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16 [ 13.631069] bcm2835-isp bcm2835-isp: Register output node 0 with media controller [ 13.641135] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller [ 13.652739] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller [ 13.655966] tc358743 10-000f: Consider updating driver tc358743 to match on endpoints [ 13.670994] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller [ 13.680609] bcm2835-codec bcm2835-codec: Device registered as /dev/video18 [ 13.688617] bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx [ 13.698551] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 13.698656] bcm2835-codec bcm2835-codec: Device registered as /dev/video31 [ 13.716198] bcm2835-codec bcm2835-codec: Loaded V4L2 encode_image [ 13.721986] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 13.731067] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video20 [ 13.758572] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video21 [ 13.771625] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video22 [ 13.783729] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video23 [ 13.794093] bcm2835-isp bcm2835-isp: Register output node 0 with media controller [ 13.803980] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller [ 13.813443] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller [ 13.823332] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller [ 13.847269] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp [ 13.847724] tc358743 10-000f: tc358743 found @ 0x1e (i2c-22-mux (chan_id 1)) [ 13.866248] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 13.873560] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 13.889667] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2 [ 13.890855] i2c i2c-22: Added multiplexed i2c bus 10 [ 13.892308] usbcore: registered new interface driver brcmfmac [ 14.022335] rtc-pcf8563 1-0051: pcf8563_write_block_data: err=-121 addr=0e, data=03 [ 14.031245] rtc-pcf8563 1-0051: pcf8563_probe: write error [ 14.037375] rtc-pcf8563: probe of 1-0051 failed with error -5 [ 14.052057] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [ 14.058670] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: ,errors=remount-ro. Quota mode: none. [ 14.116708] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 14.126789] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 14.142360] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Nov 1 2021 00:37:25 version 7.45.241 (1a2f2fa CY) FWID 01-703fd60 [ 14.148492] Bluetooth: Core ver 2.22 [ 14.159912] NET: Registered PF_BLUETOOTH protocol family [ 14.165811] Bluetooth: HCI device and connection manager initialized [ 14.172750] Bluetooth: HCI socket layer initialized [ 14.178146] Bluetooth: L2CAP socket layer initialized [ 14.183665] Bluetooth: SCO socket layer initialized [ 14.295182] EXT4-fs (mmcblk0p4): orphan cleanup on readonly fs [ 14.303740] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: ,errors=remount-ro. Quota mode: none. [ 19.234352] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay) [ 19.245081] bcmgenet fd580000.ethernet eth0: Link is Down [ 20.808989] Mass Storage Function, version: 2009/09/11 [ 20.814569] LUN: removable file: (no medium) [ 20.828816] dwc2 fe980000.usb: bound driver configfs-gadget [ 23.437384] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 23.446248] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 23.542826] EXT4-fs (mmcblk0p2): re-mounted. Opts: ,errors=remount-ro. Quota mode: none. [ 23.887420] EXT4-fs (mmcblk0p2): re-mounted. Opts: ,errors=remount-ro. Quota mode: none. [ 26.067971] EXT4-fs (mmcblk0p4): re-mounted. Opts: ,errors=remount-ro. Quota mode: none. [ 26.410282] EXT4-fs (mmcblk0p4): re-mounted. Opts: ,errors=remount-ro. Quota mode: none. [ 36.317290] cam-dummy-reg: disabling [ 58.365889] systemd-journald[250]: Oldest entry in /run/log/journal/6817026af9334cf4b81422dc2f45c090/system.journal is older than the configured file retention duration (1month), suggesting rotation. [ 58.383954] systemd-journald[250]: /run/log/journal/6817026af9334cf4b81422dc2f45c090/system.journal: Journal header limits reached or header out-of-date, rotating. [ 275.267574] use of bytesused == 0 is deprecated and will be removed in the future, [ 275.275201] use the actual size instead.


  • found the culprid it was the included 30cm hdmi cable that had the problem. after using a different cable everything is working.


  • The content provides a detailed account of the issues faced with the X630 HDMI to CSI-2 device, highlighting the importance of checking the functionality of capture devices. Mario’s thorough documentation of the problem, including the always-red LED indicator and the condition of the package, offers valuable insights for troubleshooting and improving future purchase experiences. 

    Read more: https://raspberrypi.stackexchange.com/questions/85609/install-libssl1-0-dev-package-on-slice masters-raspbian-stretch


  • @Drew Maddox Thanks


  • @ word hurdle The PiKVM-A8 is a powerful KVM-over-IP solution.


  • @Sprunki Retake I also encountered the same problem with the X630 HDMI to CSI-2 device—the red light was always on and no video was received, even though I followed the video instructions exactly. Hopefully there will be a firmware update or clearer debugging instructions to help users check if the device is working or not.


  • It sounds like you're having trouble with your X630 HDMI to CSI-2 capture device. The red LED and the fact that the video isn't being detected suggest a problem with the device itself. Since the packaging looked used, it's possible you received a defective unit.

    Here's how you can check if the capture device is working:

    1. Try a different HDMI cable and source: Rule out a faulty cable or video source.
    2. Check your software settings: Make sure your software is configured to recognize the capture device as a video input.
    3. Look for the device in your computer's device manager: On Windows, you can find this by searching for "Device Manager" in the start menu. See if the X630 device is listed and doesn't have any error symbols. On other operating systems, the method for finding a list of connected devices may be different.
    4. Test on a different computer (if possible): This will help determine if the problem is with the device or your specific computer setup.

    If none of these steps work, and the LED remains red, the device is likely faulty. Given the used packaging, you should contact Amazon for a replacement or refund.


Please login to reply this topic!
close
close
close
I have a question
sparkles
close
product
Hello! I am very interested in this product.
gift
Special Deal!
sparkles