+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone Pro (https://forum.pine64.org/forumdisplay.php?fid=177)
+--- Forum: PinePhone Pro Software (https://forum.pine64.org/forumdisplay.php?fid=179)
+--- Thread: July 1 upgrade of Mobian Bookworm boot loops. (/showthread.php?tid=19326)
July 1 upgrade of Mobian Bookworm boot loops. - mburns - 07-02-2024
It must be the kernel update then. I can continue to boot from the Trixie installation on the main chip. And then use my rescuemobian script to continue trying the upgrades on the Bookworm installation. Edit this to your installation, and then continue to try upgrades from this temporary environment.
Code:
#! /bin/bash
cd /home/d1/root
mount /dev/mmcblk1p1 /home/d1/boot
mount --bind /proc /home/d1/proc
mount --bind /sys /home/d1/sys
mount --bind /dev /home/d1/dev
mount --bind /run /home/d1/run
chroot /home/d1RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 07-14-2024
(07-02-2024, 10:41 AM)mburns Wrote: It must be the kernel update then. I can continue to boot from the Trixie installation on the main chip. And then use my rescuemobian script to continue trying the upgrades on the Bookworm installation. Edit this to your installation, and then continue to try upgrades from this temporary environment.
Code:#! /bin/bash
cd /home/d1/root
mount /dev/mmcblk1p1 /home/d1/boot
mount --bind /proc /home/d1/proc
mount --bind /sys /home/d1/sys
mount --bind /dev /home/d1/dev
mount --bind /run /home/d1/run
chroot /home/d1
Never mind then. I will treat this as a failing microSD card, and just remove it. Updates are slow. This is the second chip to be removed for this.
RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 08-13-2024
So. Updating another installation of Mobian on another microSD card causes a failure to boot again, Bookworm or Trixie. Has support in Mobian for booting from the removable chip lapsed?
RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 09-26-2024
(08-13-2024, 06:26 AM)mburns Wrote: So. Updating another installation of Mobian on another microSD card causes a failure to boot again, Bookworm or Trixie. Has support in Mobian for booting from the removable chip lapsed?
I repaired the boot menu file on the second chip. This was needed to get a second boot on the PPP with recent Mobian. /boot/extlinux/extlinux.conf is the file that needs repair for the incomplete menu entry.
RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 10-19-2024
Today, October 19, 2024, I had to disable the GDM service after a Debian/Mobian update. I used ssh to fix the usability issue.
RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 10-26-2024
(10-19-2024, 01:54 PM)mburns Wrote: Today, October 19, 2024, I had to disable the GDM service after a Debian/Mobian update. I used ssh to fix the usability issue.
Today, October 26, 2024, an automatic update of Debian disabled Mobian Trixie. I had to copy in a spare copy of /etc/systemd/system to recover.
RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 01-08-2025
The 6.12 linux kernel updates on Mobian are simply not supporting the PinePhone Pro. The backlight control is failing and everything is laggy.
I go into the extlinux.conf and specify the 6.6 kernel as default - very zippy by comparison.
RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 01-27-2025
(01-08-2025, 12:14 PM)mburns Wrote: The 6.12 linux kernel updates on Mobian are simply not supporting the PinePhone Pro. The backlight control is failing and everything is laggy.
I go into the extlinux.conf and specify the 6.6 kernel as default - very zippy by comparison.
The 6.12 kernel might be OK now.
The Console app confused me. This is because the arrow keys are now superseded by gestures on the space key.
RE: July 1 upgrade of Mobian Bookworm boot loops. - mburns - 02-18-2025
With the Mobian updates from the command line (Tues Feb 18 2025):
# apt update && apt upgrade
I periodically must enter the following command to restore fast processing and prevent hangs:
# systemctl disable gdm
RE: July 1 upgrade of Mobian Bookworm boot loops. - Kevin Kofler - 02-25-2025
If you are using another display manager, and you cannot uninstall gdm due to dependencies, then try:
Code:
sudo systemctl mask gdm