**** BEGIN LOGGING AT Wed Apr 11 02:59:58 2012
Apr 11 05:16:35 <PaulFertser> mick_laptop: QtMoko is rather popular too.
Apr 11 05:17:26 <PaulFertser> mick_laptop: are you aware that FR lacks hardware FP and is thus incompatible with quite some amount of code in SIP clients?
Apr 11 05:18:09 <PaulFertser> mick_laptop: you might have luck after properly configuring linphone and disabling power-saving for the wifi card (with wmiconfig) but i'm not aware of anybody actively using this combination.
Apr 11 05:25:01 <mick_laptop> thanks for that info PaulFertser 
Apr 11 05:25:33 <mick_laptop> PaulFertser: my current problem w/ linphone is that the devs are impossible to get ahold of
Apr 11 05:25:52 <mick_laptop> the mailinglist is broken
Apr 11 05:25:55 <PaulFertser> mick_laptop: and you'll want some harsh settings to get it to work almost half-duplex to avoid echo.
Apr 11 05:26:23 <mick_laptop> I remember having some pretty bad echo before, heh
Apr 11 05:26:48 <PaulFertser> mick_laptop: and i suggest to avoid android, it'be silly to use such an inferiour OS on basically the only device that can really run something decent.
Apr 11 05:28:07 <PaulFertser> Echo is also affected by the screws, without them there's less echo. But you still need to enable some counter-measures and probably linphone's echo cancelling is FP-based so can't be done realtime on the fpuless slow FR's cpu, so you'll have to resort to automatic half-duplex.
Apr 11 05:28:13 <mick_laptop> the other thing w/ linphone is their iphone support (I also tried this)... they support IOS v3 according to their release notes but the binary from the app store store requires 4.3
Apr 11 05:28:56 <mick_laptop> PaulFertser: ok, will avoid it :)
Apr 11 05:29:43 <PaulFertser> mick_laptop: please do not forget to report your VoIP experience on the community mailing list after you try :)
Apr 11 05:30:24 <mick_laptop> also, what does FP stand for?
Apr 11 05:30:54 <mick_laptop> I get FR == FreeRunner
Apr 11 05:31:11 <PaulFertser> But the key would be 1. disable wifi power-saving 2. set linphone to use only integer-based codecs 3. watch cpu utilisation and find the settings that allow both echo cancelling/suppression and low cpu consumption.
Apr 11 05:31:17 <PaulFertser> mick_laptop: floating point
Apr 11 05:31:26 <mick_laptop> ah ok
Apr 11 05:31:26 <mick_laptop> heh
Apr 11 05:31:43 <mick_laptop> well, #1 would be to upgrade or reinstall my phone
Apr 11 05:31:59 <mick_laptop> since it is really old at this point
Apr 11 05:32:59 <PaulFertser> Heh
Apr 11 05:33:05 <PaulFertser> I'm running plain Debian btw.
Apr 11 05:42:42 <mick_laptop> PaulFertser: this is funny that I forgot everything since 2008
Apr 11 05:43:28 <mick_laptop> I was able to setup SHR, no problems... now I'm like "WTH did I do to get this thing working... did I use minicom or what?!"
Apr 11 05:44:12 <mick_laptop> so easy to forget things :(
Apr 11 05:49:13 <mick_laptop> hmm, I held down AUX and selected "Set console to USB" and it gets me from UBoot to NOR 
Apr 11 05:50:05 <PaulFertser> mick_laptop: but you shouldn't use NOR u-boot to normally boot the device, i suggest you use it only for DFU flashing.
Apr 11 05:51:02 <mick_laptop> well, I want to flash it
Apr 11 05:51:17 <mick_laptop> how else would I get qtmoko on there?
Apr 11 05:51:34 <mick_laptop> don't i need to upgrade uboot first?
Apr 11 05:51:43 <PaulFertser> mick_laptop: yep, flashing to nand would work fine with nor u-boot.
Apr 11 05:51:45 <mick_laptop> since this is circa2008 software on here
Apr 11 05:51:54 <mick_laptop> [35340.118096] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 11 05:51:57 <mick_laptop> [35340.118106] usb 3-1: Product: Neo1973 Bootloader U-Boot 1.3.2-moko12
Apr 11 05:51:57 <PaulFertser> mick_laptop: i'm using Qi on nand, should work fine for qtmoko
Apr 11 05:52:16 * mick_laptop looks up Qi
Apr 11 05:52:34 <PaulFertser> mick_laptop: and you do not need to upgrade the NOR u-boot.
Apr 11 05:53:03 <mick_laptop> ah ok
Apr 11 05:53:13 <mick_laptop> do I need a microSD card?
Apr 11 05:53:45 <mick_laptop> or is it possible to do usb->moko upgrade?
Apr 11 05:54:11 <mick_laptop> or do I need to put it on an SD card, then boot from SD to upgrade?
Apr 11 05:54:37 <PaulFertser> mick_laptop: no, i think you can simply flash it, no need for the card unless you want to run it from card.
Apr 11 05:57:00 <mick_laptop> ok, so do I need to pull this: http://sourceforge.net/projects/qtmoko/files/qtmoko-debian-gta02-v39.ubi/download ?
Apr 11 05:57:45 <mick_laptop> ah docs say I should install qi
Apr 11 05:58:35 <mick_laptop> really? no md5/sha sums? *sigh*
Apr 11 05:58:46 <mick_laptop> ok, then I'll just cross my fingers
Apr 11 06:00:25 <PaulFertser> :(
Apr 11 06:00:35 <PaulFertser> I think i've reported lack of hashes once.
Apr 11 06:01:05 <PaulFertser> mick_laptop: you can use u-boot but you're then expected to understand enough of its manual and linux booting practicies.
Apr 11 06:02:23 <mick_laptop> besides runlevels, what else is there to understand :P
Apr 11 06:02:51 <mick_laptop> and besides, if I can figure out lilo/grub... this shouldn't be too hard
Apr 11 06:03:43 <PaulFertser> Heh, runlevels are irrelevant.
Apr 11 06:04:03 <PaulFertser> You need to be able to understand how to tell u-boot to fetch a kernel from nand and to start it passing proper bootargs.
Apr 11 06:04:42 <PaulFertser> U-boot's default command used to load only first 2M of the kernel which might be not enough if yours is bigger.
Apr 11 06:05:34 <mick_laptop> weird
Apr 11 06:05:36 <mick_laptop> Found Runtime: [0x03f0:0x181d] devnum=3, cfg=0, intf=0, alt=0, name="UNDEFINED"
Apr 11 06:05:39 <mick_laptop> Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"
Apr 11 06:05:50 <mick_laptop> that is from # dfu-util --list
Apr 11 06:07:32 <PaulFertser> Probably you have another dfu device.
Apr 11 06:08:21 <mick_laptop> http://pastebin.com/raw.php?i=AabsFHzr
Apr 11 06:08:35 <mick_laptop> this is probably where I screwed up, I did it 2x
Apr 11 06:08:56 <mick_laptop> I only have one device plugged in
Apr 11 06:09:13 <mick_laptop>  nothing  but the FR over usb
Apr 11 06:11:33 <mick_laptop> I guess this calls for a reboot
Apr 11 06:13:50 * mick_laptop hopes this works
Apr 11 06:14:33 <mick_laptop> brb
Apr 11 06:14:35 <mick_laptop> rebooting
Apr 11 06:19:42 <mick_laptop> sigh
Apr 11 06:20:17 <mick_laptop> PaulFertser: am I doing this right?
Apr 11 06:20:39 <mick_laptop> booting to usb mode, then running dfu-util
Apr 11 06:21:17 <mick_laptop> Claiming USB DFU Runtime Interface...
Apr 11 06:21:17 <mick_laptop> Determining device status: state = dfuIDLE, status = 0
Apr 11 06:21:17 <mick_laptop> WARNING: Runtime device already in DFU state ?!?
Apr 11 06:21:17 <mick_laptop> No such Alternate Setting: "kernel"
Apr 11 06:21:46 <mick_laptop> I must be doing something very wrong here
Apr 11 06:24:00 <mick_laptop> how do I get it to actually upgrade qi?
Apr 11 06:24:11 <mick_laptop> Found Runtime: [0x1d50:0x5119] devnum=5, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade" <--- i see it loaded
Apr 11 06:30:58 <PaulFertser> mick_laptop: probably your dfu-util version is old/buggy.
Apr 11 06:33:24 <mick_laptop> I added -d 0x1d50:0x5119  and it seems to at least copy over to the phone
Apr 11 06:33:40 * mick_laptop crosses fingers
Apr 11 06:36:49 <mick_laptop> PaulFertser: I pulled dfu-util from debian's repo
Apr 11 06:37:14 <mick_laptop> what version do you use?
Apr 11 07:21:32 <PaulFertser> mick_laptop: oh, i haven't used dfu-util since ages...
Apr 11 07:24:00 <mick_laptop> k
Apr 11 07:24:30 <mick_laptop> rebooting....
Apr 11 07:24:45 <mick_laptop> I really hope this worked
Apr 11 07:25:03 <mick_laptop> I guess not
Apr 11 07:25:11 <mick_laptop> i'm stuck on the splash screen
Apr 11 07:26:21 <mick_laptop> this sucks
Apr 11 07:31:02 <mick_laptop> can't read kernel
Apr 11 07:31:14 * mick_laptop reloads kernel
Apr 11 07:31:52 <mick_laptop> bad data CRC :(
Apr 11 07:38:47 <mick_laptop> PaulFertser: you in the US by any chance?
Apr 11 07:39:05 <mick_laptop> I'd like to  know if any US carriers allow the FR
Apr 11 07:39:54 <mick_laptop> I remember asking in 2008 and one carrier say that only a certain set of "allowed phones" could access their network
Apr 11 07:41:20 <mick_laptop> ok, I see a few things here... for one, I'm still using Uboot
Apr 11 07:41:37 <mick_laptop> another is this crc check that is failing w/ the kernel
Apr 11 07:43:00 <mick_laptop> another thing, the wiki might be a bit dated
Apr 11 07:43:03 <mick_laptop> # file uImage-GTA02-v39.bin 
Apr 11 07:43:04 <mick_laptop> uImage-GTA02-v39.bin: u-boot legacy uImage, Debian FreeRunner Kernel, Linux/ARM, OS Kernel Image (Not compressed), 2162556 bytes, Sat Feb  4 19:27:58 2012, Load Address: 0x30008000, Entry Point: 0x30008000, Header CRC: 0xCC474BA8, Data CRC: 0x072773E3
Apr 11 07:43:25 <mick_laptop> so how do I know what to pass it w/ -d ?
Apr 11 07:43:46 <mick_laptop> I was using: dfu-util -d 0x1d50:0x5119 -a kernel -R -D  uImage-GTA02-v39.bin
Apr 11 07:52:22 <PaulFertser> mick_laptop: heh, no, in Ru
Apr 11 07:53:11 <mick_laptop> shit, I think I bricked it
Apr 11 07:53:25 <PaulFertser> mick_laptop: impossible
Apr 11 07:53:27 <mick_laptop> kernel panic when I try to get into NAND
Apr 11 07:53:36 <PaulFertser> mick_laptop: nor u-boot is impossible to brick.
Apr 11 07:53:40 <PaulFertser> mick_laptop: sorry, gtg, ttyl
Apr 11 07:54:03 <mick_laptop> I hope I will ttyl :)
Apr 11 07:54:05 <mick_laptop> bye
Apr 11 07:55:39 <mick_laptop> heh, it came back
Apr 11 07:56:06 <mick_laptop> still not working, but better than being bricked
Apr 11 08:07:28 <radekp> mick_laptop: sorry, havent followed much, need some help?
Apr 11 15:01:56 <mick_laptop> radekp: if only I'd have seen your message before going to bed
Apr 11 15:01:57 <mick_laptop> :)
Apr 11 15:02:15 <mick_laptop> and ya, I need help
Apr 11 15:02:50 <mick_laptop> I have a kernel panic
Apr 11 15:07:49 <mick_laptop> this is what I've done (more or less)
Apr 11 15:07:51 <mick_laptop> http://pastebin.com/raw.php?i=DiHw7kh1
Apr 11 15:07:59 <mick_laptop> I get a kernel panic
Apr 11 15:09:36 <mick_laptop> I had my openmoko running 2008ish version of SHR and I wanted to flash it w/ Qi and QTMoko
Apr 11 15:09:43 <mick_laptop> radekp: ^^^^
Apr 11 15:10:08 <mick_laptop> now AUX just flashes red and I see a kernel panic
Apr 11 15:15:30 <PaulFertser> mick_laptop: have you flashed only the kernel or rootfs too?
Apr 11 15:19:16 <mick_laptop> both
Apr 11 15:19:21 <mick_laptop> hi PaulFertser :)
Apr 11 15:19:57 <PaulFertser> mick_laptop: hi again
Apr 11 15:20:03 <mick_laptop> from the pastebin: dfu-util -d 0x1d50:0x5119  -a rootfs -R -D qtmoko-debian-gta02-v39.ubi
Apr 11 15:20:29 <PaulFertser> mick_laptop: have you flashed the special "ubi" qi version?
Apr 11 15:20:35 <PaulFertser> I'm afraid not
Apr 11 15:21:16 <mick_laptop> hmm
Apr 11 15:21:27 <mick_laptop> I flashed qi twice, different images
Apr 11 15:21:42 <PaulFertser> mick_laptop: http://sourceforge.net/projects/qtmoko/files/qi-v39.udfu/download
Apr 11 15:22:00 <mick_laptop> yup got that one too
Apr 11 15:22:07 <PaulFertser> But you should flash it :)
Apr 11 15:22:09 <mick_laptop> after that didn't work, I tried the other
Apr 11 15:23:08 <PaulFertser> Can you describe in details how exactly it doesn't work?
Apr 11 15:23:29 <mick_laptop> well at this point my device isn't turning on
Apr 11 15:23:33 <PaulFertser> Also you can try to press and hold the power button and that should make the kernel output its log to the console.
Apr 11 15:23:52 <PaulFertser> mick_laptop: that would suggest your battery is discharged :)
Apr 11 15:24:28 <mick_laptop> power supply is connected to the wall
Apr 11 15:24:37 <mick_laptop> and I can't press power to start it
Apr 11 15:24:56 <PaulFertser> mick_laptop: it can't be started from the wallcharger, unfortunately.
Apr 11 15:25:06 <mick_laptop> wat
Apr 11 15:25:21 <mick_laptop> ok, what should I do? :)
Apr 11 15:25:29 <PaulFertser> mick_laptop: seach http://wiki.openmoko.org/wiki/Neo_FreeRunner_Battery for flat battery
Apr 11 15:26:00 <mick_laptop> odd thing is that it has been connected to the usb on my computer the whole time
Apr 11 15:26:04 <PaulFertser> You should be able to get to NOR u-boot and then you should stay there for long enough for the battery to charge.
Apr 11 15:26:05 <mick_laptop> so why would it be flat?
Apr 11 15:26:25 <PaulFertser> connected doesn't mean charging, that's a special logic.
Apr 11 15:28:13 <mick_laptop> http://wiki.openmoko.org/wiki/Neo_FreeRunner_Battery#More_tricks
Apr 11 15:28:18 <mick_laptop> works :)
Apr 11 15:28:40 <mick_laptop> ok, so I'm in the NOR menu
Apr 11 15:31:11 <mick_laptop> so now I run:
Apr 11 15:31:14 <mick_laptop> # dfu-util -a u-boot -R -D qi-v39.udfu
Apr 11 15:31:34 <mick_laptop> Opening USB Device 0x0000:0x0000...
Apr 11 15:31:34 <mick_laptop> Claiming USB DFU Runtime Interface...
Apr 11 15:31:34 <mick_laptop> Determining device status: state = dfuIDLE, status = 0
Apr 11 15:31:34 <mick_laptop> WARNING: Runtime device already in DFU state ?!?
Apr 11 15:31:34 <mick_laptop> No such Alternate Setting: "u-boot"
Apr 11 15:31:45 <mick_laptop> and I get a prompt
Apr 11 15:31:52 <mick_laptop> should I just reboot now?
Apr 11 15:32:29 <mick_laptop> I get a kernel panic now
Apr 11 15:33:15 <mick_laptop> and when I boot to NOR I get uboot
Apr 11 15:33:24 <mick_laptop> May 9, 2008
Apr 11 15:33:41 <mick_laptop> same as before
Apr 11 15:34:49 <mick_laptop> so when I set it to usb and do: "# dfu-util -d 0x1d50:0x5119 -a u-boot -R -D qi-v39.udfu"
Apr 11 15:35:06 <mick_laptop> it says: "No DFU capable USB device found"
Apr 11 15:36:02 <mick_laptop> PaulFertser: ideas?
Apr 11 15:37:02 <mick_laptop> will it charge at the NOR boot menu?
Apr 11 15:37:32 <mick_laptop> or at the kernel panic?
Apr 11 15:48:18 <PaulFertser> mick_laptop: it should charge at the nor boot menu
Apr 11 15:48:23 <PaulFertser> afair
Apr 11 15:54:20 <mick_laptop> as far as getting Qi to run, what would you recommend
Apr 11 15:56:35 <PaulFertser> mick_laptop: i recommend you read http://wiki.openmoko.org/wiki/Qi to understand what might and what should happen when you are trying to boot with Qi
Apr 11 15:56:38 <PaulFertser> :)
Apr 11 15:57:53 <mick_laptop> I thought it replaces uboot?
Apr 11 15:58:42 <PaulFertser> mick_laptop: but not the nor u-boot.
Apr 11 15:58:58 <mick_laptop> oh  well fuck
Apr 11 16:00:21 <PaulFertser> mick_laptop: i think this http://wiki.openmoko.org/wiki/Booting_the_Neo_FreeRunner_via_U-Boot has some reasonable explanation 
Apr 11 16:00:59 <PaulFertser> mick_laptop: Qi is used instead of u-boot in nand.
Apr 11 16:01:22 <mick_laptop> ok, what should my next step be?
Apr 11 16:01:47 <mick_laptop> I've tried to get kernel, and rootfs to load and the only way I can upload is via -d flag
Apr 11 16:01:54 <mick_laptop> yet it is all a no-go
Apr 11 16:05:36 <PaulFertser> mick_laptop: first: make sure you have a nice charged battery; second: flash Qi, rootfs and kernel all from qtmoko's site; third: try to boot and describe what is excatly happening. Also you shouldn't have a bootable uSD installed as that's the first thing Qi tries to boot from.
Apr 11 16:08:43 <PaulFertser> mick_laptop: a flat battery would probably take an hour in u-boot menu to become useable.
Apr 11 16:09:13 <PaulFertser> mick_laptop: also, you should be feeling vibes when you start Qi as it should indicate that the uSD is not present.
Apr 11 21:24:51 <stephan_arch2> hey guys, is there a tablet that can mess up with the ipad3 but where you can install, lets say gentoo?:)
Apr 11 21:44:11 <DieMumie1> stephan_arch2: if there is one you might find it unlabled at www.alibaba.com
Apr 11 21:44:44 <stephan_arch2> this is a good joke :)
**** ENDING LOGGING AT Thu Apr 12 02:59:58 2012