[00:00] <sveinse> Yes, I see that, though difficult at times. Like having a large, fast, buildserver which is useless in a armel farm
[00:01] <sveinse> But, back to another qemu issue:
[00:02] <sveinse> qemu crashes (consistenly on this machine) while compuing SSH2 keys
[00:02] <persia> With lots of output or almost no output?
[00:03] <sveinse> "Creating SSH2 RSA key; this may take some time ...qemu: uncaught target signal 11 (Segmentation fault) - core dumped
[00:03] <sveinse> Segmentation fault"
[00:03] <sveinse> dpkg: error processing openssh-server (--configure):
[00:03] <persia> Get a stack trace (you can see what was being called from /var/lib/dpkg/info/openssh-server.postinst )
[00:04] <sveinse> I need to modify the rootstock (in order for it not delete the rootfs when failing) to inspect deeper
[00:04] <persia> If the crash is in ssh-keygen, then it probably needs fixing, but I doubt this is the case.
[00:04] <persia> More likely the crash is in the kernel, in which case it's qemu not handling something in the ideal manner.
[00:05] <sveinse> FYI I see some chatter on google about uncaught target signal 11 against armel
[00:05] <persia> That, or step through it more slowly, perhaps using qemu-debootstrap
[00:05] <sveinse> so it's not restricted to ubuntu or rootstock
[00:06] <persia> signal 11 just means "Segmentation Fault".
[00:06] <sveinse> aha
[00:06] <persia> If qemu was catching segfaults, we'd all be complaining about that because it would make it hard to debug things :)
[00:07] <persia> So, quick process to reproduce:
[00:07] <persia> 1) make a directory
[00:07] <persia> 2) populate a cross-chroot in that directory with qemu-debootstrap
[00:07] <persia> 3) chroot into the populated chroot
[00:07] <persia> 4) apt-get install openssh-server
[00:08] <persia> 5) After failure, inspect the postinst
[00:08] <persia> 6) Install your favorite debugging tools, and find the crash.
[00:10] <sveinse> you need apt-get in there as well, dont you?
[00:10] <persia> Hrm.  qemu-debootstrap lacks a manpage: it takes all the same arguments (with the same meanings) as debootstrap, so just use --arch=armel and otherwise follow the debootstrap model
[00:10] <persia> apt-get where?
[00:11] <sveinse> If you do 3)  apt-get need to be inside the chroot to do 4) right? Or have I misunderstood?
[00:11] <sveinse> baaah
[00:11] <sveinse> forget it
[00:11] <persia> Ah good.  I was getting very confused :)
[00:11] <sveinse> my bad, sorry
[00:11] <persia> No worries.
[00:15] <sveinse> Is there a way to create a rootfs where everything is downloaded, but not configured, and then later when the real target executes, let it do all the postinst steps?
[00:16] <sveinse> Rootstock at least fires up qemu to run the installer (or post installer, not sure on its specific task)
[00:18] <persia> Sure.  You can separate --first-stage and --second-stage in debootstrap.
[00:18] <persia> Take a look at the qemu-debootstrap code for a simple walkthrough of how one does this with qemu.
[00:19] <persia> Replicating that with hardware ought be relatively easy.
[00:19] <persia> Mind you, it's not necessarily safe to install lots of other stuff before running --second-stage, as the base system isn't configured yet.
[00:20] <sveinse> I see debootstrap retrieves, extracts, unpacks, configures. It seems to be the unpacking a later is done emulated. Am I right?
[00:20] <sveinse> *The unpacking stage and the preceeding steps are done emulated.  (it's getting late)
[00:21] <sveinse> I'll check qemu-debootstrap in all cases, thanks
[00:21] <persia> I'm not finding the source you're quoting.
[00:22] <persia> But debootstrap pulls the base system in a way that doesn't much care about dependencies, so it kinda handy to get a base.
[00:22] <persia> It does all of retrieval, extraction, unpacking, and configuration.  Based on the arguments, it can perform subsets of these actions.
[00:23] <persia> unpacking is safe to do on a foreign system: it's just unrolling tarballs.  configuration is *not* safe to do on a foreign system.
[00:23] <sveinse> Oh? How come?
[00:24] <sveinse> foreign being the target system which shall run ubuntu in the end?
[00:24] <persia> Because configuration scripts can run arbitrary binaries to accompish their goals.  Running these in a chroot with a foreign architecture will not work.
[00:24] <persia> Mind you, if you do things like the qemu-static binfmt trick, it's not really that foreign anymore
[00:25] <persia> (although qemu support isn't quite up to full hardware)
[00:25] <sveinse> And you could have binfmt back to intel on the armel (if such exits) to bridge the oposite gap?
[00:25] <persia> "foreign" meaning that the ISA for the code doesn't match the ISA for the machine on which the chroot is construted.
[00:26] <persia> It does exist.  it's supported by qemu-debootstrap.  It's so incredibly buggy that nobody should ever use it.
[00:27] <persia> the main issue is that qemu guest support for ia32 isn't well tested on armel hosts, and there don't seem to be any engineers wanting to try to fix discovered issues.
[00:27] <sveinse> And foreign is defined by the machine running qemu-debootstrap
[00:27] <persia> Sorta.
[00:27] <persia> A chroot is "foreign" if the instruction set in the chroot is not supported by the host.
[00:28] <persia> So an i386 chroot on an amd64 host is not foreign, but an amd64 chroot on an i386 host is foreign.
[00:28] <persia> armel chroots are foreign on everything not armel
[00:28] <sveinse> Since the configure step needs to be done "native" then you're basically tied to use all of debootstrap to make an image
[00:29] <persia> (although it may be that in the future armel chroots will not be foreign for armhf hosts)
[00:29] <persia> Well, you can reimplement debootstrap, but every image building tool I know starts with debootstrap.
[00:30] <sveinse> I'm trying to figure out why rootstock is considered "not for production" while debootstrap seems to be
[00:30] <persia> I'm not entirely comfortable with the passive voice in that sentence :)
[00:31] <persia> I don't consider rootstock suitable for production for three reasons:
[00:31] <sveinse> no offence, I'm truly curious. And since we're going to use ubuntu, I should know
[00:31] <persia> 1) It uses qemu-static binfmt hacks, such that the resulting image a) has extra files and b) is subject to any bug in qemu
[00:33] <persia> 2) It doesn't use the typical d-i based scripts for initial system configuration, which in practice may mean nothing more than a potential for bitrot, but may also be incomplete
[00:34] <persia> Hrm.  I remembered there being three, but the third one escapes me now
[00:35] <persia> Most likely, it was solved (since a lot of the issues passing through my head have corresponding memories of someone telling me they fixed it)
[00:35] <sveinse> I'll give you 3) openssh keygen & installation works fine on qemu-debootstrap, but fails on rootstock
[00:36] <sveinse> I've tried twice now
[00:37] <sveinse> OK, I've surely got a lot of very useful info here
[00:37] <persia> Heh.  Then 3) it's buggy :)
[00:37] <sveinse> :D
[00:37] <sveinse> I'm very grateful for the conversation!
[00:37] <persia> Aha!  rootstock still assumes versatile as an emulation host.
[00:39] <persia> (and apparently hardcodes a lucid kernel)
[00:39] <sveinse> Why should either affect qemu in respect of SSH keygen...
[00:40] <sveinse> rootstock is running a full VM, while deboostrap is only running chroot/binfmt?
[00:40] <persia> I believe that Ubuntu is currently shipping Linaro's QEMU, which I thought was no longer targeting versatile as primary.
[00:41] <persia> Rootstock works in three stages
[00:42] <persia> 1) debootstrap to populate a chroot
[00:42] <persia> 2) debootstrap under qemu-static to configure the chroot
[00:42] <persia> 3) fully-emulated environment to install random stuff
[00:43] <persia> Mind you, I'm not that familiar with the code, but that's how it appears to me from a quick look.
[00:43] <sveinse> sounds like I should move away from rootstock and integrate debootstrap instead
[00:43] <persia> debootstrap itself doesn't do anything architecture related.
[00:43] <persia> qemu-debootstrap (also not something I'd use for production) does the chroot/binfmt stuff.
[00:44]  * persia has fairly strong feelings about doing things natively, if this isn't already obvious
[00:44] <sveinse> I understand that
[00:45] <sveinse> What's the most powerful armel machine available? Because that is what you need to do such things natively, IMHO
[00:46] <GrueMaster> Available?  Possibly TI omap4 panda or nVidia Tegra.
[00:46] <persia> All the hardware I've used it IO-bound.
[00:46] <sveinse> Doing debootstrap on armel for armel is ok, right
[00:46] <persia> Find something (anything) with non-USB SATA, or other reasonable IO path, and you'll win.
[00:47] <persia> Even an OMAP3 should keep up.
[00:47] <GrueMaster> For I/O, Marvell is the best, but not available to the general public afaik.
[00:47] <persia> Native debootstrap is the basis for all official images.
[00:47] <GrueMaster> Is this just for image builds or for package compiling?
[00:47] <persia> I'm certainly happy with my Marvell IO performance, but it's not ARMv7a, so can't run native debootstrap for Ubuntu.
[00:48] <persia> Image builds.
[00:48]  * GrueMaster too lazy/busy to read backscroll.
[00:48] <GrueMaster> Ah.
[00:48] <persia> Backscroll summary: rootstrap is buggy and was being used on a high-speed build server for production images.
[00:48] <sveinse> An dual core ARMv7a with SATA is what I want I think
[00:48] <sveinse> hahahah
[00:49] <persia> sveinse, If you can find such a beast, then yes, that's precisely what you want.
[00:49] <GrueMaster> Well, for cost/speed, definately omap3/4 based atm.  Although the imx51 isn't bad in the Efika nettop.
[00:49] <GrueMaster> rootstock?  ouch.
[00:49] <persia> Just be sure to check the internal wiring: some devices claim SATA but really just have a USB<->SATA bridge, and you could do that yourself.
[00:49] <sveinse> persia, You work at reuters or something? That's the most compact summary I've ever read
[00:49] <persia> sveinse, I haven't worked with reuters is well over a decade, but thanks :)
[00:49] <GrueMaster> The efika is true sata.  Freescale fixed it post babbage3.
[00:50] <persia> GrueMaster, Really?  Nice!
[00:50] <GrueMaster> But only Cortex A8 (single core).
[00:50] <persia> debootstrap is single-threaded anyway.
[00:50] <GrueMaster> That's what I was told at UDS.
[00:51] <GrueMaster> Yea, but having one core focus on one thing while the other core handles normal tasks does provide some improvement.
[00:51] <persia> I heard the mx51 Efika's were currently at reduced prices, to clear inventory for the mx53s, so if single-core is enough, now is probably a good time.
[00:51] <GrueMaster> $125 for the nettop.
[00:51] <persia> Ah, you mean like handling the IO requests.  Heh.  Yeah.
[00:51] <persia> Yep.  That's about half what they were.
[00:51] <sveinse> I thought I heard a rumor about a armel server blade (for energy efficiency). I have no idea from where, though
[00:52] <GrueMaster> I've heard of that too.
[00:52] <persia> sveinse, I've been hearing all sorts of rumors like that for the past couple years, often from folk who really ought to know.  I have yet to see any retail products like that which support ARMv7a
[00:53] <persia> (retail servers with ARMv5te are plentiful though)
[00:53] <GrueMaster> https://www.genesi-usa.com/store/
[00:53] <GrueMaster> Oops.  $129.  My bad.
[00:53] <sveinse> That's like USB OTG. Have you guys ever seen a product with USB UTG? Which /uses/ the OTG part?
[00:54] <persia> Yes.
[00:54] <GrueMaster> UTG?
[00:54] <sveinse> sorry, typo
[00:54] <sveinse> its 2am here soon
[00:54] <GrueMaster> Ah.
[00:54] <GrueMaster> Time for more coffee.  :P
[00:55] <sveinse> Point is OTG is well defined by the USB standards, but it's very hard to come by any product and/or cables that are wired correctly
[00:55] <persia> You're not shopping in the right places :)  Cables are plentiful in some shops.
[00:55] <sveinse> It seems the industry and the standards dont line up on it
[00:56] <persia> The main issue is really that it's hard to figure out what it ought do.
[00:56] <sveinse> The product we're taking forward does include OTG. But all cables I've had in my hands are not correct
[00:56] <GrueMaster> I have found a few OTG cables that do work.  mini to usb host.  I've had a keyboard plugged into my beagle that way and it worked fine.
[00:57] <persia> In the limited context of using OTG on an Ubuntu system, the main issue is figuring out how to provide access to a useful filesystem when in gadget mode.
[00:57] <sveinse> Mini USB seems to be better supported, but micro is not
[00:57] <GrueMaster> Gadget mode is an entirely different thing.
[00:57] <persia> There's some micro cables around, but yeah, they're lots harder to get.
[00:57] <GrueMaster> I also found a micro to mini adapter.  Just got it Saturday, but haven't teted it yet.
[00:58] <cipher> are you using the beagle xM?
[00:59] <GrueMaster> I have one, yes.
[00:59] <persia> sveinse, Do you *need* to be micro, or would mini work?
[00:59] <sveinse> Too late in the design of the product. The tools for the enclosure are being built now
[01:00] <persia> Oh well.  Maybe find some online source of cables and point customers there.
[01:00] <sveinse> But mini are deprecated by USB, that's what puzzles me
[01:01] <persia> It is?  That's annoying.  I have *lots* of mini cables and ports around.
[01:01] <GrueMaster> True.  They are taller than micro, and the EU wanted a standard deployed across all cell phone markets.
[01:01] <GrueMaster> That's why the sudden conversion to micro.
[01:02] <sveinse> http://www.penguin.cz/~utx/hardware/USB_Mini/
[01:02] <GrueMaster> Gadget cables are plentiful.  It is the Host cables that are hard to find.
[01:03] <sveinse> Host cables being usbmicro to USB B (square) or USB A female receptacle?
[01:03] <persia> Right.
[01:04]  * sveinse want 10k cables of usbmicro to USB A female receptacle
[01:04] <GrueMaster> Would you like fries with that?  :P
[01:04] <persia> That quantity ought make it easier.
[01:06] <GrueMaster> Hmmm.  Just looked closely at my micro<>mini adapter.  It is for plugging a micro cable into a mini device, not the other way.  Useless.
[01:06] <rsalveti> sveinse: persia: rootstock uses qemu and debootstrap
[01:06] <rsalveti> but it copies the qemu-arm-static before doing the second phase of debootstrap
[01:06] <rsalveti> it can also run inside a full vm
[01:07] <rsalveti> and that's why it's using vexpress kernel
[01:07] <sveinse> yup. I just hoped finding it off the shelf somewhere. Yet the 5 cable samples I've tested all wires the ID pin incorrectly, so it's not trivial
[01:07] <rsalveti> but if you run with root, it just uses user mode emulation
[01:07] <sveinse> Which for some reason is crashing while computing ssh host keys
[01:07] <rsalveti> and the reason why rootstock is not suitable for production is that it's not the official tool to generate images
[01:08] <rsalveti> and not doing all the specific hacks used by live-rootfs to create the rootfs
[01:08] <persia> rsalveti, Do you think it ought migrate to use the omap3 kernel?
[01:08] <rsalveti> it creates the user with it's own way, and set the images using it's on setup
[01:09] <sveinse> I have two things when I start: A debian repo and a list of packages. They are to be installed into a image which shall be put into an sdcard in production.
[01:10] <sveinse> And if qemu-bootstrap is also dodgy because of qemu, then the only solution is to let an armel machine build the image for production
[01:10] <rsalveti> persia: last time I checked omap3 support you needed to create a whole bin image
[01:10] <rsalveti> with x-loader/u-boot and stuff
[01:11] <rsalveti> the only real problem with versatile is the ram restriction
[01:11] <rsalveti> besides that it works better with qemu
[01:11] <persia> Oh.  I thought the kernel team dropped versatile because omap3 support had improved enough to make it more suitable with qemu.
[01:12] <rsalveti> persia: well, it's hard to push omap 3 specific patches upstream
[01:12] <rsalveti> because upstream wants to emulate it exactly as the hardware should behave
[01:12] <persia> How far do we have to push?  I thought Ubuntu was shipping a special linaro-patched qemu
[01:12] <rsalveti> and versatile is kind of a virtual machine for qemu, no one actually check if the kernel really works with real hardware
[01:13] <rsalveti> yes, but last time I checked it was still missing some bits, would be nice to check it again
[01:13] <sveinse> rsalveti: My rootstock crashes when install openssh-server. It did not prior to it being upgraded from maverick to natty. Nor does my desktop machine (amd64) crash it.
[01:13] <persia> Some people have real versatile hardware, but not many, and it'&s known that the real hardware *can't* run Ubuntu (not ARMv7a compliant)
[01:13] <rsalveti> sveinse: unfortunately I'd recommend you to run natively on an ARM board if you want a stable tool
[01:13] <rsalveti> rootstock supports running on arm currently
[01:14] <rsalveti> versatile express should be fine
[01:15] <rsalveti> don't know how well that's support in qemu
[01:15] <persia> sveinse, What's your timeframe for getting the SD images complete?  If it's in July sometime, we should have clear instructions available for you beforehand.  If it's sooner, you may have some muddling to do.  (And no, you don't need to tell me the answer, just apply your answer to my comments)
[01:15] <sveinse> rsalveti: interestingly, this is the first time since the start of our project that it has crashed. It has been faithful since like nov -10. Daily builds, 10-20 builds per day
[01:15] <rsalveti> sveinse: this could be easy to fix, but then you'll end up having issues with mono
[01:15] <sveinse> Sure, we're still in development, so I can wait
[01:16] <persia> Hrm.  My usb micro host cables were from Green House Japan, but they don't seem to be offering any now.
[01:16] <rsalveti> if you don't use mono, or not plan to use, then rootstock should work in most of the cases
[01:16] <persia> It's not just mono: it's gotten buggier again because fewer folk are heavily using the qemu-static stuff.
[01:16] <sveinse> no mono, just this little regression :)
[01:17] <rsalveti> sveinse: do you have any specific change at your rootstock?
[01:17] <persia> And there's something else wonky: the openssh-server case works with qemu-debootstrap and not with rootstrap, which implies something rootstrap-specific as a bug.
[01:17] <rsalveti> sveinse: if not, can you paste me the logs? or cmd arguments you're using?
[01:18] <persia> s/rootstrap/rootstock/
[01:18] <sveinse> sure, hold on (takes a while)
[01:23] <sveinse> persia, does this mean you are working on docs for bootstrapping or a tool? (Since referring to july)
[01:25] <persia> sveinse, Yes.  Clear documentation of the Ubuntu image building infrastructure is something that's supposed to happen soon.
[01:25] <sveinse> excellent
[01:25] <persia> Presumably you could use this for your purposes.
[01:25] <sveinse> Seems so.
[01:25] <persia> Note that we're *not* attempting to generate documentation for full factory-automated installation at this point.
[01:26] <sveinse> No, I wouldn't expect that, nor demand such a thing
[01:26] <persia> I'd like it if we could provide that, but it's a hard problem still.
[01:27] <sveinse> And there are many holes to fall into I've noticed.
[01:27] <persia> I believe there's some work in progress to handle recovery partition creation, and presumably that could also be used to generate recovery media.
[01:27] <sveinse> E.g. rootstock as discussed. Previously (well haven't resolved it yet), the missing --sysroot from ubuntu/linary armel gcc
[01:28] <persia> But multicast distribution in a production environment is still several steps away (mostly because very few hobbyists have the infrastructure to test such things, and most people who build them like to sell their solutions)
[01:29] <sveinse> Our strategy is to make an sd-image which is duplicated across all units. And then we run a firstboot to make the units unique based on information from other sources
[01:30] <persia> I'd strongly recommend using oem-config as that "firstboot".  If it doesn't work for you, let's fix that, rather than have lots of implementations.
[01:30] <sveinse> Thanks, I'll look into it
[01:31] <persia> oem-config basically wraps d-i components for personalisation of a preconfigured system.  Does stuff like handle user creation, hostname assignment, timezone & locale information, etc.
[01:31] <sveinse> nice
[01:32] <persia> Since you're installing openssh-server, you may also be interested in looking at vm-builder: I'm not sure if all the work done there to ensure post-boot systems has migrated into oem-config, but you will want to have that set of hacks as well (stuff like regenerating SSH keys on first boot, etc.)
[01:33] <sveinse> openssh-server is a development tool for now
[01:33] <persia> Heh, OK.  If you're doing something like a desktop, handheld, phone, etc. then oem-config should have all the right bits already included.
[01:33] <persia> If you're doing a server, then I'm not sure it's as ready.
[01:34] <sveinse> while I'm at it: Our guys are reporting stability problems between Qt (QWS) and Natty. Is this something which is familiar?
[01:34] <sveinse> I haven't had time to dig into the issue, so I don't know first hand
[01:35] <persia> I've had a few things crash on my Kubuntu netbook, but most stuff seems to work.
[01:35] <persia> (that being natty/armel)
[01:35] <persia> The key thing is to report the bugs: if you can make something crash, it ought be fixed.
[01:36] <sveinse> Perhaps I should diff the qt4-x11 sources and the stock qt. Because we are on stock qt (due to support from Nokia)
[01:37] <sveinse> Yes, I'll report any bugs I come across. Just wanted to hear if its known to be unstable
[01:37] <persia> Works for me, but that's only one data point, and I don't claim to use that system that much.
[01:38] <sveinse> but thanks, it does help
[01:40] <sveinse> rsalveti: I have to sleep now, but I'll get hold of you if I'm able to reproduce the crash
[01:40] <persia> Just checked: there's a heap of patches against Qt.  You don't need to diff though: just `apt-get source qt4-x11` and look in debian/patches
[01:40] <sveinse> Thanks
[01:40] <rsalveti> sveinse: sure
[01:40] <persia> kubuntu_23_arm_memory_barriers.patch is one of the things you may require :)
[01:40] <sveinse> persia, yes, there's lots
[01:42] <sveinse> persia, thanks you for your insights and discussions. I've learned a lot. In fact I shall bookmark the irc logs from this evening
[01:44] <sveinse> good night
[05:58] <MrCurious> i am not entirely sure what the omap4 package has done for me
[06:24] <MrCurious> so i repeated the process with 11.04 that i used for 10.10, and it is corrupt again. and barfing on package updates.i even used a new SD card
[09:15] <sveinse> rsalveti, still awake?
[09:39]  * persia suspects it will be a couple hours yet
[12:52] <rsalveti> sveinse: I'm away now :-)
[12:52] <sveinse> ok, I'm not in a hurry
[15:48] <hrw> shit. my panda has rescue rootshell and getty running in same time on ttyO2 ;(
[15:49] <ogra_> did you boot oem-config without splash enabled ?
[15:49] <hrw> no, old rootfs with new kernel/initrd
[15:50] <ogra_> got "single" on the cmdline ?
[15:50] <hrw> panda login: General error mounting filesystems.
[15:50] <ogra_> upstart usually only fires up the rescue shell if you tell it to
[15:50] <ogra_> oh
[15:50] <hrw> fun is that / /home are properly mounted
[15:50] <ogra_> yeah, you likely had an fsck on your display ;)
[15:51] <ogra_> it will redirect that to the splash ... if you work remotely that indeed doesnt help
[15:54] <hrw> ok, upgrading my ubuntupandaa1 to oneiric
[15:54] <jayabharath> ogra_: Here are the logs and reports on the SD card sesize issues on 11.04 on PandaBoard http://groups.google.com/group/pandaboard/browse_thread/thread/76d19fab249a1ce9#
[15:54] <jayabharath> GrueMaster: ^^^ a follow up from our recent IRC discussion
[15:55] <jayabharath> Please feel free to study them and request more info on that thread... or log a trouble ticket if that is more appropraite
[15:55] <hrw> 466MB to download, 217MB extra used on disk. 955 packages to upgrade, 95 new to install, 3 to remove, 1 on hold
[15:55] <ogra_> jayabharath, /var/log/jasper.log would be intresting ... and a proper bug report
[15:56] <jayabharath> Atleast a couple of folks included the jasper.log
[15:56] <jayabharath> do you want me to put a bug report into the system?
[15:57] <ogra_> that would help, yep, and tell people to add their stuff there
[15:57] <jayabharath> ok
[15:57] <jayabharath> Seems like we are having a lot more problem reported with natty than with maverick
[15:57] <GrueMaster> I have the same hw as magog96 (Transcend 16G Class 10 SDHC & Panda A1).  Worked fine here.
[15:58] <hrw> ~hail apt-cacher-ng
[15:58] <jayabharath> it could also be that we now have a larger user base .. i.e. more testing and more possiblity of user errors ;)
[15:58] <GrueMaster> Most of them appear to be A2/A3 pandas.
[15:59] <GrueMaster> Which I don't have to test with (backorder).
[15:59] <jayabharath> GrueMaster: We can try to update your pandaboard with a newer version... should not be a issue.
[16:00] <hrw> have a nice rest of day
[16:09] <GrueMaster> jayabharath: I have noticed sproadic issues with natty on my A1, but have not been able to reproduce them.  During testing, I would see them once or twice a week when testing daily images.  Most of the time, it was just a matter of oem-config restarting instead of completing, but there was never any signs of corruption.
[16:09] <GrueMaster> And oem-config would complete on the second pass.
[16:09] <GrueMaster> I wonder if it is something in x-loader/u-boot that ships with natty?
[16:19] <martyn> Okay, one thing I just figured out about the i.mx53 boards -- they overheat
[16:19] <martyn> fast
[16:20] <martyn> Those processors actually need a heatsink.
[16:20] <ogra_> did you check for an intel logo on the SoC ?
[16:21] <GrueMaster> heh
[16:21] <martyn> *snicker*
[16:21] <GrueMaster> Intel processors don't overheat.  They throttle back to almost off when they reach 75C.
[16:22] <martyn> They could have done a much better job on the thermals .. this thing needs a heatsink, and they should have installed one on every board
[16:22] <ogra_> persia, NCommander, do you guys remember wheer the spice seed notes are (i know for sure both of you were in the room when we discussed them) ... infinity got that spec assigned but it seems to be empty
[16:24] <NCommander> ogra_: they should be on the etherpad document
[16:25] <ogra_> hey infinity
[16:26] <infinity> o/
[16:28] <ogra_> infinity,  challenge your javascript interpreter a bit ... http://summit.ubuntu.com/uds-o/meeting/other-o-arm-seed-spices/
[16:28] <NCommander> WOOO infinity !
[16:29] <martyn> hmm?
[16:30] <infinity> ogra_: That looks decidedly unfinished.  Fun!  I especially like "Talk to lamont + kamion to make sure design is workable"
[16:30] <ogra_> lol
[16:31] <ogra_> well, talk to persia, NCommander or me if you need explanation, we were in the BOF session and *might* remember one or the other bit
[16:31]  * infinity laughs.
[16:31] <infinity> Cause it was oh-so-long ago, right? :)
[16:32] <ogra_> indeed ... and there were these beers at night
[16:32] <NCommander> Basically we decided to implement it with metapackages
[16:32] <ogra_> *hungarian* beers
[16:32] <NCommander> persia was talking notes
[16:32] <martyn> Belgian beers too
[16:32] <martyn> some pretty strong ones, as I recall
[16:32] <ogra_> pfft
[16:33] <ogra_> belgian  "beer"
[16:33] <martyn> infinity: It's been a whole _month_ ...
[16:33] <infinity> NCommander: Metapackages shouldn't be entirely necessary, but I'm happy to get back in on the discussion in a bit, if I'm expected to implement the results. ;)
[16:33]  * martyn starts the biervars with Oliver
[16:33] <ogra_> infinity, just make it work properly ...
[16:33] <ogra_> we dont care about how :P
[16:34] <GrueMaster> Wait, what?  We were in sessions between beer???
[16:34] <ogra_> GrueMaster, thats when you sat down ... remember ?
[16:34] <GrueMaster> But I sat most of the time...oh, wait.
[16:35] <martyn> *chuckle*
[19:14]  * pmathews wonders if there is a channel for low power RF devices from TI
[21:23] <hrw> ogra_: Ubuntu uses x-loader-omap4 L24.9git20100901-0ubuntu5 or x-loader-panda?
[21:24] <GrueMaster> hrw: x-loader-omap4-panda 1.5.0+git20110325+b6bbfe7-1ubuntu1
[21:26] <GrueMaster> At least that is what is currently in oneiric.
[21:46] <dumarjo> I have some problem using rootstock on ubuntu 11.04 to build an lucid image for gumstix board
[21:47] <dumarjo> I have some segfault for the locale and I also have an error about E: Sub-process /usr/bin/dpkg received a segmentation fault.
[21:47] <dumarjo> E: Second stage build in chroot failed !
[21:47] <dumarjo> E: Please see the log to see what went wrong.
[21:47] <dumarjo> can someone can help me to resolv this ?
[21:48] <GrueMaster> dumarjo: Why lucid?  Why not just use our natty-headless image?
[21:48] <dumarjo> I can try
[21:48] <dumarjo> so I use -d natty ?
[21:49] <GrueMaster> You are creating an image to run from SD, right?
[21:49] <dumarjo> yes
[21:49] <dumarjo> but i would to use qemu too
[21:49] <GrueMaster> Just download the pre-installed image and flash to an SD card.
[21:50] <dumarjo> from the gumstix web site ?
[21:50] <GrueMaster> http://cdimage.ubuntu.com/releases/11.04/release/ubuntu-11.04-preinstalled-headless-armel+omap.img.gz
[21:50] <GrueMaster> This will run through a serial console.
[21:51] <davidm> GrueMaster, he is using a gumstix, might not work
[21:51] <GrueMaster> I thought it was tested by linaro to work.
[21:51] <davidm> I don't have documentation on that
[21:52] <davidm> we should put that on the wiki if Linaro did indeed test it
[21:53] <dumarjo> is this image can be use with qemu ?
[21:57] <dumarjo> same error
[21:57] <dumarjo> I use this command line
[21:57] <dumarjo> sudo rootstock --fqdn WebNode --login gumstix --password gumstix --imagesize 2G --seed linux-image-omap,ubuntu-minimal --notarball -d natty
[21:57] <dumarjo> something wrong in taht ?
[21:58] <GrueMaster> looks ok.
[22:05] <dumarjo> ok then. I wil have to tale a look close towmorrow... thanx for your helps
[22:45] <hrw> GrueMaster: then it should provide upgrade path - my natty panda had L24.9 one and dpkg errors out with it as it's version does not begin with digit
[22:45] <hrw> GrueMaster: natty -> oneiric upgrade catched that
[22:48] <hrw> ubuntu kernel for panda still had cyan fb ;(