Before responding to your latest post, I want to report some progress using the tarball you sent me and sha256sum. That procedure using sha256sum is quite neat and will be added to my toolbox.
I did find that after extracting your tarball, I had to also extract two additional tarballs inside it. These tarballs are extracted by /etc/init.d/rc5:
Code:
tony@tony-Vostro-2520:~/BloodRagg$ sudo tar xzf usr.tgz -C .
tony@tony-Vostro-2520:~/BloodRagg$ sudo tar xzf etc/tz.tgz -C etc
tony@tony-Vostro-2520:~/BloodRagg$ sudo rm usr.tgz
tony@tony-Vostro-2520:~/BloodRagg$ sudo rm etc/tz.tgz
tony@tony-Vostro-2520:~/BloodRagg$ sudo find . -type f -exec sha256sum {} \; > sha256sums.txt
tony@tony-Vostro-2520:~/BloodRagg$ cat sha256sums.txt | wc -l
1944
I copied the sha256sums.txt on my sd card, and from the kobo serial session did the comparison:
Code:
# cd /
# sha256sum -c /mnt/sd/fs/sha256sums.txt | grep -v "OK$"
./usr/local/Kobo/libnickel.so.1.0.0: FAILED
./usr/local/Kobo/dicthtml/zt.html: FAILED
./usr/local/Kobo/dicthtml/dn.html: FAILED
./usr/local/Kobo/dicthtml/mk.html: FAILED
./usr/local/Kobo/dicthtml/fw.html: FAILED
./usr/local/Kobo/dicthtml/ap.html: FAILED
./usr/local/Kobo/dicthtml/oy.html: FAILED
./usr/local/Kobo/dicthtml/ck.html: FAILED
./usr/local/Kobo/dicthtml/qp.html: FAILED
./usr/local/Kobo/dicthtml/sk.html: FAILED
./usr/local/Kobo/dicthtml/kh.html: FAILED
./usr/local/Kobo/dicthtml/iw.html: FAILED
./usr/local/Kobo/dicthtml/xc.html: FAILED
./usr/local/Kobo/dicthtml/ur.html: FAILED
./usr/local/Kobo/dicthtml/ab.html: FAILED
./usr/local/Kobo/dicthtml/dt.html: FAILED
./usr/local/Kobo/dicthtml/du.html: FAILED
./usr/local/Kobo/dicthtml/aa.html: FAILED
./usr/local/Kobo/dicthtml/wt.html: FAILED
./usr/local/Kobo/dicthtml/kw.html: FAILED
./usr/local/Kobo/dicthtml/in.html: FAILED
./usr/local/Kobo/dicthtml/cd.html: FAILED
./usr/local/Kobo/dicthtml/hf.html: FAILED
./usr/local/Kobo/dicthtml/tl.html: FAILED
./usr/local/Kobo/dicthtml/cq.html: FAILED
./usr/local/Kobo/dicthtml/rn.html: FAILED
./usr/local/Kobo/dicthtml/ua.html: FAILED
./usr/local/Kobo/dicthtml/sw.html: FAILED
./usr/local/Kobo/dicthtml/hu.html: FAILED
./usr/local/Kobo/dicthtml/fo.html: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtXmlPatterns.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtNetwork.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtGui.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtDBus.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtScript.so.4.6.2: FAILED
./etc/zoneinfo-leaps/Mideast/Riyadh88: FAILED
./etc/zoneinfo-leaps/Europe/Nicosia: FAILED
./etc/zoneinfo-leaps/Europe/Istanbul: FAILED
./etc/zoneinfo-leaps/Turkey: FAILED
./etc/zoneinfo-leaps/Asia/Karachi: FAILED
./etc/zoneinfo-leaps/Asia/Novosibirsk: FAILED
./etc/zoneinfo-leaps/Asia/Kuching: FAILED
./etc/zoneinfo-leaps/Asia/Almaty: FAILED
./etc/zoneinfo-leaps/Asia/Brunei: FAILED
./etc/zoneinfo-leaps/Asia/Anadyr: FAILED
./etc/zoneinfo-leaps/Asia/Kuala_Lumpur: FAILED
./etc/zoneinfo-leaps/Asia/Kabul: FAILED
./etc/zoneinfo-leaps/Asia/Jayapura: FAILED
./etc/zoneinfo-leaps/Asia/Aqtau: FAILED
./etc/zoneinfo-leaps/Asia/Riyadh: FAILED
./etc/zoneinfo-leaps/Asia/Dubai: FAILED
./etc/zoneinfo-leaps/Asia/Riyadh88: FAILED
./etc/zoneinfo-leaps/Asia/Sakhalin: FAILED
./etc/zoneinfo-leaps/Asia/Pontianak: FAILED
./etc/zoneinfo-leaps/Asia/Vientiane: FAILED
./etc/zoneinfo-leaps/Asia/Nicosia: FAILED
./etc/zoneinfo-leaps/Asia/Istanbul: FAILED
./etc/zoneinfo-leaps/Asia/Kuwait: FAILED
./etc/zoneinfo-leaps/Asia/Jakarta: FAILED
./etc/zoneinfo-leaps/Asia/Novokuznetsk: FAILED
./etc/zoneinfo-leaps/Asia/Kamchatka: FAILED
./etc/zoneinfo-leaps/Asia/Bahrain: FAILED
./sha256sums.txt: FAILED
sha256sum: WARNING: 64 of 1944 computed checksums did NOT match
After fixing those problems (and getting a clean bill of health from sha256sums), my kobo now starts nickel without a segmentation fault.
It now boots and goes to a "BOOKS, BY TITLE" page on the Kobo!
I see the following in the serial session
Code:
init Flash Error !!!
fd_init Done !!!
insmod: can't insert '/lib/modules/module.ko': Operation not permitted
mount: mounting /dev/mtdblock6 on /mnt/onboard failed: No such device or address
hwclock: settimeofday() failed: Invalid argument
PORT: 4034920448 baud 115200 uart: ulcon = 0x00000003, ucon = 0x000003c5, ufcon = 0x00000051 ubrdiv 0x00000023 umcon 0x00000000
Please press Enter to activate this console. status != ButtonDev.StatusBYKeypad!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!#:.
****AP read ADC: ret 581
ret 581
IOCTL:READ 581
no usb connected, turn LED off
TZ= "NickelTime0"
CHECKING DB VERSION FOR MIGRATION
DESIRED VERSION: 12
CURRENT VERSION: 12
Writing `version` file for use by the desktop client
Setting current page: 1
s1d13521fb_ioctl() 0 params cmd=0x4528
s1d13521fb_ioctl() 0 params cmd=0x4529
s1d13521fb_ioctl() 0 params cmd=0x4528
s1d13521fb_ioctl() 0 params cmd=0x4529
s1d13521fb_ioctl() 0 params cmd=0x4528
s1d13521fb_ioctl() 0 params cmd=0x4529
s1d13521fb_ioctl() 0 params cmd=0x4528
s1d13521fb_ioctl() 0 params cmd=0x4529
*5 c=0x88 h=1 t=1*RealTimeClock::RealTimeClock(int) minutes == 15
E=E=E=E=E=E=E=E=freeze!!!!!!!!!!!!!!!!!!!!
E=E=E=E=
But it's not all good news. If I disconnect the kobo from the FTDI adapter and reboot, it doesn't get to the same page. It just sits there with the blue LED on, with none of the 7 black squares it normally puts up for progress.
If I then connect the FTDI adapter, I get a u-boot prompt
If I enter the boot command at the u-boot prompt, it boots as I described above.
One step forward, two steps back...