failed to open VCHI service

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
huidbui25
Posts: 32
Joined: Tue May 07, 2019 7:07 pm
Location: DE

failed to open VCHI service

Post by huidbui25 »

Hi! When I check journalctl I stumble upon the following error message (in red colour) that I can't explain:
Feb 14 11:11:59 DietPi kernel: IR XMP protocol handler initialized
Feb 14 11:11:59 DietPi kernel: sdhci: Secure Digital Host Controller Interface driver
Feb 14 11:11:59 DietPi kernel: sdhci: Copyright(c) Pierre Ossman
Feb 14 11:11:59 DietPi kernel: mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
Feb 14 11:11:59 DietPi kernel: sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Feb 14 11:11:59 DietPi kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Feb 14 11:11:59 DietPi kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 14 11:11:59 DietPi kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 14 11:11:59 DietPi kernel: usbcore: registered new interface driver usbhid
Feb 14 11:11:59 DietPi kernel: usbhid: USB HID core driver
Feb 14 11:11:59 DietPi kernel: vchiq: vchiq_init_state: slot_zero = bdd80000, is_master = 0
Feb 14 11:11:59 DietPi kernel: [vc_sm_connected_init]: start
Feb 14 11:11:59 DietPi kernel: vc_vchi_sm_init: failed to open VCHI service (-1)
Feb 14 11:11:59 DietPi kernel: [vc_sm_connected_init]: failed to initialize shared memory service

Feb 14 11:11:59 DietPi kernel: [vc_sm_connected_init]: end - returning -1
Feb 14 11:11:59 DietPi kernel: Initializing XFRM netlink socket
Feb 14 11:11:59 DietPi kernel: NET: Registered protocol family 17
Feb 14 11:11:59 DietPi kernel: Key type dns_resolver registered
Feb 14 11:11:59 DietPi kernel: Registering SWP/SWPB emulation handler
Feb 14 11:11:59 DietPi kernel: registered taskstats version 1
Feb 14 11:11:59 DietPi kernel: uart-pl011 3f201000.serial: cts_event_workaround enabled
Feb 14 11:11:59 DietPi kernel: 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
Feb 14 11:11:59 DietPi kernel: mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
Feb 14 11:11:59 DietPi kernel: mmc-bcm2835 3f300000.mmc: DMA channel allocated
Feb 14 11:11:59 DietPi kernel: sdhost: log_buf @ bdd07000 (fdd07000)
Feb 14 11:11:59 DietPi kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Feb 14 11:11:59 DietPi kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
What is this? Can it be ignored or should it be worked on?

I have an rPi 3 Model B (armv71), DietPi 6.22.3, upgraded from Stretch to Buster.
huidbui25
Posts: 32
Joined: Tue May 07, 2019 7:07 pm
Location: DE

Re: failed to open VCHI service

Post by huidbui25 »

I finally found an answer. The error message doesn't seem to be critical, rather only informative.

More information here:
https://github.com/raspberrypi/firmware/issues/428
User avatar
MichaIng
Site Admin
Posts: 2293
Joined: Sat Nov 18, 2017 6:21 pm

Re: failed to open VCHI service

Post by MichaIng »

@huidbui25
Jep this is expected when running the RPi with 16M GPU memory share, which is default on DietPi, reasonably for server setups.

I was also annoyed by these messages (there are some more) which become even more if you enabled headless mode (Display Options > Resolution > Headless) to disable the whole framebuffer pipe. Solution was to disable VHCI and framebuffer from device tree completely by writing and enabling a custom dtoverlay:

Code: Select all

2019-06-14 02:58:49 root@micha:/var/log# cat /mnt/sda/micha.dts
/dts-v1/;
/plugin/;

/ {
        compatible = "brcm,bcm2835";

        fragment@0 {
                target-path = "/soc/mailbox@7e00b840";
                __overlay__ {
                        status = "disabled";
                };
        };

        fragment@1 {
                target-path = "/soc/fb";
                __overlay__ {
                        status = "disabled";
                };
        };
};
However besides disabling every display/graphics and audio capabilities, this even breaks vcgenmod, which we use in dietpi-config and such, so nothing for official support ;).
Post Reply