Slarm64 on PinePhone [Unofficial Slackware ARM - 64 bit]

[donchurch]

Greetings,


I flashed Mara's latest images to the internal storage and to a micro sdhc using both the /dev/mmcblkx and the UUID variables via editing the two file specified in Mara's readme. I also tried using a boot partition and setting the boot flag all with no luck booting. The LED shines red immediately for a few seconds and then nothing. I have an external monitor connected and serial connection wired with a terminal monitoring the connection which spit out some hex numbers a time or two.


Searching online I found that U-boot is not needed.


I used PMOS running from the sd card to flash the image to internal memory noticed that the fstab and uEnv.txt file already had the correct UUID mount points in them thus the command directed to the fstab had no effect.

Also I noticed that when flashing to the sd card with dd using 1M variable the expanded size on the disk is like 13GB but on the internal using 10M it's about 7GB.

For some reason, while logged into this site now, whenever I click on any of Mara's links I get a "forbidden" error and that I don't have permission. Maybe it's my browser.
That's all I can think of for now.

[donchurch]

While exploring other os's I noticed Maemo Leste has quite a bit of functionality as of late and it's based on Devuan which is possibly the only distribution besides Slack that is systemd free and it's my current desktop OS having left Slack because of the lack of mainstream app support.  In the install process (partial copy below) it has a step that seems may help with Slarm64.  I obviously don't know the in's and out's but if these steps are necessary then it seems they should be worked into the process.

eMMC Installation
Some notes have been adapted from the Pine64 Wiki.
Preparing the .img file for eMMC boot
Download the .img.xz version of the image and extract it:
$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

The image, by default, points to

Code:

/dev/mmcblk0

for SD cards, which must be modified to point to

Code:

/dev/mmcblk2

for the eMMC. To start, mount the image to a loop device.
$ sudo losetup -P /dev/loop0 maemo-leste-*-arm64-pinephone-*.img

Mount the second partition to /mnt and the first partition to /mnt/boot and enter /mnt:
$ sudo mount /dev/loop0p2 /mnt
$ sudo mount /dev/loop0p1 /mnt/boot
$ cd /mnt

Use the editor of your choice to edit

Code:

/mnt/etc/fstab

, replacing

Code:

/dev/mmcblk0

with

Code:

/dev/mmcblk2

.
Now we need to edit

Code:

boot.scr

. For that you will need to download

Code:

boot.txt

from Maemo Leste github:
$ cd /mnt/boot
$ sudo wget https://raw.githubusercontent.com/maemo-...r/boot.txt

Now we do the same step as we did for the fstab, replacing

Code:

/dev/mmcblk0

with

Code:

/dev/mmcblk2

in

Code:

boot.txt

.

To regenerate

Code:

boot.scr

you need to install

Code:

u-boot-tools

first to be able to use mkimage.
Regenerate

Code:

boot.scr

:
$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

[donchurch]

So, still trying things I re-flashed the image to an sdhc card and verified that the two files to edit point to mmcblk0p1 which they do without editing.  When trying to boot Slarm, instead Maemo which is installed on internal  memory boots up.  Initially I though the Maemo overwrote the mmc0boot space but maybe it's because Slarm failed and it fell back to main memory.  I started messing with copying Manjero boot files etc but since it uses a boot partition and the sdhc with Slarm has just the root things became more complicated to deal with than I have ambition for now.  I found like 5 u-boot.bin files in Manjero but they use 2 partitions which I realized after I flashed one the seek 8k or whatever that was.  I'm a little burnt out for now but maybe later.  The Maemo-Leste is kinda cool since I have an N900 laying around that it replicates but I can't get the phone or data to work even though it shows registered and connected in the modem status.

[donchurch]

So, I did learn that the serial output displays the details of the boot process rather that just responding to command strings which was my initial thought but despite a lot of time and configuration I can't get intelligible output to my PC.  It's just like you Acid Andy struggled with per your post I found elsewhere on the subject.  I don't have another electronic device to connect to that I can think of and can't find a solution to invert the signal that is in my recreational league.  I've written serial interface code to interact with measuring instruments but I don't see an application here besides, I read two post where the Pinephone was connected to a PC and I've tried it with direct serial cable and several usb to serial adapters and still only a ton of garbage characters to read.

I've re-re-flashed the latest image to an sdhc card, verified fstab and mmcblk0p1 and when trying to boot, it almost immediately falls back to the emmc installation with Maemo-Leste.

It's interesting that the LED now starts out green rather that red and also when trying to adjust the baud rate the setserial function has no effect and constantly shows the baud rate at 1500000 but stty will show the baud rate at whatever I set it to using stty.

My only thought is that my usb to serial converters are too old and don't support the baud rate and maybe newer ones might have a signal inverter function.

[donchurch]

Greetings again,

With the tinkering I have confirmed, I believe that my Pinephone is locked in at 1.5mb/s and I had to get a newer usb serial converter.  No other contraptions needed and so this is the output when trying to boot from the micro sdhc card but falling back to the built-in Maemo-Leste install.  All I did was flash the card with the image and confirm that the fstab file had the correct partition for root.  Here's a copy:

#
# /etc/fstab: static file system information
#
# <file system>        <mount point>  <type>  <options>                        <dump> <pass>
shm                    /dev/shm        tmpfs    defaults                        0      0
devpts                /dev/pts        devpts  noexec,nosuid,gid=tty,mode=0620  0      0
sysfs                  /sys            sysfs    defaults                        0      0
proc                  /proc          proc    defaults                        0      0
#
#/dev/#EXT4FS_BOOT#    /boot          ext4    errors=remount-ro                0      1
#/dev/#SWAP#          swap            swap    defaults                        0      0
#/dev/#EXT4FS_ROOT#    /              ext4    errors=remount-ro                0      1
#/dev/#EXT4FS_HOME#    /home          ext4    defaults                        0      2

/dev/mmcblk0p1    /          ext4    noatime,nodiratime,data=writeback,errors=remount-ro      0      1



And here's the booting output going into Maemo:

U-Boot SPL 2023.07-rc6-sun50iw1 (Sep 24 2023 - 21:04:22 +0300)
DRAM: 3072 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.9(release):v2.9.0
NOTICE:  BL31: Built : 21:03:41, Sep 24 2023
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x2093dd8, model: Pine64 PinePhone (1.2)


U-Boot 2023.07-rc6-sun50iw1 (Sep 24 2023 - 21:04:22 +0300) Allwinner Technology

CPU:  Allwinner A64 (SUN50I)
Model: Pine64 PinePhone (1.2)
DRAM:  3 GiB
Core:  70 devices, 18 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:  serial
Err:  serial
Net:  No ethernet found.
Autoboot in 2 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
473 bytes read in 3 ms (153.3 KiB/s)
## Executing script at 4fc00000
Failed to load 'Image.gz'
SCRIPT FAILED: continuing...
Card did not respond to voltage select! : -110
No EFI system partition
No EFI system partition
Failed to persist EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
472 bytes read in 1 ms (460.9 KiB/s)
## Executing script at 4fc00000
9122270 bytes read in 218 ms (39.9 MiB/s)
Uncompressed size: 24115208 = 0x16FF808
40961 bytes read in 3 ms (13 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41990000
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
  Loading Device Tree to 0000000049ff2000, end 0000000049fff000 ... OK
Working FDT set to 49ff2000

Starting kernel ...





I haven't looked into any resolutions yet.  I am not familiar with uboot and so research is needed for me.

[donchurch]

It turns out that the image that I just documented was for 6.2.5.5 and noticing the 6.5.5 was the latest posted here I just tried it and funny thing is the green light comes on for about 4 seconds then the light goes out and nothing more happens and the serial output is blank.  When I take the card out it boots fine with Maemo.  I didn't think the card could keep the system from going to the main memory for a try.  The fstab now shows the partition ID.  I'll mess with it tomorrow.

  GNU nano 7.2                                                    fstab                                                             
#
# /etc/fstab: static file system information
#
# <file system>        <mount point>  <type>  <options>                        <dump> <pass>
shm                    /dev/shm        tmpfs    defaults                        0      0
devpts                /dev/pts        devpts  noexec,nosuid,gid=tty,mode=0620  0      0
sysfs                  /sys            sysfs    defaults                        0      0
proc                  /proc          proc    defaults                        0      0
#
#/dev/#EXT4FS_BOOT#    /boot          ext4    errors=remount-ro                0      1
#/dev/#SWAP#          swap            swap    defaults                        0      0
#/dev/#EXT4FS_ROOT#    /              ext4    errors=remount-ro                0      1
#/dev/#EXT4FS_HOME#    /home          ext4    defaults                        0      2

UUID=32539e08-a5c0-4084-9f32-0932043d95e3    /          ext4    noatime,nodiratime,data=writeback,errors=remount-ro      0      1

[donchurch]

So, I've learned a bit more  on bauds and setserial baud_base and my conclusion about the locked in 1.5mb/s is likely wrong.  For some reason the serial wasn't displaying on my pc even though I was receiving data.  Little did I know about divisors and aliases  and still not sure but it's working for the moment and I have the output for the latest kernel image.  The text shows the boot process being stuck in a loop and since there is no indication of activity on the phone it looks shutdown but not.  Here are the first two boot attempts since the initial is a little different the the subsequent:

U-Boot SPL 2023.07-rc6-sun50iw1 (Sep 24 2023 - 21:04:22 +0300)
DRAM: 3072 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.9(release):v2.9.0
NOTICE:  BL31: Built : 21:03:41, Sep 24 2023
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x2093dd8, model: Pine64 PinePhone (1.2)


U-Boot 2023.07-rc6-sun50iw1 (Sep 24 2023 - 21:04:22 +0300) Allwinner Technology

CPU:  Allwinner A64 (SUN50I)
Model: Pine64 PinePhone (1.2)
DRAM:  3 GiB
Core:  70 devices, 18 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:  serial
Err:  serial
Net:  No ethernet found.
Autoboot in 2 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2716 bytes read in 4 ms (663.1 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
148 bytes read in 3 ms (47.9 KiB/s)
53952 bytes read in 7 ms (7.3 MiB/s)
23429128 bytes read in 940 ms (23.8 MiB/s)
Working FDT set to 4fa00000
3821 bytes read in 5 ms (746.1 KiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 45000000
6940813 bytes read in 291 ms (22.7 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=418d0000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
  Image Name:  uInitrd
  Image Type:  AArch64 Linux RAMDisk Image (gzip compressed)
  Data Size:    6940749 Bytes = 6.6 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
  Loading Ramdisk to 49961000, end 49fff84d ... OK
  Loading Device Tree to 00000000498eb000, end 0000000049960fff ... OK
Working FDT set to 498eb000

Starting kernel ...

[    1.229944] scpi_protocol scpi: incorrect or no SCP firmware found
[  24.060293] sun4i-drm display-engine: Couldn't bind all pipelines components
[  71.775036] reboot: Restarting system

U-Boot SPL 2023.07-rc6-sun50iw1 (Sep 24 2023 - 21:04:22 +0300)
DRAM: 3072 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.9(release):v2.9.0
NOTICE:  BL31: Built : 21:03:41, Sep 24 2023
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x2093dd8, model: Pine64 PinePhone (1.2)


U-Boot 2023.07-rc6-sun50iw1 (Sep 24 2023 - 21:04:22 +0300) Allwinner Technology

CPU:  Allwinner A64 (SUN50I)
Model: Pine64 PinePhone (1.2)
DRAM:  3 GiB
Core:  70 devices, 18 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial
Out:  serial
Err:  serial
Net:  No ethernet found.
Autoboot in 2 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2716 bytes read in 4 ms (663.1 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
148 bytes read in 3 ms (47.9 KiB/s)
53952 bytes read in 8 ms (6.4 MiB/s)
23429128 bytes read in 941 ms (23.7 MiB/s)
Working FDT set to 4fa00000
3821 bytes read in 6 ms (621.1 KiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 45000000
6940813 bytes read in 292 ms (22.7 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=418d0000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
  Image Name:  uInitrd
  Image Type:  AArch64 Linux RAMDisk Image (gzip compressed)
  Data Size:    6940749 Bytes = 6.6 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
  Loading Ramdisk to 49961000, end 49fff84d ... OK
  Loading Device Tree to 00000000498eb000, end 0000000049960fff ... OK
Working FDT set to 498eb000

Starting kernel ...

[    1.229956] scpi_protocol scpi: incorrect or no SCP firmware found
[  10.781967] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0
[  10.788581] stk3310 2-0048: register read failed: -110
[  19.964300] sun4i-drm display-engine: Couldn't bind all pipelines components
[  22.013946] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0
[  22.020617] stk3310 2-0048: register read failed: -110
[  72.627576] reboot: Restarting system

[donchurch]

Making progress, having looked back at Acid Andy's "needs external monitor" statement I plugged an HDMI cable into the Pinephone docking bar and it turns out that after the few lines of "starting kernel" it ultimately jumps to a login prompt, albeit only on the serial output.  So then I discovered that the serial console app CuteCom, I am able to perform console commands... I'm impressed!  So just to bring this up to date I did the startx command and here's the output:


<0x1b>[?2004hroot@pinephone:/# startx
<0x1b>[?2004lxauth:  file /root/.serverauth.1575 does not exist
xauth:  file /root/.Xauthority does not exist
xauth:  file /root/.Xauthority does not exist


X.Org X Server 1.21.1.8
X Protocol Version 11, Revision 0
Current Operating System: Linux pinephone 6.5.5 #1 SMP Sun Sep 24 13:20:03 EEST 2023 aarch64
Kernel command line: root=UUID=32539e08-a5c0-4084-9f32-0932043d95e3 ro rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 consoleblank=0 loglevel=4 usb-storage.quirks= 

Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 22 17:50:26 2024
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error



I've messed with xserver a bit in the past so there I'm going.

[donchurch]

Well I'm at a bit of a loss... Here are some outputs that may help someone else.  I highlighted some critical errors.


(lightdm.log)

+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=1787
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/50-directories.conf
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/50-slarm64-defaults.conf
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.04s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.04s] DEBUG: Monitoring logind for seats
[+0.04s] DEBUG: New seat added from logind: seat0
[+0.04s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.04s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.04s] DEBUG: Seat seat0: Starting
[+0.04s] DEBUG: Seat seat0: Creating greeter session
[+0.04s] DEBUG: Seat seat0: Creating display server of type x
[+0.04s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.04s] DEBUG: Using VT 7
[+0.04s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.04s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.05s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.05s] DEBUG: XServer 0: Launching X Server
[+0.05s] DEBUG: Launching process 1793: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.05s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.05s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.50s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.50s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.51s] DEBUG: Process 1793 exited with return value 1
[+0.51s] DEBUG: XServer 0: X server stopped
[+0.51s] DEBUG: Releasing VT 7
[+0.51s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+0.51s] DEBUG: Seat seat0: Display server stopped
[+0.52s] DEBUG: Seat seat0: Stopping session
[+0.52s] DEBUG: Seat seat0: Session stopped
[+0.52s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.52s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.52s] DEBUG: Seat seat0: Stopping
[+0.52s] DEBUG: Seat seat0: Stopped
[+0.52s] DEBUG: Required seat has stopped
[+0.52s] DEBUG: Stopping display manager
[+0.52s] DEBUG: Display manager stopped
[+0.52s] DEBUG: Stopping daemon
[+0.52s] DEBUG: Exiting with return value 1





(end of dmesg)


[  16.969368] Bluetooth: MGMT ver 1.22
[  17.137548] Bluetooth: hci0: broken local ext features page 2
[  17.173207] NET: Registered PF_ALG protocol family
[  18.930919] sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff800080f1d528)
[  18.932370] sun4i-drm display-engine: bound 1200000.mixer (ops 0xffff800080f1d528)
[  18.932940] sun4i-drm display-engine: No panel or bridge found... RGB output disabled
[  18.932954] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xffff800080f1a370)
[  18.933195] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xffff800080f1a370)
[  18.933227] sun4i-drm display-engine: bound 1ca0000.dsi (ops 0xffff800080f1c238)
[  18.935201] sun4i-drm display-engine: Couldn't bind all pipelines components
[  18.936584] platform sound_hdmi: deferred probe pending
[  18.936603] platform 1ee0000.hdmi: deferred probe pending
[  18.936609] platform sound: deferred probe pending
[  19.403563] dw-apb-uart 1c28000.serial: forbid DMA for kernel console
[  20.993959] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0
[  20.994023] stk3310 2-0048: register read failed: -110
[  31.710028] dc1sw: disabling
[  31.710229] vcc-mipi-io: disabling
[  31.710314] avdd-csi: disabling
[  31.710458] vcc-1v2-hsic: disabling




( dmesg | grep -i gpu)

[    7.862043] lima 1c40000.gpu: gp - mali400 version major 1 minor 1
[    7.862130] lima 1c40000.gpu: pp0 - mali400 version major 1 minor 1
[    7.862201] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1
[    7.862237] lima 1c40000.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit external bus
[    7.862670] lima 1c40000.gpu: bus rate = 200000000
[    7.862682] lima 1c40000.gpu: mod rate = 297000000
[    7.863662] [drm] Initialized lima 1.1.0 20191231 for 1c40000.gpu on minor 0



(startx)

<0x1b>[?2004lxauth:  file /root/.serverauth.1702 does not exist
xauth: (argv):1:  bad display name "pinephone:0" in "list" command
xauth: (stdin):1:  bad display name "pinephone:0" in "add" command


X.Org X Server 1.21.1.8
X Protocol Version 11, Revision 0
Current Operating System: Linux pinephone 6.5.5 #1 SMP Sun Sep 24 13:20:03 EEST 2023 aarch64
Kernel command line: root=UUID=32539e08-a5c0-4084-9f32-0932043d95e3 ro rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 consoleblank=0 loglevel=4 usb-storage.quirks= 

Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 23 14:35:45 2024
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
xauth: (argv):1:  bad display name "pinephone:0" in "remove" command