So I am running bookworm, because the last time I tried bullseye on the pi5 did not go so well. Gil, that's interesting an interesting comment about bookworm turning off devices; sounds like something that should be restricted to win laptops,? and a big portion of pis being used are for headless server applications where such behavior could break all sorts of things. Also I am using the official pi5 power supply, and the sdr's and 7300 I've got plugged in to a powered hub. Also fwiw, I'm not using any usb3 ports to avoid noise issues. I knew going in to this that pi5 is still bleeding edge and bugs are likely... especially considering wide sweeping fundamental changes like gpio, xsession, pulse, etc. I'm still hoping I won't have to break down and use one of my pi4's on this... then I would likely be in the same boat figuring out how to get pi5 working with different sets of apps.
Thanks to my long term geek lifestyle, a have many sd cards, usb ssd's, and a nas I could use to save an image.?However as my luck turns out, I may not benefit from an image anyways. I let the cm108 digipeat wide1-1 overnight since it was seemingly stable for hours before bed time. I found it effectively frozen this morning (no vnc access), so I rebooted, accessed vnc, and took kids to school. I got back home 30min later the vnc server was crashed once again. This time, no apps were running at all when it crashed. So something got hosed recently, and I should probably redo the os anyways. Fortunately I have all? my pi's setup to rsync to my nas. So all of my important files like .config, log databases, assorted shell scripts, etc are safely backed up (and more importantly restoring those files has been successfully tested).
I do have that second pi5 ready to go, but it also has bookworm. To get my digital back on air I'll probably set that up with everything but direwolf, and redo the os on other one to experiment with direwolf.
