Kobo Clara not booting with mainline kernel
Describe your issue
What's the expected behaviour?
On pressing the power button the device boots when using the mainline kernel.
What's the current behaviour?
On pressing the power button, the led lights up for a second and then turns off, then lights up again for a second before turning off.
How to reproduce your issue?
Hopefully its as simple as doing a fresh install of pmos edge to a kobo clara, but my device has a replacement display.
What device are you using?
On what postmarketOS version did you encounter the issue?
-
edge (
masterbranch) -
v23.06 -
v22.12(Supported until 2023-07-06) -
I confirm that the issue still is present after running
sudo apk upgrade -a
On what environment did you encounter the issue?
Environments
- GNOME Shell on Mobile
- Phosh
- Plasma Mobile
-
Sxmo (Wayland/Sway) Please post the output of
sxmo_version.sh - Other: console
How did you get postmarketOS image?
- from https://images.postmarketos.org
- I built it using pmbootstrap
- It was preinstalled on my device
What's the build date of the image? (in yyyy-mm-dd format)
2023-11-08
Additional information
This was for my kobo clara which is using a replacement display. The clara boots perfectly with this display, when using the manufacturers OS.
I followed the instructions on the pmos wiki to write the original sd card image to the new card before installing pmos.
Activity
do you have any life sign on the usb line? Battery is charged?
By Andreas Kemnade on 2023-11-08T23:31:03
Edited by Ghost User-
just tried a fresh sd card install with console ui, just works, so not easily reproducible or fixed with 6.6. Well, I usually do a fresh install on every new kernel I try. Do we have different board versions? Well, the clara 2e is really named different. Mine is marked as 37NB-E60K00+4A4. Do you have the ability to look at the serial console?
By Andreas Kemnade on 2023-11-09T08:15:52
-
@akemnade Thanks for having a look! Its definitely a Clara HD, but I'll check the board label in the morning for you.
I can probably get the serial console hooked up? I can definitely solder the pins, and I think I have an arduino uno somewhere that I can use as an adapter. Might just take me a little while to get around to it.
By Geoffrey Tearle on 2023-11-09T08:27:24
-
Can you extract the devicetree with extract-kobohidden clara-sdcard-image.dtb 1286 dtb-orig.dtb ?
I found in the clara2e vendor sources arch/arm/boot/dts/imx6sll-e60k02b00.dts which might be your device. Also a photo of the board might be interesting and chip numbers on the photo. I am preparing a MR for cleanup/updating u-boot. That should be a starting point for further pmOS development. Then IMHO we should check whether auto-detection of model is possible.
By Andreas Kemnade on 2023-11-10T12:07:15
-
extract-kobohidden is from package kobo-firmware-extractor or https://github.com/akemnade/kobo-firmware-extractor
By Andreas Kemnade on 2023-11-10T12:15:04
-
Can you extract the devicetree with extract-kobohidden clara-sdcard-image.dtb 1286 dtb-orig.dtb ?
No problem, would you like me to add it as an attachment here?
Also a photo of the board might be interesting and chip numbers on the photo.
Same as above, would you like me to add these to the thread, or is there an image hosting platform you would prefer me to use?
By Geoffrey Tearle on 2023-11-11T07:24:36
-
-
ok, difference:
- arm-supply = <&ricoh619_dcdc3_reg>; - soc-supply = <&ricoh619_dcdc1_reg>; + arm-supply = <&ricoh619_dcdc5_reg>; + soc-supply = <&ricoh619_dcdc2_reg>; ... -#include "ricoh619_mx6sll.dtsi" +#include "ricoh619_mx6sll_RICOH1145.dtsi"
ugh, that is ugly. Can you confirm which Ricoh chip is there?
By Andreas Kemnade on 2023-11-11T20:10:21
Edited by Ghost User -
looking at the chips, I guess they differ in the bootup default configuration of the regulators, probably different OTP version, so we can detect powerup defaults in u-boot and choose devicetree accordingly.
By Andreas Kemnade on 2023-11-11T20:33:35
Edited by Ghost User -
so next step: lets boot the near-mainline u-boot proposed in !4550 (merged) and dump the registers of the pmic. That does not touch the pmic, so it should be safe. Boot that one without sd-card, remove it, just boot via usb: uuu u-boot-dtb.imx and break into u-boot commandline. You need serial console for that.
The u-boot is at https://github.com/akemnade/u-boot-fslc branch kobo-2020-10 see https://github.com/akemnade/u-boot-fslc/wiki
But again, booting anything in pmOS (the downstream or mainline kernel) is dangerous to your device due to the different voltage regulator settings.
By Andreas Kemnade on 2023-11-11T20:44:19
-
Sorry for the delay, I'm struggling with this a bit.
I've built the linked u-boot, it seems to upload to the kobo fine. The power led doesn't come on, but I'm not sure if its supposed to.
But I cannot for the life of me get a serial console to connect.
By Geoffrey Tearle on 2023-12-02T02:58:58
-
OK looks like we are booting the u-boot fine, its just my serial console that's not working.
Output from uuu
$ uuu u-boot-dtb.imx uuu (Universal Update Utility) for nxp imx chips -- lib1.5.139 Success 1 Failure 0 1:1 2/ 2 [Done ] SDP: doneOutput from dmesg:
[82706.894248] usb 1-1: USB disconnect, device number 2 [82707.188834] usb 1-1: new high-speed USB device number 3 using ehci-platform [82707.349699] usb 1-1: New USB device found, idVendor=18d1, idProduct=0d02, bcdDevice= 2.21 [82707.357933] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [82707.365116] usb 1-1: Product: USB download gadget [82707.369844] usb 1-1: Manufacturer: U-BootBy Geoffrey Tearle on 2023-12-03T01:03:53
-
i2c dev 2 i2c probe i2c md 0x32 0 0x100By Andreas Kemnade on 2023-12-04T01:19:47
Edited by Ghost User -
=> i2c dev 2 Setting bus to 2 => i2c probe Valid chip addresses: 32 => i2c md 0x32 0 0x100 0000: 03 2d 10 01 00 01 00 00 00 04 01 03 9f 00 00 00 .-.............. 0010: 3b 05 00 45 00 0f 5f 2f 5f 5f 2f 5f 2f 5f 5f 5f ;..E.._/__/_/___ 0020: 2f 8f 6f 5f 5f ff ff ff ff ff 0f 00 03 03 03 03 /.o__........... 0030: 03 03 03 03 03 03 28 20 d8 60 28 28 20 d8 60 28 ......( .`(( .`( 0040: 00 00 00 00 ff 13 ff 03 00 00 00 00 60 60 00 24 ............``.$ 0050: 6c 00 60 24 24 60 04 60 60 60 00 24 6c 00 60 24 l.`$$`.```.$l.`$ 0060: 24 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 $`.............. 0070: 00 00 00 00 00 00 00 00 00 ff 00 ff 00 ff 00 ff ................ 0080: 00 ff 00 ff 00 ff 00 ff 00 00 00 00 00 00 00 00 ................ 0090: 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 ........@....... 00a0: 00 00 12 00 01 01 00 00 00 00 00 00 00 00 00 10 ................ 00b0: 07 07 00 23 00 01 08 44 04 0b 41 31 01 83 7f ff ...#...D..A1.... 00c0: ff ff 02 2b cf 00 02 21 4a 00 ff 0f ff ff ff ff ...+...!J....... 00d0: ff 0f 01 00 f1 00 55 00 01 00 88 00 11 80 44 80 ......U.......D. 00e0: 00 00 08 ca 08 ca 64 ff ff ff ff 00 00 00 00 00 ......d......... 00f0: 00 28 5d 00 21 59 98 00 00 00 00 00 47 00 00 00 .(].!Y......G...By Geoffrey Tearle on 2023-12-04T08:03:43
-
rev a:
=> i2c md 0x32 0 0x100 0000: 03 25 10 01 00 01 00 22 00 04 01 03 9f 00 00 00 .%....."........ 0010: 3b 05 00 40 00 0f 3f 4f 3f 8f 7f bf 2f 9f df 5f ;..@..?O?.../.._ 0020: 8f cf df ef ef ff ff ff ff ff 0f 00 03 03 03 03 ................ 0030: 03 03 03 03 03 03 30 d8 38 30 60 30 d8 38 30 60 ......0.80`0.80` 0040: 00 00 00 00 ff 13 ff 03 00 00 00 00 60 60 0c 0c ............``.. 0050: 6c 00 60 24 0c 14 40 60 60 60 0c 0c 6c 00 60 24 l.`$..@```..l.`$ 0060: 0c 14 00 00 32 00 02 00 00 00 c2 01 00 00 00 00 ....2........... 0070: 81 02 91 0d 00 00 00 00 00 ff ad ff 00 ff 00 ff ................ 0080: 00 ff 58 ae 00 ff 00 ff 22 20 01 00 00 00 00 00 ..X....." ...... 0090: 00 00 00 00 00 00 00 00 40 00 00 00 00 00 40 00 ........@.....@. 00a0: 20 14 21 01 04 92 23 00 01 07 06 a2 07 23 20 20 .!...#......# 00b0: 07 07 00 23 00 11 06 e4 44 0b 49 33 01 83 7c fc ...#....D.I3..|. 00c0: ff ff 0a 39 ec 00 02 21 c8 00 ff 0f f5 ff ff ff ...9...!........ 00d0: ff 0f 01 00 f1 00 55 00 01 00 08 00 11 80 44 80 ......U.......D. 00e0: 11 01 00 0b 05 69 64 ff ff 01 2e 0c 00 01 71 00 .....id.......q. 00f0: d6 8b b9 fe 07 37 2e 00 00 00 00 01 11 00 00 00 .....7..........most interesting things are at 36-3a probably
By Andreas Kemnade on 2023-12-04T21:25:07
-
anyways, booting that device with the mainline kernel is dangerous
By Andreas Kemnade on 2023-11-11T20:30:51
Edited by Ghost User -
ok, here is https://github.com/akemnade/u-boot-fslc branch kobo-2023-10 compiles the same way. It has a detect_clara_rev command which should set $fdt_file can you give it a try?
By Andreas Kemnade on 2024-02-14T22:05:28
Edited by Ghost User -
Sorry for the delay on this, looks like it works beautifully
=> detect_clara_rev DCDC1 at 1100 mV DCDC2 at 1000 mV DCDC3 at 3300 mV DCDC4 at 1800 mV DCDC5 at 1100 mV rev B detected => print arch=arm baudrate=115200 board=mx6sllclarahd board_name=mx6sllclarahd boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi boot_efi_bootmgr=if fdt addr -q ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr;fi boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf} boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_syslinux_conf=extlinux/extlinux.conf boot_targets=mmc0 mmc1 bootcmd=fastboot 0 bootcmd_mmc0=devnum=0; run mmc_boot bootcmd_mmc1=devnum=1; run mmc_boot bootdelay=2 console=ttymxc0 cpu=armv7 distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ fdt_addr_r=0x83000000 fdt_file=imx6sll-kobo-clarahd-b.dtb fdtcontroladdr=9fb8cc90 initrd_high=0xffffffff kernel_addr_r=0x82000000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile} loadaddr=0x82000000 mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi ramdisk_addr_r=0x83100000 scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi; scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then part uuid ${devtype} ${devnum}:${distro_bootpart} distro_bootpart_uuid ; run scan_dev_for_boot; fi; done; setenv devplist scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;run boot_efi_bootmgr;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootarm.efi; then echo Found EFI removable media binary efi/boot/bootarm.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo EXTLINUX FAILED: continuing...; fi scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done scriptaddr=0x87000000 soc=mx6 stderr=serial@2020000 stdin=serial@2020000 stdout=serial@2020000 vendor=kobo Environment size: 3006/8188 bytes =>By Geoffrey Tearle on 2024-02-25T22:47:41
mentioned in merge request !4550 (merged)
By Andreas Kemnade on 2024-04-03T20:58:24
mentioned in merge request !5057 (merged)
By Andreas Kemnade on 2024-04-22T14:46:48
-
@GeoffTearle can you confirm that your clara is now working fine with things fixed now? Or are there other issues?
By Andreas Kemnade on 2024-05-04T00:19:08
Edited by Ghost User -
Actually, @akemnade I've just come across one issue but I'm not sure if its related. But my Claras CPU is locked to the lowest frequency, and when I check
dmesgthere's hundreds of this log:[83791.375121] DCDC2: unsupportable voltage range: 1175000-1000000uV [83791.375207] DCDC2: unsupportable voltage range: 1175000-1000000uV [83791.375257] cpu cpu0: failed to scale vddsoc up: -22 [83791.375298] cpufreq: __target_index: Failed to change cpu frequency: -22By Geoffrey Tearle on 2024-05-08T02:58:45
-
I've made a new issue to track this here
By Geoffrey Tearle on 2024-05-08T20:15:19
mentioned in issue #2811 (closed)
By Geoffrey Tearle on 2024-05-08T20:14:45
