[00:11] <wookey> OK, cheers
[00:13] <wookey> and sucked back down in <2mins :-)
[01:03] <wookey> OK, If I boot the right image. Either ubuntu-core or doko's uploaded tarball it gets as far as init: upstart-udev-bridge state changed from pre-start to spawned
[01:04] <wookey> then three lots of CPU1: failed to boot (and CPU2 and 3)
[01:04] <wookey> myabe it'll give me a prompt eventually... bu that sounds bad
[01:05] <wookey> oh, yes it's not actually dead yet...
[01:06] <wookey> right doko's image boots to a prompt, but now I need to know a login. bum
[01:17] <wookey> hmm. looks like doko's image boots but the plain suacy one doesn't. I'll leave it another hour or so..
[02:29] <wookey> yep. still hung.
[02:29] <wookey> I give up.
=== arun_ is now known as run
=== run is now known as arun
[06:05] <Vialas> yay
[09:24] <talentless> hello. eclipse-platform package has not been available for arm for a while now. anybody got a workaround?
=== psivaa is now known as psivaa-afk
=== doko_ is now known as doko
[11:38] <reisei> hi, all! I'm trying to compile omap4-pvr-dkms, but got an error: http://pastebin.com/n8VcVQMi Can somebody help to solve it?
=== psivaa-afk is now known as psivaa
[13:35] <linu> hi i have been using kernel 3.13 and enabled all framebuffer driver but when i try to run a sample  qt apps in at91sam9g35ek it shows QScreenLinuxFb::connect: No such device Error opening framebuffer device /dev/fb0 can you tell me what is that issues
[17:02] <doko> wookey, login is ubuntu/ubuntu
[17:12] <shadeslayer> can someone tell me the specs of the arm64 builder?
[17:13] <shadeslayer> There is like a 2 hour build difference between armhf and arm64 for qt4-x11
[17:13] <shadeslayer> ( i.e. arm64 took 2 hours less to build qt4-x11 )
[17:43] <wookey> doko: cheers. I booted as /bin/init and changed root to get in. It works now :-) Just testing some stuff and faffing with model networking
[23:34] <doko> wookey, http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=arm64;users=debian-arm@lists.debian.org updated, have fun ;-P