**** BEGIN LOGGING AT Mon Jun 14 02:59:57 2010
Jun 14 07:20:42 <lag> cooloney: ping
Jun 14 07:22:06 <cooloney> lag: yeah,
Jun 14 07:22:21 <lag> cooloney: Good morning
Jun 14 07:22:36 <cooloney> lag: morning, man
Jun 14 07:22:44 <lag> Is the OMAP4 repo on our server yet?
Jun 14 07:23:35 <amitk> morning guys!
Jun 14 07:23:45 <lag> Morning Amitk
Jun 14 07:24:17 <amitk> I heard that we have a newly-rebased tree from TI?
Jun 14 07:24:28 <cooloney> lag: yeah, i just synced one from sebjan
Jun 14 07:24:53 <cooloney> and he is trying to unify the panda code into his tree
Jun 14 07:25:10 <lag> Great
Jun 14 07:25:13 <cooloney> i will pull from him after that and built for you guys for testing
Jun 14 07:25:24 <amitk> what version is the tree based on cooloney ?
Jun 14 07:25:27 <lag> What's it' called?
Jun 14 07:25:39 <cooloney> lag: do you have other omap4 hardware instead of panda?
Jun 14 07:25:50 <cooloney> amitk: oh it is based on TI 2.6.34 integration tree
Jun 14 07:26:02 <lag> No, just Panda
Jun 14 07:26:24 <hrw> morning
Jun 14 07:26:28 <lag> I'm guessing it would be called ubuntu/ubuntu-lucid-arm.git
Jun 14 07:26:41 <comradekingu> Gnome bytter ut F-spot med shotwell
Jun 14 07:26:53 <comradekingu> Wrong chan, sorry
Jun 14 07:27:17 <cooloney> lag: lucid-arm.git? no, the new branch is for maverick
Jun 14 07:27:43 <lag> I'm guessing it would be called ubuntu/ubuntu-maverick-arm.git
Jun 14 07:27:45 <lag> ;)
Jun 14 07:28:28 <amitk> why is it a separate tree and not a branch in the maverick git tree?
Jun 14 07:28:54 <lag> I understood that it's not ready to go into the main repo yet
Jun 14 07:29:15 <lag> I was chatting with cooloney and ogra about it the other day
Jun 14 07:29:50 <cooloney> lag: http://kernel.ubuntu.com/git?p=roc/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-ubuntu-2.6.34
Jun 14 07:30:01 <cooloney> that is a temp branch in my repo
Jun 14 07:30:14 <lag> Okay
Jun 14 07:30:18 <lag> And after?
Jun 14 07:30:19 <cooloney> after it is ready, i will push it out for review and merge into maverick
Jun 14 07:30:32 <cooloney> amitk ^^
Jun 14 07:30:42 <amitk> ok
Jun 14 09:29:52 <lag> cooloney: ping
Jun 14 10:01:33 <cooloney> lag: could you please try the kernel from http://people.canonical.com/~roc/kernel/omap4-2.6.34-panda/ on your panda?
Jun 14 10:03:00 <lag> Was it built from roc/ubuntu-maverick.git
Jun 14 10:03:43 <cooloney> lag: yeah, it is
Jun 14 10:03:51 <cooloney> lag: i cross built it locally
Jun 14 10:04:09 <lag> By locally, do you mean on 'your' machine?
Jun 14 10:04:28 <lag> I am building the same kernel currently on one of the build servers
Jun 14 10:04:44 <cooloney> lag: yes, on my machine, since i failed to use sbuild on tyler
Jun 14 10:04:58 <cooloney> lag: aha, cool, are you using sbuild?
Jun 14 10:05:26 <lag> No idea
Jun 14 10:05:50 <lag> Whatever's specified in the chroot
Jun 14 10:06:17 <lag> I guess so, as I received an sbuild error this morning when the permissions were messed up
Jun 14 10:08:17 <cooloney> lag: yeah, me2, so i switched to my local builder
Jun 14 10:09:20 <lag> Well once the maverick-armel issue is sorted apw will have it available again within 2 mins
Jun 14 10:10:00 <apw> lag its not that simple
Jun 14 10:10:04 <apw> but i am working on it
Jun 14 10:10:27 <lag> Is it not the same issue as the other build server?
Jun 14 10:10:32 <apw> lag no
Jun 14 10:10:38 <lag> You nailed that in moments few
Jun 14 10:10:47 <apw> as in the machine is now working for you, but not for him
Jun 14 10:10:53 <lag> Ok, sorry for giving false hope :)
Jun 14 10:11:00 <lag> Oh, that sucks
Jun 14 10:11:07 <lag> (for him)
Jun 14 10:11:09 <apw> there is a collision due to two different chroot types, a normal one, and a union one for hard builds
Jun 14 10:11:09 <lag> :)
Jun 14 10:12:27 <lag> I'll not pretend to know a great deal about chroot architecture. I thought they were just different directories each with their own TLD in
Jun 14 10:18:49 <apw> lag, nope they arn't quite.  well they are in the normal case which you use to build, and are union mount overalys in the case of the sbuild use case
Jun 14 10:18:58 <apw> and by default they use the same names and everything breaks
Jun 14 10:19:21 <apw> i think i have it sorted out though
Jun 14 10:22:01 <lag> Good stuff
Jun 14 10:24:51 <cooloney> apw: ok, let me try again.
Jun 14 10:25:19 <apw> cooloney, not fixed yet
Jun 14 10:25:33 <apw> cooloney, i'll let you know when we are there
Jun 14 10:25:33 <lag> !Good stuff
Jun 14 10:25:34 <ubot2> Factoid 'Good stuff' not found
Jun 14 10:25:46 <apw> lag, i am waitng on a new chroot building
Jun 14 10:25:53 <cooloney> apw: no, failed again. ok, no problem.
Jun 14 10:26:09 * lag gigges - "stupid bot"
Jun 14 10:26:16 <apw> cooloney, yep i know
Jun 14 10:26:26 <apw> sbuild -d sbuild-maverick-armel PACKAGE*.dsc
Jun 14 10:26:43 <apw> cooloney, could you try again now, note the sbuild- prefix on the chroot name as above
Jun 14 10:29:01 <cooloney> apw: thanks a lot, man. it is running now
Jun 14 10:29:22 <cooloney> apw: i guess you created a new chroot named sbuild-maverick-armel?
Jun 14 10:30:15 <apw> cooloney, yes, as it needs to be a different form from the normal ones, in which changes are persistant
Jun 14 10:30:35 <apw> i've only make one on that machine and only for maverick
Jun 14 10:30:52 <apw> now i know it works i'll get with rtg to get them made across the board
Jun 14 10:31:12 <cooloney> apw: ok, very nice, thx.
Jun 14 10:31:30 <apw> cooloney, if you need a different release made let me know
Jun 14 10:33:33 <cooloney> apw: one more sbuild-lucid-armel is better.
Jun 14 10:33:50 <apw> cooloney, you need lucid yes ?
Jun 14 10:34:11 <cooloney> apw: yeah, i might use it for build ti-omap and fsl-imx51
Jun 14 10:34:24 <apw> cooloney, ok, its building now will let you know when its done
Jun 14 10:34:38 <cooloney> apw: currently, i focus on ti-omap4 for M
Jun 14 10:34:49 <apw> yp
Jun 14 10:35:00 <cooloney> apw: thanks a lot.
Jun 14 10:35:01 <apw> i suspect we'll make them all as they are pretty cheap
Jun 14 10:35:42 <cooloney> yeah, i think so, and are those schroot setup scripts in our kteam-tools?
Jun 14 10:44:03 <amitk> cooloney: lag: how are we doing on the bugs in omap support in lucid?
Jun 14 10:44:40 <amitk> can one of you take up the USB OTG bug
Jun 14 10:44:44 <amitk> ?
Jun 14 10:46:13 <lag> amitk: I am still quite tied up with a suspend-resume bug, but I can take a look for you if you like?
Jun 14 10:49:29 <amitk> lag: please do, assuming you have a beagleboard now
Jun 14 10:50:27 <lag> I do not :(
Jun 14 10:51:00 <amitk> does either mporier or cooloney have one?
Jun 14 10:51:02 <lag> Just my lonely panda - no wonder they're going extinct
Jun 14 10:51:30 <amitk> most zoos would love to get a panda :)
Jun 14 10:51:49 <lag> I couldn't tell you
Jun 14 10:55:39 <cooloney> amitk: i'd love to do that. but i don't have beagleboard and panda
Jun 14 10:55:49 <cooloney> amitk: what's the USB OTG bug?
Jun 14 10:56:02 <cooloney> i saw some fixing in 2.6.34 kernel
Jun 14 10:57:55 <amitk> cooloney: we need to find patches and fix configuration so the USB OTG works in Lucid
Jun 14 10:59:26 <cooloney> amitk: ok, any bug on LP? i do love to do that.
Jun 14 10:59:58 <lag> cooloney: That image works
Jun 14 11:00:14 <cooloney> lag: thanks for the testing.
Jun 14 11:00:35 <lag> But has a heart attack when a monitor is plugged in via HDMI
Jun 14 11:02:24 <cooloney> lag: do you think that is the first time you meet that?
Jun 14 11:02:27 <amitk> cooloney: lag: you should bookmark this page -> https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap/
Jun 14 11:02:56 <cooloney> no such thing in .33 kernel?
Jun 14 11:03:03 <cooloney> amitk: got it. thx
Jun 14 11:06:52 <lag> amit: I already have it, thanks
Jun 14 11:06:58 <lag> cooloney: bug592295
Jun 14 11:07:11 <lag> cooloney: bug 592295
Jun 14 11:07:14 <ubot2> Launchpad bug 592295 in linux-ti-omap (Ubuntu) "omapdss DISPC error: SYNC_LOST_DIGIT (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/592295
Jun 14 12:26:22 <lag> cooloney: Are you still around?
Jun 14 13:39:35 <cwillu_at_work> cwillu@lucid-zippy:~$ sudo modprobe usbhid
Jun 14 13:39:35 <cwillu_at_work> [sudo] password for cwillu:
Jun 14 13:39:35 <cwillu_at_work> [  400.146759] usbhid: unknown relocation: 3
Jun 14 13:39:35 <cwillu_at_work> FATAL: Error inserting usbhid (/lib/modules/2.6.35-rc3-dl0/kernel/drivers/hid/usbhid/usbhid.ko): Invalid module format
Jun 14 13:39:51 <cwillu_at_work> that doesn't strike me as the sort of thing that should be possible :p
Jun 14 13:47:16 <rsavoye> does anyone know the url for gcc 4.4 in Maverick for ARM ?
Jun 14 13:47:53 <rsavoye> I dug around on launchpad, but only found lp:ubuntu/gcc-4.4
Jun 14 14:02:58 <cwillu_at_work> rsavoye, http://ports.ubuntu.com/ubuntu-ports/pool/universe/g/gcc-4.4/
Jun 14 14:08:48 <rsavoye> is there a bzr branch for it ?
Jun 14 14:09:01 <cwillu_at_work> apt-get source it, it'll tell you if there is
Jun 14 14:09:06 <cwillu_at_work> but yes, probably
Jun 14 14:09:17 <rsavoye> I wanted to check the level of ARM patches
Jun 14 14:10:02 <cwillu_at_work> okay, that's a week since rcn was last on, anybody want to come with me on a rescue mission? :p
Jun 14 14:10:29 <cwillu_at_work> https://launchpad.net/ubuntu/+source/gcc-4.4
Jun 14 14:11:40 <rsavoye> that looks like it, thanks
Jun 14 14:11:41 <zumbi> rsavoye: afaik, doko uses debian svn for gcc devel, svn.debian.org -- project: gcccvs
Jun 14 14:12:14 <rsavoye> I wanted to check the code sourcery patches for ARM, which aren't in the Debian sources
Jun 14 14:12:41 <rsavoye> there are some new patches in gcc trunk for Android I was going to migrate
Jun 14 14:13:06 <zumbi> rsavoye: http://svn.debian.org/wsvn/gcccvs/branches/sid/gcc-4.5/debian/patches/#_branches_sid_gcc-4.5_debian_patches_
Jun 14 14:13:39 <rsavoye> right, but this patch I don't believe is in debian at all
Jun 14 14:13:41 <zumbi> rsavoye: where are CS patches at?
Jun 14 14:13:58 <rsavoye> got me, but I heard there was one for ARM stuff
Jun 14 14:14:24 <zumbi> well, there are tons of fixes and patches for ARM
Jun 14 14:14:43 <rsavoye> as the CS sources haves fixes for 4.4 based on 4.6
Jun 14 14:15:04 <rsavoye> not a huge big deal, I was just doing some Android toolchain hacking and thought maybe I'd check
Jun 14 14:15:26 <zumbi> they backport 4.6 development into 4.4 (probably for next release)
Jun 14 14:15:38 <rsavoye> yes
Jun 14 14:15:53 <rsavoye> maybe it's not merged in yet
Jun 14 14:15:54 <zumbi> well, g'luck!
Jun 14 14:16:29 <rsavoye> Guess I'll stick to my build of 4.5 for now.
Jun 14 14:22:59 <wocao> where is the soucelist for  arm
Jun 14 14:29:16 <cwillu_at_work> wocao, how do you mean?
Jun 14 14:29:44 <amitk> sources.list?
Jun 14 14:29:54 <amitk> sauce list?
Jun 14 14:29:55 <amitk> :)
Jun 14 14:30:02 <ogra> yum
Jun 14 14:30:09 <ogra> sauce
Jun 14 14:35:57 <wocao> sourcelist for arm platform
Jun 14 14:36:00 <wocao> ?
Jun 14 14:36:15 <wocao> where i can fine
Jun 14 14:36:17 <wocao> where i can find
Jun 14 14:37:09 <ogra> in /etc/apt/
Jun 14 14:41:50 <cwillu_at_work> wocao, deb ports.ubuntu.com/ubuntu-ports lucid main universe
Jun 14 15:09:13 * cwillu_at_work found rcn
Jun 14 15:59:22 <mpoirier_> lag: what was that ?
Jun 14 16:10:01 <lag> amitk: Ping
Jun 14 16:13:41 <lag> Ogra: Ping
Jun 14 16:19:36 <ogra__> lag, yep ?
Jun 14 16:20:00 <lag> If I'm fixing bugs for Panda, which tree should I be using?
Jun 14 16:20:14 <lag> Things seem a little scattered
Jun 14 16:20:24 <ogra> no idea, cooloney should have created one on the server
Jun 14 16:20:37 <lag> He has one for Maverick
Jun 14 16:20:42 <ogra> right
Jun 14 16:20:45 <lag> Hang on
Jun 14 16:20:54 <ogra> panda will be maverick
Jun 14 16:21:20 <lag> He has one for Maverick in his own area
Jun 14 16:21:25 <ogra> hmm
Jun 14 16:21:29 <lag> Will panda only be Maverick?
Jun 14 16:21:32 <ogra> then i dont know
Jun 14 16:21:35 <ogra> yes
Jun 14 16:21:37 <lag> I have a working Lucid kernel?
Jun 14 16:21:40 <Martyn> good morning
Jun 14 16:21:51 <ogra> lag, we wont add new kernels to lucid :)
Jun 14 16:21:55 <ogra> its released
Jun 14 16:22:17 <lag> Okay, but the Maverick one doesn't work on Panda yet?
Jun 14 16:22:19 <lag> Or does it?
Jun 14 16:22:23 <ogra> no idea
Jun 14 16:22:30 <ogra> afaik we dont have binaries yet
Jun 14 16:22:34 <Martyn> I've nearly finished the first set of ARM symbol de-dup patches.   I honestly had no idea how much work I had signed up for at UDS.  This is tough, tough work
Jun 14 16:22:37 <ogra> so i havent tested anything yet
Jun 14 16:22:49 <lag> Okay
Jun 14 16:23:04 <ogra> we got the branch on friday afaik
Jun 14 16:23:05 <lag> So I can't fix Panda bugs yet then, is that what you're saying?
Jun 14 16:23:09 <Martyn> I thought it would be easy to separate the functions out .. but it wasn't.
Jun 14 16:23:17 <Martyn> ogra : What's new?
Jun 14 16:23:41 <ogra> lag, do we do have bugs for omap4 yet ?
Jun 14 16:24:01 <ogra> since there is no package in the archive yet i doubt we do
Jun 14 16:24:13 <lag> I have filled one
Jun 14 16:24:23 <lag> But that was with the Lucid kernel!
Jun 14 16:24:34 * lag head explodes 
Jun 14 16:24:37 <lag> 's*
Jun 14 16:24:42 <ogra> which was just a build of the plain TI omap4 upstream kernel
Jun 14 16:25:01 <ogra> we dont have the actual kernel yet we will use
Jun 14 16:25:18 <lag> Okay, I guess that clears things up
Jun 14 16:25:23 <lag> Phew!
Jun 14 16:25:35 <ogra> the lucid package you use was just a quick build of what was available to get the boards up at all
Jun 14 16:25:46 <lag> Got you
Jun 14 16:26:15 <ogra> the actual kernel package we will use has to be built by cooloney first, would probably be best to ask if you can help him with that
Jun 14 16:26:26 <ogra> since thats the current blocking factor
Jun 14 16:26:45 <lag> Okay, I'll have a word with him tomorrow
Jun 14 16:27:03 <ogra> what was your bug about ?
Jun 14 16:27:05 * cwillu_at_work continues happily using his working rcn kernels :)
Jun 14 16:27:08 <ogra> clearly a kernel issue ?
Jun 14 16:27:17 <lag> HDMI
Jun 14 16:27:19 <lag> Yeah
Jun 14 16:27:39 <ogra> k
Jun 14 16:27:42 <lag> https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap/+bug/592295
Jun 14 16:27:44 <ubot2> Launchpad bug 592295 in linux-ti-omap (Ubuntu) "omapdss DISPC error: SYNC_LOST_DIGIT (affects: 1) (heat: 6)" [Undecided,New]
Jun 14 16:28:05 <cwillu_at_work> now, if only I could get firefox to stop crashing when using webworkers
Jun 14 16:28:06 <Martyn> When did the Panda board support go into the kernel?
Jun 14 16:28:19 <ogra> Martyn, not yet
Jun 14 16:29:18 <Martyn> *nod*  The only thing I've seen so far was the proposed patch by David Anders, and it missed the patch window (just like the Smooth-Stone patch missed it)
Jun 14 16:29:39 <Martyn> Both then end up on hold until 2.6.36
Jun 14 16:45:23 <tumbleweed> I'm trying to replicate http://launchpadlibrarian.net/49300098/buildlog_ubuntu-maverick-armel.hdf5_1.8.4-patch1-2_FAILEDTOBUILD.txt.gz in qemu but it keeps segfaulting at the same point in the build processes
Jun 14 16:46:03 <tumbleweed> are qemu-system-arm segfaults the norm?
Jun 14 16:56:44 <ogra> tumbleweed, depneds what kernel you use
Jun 14 16:57:37 <tumbleweed> ogra: the versatile kernel in the repos doesn't work with my qemu
Jun 14 16:58:01 <tumbleweed> so I'm using the one from http://ports.ubuntu.com/ubuntu-ports/dists/lucid/main/installer-armel/current/images/versatile/netboot/
Jun 14 16:59:03 <ogra> thats the same kernel as the archive kernel
Jun 14 16:59:26 <ogra> but thats alright then, you shouldnt see segfaults
Jun 14 17:00:12 <tumbleweed> ogra: it doesn't seem to be. md5sums don't mathc
Jun 14 17:00:32 <tumbleweed> also 2.8M vs 3M
Jun 14 17:00:43 <ogra> well, debian-installer just pulls the binary out of the package
Jun 14 17:00:51 <ogra> when it builds the netinstall kernel
Jun 14 17:01:38 <tumbleweed> with a HEAD qemu and the archive kernel: http://paste.ubuntu.com/449748/
Jun 14 17:01:52 <ogra> oh
Jun 14 17:02:00 <ogra> you should mention that you dont use the ubuntu qemu
Jun 14 17:02:16 <tumbleweed> I was getting it with ubuntu qemu first, tried git after that
Jun 14 17:02:51 <tumbleweed> actually haven't tried ubuntu qemu with the archive kernel. does that
Jun 14 17:03:12 <ogra> vmlinuz-2.6.35-2-versatile ?????
Jun 14 17:03:18 <ogra> thats not a lucid kernel
Jun 14 17:03:49 <tumbleweed> ogra: maverick
Jun 14 17:04:01 <tumbleweed> aah, right
Jun 14 17:04:04 <ogra> right, thats untested yet :)
Jun 14 17:04:31 <ogra> theoretically it should work though
Jun 14 17:05:00 <ogra> there were no changes to the versatile branch to my knowledge
Jun 14 17:05:10 <ogra> apart from newer upstream
Jun 14 17:06:02 <tumbleweed> ok. I see no bugs. I'll file one
Jun 14 17:06:17 <ogra> great, thanks
Jun 14 17:06:50 <ogra> anyway, your build log seems to have a SIGILL
Jun 14 17:07:23 <ogra> could be a toolchain issue
Jun 14 17:07:34 <tumbleweed> yeah, I saw that. Tried to replicate, and got sidetracked by this
Jun 14 17:07:35 <ogra> since it happens during linking
Jun 14 17:07:40 <tumbleweed> I tihnk it cgot past that, though
Jun 14 17:08:09 <ogra> are you using a lucid rootfs in your vm image ?
Jun 14 17:08:16 <tumbleweed> maverick
Jun 14 17:08:24 <ogra> ah
Jun 14 17:09:45 <cwillu_at_work> what's the newest firefox build available for arm?
Jun 14 17:10:08 <cwillu_at_work> i.e., does anyone have 3.7 builds?
Jun 14 17:10:33 <ogra> i dont think so
Jun 14 17:10:46 <ogra> theer was no firefox upload to maverick yet
Jun 14 17:11:00 <ogra> so the latest in the archive must be the lucid version
Jun 14 17:11:44 <cwillu_at_work> :/
Jun 14 17:11:51 <cwillu_at_work> building firefox isn't fun :*(
Jun 14 17:12:47 <ogra> i dont know if there is any PPA with dailies of trunk
Jun 14 17:12:54 <ogra> asac would know such stuff
Jun 14 17:13:36 <asac> cwillu_at_work: ogra: https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
Jun 14 17:13:42 <asac> not for armel ;)
Jun 14 17:13:52 <ogra> right, thats what i suspected
Jun 14 17:14:02 <asac> but firefox 3.7 is there ... which afaik is now branched ... so trunk might be missing temporarily
Jun 14 17:14:03 <cwillu_at_work> asac, I suppose I could apt-get source it myself :/
Jun 14 17:14:08 <asac> cwillu_at_work: yep
Jun 14 17:14:23 <asac> cwillu_at_work: is there any important reason why we should try a ffox 3.7 build?
Jun 14 17:14:34 <ogra> tahts great, you can tell us about build failures in advance then :)
Jun 14 17:14:39 <asac> if there is a good reason (like important bug fix landing for arm that needs landing), i spin that in a ppa
Jun 14 17:15:28 <cwillu_at_work> asac, I can crash a 3.6 build at will by running my app on it?
Jun 14 17:15:51 <cwillu_at_work> no idea if it's fixed yet, but it's annoying enough to duplicate that I really want it to get fixed by accident :p
Jun 14 17:16:05 <asac> cwillu_at_work: do you see that problem o intel too?
Jun 14 17:16:08 <cwillu_at_work> yep
Jun 14 17:16:13 <asac> then test it with that ppa
Jun 14 17:16:23 <ogra> and it worked on former releases i assume
Jun 14 17:16:25 <cwillu_at_work> asac, have been, so far so good
Jun 14 17:16:25 <asac> intel builds are avail there ;)
Jun 14 17:16:35 <cwillu_at_work> ogra, no, webworkers didn't exist previously
Jun 14 17:16:42 <ogra> ah
Jun 14 17:16:49 <cwillu_at_work> but they're a pretty big win performance wise in my case
Jun 14 17:16:51 <tumbleweed> ogra: gaaah. wrong terminal. ubuntu qemu boots the maverick kernel fine, sorry
Jun 14 17:16:59 <ogra> phew
Jun 14 17:17:13 * ogra wipes the sweat off his forehead 
Jun 14 17:18:49 <ogra> tumbleweed, what i would try is to build the package in the same vm inside a lucid chroot, if thta succeeds its most likely a toolchain issue
Jun 14 17:20:29 <tumbleweed> brb supper
Jun 14 17:28:12 <ojn> Martyn: I didn't see patches for either go by on arm-kernel. Where were they posted? (panda and smooth-stone support)?
Jun 14 17:31:58 <tumbleweed> ogra: when I say "boots fine" I mean it says "booting the kernel" and then hangs at 100% CPU
Jun 14 18:02:15 * gsnedders found the reason why the BeagleBoard he has wasn't working properly: the NAND is b0rked.
Jun 14 22:35:31 <cwillu_at_work> ogra, well, I seem to be stable given some code modifications on 3.6.6 from the nightlies
Jun 14 22:35:43 <cwillu_at_work> on x86
Jun 14 23:20:42 <playya_> how much space is required to bootstrap ubuntu-minimal on ARM?
**** ENDING LOGGING AT Tue Jun 15 02:59:57 2010