What's a good image to use now? [tutorial help as well]

[Der Geist der Maschine]

In rc.local echo disabled > /sys/devices/platform/dc-charger/power/wakeup

If I recall, that value gets reset after replugging the power supply back in. You need an udev rule that fires on every "add". Perhaps double check.

BTW, it had 5.4 on it, STR did NOT work, had to install 5.8.14, works,, I had nothing in /etc/tmpfiles.d/

You do not have a /etc/tmpfiles.d/force-s2idle.config file b/c it gets created in Daniel Thompson's Debian installer's first commit while you run Manjaro. As the file name suggests, that file enforces s2idle which barely saves power.

The first Debian installer version was using Kernel 5.4 and, as you pointed out, suspend to memory did not work at that time (well, s2idle worked but that does not count). His most recent Debian installer is using kernel version 5.7. That kernel version supports suspend to memory quite well and so that /etc/tmpfile.d/ should be removed, again. It was an oversight not having done that.

After several sleep/wake cycles it gets a bit slow, needs a reboot (>10?)

I never noticed that. Maybe you want to try out Debian Bookworm + Kernel 5.7 from https://github.com/schaecsn/pinebook-pro...-installer? In its simplest form you just run ./install-debian from the emmc. It installs Debian onto a blank micro sd which you can then test. If you like that kernel but not Debian, then you maaaaay be able to copy that kernel + modules over to Manjaro.

Are there any later kernels where STR works correctly?

I don't know. All this is kept secret by whoever is releasing Pinebook Pro specific kernels. If you want to put a lot of effort into this, then look at the kernel sources. I don't know how to get the kernel source from Manjaro, the kernel sources for Daniel Thompson's kernels are here https://github.com/schaecsn/pinebook-pro...d4124e862f.

[wdt]

So I gave this install tool a try, didn't work
Bad vermagic libfdt
Maybe because boot (partition) is empty except for a empty efi dir,
and no sign of a kernel or Image anywhere (this is with a temporary tow-boot uboot)

[Der Geist der Maschine]

So I gace this install tool a try, didn't work
Bad vermagic libfdt
Maybe because boot (partition) is empty except for a empty efi dir,
and no sign of a kernel or Image anywhere (this is with a temporary tow-boot uboot)

This installer install Mrfixit's uboot (see partition 1, 2 and 3)

Code:

$ sudo fdisk -l /dev/mmcblk1
Disk /dev/mmcblk1: 29.81 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5F5F39F0-0383-CE4B-9025-E8C8A8993C43

Device          Start      End  Sectors  Size Type
/dev/mmcblk1p1      64    16383    16320    8M Linux reserved
/dev/mmcblk1p2  16384    24575    8192    4M Linux reserved
/dev/mmcblk1p3  24576    32767    8192    4M Linux reserved
/dev/mmcblk1p4  32768  442367  409600  200M EFI System
/dev/mmcblk1p5  442368  1466367  1024000  500M Linux filesystem
/dev/mmcblk1p6 1466368 62519295 61052928 29.1G Linux filesystem

and it comes with a kernel, or course:

Code:

$ dir /boot
total 96313
drwxr-xr-x  5 root root    1024 Mar  9 22:56 .
drwxrwxrwx+ 4 root root    4096 Mar  9 23:12 ..
-rw-r--r--  1 root root  5248249 Sep 25  2020 System.map-5.7.0-2-pinebookpro-arm64
-rw-r--r--  1 root root  212744 Sep 25  2020 config-5.7.0-2-pinebookpro-arm64
drwxr-xr-x  2 root root    1024 Mar  9 22:01 efi
drwxr-xr-x  2 root root    1024 Mar  9 23:14 extlinux
-rw-r--r--  1 root root 17949952 Mar  9 22:50 initrd.img-5.7.0-2-pinebookpro-arm64
drwx------  2 root root    12288 Mar  9 21:18 lost+found
-rwxr-xr-x  1 root root    64591 Mar  9 22:56 rk3399-pinebook-pro.dtb
-rwxr-xr-x  1 root root 22149632 Sep 25  2020 vmlinuz-5.7.0-2-pinebookpro-arm64

a) it comes with its own uboot, so I assume your spi tow-boot may do things different? Suspend to sleep will probably only work with Mrfixit's uboot and not tow-boot (at least you said so and I believe I heard that elsewhere as well)

b) are you sure the install ran to the end, e.g. it did not abort. The last step is tasksel where you choose your desktop.

[wdt]

To a usb stick, tried both sockets, with a blanked emmc uboot
and got a emmc boot, but usb should have priority over emmc
(strings uboot.img |grep boot_target)
since the emmc uboot was not there I could use ONLY tow-boot on SD and force usb boot
It did not work
I thought the install was finished, there was no setup, I thought that would be with 1st boot

[Der Geist der Maschine]

To a usb stick, tried both sockets, with a blanked emmc uboot
and got a emmc boot, but usb should have priority over emmc
(strings uboot.img |grep boot_target)
since the emmc uboot was not there I could use ONLY tow-boot on SD and force usb boot
It did not work

Tow-boot on micro SD to boot Debian from usb. That's not a straightforward setup. There you are on your own.

I thought the install was finished, there was no setup, I thought that would be with 1st boot

Then the install aborted. That can happen if you press "enter" in advance so that it takes effect on the next prompt where "enter" means stop.

Quite a few folks succeeded in setting up Debian though Daniel Thompson's installer. You can do that, too

[wdt]

so, I tried again, twice
------
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 288.64 s, 7.4 MB/s
Setting up swapspace version 1, size = 2 GiB (2147479552 bytes)
no label, UUID=9bed6eb0-5672-4607-9c21-b58daadebb99
install: cannot create regular file '/home/d/pinebook-pro-debian-installer/sysimage/etc/fstab': No such file or directory


>>>> umount

umount: /home/d/pinebook-pro-debian-installer/sysimage/dev: no mount point specified.
umount: /home/d/pinebook-pro-debian-installer/sysimage/proc: no mount point specified.
umount: /home/d/pinebook-pro-debian-installer/sysimage/sys: no mount point specified.
[d@farm pinebook-pro-debian-installer]$

also tried as root
fatal: detected dubious ownership in repository at '/home/d/pinebook-pro-debian-installer'
To add an exception for this directory, call:

git config --global --add safe.directory /home/d/pinebook-pro-debian-installer

[Der Geist der Maschine]

so, I tried again, twice
------
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 288.64 s, 7.4 MB/s
Setting up swapspace version 1, size = 2 GiB (2147479552 bytes)
no label, UUID=9bed6eb0-5672-4607-9c21-b58daadebb99
install: cannot create regular file '/home/d/pinebook-pro-debian-installer/sysimage/etc/fstab': No such file or directory

You don't have a etc/ directory. That gets created by the installation of all the many Debian packages (they install some files into the etc/ directory thereby creating it).

Perhaps something went wrong in do_prep(). The code differs between Debian and Manjaro:

Code:

do_prep () {
        printf '\n\n>>>> Preparing to install\n\n'

        git submodule update --init

        PACKAGES="debootstrap pigz dosfstools"
        [ ! -z "$CRYPT" ] && PACKAGES="$PACKAGES cryptsetup"

        if [ -x "$(command -v apt-get)" ]
        then
                sudo apt-get install -y $PACKAGES
        else if [ -x "$(command -v pacman)" ]
        then
                sudo pacman -S --needed --noconfirm $PACKAGES
        else
                printf '\n\nWARNING: could not find a package manager.\n'
                printf 'Make sure the following packages are installed:\n'
                printf "  $PACKAGES\n\n"
        fi
        fi
}

Are you sure the "Preparing to install" phase went through fine?

I run the debian installer from Debian (initially from Mrfix't Debian 9 ... and nowadays from a debian bootstrap'ed Debian 10, 11 and 12). I never tried to run it from Manjaro. I'm sure many folks did it. There should be hope. Just analyze the output from the do_prep() phase (or from any other previous phase).

[wdt]

OK, I booted mrfixit on sd , and got same results, maybe there needs to be a "clean" command?
no errors shown until the fstab line

[Der Geist der Maschine]

OK, I booted mrfixit on  sd , and got same results, maybe there needs to be a "clean" command?
no errors shown until the fstab line

The clean command is

Code:

install-debian do_clean

Can you please insert "set -x" right after the first line? That makes the shell script very verbose. Post the whole output.


Also, how do you call the script, anyway? As mentioned earlier:

In its simplest form you just run ./install-debian from the emmc. It installs Debian onto a blank micro sd which you can then test.

What arguments do you pass to have it installed on usb?

[wdt]

$ ./install-debian BLKDEV=/dev/sda