=== prp^2 is now known as prpplague [02:22] .wc === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === piscodig is now known as discopig === piscodig is now known as discopig === chihchun is now known as chihchun_afk [12:16] ogra: can you spin one more Nexus 7 Kubuntu Active image? or give me the scripts to do that? [12:16] a) the scripts wont help you and b) there is no desktop kernel for the nexus7 anymore in saucy [12:16] I have access to a N7 now and can investigate why things are going wrong on the desktop image [12:17] bah [12:17] you could change your seeds to use the ubuntu touch kernel, but would then end up without touchscreen support [12:17] ogra: mostly it seems like the OEM thingy doesn't run post boot [12:18] wait, isn't the kernel image separate from the one that's flashed to the data partition? [12:18] so why can't we use the kernel image that's already there + a different rootfs [12:18] no [12:18] uhhh [12:18] http://cdimage.ubuntu.com/kubuntu-active/daily-preinstalled/current/raring-preinstalled-desktop-armhf+nexus7.bootimg < isn't that the kernel + initramfs? [12:18] well, the kernel would be, but the installl updates the initrd which in turn updates the kernel from /boot [12:19] yes [12:19] ah [12:19] but you need to re-roll the initrd after first boot [12:19] I see [12:21] ogra: can we bring the desktop kernel back? How much of a headache would it be to maintain it? [12:22] since the one in raring already works, would it need much work to get it to boot saucy? [12:22] you could use the linux-grouper tree with a different config and patches added to make touch input work [12:23] ask the kernel team, i dont know how much work it is ... [12:23] oh okay [12:25] ogra: oh, one more question, why would the touch not work with the ubuntu touch kernel? [12:26] because it needs a hack to the touchscreen driver (which breaks it on touch) [12:26] and indeed a completely different config [12:26] touch uses all the android bits [12:27] I see [13:14] ogra: does Ubuntu has working installer for any ARM device? [13:14] ac100 [13:15] and if you want d-i/ubiquity ... pandaboard [13:15] ogra: where I can read about it? [13:16] wiki.ubuntu.com/Ubiquity ?! [13:16] hrw, about what specifically ? [13:16] https://wiki.ubuntu.com/ARM/TEGRA/AC100 found [13:16] d-i or preinstalled ? [13:16] for pandaboard it's bog-standard ubiquity just like on the desktop. For ac100, it's pre-installed system running in oem-config mode. [13:17] ogra: thinking of a way to get more usable installer for chromebook than JayLee script [13:17] preinstalled uses the ac100-tarball-nstaller package ... i guess yu need to read the source, it doesnt have any additional docu === hrww is now known as hrw === nslu2-log_ is now known as nslu2-log === tgm4883_ is now known as tgm4883 === NCommander is now known as Guest14386 === calculu5 is now known as calculus === ieatlint_ is now known as ieatlint === nslu2-log_ is now known as nslu2-log === Guest14386 is now known as NCommander === nrirclog511 is now known as nrirclog === panda is now known as Guest56253 === Daviey_ is now known as Daviey === mbm is now known as [mbm] === doko_ is now known as doko === chuck_ is now known as zul [23:16] Does ubuntu arm run on the MK908 quadcore [23:35] Would you say Ubuntu ARM is suitable for a production system or not yet? === nslu2-log_ is now known as nslu2-log