**** BEGIN LOGGING AT Wed May 14 03:00:00 2014 May 14 14:56:39 Hi all.. I seem to be having trouble building an armhf trusty image, is 14.04 supported for armhf yet? I keep getting the "Failure while configuring base packages. This will be re-attempted up to five times." while running debootstrap or mk-sbuild, and while it finishes, when i try the finished product on my evk board, I get no console. May 14 14:57:20 12.04 works.. I've checked to make sure I've got a getty session on the usb uart that *should* be starting. May 14 14:57:48 yes, 14.04 armhf is supported and used by many people May 14 14:58:08 (in cloud setups as well as on phones for example) May 14 14:59:14 Hmmm. May 14 15:00:22 Maybe I'm not setting up the terminal correctly then after all, but I'm just copying what I have in 12.04... May 14 16:55:42 applepi: What are you running debootstrap on? May 14 16:56:21 applepi: Also, if in doubt, you could try unpacking ubuntu-core and configuring it, instead of debootstrap itself. May 14 16:56:30 applepi: (But if debootstrap fails, looking at the log is also helpful...) May 14 16:58:10 infinity: Mint 14 May 14 16:59:02 infinity: I can build 12.04 just fine but I get several configuring errors when during --second-stage when making 14.04 May 14 16:59:14 awww May 14 16:59:49 use qemu-user-static ... then you can use qemu-debootstrap ... and wont need all that crap like foreign and second stage May 14 17:00:00 (well, if mint didnt break their kernel to much) May 14 17:01:41 I'm not entirely sure what the issue is honestly, I can see in the dmesg logs that it IS finding ttymxc0 when booting... right now the last thing I get is 'Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory' but looking around online that seems like it shouldn't stop it from booting.. May 14 17:02:52 apt-get install qemu-user-static; sudo qemu-debootstrap --arch armhf trusty myarmchroot May 14 17:02:58 do that May 14 17:03:23 probably you need a reboot after installing the package, depends on the mint kernel May 14 17:09:53 odd, I swear I tried that before, but I'm watching it run now and it does look like it's behaving MUCH better May 14 17:10:53 :) May 14 17:11:34 the nice thing is that you can just chroot into it now and prepatre your rootfs as you need it later ... no need for doing that on the device May 14 17:14:56 Bugger... right at the end. "Configuring udev..." "Failure while configuring base packages. This will be re-attempted up to five times." Four times, but then it says "Base system installed successfully." May 14 17:15:50 I suppose it succeeded? May 14 17:52:15 Bah... I can *not* get trusty to give me a friggin login prompt... May 14 17:53:48 applepi: Are you setting up a console job in /etc/init/ttymxc0.conf ? May 14 17:54:12 infinity: yes. and i've checked that ttymxc0 is being set up in dmesg.. May 14 21:03:27 May 14 21:05:28 A question regarding upstart- "When 2 or more upstart files start on the same event, how to make sure one of them always start before others" Ex: JobA.conf --> start on ALPHA . JobB.conf --> start on ALPHA. How do I make sure JobB.conf always start before JobA.conf ?? May 14 21:07:57 arg: If the order matters, you have an undeclared dependency. May 14 21:09:57 infinity: Here is what I am trying to do - May 14 21:09:58 I have a firstboot script /etc/init/firstboot.conf which starts on "filesystem". This file creates some symlinks to some libs in /usr/lib May 14 21:10:00 Issue is , /etc/init/lightdm.conf also starts on "filesystem". May 14 21:10:03 If I traverse backwards, mountall.conf is the file which emits "filesystem" event and when this event is generated, lightdm.conf as well as my custom firstboot.conf both try to execute their scripts but the ordering is not guarenteed and you can never tell which one runs first. Now I want to always ensure that firstboot.conf runs before lightdm.conf . How can I ensure this without editing lightdm.conf ( I know I can create a dependency by emitting an e **** ENDING LOGGING AT Thu May 15 02:59:59 2014