**** BEGIN LOGGING AT Fri Nov 19 02:59:58 2010 Nov 19 08:54:42 morning Nov 19 13:00:26 * ogra twiddles thumbs watching lightspark build Nov 19 13:05:08 gah Nov 19 13:05:11 the linker fails Nov 19 13:05:14 :( Nov 19 13:08:04 linking qt took so far 1.5GB of memory and still linking Nov 19 13:09:17 heh, but it doesnt fail for you at least Nov 19 13:09:24 * ogra curses intel centric code Nov 19 13:09:37 ogra: with 10GB of swap it should not Nov 19 13:09:39 armv7l/Debian/lib/liblightspark.so.0.4.4: undefined reference to `fastYUV420ChannelsToYUV0Buffer_SSE2Unaligned' Nov 19 13:09:39 armv7l/Debian/lib/liblightspark.so.0.4.4: undefined reference to `fastYUV420ChannelsToYUV0Buffer_SSE2Aligned' Nov 19 13:09:47 silly ! Nov 19 13:09:59 auch Nov 19 13:10:01 * hrw -> off Nov 19 13:11:17 hrw: I was only able to pass the linking part with 1gb of swap Nov 19 13:18:51 rsalveti, static no-neon change for QT re-uploaded Nov 19 13:18:57 waiting for approval Nov 19 13:19:03 (just FYI) Nov 19 13:19:08 ogra: cool, thanks Nov 19 13:20:15 We've got Pico Node running on a Beagle-xM with Ubuntu 10.10 now. :) Nov 19 13:20:26 congrats Nov 19 13:20:32 ogra: what is the package version? will push the same one with with neon on the ppa Nov 19 13:20:40 cool :-) Nov 19 13:20:41 Thanks. :) Nov 19 13:20:48 rsalveti, ubuntu4.1 again Nov 19 13:21:02 rsalveti: Once it's there, would you please point me at it, I know some people that will definitely want it. Nov 19 13:21:07 i hope it doesnt clash with anything, please wait until i have confirmation Nov 19 13:21:11 ScottK: sure Nov 19 13:21:16 Ubuntu is proving way more stable and nice than Angstrom, especially for networking. Nov 19 13:21:18 ogra: ok Nov 19 13:21:28 ogra: Since it was source accepted the version number is used. You'll have to bump it. Nov 19 13:21:44 slangasek said he removed 4.1 from proposed but i'm not sure that removes everything Nov 19 13:21:50 I also have two different wireless dongles working with Beagle and Ubuntu. :) Nov 19 13:21:57 ScottK, hmm, k Nov 19 13:24:19 * ogra hasnt seen any wireless dongles that dont work on ubuntu Nov 19 13:24:49 ogra: Cool. :) Ubuntu is very wireless friendly. :) Nov 19 13:25:02 we try our best :) Nov 19 13:25:34 I think moving to Ubuntu for Pico Node was the best choice. :) Nov 19 13:26:18 We are working on getting a 2.6.36 kernel up on it now. Nov 19 13:29:02 shouldn't be that hard, as maverick's 2.6.35 is quite similar with upstream Nov 19 13:29:22 We have a problem with an undefined symbol. Nov 19 13:29:46 rsalveti, so ubuntu4.2 it is (and uploaded, waiting for approval) Nov 19 13:30:00 ogra: ok, that will be accepted Nov 19 13:30:03 thanks Nov 19 13:31:22 When I put a beagleboard on my robot, it will have WiFi. :) Nov 19 13:33:00 you will even be able to run a unity robot with it *g* Nov 19 13:33:36 Unity robot?? Nov 19 13:34:15 My robot is W.A.L.T.E.R. Nov 19 13:40:16 Right now, I am focused on Pico Node though, and getting it completed. Nov 19 13:47:54 hmm, so it needs that for lightspark to build we need some assembler guy to re-write the SSE asm stuff for arm Nov 19 13:47:56 to bad Nov 19 13:50:26 ogra: since ubuntu uses .35 kernel I do not see such neither Nov 19 13:50:37 ogra: lucid ignored one of my wifi dongles Nov 19 13:50:47 bad dongle :P Nov 19 13:51:38 i just said i havent seen any that doesnt work ... doesnt mean that there arent any Nov 19 13:51:39 :) Nov 19 13:51:40 very good dongle ;D Nov 19 13:51:48 80211n one Nov 19 13:52:46 well, all i have and all my friends have did work :) Nov 19 13:53:32 but then i dont buy exotic HW Nov 19 13:54:10 ;) Nov 19 13:54:22 it was cheapest 802.11n usb dongle Nov 19 13:54:32 worked fine with my x86 machines Nov 19 13:57:43 * ogra goes for food Nov 19 14:56:03 hey guys if I have a kernel with built-in modules like pata and then replace it with a kernel with pata as a module how do I force initramfs-tools to include that module if it cannot detect it Nov 19 14:59:21 /etc/initramfs-tools/modules should suffice right? Nov 19 15:05:12 Neko_, it should, although initramfs.conf -> MODULES=most should take care of it to, I'd expect Nov 19 15:09:16 eureka pretty simple install maverick on beagle did the aptitude install for the full gui but then had to aptitude install for the x11vnc cannot start the x11vnc any ideas? Nov 19 15:09:18 Warning: cwillu comes with ABSOLUTELY NO WARRANTY, including warranties of merchantability and fitness for a particular purpose. Do not consume cwillu. If injested, contact a kernel developer immediately. Not suitable for children under the age of 24. May cause addiction. May cause insanity. May cause slight tingling in the fingertips when exposed to sunlight. Nov 19 15:09:22 if modules.dep is properly generated it should just be pulled in Nov 19 15:17:06 cwillu_at_work, modules=most doesn't seem to cover it and I can't work out where it gets this list Nov 19 15:21:24 modules.dep as ogra said Nov 19 15:21:52 /etc/initramfs-tools/modules should suffice, it's just nice to have things working properly Nov 19 15:22:12 (and by nice, I mean very nearly vital :p) Nov 19 15:24:56 modules.dep doesn't really tell anything to initramfs-tools though does it? Nov 19 15:25:02 like "I actually need this to boot" Nov 19 15:25:13 it will just pull in the ones the ones you list are dependent on too Nov 19 15:25:26 how would it know from modules.dep that pata_fsl is required to boot from pata Nov 19 15:25:55 that's what the "most" is for though Nov 19 15:26:49 how does it tell what to not put in Nov 19 15:27:05 is there a list of modules pointless to have in initramfs which it culls out so most != everything? Nov 19 15:28:00 dunno - I guess everything except storage and filesystem-related drivers are not useful in there Nov 19 15:28:48 You could try booting with rdinit=/bin/sh and see what modules actually end up loaded in the initramfs environment Nov 19 15:33:14 you might have toi add the module in question to hook_functions, some module sets are hardcoded in there Nov 19 15:33:28 i.e. network card drivers definitely are Nov 19 15:36:10 have a look at the auto_add_modules() function in there Nov 19 15:42:17 at which point you might just want to add the damn module to the modules file :p Nov 19 15:43:32 well, if the module sits in a proper kernel dir it will get auto copied Nov 19 15:43:51 i guess its another of these broken platform modules Nov 19 15:43:57 I'm trying to remember if pata is the deprecated one Nov 19 15:44:03 that dont live in the right kernel subdir Nov 19 15:44:25 it should live under kernel/drivers/ata Nov 19 15:44:25 i.e., isn't it unified with scsi now? Nov 19 15:44:37 then it should live in kernel/drivers/scsi Nov 19 15:44:57 or if its more generic it shoudl live in kernel/drivers/block Nov 19 15:45:19 * cwillu_at_work waits for his home machine to answer the phone Nov 19 15:45:29 using ide on that one, it'll know :p Nov 19 15:45:38 ... pick up the syn Nov 19 15:45:53 ugh, dynip fail Nov 19 15:46:28 * cwillu_at_work retries the ip from his webserver Nov 19 15:46:58 there we go Nov 19 15:47:01 oh, there is also kernel/drivers/ide :) Nov 19 15:47:09 that might be very old pata Nov 19 15:47:42 that's the one that's deprecated Nov 19 15:47:50 yep Nov 19 15:47:58 Neko_, which module are you looking for again? Nov 19 15:48:00 well, initramfs-tools cpoies it nontheless Nov 19 15:48:04 *copies Nov 19 15:48:48 Neko_, there's no "pata" module Nov 19 15:48:53 not sure there ever was Nov 19 15:49:05 just a bunch of device specific pata_*.ko Nov 19 15:49:29 pata_fsl Nov 19 15:49:43 i guess thats what he means Nov 19 15:49:43 I don't have that driver Nov 19 15:49:59 likely living ion some odd platform subdir Nov 19 15:50:18 instead of a kernel subsystem dir Nov 19 15:50:18 I checked the whole modules folder Nov 19 15:50:26 you dont have his kernel :) Nov 19 15:50:34 and I'm not looking at an arm machine Nov 19 15:50:50 (what arm machines have ide on them, that actually work with recent ubuntu?) Nov 19 15:50:57 that too, but he likely uses a special fsl kernel as usual Nov 19 15:51:07 none Nov 19 15:51:13 dove has SATA Nov 19 15:51:34 Neko_, quit using non-existing hardware Nov 19 15:51:36 we dont support FSL anymore, but i think their latest babbage boards have a plain PATA port Nov 19 15:51:52 so theye might also use pata_fsl Nov 19 15:52:04 but i cant tell, since we dont support it anymore :) Nov 19 15:52:38 (the releases of FSL babbage we supported didnt have PATA) Nov 19 16:01:49 pata_fsl is in 2.6.31-fsl tree Nov 19 16:01:57 and it is using libata Nov 19 16:02:16 well, the auestion is where the module lives Nov 19 16:02:20 *question Nov 19 16:02:30 must be a path that initramfs-tools copies Nov 19 16:02:34 else its left out Nov 19 16:02:49 ./drivers/ata/pata_fsl.o Nov 19 16:02:52 and initramfs tools only cares for proper kernel subsystem dirs Nov 19 16:03:14 kernel/drivers/ata is copied with MODULES=most Nov 19 16:09:31 okay Nov 19 16:09:46 boot with brak=premount Nov 19 16:09:46 lemme get back with steev and see if he can get some debug Nov 19 16:09:51 *break=premount Nov 19 16:10:04 that will drop you into the initramfs shell so you can inspect Nov 19 16:10:09 ok Nov 19 16:10:36 if it really lives in that dir, i would suspect it gets copied but doesnt load Nov 19 16:10:51 that is the effect we're assuming Nov 19 16:10:57 right Nov 19 16:11:11 but before we think, why doesn't it load, I wanted to make sure it wasn't just not there Nov 19 16:11:14 same thing as with your audio modules i suspect Nov 19 16:11:32 well I modularized those only yesterday otherwise they were built-in Nov 19 16:11:38 ata) Nov 19 16:11:38 copy_modules_dir kernel/drivers/ata Nov 19 16:11:38 ;; Nov 19 16:11:46 thats from hook-functions Nov 19 16:11:58 one part thats run for MODULES=most Nov 19 16:12:24 it means it recursively copies all .ko files below that dir Nov 19 16:13:58 yeah I see it I just don't "believe" it :) Nov 19 16:14:19 well, it works :) Nov 19 16:21:20 ogra: there were rumours that natty wants to get rid of initrd Nov 19 16:21:40 hrw, huh ? Nov 19 16:21:43 i doubt that Nov 19 16:21:53 since lucid you *can* boot without initrd Nov 19 16:22:04 but only if you dont use a certain set of packages Nov 19 16:22:12 hrw: hehe, you were dreaming probably ;-) Nov 19 16:22:37 i guess they might want to get rid of current initrd generation scripts Nov 19 16:22:41 I know you don't like it :-) Nov 19 16:23:07 well, initrd is supposed to be switched to upstart completely Nov 19 16:23:19 so yeah, the scripts will heavily change Nov 19 16:23:41 I just hope that natty will still allow to boot without initrd Nov 19 16:23:44 but as long as we offer dm-raid or lvm or encryption for any disk stuff, initrd will not be dropped Nov 19 16:26:42 sure, but for toys like ac100/efikasb you usually do not do that Nov 19 16:27:59 oh, and mountall Nov 19 16:28:14 fsck need mountall from initrd before the rootfs is mounted RW Nov 19 16:28:24 that would have to be changed Nov 19 16:53:58 ogra: wrt the qa testing of the daily images, I hadn't tested them because I didn't see them. They are being posted at http://cdimage.ubuntu.com/ubuntu-netbook/daily-preinstalled/current instead of http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current/ (i,e. not in /ports). My mirror scripts didn't see the change, nor did my browser. Nov 19 16:54:05 I do check daily. Nov 19 16:54:59 have a nice weekend Nov 19 16:55:19 GrueMaster, hmm, that might be due to persia's quest of letting ports die Nov 19 16:55:41 http://cdimage.ubuntu.com/ubuntu-netbook/daily-preinstalled/current/ has the right images though Nov 19 16:55:59 Ah. Well, if this is permanent, I'll need to update my mirror scripts. Nov 19 16:56:17 no idea if thats permanent or even how they got there Nov 19 16:56:20 Nice for people to tell me. Nov 19 16:56:24 hrmm. Nov 19 16:56:31 but i'd suspect its due to some cdimage reorganization Nov 19 16:56:40 there was a BOF for it at UDS Nov 19 16:56:43 Also, only omap4 images. Nov 19 16:56:54 Yea, I kind of missed UDS. Nov 19 16:56:55 yes Nov 19 16:57:07 the schedule was online :P Nov 19 16:57:16 we dont have omap3 kernels yet Nov 19 16:57:22 so no omap3 images either Nov 19 16:57:22 ok Nov 19 16:57:30 and i dont expect them before A2 Nov 19 16:57:40 Yeah, but I failed to publish the announcement about the change. I'll get that done in the next 48 hours (have to fix a couple scripts along the way) Nov 19 16:57:48 What's the hold up? Ubuntu vs Linaro kernel? Nov 19 16:58:01 GrueMaster, right, see the ML discussion Nov 19 16:58:16 waiting for a statement from kernel and security teams Nov 19 16:58:48 if it is clear we dont get any support we will build omap3 but only as unofficial images Nov 19 16:59:56 That shouldn't stop us from building dailies for testing. They're unsupported anyways. Nov 19 17:00:07 The rest is paperwork. Nov 19 17:00:30 we dont have a kernel Nov 19 17:00:43 i cant build images without one :P Nov 19 17:00:52 Can't use the existing maverick kernel? Nov 19 17:00:59 its gone Nov 19 17:01:50 The documentation for adding kernels is supposed to be published before Alpha-1, but there may not be time to actually use that documentation before then to make a kernel. Nov 19 17:01:50 Huh? How so? It is a release package in main. It shouldn't be gone. Nov 19 17:02:31 GrueMaster, The "linux" source package no longer provides that binary package. It's not uncommon for the set of binary packages to change between releases. Oh, and "main" doesn't mean anything :) Nov 19 17:02:35 it is built from linux Nov 19 17:02:43 linux doesnt build that flavour in natty Nov 19 17:02:59 we need to move the linaro kernel to main Nov 19 17:03:11 which i wont do until the discussion has settled Nov 19 17:03:31 Ok, I (kind of) get it. Nov 19 17:04:11 building with universe kernel will put a lot of extra work on us which i'd like to justify first Nov 19 17:04:34 i.e. by security and kernel team refusing to take the support Nov 19 17:04:35 Why? It's a two-line change, and if care is taken with the seeds, doesn't otherwise affect the image. Nov 19 17:05:15 Should be independent of who offers to maintain the kernel. Nov 19 17:05:25 (or the timing of that offer) Nov 19 17:06:31 heh Nov 19 17:06:31 two line change ? Nov 19 17:06:46 we need a universe mirror on antimony for that Nov 19 17:06:52 and way more than two lines Nov 19 17:07:19 Isn't that already present for building Xubuntu Desktop, Ubuntu Studio, and Mythbuntu? Nov 19 17:07:28 not that i know of Nov 19 17:07:52 How do those get built then? I thought it was the same infrastructure. Nov 19 17:07:53 in any case i wont bother for omap3 until thats sorted Nov 19 17:07:53 We don't currently build those for arm. They may exist for other arch's. Nov 19 17:08:37 But I do agree that we shouldn't hold up test image builds for paperwork that can get sorted over time. Nov 19 17:09:30 Which one is antimony again? I thought that was separate from the livefs builders. **** ENDING LOGGING AT Sat Nov 20 02:59:57 2010