08-12-2021, 02:53 AM
(08-11-2021, 10:34 PM)calinb Wrote: ...
I'll use 01.003.01.003. for a while and then I'll try 01.002.01.002.
...
I have had 01.003.01.003 in my modem for many months (since about when there was a link here to @biktorgj repository). It broadly worked fine with Mobian, in the last months arch was unusable as the modem would vanish within an hour or 2. (Note I have a dual-boot setup so the 2 OS are using precisely the same modem.)
A few days ago I added my experience to the issue on the Pine64-arch git and was "nudged" that the modem-vanishing "trick" was more of a problem with 01.003.01.003. So I flashed 01.002.01.002 about 36 hours ago and since then have been running arch without a hiccup.
I just had a quick check through my journal and it seems the eg25manager code to regularly try recover the modem works as intended with 01.002.01.002 and (my suspicion) does not work with arch & 01.003.01.003?
YMMV
- ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.2 kernel, Openbox desktop) for general purpose daily PC.
- PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO & Arch/phosh on eMMC
- PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with Arch/SXMO on eMMC