[01:14] <cyphermox> is it a known issue that overlayfs doesn't seem to be available in saucy right now?
[16:29] <apw> cyphermox, it is a known issue that the modules does not autoload, modprobe overlayfs will sort it out
[16:30] <apw> cyphermox, the upload 3.9.0-0.4 should contains the fix, let us know if that does not
[16:32] <rtg_> apw, rm -rf ubuntu-nexus* ?
[16:42] <cyphermox> apw: yeah, all good thanks.
[17:20] <xnox> apw: heya, Where abouts are you? Ondrej was looking for you.
[18:41] <infinity> apw: Am I getting a linux-meta-mako today too?
[18:54] <apw> infinity, it should be in the queue right now, i thnk
[18:56] <infinity> apw: And so it is, thanks.
[18:57] <apw> infinity, np
[18:58] <infinity> apw: Hah.  Nice that the old nexus4 stuff had "Nexus 7" all over it. :P
[18:58] <apw> infinity, la la la nothing to see there :)
[19:04] <ogasawara> apw: test
[19:48] <deffrag> Hello! I'd like to know about kenel compatibility with hardware raid controller. My system's motherboard got 4 sata ports, all used. I intend to extend the number of ports from 4 to 6/8 by buying a card. My primary requirement is only to increase number of sata ports. Could anyone please guide me with supported raid cards for the same?
[21:28] <cyphermox> hi; I think there's a config missing from the nexus4 kernel; specifically to enable BT_HCISMD which is required for bluetooth on the nexus 4 -- https://lists.launchpad.net/ubuntu-phone/msg01529.html
[21:29] <apw> cyphermox, ok
[21:32] <apw> cyphermox, any others changed in that period?  as it seems that this was not communicated to our copy ...
[21:32] <cyphermox> let me double check, but I don't think there were other kernel changes
[21:33] <cyphermox> no, that was the only one
[21:34] <cyphermox> I think it just got applied a little after the tree was cloned
[21:34] <cyphermox> http://phablet.ubuntu.com/gitweb?p=CyanogenMod/lge-kernel-mako.git;a=commit;h=6f4216569fdcde11a7decb5f8f3f5c7d76e67e48
[22:03] <xnox> apw: my hardware has intel graphics and free drivers. Can I also run and dog-food MIR?
[22:03]  * xnox has the broken 3 monitors use-case which I'd rather MIR work correctly with.
[22:03] <xnox> apw: where are you running X on mir from? Is there a daily ppa or something like that.
[22:04] <apw> xnox, erm, a ppa somewhere
[22:07] <apw> cyphermox, i assume you want this uploaded or do you want a test kernel to confirm that is all you are missing
[22:08] <cyphermox> I had confirmed it before with the android kernel tree I linked above, I think it's ok as-is
[22:08] <cyphermox> apw: up to you, is it much trouble to make a test kernel?
[22:08] <apw> cyphermox, so just upload yes?
[22:08] <cyphermox> yeah
[22:08] <apw> cyphermox, not difficult if you can test
[22:08] <cyphermox> I can test, but I don't expect any issues at all
[22:08] <cyphermox> I'm really just missing that interface to speak to the hci device
[22:09] <apw> cyphermox, then i'll get you this test kernel and prep the upload in parallel
[22:09] <cyphermox> ok
[22:12] <apw> cyphermox, http://people.canonical.com/~apw/mako-saucy/
[22:12] <cyphermox> ugh, I had no idea it was *that* quick.
[22:15] <cyphermox> apw: oh, but wait... how can I install that on the android side?
[22:18] <apw> cyphermox, that ... is the 20k$ question ...
[22:18] <apw> ppisati, you have some incantations for installing a kernel right ?
[22:18] <apw> (onto a phone et al)
[22:18] <ppisati> apw: yep
[22:18] <ppisati> apw: hold on
[22:19] <ppisati> apw: https://wiki.ubuntu.com/Kernel/Dev/AndroidKernel
[22:20] <apw> cyphermox, ^^
[22:20] <ppisati> apw: IOW 'abootimg -u /dev/block/$device -k $mykernel'
[22:20] <apw> ppisati, ta
[22:20] <cyphermox> ah, thanks!
[22:31] <cyphermox> apw: ppisati: not sure the kernel in that current state is actually quite right to be applied to the mako boot partition as is.. at the very least, it doesn't boot past the Google logo now
[22:32] <apw> cyphermox, quality
[22:35] <cyphermox> yeah..
[22:36] <cyphermox> rsalveti: ^ know how I can go from the .deb kernel image to flashing it to the mako boot partition?
[22:37] <cyphermox> rsalveti: I assume the image builder does some magic to massage it all into the right format or something
[22:37] <rsalveti> cyphermox: did you just flash the kernel or together with initrd?
[22:37] <rsalveti> just the kernel should be enough
[22:38] <rsalveti> I'm fixing flash-kernel to have it updated automatically
[22:38] <cyphermox> I tried just the kernel, and the kernel and initrd
[22:38] <rsalveti> abootimg -u /dev/block/mmcblk0p6 -k <kernel> should be enough
[22:38] <cyphermox> ok.
[22:38] <cyphermox> with the vmlinuz from a debian package?
[22:39] <rsalveti> yup
[22:39] <apw> cyphermox, let me know when you are happy
[22:39] <cyphermox> rsalveti: if you have a mako, care to try http://people.canonical.com/~apw/mako-saucy/
[22:39] <cyphermox> apw: already happy tbh
[22:39] <cyphermox> I don't see what other than BT_HCISMD it might be needing
[22:40] <cyphermox> I just want my bluetooth to work :)
[22:42] <rsalveti> cyphermox: sure
[22:46] <ppisati> cyphermox: extract .deb contents, and then abootimg just kernel
[22:47] <ppisati> cyphermox: that's enough
[22:48] <rsalveti> cyphermox: yup, doesn't boot
[22:50] <cyphermox> uh-oh
[22:50] <rsalveti> cyphermox: what changed?
[22:52] <apw> BT_HCISMD=y
[22:53] <apw> cyphermox, i guess you should confirm the one in the archive boots
[22:54] <rsalveti> apw: the one we're currently using is still from raring, was going to switch today to saucy as you pushed the meta package
[22:54] <rsalveti> but indeed, not yet tested
[22:55] <rsalveti> I tested the one for nexus 7, but breaks the android boot side, maybe because it's loading as usb gadget by default
[22:56]  * apw holds of any kind of upload
[22:57] <apw> rsalveti, mako and grouper are likely to have the same settings there
[22:57] <rsalveti> yeah, weird 
[22:57] <rsalveti> I'll compare the configs later
[23:01] <cyphermox> I'll try the one in the archive now on my nexus 4
[23:06] <apw> rsalveti, great, let us know
[23:33] <rsalveti> apw: cyphermox: raring nexus4 boots, saucy mako doesn't
[23:35] <rsalveti> apw: is it using the same config?
[23:35]  * rsalveti checking
[23:51] <apw> rsalveti, that would be my expectation indeed
[23:52] <rsalveti> apw: yup, I'm cross building the head from saucy to see if it'll work
[23:52] <rsalveti> apw: we're using gcc 4.8 by default already right?
[23:52] <rsalveti> wonder if that might have caused any issue, otherwise will try to revert the top patches to see
[23:55] <apw> rsalveti, ok the configs appear to be the same for those two
[23:57] <rsalveti> yeah