New Allstar user here. Pi4 + Shari hat. A few days back, my node (after a reboot) would transmit insanely hot. Parrot used very descriptive language about how obnoxiously hot it was.
Go into Putty, Node Settings, Restart Asterisk, Parrot likes me again.
Lather, rinse, repeat. Shutdown, boot up, hot as a pistol. Restart Asterisk: life is good again.
Anyone have experience with this? Is something here corrupt?
Thanks much. I’m new enough that I might not understand some suggestions, so please bear with me.
This thing is driving me nuts. I would think that Asterisk would “restart” with each boot, so why it would start up bad, then need an Asterisk restart completely baffles me.
Yep, I just printed the entire file on paper in case I end up doing a virgin flash (so I can compare them). I know nothing about Linux, I'm more of a Windows guy; it's behaving as if it loads Asterisk from ie: a hard drive, then restarts from my SD. Impossible, I know.
If no one has experienced this and have some solution, I'll probably try configuring a new imaged SD card, but I'd really rather not.
I have had SD cards fail in a mode where they appear to accept writes but in fact it’s not been commited and after a reboot (even after several months of apparently running correctly) the contents revert to a prior state. It may be worth checking simpleusb.conf again after rebooting to see if your changes have stuck and if not then try a new card.
Well that is what happened here. Been fine for months. I have heard some horror stories about SD cards. The node I bought has a few USB sockets on it. Can you boot from one of those? Are they more reliable? I could write my newly flashed image to a USB and boot from it..
A Pi4 can boot from USB but it’s not something I’ve done and may not be supported by ASL3. I’d just replace the SD card; it’s not a common problem and despite having experienced it a couple of times I’ve also had Pis running 24/7 for many years without such issues.
Ok, I'll do a new SD. It's been so long, I forgot what I did to get it where I wanted it. I don't use Allmon or Supermon, but I do use Allscan. I think that was a “get app” type of thing. That'll be my morning coffee project. Last question… there are many YouTube videos on configuring Allstar on a node after installing a “first time” card. Do you have a favorite? One that is well detailed and accurate? If you have a recommendation, I'd appreciate it. There's a video on Allstar wiki, but some of it seemed not associated. Like a cmd to delete the Allmon password, and the system said one didn't exist.
Any Pi 4 or Pi 5 will boot from USB just fine. For all my non-portable Pis, I exclusively use USB-attached SATA SSDs. A good power supply can power it without issue. Just make sure you plug them into the blue high-speed USB port and not the black one (USB1). ASL works perfectly. I build the image and it's been well-tested on boot-from-USB.
So, here is a weird finale to this issue. Just for the heck of it, I put my SD card in a USB adapter and booted from that.
Four reboots later and all 4 started the node with perfect audio. So I think I'll just use that, but what the heck does that prove? Bad SB slot? Maybe I'll never know…..
To rephrase your issue: are you saying that your TX audio is HIGHER when you boot your node (rpi4 with a Shari hat) from the microsd card slot than when you boot using the same microsd card using an usb adapter?
If so, do you have another rpi4 you can try?
that is very strange! nonetheless it is probable. Wow.
better yet, back up your node, and reinstall Debian trixie and asl3 again…and finally restore your settings from the backup.
Your summation is correct, and you can also add the fact that when booting from the SD card (and getting super loud audio)… a restart of Asterisk alone corrects the audio for that up-time period. I've now done 8 or 9 reboots from the USB adapter and it's perfect every time. People in my talk group who know more about this than I do (which is everyone), say that it is possible that the Pi uses a different script when booting from the 2 different sources, instead of using the same script, just pointing to a different device. And that if so, the script for the SD load could be corrupt. So, for now, I'm running off the USB (it's a permanent install); boots perfectly every time, and faster.
Your idea on how to repair the SD side could be the answer, but quite honestly, I don't know how to do those things. (Noob here). If you have the time to share the resources where step by step instructions can be found; I'll pick a day, brew a pot of coffee and give it a shot.
Thanks for your help, and have a great Thanksgiving! 7-3
This is incorrect and they are speculating. All of ASL3 operates the same, consistent way regardless of media type. Most likely, you had a messed up SD Card. But, overall, if ultra portability isn't a concern, using an USB-attached SSD (not a USB stick!) is most robust and performant want to use a Pi.
