11-15-2025, 12:04 PM
|
#1 |
|
Junior Member
 Posts: 4
Karma: 10
Join Date: May 2025
Device: Kobo Libra 2
|
Libra 2 stuck in boot loop
This is a bit of documenting my process that other may find interesting. If you've got more ideas on what to follow up on as well I'm keen to hear them!
My Kobo Libra 2 (N418) got stuck in the boot loop after uploading an epub to the device via a USB cable. Resulting in a blank screen, and continuing flashing indicator light. After posting here I uploaded three different revisions of the firmware to a new uSD card using balenaEtcher, I wasn't able to find a particular revision label on the board so am trying all three. The board has E70K14 and the serial number starts with N4182C.... Maybe that's E revision... Most of these I was testing by holding the power button, the indicator would stop flashing, go solid on then solid off before starting to blink again. kobo_libra2 4.raw - On this revision of the firmware after the indicator going solid off the front backlight would flash on then off before the continual blinking began Rev E & Rev G - Here the backlight didn't flash on (it also wasn't as consistent going into the loop? Sometimes required power to be attached) I checked the battery voltage after this and was able to hold steady 3.8-3.9v without external power attached and after looping for a while, I concluded it's likely not the battery. After this I noticed the serial output on the device and attached a USB Serial device. Each of the revisions of the firmware gave a pretty similar output. Here was the output for Rev E firmware. Code:
U-Boot 2016.03-00122-gdb90f902ea (Mar 30 2022 - 10:14:36 +0800)
CPU: Freescale i.MX6SLL rev1.1 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 40C
Reset cause: POR
Board: MX6SLL LPDDR2 NTX
I2C: ready
DRAM: 512 MiB
__get_sd_number(),cfg23=1,cfg24=0
MMC: board_mmc_init() : isd=1
board_mmc_init() : wifi=2
FSL_SDHC: 0, FSL_SDHC: 1
In: serial
Out: serial
Err: serial
ntx_hw_early_init() 0
ram p=80000000,size=536870912
switch to partitions #0, OK
mmc0 is current device
mmc read 0x9ffffe00 0x3ff 0x1
MMC read: dev # 0, block # 1023, count 1 ... 1 blocks read: OK
mmc read 0x9ffffe00 0x400 0x1
MMC read: dev # 0, block # 1024, count 1 ... 1 blocks read: OK
ntx_hw_early_init() BD71828 INIT
BD71828_regulator_init
BD71828 RESETSRC [0x3]=0x1
BD71828 KEYSTATUS [0xe2]=0x3c
BD71828 BOOTSRC [0x2]=0x81
COLD reset from others, poweroff
BD71828 read battery capacity 058, 911,1545
ntx_hw_late_init()
mmc read 0x9ffffc00 0x1 0x1
MMC read: dev # 0, block # 1, count 1 ... 1 blocks read: OK
NTXSN not avalible !
ntx_gpio_get_value(404) : error parameter ! null ptr !
ntx_config_fastboot_layout():10 binaries partition added
ntx_config_fastboot_layout():3 mbr partition added
check_and_clean: reg 0, flag_set 0
Fastboot: Normal
Net: CPU Net Initialization Failed
No ethernet found.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
mmc read 0x80800000 0x800 0x2c00
MMC read: dev # 0, block # 2048, count 11264 ... 11264 blocks read: OK
Booting from mmc ...
mmc read 0x83000000 0x505 0x1
MMC read: dev # 0, block # 1285, count 1 ... 1 blocks read: OK
dtb size = 35513@83000000
mmc read 0x83000000 0x506 0x4b
MMC read: dev # 0, block # 1286, count 75 ... 75 blocks read: OK
hwcfgp=9ffffe00,pcb=101,customer=9
ntx_gpio_get_value(404) : error parameter ! null ptr !
ntx_wait_powerkey_ex() : checking power key ...
ntx_wait_powerkey_ex():wait condition check failed !!!
ESDin=0,UPGKey=0,PWRKey=1,USBin=0x0,BootESD=0,MenuKey=0
mmc read 0x9ffffc00 0x37ff 0x1
MMC read: dev # 0, block # 14335, count 1 ... 1 blocks read: OK
mmc read 0x9fdf8800 0x3800 0x103b
MMC read: dev # 0, block # 14336, count 4155 ... 4155 blocks read: OK
mmc read 0x9fdf8600 0x405 0x1
MMC read: dev # 0, block # 1029, count 1 ... 1 blocks read: OK
[WARNING] Binaries load sequence should Lo->Hi !
mmc read 0x9fdf5a00 0x406 0x17
MMC read: dev # 0, block # 1030, count 23 ... 23 blocks read: OK
Kernel RAM visiable size=509M->509M
hwcfg rootfstype : 2
hwcfg partition type : 2,bootmode=0
imx2_watchdog() : WCR=0x39
imx2_watchdog() : enable watchdog,timeout 30 secs,WCR=0x3b35
ntx_prebootm : cmd=setenv bootargs ${bootargs} hwcfg_p=0x9ffffe00 hwcfg_sz=110 waveform_p=0x9fdf8800 waveform_sz=212690t
Kernel image @ 0x80800000 [ 0x000000 - 0x4b8400 ]
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300bab8
Starting kernel ...
AW99703 TotalColors:11 , items:12
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 reg4 via I2C after waked! retry ...
sy7636 1-0062: Unable to write SY7636 register4 via I2C
sy7636 1-0062: Unable to write SY7636 register5 via I2C
sy7636 1-0062: Unable to write SY7636 register1 via I2C
sy7636 1-0062: Unable to write SY7636 register2 via I2C
sy7636 1-0062: Unable to write SY7636 register3 via I2C
sy7636 1-0062: Unable to write SY7636 register6 via I2C
i2c i2c-1: Device probe no ACK , retry 1/100 ...
i2c i2c-1: Device probe no ACK , retry 2/100 ...
i2c i2c-1: Device probe no ACK , retry 3/100 ...
i2c i2c-1: Device probe no ACK , retry 4/100 ...
i2c i2c-1: Device probe no ACK , retry 5/100 ...
i2c i2c-1: Device probe no ACK , retry 6/100 ...
i2c i2c-1: Device probe no ACK , retry 7/100 ...
i2c i2c-1: Device probe no ACK , retry 8/100 ...
i2c i2c-1: Device probe no ACK , retry 9/100 ...
i2c i2c-1: Device probe no ACK , retry 10/100 ...
i2c i2c-1: Device probe no ACK , retry 11/100 ...
i2c i2c-1: Device probe no ACK , retry 12/100 ...
i2c i2c-1: Device probe no ACK , retry 13/100 ...
i2c i2c-1: Device probe no ACK , retry 14/100 ...
i2c i2c-1: Device probe no ACK , retry 15/100 ...
i2c i2c-1: Device probe no ACK , retry 16/100 ...
i2c i2c-1: Device probe no ACK , retry 17/100 ...
i2c i2c-1: Device probe no ACK , retry 18/100 ...
i2c i2c-1: Device probe no ACK , retry 19/100 ...
i2c i2c-1: Device probe no ACK , retry 20/100 ...
i2c i2c-1: Device probe no ACK , retry 21/100 ...
i2c i2c-1: Device probe no ACK , retry 22/100 ...
i2c i2c-1: Device probe no ACK , retry 23/100 ...
i2c i2c-1: Device probe no ACK , retry 24/100 ...
i2c i2c-1: Device probe no ACK , retry 25/100 ...
i2c i2c-1: Device probe no ACK , retry 26/100 ...
i2c i2c-1: Device probe no ACK , retry 27/100 ...
i2c i2c-1: Device probe no ACK , retry 28/100 ...
i2c i2c-1: Device probe no ACK , retry 29/100 ...
i2c i2c-1: Device probe no ACK , retry 30/100 ...
i2c i2c-1: Device probe no ACK , retry 31/100 ...
i2c i2c-1: Device probe no ACK , retry 32/100 ...
i2c i2c-1: Device probe no ACK , retry 33/100 ...
i2c i2c-1: Device probe no ACK , retry 34/100 ...
i2c i2c-1: Device probe no ACK , retry 35/100 ...
i2c i2c-1: Device probe no ACK , retry 36/100 ...
i2c i2c-1: Device probe no ACK , retry 37/100 ...
i2c i2c-1: Device probe no ACK , retry 38/100 ...
i2c i2c-1: Device probe no ACK , retry 39/100 ...
i2c i2c-1: Device probe no ACK , retry 40/100 ...
i2c i2c-1: Device probe no ACK , retry 41/100 ...
i2c i2c-1: Device probe no ACK , retry 42/100 ...
i2c i2c-1: Device probe no ACK , retry 43/100 ...
i2c i2c-1: Device probe no ACK , retry 44/100 ...
i2c i2c-1: Device probe no ACK , retry 45/100 ...
i2c i2c-1: Device probe no ACK , retry 46/100 ...
i2c i2c-1: Device probe no ACK , retry 47/100 ...
i2c i2c-1: Device probe no ACK , retry 48/100 ...
i2c i2c-1: Device probe no ACK , retry 49/100 ...
i2c i2c-1: Device probe no ACK , retry 50/100 ...
i2c i2c-1: Device probe no ACK , retry 51/100 ...
i2c i2c-1: Device probe no ACK , retry 52/100 ...
i2c i2c-1: Device probe no ACK , retry 53/100 ...
i2c i2c-1: Device probe no ACK , retry 54/100 ...
i2c i2c-1: Device probe no ACK , retry 55/100 ...
i2c i2c-1: Device probe no ACK , retry 56/100 ...
i2c i2c-1: Device probe no ACK , retry 57/100 ...
i2c i2c-1: Device probe no ACK , retry 58/100 ...
i2c i2c-1: Device probe no ACK , retry 59/100 ...
i2c i2c-1: Device probe no ACK , retry 60/100 ...
i2c i2c-1: Device probe no ACK , retry 61/100 ...
i2c i2c-1: Device probe no ACK , retry 62/100 ...
i2c i2c-1: Device probe no ACK , retry 63/100 ...
i2c i2c-1: Device probe no ACK , retry 64/100 ...
i2c i2c-1: Device probe no ACK , retry 65/100 ...
i2c i2c-1: Device probe no ACK , retry 66/100 ...
i2c i2c-1: Device probe no ACK , retry 67/100 ...
i2c i2c-1: Device probe no ACK , retry 68/100 ...
i2c i2c-1: Device probe no ACK , retry 69/100 ...
i2c i2c-1: Device probe no ACK , retry 70/100 ...
i2c i2c-1: Device probe no ACK , retry 71/100 ...
i2c i2c-1: Device probe no ACK , retry 72/100 ...
i2c i2c-1: Device probe no ACK , retry 73/100 ...
i2c i2c-1: Device probe no ACK , retry 74/100 ...
i2c i2c-1: Device probe no ACK , retry 75/100 ...
i2c i2c-1: Device probe no ACK , retry 76/100 ...
i2c i2c-1: Device probe no ACK , retry 77/100 ...
i2c i2c-1: Device probe no ACK , retry 78/100 ...
i2c i2c-1: Device probe no ACK , retry 79/100 ...
i2c i2c-1: Device probe no ACK , retry 80/100 ...
i2c i2c-1: Device probe no ACK , retry 81/100 ...
i2c i2c-1: Device probe no ACK , retry 82/100 ...
i2c i2c-1: Device probe no ACK , retry 83/100 ...
i2c i2c-1: Device probe no ACK , retry 84/100 ...
i2c i2c-1: Device probe no ACK , retry 85/100 ...
i2c i2c-1: Device probe no ACK , retry 86/100 ...
i2c i2c-1: Device probe no ACK , retry 87/100 ...
i2c i2c-1: Device probe no ACK , retry 88/100 ...
i2c i2c-1: Device probe no ACK , retry 89/100 ...
i2c i2c-1: Device probe no ACK , retry 90/100 ...
i2c i2c-1: Device probe no ACK , retry 91/100 ...
i2c i2c-1: Device probe no ACK , retry 92/100 ...
i2c i2c-1: Device probe no ACK , retry 93/100 ...
i2c i2c-1: Device probe no ACK , retry 94/100 ...
i2c i2c-1: Device probe no ACK , retry 95/100 ...
i2c i2c-1: Device probe no ACK , retry 96/100 ...
i2c i2c-1: Device probe no ACK , retry 97/100 ...
i2c i2c-1: Device probe no ACK , retry 98/100 ...
i2c i2c-1: Device probe no ACK , retry 99/100 ...
i2c i2c-1: Device probe no ACK , retry 100/100 ...
i2c i2c-1: Device no ACK and retry 100 times failed
dt_get_rsens() RSENS dts property 27000000
bd71827-power bd71827-power: Power-on-reset off
bd71827-power bd71827-power: Temperature = 26
bd71827-power bd71827-power: bd71827_init_hardware() read_cc = 59747514
bd71827-power bd71827-power: VM_OCV_3 = 3783000
bd71827-power bd71827-power: bd71827_init_hardware() sorg = 47, soc_cal = 35, voltage 3783000
bd71827-power bd71827-power: bd71827_init_hardware() reset_for_manual_Calibration
bd71827-power bd71827-power: VM_OCV_3 = 3785000
bd71827-power bd71827-power: ocv 3785000
bd71827-power bd71827-power: soc 371[0.1%]
bd71827-power bd71827-power: calibration_coulomb_counter() CC_CCNTD = 46923776
bd71827-power bd71827-power: bd71827_init_hardware() CC_CCNTD = 46923776
bd71827-power bd71827-power: bd71827_init_hardware() pwr->soc = 37
bd71827-power bd71827-power: bd71827_init_hardware() pwr->clamp_soc = 37
=== fts_ts_init_2201 ===
elan_ktf 1-0010: [elan] enter elants_i2c_probe..0823_1..
kx122 0-001e: Unable to read property x-map. Use default 0.
kx122 0-001e: Unable to read property y-map. Use default 1.
kx122 0-001e: Unable to read property z-map. Use default 2.
kx122 0-001e: Unable to read property y-negate. Use default 0.
kx122 0-001e: Unable to read property z-negate. Use default 0.
kx122 0-001e: Unable to read property g-range. Use default 8g
kx122 0-001e: Failed to look up default state
[kx122_probe_2674] irq1:121 , gpio1:91
[kx122_probe_2715] using irq1:121
[kx122_probe_2747] g_range:8
[kx122_probe_2780] using irq
[kx122-CNTL1]:1
[kx122-CNTL2]:3f
[kx122-CNTL3]:98
[KX122_TILT_ANGLE_LL]:11
[kx122_probe_2827] success
[P15USB30216C_probe_808] irq:176
[P15USB30216C_probe_828] Set Reg: 0x46
[P15USB30216C] set reg 0x46 failed !!!
syscon-poweroff 20cc000.snvs:snvs-poweroff: pm_power_off already claimed 80021adc ntx_machine_poweroff
cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
Unable to handle kernel NULL pointer dereference at virtual address 00000048
pgd = 80004000
[00000048] *pgd=00000000
Internal error: Oops: 805 [#1] PREEMPT SMP ARM
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.15-00769-g20c06d7161f #62
Hardware name: Freescale i.MX6 SoloLite (Device Tree)
task: 9c058000 ti: 9c05c000 task.ti: 9c05c000
PC is at sy7636_int_callback_setup+0x0/0xc
LR is at mxc_epdc_fb_probe+0x1d38/0x21cc
pc : [<80274a34>] lr : [<80243568>] psr: 60000113
sp : 9c05de08 ip : 00000032 fp : 9c4ea438
r10: ffffffff r9 : 8087bd48 r8 : 00000000
r7 : 00004000 r6 : 00000000 r5 : 8075a474 r4 : 00000000
r3 : 808f5960 r2 : 00000000 r1 : 802486e8 r0 : 00000000
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 10c53c7d Table: 80004059 DAC: 00000015
Process swapper/0 (pid: 1, stack limit = 0x9c05c210)
Stack: (0x9c05de08 to 0x9c05e000)
de00: 00000010 00000a00 9c4ea000 9c05de28 8075f548 808f5960
de20: 808a6508 9c4ea214 808a64ec 9c4ea438 808ed8f0 9c4d0410 00000000 00000000
de40: 00000001 00000004 786dbbe0 64706563 00626663 9c0dbbe0 8075f548 00000001
de60: 9c4d0410 808f8898 9c0daa10 8087bd60 fffffdfb 00000000 808583b4 8085f7d4
de80: 00000000 802c2e38 808f8898 9c0daa10 8087bd60 00000000 00000000 802c16d4
dea0: 9c0daa10 8087bd60 9c0daa44 8088af78 00000000 802c18e4 00000000 8087bd60
dec0: 802c1858 802bfd60 9c02c95c 9c0d39b4 8087bd60 9c4caa00 00000000 802c0e64
dee0: 8075a3d4 8086a6a0 9c4cf2c0 8087bd60 8086a6a0 9c4cf2c0 808420fc 802c1ee4
df00: 8086a6a0 8086a6a0 9c4cf2c0 80009718 80858390 8013154c 00000000 9c09d080
df20: 00000000 808728bc 60000113 00000000 9fbfca60 9fbfca5b 805f97fc 80050e44
df40: 00000000 807285ac 00000007 00000007 808728a4 000000a8 00000007 808a6000
df60: 000000a8 00000007 808a6000 808a6000 808583b0 80808db0 00000007 00000007
df80: 80808594 8005538c 00000000 8059eeec 00000000 00000000 00000000 00000000
dfa0: 00000000 8059eef4 00000000 8000f528 00000000 00000000 00000000 00000000
dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 25000280 0f400440
[<80274a34>] (sy7636_int_callback_setup) from [<80243568>] (mxc_epdc_fb_probe+0x1d38/0x21cc)
[<80243568>] (mxc_epdc_fb_probe) from [<802c2e38>] (platform_drv_probe+0x44/0xac)
[<802c2e38>] (platform_drv_probe) from [<802c16d4>] (driver_probe_device+0x174/0x2b4)
[<802c16d4>] (driver_probe_device) from [<802c18e4>] (__driver_attach+0x8c/0x90)
[<802c18e4>] (__driver_attach) from [<802bfd60>] (bus_for_each_dev+0x68/0x9c)
[<802bfd60>] (bus_for_each_dev) from [<802c0e64>] (bus_add_driver+0x148/0x1f0)
[<802c0e64>] (bus_add_driver) from [<802c1ee4>] (driver_register+0x78/0xf8)
[<802c1ee4>] (driver_register) from [<80009718>] (do_one_initcall+0x8c/0x1d4)
[<80009718>] (do_one_initcall) from [<80808db0>] (kernel_init_freeable+0x144/0x1e4)
[<80808db0>] (kernel_init_freeable) from [<8059eef4>] (kernel_init+0x8/0xe8)
[<8059eef4>] (kernel_init) from [<8000f528>] (ret_from_fork+0x14/0x2c)
Code: e3a03000 e1a00003 e5823044 e12fff1e (e5801048)
Open /dev/watchdog error
---[ end trace 469cf16a95b8b885 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Next steps I wanted to try out
Does anyone have the logs from a clean boot sequence? It would be interesting to compare them, unfortunately most logs I'm seeing are ones with issues. Do you make anything differently from the logs? 
|
|
|
|
11-15-2025, 02:40 PM
|
#2 |
|
Junior Member
Posts: 4
Karma: 10
Join Date: May 2025
Device: Kobo Libra 2
|
Linking a few things together here I think the firmware revision is likely wrong here for me. The power management for the screen looks to be a JD9930 instead of the SY7636 that the firmware is looking for. So something isn't aligning there.
However all three revisions offered all seemed to try and communicate with a SY7636 device. Last edited by LukeLibra; 11-15-2025 at 02:43 PM. |
|
|
|
|
11-15-2025, 05:29 PM
|
#3 |
|
Zealot
 
Posts: 142
Karma: 3339
Join Date: Jun 2017
Device: Tolino,Kobo,Onyx,Kindle,BN,PB,Likebook...
|
Hi,
I'm not sure if this will help you, but I sent you a private message with an image of the SD card from the 6F0 motherboard. https://ibb.co/0y303tHX https://ibb.co/hJTmF87M Last edited by Waldy; 11-15-2025 at 05:43 PM. |
|
|
|
|
11-15-2025, 06:39 PM
|
#4 |
|
Junior Member
Posts: 4
Karma: 10
Join Date: May 2025
Device: Kobo Libra 2
|
Legend, that's done it!
Appreciate the help, I thought it was going to be a much more in depth adventure 
|
|
|
|
|
11-15-2025, 09:07 PM
|
#5 | |
|
Grand Sorcerer
Posts: 13,710
Karma: 80104526
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
|
Quote:
|
|
|
|
|
|
Yesterday, 01:52 AM
|
#6 | |
|
Bibliophagist
Posts: 48,443
Karma: 174510100
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
|
|
|
|
|
|
Yesterday, 06:34 AM
|
#7 | |
|
Zealot
Posts: 142
Karma: 3339
Join Date: Jun 2017
Device: Tolino,Kobo,Onyx,Kindle,BN,PB,Likebook...
|
Quote:
Today I sent you a Kobo Libra2 image with a 37NB-E70K1M+6F0 motherboard PCB_LVL='F'. I still don't understand what we mean by "revision" Using the Kobo Nia with a 37NB-E60U20+4C1 motherboard and PCB_LVL='B' as an example, is it rev C or rev B? For those requesting images, it's highly recommended to specify the motherboard version; you'll need to open the back cover anyway. Last edited by Waldy; Yesterday at 12:39 PM. |
|
|
|
|
|
Yesterday, 05:51 PM
|
#8 | |
|
Bibliophagist
Posts: 48,443
Karma: 174510100
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
And yes, it is good when for those Kobo ereaders with multiple versions, the requester includes the motherboard version. |
|
|
|
|
 |
| Tags |
| kobo libra 2 |
«
Previous Thread
|
Next Thread
»
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Troubleshooting PW3 stuck in boot loop | zuma | Amazon Kindle | 1 | 06-01-2021 06:36 PM |
| [PW] Stuck in boot loop? | abarthch | Kindle Developer's Corner | 11 | 02-04-2016 01:20 PM |
| Stuck in Boot Loop -- Options? | brannanbenjamin | Kindle Developer's Corner | 6 | 01-07-2014 01:01 PM |
| Kindle 4 stuck in boot loop | gers1978 | Amazon Kindle | 5 | 07-16-2013 07:56 AM |
| Paperwhite 5.3.1 stuck on boot loop | ponso | Kindle Developer's Corner | 7 | 03-17-2013 09:36 AM |
All times are GMT -4. The time now is 02:55 PM.