One question: what would I have to do to update from v2 go to v3? I’m not so much asking about the general Bookworm install but about Kernel and Kernel Repo. Is there any info to be found.
I’ve spent considerable time to get everything configured nicely and don’t really want to redo everything again (altough I have backups of the most important config stuff).
were you able to get it to work? I don’t have a uConsole but helped someone on my last image and incorporated that into this image. Is there any software or something that came with the stock image?
@OE4DNS Yes you can add the apt repo in the OP the regular one or if you’re feeling froggy you can use the bleeding one which is on 6.9.0. you’ll have to unhold the stock kernels and remove them you can leave the 6.6.30 one in just the linux-image and linux-headers. then sudo apt install clockworkpi-cm4-kernel
if you add the bleeding it will replace the kernel in my main bookworm repo.
Using sudo service uconsole-4g-cm4 start is the same as enable was on the old script. Once you start clthe service continue with the rest of the instructions on that page.
Thank you! Even after your message I did not see the link to the Kernel Repository. So I downlaoded, the image, unpacked it, looked at the APT sources and only then found the link. Which is of course in your topmost post. Silly me
Anyway this is solved. Are there any other changes (non UI configuration) from v2 to v3. The uconsole-4g-cm4 service is new of course, but anything else important?
The image was built using pi-gen and the kernel I compiled not pulling the stock kernel out and jamming another one in the image file. It’s missing the big apps like libre office, Wolfram alpha and other stuff. A few other apps added. Just a lot cleaner image then how we were making the images. @OE4DNS If it was me and you didn’t have to compile a bunch of custom stuff. I’d reflash, there’s still remnants of the old stock kernel in the v2 image.
@Rex, by using sudo service uconsole-4g-cm4 I don’t think the 4G Modem is powering on. When I use this command then I dont see a green LED blinking.
Below is what happens on the stock image. The only added step is sudo systemctl restart ModemManager otherwise Clockwork’s steps in their Wiki do not work.
In the mega link, in the kernel folder go to the userland scripts and download that 4G script. That’s the same one that I have trying to start the service. Run just that script by itself from your desktop and see if it works. I’m night of messed something up with the systemd file
I just tried the original script. It works (I did chmod +x before checking the permissions). Looking at the service, I don’t see the commands “enable” or “disable” being passed to the script.
Just got a chance to take a look and the script was executable. I’ll check out the service file and fix it when I get home and make a script to run to correct it. If you’ve already fixed it let me know, and share it so I can just put out a fix quickly.
Can you do me a favor. I put 2 new files in userland scripts in the mega link uconsole-4g and uconsole-4g-cm4.service download both of them change out the systemd service file and try sudo service uconsole-4g-cm4 start to enable and sudo service uconsole-4g-cm4 stop to disable. If that don’t work or if it does and you want to do it a different way put the uconsole-4g file in /usr/bin and just run the command uconsole-4g enable and uconsole-4g disable
Please try both and let me know how they both work so I can whip up a deb to fix.
I made it executable, mega must not preserve that.
I’ll pack them up into a deb and toss it on the repo, I’ll leave both options just in case someone wants it systemd or just wants a simple command.
can you do me a favor and remove the 4g files and sudo apt install uconsole-4g and run the systemd and the bash command and let me know how it goes. If you have my repo setup that is.
I’ve checked inside clockworkpi-cm4-kernel_6.6.30_arm64.deb and I am unable to understand the purpose of having duplicated files in boot/firmware/ and usr/lib/, as well as empty etc/ directory structures. Can you clarify?