**** BEGIN LOGGING AT Mon Feb 25 10:59:56 2008 Feb 25 11:18:55 yay, finally got a gps lock Feb 25 11:19:10 inside too :) Feb 25 11:19:49 Psi_ was it you posting to the list that you couldn't get a lock? Feb 25 11:19:59 yep Feb 25 11:20:52 i was playing with gllin options and i tried -sim (not using simulator) and its working Feb 25 11:21:19 no idea why the simulator was on in the first place tho, assuming -sim has anything to do with why its working now Feb 25 11:21:31 ok... I'm always keen to hear the explanation about the problem Feb 25 12:14:24 hi would it be possible to use a usb hub with the freerunner when it is released ? Feb 25 12:20:16 -to use a usb keyboard and a wifi card Feb 25 12:20:46 will need external power if it's like gta01/02 Feb 25 12:20:55 oh really ... Feb 25 12:21:40 tis just the monitor mode is not there and injection likewise atm -firmware constraints on the ak600 still no ? Feb 25 12:21:48 -wants kismet Feb 25 13:31:13 hi Feb 25 13:31:32 NOTE: Waiting for 1 active tasks to finish Feb 25 13:31:33 NOTE: 1: /root/openmoko/openembedded/packages/u-boot/u-boot-openmoko_1.3.1+git+svn.bb, do_fetch (8632) Feb 25 13:31:43 my openmoko build is stuck at this point Feb 25 13:31:49 from the last 10 hours Feb 25 13:31:55 can any body tell me what to do ? Feb 25 13:32:57 alam: I think you can go download that file yourself & put it in your cache, then restart the build Feb 25 13:33:24 let me try this. Feb 25 13:36:57 please tell me where to download this package. Feb 25 13:37:05 as google is giving no hints Feb 25 13:38:04 where i can download the file: u-boot-openmoko_1.3.1+git+svn.bb Feb 25 13:38:12 as my build is stuck at this point from the morning. Feb 25 13:39:42 look at that .bb file for SRC_URI Feb 25 13:42:31 ynezz: did not get your point Feb 25 13:42:36 kindly tell me a bit. Feb 25 13:42:48 i am here Feb 25 13:42:50 http://www.openembedded.org/filebrowser/org.openembedded.dev/packages/u-boot Feb 25 13:44:10 no, in your local OE dir Feb 25 13:44:37 man read something about OE first, it'll save you a lot of time Feb 25 13:44:40 belive me Feb 25 13:44:53 s/belive/believe/ Feb 25 13:44:53 ynezz meant: believe me Feb 25 13:49:44 hi...is it possible to build only the kernel with the mokomakefile? Feb 25 13:50:10 i have copied the file: http://www.openembedded.org/repo/org.openembedded.dev/packages/u-boot/u-boot-openmoko_1.3.1+git+svn.bb Feb 25 13:50:14 to the specified directory Feb 25 13:50:20 and restarted the proecess Feb 25 13:50:53 now again stuck Feb 25 13:59:46 zefanja: bitbake virtual/kernel Feb 25 14:00:15 zefanja: dunno if mokomakefile's build-package-virtual/kernel would work Feb 25 14:07:28 yay, my toolchain just built successfully Feb 25 14:11:46 hi every body, can body please please please help me Feb 25 14:11:48 NOTE: Waiting for 1 active tasks to finish Feb 25 14:11:48 NOTE: 1: /root/openmoko/openembedded/packages/u-boot/u-boot-openmoko_1.3.1+git+svn.bb, do_fetch (9208) Feb 25 14:11:57 this task is waiting since morning. Feb 25 14:11:59 any clue? Feb 25 14:12:27 i have copied the required file Feb 25 14:12:31 but still stuck there Feb 25 14:12:35 no, you didn't Feb 25 14:13:42 i had Feb 25 14:13:47 from the site of openmoko Feb 25 14:14:43 THis is the ine in the source Feb 25 14:14:44 SRC_URI = "\ Feb 25 14:14:45 git://www.denx.de/git/u-boot.git;protocol=git;tag=${UBOOT_UPSTREAM_REV} \ Feb 25 14:14:45 svn://svn.openmoko.org/trunk/src/target/u-boot;module=patches;rev=${UBOOT_OPENMOKO_REV};proto=http \ Feb 25 14:14:45 file://uboot-eabi-fix-HACK.patch \ Feb 25 14:14:45 file://uboot-20070311-tools_makefile_ln_sf.patch;patch=1 \ Feb 25 14:14:45 file://makefile-no-dirafter.patch;patch=1 \ Feb 25 14:14:48 " Feb 25 14:14:49 what shall i remove from this Feb 25 14:14:53 in order to make it function Feb 25 14:15:19 nothing to remove Feb 25 14:15:34 that git:// or svn:// url isn't working Feb 25 14:15:44 do you need u-boot? Feb 25 14:15:55 yes, for emulator Feb 25 14:16:16 so shall remove git:// Feb 25 14:16:24 so that i can function from the emulator Feb 25 14:18:02 i think so Feb 25 14:18:29 If I were you I would use precompiled images Feb 25 14:19:34 you are right, but i want to do some chang ein the openmoko kernel Feb 25 14:19:43 thats why precompiled images will not be sufficient. Feb 25 14:20:02 I will have to build by my self. Feb 25 14:20:04 i think so Feb 25 14:56:15 freesmartphone.org: 03emdete * r79 10/trunk/software/pyneod/ (15 files): Feb 25 14:56:15 freesmartphone.org: new "method-response-signature equals signal-signature"-pattern implemented Feb 25 14:56:15 freesmartphone.org: steps taken towards open-smartphone-gsm api Feb 25 14:56:15 freesmartphone.org: fixed problems with ggl location by cell-id lookup Feb 25 16:54:08 I'd like to take a look at the openembedded/packages/openmoko-examples code but the build environment only contains the bb files. So I tried to build them with, for example, "make build-package-openmoko-finger-demo" but the fetch task fails Feb 25 16:54:34 So where can I take a look at the openmoko-examples files Feb 25 16:54:37 ? Feb 25 18:29:37 jmichel: look in your openmoko directory Feb 25 18:31:16 ${OMDIR}/openmoko/trunk/src/target/OM-2007.2/examples Feb 25 18:37:08 ScaredyCat: Thanks I found the example code you are talking about Feb 25 18:37:49 I'll try to start from there to build by OM application Feb 25 18:41:51 Heh, failed on the kernel again now Feb 25 18:42:07 The bleeding edge build that is. At least something is happening.. Feb 25 19:04:12 jmichel: take a look at the wiki page for the toolchain... Feb 25 19:04:36 http://wiki.openmoko.org/wiki/Toolchain Feb 25 19:04:41 bbl Feb 25 20:21:35 whenever I connect with cu -l /dev/ttyACM0 , the terminal keeps giving me pages of garbages Feb 25 20:21:40 neverending Feb 25 20:21:55 is it a known thing? Feb 25 20:24:14 I was able to connect and do thing normally before Feb 25 20:25:18 ahven: I never use cu Feb 25 20:25:29 Is your neo in the boot menu, set in USB console mode? Feb 25 20:25:48 (I use 'screen /dev/ttyACM0' instead) Feb 25 20:29:38 usb console and screen does the same Feb 25 20:35:58 So, your neo is plugged into usb, you shut down & restart to the boot menu (aux + power) Feb 25 20:36:11 then you aux down to usb console, hold power until it refreshes the menu Feb 25 20:36:28 then 'screen /dev/ttyACM0', and you get a bunch of garbage on the screen? Feb 25 20:36:44 If that were the case for me, I would try unplugging & replugging the usb cable Feb 25 20:36:52 preferably to a different port on the desktop Feb 25 20:36:56 and avoiding a usb hub Feb 25 20:40:28 aah, forgot the scanner :P Feb 25 20:40:49 hmm.. Feb 25 20:41:21 forgot the scanner? Feb 25 20:45:15 Does your scanner try to talk on ttyACM0? Feb 25 20:45:47 it and the usb webcam interfered, forgot Feb 25 20:45:54 about the other devices* Feb 25 20:52:36 cool Feb 25 20:52:49 I will have to remember that; I don't have any such devices connected to my computer right now Feb 25 20:57:26 you can get minicom from my repo too ahven Feb 25 21:31:52 So, do the current snapshots actually suspend the phone? Feb 25 21:34:29 It's been able to suspend and resume from RAM for some time. Feb 25 21:34:51 Even taking calls in suspend. The qeustion of if current images do it ... Feb 25 21:35:41 SpeedEvil, it seems as though they've disabled it. Feb 25 21:36:29 the only options in the power menu are "dim first, then lock" and "dim only, don't lock". Feb 25 21:36:44 either that or it's so stable that they don't bother exposing the setting for it anymore. :) Feb 25 21:36:45 orospakr: Which build are you using? Feb 25 21:36:56 http://wiki.openmoko.org/wiki/Snapshot_review/2008-02-20 Feb 25 21:37:07 Dim first, then lock I think is the option to suspend... Feb 25 21:37:35 'lock' doesn't mean screen lock, because "Dim only, don't lock" *does* screen lock Feb 25 21:37:45 wurp2, I was noticing that with my build from a month ago, the phone would suspend, and my ssh sessions to it would die. Feb 25 21:38:08 I never use the lock option Feb 25 21:38:25 what's your battery life? :) Feb 25 21:38:31 Because the talk was all saying it didn't work, until recently Feb 25 21:38:38 I dunno, it never goes dead Feb 25 21:38:47 how often do you charge? Feb 25 21:38:54 because I never let it sit more than 2-3 hours w/o being plugged in :-) Feb 25 21:39:03 ah. Feb 25 21:39:13 In honor of kdean06, I shouldn't say never Feb 25 21:39:45 I have let it go dead two or three times in the 2-3 months that I've had it Feb 25 21:40:07 I dunno how long it took to go dead then, but I'd guess I don't have more than 5 hours of battery life Feb 25 21:40:21 Mines been dead more the past few days than alive. :S Feb 25 21:40:31 ack Feb 25 21:40:54 I swear, either I have a defective battery or the management on this thing is controlled by a pRNG or something... Feb 25 21:40:59 SpeedEvil, have you been using yours with the suspend mode enabled? Is the battery life reasonable? Feb 25 21:41:01 kdean06, heh Feb 25 21:41:25 I took it off a 24 hour charge and had it die on a 1 hour car trip in "Dim but don't lock" mode. Feb 25 21:41:45 I've also had it go about 5 hours with light (my daily review) use. Feb 25 21:41:46 Wow, something is definitely wrong there Feb 25 21:41:55 Is it possible that it was illuminated the whole time? Feb 25 21:41:57 orospakr: no Feb 25 21:42:08 orospakr: heard reports of Feb 25 21:42:12 by bumping against the inside of your pocket or something? Feb 25 21:42:28 wurp2, It was in my car's cupholder, so no. :) Feb 25 21:42:40 Even at full 750 mA usage, it should go over an hour, though... Feb 25 21:42:44 I know! Feb 25 21:43:10 I'm writing that one off as a "maybe something happened and it didn't charge"... Feb 25 21:43:27 It does sometimes get confused and go into low power mode Feb 25 21:43:33 install my daemon :-) Feb 25 21:43:51 s/low power mode/slow charge mode/ Feb 25 21:43:58 wurp2, I'm waiting for the next snapshot (need to E-mail Wolfgang, BTW...) but I wanna try your daemon. The lack of mobile charging is a bigger deal-breaker than the poor life, IMO. Feb 25 21:45:29 wow, I just thought you had been too busy to test new releases Feb 25 21:45:35 I didn't realize 2/20 was the latest Feb 25 21:45:40 No, it hasn't generated any. Feb 25 21:45:53 I see that Feb 25 21:47:18 It generated a kernel though... Feb 25 21:47:25 22 Feb 2008. :P Feb 25 21:52:42 ah, it's suspended. Feb 25 21:52:48 I just wasn't being patient enough. Feb 25 21:52:53 Now to try calling it... Feb 25 21:53:26 hm. Feb 25 21:54:44 bah. ringing did not wake the phone up. If I manually woke it with the power button, it saw the incoming call. Feb 25 21:56:23 Are there any 'real' gtk programmers in here? Feb 25 21:56:41 I want my gtk app's buttons to ignore the theme and use a background color Feb 25 21:56:56 heck, even if they use the theme, but let me set the background color, that would be fine Feb 25 21:57:15 I do not want to just set my OM to ignore the theme altogether Feb 25 22:13:15 I believe I found the answer to my question at http://ometer.com/gtk-colors.html Feb 25 22:13:24 I'll have to wait until I get home to try it out Feb 25 22:24:29 this is probably a stupid question, but is the debugboard connection between the cable usually the reason openocd says there's a JTAG communication error? Feb 25 22:25:07 im pretty sure its talking to the ft2232 chip okay. I've never actually successfully run openocd before so i dont really know how differentiate its debugging messages Feb 25 22:31:59 johnycsh: try the connection sequence at http://wiki.openmoko.org/wiki/Neo1973_Debug_Board_v2#Hardware_connection before running openocd. Feb 25 22:33:36 I'll give it another go. Do i need the phone to be paused at the U-boot screen, or can the kernel already be loaded? Feb 25 22:35:31 openocd should be able to connect even if the phone has already booted. Feb 25 22:35:56 thanks, thats what i thought. Feb 25 22:44:23 mmontour: seems like I always get this same thing. Feb 25 22:44:27 nfo: openocd.c:86 main(): Open On-Chip Debugger (2007-03-30 12:00 CEST) Feb 25 22:44:27 Debug: arm920t.c:726 arm920t_target_command(): chain_pos: 0, variant: arm920t Feb 25 22:44:27 Debug: jtag.c:1335 jtag_init(): - Feb 25 22:44:27 Debug: ft2232.c:1270 ft2232_init(): 'ft2232' interface using libftdi with 'jtagkey' layout Feb 25 22:44:27 .., etc Feb 25 22:44:27 Debug: jtag.c:1027 jtag_read_buffer(): fields[0].in_value: 0x0000000000000000 Feb 25 22:44:29 Error: jtag.c:1182 jtag_examine_chain(): JTAG communication failure, check connection, JTAG interface, target power etc. Feb 25 22:44:57 and then TTYUSB0 is gone, have to reload ftdi_sio to get it back. Feb 25 22:47:47 You shouldn't need to reload the module. Try exiting openocd, unplugging and then re-plugging the debug board's USB cable, then re-running openocd. Also don't plug the phone into the USB hub on the debug board. Feb 25 22:48:42 Also make sure that when you load the ftdi_sio module that you give it the correct vendor/product ID as module parameters. Feb 25 22:51:43 johnycsh: Use pastebin next time Feb 25 22:51:49 ~pastebin Feb 25 22:51:49 [~pastebin] A "pastebin" is a web-based service where you can paste anything over 3 lines without flooding the channel. Here are links to a few : http://www.pastebin.com , http://pastebin.ca , http://channels.debian.net/paste , http://paste.lisp.org , http://www.rafb.net/paste Feb 25 22:52:23 mwester-road: okay, thanks. Feb 25 23:26:43 mmontour: seems like no matter what i do, i get the same thing from openocd. http://pastebin.com/d612e58f5 Feb 25 23:27:00 same set of messages even if the FPC cable is unplugged.. Feb 25 23:39:45 johnycsh: The only other suggestions I have are: make sure the Neo is powered on, and try a newer version of openocd (such as one built by MokoMakefile with "make openmoko-devel-tools" or "bitbake openocd-native"). Feb 26 00:28:40 openmoko: 03werner * r4111 10/branches/src/target/kernel/2.6.24.x/patches/ (fix-i2c-s3c2410-resume-race.patch series): (log message trimmed) Feb 26 00:28:40 openmoko: fix-i2c-s3c2410-resume-race.patch Feb 26 00:28:40 openmoko: From: Andy Green Feb 26 00:28:40 openmoko: There is a nasty race between i2c-s3c2410 resume and resume of I2C Feb 26 00:28:42 openmoko: driver and the client drivers -- the watchdog device actually gets to Feb 26 00:28:44 openmoko: use the dead I2C bus before it is reinitialized by the I2C driver Feb 26 00:28:46 openmoko: resume! This patch makes sure any customers get turned away until Feb 26 00:32:25 mmontour: I got the debugboard talking! It was just a bad connection Feb 26 00:32:32 thanks for the help :) Feb 26 01:29:06 Hi. i was wondering if anyone with a Neo had a chance to run tests on Rogers in Alberta (more specifically Edmonton/St.Albert)? i tested a Nokia N70 (no 850 Mhz) and it ran fine, so I was wondering how the current GTA01 works. Feb 26 02:16:49 Does anyone know why python-dbus isn't in the repositories any more? Feb 26 02:17:00 Or where I can find it? Feb 26 03:18:19 openmoko: 03werner * r4112 10/trunk/src/target/gpio/gpio.c: gpio.c (pin_a): mark port A pin values as outputs Feb 26 04:38:22 openmoko: 03werner * r4113 10/trunk/src/host/devirginator/flashnor: flashnor: utility to intelligently flash the GTA02 NOR Feb 26 07:20:10 good morning Feb 26 07:26:17 Hopscotch: Good Morning Feb 26 07:33:00 * * OM Bug 1236 has been created by julian_chu(AT)openmoko.com Feb 26 07:33:01 * * Xglamo Feb 26 07:33:02 * * http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1236 Feb 26 07:53:09 openmoko: 03werner * r4114 10/branches/src/target/kernel/2.6.24.x/patches/gta01-inputdevice.patch: Feb 26 07:53:09 openmoko: We can wake up from suspend with POWER, so there's no need to have AUX as Feb 26 07:53:09 openmoko: as another wakeup source, and in particular one that's easily triggered Feb 26 07:53:09 openmoko: by accident. Feb 26 07:53:09 openmoko: gta01-inputdevice.patch: Feb 26 07:53:11 openmoko: - drivers/input/keyboard/neo1973kbd.c (neo1973kbd_probe): don't make AUX a Feb 26 07:53:15 openmoko: wakeup source ever Feb 26 07:57:50 morning Feb 26 08:06:47 hey Feb 26 08:06:56 errr... is the neo1973 waterproof? Feb 26 08:07:38 HAHAHAHHAHAHAHAHAHAHAHAHAH Feb 26 08:57:19 openmoko: 03erin_yueh * r4115 10/trunk/src/target/gsm/ (6 files in 5 dirs): gsmd: add vibrator at cmd (Sudharshan S) Feb 26 09:02:37 openmoko: 03erin_yueh * r4116 10/trunk/src/target/gsm/include/gsmd/usock.h: gsmd: sms data structure (Paulius Zaleckas) Feb 26 09:50:19 wurp2: http://celtune.morb-design.com/ipk/armv4t/python-dbus_0.81.1-ml1_armv4t.ipk Feb 26 09:52:04 good morning Feb 26 10:13:05 openmoko: 03werner * r4117 10/trunk/src/host/devirginator/setup.sh: setup.sh: use envedit.pl -s 0x40000 on GTA02 **** ENDING LOGGING AT Tue Feb 26 10:59:56 2008