Installation with Pisound

[tonyreid]

Hi! I'm trying to install pi-Stomp on rpi4 + pisound from modep. I've used this command to launch the installation process

Code Select Expand

nohup ./setup.sh -m > setup.log | tail -f setup.log

but I get the following error eventually

Code Select Expand


===== RT Kernel Install =====
+ set -e
+ sudo dpkg -i setup/sys/linux-image-5.15.40-rt43-v8+_arm64.deb
(Reading database ... 78074 files and directories currently installed.)
Preparing to unpack .../linux-image-5.15.40-rt43-v8+_arm64.deb ...
Unpacking linux-image-5.15.40-rt43-v8+ (5.15.40-rt43-v8+-1) over (5.15.40-rt43-v8+-1) ...
dpkg: error processing archive setup/sys/linux-image-5.15.40-rt43-v8+_arm64.deb (--install):
unable to make backup link of './boot/config-5.15.40-rt43-v8+' before installing new version: Operation not permitted
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
setup/sys/linux-image-5.15.40-rt43-v8+_arm64.deb


Is Pisound supported somehow?

[tonyreid]

I solved by removing the file config-5.15.40-rt43-v8+ before launching the setup.

[tonyreid]

Next one

Code Select Expand


pistomp@pistomp:~ $ sudo journalctl | grep 'error'
Sep 22 05:06:13 raspberrypi kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
Sep 22 05:06:14 raspberrypi alsactl[371]: alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
Sep 22 05:06:14 raspberrypi alsactl[371]: alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2
Sep 22 05:06:14 raspberrypi alsactl[371]: /usr/share/alsa/init/default:181: value write error: Operation not permitted
Sep 22 05:06:14 raspberrypi alsactl[371]: /usr/share/alsa/init/default:183: value write error: Operation not permitted
Sep 22 05:06:14 raspberrypi alsactl[371]: alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -2
Sep 22 05:06:14 raspberrypi alsactl[371]: alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:3 use case configuration -2
Sep 22 05:06:35 pistomp kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
Jan 24 23:44:52 pistomp kernel: bcm2708_fb: probe of soc:fb failed with error -2
Jan 24 23:44:53 pistomp kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
Jan 24 23:44:53 pistomp kernel: wm8731: probe of 1-001a failed with error -121
Jan 25 00:17:01 pistomp kernel: bcm2708_fb: probe of soc:fb failed with error -2
Jan 25 00:17:02 pistomp kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
Jan 25 00:17:02 pistomp kernel: wm8731: probe of 1-001a failed with error -121
Jan 25 14:43:55 pistomp kernel: bcm2708_fb: probe of soc:fb failed with error -2
Jan 25 14:43:56 pistomp kernel: wm8731: probe of 1-001a failed with error -121
Jan 25 21:38:55 pistomp kernel: bcm2708_fb: probe of soc:fb failed with error -2
Jan 25 21:38:56 pistomp kernel: wm8731: probe of 1-001a failed with error -121
Jan 25 22:09:56 pistomp kernel: bcm2708_fb: probe of soc:fb failed with error -2
Jan 25 22:09:57 pistomp kernel: wm8731: probe of 1-001a failed with error -121
pistomp@pistomp:~ $ sudo systemctl list-units --failed
  UNIT            LOAD   ACTIVE SUB    DESCRIPTION
● dnsmasq.service loaded failed failed dnsmasq - A lightweight DHCP and caching DNS server
● jack.service    loaded failed failed JACK2 Audio Server

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
2 loaded units listed.
pistomp@pistomp:~ $



[Randall (Admin)]

pi-Stomp has never had any intention to work with pisound.  The 3 audio cards that pi-Stomp does support (IQAudio, AudioInjector and HifiBerry) all share the same pinout, but pisound has its own which is not compatible.   The GPIO's that pi-Stomp expects to use for encoder inputs, footswitches, relays and the SPI bus for the LCD, pisound uses for its own purposes.  Doesn't mean you couldn't use it with pi-Stomp, but I believe you'd have to disable so many pi-Stomp facilities (the LCD being the most significant) that I'm not sure what use it would be.

But if you must, feel free to try.

Hardware aside, I'm also not sure if pisound can be installed upon Raspberry pi OS.  Do you know if that is possible?  If not, then any debugging of logs is futile because pisound would never be happy.