|
PSA: Transition in progress - don't update !
|
11-06-2020, 09:51 AM
I also broke my mobian with update to 5.9 and after that found this thread - too late. But today I managed to update it more or less cleanly (using only instructions from apt update) and without reflashing. The only issue now I have 2 kernels - 5.8 and 5.9 (active), so 5.8 will need to manually uninstall.
11-06-2020, 11:50 AM
I am using Mobian on an SD card to port Kalliope. I upgrade using apt-get and managed to bork my device about 2 hours before finding this thread. It all seemed to work however, there was no sound, incoming or outgoing. Yesterday I once again upgraded. Not realizing that it was a full-upgrade situation I had some issues but in the end it all worked. "sudo apt-get full-upgrade"
5.9 kernel, sound works again, pretty good quality too, however, on incoming calls, the phone wakes up, rings, but does not allow me to answer! lol No problems calling back,  I have managed to load the dependencies (with one exception) for Kalliope and I have managed to build it. A 3 hour build, felso t like I was back in the 1990's lol, The one exception is the library libttspico-utils. This is related to the pico TTS application. The package exists in x86 Debian but I suspect I may have to build it for ARM. I figure I should ask before I do that if anyone knows if this package is available for ARM. Thanks to all who contribute LF 
11-07-2020, 04:44 AM
(This post was last modified: 11-07-2020, 11:09 AM by devrtz.
Edit Reason: fake news
)
(11-05-2020, 06:24 PM)HLing Wrote:(11-05-2020, 04:55 PM)a-wai Wrote:What to do when I get this?:(11-05-2020, 10:28 AM)bcnaz Wrote: Should we consider November 04 or 05 as a 'reference' release ? u-boot-install-pinephone is superseeded by u-boot-install-sunxi64
11-07-2020, 07:16 AM
11-09-2020, 02:58 PM
What to do when I get this?:
[quote pid='82556' dateline='1604622255'] sh: 1: /usr/sbin/u-boot-install-pinephone: not found [/quote] u-boot-install-pinephone is superseeded by u-boot-install-sunxi64 So no worries. I did a fresh install. followed with a u-boot-install-pinephone. After the self-inflicted complication that came from not having a fully charged pinephone (when will I ever learn?!), and remembering to use Disk utility from a newer computer so that I could "grow the rootfs", (Jumpdrive 5.0 did not automatically increase the rootfs, I think maybe because the older computer's Disk utility?) I was able to boot successfully into the new 5.9 kernel. By this weekend's update I was happily noticing that the battery life seemed stabilized quite a bit more. This morning, I confirmed that finally I was able to connect my pinephone to the laptop via USB, at which time the internet became available to the laptop. Hurray! (I could have used wifi, but really preferred wired tethering) So many good things in week one of the 5.9 kernel. Thank you!
11-10-2020, 09:59 AM
Hi,
i have seen this post to late -.- . I have forced the update via apt now nothing work anymore. Please paste an information then the next stable image with the breaking chnages is available. https://gitlab.com/mobian1/issues/-/issues/174
11-10-2020, 02:08 PM
(11-10-2020, 09:59 AM)lipkowski.be Wrote: Hi,The 20201104 nightly worked fine for me for the last days. I installed the 20201110 today and it seems really good. The nightlies are here.
11-10-2020, 07:00 PM
But if I install a Mobian nightly today, keeping it updated with APT is the same as re-flashing it with a new version? Is it possible to migrate from Nightly to "stable" afterwards without a complete re-flash?
11-11-2020, 04:53 AM
(11-10-2020, 02:08 PM)dukla2000 Wrote:(11-10-2020, 09:59 AM)lipkowski.be Wrote: Hi,The 20201104 nightly worked fine for me for the last days. I installed the 20201110 today and it seems really good. Hi, thanks i wait for the next stable version. Nightly are to unsecure for me, i don't want to crash my mobilephone again after a few days. My destionation is to use mobian as productive os. I think the best way is to create a stable repo tree to solve this problems in future. |
