**** BEGIN LOGGING AT Mon Feb 18 02:59:57 2008 Feb 18 06:33:46 hi all Feb 18 06:34:31 i m trying to connect to gprs from my neo 1973...i followed the instructions in Wiki n used "pppd debug nodetach call gprs" ... Feb 18 06:34:45 but, its showing error "connection script failed" Feb 18 06:43:52 jus changed the APN details n tried the script given in wiki..anybody using GPRS?? Feb 18 08:21:35 guys.. any of you know how to flash u-boot into gta02? Feb 18 08:22:00 i am not getting the u-boot menu when i press the AUX+power key Feb 18 08:22:07 gta02? Feb 18 08:22:17 yes gta02 Feb 18 08:22:41 vijayvb: who are you lucky person to hold a gta02 Feb 18 08:22:56 vijayvb: you need debug board for gta02 Feb 18 08:23:17 we cant flash it without debig board? Feb 18 08:23:31 ummm... gta02 is out? Feb 18 08:23:41 vijayvb: does it recognise as a ttyACM0 when you plug it in? Feb 18 08:23:43 not yet.. this is a engg version Feb 18 08:23:49 it does Feb 18 08:23:57 vijayvb: then you can connect to that device Feb 18 08:24:06 vijayvb: and use u-boot same as gta01 Feb 18 08:24:10 when i do a "cu" it stays connected fro a while and gets disconnected Feb 18 08:24:33 gta02 should have been shipped with functional u-boot Feb 18 08:24:46 vijayvb: try pressing enter a few times, you need to stop the countdown Feb 18 08:24:56 vijayvb: then you can use dfu-util to flash Feb 18 08:25:13 and you don't have a jtag board and your using an eng. run? Feb 18 08:25:16 ;-) Feb 18 08:25:32 * XorA bets its a later gta02 than his :-) Feb 18 08:30:24 basically - there is no response to the AUX+Power key Feb 18 08:33:03 vijayvb: how old is your gta02, only recent u-boots gained glamo support Feb 18 08:33:12 vijayvb: so dont expect graphics Feb 18 08:34:39 i got it a couple of weeks ago Feb 18 08:35:12 the kernel version is 2.6.22.5-moko.. Feb 18 08:37:10 i was googled for the gta02 and u-boot and got to know tht there is a tool neocon Feb 18 08:37:16 i tried that out also.. Feb 18 08:37:43 the text says that we will receive a prompt from the phone.. but i dont receive it Feb 18 08:38:33 are you connecting via a usb hub? Feb 18 08:39:50 vijayvb: it is possible your u-boot is set to serial port, in that case you will need to connect debug board Feb 18 08:40:17 yes via usb hub Feb 18 08:40:31 might be your issue, plug directly into your usb port Feb 18 08:40:36 Hi Feb 18 08:40:54 Is anybody help me Feb 18 08:41:02 ok.. ill try that out Feb 18 08:41:14 i've had issues using a hub for flashing Feb 18 08:41:59 the neocon says "connected" Feb 18 08:42:11 hit enter Feb 18 08:42:15 so i would infer that it is not a usb hub issue right Feb 18 08:57:25 Hi Feb 18 09:02:42 Hi Feb 18 09:03:04 who can help me, thanks Feb 18 09:36:33 gb time Feb 18 09:36:45 oops wrong channel Feb 18 09:42:08 openmoko: 03tick * r4083 10/developers/tick/scripts/ (. chout): put a grep script Feb 18 09:42:15 openmoko: 03erin_yueh * r4084 10/trunk/src/target/gsm/ (include/gsmd/gsmd.h src/gsmd/usock.c src/util/shell.c): gsmd: bug fixed for some changes (Sudharshan S, Paulius Zaleckas) Feb 18 09:54:28 morning Feb 18 09:59:52 greetings TRIsoft Feb 18 10:12:51 Bonjour Feb 18 10:56:28 good morning Feb 18 11:35:00 * * OM Bug 1234 has been created by dodji(AT)openedhand.com Feb 18 11:35:01 * * investigate using DMA for pixmap migration Feb 18 11:35:02 * * http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1234 Feb 18 12:05:18 openmoko: 03thomas * r4085 10/trunk/src/target/opkg/libopkg/ (6 files): opkg: add autoremove command line option Feb 18 12:25:57 greetings all Feb 18 12:27:15 guys, I have build populated on SD and a few boots went fine but now it hangs, I'd like to ask how to check any start up logs to see what's wrong? Feb 18 12:53:01 * * OM Bug 1235 has been created by mdt(AT)emdete.de Feb 18 12:53:02 * * aux button and charger/usb insertion emit same keycode Feb 18 12:53:03 * * http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1235 Feb 18 14:26:42 hi all...have had a few issues getting MokoMakefile happening on fedora Feb 18 14:27:04 has anyone created a openmoko development VM? Feb 18 14:27:14 that would be sexy... Feb 18 14:40:41 Hullo, somebody know what happened to svn.openmoko.org? I can't fetch 2.6.24 kernel? Feb 18 14:41:10 openmoko: 03thomas * r4086 10/trunk/src/target/opkg/libopkg/opkg_state.c: opkg: use strdup() to prevent memory corruption Feb 18 15:41:55 XorA: Can you bump up the sane-srcrev for the openmoko kernel (linux-openmoko) to 4082? SD card changes seem to work; gave it a good test with bonnie++ yesterday. Feb 18 15:42:57 mwester: speed? Feb 18 15:43:35 Slow, but not a fair comparison as every MMC transaction is logged to the console. Feb 18 15:43:37 mwester: done Feb 18 15:44:00 mwester: ah - yes, that's a big slowdown Feb 18 15:44:03 But at least it now works! Feb 18 15:50:18 ahoi+ Feb 18 15:50:29 ahoi++ **** BEGIN LOGGING AT Mon Feb 18 18:44:15 2008 **** ENDING LOGGING AT Mon Feb 18 18:47:08 2008 **** BEGIN LOGGING AT Mon Feb 18 19:56:14 2008 Feb 18 20:04:19 hello all Feb 18 20:05:27 guy, did anybody use navit? Feb 18 20:05:47 I run it with gllin and gpsd but it doesn't see my current location Feb 18 20:06:14 any ideas why it doesn't work? Feb 18 20:06:47 zdane1, nope but some folks report good results with www.tangogps.org .... Feb 18 20:08:03 zdane1, but maybe you are inside!! Feb 18 20:08:06 I did all according to wiki Feb 18 20:08:26 nope, I use AGPS test program to check if I have fix Feb 18 20:08:28 I do Feb 18 20:10:43 jamewill: thx for the link. looking at screenshots, this tangogps looks very nice Feb 18 20:11:06 I didn't know this app Feb 18 20:17:36 zdane1, check the vid at the bottom of the page Feb 18 20:18:30 I run tangogps now and it works awesome Feb 18 20:18:38 :-) Feb 18 20:19:03 but still this navit case bothers me :) Feb 18 21:27:31 XorA|gone: 'tis late, but there's yet another change for that SD card patch; turns out the last svn patch was applied to the wrong portion of the source code. Feb 18 21:28:03 Which results in writes being broken but also exposes a similar problem in the read logic, which is not half-way fixed by virtue of the misplaced write fix... Feb 18 21:29:00 At present the unstable linux kernel will corrupt SD cards; I'm going to update sane-srcrevs to revert back to 3801 for the moment, as it seems to be a bad problem. Feb 18 21:34:18 er, make that reverting to 4079 -- no need to be quite so drastic. Feb 18 22:01:05 mwester: there is a reason why its .dev branch :-) Feb 18 22:04:50 XorA|gone: Yes :) but I feel bad for declaring it "good" when it can do such damage to the data on the SD card... Feb 18 22:06:21 mwester: heh heh, teaches people about backups Feb 18 22:12:43 mwester, is rev4081 save to use? Feb 18 22:31:10 josch: only if you don't have an SD card plugged in. Feb 18 22:32:03 mwester, I have my rootfs on an sdcard Feb 18 22:32:28 oops, then definitely don't use the 2.6.24 kernel yet. Feb 18 22:32:56 mwester, ah thanks - you stopped me right before flashing ^^ Feb 18 22:33:15 Well, I'm glad that I may have saved one rootfs, then ;) Feb 18 22:33:18 Marcel_M, ping Feb 18 22:33:40 one saved, thousands to go! Feb 18 23:17:05 wurp2|away: soo... the results of my first field test day with the modem waking up my neo is as follows: 22h uptime (since yesterday, 2AM my time, no its about midnight here in europe), 2/3 battery charge still remaining, bust just two calls and two SMS today. only problem is that the PIN dialog gets hidden sometimes behind some other windows (lock screen etc.) and can't be brought to front again. PIN dialog came up one time after forced wakeup (au Feb 18 23:17:05 x button), probably because I lost connectivity in the concrete office building I was in (I had that problem with my old cellphone). Summary: the phone works and should be, from the point of view 'power consumption' and if the battery display is in any way linear, working for two days without recharging. I'm recharging now, but as I said, I just had 22h standby and maybe 20min uptime. Feb 18 23:18:11 I assume the phone doesn't actually work after wake? - as a phone that is. Feb 18 23:18:21 no, it does Feb 18 23:18:29 For calls? Feb 18 23:18:38 yes. when removing the kernel console line Feb 18 23:18:47 nice. Feb 18 23:19:14 you mean simply remove the console line from the environment? Feb 18 23:19:39 yes, from the uboot line. Feb 18 23:19:48 Interesting. Feb 18 23:21:25 yes, USEFUL! :-) Feb 18 23:21:50 the only thing which is annoying is the sporadic hiding of the PIN dialog. and that there seems to be no way to bring it to front again Feb 18 23:22:09 *gnarf* Feb 18 23:22:39 if I call my neo and it is in sleep mode, it makes this white flash on the display, shows the console cursor for a fraction of a second, is back in X and then the call can be picked up (and the phone rings btw :-) Feb 18 23:22:59 i cant wait to get my hands on it :) yay! Feb 18 23:23:10 if i wake it up with another interrupt (power button or whatever), it goes from sleep to X the same way and I can make calls without any audio problems or similar Feb 18 23:23:12 nvm, just wanted to say something Feb 18 23:24:08 this all is happening with the february, 11th snapshot and the uboot console kernel command line option fix. or however you'd call that ;-) Feb 18 23:25:20 so... this is not supposed to work, is it? Feb 18 23:25:37 or is this simply an issue of me having a late GTA01 neo with late modem firmware? Feb 18 23:25:56 (I didn't mail anything to the openmoko michael for updating) Feb 18 23:28:21 i have no idea, i just have a veeerry slow qemu package, which make it impossible to work with Feb 18 23:30:58 toxx_: That is friggin' fantastic! Feb 18 23:31:24 OK, retarded question... how do I update my boot parms on the neo? Feb 18 23:31:32 well, here they are: Feb 18 23:31:37 'cause I gotta try that Feb 18 23:31:41 you have to do this (I boot from SD btw) Feb 18 23:31:43 Oh, I think I know what I want to do Feb 18 23:31:44 (more space) Feb 18 23:31:53 once I know where they are :-) Feb 18 23:32:02 I do not boot from SD currently Feb 18 23:32:07 so this will be a new test Feb 18 23:32:08 wait, I just reboot my phone so that I can cu-l into it and give you the paramteres :) Feb 18 23:32:24 toxx_: This totally deserves a wiki page Feb 18 23:32:37 If you don't want to add one, I will once I've worked through it all Feb 18 23:32:41 ok, I'll make one after you also give a thumbs up :) Feb 18 23:32:47 no I can do that Feb 18 23:32:49 no problem Feb 18 23:33:05 maybe you can link it from the appropiate pages Feb 18 23:33:13 I haven't even tried suspend, because I thought everyone knew it doesn't work :-) Feb 18 23:33:28 Maybe a link in from battery life, and the new 'official' index Feb 18 23:33:45 my menu_6 entry is (set with setenv and escape all $ and ; symbols): Feb 18 23:33:51 menu_6=Boot SD standby-ready: setenv bootargs root=/dev/mmcblk0p1 rootdelay=5 console=tty0 loglevel=8 ${mtdparts}; mmcinit; ext2load mmc 0 0x32000000 /boot/${sd_image_name}; bootm 0x32000000 Feb 18 23:33:58 well, suspend maybe is OK, but wake "won't work" Feb 18 23:34:04 that works. it is already from the wiki somewhere, for the qtopia image though Feb 18 23:34:15 ah, I see Feb 18 23:34:27 You add a new boot option in the boot menu Feb 18 23:34:48 I will prolly do that first, then if it works, update the default boot option Feb 18 23:35:05 The important thing is just to remove Feb 18 23:35:12 even my nokia 6230 doesnt have 22h standby :) Feb 18 23:35:16 console=ttySAC0,115200 Feb 18 23:35:18 from the options Feb 18 23:35:20 I'll go hunt around on the wiki to see what the correct root is for SD Feb 18 23:35:45 /dev/mmcblk0p1 ? Feb 18 23:36:57 I've been annoyingly delaye. Feb 18 23:37:09 So haven't got power usage figures in all states updated. Feb 18 23:37:22 hopefully tomorrrow - including stanby using this metho Feb 18 23:37:24 d Feb 18 23:38:02 kahless_, my nokia has days and days standby Feb 18 23:38:14 Mine goes about a week. Feb 18 23:38:20 Mono displays ++ Feb 18 23:40:03 jamewill: :) Feb 18 23:40:36 Does anyone know if there is a way to display the data for a menu option from the console at ttyAC0? Feb 18 23:40:57 as in, let me see what my default boot options are so I can copy them into a new menu option? Feb 18 23:41:10 kahless_, but you are right this is REALLY good news 22hrs and 2/3 of battery left is REALLY good Feb 18 23:41:32 Well, we should note that 2/3 battery life isn't 2/3 battery life Feb 18 23:41:33 jamewill: it's probably not 2/3 - the guage is inaccurate. Feb 18 23:41:44 but it's still really good compared to 4 hours, then dead :-) Feb 18 23:41:55 Ballpark - 50%=5%, 95%=90% Feb 18 23:42:01 SpeedEvil, fair enough - roll on the new Coulomb counter batteries... Feb 18 23:42:16 That's utterly irrelevant Feb 18 23:42:21 and IMO unneeded. Feb 18 23:42:39 For this class of device voltage gives you an absolutely adequate battery meter Feb 18 23:43:14 At the cost of much more expensive batteries. Feb 18 23:43:37 really away again; wife home Feb 18 23:44:07 SpeedEvil, Ahh well nothing but the best at OpenMoko.... price is not exactly our KSP Feb 18 23:45:54 SpeedEvil, has anyone reverse engineered the protocol Nokia seems to use to talk to its "intelligent" batteries yet? Feb 18 23:46:21 SpeedEvil, would be very handy to be able to source cheap Nokia replacements... Feb 18 23:46:34 argl. i got but by the KDE 'slow key option' kicking in after some seconds on some i-dont-know-key. gladly, I faintly remembered that I triggered this stupid behaviour before.... :-| Feb 18 23:46:48 wurp2|away: I'll write the wiki article now! :-) Feb 18 23:49:18 jamewill: I' be very surprised if they bothered - though I haven't looked. From the basic lithium-ion charge curve, and a knowledge of the capacity of the battery - at least at low discharge rates (and 2-4 hours is low), with a knowledge of temperature, you can get charge state to within 5% - within 1% or so when it's changing fast, without much issue. Feb 18 23:50:24 SpeedEvil, Nokia issue (as i understand) is not capacity but that Neo cannot charge this battery at mo (its on the wiki somewhere....MickeyL) Feb 18 23:51:12 SpeedEvil, so you can have charged Nokia brand battery (charged elsewhere) and insert into Neo and it works......till discharged. Feb 18 23:52:00 jamewill, fair enough though its not even "secondary" at this point Feb 18 23:53:50 wurp2|away: printenv Feb 19 00:08:23 wurp2|away: I just created http://wiki.openmoko.org/wiki/GTA01Standby . can you have a look? Feb 19 00:09:32 toer: search gta01 power managment] Feb 19 00:09:45 I forget the exact title of the page - and add it to that probably. Feb 19 00:09:56 Or at least link Feb 19 00:10:35 SpeedEvil: http://wiki.openmoko.org/wiki/Neo1973_GTA01_Power_Management Feb 19 00:13:37 cesarb, SpeedEvil : Done. Ok as it is? Feb 19 00:13:47 (Right at the top, where it says unimplemented) Feb 19 00:15:18 toxx_: anywhere is good, as long as you can get from the central gta01 power management page to it Feb 19 00:15:42 toxx_: else it gets "lost in the wiki" ;-) Feb 19 00:16:19 cesarb: alright, I think my change should do it. not very experienced with keeping a wiki together! :) Feb 19 00:17:39 toxx_: as we say on Wikipedia, "Be bold!" (http://en.wikipedia.org/wiki/Wikipedia:Be_bold) Feb 19 00:18:55 anyone happen to have built an up to date midpath package containing midpath-microbackend.jar? Feb 19 00:23:52 * Stephmw would also settle for the midpath ipk to extract it from ;) Feb 19 00:35:33 nevermind, found one ;) Feb 19 01:02:51 mickey|zzZZzz: svn: Unable to find repository location for 'http://svn.openmoko.org/branches/src/target/kernel/2.6.24.x/config' in revision 3801 Feb 19 01:03:07 * rwhitby grumbles about the openmoko repo being "stable" ... Feb 19 01:03:52 rwhitby: that problem has been there since the beginning of the repo Feb 19 01:04:16 I guess it's stably broken then :- Feb 19 01:04:18 rwhitby: I suspect someone played unclean games with the svn repo (removed the directory and added it again instead of removing it) on a revision after that one Feb 19 01:04:42 rwhitby: meaning that, as svn says, the directory currently called by that name didn't exist on revision 3801 Feb 19 01:04:51 cesarb: well the sane-srcrevs.inc file must have been updated without testing then Feb 19 01:05:15 rwhitby: that revision probably worked before the directory was removed/added Feb 19 01:05:19 (being able to play with svn structure is *exactly* why we have SRCREVs in the first place. Feb 19 01:05:47 toxx_: The instructions look great to me! I'll add the proper boot sequence for flash boot after I get it working on my neo. Feb 19 01:05:54 cesarb: huh? you can't change an SVN revision once it's commited. even by removing directories afterwards. Feb 19 01:06:11 rwhitby: r3824 | werner | 2008-01-13 22:46:12 -0200 (Dom, 13 Jan 2008) | 7 lines Feb 19 01:06:20 rwhitby: A /branches/src/target/kernel/2.6.24.x/config Feb 19 01:06:31 rwhitby: as you can see, the directory was added on revision 3824 Feb 19 01:06:48 away again :-) Feb 19 01:07:11 rwhitby: svn gets what currently is at the specified location (i.e. HEAD) and goes back in time until it finds the specified revision. It can even follow moves while doing so AFAIK Feb 19 01:07:24 3801 was the stable version for the 2.6.22 kernel, but doesn't apply to the 2.6.24 kernel AFAIK Feb 19 01:07:48 So when the default kernel was switched in OE, the SVN version no longer makes sense. Feb 19 01:08:57 Just don't use the latest SVN version with the 2.6.24 kernel, if you value the contents of your SD card... Feb 19 01:10:13 mwester-laptop: you can always simply remove the SD card, like I've done while testing what little I developed of cpufreq so far Feb 19 01:10:31 That's a really good idea. I was lazy, though. Feb 19 01:11:06 Plus, I was the one doing the debugging and testing my patches; you'd think I'd know that I was risking my SD data :-) Feb 19 01:11:52 mwester-laptop: that's the downside of being a kernel dev: someone has to test what you wrote, and well... Feb 19 01:12:25 So have you toasted your HW yet with the clock changing? That has a certain element of risk, doesn't it? Feb 19 01:12:33 mwester: if the svn version no longer made sense, then it shouldn't have been copied to be the SVNREV for the 2.6.24 version of the kernel recipe Feb 19 01:13:18 mwester-laptop: I knew from other people's experiments that the worst which could happen would be a recoverable crash Feb 19 01:13:42 mwester-laptop: well, I could also somehow hose some of the NAND contents in someone's far-fetched theory, but I have a debug board if needed Feb 19 01:13:49 It wasn't copied; it was left behind in the sane-srcrevs.inc file because there's nothing in the sane-srcrevs that can qualify the svn version to the specific version of the kernel :( Feb 19 01:14:20 cesarb: the worst case I came up with was some wierd oops that wrote to block 0 of the NAND a lot Feb 19 01:14:21 cesarb, ok - I had heard somewhere that you could actually damage components like the LCD if you messed up the clocks too badly. Feb 19 01:14:30 mwester: you can Feb 19 01:14:33 mwester-laptop: however, I have no idea so far how the SD card would behave without having the driver modified, so I tested without it (and without a SIM too, just for the heck of it) Feb 19 01:15:07 cesarb: do that >1000 times and the NAND is no longer specced to be error free on block 0 - which may screw the bootloader. Feb 19 01:15:29 mwester-laptop: you could in theory burn the vibrator motor (or not -- SpeedEvil is the hw guy around here, I never played with motors), but I didn't put a SIM in, so the vibrator wouldn't light up Feb 19 01:15:51 vibrator motor will be fine unless you run it for hours. Feb 19 01:16:13 SpeedEvil: even without the PWM pulsing it on and off? good to know Feb 19 01:16:43 cesarb: they are used in model aircraft - the motors Feb 19 01:17:03 cesarb: though they are way too heavy for the smallest planes of course. Feb 19 01:17:06 cesarb: Feb 19 01:17:13 cesarb: R/C with a mass under 0.5g Feb 19 01:18:56 rwhitby: although I'll agree with the concern that the stable branch was not tested, and also note that this problem has been around for at least a week, which is even more concerning. (Does nobody build stable, or does nobody build at all?) Feb 19 01:20:24 * technil builds using MokoMakeFile about once a month Feb 19 01:21:34 mwester-laptop: a week? Feb 19 01:21:39 mwester-laptop: a _week_? Feb 19 01:21:42 mwester-laptop: more like a month Feb 19 01:22:04 * mwester-laptop hangs his head in shame; he only builds "bleeding edge" Feb 19 01:22:28 er, "attempts" to build -- success rates vary ;) Feb 19 01:23:08 mwester-laptop: I think stable never built at all Feb 19 01:23:46 mwester-laptop: I tried once, gave up, and edited my copy of mokomakefile to use "unstable" by default Feb 19 01:23:54 mwester-laptop: since it was more stable ;-) Feb 19 01:24:58 cesarb: http://www.rcgroups.com/forums/showthread.php?t=806518 silly plane Feb 19 01:25:03 I just checked my "mokostable" directory; January 17th Feb 19 01:25:14 So it built back then! Feb 19 01:25:31 mwester-laptop: wow Feb 19 01:30:47 my last build MokoMakefile was Jan 5, so a bit more than a month. Works fine, but I'm in 850 land so no GSM testing. I remember I had to skip building openmoko-terminal2 Feb 19 01:34:01 anyone have a favorite application for viewing GPS tracks? Feb 19 01:34:21 (desktop) Feb 19 01:46:09 josm Feb 19 01:46:23 -> technil Feb 19 01:47:06 http://wiki.openstreetmap.org/index.php/JOSM **** ENDING LOGGING AT Tue Feb 19 02:59:56 2008