**** BEGIN LOGGING AT Thu Aug 18 02:59:56 2011
Aug 18 09:27:26 <ant_work> he, some downloads but no reports yet about latest linux-kexecboot
Aug 18 09:28:14 <ant_work> next time we'll let download from the kexecboot site
Aug 18 09:28:28 <ant_work> once we are sure all images are ok ;)
Aug 18 09:29:15 <ant_work> bluelightning: could you by chance retry to reflash your collie?
Aug 18 11:43:51 <lumag_gone> hi all
Aug 18 11:48:44 <ant_work> hi lumag
Aug 18 12:26:35 <ant_work> lumag: compiled any bootable image ?
Aug 18 12:28:05 <lumag> still didn't have time to test again
Aug 18 12:28:36 <ant_work> I have built core-image-sato with x86lite
Aug 18 12:28:45 <ant_work> will test later
Aug 18 12:29:01 <ant_work> kdrive lacks kb an ts
Aug 18 12:29:26 <ant_work> all like in oe-dev ;)
Aug 18 13:06:02 <bluelightning> ant_work: I can try this evening
Aug 18 15:45:35 <ant_work> bbl
Aug 18 21:05:39 <ant__> Jay7: we have now the device_table-minimal.txt issue: the on ein oe-core has no input devices
Aug 18 21:05:56 <Jay7> ant__: hi
Aug 18 21:06:13 <Jay7> ant__: we need event devices..
Aug 18 21:06:21 <ant__> really time for devtmpfs patch
Aug 18 21:06:33 <Jay7> ah
Aug 18 21:06:45 <Jay7> well.. I promise to do it in this weekend :)
Aug 18 21:06:58 <Jay7> bother me please :)
Aug 18 21:06:59 <ant__> it seems oe-core has no interest changing the files
Aug 18 21:07:19 <ant__> I'll be away from 21st to 31st
Aug 18 21:07:20 <Jay7> they should be conservative to be stable
Aug 18 21:07:43 <ant__> yes, still...nobody is using it, they have udev
Aug 18 21:07:44 <Jay7> ant__: vacation or business trip?
Aug 18 21:07:51 <ant__> this time vacation :)
Aug 18 21:08:05 <Jay7> lucky you :)
Aug 18 21:08:13 <ant__> not long as desired because a business visit on 1st september :/
Aug 18 21:09:23 <Jay7> sh#t.. summer is almost over
Aug 18 21:10:02 * Jay7 is setting up proxy traffic accounting..
Aug 18 21:10:44 <Jay7> I don't know why customers want this even on unlim tariffs..
Aug 18 21:20:28 <ant__> wow, 5 downloads for tosa on ltg...and I'm pretty sure it's broken :/
Aug 18 21:21:39 <ant__> only one other for poodle :/ almost extinct :)
Aug 18 22:20:26 <lumag> hi
Aug 18 22:22:35 <lumag> Jay7, ant__ I was able to boot old kexecboot on tosa. Unfortunately the only one that worked correctly was one from 2.6.2x era :(
Aug 18 22:23:15 <Jay7> lumag: hehe
Aug 18 22:23:44 <lumag> I was able to boot my old opie installation, but it cannot boot current kernels (hda vs sda).
Aug 18 22:23:55 <Jay7> hard to find who is broken - kexecboot or kernel
Aug 18 22:24:41 <lumag> I'll try creating recent kernel with ide enabled (to be able to boot there).
Aug 18 22:25:10 <lumag> Or I'll try using working kexecboot to load contemporary kexecboot.
Aug 18 22:39:25 <ant__> yes, pls try it standalone
Aug 18 22:40:02 <ant__> but I'm pretty sure tosa could boot 2.6.31 or 32
Aug 18 22:41:12 <ant__> lumag: pls check you have /dev/input in the initramfs
Aug 18 22:41:51 <lumag> ant__, I've tried v2.6.3x kexecboot images from linuxtogo
Aug 18 22:42:04 <lumag> and failed
Aug 18 22:42:08 <ant__> ok, there I removed oe-core's device_table-minimal.txt
Aug 18 22:43:09 <ant__> maybe there is some defconfig mismatch...
Aug 18 22:44:51 <lumag> ant__, don't think so.
Aug 18 22:45:58 <lumag> succeeded in chainloading new kexecboot
Aug 18 22:46:03 <ant__> iirc tosa had only 2 patches for 2.6.30 or .32
Aug 18 22:46:13 <ant__> can't remember exactly
Aug 18 22:46:40 <lumag> Probably I should check the last kernel that still had tosakbd.c
Aug 18 22:47:42 <ant__> yes, with new gpio matrix drivers some breakage happened (as for corgi)
Aug 18 22:48:15 <lumag> Sometimes some keys can break in.
Aug 18 22:48:35 <lumag> I once was able to get into system menu. And now somehow stepdown worked
Aug 18 22:49:54 <ant__> so you can kexec the 2.6.3x linux-kexecboot?
Aug 18 22:50:17 <ant__> but it doesn't boot from cold?
Aug 18 22:51:31 <lumag> No, it boots, but keys don't work.
Aug 18 22:51:59 <ant__> I see
Aug 18 22:52:32 <ant__> the keyb_tweak_r2 patch seems have solved on poodle
Aug 18 22:52:34 <lumag> Basically I'll be now able to check my super-debug version kexecboot (or even kexecboot + sh :)) without doing too many rewrites on nand
Aug 18 22:52:37 <ant__> and I hope on collie
Aug 18 22:57:37 <lumag> Hmmm.
Aug 18 22:58:57 <lumag> I'm getting very strange readings from event devies
Aug 18 22:59:36 <lumag> I'll post a log
Aug 18 23:03:46 <lumag> ant__, http://paste.debian.net/126678/
Aug 18 23:04:11 <lumag> That's the log of boot of kexecboot + 1 keypress (down).
Aug 18 23:06:26 <ant__> hm.. it looks like the logs I had: one keypress has more codes
Aug 18 23:07:32 <ant__> wait
Aug 18 23:07:36 <ant__> We have no tty
Aug 18 23:07:36 <ant__> FB angle is 0, tty is (null)
Aug 18 23:08:16 <lumag> so?
Aug 18 23:08:32 <lumag> I see menu on the screen.
Aug 18 23:09:45 <lumag> And it looks like codes for the arrows are rotated (down is left, etc.)
Aug 18 23:10:24 <ant__> hm..
Aug 18 23:10:28 <ant__> console=tty1 console=ttyS0,115200n8 debug
Aug 18 23:10:49 <ant__> -> console [tty1] enabled
Aug 18 23:10:59 <ant__> ^^ I'd expect this
Aug 18 23:11:18 <lumag> Also it seems lcd/backlight interaction is a bit broken.
Aug 18 23:11:32 <lumag> Maybe I'll have to rewrite that driver again.
Aug 18 23:11:36 <ant__> this is specific tosa driver iirc
Aug 18 23:12:13 <lumag> yes.
Aug 18 23:12:34 <lumag> Record key is working BTW :)
Aug 18 23:12:42 <lumag> Read event type 1, code 124 (0x7c) value 1
Aug 18 23:12:42 <lumag> Read event type 0, code 0 (0x0) value 0
Aug 18 23:12:42 <lumag> Read event type 1, code 124 (0x7c) value 0
Aug 18 23:12:42 <lumag> Read event type 0, code 0 (0x0) value 0
Aug 18 23:12:52 <lumag> So it's really a matrixkbd problem.
Aug 18 23:13:45 <Jay7> lumag: I hope you will fix it quickly ;)
Aug 18 23:13:55 <lumag> And power is more or less working:
Aug 18 23:13:58 <ant__> Found device '/dev/mtdblock0' (31, 0) of size 110485Mb
Aug 18 23:14:01 <ant__> ?
Aug 18 23:14:25 <lumag> Read event type 16, code 205 (0xcd) value 1
Aug 18 23:14:26 <lumag> Read event type 0, code 0 (0x0) value 0
Aug 18 23:14:26 <lumag> Read event type 16, code 0 (0x0) value 1
Aug 18 23:14:26 <lumag> Read event type 0, code 0 (0x0) value 0
Aug 18 23:14:26 <lumag> Read event type 16, code 0 (0x0) value 0
Aug 18 23:14:26 <lumag> Read event type 0, code 0 (0x0) value 0
Aug 18 23:14:28 <lumag> Read event type 16, code 205 (0xcd) value 0
Aug 18 23:14:30 <lumag> Read event type 0, code 0 (0x0) value 0
Aug 18 23:14:46 <lumag> It seems it cannot get mtd sizes correctly. Does it for you?
Aug 18 23:15:16 <ant__> I don't have tosa
Aug 18 23:15:27 <ant__> Jay7: did you test it? iirc was ok
Aug 18 23:15:54 <lumag> ant__, tosa shouldn't matter here.
Aug 18 23:16:15 <Jay7> ant__: can't remember
Aug 18 23:16:15 <ant__> well, I see different nand chips
Aug 18 23:16:42 <ant__> I'm pretty sure you did ;)
Aug 18 23:17:11 <ant__> poodle has  NAND device: Manufacturer ID: 0xec, Chip ID: 0x79 (Samsung NAND 128MiB 3,3V 8-bit)
Aug 18 23:17:43 <ant__> ah, no, it's husky
Aug 18 23:17:46 <ant__> C860
Aug 18 23:18:45 <lumag> Aniway it's strange: I got 110485 for PROM, smf and root partitions. Home returned 0
Aug 18 23:19:13 <Jay7> lumag: please look at code which prints that messages
Aug 18 23:19:19 <ant__> mtdparts=sharpsl-nand:7168k(smf),28672k(root),-(home)
Aug 18 23:19:27 <Jay7> it may be wrong in your version
Aug 18 23:19:27 <ant__> ^^ this comes from kexecboot?
Aug 18 23:20:07 <ant__> the mtd routine is unchanged btw the 2 kernels on ltg
Aug 18 23:20:31 <ant__> both 2.6.2x and 2.6.39.3 force the mtdparts
Aug 18 23:20:37 <lumag> yes, that comes from previous kexecboot. I don't remember kernel params passed by original bootloader.
Aug 18 23:21:09 <ant__> then is kernel/mtd driver issue :/
Aug 18 23:21:14 <Jay7> compare with /proc/partitions blocks field
Aug 18 23:21:58 <Jay7> kexecboot is reading them from there (and then applies values from zaurus paraminfo area)
Aug 18 23:22:29 <lumag> Let me boot into opie
Aug 18 23:22:29 <ant__> Creating 3 MTD partitions on "tmio-nand":
Aug 18 23:22:30 <ant__> 0x000000000000-0x000000700000 : "smf"
Aug 18 23:22:39 <ant__> ^^ this comes from kexecboot
Aug 18 23:23:01 <ant__> "smf" "root" "home" names
Aug 18 23:23:03 <lumag> from 2.4 bootloader: COMMANDLINE= console=ttyS0 root=/dev/mtdblock2 mtdparts=sharpsl-nand:7168k@0k(smf),28672k@7168k(root),-(home)
Aug 18 23:23:57 <lumag> Also tosa.c still contains valid partition table:
Aug 18 23:24:08 <lumag> smf, offset=0, size = 7*1024*1024, etc.
Aug 18 23:25:35 <lumag> I don't remember if kexecboot kernel contain cmdline parser
Aug 18 23:25:45 <ant__> yes
Aug 18 23:26:29 <lumag> Damn. I also should finally find the cause for misterious AC97 problems on tosa bootup.
Aug 18 23:29:00 <ant__> 0x000000700000-0x000002300000 : "root"
Aug 18 23:29:06 <ant__> ^^ this is correct
Aug 18 23:30:38 <lumag> On 2.6.29.6 /proc/partitions contains valid sizes for mtdblock devices
Aug 18 23:34:35 <lumag> Damn. And serial console isn't working properly with this unit and/or cable
Aug 18 23:37:01 <ant__> see this log  http://pastebin.com/xPzM00eM
Aug 18 23:39:12 <Jay7> lumag: can't login on serial?
Aug 18 23:39:26 <lumag> yep.
Aug 18 23:39:31 <Jay7> I've faced this one time..
Aug 18 23:39:40 <lumag> That's the unit I got from you.
Aug 18 23:40:00 <Jay7> I know, but I'm sure this is not unit/cable problem
Aug 18 23:40:17 <lumag> It also might be the cable, as I did experiments with it before.
Aug 18 23:40:35 <lumag> And might have disconnected RX line.
Aug 18 23:40:36 <Jay7> I can't login to akita via serial when tried last time (about half-year ago)
Aug 18 23:40:59 <Jay7> but I remember that I can login to akita before
Aug 18 23:41:13 <lumag> I see login prompt but keys simply don't work.
Aug 18 23:41:23 <Jay7> so I suspect kernel
Aug 18 23:41:41 <lumag> I'll check that later.
Aug 18 23:42:01 <Jay7> I should check with latest kernels
Aug 18 23:42:08 <lumag> Do we have some issue tracker for kernel/kexecboot zaurus problems?
Aug 18 23:42:20 <Jay7> ant__: iirc, you still may login to your units?
Aug 18 23:42:39 <Jay7> lumag: we have tracker on ltg
Aug 18 23:42:51 <Jay7> but it's not used :)
Aug 18 23:42:58 <lumag> kexecboot or zaurus project?
Aug 18 23:43:27 <Jay7> kexecboot
Aug 18 23:43:33 <ant__> yes, even core-image-sato stalls in gui but allows login from serial
Aug 18 23:43:40 <Jay7> zaurus project have it as well
Aug 18 23:43:52 <ant__> last I tried is poodle but did lot of logs on c7x0
Aug 18 23:43:54 <Jay7> but unused too :)
Aug 18 23:43:58 <ant__> and spitz
Aug 18 23:44:24 <lumag> poodle has wrong wiring of some serial contacts (there was a patch somewhere on rpsys.net)
Aug 18 23:44:25 <ant__> anyway, I always declare 2 consoles in cmdline
Aug 18 23:44:27 <Jay7> ant__: have you standard sharp cable?
Aug 18 23:44:29 <ant__> fwiw
Aug 18 23:44:39 <ant__> yes, original
Aug 18 23:44:42 <Jay7> CE-170TS?
Aug 18 23:44:57 <ant__> yes
Aug 18 23:45:34 <ant__> here it looks lumag is missing tty1
Aug 18 23:45:38 <Jay7> I have this cable and usb2com on pl2303
Aug 18 23:46:21 <ant__> I have *real* serial
Aug 18 23:46:23 <Jay7> ant__: what chip have your usb2com? or did you using real hw com port?
Aug 18 23:46:33 <Jay7> lucky you again :)
Aug 18 23:46:40 <ant__> old good Intel
Aug 18 23:46:51 <Jay7> lumag: are you using usb2com? or real hw port?
Aug 18 23:46:59 <lumag> real hw
Aug 18 23:47:03 <Jay7> hmhm
Aug 18 23:47:04 <Jay7> well
Aug 18 23:47:05 <lumag> fujitsu laptops :)
Aug 18 23:47:19 <Jay7> ah, btw
Aug 18 23:47:22 <lumag> I really suspect cable. Lemme check with another one.
Aug 18 23:47:29 <Jay7> I have serial on thinkpads docstation
Aug 18 23:48:42 <Jay7> well.. too late here
Aug 18 23:48:45 * Jay7 -> sleep
Aug 18 23:49:05 <lumag> Yes cable problem.
Aug 18 23:49:09 <lumag> Second cable worked
Aug 18 23:49:10 <ant__> :)
Aug 18 23:49:30 <ant__> resolder it ;)
Aug 18 23:49:38 <Jay7> hmm..
Aug 18 23:49:46 <Jay7> then I should check my cable next time
Aug 18 23:50:38 <lumag> ant__, I wanted to create a 'minidock' cable which would support both serial and udc interfaces. Seems I disconnected RX somehow.
Aug 18 23:50:59 * lumag is going to sleep also.
Aug 18 23:51:15 <ant__> yes, late now
Aug 18 23:51:20 <ant__> good night
Aug 18 23:51:27 <lumag> night
**** ENDING LOGGING AT Fri Aug 19 02:59:57 2011