Pinephone: installer stalls at first screen, "continue" button unresponsive
Using Balena Etcher on Ubuntu Mate 20.04, on two different known-good SD cards, the following images: 20230101-0443-postmarketOS-v22.12-phosh-22.1-pine64-pinephone-installer.img.xz 20230101-0457-postmarketOS-v22.12-plasma-mobile-3.9-pine64-pinephone-installer.img.xz 20221228-1825-postmarketOS-edge-plasma-mobile-3.9-pine64-pinephone-installer.img.xz
All images fail to respond to my pressing of the "Continue" button.
This isn't me, but a guy on Reddit had the same issue a couple weeks ago: https://www.reddit.com/r/postmarketOS/comments/zpk9zd/unable_to_install_newer_version_on_pinephone/
Activity
Thanks for creating the issue! Can't look into it right now, but I'll try to reproduce and fix it over the next days.
In the meantime, one workaround is installing the v22.06 image and upgrading to v22.12 afterwards: https://wiki.postmarketos.org/wiki/Upgrade_to_a_newer_postmarketOS_release
By Oliver Smith on 2023-01-05T03:20:55
-
Confirmed that image 20230104-1357-postmarketOS-v22.06-plasma-mobile-3.8-pine64-pinephone-installer.img.xz at https://images.postmarketos.org/bpo/v22.06/pine64-pinephone/plasma-mobile/20230104-1357/ responds to touch input appropriately. Installing now, thanks for the workaround advice and everything else you do for this fantastic project.
By Dan Hall on 2023-01-06T21:34:37
Edited by Ghost User -
I just tried
20230101-0443-postmarketOS-v22.12-phosh-22.1-pine64-pinephone-installer.img.xzwith both:- PinePhone v1.2
- PinePhone v1.2a
(see revisions) and I cannot reproduce this. Which PinePhone version do you have?
If somebody who can reproduce this could use the serial cable to get the output from the installer (displayed while it runs), and if that doesn't help, maybe look at dmesg, it would be useful to get this resolved.
Note that this installer is on its way out already, the more lightweight ondev2 is in development and will replace it at one point. (Should be able to spend some time on it next week, trying to get an initial version out for testing in edge some time soon...) It has a different stack, the issue might not be present there.
By Oliver Smith on 2023-01-06T23:02:44
-
I observe the same thing on my PinePhone "Braveheart" (v1.1?). The 22.06 install image (sxmo version) works, but with the 22.12 image, I can't tap "Continue" to get started. Unfortunately I don't have a way to connect a serial cable to either my phone or my laptop.
By James on 2023-01-14T03:22:09
-
I have the same issue with the edge channel - just tested phosh, plasma mobile, gnome-mobile. Flashed with Etcher to sd-card. (Braveheart-Edition) No reaction of touch screen at first boot. 20230201-0535-postmarketOS-edge-phosh-22.2-pine64-pinephone.img.xz 20230201-0550-postmarketOS-edge-plasma-mobile-3.9-pine64-pinephone.img.xz 20230201-0520-postmarketOS-edge-gnome-mobile-1-pine64-pinephone.img.xz
By Jürgen Ries on 2023-02-07T20:15:52
-
Thanks for the reports. I wonder if this only happens with the Braveheart edition then...
If somebody who can reproduce this could use the serial cable to get the output from the installer (displayed while it runs), and if that doesn't help, maybe look at dmesg, it would be useful to get this resolved.
This would still be very helpful.
By Oliver Smith on 2023-02-08T06:46:00
-
Hope it helps.
U-Boot SPL 2023.01 (Jan 14 2023 - 18:27:51 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.8(release): NOTICE: BL31: Built : 18:16:06, Jan 14 2023 NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) NOTICE: BL31: Found U-Boot DTB at 0x208fb48, model: Pine64 PinePhone Bravehear) U-Boot 2023.01 (Jan 14 2023 - 18:27:51 +0000) Allwinner Technology CPU: Allwinner A64 (SUN50I) Model: Pine64 PinePhone Braveheart (1.1) DRAM: 2 GiB @ 528 MHz Core: 71 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... Warning: HDMI PHY init timeout! Warning: HDMI PHY init timeout! Warning: HDMI PHY init timeout! Warning: HDMI PHY init timeout! In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 1627 bytes read in 1 ms (1.6 MiB/s) ## Executing script at 4fc00000 gpio: pin 98 (gpio 98) value is 1 gpio: pin 114 (gpio 114) value is 1 Booting from SD arch=arm baudrate=115200 board=sunxi board_name=sunxi boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${pref} boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} ei boot_efi_bootmgr=if fdt addr -q ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_i boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr}} boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_syslinux_conf=extlinux/extlinux.conf boot_targets=fel mmc_auto pxe dhcp bootargs=init=/init.sh rw console=tty0 console=ttyS0,115200 earlycon=uart,mmio32 bootcmd=run distro_bootcmd bootcmd_dhcp=devtype=dhcp; if dhcp ${scriptaddr} ${boot_script_dhcp}; then sour; bootcmd_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(i bootcmd_mmc0=devnum=0; run mmc_boot bootcmd_mmc1=devnum=1; run mmc_boot bootcmd_mmc_auto=if test ${mmc_bootdev} -eq 1; then run bootcmd_mmc1; run bootci bootcmd_pxe=dhcp; if pxe get; then pxe boot; fi bootdelay=0 bootdev=0 bootfstype=ext4 bootm_size=0xa000000 console=ttyS0,115200 cpu=armv8 devplist=1 dfu_alt_info_ram=kernel ram 0x40080000 0x1000000;fdt ram 0x4FA00000 0x100000;ra0 distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ ethaddr=02:ba:a3:6b:38:fc fdt_addr_r=0x4FA00000 fdtcontroladdr=b9f39f80 fdtfile=allwinner/sun50i-a64-pinephone-1.1.dtb fdtoverlay_addr_r=0x4FE00000 fileaddr=4fc00000 filesize=65b kernel_addr_r=0x40080000 kernel_comp_addr_r=0x44000000 kernel_comp_size=0xb000000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefi} loadaddr=0x42000000 mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi mmc_bootdev=0 partitions=name=loader1,start=8k,size=32k,uuid=${uuid_gpt_loader1};name=loader2; pxefile_addr_r=0x4FD00000 ram_freq=528 ramdisk_addr_r=0x4FF00000 scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for; scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env et scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixee scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefi scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${e scriptaddr=0x4FC00000 serial#=92c095baa36b38fc soc=sunxi stderr=serial,vidconsole stdin=serial stdout=serial,vidconsole uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b uuid_gpt_system=b921b045-1df0-41c3-af44-4c6f280d3fae Environment size: 4678/65532 bytes Detecting psci idle state Working FDT set to b9f39f80 PSCI idle state enabled Loading DTB 53850 bytes read in 5 ms (10.3 MiB/s) Working FDT set to 4fa00000 ram_freq=528 Adding FTD RAM clock Applying PSCI DTBO 1130 bytes read in 2 ms (551.8 KiB/s) Loading Initramfs 2520619 bytes read in 113 ms (21.3 MiB/s) Loading Kernel 19021832 bytes read in 840 ms (21.6 MiB/s) gpio: pin 115 (gpio 115) value is 1 Loading user script Failed to load 'user.scr' No user script found Booting kernel gpio: pin 116 (gpio 116) value is 1 gpio: pin 98 (gpio 98) value is 0 Moving Image from 0x40080000 to 0x40200000, end=414a0000 ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 49d98000, end 49fff62b ... OK Loading Device Tree to 0000000049d85000, end 0000000049d97fff ... OK Working FDT set to 49d85000 Warning: HDMI PHY init timeout! Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.1.7 (pmos@build) (aarch64-alpine-linux-musl-gcc 0 [ 0.000000] Machine model: Pine64 PinePhone Braveheart (1.1) [ 0.000000] earlycon: uart0 at MMIO32 0x0000000001c28000 (options '') [ 0.000000] printk: bootconsole [uart0] enabled ### postmarketOS initramfs ### Configuring kernel firmware image search path NOTE: Waiting 10 seconds for the framebuffer /dev/fb0. If your device does not have a framebuffer, disable this with: no_framebuffer=true in <https://postmarketos.org/deviceinfo> Setting framebuffer mode to: U:720x1440p-0 Setup usb network /sys/class/android_usb does not exist, skipping android_usb Setting up an USB gadget through configfs Starting unudhcpd Using interface usb0 Starting the DHCP daemon Trying to start server with parameters: Server IP addr: 172.16.42.1:67, client 0 Trying to bind to interface: usb0 Server started! Mount boot partition (/dev/mmcblk0p1) to /boot (read-only) Detected ext filesystem Extract /boot/initramfs-extra cpio: lib/ld-musl-aarch64.so.1 not created: newer or same age file exists cpio: lib/libc.musl-aarch64.so.1 not created: newer or same age file exists cpio: lib/libdevmapper.so.1.02 not created: newer or same age file exists 338433 blocks Mount root partition (/dev/mmcblk0p2) to /sysroot (read-only) Detected ext4 filesystem Mount boot partition (/dev/mmcblk0p1) to /sysroot/boot (read-write) Detected ext filesystem umount: can't unmount /dev: Invalid argument OpenRC 0.46 is starting up Linux 6.1.7 (aarch64) /lib/rc/sh/init.sh: line 15: can't create /dev/null: Read-only file system * md5sum is missing, which suggests /usr is not mounted * If you have separate /usr, it must be mounted by initramfs * If not, you should check coreutils is installed correctly * Mounting /proc ... [ ok ] * Mounting /run ... * /run/openrc: creating directory * /run/lock: creating directory * /run/lock: correcting owner /lib/rc/sh/gendepends.sh: line 53: can't create /dev/null: Read-only file system zram swap: activating with size: 1494 MB * Caching service dependencies ... [ ok ] * Clock skew detected with `/etc/init.d' * Adjusting mtime of `/run/openrc/deptree' to Wed Feb 1 05:38:24 2023 * WARNING: clock skew detected! * Mounting devtmpfs on /dev ... [ ok ] * Mounting /dev/mqueue ... [ ok ] * Mounting /dev/pts ... [ ok ] * Mounting /dev/shm ... [ ok ] * Mounting /sys ... [ ok ] * Mounting security filesystem ... [ ok ] * Mounting debug filesystem ... [ ok ] * Mounting config filesystem ... [ ok ] * Mounting fuse control filesystem ... [ ok ] * Starting udev ... [ ok ] * Generating a rule to create a /dev/root symlink ... [ ok ] * Populating /dev with existing devices through uevents ... [ ok ] * Waiting for uevents to be processed ... [ ok ] * WARNING: clock skew detected! * Loading modules ... [ ok ] * Setting system clock using the hardware clock [UTC] ... [ ok ] * Checking local filesystems ... [ ok ] * Remounting root filesystem read/write ... [ ok ] * Remounting filesystems ... * fstabinfo: empty fstab [ ok ] * Mounting local filesystems ... [ ok ] * Configuring kernel parameters ...sysctl: error: 'kernel.unprivileged_bpf_disy [ ok ] * Creating user login records ... [ ok ] * Wiping /tmp directory ... [ ok ] * Setting hostname ... [ ok ] * Starting busybox syslog ... [ ok ] * WARNING: clock skew detected! * /run/dbus: creating directory * /run/dbus: correcting owner * Starting System Message Bus ... [ ok ] * Starting Bluetooth ... [ ok ] * Loading nftables rules and starting firewall ... [ ok ] * Starting haveged ... [ ok ] * /var/run/wpa_supplicant: creating directory * Starting WPA Supplicant ... [ ok ] * Starting networkmanager ... [ ok ] * Starting chronyd ... [ ok ] * Starting modemmanager ... [ ok ] * Starting eg25-manager ... [ ok ] * Bringing up network interface lo ... [ ok ] * Starting gpsd ... [ ok ] * Starting HKDM ... [ ok ] * Starting iio-sensor-proxy ... [ ok ] * Starting postmarketos-tweakd ...Scanning /usr/share/postmarketos-tweaks Loading /usr/share/postmarketos-tweaks/sound.yml Loading /usr/share/postmarketos-tweaks/appearance.yml Loading /usr/share/postmarketos-tweaks/about.yml Loading /usr/share/postmarketos-tweaks/fonts.yml Loading /usr/share/postmarketos-tweaks/phosh.yml Loading /usr/share/postmarketos-tweaks/unlocker.yml Loading /usr/share/postmarketos-tweaks/pinephone.yml Loading /usr/share/postmarketos-tweaks/power.yml Scanning /etc/postmarketos-tweaks [ ok ] * Restoring rfkill configuration ... [ ok ] * Starting sleep-inhibitor ... [ ok ] * Activating swap file ...Configured swap file size is 0, skipping creation. [ ok ] * Starting System login manager ... [ ok ] * Starting tinydm ... [ ok ] * Starting wake daemon ... [ ok ] * Activating swap devices ... [ ok ] zram swap: activating with size: 1494 MB * Loading zram module... [ ok ] * Swap->zram0 [ ok ] * Starting local ... [ ok ] Welcome to postmarketOS Kernel 6.1.7 on an aarch64 (/dev/ttyS0) pine64-pinephone login:By Jürgen Ries on 2023-02-09T07:05:42
Edited by Administrator -
Thanks, it definitively does help to have this! I don't see anything unusual in it right now though.
So this is until the boot up, can somebody also get the logs from the installer? I don't have it infront of me right now, but either it should show up pretty soon after printing this login prompt (even without logging in), or it should be possible to get the logs after logging in. Logging into the login prompt should be possible with username
userandyas password. Also it's probably worth looking atdmesgoutput after logging in.By Oliver Smith on 2023-02-09T07:05:42
-
I see this in dmesg on the 1.0 PinePhone
[ 2.494902] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 2.494943] Goodix-TS 0-005d: Error reading 1 bytes from 0x8140: -110 [ 4.574892] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 4.574907] Goodix-TS 0-005d: Error reading 1 bytes from 0x8140: -110 [ 4.602888] Goodix-TS 0-005d: I2C communication failure: -110 [ 4.604163] Goodix-TS: probe of 0-005d failed with error -110So this is for sure why at least on this boot touchscreen doesn't work. What's different compared to earlier versions or a normal boot I don't know... It's using this dtb
Pine64 PinePhone Braveheart (1.1)but I actually can't see any changes for touchscreen between the different dtbs. Though the anx7688 which sits on the same I2C bus has differences including also a reference to "supply for i2c bus" so perhaps this regulator just needs to be turned on also for the touchscreen?On a sidenote, no clue why we only have 1.1 and 1.2 dtb included while there's also 1.0 and 1.2b dtbs
By Luca Weiss on 2023-02-09T21:11:10
Edited by Administrator -
For the last paragraph see https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3860#note_1272999593
Anyways, manually probing the touchscreen later seems to work fine, then you can use the touchscreen in the installer again.
$ echo 0-005d > /sys/bus/i2c/drivers/Goodix-TS/bind[ 523.284322] Goodix-TS 0-005d: ID 917S, version: 0200 [ 523.284642] Goodix-TS 0-005d: Direct firmware load for goodix_917S_cfg.bin failed with error -2 [ 523.305532] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-0/0-005d/input/input5Not sure what changed between earlier kernel versions and now, I don't really see any obvious difference in dts(i)
By Luca Weiss on 2023-02-10T06:54:40
Edited by Ghost User