**** BEGIN LOGGING AT Wed May 24 03:00:05 2017
May 24 08:37:39 <VartiWork> greguu: the frankenstein version boots without problems, I was very happy to see it working :)
May 24 08:38:15 <VartiWork> greguu: the other, experimental f2fs does not, blinking led all the time and black screen as usual
May 24 08:40:20 <greguu> VartWork: thanks, can you try this one https://github.com/greguu/linux-3.10.y-c3x00-f2fs-kexec-r0/releases/download/r0/linux-3.10.y-c1000-f2fs-kexec-test-r0.tar.gz
May 24 08:40:35 <greguu> VartiWork: I think I uploaded the wrong zImage last time
May 24 08:42:43 <greguu> with the frankenstein kexecboot you should be able to test if the 4.12 kernel boots, too.
May 24 08:42:56 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02276.jpg
May 24 08:43:12 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02278.jpg
May 24 08:43:21 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02279.jpg
May 24 08:43:27 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02280.jpg
May 24 08:43:41 <VartiWork> just in case there's anything useful in the log
May 24 08:44:19 <VartiWork> ok, I'll try the new kexec soon, I have my Akita here
May 24 08:46:07 <VartiWork> I have only little time this morning, I have quickly tried to boot a 64GB ext3 alarmz rootfs and kernel with no avail
May 24 08:46:11 <VartiWork> have = had
May 24 08:46:35 <greguu> did you see a kernel option in kexecboot ?
May 24 08:48:02 <greguu> ant_work : should the 2.6 kernel not detect the FS on mtd2 and mtd3 ? http://www.oesf.org/pics/IMG-20170524-02279.jpg
May 24 08:49:09 <greguu> VartiWork, does the 64GB card actually show a kernel as a boot option in the kexecboot menu ? maybe try a 4GB card or smaller ?
May 24 08:49:17 <VartiWork> no, the card wasn't recognised at all
May 24 08:49:40 <VartiWork> I anyway forgot to change the config file in /boot to the older syntax
May 24 08:49:48 <ant_work> hello
May 24 08:50:00 <greguu> you do not need to change the syntax, as the kexecboot is 0.6
May 24 08:50:06 <VartiWork> ah ok
May 24 08:50:32 <VartiWork> I'll also try with a 2GB card
May 24 08:50:38 <ant_work> greguu, which FS on mtd2/3 ?
May 24 08:50:42 <VartiWork> hi ant_work
May 24 08:50:48 <ant_work> old Sharp stuff?
May 24 08:51:01 <greguu> ant_work: well stock rom was jffs no _
May 24 08:51:35 <VartiWork> my mtd2 and mtd3 are jffs v1 at the moment
May 24 08:51:45 <VartiWork> from a NAND restore
May 24 08:52:10 <ant_work> greguu, JFFS2 changed with 2.6.x
May 24 08:52:23 <greguu> ok, so it can not read the old one ?
May 24 08:52:53 <greguu> anyway, at least it boots.
May 24 08:53:35 <ant_work> sometimes I've seen it taking long time trying to scan/detect
May 24 08:55:47 <VartiWork> I have also tried various resets and switch off/on, kexec was always booting (so no "it boots only the first time" problem as on 4.x)
May 24 08:56:10 <VartiWork> and the boot is very fast, 2s roughly
May 24 08:57:01 <greguu> well, there is not much too it, also it did not find any boot devices or supported FS
May 24 08:57:33 <greguu> it would take longer to parse these and the boot.cfg(s)
May 24 08:57:53 <greguu> with this kernel you are stuck with ext3 and no UBI or F2FS
May 24 08:58:13 <greguu> also the main kernel may not boot even
May 24 08:58:19 <greguu> more testing
May 24 08:59:48 <greguu> 64GB is maybe not supported, at least not on 2.6.26
May 24 09:00:03 <greguu> I tried 16GB max on 3.x for SD / CF cards
May 24 09:00:39 <greguu> it may work with a SD to CF adapter ..
May 24 09:01:01 <greguu> anyway I go back on the couch....:) lazy today
May 24 09:01:19 <VartiWork> ok, we'll see, I'll do again tests during my lunch break (roughly after 1h 30m from now)
May 24 09:01:21 <greguu> let us know how you go with the 3.10.y kernel and booting also 4.12
May 24 09:01:27 <greguu> yes sure
May 24 09:01:56 <ant_work> maybe big cards need 3 sec delay as for spitz
May 24 09:02:05 <ant_work> akita has 2 atm
May 24 09:02:23 <ant_work> we must improve kexecboot here...
May 24 09:03:04 <VartiWork> we will eventually manage to fix it :)
May 24 09:03:37 <ant_work> It's like inotify/dnotify but done by hand
May 24 09:03:59 <ant_work> there is surely similar code to borrow around :)
May 24 11:03:58 <VartiWork> greguu: no luck with the new f2fs kexec, blinking led again
May 24 11:10:42 <VartiWork> I have just now realized that there was a third beta kexec to test, which I haven't tested and which seems you have removed: akita-test.tar.xz
May 24 11:11:10 <VartiWork> you asked me to test it 3 days ago
May 24 11:11:38 <VartiWork> (well, 4)
May 24 11:11:39 <VartiWork> May 20 22:04:46 <greguu> Varti: I have compiled a Akita version of the kexecboot kernel, disabled 3100/3200. Also one more version that has NAND completely disabled. Please try:https://github.com/greguu/linux-3.10.y-c3x00-f2fs-kexec-r0/releases/download/r0/akita-test.tar.xz
May 24 11:11:59 <VartiWork> do you still need me to test it?
May 24 11:27:25 <VartiWork> switched back to the frankenstein, put the latest rootfs on my 64GB SD
May 24 11:28:33 <VartiWork> this morning it was actually formatted as ext4, hence it didn't find it, I have now formatted it as ext3, kexec has recognised the partition and it is booting it!
May 24 11:29:31 <VartiWork> the kernel is now running fsck on /dev/mmcbl01blk0p1
May 24 11:30:09 <VartiWork> I wonder why, since I have it just formatted it to ext3 with gparted
May 24 11:32:39 <ant_work> VartiWork, pls try to kexec zImage in root of the card
May 24 11:32:51 <ant_work> put i.e. the latest 4.x kexecboot
May 24 11:33:12 <ant_work> no boot.cfg, anything, just zImage
May 24 11:35:35 <VartiWork> aha, so basically to try to boot kexec 4.x from within kexec 0.6
May 24 11:35:40 <VartiWork> ok, will try it now
May 24 11:36:05 <VartiWork> alarmz has anyway successfully booted, I'm in the shell now \o/
May 24 11:37:03 <VartiWork> btw why does Danboid suggest in his guide to do this once the rootfs has been copied to the SD card?
May 24 11:37:05 <VartiWork> # cp alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz /mnt/root/
May 24 11:39:59 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02281.jpg
May 24 11:40:01 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02282.jpg
May 24 11:40:02 <ant_work> you could also kexec -l zImage and kexec -e but you harm th efilesystem quitting abruptly
May 24 11:40:04 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02283.jpg
May 24 11:40:07 <VartiWork> http://www.oesf.org/pics/IMG-20170524-02284.jpg
May 24 11:40:15 <VartiWork> there's a FAIL btw during the boot
May 24 11:46:05 <ant_work> have you tried to kexec linux-kexecboot?
May 24 11:48:10 <VartiWork> yes, and it works
May 24 11:48:22 <VartiWork> I have used this: https://github.com/LinuxPDA/linux-kexecboot/blob/master/zaurus/kernel-4.4.8/installkit-akita.tar.gz
May 24 11:50:41 <ant_work> good news
May 24 11:50:52 <ant_work> but still it doesn't boot alone
May 24 11:51:19 <ant_work> can you pls flash it with nandlogical?
May 24 11:52:08 <ant_work>  nandlogical /dev/mtd1 WRITE 0x0E0000 0x140000 zImage.bin
May 24 11:52:25 <ant_work> so we rule out updater.sh
May 24 11:53:56 <VartiWork> it booted fine 5 times out of 5, by resetting, switching it off via menu, switching off with the battery removed
May 24 11:54:40 <ant_work> which one is fine? the 2.6 I understand
May 24 11:55:06 <VartiWork> 2.6 booting 4.x
May 24 11:55:48 <ant_work> that 4.x should boot fine alone as it does on spitz...
May 24 11:56:02 <VartiWork> I'll try with nandlogical soon (have to work now for a bit)
May 24 11:56:11 <ant_work> sure, np
May 24 12:05:19 <VartiWork> [13:55] <ant_work> that 4.x should boot fine alone as it does on spitz...
May 24 12:05:50 <ant_work> right
May 24 12:06:13 <VartiWork> no, I have never managed to boot it. It only boots (once) after doing a NAND restore -> flash and boot 2.6 -> flash and boot 4.4.8
May 24 12:06:19 <ant_work> if correctly flashed I add
May 24 12:07:52 <ant_work> but if 2.6 is flashed and boots the updater.sh does its job I'd say
May 24 12:08:29 <ant_work> then is a kernel issue, being as improbable as it is
May 24 12:09:42 <VartiWork> do you still want me to do try with nandlogical?
May 24 12:09:50 <VartiWork> to do try = to try
May 24 12:10:01 <ant_work> yes but with little hope...
May 24 12:10:05 <VartiWork> ok
May 24 12:10:33 <VartiWork> I'm thinking now on how to do this
May 24 12:10:49 <ant_work> you should kexec one of the OE images
May 24 12:10:56 <VartiWork> ok, got it
May 24 12:11:00 <ant_work> there is nandlogical inside
May 24 12:11:32 <VartiWork> maybe alarmz has it too, now that I have it booting, but better try the OE route
May 24 12:11:37 <ant_work> one small partition is enough
May 24 12:29:59 <VartiWork> I wonder if the 2.6 frankenstein version has the f2fs support... I'd like to have alarmz on an f2fs partition
May 24 12:33:46 <ant_work> not that one, f2fs was backported to 3.0, dunno if even for 2.6
May 24 12:33:57 <ant_work> probably someone did
May 24 12:44:28 <VartiWork> I guess I could try to boot 2.6, then ant's 3.x to recognise it
May 24 12:46:53 <VartiWork> I could make on the SD an ext3 partition with kexec 3.x, and an f2fs one with alarmz. At the first boot only the kexec 3.x would be recognised, I'd boot that, then boot alarmz. Not a very clean solution, but at least I wouldn't have to swap the SD cards eveytime
May 24 12:48:36 <ant_work> did greg compile the kexecboot-kernel without logo and with debug? Do you see messages of kernel booting?
May 24 12:49:00 <ant_work> my 4.x are totally quiet
May 24 12:50:25 <ant_work> both kernel and kexecboot
May 24 12:50:55 <ant_work> (PRINTK and BUG are disabled in kernel, loglevel is 3 and stdout/stderr are on ttyS0)
May 24 12:52:40 <VartiWork> his 2.6 frankenstein is without logo and with debug
May 24 12:53:00 <VartiWork> I have not tried his official 3.x one
May 24 12:53:46 <VartiWork> this is what his 2.6 prints: http://www.oesf.org/pics/IMG-20170524-02278.jpg
May 24 12:54:40 <ant_work> yes, we see it launches init=kexecboot
May 24 12:55:12 <ant_work> (on nextpage you should see ..I'm the init proces....)
May 24 13:57:48 <ant_work> bbl
**** ENDING LOGGING AT Thu May 25 03:00:02 2017