PINE64
Phone doesn't boot after latest kernel update - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Mobian on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=139)
+---- Thread: Phone doesn't boot after latest kernel update (/showthread.php?tid=10791)

Pages: 1 2


RE: Phone doesn't boot after latest kernel update - Boern - 08-04-2020

Compiling a kernel without https://gitlab.com/mobian1/devices/pinephone-linux/-/commit/60d630602f22d2db881a7cfd19e56eb23028cf39 fixed it.


RE: Phone doesn't boot after latest kernel update - bingo600 - 08-06-2020

When does one want to do a dist-upgrade ??



I just did an : apt update && apt upgrade -y   - And a reboot



Now i have :



mobian@mobian:~$ uname -a

Linux mobian 5.7-pinephone #1 SMP PREEMPT Tue Aug 4 13:57:41 UTC 2020 aarch64 GNU/Linu






If i do a dist-upgrade , would i be hit by the HDMI Bug ??





I have a PP CE


Ohh i see 9 packages have been kept pack , but they're marked unstable

The following packages have been kept back:
  libnss-systemd libpam-systemd libsystemd0 mobian-base mobian-phosh-base mobian-phosh-games
  mobian-phosh-phone systemd systemd-timesyncd


Well did a dist-upgrade , but these 4 are still held back:

4 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@mobian:~# apt list --upgradable
Listing... Done
mobian-base/unstable,unstable,unstable 0.1.9 all [upgradable from: 0.1.5]
mobian-phosh-base/unstable,unstable,unstable 0.1.9 all [upgradable from: 0.1.5]
mobian-phosh-games/unstable,unstable,unstable 0.1.9 all [upgradable from: 0.1.5]
mobian-phosh-phone/unstable,unstable,unstable 0.1.9 all [upgradable from: 0.1.5]



How do i update those ?
Why would i update to those (marked unstable) ?


The PP is still my 2'nd phone right now , but is 0.1.5 a "stable" , and 0.1.9 unstable ... How unstable ???


/Bingo


RE: Phone doesn't boot after latest kernel update - Boern - 08-06-2020

Looks like you are already on the latest kernel. Somehow I think I'm the only one with the bug.

You can update the packages that were held back with "apt install packagename".