Hi, we finally got to porting our image to core 18. And we have run into a couple of issues - I updated the assertion with base18, new gadget snap, and pi-kernel. (The target device is Pi 3).
- So the first issue is that our snap can’t start because of this error:
Sep 19 20:31:04 localhost screenly-client.viewer: * failed to open vchiq instance
I remember having this error in the early 16 days, we initially had to run the snap in devmode and then the fix came out. OpenGL interface was added I think?
Not sure, but I did check that interface is connected and it certainly is. Below is a part of
snap interfaces output.
So no idea what changed. The one thing I had to do for new gadget snap (we had old pi3 gadget snap used + our changes) - was building with sudo. This is the command used to actually build the gadget snap:
sudo snapcraft snap --target-arch=armhf --destructive-mode
I did try building it without sudo but it fails:
Building gadget Cross compilation detected; using pre-defined sources list make: Entering directory '/home/sergey/work/pi-gadget' mkdir -p "/home/sergey/work/pi-gadget/stage"/apt cp "./helpers/sources.list.cross" ""/home/sergey/work/pi-gadget/stage"/apt/multiverse.sources.list" sed -i "/^deb/ s/\bfocal/bionic/" ""/home/sergey/work/pi-gadget/stage"/apt/multiverse.sources.list" sed -i "/^deb/ s/$/ multiverse/" ""/home/sergey/work/pi-gadget/stage"/apt/multiverse.sources.list" apt-get update \ -o Dir::Etc::sourcelist=""/home/sergey/work/pi-gadget/stage"/apt/multiverse.sources.list" \ -o APT::Architecture=armhf 2>/dev/null Reading package lists... Done make: *** [Makefile:70: multiverse] Error 100 make: Leaving directory '/home/sergey/work/pi-gadget' Failed to run 'override-build': Exit code was 2.
Any ideas what can be causing this issue?
- And the second issue is as important - when running on Pi 3B+ there is no ethernet connection.
root@localhost:/# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether b8:27:eb:0c:d1:a1 brd ff:ff:ff:ff:ff:ff
root@localhost:/# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DORMANT group default qlen 1000 link/ether b8:27:eb:0c:d1:a1 brd ff:ff:ff:ff:ff:ff
When image is starting up there is a message about netplan failing. Not sure if relevant.
In our old gadget snap we had this code:
RmBXKl6HO6YOC2DE4G2q1JzWImC04EUy: ethernet.enable: true
I moved it to the
pi-gadget as well but it does not seem to have any effect. Did something change here? DO we need to change this stuff to get it working?