Draft: linux-pine64-pinephonepro: upgrade to 6.12.6
Merge request reports
Activity
added 1 commit
- 2e1730b0 - linux-pine64-pinephonepro: upgrade to 6.12.6
@StacyHarper: Can you also try this update with your FDE-install on the PPP? I haven't really changed anything yet, but maybe there was some regression between 6.11.11 and 6.12.6.
Still the same thing:
Tow-Boot TPL 2023.07 lpddr4_set_rate: change freq to 400MHz 0, 1 Channel 0: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB 256B stride lpddr4_set_rate: change freq to 800MHz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... Tow-Boot SPL 2023.07 Trying to boot from SPI spl_load_fit_image: Skip load 'atf-5': image size is 0! NOTICE: BL31: v2.9(release): NOTICE: BL31: Built : 00:00:00, Jan 1 1980 Tow-Boot 2023.07 007 [variant: spi] SoC: Rockchip rk3399 Reset cause: POR Model: Pine64 PinePhonePro DRAM: 4 GiB (effective 3.9 GiB) Initializing Pinephone Pro charger PMIC: RK8180 (on=0x80, off=0x04) Core: 265 devices, 26 uclasses, devicetree: separate MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from SPIFlash... SF: Detected gd25lq128e with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Pine64 PinePhonePro Net: No ethernet found. starting USB... No working controllers found Please press [ESCAPE] or [CTRL+C] to enter the boot menu. off off switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Card did not respond to voltage select! : -110 BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 733184 bytes read in 59 ms (11.9 MiB/s) Booting /efi\boot\bootaa64.efi Booting `postmarketOS' EFI stub: Booting Linux Kernel... EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.6 (pmos@yellow-orcess) (aarch64-alpine-linux-musl-gcc (Alpine 14.2.0) 14.2.0, GNU ld (GNU Binutils) 2.42) #1 SMP PREEMPT Sun Dec 22 07:04:39 UTC 2024 [ 0.000000] KASLR enabled [ 0.000000] Machine model: Pine64 PinePhone Pro [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff1a0000 (options '') [ 0.000000] printk: legacy bootconsole [uart8250] enabled@StacyHarper, there's one thing that really stands out for me in your provided serial boot console.
If I look back at the boot logs on Kernel 6.6 in the issue tracker, which have been provided in the past, it looks like mmc initialization functions properly.
On the serial boot logs you provide right now I can see the error message: "Card did not respond to voltage select! : -110"
It looks like it might have to do something with timings or so.
Do you boot from SD-Card or MMC, and if using MMC is it possible to try SD-Card as well, just to see if this gives a different result?Edit 1: Can you also try to grab a serial bootlog of unencrypted (non-FDE) installation, this way it's easier for me to compare the differences in sequences.
I unfortunately don't own a USB-serial cable, which makes it harder for me to do some proper debugging.Edited by Jan Jasper de Kroon-
Do you boot from SD-Card or MMC, and if using MMC is it possible to try SD-Card as well, just to see if this gives a different result?
From MMC here.
I just tried on fresh sd card, FDE and non-FDE. I got the same issue on FDE. Here both logs:
FDE:
Tow-Boot TPL 2023.07 lpddr4_set_rate: change freq to 400MHz 0, 1 Channel 0: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB 256B stride lpddr4_set_rate: change freq to 800MHz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... Tow-Boot SPL 2023.07 Trying to boot from SPI spl_load_fit_image: Skip load 'atf-5': image size is 0! NOTICE: BL31: v2.9(release): NOTICE: BL31: Built : 00:00:00, Jan 1 1980 Tow-Boot 2023.07 007 [variant: spi] SoC: Rockchip rk3399 Reset cause: POR Model: Pine64 PinePhonePro DRAM: 4 GiB (effective 3.9 GiB) Initializing Pinephone Pro charger PMIC: RK8180 (on=0x80, off=0x00) Core: 265 devices, 26 uclasses, devicetree: separate MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from SPIFlash... SF: Detected gd25lq128e with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Pine64 PinePhonePro Net: No ethernet found. starting USB... No working controllers found Please press ESCAPE or CTRL+C to enter the boot menu. off on switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Card did not respond to voltage select! : -110 Failed to load EFI variables BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 733184 bytes read in 84 ms (8.3 MiB/s) Booting /efi\boot\bootaa64.efi Booting `postmarketOS' EFI stub: Booting Linux Kernel... EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.6 (pmos@yellow-orcess) (aarch64-alpine-linux-musl-gcc (Alpine 14.2.0) 14.2.0, GNU ld (GNU Binutils) 2.42) #1 SMP PREEMPT Sun Dec 22 07:04:39 UTC 2024 [ 0.000000] KASLR enabled [ 0.000000] Machine model: Pine64 PinePhone Pro [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff1a0000 (options '') [ 0.000000] printk: legacy bootconsole [uart8250] enablednon-FDE:
Tow-Boot TPL 2023.07 lpddr4_set_rate: change freq to 400MHz 0, 1 Channel 0: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB 256B stride lpddr4_set_rate: change freq to 800MHz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... Tow-Boot SPL 2023.07 Trying to boot from SPI spl_load_fit_image: Skip load 'atf-5': image size is 0! NOTICE: BL31: v2.9(release): NOTICE: BL31: Built : 00:00:00, Jan 1 1980 Tow-Boot 2023.07 007 [variant: spi] SoC: Rockchip rk3399 Reset cause: POR Model: Pine64 PinePhonePro DRAM: 4 GiB (effective 3.9 GiB) Initializing Pinephone Pro charger PMIC: RK8180 (on=0x80, off=0x00) Core: 265 devices, 26 uclasses, devicetree: separate MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from SPIFlash... SF: Detected gd25lq128e with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Pine64 PinePhonePro Net: No ethernet found. starting USB... No working controllers found Please press ESCAPE or CTRL+C to enter the boot menu. off on switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Card did not respond to voltage select! : -110 Failed to load EFI variables BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 733184 bytes read in 84 ms (8.3 MiB/s) Booting /efi\boot\bootaa64.efi Booting `postmarketOS' EFI stub: Booting Linux Kernel... EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.6 (pmos@yellow-orcess) (aarch64-alpine-linux-musl-gcc (Alpine 14.2.0) 14.2.0, GNU ld (GNU Binutils) 2.42) #1 SMP PREEMPT Sun Dec 22 07:04:39 UTC 2024 [ 0.000000] KASLR enabled [ 0.000000] Machine model: Pine64 PinePhone Pro [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff1a0000 (options '') [ 0.000000] printk: legacy bootconsole [uart8250] enabled tfb_acquire_fb() failed with error code: 1 OpenRC 0.55.1 is starting up Linux 6.12.6 (aarch64) * /proc is already mounted * /run/openrc: creating directory * /run/lock: creating directory * /run/lock: correcting owner zram swap: activating with size: 1931 MB * Caching service dependencies ... [ ok ] * Clock skew detected with `/etc/init.d' * Adjusting mtime of `/run/openrc/deptree' to Mon Dec 23 09:22:02 2024 ... TRUNCATEDI've truncated the regular openrc outputs
@StacyHarper, Thank you for your valuable input/time.
This helps me a long way, as the errorCard did not respond to voltage select! : -110appears in both cases, but with FDE renders unbootable/without FDE boots succesfull.
This makes me think the error I was looking into is not the failure which makes the boot process stall.
I shall look further in the difference of booting a FDE / Non-FDE system, to see if I can come up with an answer as to why this might be failing.I might have found some valuable information, in a open MR for kernel 6.8.0. In this kernel it seems some people reported that the unl0kr wouldn't come up, but someone found a solution which is the following:
Looks like you need
rockchip-isp1in initramfs for display to come up. Add that to/usr/share/mkinitfs/modules/00-device-pine64-pinephonepro.modulesand re-runmkinitfs.-
omg it seems works! but now I have a crash after tty, before tinydm to start:
Tow-Boot TPL 2023.07 lpddr4_set_rate: change freq to 400MHz 0, 1 Channel 0: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 400MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB 256B stride lpddr4_set_rate: change freq to 800MHz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... Tow-Boot SPL 2023.07 Trying to boot from SPI spl_load_fit_image: Skip load 'atf-5': image size is 0! NOTICE: BL31: v2.9(release): NOTICE: BL31: Built : 00:00:00, Jan 1 1980 Tow-Boot 2023.07 007 [variant: spi] SoC: Rockchip rk3399 Reset cause: RST Model: Pine64 PinePhonePro DRAM: 4 GiB (effective 3.9 GiB) Initializing Pinephone Pro charger PMIC: RK8180 (on=0x80, off=0x04) Core: 265 devices, 26 uclasses, devicetree: separate MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from SPIFlash... SF: Detected gd25lq128e with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Pine64 PinePhonePro Net: No ethernet found. starting USB... No working controllers found [0mPlease press [[1mESCAPE[0m] or [[1mCTRL+C[0m] to enter the boot menu. off off switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... 7[r[999;999H[6n8Card did not respond to voltage select! : -110 BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 733184 bytes read in 60 ms (11.7 MiB/s) Booting /efi\boot\bootaa64.efi Booting `postmarketOS' EFI stub: Booting Linux Kernel... EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.6 (pmos@yellow-orcess) (aarch64-alpine-linux-musl-gcc (Alpine 14.2.0) 14.2.0, GNU ld (GNU Binutils) 2.42) #1 SMP PREEMPT Sun Dec 22 07:04:39 UTC 2024 [ 0.000000] KASLR enabled [ 0.000000] Machine model: Pine64 PinePhone Pro [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff1a0000 (options '') [ 0.000000] printk: legacy bootconsole [uart8250] enabled OpenRC 0.55.1 is starting up Linux 6.12.6 (aarch64) * /proc is already mounted * /run/openrc: creating directory * /run/lock: creating directory * /run/lock: correcting owner zram swap: activating with size: 1931 MB * Caching service dependencies ... [ ok ] * Clock skew detected with `/etc/init.d' * Adjusting mtime of `/run/openrc/deptree' to Sun Dec 22 08:08:36 2024 * WARNING: clock skew detected! * Remounting devtmpfs on /dev ... [ ok ] * Mounting /dev/mqueue ... [ ok ] * Mounting /dev/shm ... [ ok ] * Mounting security filesystem ... [ ok ] * Mounting debug filesystem ... [ ok ] * Mounting config filesystem ... [ ok ] * Mounting persistent storage (pstore) filesystem ... [ ok ] * Mounting efivarfs 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 ] * Setting up dm-crypt mappings ... * crypt-sd using: open /dev/mmcblk1 crypt-sd ... [ ok ] [ ok ] * Checking local filesystems .../dev/mapper/crypt-sd: recovering journal /dev/mapper/crypt-sd: clean, 7099/7806976 files, 5109897/31213056 blocks [ ok ] * Remounting filesystems ... [ ok ] * Mounting local filesystems ... [ ok ] * Configuring kernel parameters ... [ ok ] * Mounting /tmp as tmpfs ... [ ok ] * Creating user login records ... [ ok ] * /run/dbus: creating directory * /run/dbus: correcting owner * Starting System Message Bus ... [ ok ] * Setting hostname ... [ ok ] * Starting logbookd ... [ ok ] * Starting CUPS ... [ ok ] * WARNING: clock skew detected! * Activating swap file ...Configured swap file size is 0, skipping creation. [ 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 avahi-daemon ... [ ok ] * Starting avahi2dns ... [ ok ] * Starting Bluetooth ... [ ok ] * Starting cachefilesd ... * /dev/cachefiles doesn't exist, trying to modprobe cachefiles [ ok ] * Checking /etc/unbound/unbound.conf ... [ ok ] * Starting unbound daemon ... [ ok ] * Starting chronyd ... [ ok ] * Starting modemmanager ... [ ok ] * Starting eg25-manager ... [ ok ] * Starting fcron ... [ ok ] * Starting HKDM ... [ ok ] * Starting iio-sensor-proxy ... * supervise-daemon: /usr/libexec/iio-sensor-proxy does not exist * failed to start iio-sensor-proxy [ !! ] * ERROR: iio-sensor-proxy failed to start * Starting kill-pbsplash ... [ ok ] * Starting rpcbind ... [ ok ] * Starting NFS statd ... [ ok ] * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... * Ping prodd.missbanal.net ... [ !! ] * ERROR: prodd_ensure failed to start * ERROR: cannot start openvpn.willow as prodd_ensure would not start * ERROR: cannot start willow_vpn_ensure as prodd_ensure would not start * Starting NFS sm-notify ... [ ok ] * Mounting NFS filesystems ...mount.nfs: Protocol not supported for 42.127.213.1:/home/reed/music on /home/stacy/music [ !! ] * ERROR: nfsmount failed to start * Restoring rfkill configuration ... [ ok ] * Starting seatd ... [ ok ] * Starting sshd ... [ ok ] * Starting syncthing ... [ ok ] * Starting tinydm ... [ ok ] * Starting Waydroid Container Manager ... [ ok ] * Activating swap devices ... [ ok ] zram swap: activating with size: 1931 MB * Loading zram module... [ ok ] * Swap->zram0 [ ok ] * Starting local ... [ ok ] Welcome to postmarketOS Kernel 6.12.6 on an aarch64 (/dev/ttyS2) [9;5]cyan-bottle login: [ 82.279790] Internal error: Oops: 0000000096000021 [#1] PREEMPT SMP [ 82.286829] Modules linked in: zram zsmalloc loop nfs lockd grace sunrpc cachefiles netfs algif_hash algif_skcipher af_alg bnep fuse uhid uinput ledtrig_pattern option qmi_wwan snd_soc_simple_card ghash_ce leds_sgm3140 brcmfmac_wcc sha2_ce sha1_ce gpio_vibra snd_soc_simple_card_utils ppkb_manager v4l2_flash_led_class leds_gpio snd_soc_rockchip_i2s usb_wwan usbnet hci_uart btsdio usbserial mii rockchip_vdec(C) hantro_vpu btbcm inv_mpu6050_i2c brcmfmac inv_mpu6050 inv_sensors_timestamp rockchip_rga v4l2_vp9 v4l2_jpeg videobuf2_dma_sg bluetooth v4l2_h264 af8133j pl330 v4l2_mem2mem snd_soc_rt5640 syscon_reboot_mode snd_soc_hdmi_codec reboot_mode snd_soc_simple_amplifier snd_soc_rl6231 pinephone_keyboard crc8 snd_soc_core matrix_keymap snd_pcm_dmaengine joydev rockchip_saradc snd_pcm imx258 snd_timer v4l2_cci ov8858 dw9714 industrialio_triggered_buffer cfg80211 kfifo_buf stk3310 snd rfkill brcmutil adc_keys industrialio soundcore efivarfs nls_ascii nls_cp437 vfat fat evdev rockchip_isp1 videobuf2_vmalloc [ 82.287240] videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common v4l2_fwnode v4l2_async videodev goodix_ts mc [ 82.399144] CPU: 1 UID: 0 PID: 52 Comm: kworker/u25:2 Tainted: G C 6.12.6 #1 [ 82.408624] Tainted: [C]=CRAP [ 82.411970] Hardware name: PINE64 PinePhone Pro/PinePhone Pro, BIOS Tow-Boot 2023.07 007 [variant: spi] 07/01/2023 [ 82.423576] Workqueue: events_power_efficient nft_rhash_gc [ 82.429732] pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 82.437527] pc : nft_rhash_gc+0x1e4/0x298 [ 82.442022] lr : nft_rhash_gc+0x11c/0x298 [ 82.446512] sp : ffff800080323ce0 [ 82.450216] x29: ffff800080323d40 x28: ffff0caf62061b0c x27: 0000000000000000 [ 82.458217] x26: ffff0caf53108cf0 x25: ffff0cb02ebea480 x24: ffff0caf53100d78 [ 82.466215] x23: 000000000000000a x22: ffff0caf41388000 x21: ffff0caf53108d78 [ 82.474212] x20: ffffbd5b83cd54c0 x19: ffff0caf62061b00 x18: 0000000000000000 [ 82.482207] x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff8ec50928 [ 82.490203] x14: ffffffffffffffff x13: 0000000000000030 x12: ffff0caf53108cf0 [ 82.498198] x11: 0000000000000000 x10: ffff800080323cf8 x9 : ffff0caf41d23060 [ 82.506193] x8 : 0000000000000000 x7 : ffffbd5b82edc6b0 x6 : 0000000000000000 [ 82.514189] x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff0caf62061b00 [ 82.522184] x2 : ffff0caf62061b0c x1 : 00000000fffcad84 x0 : 00000000fffcaabe [ 82.530180] Call trace: [ 82.532916] nft_rhash_gc+0x1e4/0x298 [ 82.537020] process_one_work+0x17c/0x400 [ 82.541513] worker_thread+0x258/0x380 [ 82.545711] kthread+0x114/0x120 [ 82.549332] ret_from_fork+0x10/0x20 [ 82.553354] Code: eb00003f 54fff9e4 91003262 f9800051 (c85f7c40) [ 82.560184] ---[ end trace 0000000000000000 ]--- [ 82.565355] Kernel panic - not syncing: Oops: Fatal exception [ 82.571786] SMP: stopping secondary CPUs [ 82.576245] Kernel Offset: 0x3d5b020b0000 from 0xffff800080000000 [ 82.583057] PHYS_OFFSET: 0xfffff350c0000000 [ 82.587732] CPU features: 0x08,00002082,c0000000,4200401b [ 82.593771] Memory Limit: none [ 82.597190] Rebooting in 120 seconds..Ignore the
prodd.missbanal.net, and NFS mount parts, that's probably on my own. But it means no network wifi is connected for a big while.Edited by Willow Barraco Perfect, thank you so much for testing it. In the meanwhile I already included the specific kernel module as built-in, which also improves the loading of the PostmarketOS boot-logo during starting up of the PinePhone Pro. Adding the module to initramfs shouldn't be necessary in this case anymore. If you want to test this out at a later point when trying to triage this new error that would be great. I'll dive into the new discovered error as soon as possible. My goal is to land 6.12 with full FDE ability.
Edited by Jan Jasper de Kroon-
Here serial logs that I have, with this last MR update:
https://paste.sr.ht/~stacyharper/de3cae8f8fc9c9bd70f1c727b1b7d0db510f209f
I've just booted, wait for some seconds, and tried to poweroff. The device hang indefinitely, after most of the process to exits. I've 70% battery, meaning the warnings
rk818-bat: lower power yet, power off system! v=3515, c=-1560, dsoc=74seems out of touch.Edited by Willow Barraco That's great to hear. The kernel oops you provided was traced back to something in nftables, so it seems something network related.
So I'm not fully convinced that it will not randomly appear once in a while.
It seems like we're getting closer and closer to a solution on the FDE installations.
Lets focus on the hanging shut-down first for now, as I feel this is a priority.
The "state of charge" messages in dmesg are from megi's rk818 battery driver, but it's safe to ignore them.
This is always happening on my device as well, but doesn't impact anything really.
I'll see if I can make it less verbose.I've made some changes in which we switch from FB_SIMPLE to the newer more maintained SIMPLEDRM, this might be what is causing this strange behavior.
Does the boot stall happen everytime you try to shut-down the system or is it randomly?
To make sure that the built-in module isn't the culprit, later in the day I will once more make the config back to module, and we manually add it to the mkinitfs to see if unloading of the module (which it can't do due to being built-in) might be to blame.Edited by Jan Jasper de Kroon-
Another thing I've noted, the leds got no types in the filesystem. Exemple in Pinephone/sys/class/leds/blue:indicator, while here/sys/class/leds/blue:. Sxmo then fails to detect those leds.edit: moved to another thread
Edited by Willow Barraco @StacyHarper I've just uploaded a new build, where I reverted rockchip-isp1 as built-in.
Whenever you have some time, please test if adding the module to/usr/share/mkinitfs/modules/00-device-pine64-pinephonepro.modulesand re-runmkinitfs, solves the problem of shutting-down the system.
The shutdown-freeze certainly has something to do with the error:detected fb_set_par error, error code: -16The error code -16 (EBUSY) suggests that the framebuffer device is currently in use or locked, preventing the parameters from being updated.
I hope that reverting the rockchip-isp1 to module, makes this specific part able to unload/release during shut-down (which hopefully is the culprit.)
added 1 commit
- be92f5e3 - linux-pine64-pinephonepro: upgrade to 6.12.6
added 1 commit
- aeaf500a - linux-pine64-pinephonepro: upgrade to 6.12.6
added 1 commit
- c0e2c4d9 - linux-pine64-pinephonepro: upgrade to 6.12.6
added 1 commit
- 81ba1872 - linux-pine64-pinephonepro: upgrade to 6.12.6
- Resolved by Jan Jasper de Kroon
@fossdd, @ethical_haquer, Since you tested 6.11.11 as well are you able to test this 6.12.6 for regressions as well?
Currently I'm also running this on my PPP, without FDE that is and running on MMC without any noticeable regressions. - Last reply by ethical_haquer
mentioned in issue #2627
added 1 commit
- cc7fcbab - linux-pine64-pinephonepro: upgrade to 6.12.6
-
Another thing I've noted, the leds got no types in the filesystem. Exemple in Pinephone
/sys/class/leds/blue:indicator, while here/sys/class/leds/blue:. Sxmo then fails to detect those leds.edit: Well, maybe this isn't the place to report every disfunction with this kernel? But iirc this was working before, so probably it is a regression to be noted
Edited by Willow Barraco @ethical_haquer I think when you test this new change to the MR, thr notification led should be back at the normal led.
So the led at the top of the screen instead of the camera led.
To test you have to use mrtest zap and re-add with mrtest add 5934.-
No problem! Whenever you need people to test something for the PPP, feel free to let me know!
Edited by ethical_haquer
@StacyHarper: If I look at the DTS of the PinePhone Pro I can see that red, blue, and green LED's haven't got indicator types defined in the DTS. This is why there is no prefix ":indicator" behind these LED's.
What I did find out in DTS is that we have:
multi-led {
compatible = "leds-group-multicolor";
color = <LED_COLOR_ID_RGB>;
function = LED_FUNCTION_INDICATOR;
leds = <&led_red>, <&led_green>, <&led_blue>;
};
But multi-led doesn't appear in /sys/class/leds at all.
This might be because "CONFIG_LEDS_GROUP_MULTICOLOR is not set" in current kernel configuration.
I'll look into this as well to see if I can make it work properly.
What I otherwise could do as well is patch the DTS to define the LED types, but I prefer to keep the source as close to megi's as possible.Edit 1: I have done some research into the commit history, and it seems that the function = LED_FUNCTION_INDICATOR; definitions have been stripped away from the separate led-colors upon mainlining them in upstream Torvalds kernel.
I have found an e-mail address of the patch submitter, and asked for the logic behind this change.
Lets wait and see if I get a response, for now I've added CONFIG_LEDS_GROUP_MULTICOLOR=m to the configuration, so the combined RGB (White) indicator light should be working this way instead of the flashlight as indicator light.Edited by Jan Jasper de Kroonadded 1 commit
- cf3d0e00 - linux-pine64-pinephonepro: upgrade to 6.12.6
@Newbyte I will makr the MR a Draft again for now.
The LED regression has been worked out partly for now, but although the notification led is working properly again, the blue, red and green led still arent marked as indicator lights, so my guess is that this still somehow breaks compatibility with SXMO.
This issue can be worked out fairly easy, but requires an additional patch on top of mainline.
I've been in contact with the original upstreamer of the led related dts changes, who said that the :indicator definitions probably got overlooked while upstreaming the dts patch.
My preference is that it will be fixed in upstream instead of adding an additional patchset on top of mainline, but this could be an easy option to push this MR forward on PostmarketOS for now.
Remaining thing to be worked out seems that the system with FDE doesn't properly shut-down the PinePhone Pro.
We've made a lot of progress in making FDE function on PinePhone Pro again, that it would be a shame to push this kernel release forward without working this out first.
That would make this a fairly strong improved kernel release for PinePhone Pro.
@StacyHarper Is SXMO still complaining about the missing :indicator definitions, or does it now use the new combined-led as indicator light?
My understanding from looking at the sourcecode is that SXMO uses different colours to indicate different types of notifications am I correct (I've never used SXMO before to be honest).Edited by Jan Jasper de Kroon
added 17 commits
-
cf3d0e00...65873483 - 16 commits from branch
postmarketOS:master - c6578eed - linux-pine64-pinephonepro: upgrade to 6.12.6
-
cf3d0e00...65873483 - 16 commits from branch
-
@PsychoGame I think suspend might be broken with this kernel currently. I've noticed that screen off battery life has regressed since the 6.6 kernel, even though I have the suspend timeout (plugged and not plugged in to power) set to 1 minute. Also, in the past the back camera (the 13 MP main camera) would stop working after a suspend, but now it always works. Both of these seem to indicate that it never actually suspends. Is there a way to know for sure if it's not suspending? Also, are other people experiencing this? TIA.
Edited by ethical_haquer mentioned in issue #3424 (closed)
