The CM4 doesn’t have a realtime clock, so it needs to pull the time from your router. You might want to check to see if your router is providing time to network devices.
1 Like
Now I want to enable the 4G module. I wonder where to begin. Can any ClockworkOS user clue us in on how the module is enabled? The wiki only suggests keying in either one of two shell commands, but it does not go into detail what are the contents of those.
In this mega folder along side the kernel I have a script for the 4g card.
You’ll have to make it executable.
Let me know how it works for you.
2 Likes
Great Scott, it actually worked!
To anybody else trying this out, here are a few notes:
- You will need to install
raspberrypi-utilsfrom the package manager. Or at leastraspberrypi-utils-pinctrl. - Additionally, you may also need to install
libqmiandqmi-utilsto recognize the modem. - Use the
same shell script from ClockworkOS. Or thetext file from above link. - The module will not appear immediately after executing the script. Don’t panic if
mmcli -Lreturns nothing. Wait at least a minute before entering the command.
For GNOME Shell, you should see a “Mobile Network” entry on the left panel.
1 Like
Thank you for the feed back! Raspberry pi Debian includes pinctrl out the box with kernel 6.6 give or take I didn’t look into it. The GPIO command/package has been deprecated. So I helped another user by adapting the old script. I don’t have my uConsole yet (just a DevTerm) and i didn’t order a 4G card. If you have any input on it let me know so I can change/improve it.
Thanks for your help. I’ve used the script to enable the module a couple times now, and it’s consistently worked wonderfully. You should consider sharing the script on GitHub.
And as an update, the module does connect to the SIM’s mobile network, and even receives incoming calls. I’ve yet to test for mobile data, as well as SMS. But I’m sure those are shoo-ins. 
UPDATE: SMS tested, and working. Wow, I think I have a daily driver in my hands now…, if only I can figure why the unit dies at 30%.
FINAL UPDATE (for this post): Cellular just works. Calls, texts, mobile data confirmed. I’ve even used the unit as a hotspot. My uConsole is a certified keeper.
Glad to hear that the LTE module works!
I might be able to answer your problem with the power cutting out at 30%. That happened to me when the batteries I was using couldn’t keep up with the current drawn by the uConsole.
Switching to a pair of Samsung 35Es solved the problem and gave me a much longer runtime (7-8 hours, up from 2-3). I know that the LTE module will significantly add to the load, so maybe playing the battery lottery is not something that would help but at $5 per cell it might be worth a try.
1 Like
Impressive. I also think I won’t be able to reach those figures anyway, given I’m hopelessly accustomed to GNOME. But I will keep the model in mind on my next battery change. 3 hours is just about par with my laptop on light duty.
Eh, if I’m getting over 6 hours in performance mode playing Balatro I think you should be fine running GNOME.
For me, going from 2 hours to 7 hours moved it from a desk toy with a battery backup to a device I’d throw in a backpack and carry with me.
1 Like
ArchlinuxARM from Yatli work well. I’ll try to build an Alpine linux kernel it’ll be more lightweight then an arch based system
Next activity for me is to update the keyboard firmware using pmOS. Of course, it means getting down and dirty with the scripts provided here. So far, I replaced all mentions of dpkg to the equivalent commands in apk; but now I’m stumped with the correct location of the keyboard. In pmOS, /dev/ttyACM0 is assigned to the 4G module.
Mind you, I shall not be bothered to setup a ClockworkOS or Ubuntu instance to pull this off.
1 Like
I’m now also trying to troubleshoot the mystery of the poor Wi-Fi reception. I was getting quite frustrated as to why my Wi-Fi signal is still bad, despite:
- Having setup a spacer between the supplied Wi-Fi antenna and the chassis.
- Plugging
dtparam=ant2into/boot/usercfg.txt.
I was about to condemn the antenna, when I went ahead and installed the dtparam utility. I also double-checked using the old-fashioned ls /boot/overlays command. I found out that ant2 isn’t among the DT’s listed. Could this mean I’m still using the CM4’s internal antenna?
I don’t think you need to use dtparam=ant2 on PostmarketOS, it should just work with the external antenna. It works on my device, and the developers have wifi listed as working.
Did you get it working in the ClockworkPi distro? If not, you might have a faulty antenna, antenna connector, or CM4.
1 Like
I tried positioning the antenna this way, and I guess it’s a suitable patch for the moment. At worst, I may have to replace my antenna for this one. I shudder to think my CM4’s antenna is compromised. 
And if ever I’m looking forward to replace my CM4, it is to upgrade to a theoretical CM5.
If you’re not slowly turning your uConsole into the Ship of Theseus what are you even doing?
Anyway, always best to troubleshoot in order of least expensive intervention first.
Edit: Another thing you can try is reflow the solder on the antenna PCB. Those joints could be another failure point.
1 Like
Good call! I pressed hard against the solder point and saw the signal shoot up. I’ll have to work on that soon.
UPDATE: Thank the lucky stars, it isn’t my CM4 that’s borked. But in my frustration, I hammered the solder point in the hope that it fixes the problem. And it worked. (For a while. 
) If there’s no saving the antenna, I’m heading to the hobby shop for a replacement.
Yeah, I looked at mine and thought “that doesn’t look like a great solder joint and it’s on a piece of flexible material.”
I feel it’s been a week since I loaded postmarketOS on my uConsole. Sadly, I have to write it off as a disappointing experience.
Sure; I got calls, texts, and cellular data to work with it. But for some reason (and I can’t believe I’m saying this, but), the Wi-Fi reception is worse, and so is the general performance. I can barely get a smooth Discord experience. (And now you guys know why I chose to purchase a CM4 with 8GB RAM.) The OS chokes when I plug in a second screen in 4K. None of the downsides I mentioned are that much of a big deal when I hopped to Arch Linux ARM. In exchange, I have to put a little extra elbow grease to replicate the functions that worked with postmarketOS (i.e. calls and texts).
I do have hope, however, that these cons I listed can be addressed down the line. And I have much more faith in community-supported distros like this one, than the distros officially supplied by Clockwork. Nevertheless, therein lies the best feature of running a core without built-in storage. I can distro hop.
So, for now, I’m going to main my Arch Linux install. But I want to see what I can do to one day make my pmOS install run better. And my two bets are on the Wi-Fi firmware and the GPU driver.
Heh, I had a similar experience when I was trying to recreate my setup in Debian Bookworm today. The trackball behaved weird and erratic and for some reason Chromium was all flickery in Sway. I’m sure there are workarounds.
One thing I would recommend is setting the CPU governor to performance mode. It makes a significant difference.
1 Like
I have noticed that trackball behaves weird when hands are little sweaty. Keeping a clean cloth between finger and trackball for a while during use cleans both finger and trackball. Btw., has anyone got alpine working ?