[01:41] <blk_jack> Does anybody know a workaround for the plymouth error on boot?
[01:41] <ogra_> plymouth error ?
[01:41] <blk_jack> I've tried adding overrides and deleting the init files but it still crashes and I can't boot
[01:42] <ogra_> what HW is that on ?
[01:42] <blk_jack> It's on the Ubuntu launchpad, but the device is the new samsung chromebook
[01:43] <blk_jack> The bug is reported on the launchpad, I mean
[01:43] <ogra_> get the source for ac100 tarball installer ... look at the postinst
[01:43] <ogra_> it adds a bunch of diversions ... apply them
[01:44] <ogra_> once thats dont add FRAMEBUFFER=True to your intramfs.conf ... then rebuild your intramfs and it should work
[01:44] <ogra_> s/dont/done/
[01:45] <ogra_> hmm, even though, on the chromebook you could probably get through without the diversions
[01:45] <blk_jack> Well right now I'm effectively locked out
[01:45] <blk_jack> It doesn't boot
[01:45] <ogra_> can you change the kernel cmdline ?
[01:46] <ogra_> if so, add break=bottom ... boot and then exit with ctrl-d from the initramfs shell
[01:46] <ogra_> it should boot normally that way
[01:47] <blk_jack> I'd need to build a new kernel to do this right?
[01:47] <ogra_> no, you need  access to the bootloader for this
[01:47] <ogra_> or to the bootloader config
[01:48] <wookey> ogra_: is this the general runes for how to boot with plymouth missing?
[01:48] <wookey> I could really use this info...
[01:48] <blk_jack> The chromebook bootloader is signed and locked
[01:48] <ogra_> wookey, the general rules is: make console-setup run in your initrd and plymouth will work
[01:49] <wookey> ogra_: my problem is building plymouth...
[01:49] <wookey> it'd be nice to test the system without having to do that
[01:49] <ogra_> well, mountall kind of relies on libplymouth for user interaction
[01:50] <wookey> OK, so the short version is 'it's hard'
[01:50] <ogra_> if you can make sure to suppress all filesystem checks and boot with rw on the cmdline it should work
[01:50] <wookey> in which case building it should be OK if I can just remove the X build-dep
[01:50] <ogra_> but will complain
[01:51] <blk_jack> For some reason I thought 13.04 fixed this issue
[01:51] <blk_jack> Apparently not
[01:51] <ogra_> no, its still being researched
[01:51] <ogra_> its a race condition ... a tricky one
[01:54]  * ogra_ notes its kind of late and goes to bed
[02:02] <blk_jack> Bleh
[02:02] <blk_jack> Hard to believe there's no decently documented workaround for this issue
[06:37] <infinity> wookey / cjwatson: arm64-cross-toolchain-base is up to date again, enjoy.
[08:45]  * ogra_ grumbles ... seems one sick cat isnt enough ...
[09:06] <shadeslayer> robclark , hrw oh ... okay
[09:07] <shadeslayer> then I'm back to square one basically
[09:07] <shadeslayer> can't find compatible hardware that I can play with
[09:07] <shadeslayer> or the ones that are compatible are ETOOEXPESIVE
[09:08] <shadeslayer> *EXPENSIVE
[15:38] <bruvik> hello, I have a question about the /debian/* files in a source directory
[15:38] <bruvik> is it possible to manually install them if I compiled the program and installed it manually or do i have to build a deb package?
[17:41] <Gaga> Hello, I have a few newbie questions. 1. Please tell me is there any differance between Ubuntu x86 and ARM root filesystem?
[17:42] <Gaga> Differance in source