**** BEGIN LOGGING AT Wed Apr 20 02:59:58 2016
Apr 20 12:00:48 <VartiWork> hi ant_work
Apr 20 12:01:05 <VartiWork> congrats for the fixed audio... what was the problem causing it to not work?
Apr 20 12:01:18 <VartiWork> btw
Apr 20 12:01:20 <VartiWork> I'm right now testing the new kernel. I have extracted both updater.sh and zImage from installkit-akita.tar.gz to my 1GB SD card, the flashing itself has been successful, but the kernel itself doesn't boot
Apr 20 12:01:23 <ant_work> apparently a misnamed module binding
Apr 20 12:01:36 <VartiWork> aha
Apr 20 12:01:41 <VartiWork> with the charger plugged in, what I see during the boot is that the screen gets initialized (it becomes white for a millisecond), the charging led is switched off, it is switched on again for a second then switched off, nothing else happens (waited 5 minutes to see if it boots)
Apr 20 12:01:46 <VartiWork> without the charger, same but the charging led is never switched on
Apr 20 12:01:51 <VartiWork> just wondering, what are the zImage--4.4-r0-akita-20160417223355.bin and modules for? Are they intended for the boot of any Linux distro?
Apr 20 12:02:19 <VartiWork> (I'm doing a copy and paste btw, just in case you were wondering how can I type this fast :)
Apr 20 12:02:21 <ant_work> I plan to upload a basic image
Apr 20 12:03:18 <ant_work> can you please do this try: put the kexecboot zImage on the SD/CF card and edit boot.cfg to point to it?
Apr 20 12:03:52 <ant_work> ofc you have to reflash a working linux-kexecboot first
Apr 20 12:04:57 <ant_work> I fear there might be some pxa27x/akita specific breakage
Apr 20 12:05:20 <ant_work> because the gpio expander on it has been heavily touched in the last releases
Apr 20 12:05:22 <VartiWork> ok
Apr 20 12:05:24 <VartiWork> does the root partition size on the NAND matter? (I guess not, I'm asking just in case) Mine is 32MB, the default size for Cacko... does anything get written/decompressed on it, during each boot?
Apr 20 12:06:07 <ant_work> no, if it is not correct kexecboot would just not find any bootable image on it
Apr 20 12:06:52 <VartiWork> hmm, isn't kexecboot itself installed there?
Apr 20 12:07:52 <VartiWork> or is kexecboot installed in a different partition, and during boot it searches there for bootable images (as well as on an SD)?
Apr 20 12:08:05 <ant_work> yes, it is in the first small mtd partitiob
Apr 20 12:08:07 <ant_work> *n
Apr 20 12:08:32 <ant_work> mtd0 = boot PROM (ignore it)
Apr 20 12:08:36 <ant_work> mtd1 = kernel
Apr 20 12:08:42 <ant_work> mtd2 = root
Apr 20 12:08:55 <ant_work> mtd3 = second root or alternatively /home
Apr 20 12:09:45 <ant_work> the zaurus 1st stage bootloader is on (P)ROM and just launches zImage from mtd1
Apr 20 12:09:53 <VartiWork> you mean it is installed on mtd0? or mtd1?
Apr 20 12:09:57 <ant_work> mtd1
Apr 20 12:10:11 <ant_work> kexecboot is a '2nd stage' bootloader
Apr 20 12:10:12 <VartiWork> ok, thanks for the explanation
Apr 20 12:10:30 <ant_work> actually is the third but we can ignore the pxa hw specifics :)
Apr 20 12:10:39 <VartiWork> hehe
Apr 20 12:10:56 <ant_work> the 1st stage bootloader is called Angel
Apr 20 12:11:10 <ant_work> it was popular back then before u-boot
Apr 20 12:11:19 <VartiWork> wonder why it is called that way...
Apr 20 12:11:42 <ant_work> should be some short for Arm ...
Apr 20 12:11:44 <VartiWork> nice though to think that I have an angel inside my Z :P
Apr 20 12:19:14 <ant_work> VartiWork, http://elinux.org/Flameman/zaurus-akita
Apr 20 12:19:25 <ant_work> we lost the guy in the years...
Apr 20 12:22:02 <ant_work> VartiWork, if you have time pls try to boot that 4.4 kernel as well, even standalone, w/out rootfs
Apr 20 12:22:18 <VartiWork> amazing stuff, he really worked a lot on it
Apr 20 12:22:37 <VartiWork> so Gentoo was also ported on the Z, interesting
Apr 20 12:22:46 <ant_work> yes, long ago
Apr 20 12:23:00 <ant_work> but the guys did prefer to compile on Z :/
Apr 20 12:23:39 <VartiWork> I can imagine the compilation time...
Apr 20 12:23:42 <ant_work> heh
Apr 20 12:23:57 <VartiWork> at least I believe distcc was available too
Apr 20 12:24:29 <ant_work> cross-compile was already possible, even if imperfect back then
Apr 20 12:25:58 <VartiWork> [14:03] <ant_work> can you please do this try: put the kexecboot zImage on the SD/CF card and edit boot.cfg to point to it?
Apr 20 12:26:25 <VartiWork> I don't have here a copy of boot.cfg, hmm
Apr 20 12:27:24 <ant_work> you can find some in the images I uploaded, under /boot
Apr 20 12:27:33 <ant_work> or else write couple of lines  https://github.com/kexecboot/kexecboot/wiki/how_to_write_config
Apr 20 12:27:58 <ant_work> you can keep several kernels in the same partition if you want
Apr 20 12:28:05 <ant_work> just add more LABEL=
Apr 20 12:28:26 <ant_work> for testing we just need LABEL= and KERNEL=
Apr 20 13:02:20 <VartiWork> just tried booting the new kexecboot using kexecboot 2.6
Apr 20 13:02:59 <VartiWork> same behaviour as before, only that this time, after ca. 1 minute, it returns back to the 2.6 kexec
Apr 20 13:04:30 <VartiWork> either that, or it correctly boots kexec 4.4.7 but without showing any boot text, and both kexec 2.6 and 4.4.7 are graphically identical, so I can't tell which one has booted
Apr 20 13:07:47 <VartiWork> 14:22] <ant_work> VartiWork, if you have time pls try to boot that 4.4 kernel as well, even standalone, w/out rootfs
Apr 20 13:07:51 <VartiWork> trying this now
Apr 20 13:08:53 <ant_work> it should take some seconds, but if you have images on mtd it can take 20-30 secs
Apr 20 13:09:05 <ant_work> but no longer
Apr 20 13:09:16 <ant_work> jffs2 is especially slow
Apr 20 13:10:49 <ant_work> no output on screen is expected
Apr 20 13:10:53 <VartiWork> no images on mtd
Apr 20 13:11:16 <VartiWork> ah, unlike kexec 2.x then? it shows the boot procedure
Apr 20 13:11:22 <ant_work> the normal kernel is more verbose and you should see it panic
Apr 20 13:11:30 <VartiWork> ok
Apr 20 13:12:25 <ant_work> in my builds I redirect kernel msgs to serial so screen is not disturbed
Apr 20 13:12:43 <VartiWork> I guess then kexec 4.4 booted correctly if started from kexec 2.6
Apr 20 13:13:38 <VartiWork> ok, the normal kernel has panicked
Apr 20 13:13:47 <VartiWork> just a sec that I paste the error
Apr 20 13:13:55 <ant_work> it lacks rootfs, is normal
Apr 20 13:14:13 <VartiWork> aha indeed
Apr 20 13:14:20 <ant_work> is the screen ok§?
Apr 20 13:14:23 <VartiWork> yes
Apr 20 13:14:26 <ant_work> good
Apr 20 13:14:30 <VartiWork> openembedded screen shown
Apr 20 13:14:47 <VartiWork> pxa-rtc: failed to find rtc clock source
Apr 20 13:14:49 <ant_work> I mean during boot, before panicking
Apr 20 13:15:16 <ant_work> ah ha, interesting..I changed from rtc_sa1100 to rtc_pxa
Apr 20 13:15:18 <VartiWork> FAT-fs (mmcblk0p1): codepage cp437 not found
Apr 20 13:15:38 <ant_work> that's your old linux-kexecboot :/
Apr 20 13:15:39 <VartiWork> then the kernel panic for not finding the rootfs
Apr 20 13:15:48 <VartiWork> hmm
Apr 20 13:16:00 <ant_work> I had forgotten the codepage for fat, it was fixed long ago
Apr 20 13:16:25 <VartiWork> let me check again
Apr 20 13:16:59 <ant_work> http://cgit.openembedded.org/meta-handheld/commit/recipes-kernel/linux?id=8b31b9f06dd6796dfbd2fd666f94ff66418490a5
Apr 20 13:17:11 <ant_work> it was 3.10 back then
Apr 20 13:17:39 <ant_work> do you happen to have serial cable?
Apr 20 13:21:27 <VartiWork> unfortunately not
Apr 20 13:21:43 <VartiWork> I don't understand what I'm doing wrong...
Apr 20 13:22:25 <VartiWork> the file on the SD is the correct zImage--4.4-r0-akita-20160417223355.bin file, renamed as zImage
Apr 20 13:22:36 <VartiWork> (just did a diff to make sure)
Apr 20 13:23:30 <VartiWork> the item in the boot menu I choose is the correct one, the SD card (tried to take off the SD and do a refresh to check)
Apr 20 13:24:11 <VartiWork> both boot.cfg and zImage are on the SD card, under boot/
Apr 20 13:24:26 <VartiWork> the boot.cfg file seems to be correct, too
Apr 20 13:24:26 <ant_work> ok, what's the doubt?
Apr 20 13:25:28 <VartiWork> I was wondering if I am doing something wrong that the old kexecboot is loading...
Apr 20 13:28:06 <ant_work> once you start a kernel from it the screen should flicker for a moment then the OE bootlogo should appear
Apr 20 13:28:46 <VartiWork> yes, that's what happens
Apr 20 13:29:08 <ant_work> if th ekernel is a linux-kexecboot (<1,2 MB) you should see the menu again, no logs or else
Apr 20 13:29:36 <VartiWork> aha ok
Apr 20 13:29:36 <ant_work> if it is the 'production' kernel then some messages should be displayed on screen
Apr 20 13:30:07 <VartiWork> I misunderstood you then, sorry about that
Apr 20 13:30:16 <ant_work>  FAT-fs (mmcblk0p1): codepage cp437 not found
Apr 20 13:30:31 <ant_work> ^ that is in kexecboot debug-menu I bet
Apr 20 13:30:59 <VartiWork> aha
Apr 20 13:31:21 <ant_work> pxa-rtc: failed to find rtc clock source
Apr 20 13:31:36 <ant_work> ^ this should be the 4.4 normal kernel
Apr 20 13:32:46 <ant_work> finally, the bad news are that once flashed the linux-kexecboot_4.4 doesn't start :/
Apr 20 13:33:23 <ant_work> I'll check again the kernel config
Apr 20 13:33:33 <ant_work> for akita/spitz
Apr 20 13:34:45 <ant_work> me or dal need to test on a spitz to verify if the culprit is the CONFIG_GPIO_PCA953X=y
Apr 20 13:34:50 <ant_work> only present on akita
Apr 20 13:35:15 <ant_work> gpio's have been under heavy rework
Apr 20 13:37:15 <VartiWork> ok
Apr 20 13:37:45 <VartiWork> as a last test, I have tried again to flash kexec 4.4 and leave it booting
Apr 20 13:38:33 <VartiWork> could there be some timeout that once expired it allows the boot to continue?
Apr 20 13:38:59 <ant_work> the only delay is scanning (mounting RO) the mtd partitions
Apr 20 13:39:26 <VartiWork> ok, no point in testing it more then
Apr 20 13:39:41 <ant_work> are you sure mtd parts are empty?
Apr 20 13:40:41 <ant_work> ah, no matter, well, old kexecboot would have the same issues
Apr 20 13:41:01 <ant_work> thanks for your time, I'll verify once again
Apr 20 13:43:05 <VartiWork> the mtd parts are not empty, they contain a Cacko installation
Apr 20 13:43:45 <VartiWork> which I'm not using since I'm planning to use Cacko from SD
Apr 20 13:44:40 <ant_work> ok, I see
Apr 20 13:44:47 <VartiWork> if you want I can try to erase them and try to flash kexec 4.4 again
Apr 20 13:45:05 <VartiWork> I believe there's some option for that in the service menu
Apr 20 13:45:10 <ant_work> iirc jffs2 and ubifs changed ABI btw 2.6 and 3.x so maybe it's that
Apr 20 13:45:22 <ant_work> no, pls do that only from userspace
Apr 20 13:45:22 <VartiWork> ok
Apr 20 13:46:32 <ant_work> https://github.com/LinuxPDA/meta-handheld/blob/master/README.zaurus
Apr 20 13:46:56 <ant_work> I'll upload new images today/tomorrow
Apr 20 13:47:06 <ant_work> with sound fixed ...
Apr 20 13:47:50 <VartiWork> ok
Apr 20 13:47:53 <VartiWork> thanks
Apr 20 14:11:37 <ant_work> bbl
Apr 20 21:04:52 <ant_home> Varthall: see this memo  http://www.h5.dion.ne.jp/~rimemoon/zaurus/memo_006.htm
**** ENDING LOGGING AT Thu Apr 21 02:59:58 2016