Hi Giedrius (and all) - Sorry for the long delayed reply. Life tends to redirect me for large amounts of time. As to my earlier statement where I mentioned the desktop, I should have said, “run startx”. But I have had several problems and some success at getting my configuration up and running with Berryboot and I’ll come back to the startx issue in a moment with more context.
First off, getting an image of Patchbox loaded via Berryboot: Giedrius was correct with his original suggestion of the steps listed in https://www.berryterminal.com/doku.php/berryboot/adding_custom_distributions . For some reason, as I had mentioned above, I could not get kpartx to work for me to save my life. I won’t go into the massive odyssey that’s taken me on, only to say, I kept looking back at the original solution presented and saying, “that addresses all the problems I’m facing if only I could get it to work!” Then just a few days ago, for grins I tried it again… and it worked flawlessly! I can only assume kpartx or some dependency got an update that fixed my original problem. Regardless, I now have two copies on I can boot from as well as Rasbian on my RPi4. However, the installations have not been flawless and I’m currently trying to trouble shoot the resulting symptoms.
The first error I catch on bootup is something about the EPROM access(?) failing. Looked like some utility and it certainly wasn’t a critical failure. Sorry I can’t be more specific, as it flashes by early and quickly during the boot and I haven’t looked at it in journalctl deeply yet.
Next is dphys-swapfile produces an error on boot. Subsequent install get-update operations all mention an error trying to use dphys-swapfile, though the failure seems non-critical So far, changes to the parameters within dphys-swapfile have not made any change to the problem. Some of my readings suggest this is an inconsequential matter, but it’s one of the few failures I see when Patchbox boots up. Could this be because I’m using Berryboot (or any bootloader like NOOBS)?
Bluetooth. I have been unsuccessful at configuring bluethooth. Using patchbox>Manage Bluetooth>status, I get:
bluetoothctl>list returns empty
bluetoothctl>show and most other commands return, “No default controller available”.
rfkill list all shows
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
I have been able to start and connect to the Pisound WiFi, but can not get beyond that.
Before mentioning my problem with startx,I should go into how the RPi4 is configured, as this not only might shed light with my startx problem, but perhaps the other problems I’ve already mentioned.
The RPi4 has 4Gb, has an OFFICIAL RASPBERRY PI 7" touch sensitive monitor attached in via the ribbon port, is housed in an OFFICIAL RASPBERRY PI enclosure that have been upgraded with a dual-fan, full body heat sink (OFFICIAL RASPBERRY PI?) where I have then added header pins to extent the GPIO so as to allow the attachment of the Pisound card. I was running a wireless keyboard off of a usb port, but switched it out for a straight up usb keyboard to see if that effected the bluetooth problem, which it didn’t. There’s many reasons why I’d like to get this configuration to work, but i’m fully aware this is not typical setup or intent of most successful Pisound installations I’ve seen to date. To further add insult to injury, I am trying to come up the learning curve quickly and know a smattering of information randomly gleaned by running into problems such as this. So any specific information I provide that’s of any use to anyone is probably more luck than skill! Please bear with me.
Needless to say, when I try to run startx, my terminal becomes a blank cursor and is unresponsive to any commands. I have tried plugging a monitor into HDMI 1 and 2, but get nothing there. 1 just has the rainbow screen and 2 remains off. My only option at that point is a power cycle. Startx is not my first priority however, as my goal is to get up and running with the Pisound.
I realize I’m throwing a lot of issues out there that might not be directly related to the original Berryboot question. I think that issue is close to being put to bed with a successful resolution and then move the other issues to other threads as needs be, but again, I look to yours and the hivemind’s guidance in this matter.