02-20-2020, 01:43 PM
(02-20-2020, 05:47 AM)M@yeulC Wrote: Not sure there is a *lot* of value in image-hopping for now, for you or for devs.For now I am happy to stick with pmOS/phosh as I appreciate you pm folk are keeping damn close to the bleeding edge. Is there any way for us to report how close we are to the bleeding edge when making comments? Or just say "last update/upgrade 20 Feb 1900 GMT" or similar?
(02-20-2020, 06:12 AM)MartijnBraam Wrote:(02-20-2020, 05:10 AM)dukla2000 Wrote: Failing to have wifi disabled then ofonoctl wan --connect seems to fail most of the time, or if it works DNS resolution fails on mobile broadband if you later disable wifi.
If modemmanager is in the default runlevel then minimal chance of the 3 ofonoctl commands completing OK, for me even the poweron mostly fails
Interesting, how does ofonoctl wan --connect fail exactly when wifi is enabled? do you get a stacktrace?
I need to retract that line about WiFi enabled causing problems Just did 3 boots and ran the sequence I listed with no problems!Now to put modemmanager back in the default runlevel and find out if I need to eat more of my own words!
pmOS/phosh last update/upgrade 20 Feb 1900 UTC
- 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