Slarm64 on PinePhone [Unofficial Slackware ARM - 64 bit]

[acid andy]

This might be a bit of a tangent from the original purpose or the thread, but what does it take to get a SDDM login screen working?

I've not really done very much with Manjaro so I don't know any quick answer. On Slarm64 I built SDDM from source. Maybe the SDDM package that comes on the PinePhone has been altered or cut down? If so compiling it yourself might be the only option.

The sources are here: https://github.com/sddm/sddm

Or it could be another configuration thing.

https://wiki.archlinux.org/title/SDDM#Configuration

It's also worth taking a look in /var/log/sddm.log to see how far SDDM gets. On my PinePhone it got stuck interfacing with ConsoleKit but as you're on systemd that shouldn't be an issue.

It says here:

The configuration file for SDDM can be found at /etc/sddm.conf. See sddm.conf(5) for all options.

On systems controlled by systemd, everything should work out of the box  , since SDDM defaults to using systemd-logind for session management. The configuration file will therefore not be created at package installation time. SDDM offers a command for generating a sample configuration file with the default settings if you really want one:

# sddm --example-config > /etc/sddm.conf

One other thing I had to do on Slarm64 is add an "sddm" user to the "video" group but on Manjaro I would've thought that would already be set up...

[teneighty]

I thought the implementation was likely to be at least similar. I was wrong, and you are correct. The config I had removed has reappeared with a comment line that reads "# Created by Manjaro USER Module Handler".

I apologize for polluting the thread with this, but at least I can say that the Manjaro-ARM implementation of SDDM is indeed different, evidently actively managed buy this user module handler.

If I want to pursue this I might have to follow your Slarm64 guide! Thanks for your assistance!

[jfenn2199]

Curious as to the current state of this?  With Mara's image should one still have to copy over the boot directory, move kernel files, and reflash u-boot?  If so which Manjaro release was current with 5.9.12, I checked out the current Beta5 release of plasma mobile which has a newer kernel but noticed in it's boot configuration it had GPIO set options as the only major difference from uEnv.txt in Mara's image (could this be lack of SCP?).  Definitely eager to try this out just don't want to follow the wrong rabbit holes.

[acid andy]

first option without SCP for testing
README.TXT

slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-pinephone-build-20201206.img.zst
slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-pinephone-build-20201206.img.zst.sha256

@mara Sorry it took me so many months to test this image.  I've been buried with other projects.

Unfortunately the supplied uboot doesn't seem to work on my PinePhone. I just get a black screen with no LED lit. The one I took from Manjaro which uses an extlinux.conf file works.

It's very hard to debug as there's no output unless I can setup a serial link. Later I can try and swap in different boot files to see if the rest of the image works.

This is what I did, anyway:

Code:

# dd if=slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-pinephone-build-20201206.img of=/dev/mmcblk0 bs=512K status=progress

# dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8

[mara]

first option without SCP for testing
README.TXT

slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-pinephone-build-20201206.img.zst
slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-pinephone-build-20201206.img.zst.sha256

@mara Sorry it took me so many months to test this image.  I've been buried with other projects.

Unfortunately the supplied uboot doesn't seem to work on my PinePhone. I just get a black screen with no LED lit. The one I took from Manjaro which uses an extlinux.conf file works.

It's very hard to debug as there's no output unless I can setup a serial link. Later I can try and swap in different boot files to see if the rest of the image works.

This is what I did, anyway:

Code:

# dd if=slarm64-current-aarch64-xfce-rootfs-20201115-5.9.12-pinephone-build-20201206.img of=/dev/mmcblk0 bs=512K status=progress

# dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8

thank @acid andy , I updated the build config, I will update the image later

[mara]

update kernel and image.
slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst
slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst.sha256

[tllim]

update kernel and image.
slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst
slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst.sha256

Thanks :-)

[marodgz]

update kernel and image.
slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst
slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst.sha256

Thanks :-)

Hello @mara, I've executed ```zstdcat slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst > /dev/sdb``` and it finished just fine. After that I restarted my pinephone but it does not boot.

Am I missing an additional step?

Thanks

[acid andy]

Hello @mara, I've executed ```zstdcat slarm64-current-aarch64-xfce-pinephone-5.14.6-build-20210920.img.zst > /dev/sdb``` and it finished just fine. After that I restarted my pinephone but it does not boot.

Am I missing an additional step?

Thanks

If you're able to connect an external screen to your PinePhone, can you let us know if it boots with that?

I had an issue with the image not working with the PinePhone's own screen.

[acid andy]

It would be good to hear from anyone else running this on their PinePhone.

As mentioned above, on my PinePhone the latest image only outputs to an external monitor. We've not gotten to the bottom of this issue yet because @mara doesn't have a PinePhone to test it on and unfortunately I'm incredibly short of time and knowledge to fully diagnose it.

If any PinePhone user with more experience of kernels and u-boot wants to lend a hand it would certainly speed things up. Swapping in a different kernel and / or device tree may solve it.

Update: As a temporary workaround, the image boots on the PinePhone's screen after installing Megi's 5.16 kernel.