**** BEGIN LOGGING AT Thu Feb 03 02:59:57 2011 Feb 03 04:45:39 have a docs bug Feb 03 04:46:00 this page -> https://wiki.ubuntu.com/ARM/OMAPMaverickInstall Feb 03 04:46:19 On Beagleboard xM rev A3 and B, the wgets are to the wrong directories Feb 03 04:46:26 they're right, but reversed Feb 03 05:10:42 straszheim, Would you mind correcting that? Feb 03 05:14:49 np Feb 03 05:17:22 Thanks! Feb 03 05:28:43 after a solid week of trying to get things built for a gumstix I have to say that install was pretty awesome. Feb 03 05:30:44 I heard of someone running on a gumstix before. Did you have to do anything special to the image, or did it mostly just work? Feb 03 05:31:41 ah, no, i mean the omap3/maverick install was awesome because it worked and took a few hours. gumstix is unplugged, major fail Feb 03 05:32:20 Which gumstix do you have? Feb 03 05:32:32 verdex pro Feb 03 05:32:49 armv5te iirrc Feb 03 05:33:17 Indeed. Debian ought be not too hard to get running on that. Feb 03 05:34:15 I think the omap3 images work on the Overos, but I haven't seen enough confirmation to be sure: none of the regulars on this channel seems to use one with Ubuntu. Feb 03 05:38:33 is there a recommended way to strip the gui stuff out of this install? This thing is intended to run headless. I'm considering just removing x11-common. Feb 03 05:38:49 that'll take a ton of stuff with it Feb 03 05:41:07 check out tasksel Feb 03 05:41:24 ah nice Feb 03 05:41:25 thx Feb 03 05:42:11 I'd recommend making sure ubuntu-standard and ubuntu-minimal are installed, and then removing ubuntu-netbook and all it's dependencies (avoiding removing -standard and -minimal) Feb 03 05:42:17 From there you can build up again. Feb 03 05:43:29 sounds good **** ENDING LOGGING AT Thu Feb 03 08:26:14 2011 **** BEGIN LOGGING AT Thu Feb 03 08:30:17 2011 Feb 03 09:15:08 straszheim: I'm reverting your change Feb 03 09:15:30 the first sd card partition should have the uImage, not vmlinuz Feb 03 14:45:35 http://projects.goldelico.com/p/ombeagle/ Feb 03 14:56:56 ogra: cool! Feb 03 14:57:11 yep Feb 03 14:57:18 waiting for the panda version :) Feb 03 15:11:29 rsalveti, wrt https://blueprints.launchpad.net/ubuntu/+spec/other-arm-n-handle-core-boot-files-update Feb 03 15:11:50 is that tool suipposed to do what flash-kernel currently does but for uboot binaries ? Feb 03 15:11:51 janimo: moving it for you Feb 03 15:11:57 kind of Feb 03 15:12:10 because u-boot and x-loader is not updated Feb 03 15:12:13 just the kernel Feb 03 15:12:26 * janimo wonders if code can be reused from flash-kernel at all Feb 03 15:13:49 janimo: yup, that's why you need to talk with NCommander later, to check the flash kernel and the sub arch detect code Feb 03 15:13:54 to see what can be shared Feb 03 15:14:06 ok Feb 03 15:19:30 rsalveti, we should just seed them and make sure they are on the image worst case ... then people can at least manually update Feb 03 15:20:13 ogra: but the idea is to have a tool to manually update the core boot files Feb 03 15:20:17 shouldn't be that hard Feb 03 15:20:21 indeed Feb 03 15:20:37 but if we dont manage, seeding should at least get us a step forward Feb 03 15:20:56 yup, true Feb 03 15:54:40 ogra, seeding all? For instance for omap3 image seed all the omap3 based xloader/uboot binaries? Feb 03 15:55:43 janimo, well, we cant be that distinctive in the seeds (seeds dont support subarches) Feb 03 15:55:51 so we would need to seed all Feb 03 15:56:17 ok Feb 03 15:56:25 the point is that apt-get update will get you the latest binaries on disk Feb 03 15:56:44 so even without the desired script we would have them available for manual tinkering Feb 03 15:56:50 I am thinking having them on the disk and then adding a post install hook like flash-kernel would solve this Feb 03 15:56:58 right Feb 03 15:57:04 that was the initial plan Feb 03 15:57:20 but if we dont have time for the flash-kernel bit, at least seeding should be done Feb 03 15:57:59 janimo: we don't want a post install hook Feb 03 15:58:04 we want the user to manually update the files Feb 03 15:58:07 avoid problems Feb 03 15:58:09 right Feb 03 15:58:14 and a lot easier to implement Feb 03 15:58:17 just a script Feb 03 16:02:47 rsalveti, so not the same ease and transparency s grub is installed with? Feb 03 16:02:52 ok Feb 03 16:03:08 yeah, we want a script that the user can trigger by hand Feb 03 16:03:12 or rather ease, but not automatic Feb 03 16:03:16 and we also want to notify the user about such update Feb 03 16:03:18 ack Feb 03 16:03:20 we dont update grub stage 1 Feb 03 16:03:27 there is no such ease ;) Feb 03 16:23:17 rsalveti: Hey, would you know whether USB storage is fully stable on xm now? Feb 03 16:23:33 lool, given that the buildds use it ... Feb 03 16:23:39 We use xms as buildds now? Feb 03 16:23:49 you should know it :) Feb 03 16:23:55 they come from linaro afaik Feb 03 16:24:16 see https://launchpad.net/builders Feb 03 16:24:41 ogra: how do I know they are xms? Feb 03 16:24:49 lamont Feb 03 16:24:58 Ok, so https://launchpad.net/builders doesn't help much I guess Feb 03 16:25:05 the arm team helped him to bring them up Feb 03 16:25:17 well, it shows that there are 15 instead of 8 now Feb 03 16:25:25 indeed it doesnt show the arch Feb 03 16:26:02 The *ceae systems are the new ones. Feb 03 16:26:15 right Feb 03 16:26:24 i was just looking for the naming convention Feb 03 16:26:30 had noted it somewhere Feb 03 16:27:46 ogra: lool: I didn't know the builders moved to XM! Feb 03 16:27:57 ndec, on *the builders* Feb 03 16:28:03 s/on/not Feb 03 16:28:29 Well /builders is confusing Feb 03 16:28:29 ndec, linaro added 6 XM builders to the queue so their rebuilds dont impact the distro Feb 03 16:28:42 ogra: they are shared though, right? Feb 03 16:28:50 ndec, we are still waiting for the panda cluster Feb 03 16:28:53 lool, yep Feb 03 16:28:58 lool: i was about that too. Feb 03 16:28:59 ndec: we have two types of buildds Feb 03 16:29:03 lool, but can be used dedicated as i understood Feb 03 16:29:08 ndec: some for packages and some for images Feb 03 16:29:15 we can actually share them, but we usually don't Feb 03 16:29:36 and offspring/linaro don't use these for image builds, but another separate pool -- let's call them offspring builders Feb 03 16:29:39 lool, so during archive rebuild tests they wont be shared Feb 03 16:29:41 lool: ok, and the one for the packages are split between archive and PPA? Feb 03 16:29:47 ndec: Yes Feb 03 16:29:59 ndec: That's only on ARM because these are non-virtual Feb 03 16:30:04 on other arches, they are actually separate Feb 03 16:30:20 ndec, though your PPA builders are the two at the very bottom of the /builders page Feb 03 16:30:36 they are not in the normal builder pool Feb 03 16:30:39 Actually, there are two dedicated ppa buildds, according to the link above. Feb 03 16:30:40 ogra: did they moved to XM too? Feb 03 16:30:45 ndec, nope Feb 03 16:31:12 wait, nevermind. Feb 03 16:31:25 eyes are blurry. need more coffee. Feb 03 16:32:42 GrueMaster, the two are for private PPAs Feb 03 16:33:52 Ah, there they are, at the bottom. I had sorted by arch and thought I saw two, but then they disappeared. Thought my eyes were bugging out. Feb 03 16:35:01 heh Feb 03 16:37:30 ndec, they will likely move to pandas once we have them Feb 03 17:01:57 ndec: Sorry, I was confused, we're using separate PPA builders nowadays it seems Feb 03 17:04:01 lool, depends on the PPA Feb 03 17:04:51 ogra: How so? Feb 03 17:05:11 see PM Feb 03 17:27:40 lool: it should be, the only issue atm is that the driver is allocating a lot of memory when you stress the ethernet or usb Feb 03 17:27:57 and some times you can see the traces, but not something that breaks Feb 03 17:28:19 same problem we have with panda, as it's the same driver Feb 03 17:28:32 Ok thanks Feb 03 17:29:44 lool: but I'd say beagle in general is a lot more stable than panda Feb 03 17:29:58 and I think we didn't face any major issues with the builders Feb 03 17:33:43 I'm impressed by the amount of bug reports for unity-2d since it was released Feb 03 17:33:49 seems people are really using it Feb 03 17:56:30 ogra: hey there, another question on historic qemu packaging. You have another sysctl here for 'vm.vdso_enabled = 0' with the reason "else chroot execution fails" - how did it fail, how can I verify if this is still needed? Feb 03 17:57:02 slangasek, hmm, did i actually add that ? Feb 03 17:57:24 ogra: in karmic, yes Feb 03 17:57:52 hmm, i think i had that from the maemo ML somewhere Feb 03 17:57:56 let me dig Feb 03 17:58:50 ogra: thanks Feb 03 18:00:02 http://maemo.org/development/sdks/maemo5_alpha_installation/#sboxissue Feb 03 18:00:05 http://bugs.maemo.org/show_bug.cgi?id=3479 Feb 03 18:00:09 bugs.maemo.org bug 3479 in SDK "SDK does not work on Debian lenny system" [Major,Resolved: fixed] Feb 03 18:00:11 might not be needed anymore Feb 03 18:01:34 since it refers to intrepid Feb 03 18:04:51 slangasek, ^^^ Feb 03 18:05:31 ogra: so is this specific to scratchbox in some way? Feb 03 18:06:19 i had the same error in rootstock/qemu back then, else i wouldnt have added it Feb 03 18:06:27 ok Feb 03 18:06:34 i would suggest a test on amd64 Feb 03 18:06:49 i'm not sure its still valid Feb 03 18:07:08 well, testing how? Feb 03 18:07:20 and on amd64 we don't set this at all, the key doesn't exist in /proc/sys on amd64 Feb 03 18:07:25 seems related to the glibc in side the VM Feb 03 18:07:35 VM? Feb 03 18:07:44 should be a chroot not a VM, yes? Feb 03 18:07:56 err, yes, sorry Feb 03 18:09:24 the bug seems to also rather suggest to set it to 2 instead of 0 Feb 03 18:09:36 looking at the last comment Feb 03 18:10:27 i would actually drop it and look out for related bugs Feb 03 18:10:34 its natty after all ;) **** ENDING LOGGING AT Fri Feb 04 02:59:57 2011