**** BEGIN LOGGING AT Thu Jun 15 03:00:03 2017
Jun 15 07:17:55 <greguu> ant_work : you had any luck with 3.4.y-f2fs ?
Jun 15 07:20:14 <ant_work> yes, it is ok
Jun 15 07:20:22 <ant_work> like 3.10.y
Jun 15 07:20:37 <ant_work> seems equivalent I'd say
Jun 15 07:20:54 <ant_work> imho 3.2 is still a bit faster with SD detection...
Jun 15 07:21:37 <ant_work> I see a progressive slowness moving from 3.2 to 4.x
Jun 15 07:21:52 <ant_work> surely the deferred probing done in kernel does not help
Jun 15 07:22:19 <ant_work> greguu, I must send you the patches
Jun 15 07:22:24 <ant_work> I'll do now
Jun 15 07:22:54 <greguu> will it boot akita?
Jun 15 07:22:58 <ant_work> fwiw I don't know results on akita yet...
Jun 15 07:23:00 <ant_work> heh
Jun 15 07:23:09 <greguu> well that is the main goal
Jun 15 07:23:26 <ant_work> right, then stop with bootloaders :)
Jun 15 07:25:18 <ant_work> for kexecboot just devicetree plus some fix
Jun 15 07:25:23 <ant_work> then is done
Jun 15 07:33:26 <greguu> whatever broke booting akita on 3.2+ , if fixed, will very likely allow booting akit on 3.10.y or even 4.x
Jun 15 07:34:14 <greguu> I hope 3.4.y boots on akita, then the diff to 3.5 can not be that large
Jun 15 07:40:33 <greguu> Varti will be the guinea pig :)
Jun 15 07:52:57 <ant_work> heh, in future on tosa as well
Jun 15 07:55:06 <greguu> did he win the auctions ?
Jun 15 07:57:19 <ant_work> yes, 3 pcs but no wifi no bt
Jun 15 08:11:32 <ant_work> you got mail
Jun 15 08:53:20 <ant_work> VartiWork, hi
Jun 15 08:53:32 <VartiWork> hi ant_work
Jun 15 08:53:41 <ant_work> don't let us in the dark
Jun 15 08:53:55 <VartiWork> I'll try to test 3.4 during the day
Jun 15 08:54:01 <ant_work> I still have fingers crossed ;(
Jun 15 08:54:26 <VartiWork> unfortunately I'm busy during the lunch break, I'll try to do the test before or after the break
Jun 15 08:54:32 <VartiWork> heh I can imagine
Jun 15 08:54:59 <VartiWork> do you remember if you gave me any user port cable with the 5500 and the 860?
Jun 15 08:55:20 <VartiWork> I remember a cable for the 5500, but it was for the cradle
Jun 15 09:02:03 <ant_work> maybe there was an usb one, yes
Jun 15 09:02:09 <ant_work> untested by me
Jun 15 09:02:34 <ant_work> it had theSharp connector at one hand
Jun 15 09:02:51 <ant_work> but afaik is not good for serial
Jun 15 09:04:27 <VartiWork> ok
Jun 15 09:05:09 <ant_work> we have to ping dromede, once he comes near Trieste
Jun 15 09:05:20 <ant_work> he could give it to you
Jun 15 09:05:30 <VartiWork> yep... I'll try to send him an email
Jun 15 09:07:20 <VartiWork> about posting the new kexec on oesf, if you agree I'd create a new subforum dedicated to kexecboot, to give more visibility to the project
Jun 15 09:08:03 <VartiWork> otherwise, "Zaurus - Other distros support" should be the most appropriate, even if technically it isn't a distro
Jun 15 09:19:45 <ant_work> I'd like to remove the older binaries around in the web
Jun 15 09:19:56 <ant_work> with old boot.cfg sytax, etc
Jun 15 09:20:16 <VartiWork> are there any outside LinuxPDA?
Jun 15 09:20:41 <ant_work> yes, not many but there are
Jun 15 09:21:13 <ant_work> if we put the link sticky in the forums is not a prob
Jun 15 09:22:06 <ant_work> in fact LinuxPDA is the sandbox, then I commit to kernel upstream, kexecboot or OpenEmbedded
Jun 15 09:22:41 <ant_work> but I'd prefere to link to official kexecboot site/github
Jun 15 09:23:29 <ant_work> VartiWork, whre to put some test images is another question
Jun 15 09:23:56 <ant_work> i.e. a repository full of packages
Jun 15 09:25:54 <VartiWork> so, you'd put the official kexecs on the official kexec site, and you'd prefer an alternative place to LinuxPDA to store test builds?
Jun 15 09:27:56 <ant_work> yes
Jun 15 09:28:48 <ant_work> nobody complained but I'm uploading too much on github I fear
Jun 15 09:29:07 <VartiWork> we can put all the stuff on oesf if you wish
Jun 15 09:29:53 <ant_work> how is with ALArm feeds?
Jun 15 09:30:37 <VartiWork> we directly use the official arch linux ARM armv5 feeds
Jun 15 09:31:01 <ant_work> ok, like it was for OpenZaurus
Jun 15 09:31:09 <VartiWork> yes, very handy
Jun 15 09:31:41 <ant_work> I can ask ka6sox, maybe we obtain some GB on openembedded.org
Jun 15 09:32:00 <VartiWork> how much space would be needed?
Jun 15 09:32:49 <ant_work> hard to say, a few GB I'd say
Jun 15 09:33:12 <VartiWork> would you need a git account as well? I need to check if ibiblio offers this service as well
Jun 15 09:33:44 <VartiWork> a few GB won't be a problem, I have recently remove 3GBs of so of old backups
Jun 15 09:33:52 <VartiWork> remove+d
Jun 15 09:34:50 <ant_work> the issue is, there should be an autobuilder regularly populating the feeds with updated packages
Jun 15 09:35:12 <ant_work> otherwise we can opt for some 'static' repo
Jun 15 09:35:40 <VartiWork> ah, a sort of nightly builds?
Jun 15 09:35:50 <VartiWork> or built on request?
Jun 15 09:35:55 <ant_work> we need to discuss this all
Jun 15 09:36:10 <ant_work> now is a bit premature...
Jun 15 09:39:01 <VartiWork> ok
Jun 15 09:41:40 <VartiWork> [oesf@login1 ~]$ which git /usr/bin/which: no git in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/export/sunsite/users/oesf/bin)
Jun 15 09:42:18 <VartiWork> and they used to host it :( https://answers.ibiblio.org/questions/1821/git-removed-from-ibiblio.html
Jun 15 09:49:29 <VartiWork> I have searched for kexec's binaries in the forum's attachments, but I have found only a couple of old ones
Jun 15 09:49:38 <VartiWork> http://www.oesf.org/forum/index.php?showtopic=25555&st=30&p=175783&#entry175783
Jun 15 09:49:52 <VartiWork> http://www.oesf.org/forum/index.php?showtopic=25555&st=0&p=174922&#entry174922 (in the middle of the post)
Jun 15 10:43:50 <VartiWork> ant_work: same results with 3.4 as with 3.2 and 3.10, unfortunately
Jun 15 10:44:22 <VartiWork> kexec boots, menu browsing is fast, SD recognition is also fast
Jun 15 10:45:00 <VartiWork> it recognises both boot/ directories under b0p1 (ext3) and b0p2 (f2fs)
Jun 15 10:45:39 <VartiWork> but when trying to boot them, screen remains black, power led blinks once, mail led not blinking at all
Jun 15 10:46:58 <VartiWork> brb
Jun 15 10:58:52 <ant_work> wait, the kernel itself boots then?
Jun 15 11:18:54 <ant_work> you see kexecboot menu with all 3 kernels?
Jun 15 11:19:25 <ant_work> no way, I understood only linux-kexecboot 3.2 was booting
Jun 15 11:51:21 <VartiWork> the kernel itself boots, in all the three kexecboots
Jun 15 11:52:54 <VartiWork> on my akita, all three kernels behave the same
Jun 15 11:54:24 <VartiWork> the only difference between them I have found is that in 3.2 and 3.10 the mail led blinks for a couple of seconds, on 3.4 it never blinks, probably nothing important
Jun 15 11:57:30 <VartiWork> otherwise, I can browse the menus with no problems, do a refresh of the SD card, reboot etc.
Jun 15 12:16:19 <ant_work> if you plug AC does the orange led switch on?
Jun 15 12:16:27 <ant_work> try a couple of times
Jun 15 12:16:51 <ant_work> usually on second try it does recharge
Jun 15 12:19:04 <ant_work> the green leds blinks during mtd parsing on poodle
Jun 15 12:19:10 <ant_work> must check on c7x0
Jun 15 12:19:38 <ant_work> I did not change leds in kernel (yet)
Jun 15 12:19:39 <VartiWork> unplug and plug it when trying to boot the f2fs partition?
Jun 15 12:19:53 <VartiWork> or when the menu is displayed?
Jun 15 12:19:59 <ant_work> at menu
Jun 15 12:20:05 <VartiWork> ok
Jun 15 12:20:07 <ant_work> try to plug it and reboot
Jun 15 12:20:15 <ant_work> it switches off iirc :/
Jun 15 12:20:48 <ant_work> it = led = no recharge
Jun 15 12:21:11 <ant_work> th eidea is to allow recharge from within kexecboot
Jun 15 12:21:27 <ant_work> but I don't remember if I compiled th ebattery drivers...
Jun 15 12:21:30 <ant_work> :)
Jun 15 12:23:01 <VartiWork> same happens here
Jun 15 12:23:36 <VartiWork> if I boot with no charger, on menu I plug it back, the led is switched on for a second, then it is switched off
Jun 15 12:23:42 <ant_work> some register is not set correctly I think
Jun 15 12:23:48 <ant_work> on reboot path
Jun 15 12:23:56 <VartiWork> when I unplug and plug it again, the led remains switched on
Jun 15 12:24:21 <ant_work> ok, it is rather inconsistent on akita as well...
Jun 15 12:24:43 <ant_work> iirc 4.x kernels are ok from this POV
Jun 15 12:25:31 <ant_work> anyway, I am building 4.4 kernels with f2fs: I'll compile some small image to test on SD
Jun 15 12:26:04 <ant_work> are you sure the kernel you are booting supports f2fs?
Jun 15 12:27:04 <VartiWork> yes, it's greguu's latest 4.12 one
Jun 15 12:27:45 <VartiWork> I'm able to boot the same SD card, hence with the same kernel, with greguu's 2.6 frankenstein kexec
Jun 15 12:28:49 <VartiWork> the 2.6 kexec boots 4.12 on ext3, and this same 4.12 loads the root partition on f2fs
Jun 15 12:31:24 <ant_work> and the 3.2 / 3.4 / 3.10 do not boot ext2/3/4?
Jun 15 12:36:49 <VartiWork> no, all three fail to boot the kernel on ext3
Jun 15 12:37:02 <ant_work> that's rare
Jun 15 12:37:13 <VartiWork> it is recognised, but it fails to boot
Jun 15 12:37:28 <VartiWork> imho to me it seems the backlight problem
Jun 15 12:37:36 <ant_work> pls try the same on c860 to appreciate evtl differences
Jun 15 12:37:42 <VartiWork> ok
Jun 15 12:37:57 <VartiWork> I have it here btw, I'll try this afternoon
Jun 15 12:38:30 <ant_work> any kexecboot 3.x or the latest 4.4 (no f2fs yet)
Jun 15 12:38:39 <ant_work> I'll update this later today
Jun 15 12:39:06 <ant_work> it's sllllowww
Jun 15 12:39:20 <VartiWork> btw, could adding console=/dev/mmcblk0p1 in boot.cfg redirect the boot output to a file?
Jun 15 12:39:42 <ant_work> no, must be a tty afaik
Jun 15 12:39:59 <VartiWork> I see
Jun 15 12:40:17 <VartiWork> indeed, either tty, uart or hvc
Jun 15 12:42:27 <ant_work> yep, uart as well
Jun 15 13:10:11 <ant_work> bbl
Jun 15 16:37:03 <ant_home> greguu, I bet Varti has /dev/hda in boot.cfg
Jun 15 16:37:29 <ant_home> that would explain why only 2.6-frankie boots his kernel on SD
Jun 15 16:38:26 <ant_home> it is /dev/sda with 3.x (SCSI)
Jun 15 16:38:32 <ant_home> for Varti ^
Jun 15 18:13:57 <ant_home> Varti, hi, check last lines of the logs :)
Jun 15 20:26:48 <Varti> ant_home: I have set it to /dev/mmcblk0p2 ... I have tried it with /dev/sda2 first but it didn't work, since sda2 apparently still wasn't mounted at the moment when boot.cfg was read
Jun 15 21:12:46 <ant_home> ah, sorry..that is the CF card
Jun 15 21:19:02 <ant_home> I am finished to boot-test the uilds on LinuxPDA
**** ENDING LOGGING AT Fri Jun 16 03:00:03 2017