Is this means hardware fault of paperwhite?

[demfare]

Hi, every one. I'm in china , and I had bought a kpw from japan. When I received my kpw, I pressed the power button, the screen change to the "Big tree", and then it stopped!
I bought a USB-TTL convertor, and what it print is as follow. I tried to update bin file, flash main_kernel.img/diags_kernel.img/pw_5.2.0-mmcblk0p2.img, but it still cannot work.
Then I found my print is different with others, Is this means hardware fault? Please help mel, thank you very much.

the print:

U-Boot 2009.08-lab126 (Jan 08 2013 - 21:47:48)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 66666666Hz
ipg per clock : 66666666Hz
uart clock    : 24000000Hz
ahb clock     : 133333333Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Celeste WFO (256 MB)
Boot Reason: [POR]
Boot Device: MMC
Board Id: 00A1607130530E4S
S/N: B024160430561V99
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffc000
POST done in 17 ms
Hit any key to stop autoboot:  0 
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4608640 Bytes =  4.4 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
MX50 LPDDR2 MfgID: 0x3 [Elpida]
kernel: E papyrus:Power_good_timed_out::
papyrus 1-0068: Papyrus: Probe fail wait power good
2.6.31-rt11-lab126 #1 Tue Jan 8 22:06:21 PST 2013 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (39836 bytes)
regulator: Unable to get requested regulator: DISPLAY
mxc_epdc_fb mxc_epdc_fb: Unable to get display PMIC regulator.err = 0xffffffed
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (51424 bytes)
ERROR:/dev/fb0:No such device(19)
Press [ENTER] for recovery menu...       0 /INFO:!!! Checking MBR /dev/mmcblk0 !!!!  
INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 4, start sector is 1044480
INFO:maximizing partition 2863104 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/44736 size=1465909248 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    2863088
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
BOOTING DEFAULT.
  argc == 11
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p1"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
  argv[9]: "mem=256M"
  argv[10]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1)
kinit: root_dev = dev(179,1)
kinit: /dev/root appears to be a ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.
info system:emiting_event:mounted_proc:
info system:emiting_event:mounted_sys:
info system:emiting_event:mounted_dev:
info system:emiting_event:mounted_tmpfs:
info milestone:4.63:sy50:
init.exe: recevent pre-start process (484) terminated with status 1
info system:start:time=4680:
info hardware:no_wan::WiFi only device. No WAN found
info system:config:platform=yoshime3,board=celeste,rev=22,proto=N,wifi=Y,wan=N:
info milestone:4.89:sy51:
info milestone:5.52:sy99:
info system:done:time=5550:
info system_cramfs_loopbacks:mountingcramfs:Mounting compressed directories filesystem images:
info system_cramfs_loopbacks:mounted:Image /lib/firmware/cyttsp.cramfs.img mounted:
info system_cramfs_loopbacks:mounted:Image /usr/share/X11/xkb.cramfs.img mounted:
info system_cramfs_loopbacks:mounted:Image /usr/java/lib/fonts.cramfs.img mounted:
info system_cramfs_loopbacks:mounted:Image /etc/kdb.src.cramfs.img mounted:
info system_cramfs_loopbacks:mounted:Image /usr/lib/locale.cramfs.img mounted:
info system_cramfs_loopbacks:mounted:Image /usr/share/keyboard.cramfs.img mounted:
info system:emiting_event:mounted_cramfs_loopbacks:
info milestone:6.18:fs75:
info system:emiting_event:loaded_modules_dependencies:
info modules:modprobe:loading module g_file_storage:
info system:emiting_event:loaded_g_file_storage:
info modules:modprobe:loading module fuse:
info system:emiting_event:loaded_fuse:
info hardware:no_wan::WiFi only device. No WAN found
info system:emiting_event:loaded_ppp_async:
info milestone:6.56:fs00:
info system:emiting_event:loaded_fakekey:



Welcome to Kindle!

kindle login: info system:emiting_event:mounted_varLocal:
info milestone:6.74:fs25:
info milestone:6.79:vi00:
info milestone:7.00:vi99:
info display:started:time=7010:
info system:emiting_event:display_ready:
info battery:charged:cap=100,mV=4201,mAH=1412:
info userstore:run:time=7250,action=start:
info system:emiting_event:battery_ready:
info cyttsp:update:vendor=CANDO:
info system:emiting_event:loaded_touch:
info system:emiting_event:mounted_userstore:
info milestone:8.03:fs50:
info milestone:8.05:fs90:
info milestone:8.08:fs99:
info milestone:8.11:sys99:
info system:emiting_event:dbus_ready:
info dbus:check-update:status=2:dbus_ready sent
info hardware:no_wan::WiFi only device. No WAN found
info milestone:9.39:xx00:
info X:load:time=9470:
info X:xorg.conf:Generating xorg.conf:
info X:makexconfig:Celeste Input device detection status:
info X:makexconfig:Touch device: OK:
info X:makexconfig:Accelerometer device: N/A !!:
info X:xorg.conf:xorg.conf generated:
info milestone:10.14:xx50:
info X:starting:time=10170:
info x_monitor:x_monitor starts::
info x_monitor:read_counters::REBOOTS=2, RESTART=0, REBOOT_LIMIT=1, RESTART_LIMIT=5 
crit x_monitor:shutdown::REBOOTS=2, REBOOT_LIMIT=1, shutdown_mode=cust_service 
info shutdown:begin:level=0,halt=1,special=cust_service:
info shutdown:closing password dialog::
warn shutdown_showimage:x/blanket is not running:screen not updated:
warn shutdown:splash image not displayed::
info upstart_f:stopping_job:job=lab126:
info upstart_f:job_already_stopped:job=x:
info upstart_f:jobs_stopped:elapsed_ms=0,timeout_ms=45000:
info shutdown:cust_service:starting:
info ss_cust_service:nothing to do for this shutdown mode:"cust_service":
info ss_cust_service:completed successfully::
info shutdown:cust_service:done:
info upstart_f:stopping_job:job=filesystems:
info filesystems_userstore:unmount_userstore:Unmounting UserStore:
info filesystems_var_local:rotate_log:Rotating Logs:
info userstore:run:time=13590,action=stop:
err mntus:partition_unmount_failed::partition unmount failed (1)
info filesystems_var_local:unmount_varLocal:Unmounting VarLocal:
info upstart_f:jobs_stopped:elapsed_ms=3800,timeout_ms=30000:
info shutdown:mounting root filesystem read-only::
info shutdown:syncing disks::
info shutdown:end:level=0,halt=1:
System halted.
Halting ...

[twobob]

Spoiler:

I suppose the module could be failing somehow?

Loaded module /lib/modules/eink_fb_waveform.ko (39836 bytes)

but honestly that is outside my knowledge. But it says Loaded rather than an error about the loading itself...

So possibly not that.

But... what confuses me is you say the screen actually "works" so I fail to see how it could be "broken"...

Hmmm... maybe someone with ninja module skills can help you further.


did you try a few things with regards to the module? like err... modprobe to check it actually is loaded. Or modinfo maybe, I dont have a PW so here my help (such as it was) ends.

Hope you get it sorted.

see below... I thought you inferred the screen was working... evidentially not.

[hawhill]

Oh dear, it looks like a hardware fault. Before the e-ink drivers are loaded, the PMIC gives an error - for the DISPLAY regulator. That is bad - the PMIC is the power source (or better phrased: the power distribution chip). So likely, the e-ink system does not get any power, hence no wonder that the driver for it fails, too.

If it is open anyway, have a close look if some traces have been shortened. Maybe the cable for the display isn't fit correctly to its socket (is there any?).

So yes, hardware fault, unfortunately.

[szfisher]

Try to clear BOOT COUNTER and check difference...

[hawhill]

Given the error messages highlighted in red, I really doubt that this is worth the hassle... If possible at all, since the KPW is a bit more difficult to handle than the KT.