Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - lokomoko

Pages: [1]
1
Cosmo Communicator - Linux / SIM-PIN-Entry in Linux v3 / v4
« on: May 17, 2021, 05:22:27 am »
Planet computer's Linux for Cosmo Article does not mention how to enter the PIN for Telefonie and Messaging. It used to be recommended for v2 to use ofono-scripts to enter the PIN (I don't remember where). Up to now this still for me.

Still I'm wondering, wether there exists a more "out of the box" way of entering the PIN, since there's hardly any mentioning of ofono-scripts here in the forum and the packages is still not installed by default under v4.Any hints?

2
Cosmo Communicator - Linux / Prevent wearing internal flash storage?
« on: December 18, 2020, 04:52:00 am »
Running the Linux firmware (currently V3) for some days now and I observe the /var/log directory grow to impressive size of many GB as I already saw with V2. I can find a whole lot of "fuelgauged", "pmic_thread" and "battery_thread" related messages in syslog, messages and kern.log. I'm concerned that this - besides draining the battery - will wear the internal flash storage. Can anyone confirm that this is a problem or am I just a bit paranoid?

While /var/log/journal/ will grow to a max. of around 4GB (Thats what 'systemctl status systemd-journald' tells me), the text files seem to keep growing until they get log-rotated. All together the logging creates a continuos write-bandwith of 200 to 700 kB/s on mmcblk0p43 - around a GB per hour.

So I turned the text file output off by commenting out in /etc/rsyslog.conf. This did not reduce the bandwidth much, but at least it stopped growing the textfiles. Additionally I temporarily deactivated systemd-journald, which brought the storage bandwidth close to 0. So now I don't have to worry about wearing my internal storage anymore.

Still I would like to filter the above mentioned messages before systemd-journald produces write-bandwidth. This would allow me to turn back to normal (stock) logging.

Any ideas how to turn off that excesive kernel logging. Do I have to modify the boot commandline (which probably is not trivial) or can I switch it off in a runing system? What other strategies do you use to prevent wearing flash storage?

Thanks for any help in advance!

3
After upgrading to V23 the eSim is not being detected and as result no mobile connection (phone, mobile data) can be established.
The eSIM wallet tells me to set SIM 2 as a default. All the SIM settings under Settings -> Network & Internet -> SIM cards : are disable, so no way to change.

Sofar the eSim survived upgrades to V20, V21 and V22 without problems. I assume it still there but not detected properly.

Pages: [1]