[02:49] lilstevie: hey man, you awake? [02:50] I'm thinking about getting a new arm netbook, wondering if you had any opinions. [02:51] Pretty much just want a 1kg/10"/all-day battery and running debian or ubuntu natively (chroot inside android doesn't count). Don't care if it's sold as a tablet+dock, long as I can use it as a netbook :-) [03:02] twb: If you are willing to jump through a few hoops, you can get Ubuntu running on the Samsung Chromebook. [03:02] I heard bad things about the google stuff [03:02] Something about SBK? [03:03] THis is news to me... [03:03] You are probably thinking of the Intel variant of the Chromebook. [03:03] twb, I'm awake [03:03] I think Samsung have an Arm version and an Intel version, probably named different things and look differently, but yeah. [03:03] TheMuso: not sure. I'll see if I can find the reference I"m thinking of [03:03] the samsung one does have a few issues [03:03] Don't know the name differences. [03:03] like melting the speakers [03:03] if you futz with alsa incorrectly [03:03] Ok, wasn't really aware of the issues, just know it can be done., [03:04] lilstevie: Yeah but thats fixed as of raring., [03:04] http://mjg59.dreamwidth.org/22465.html "Don't like Secure Boot? Don't buy a Chromebook." [03:04] "Out of the box, Chromebooks are even more locked down than Windows 8 machines." [03:04] twb: Yeah thats about the intel variants, I *think* [03:04] It's not clear if that's x86_64 ones [03:05] NFI how far the EFI madness has penetrated the arm space [03:05] twb, remove a single gold screw and the arm chromebook is open [03:05] lilstevie: OK [03:05] EFI on arm has only penetrated the windows rt devices so far [03:05] arm chromebook uses u-boot [03:06] RaYmAn would be better than me at this though [03:06] he flashed a full devel unlocked u-boot to his device (can only be done with the gold screw undone) [03:07] the gold screw basically enforces SPI writelock [03:07] OTOH the TF101 is still working fine, I'm mainly just wanting to do upgrades to its kernel and stuff that are likely to brick it for a couple of days, meaning I can't do my job. So maybe what I *should* be doing is getting an x86 netbook instead as my backup... [03:07] tf101 is dead [03:07] Lo [03:08] performance of chromebook is much faster [03:09] Meh, it's only doing emacs and ssh, and it's pretty much already limited by how fast I can type [03:09] >1G of ram would be nice so I can buffer more of the SD card in RAM [03:11] http://www.google.com/intl/en/chrome/devices/samsung-chromebook.html#specs says only 6½hr battery [03:14] it says "over" [03:14] :p [03:16] yeah but it's a vendor claim running vendor's OS, so when you switch to a proper linux you assume it's about 80% of their lowest claim === zz_chihchun is now known as chihchun [03:41] at full load I get 6 hours on my chromebook battery (like, compiling the whole time) [03:42] if you let it clock down it's closer to 12 hours [03:42] OK [03:49] Zero_Chaos, running ubuntu [03:49] or chromeos [03:49] lilstevie: niether ;-) [03:50] Zero_Chaos, lol [03:51] lilstevie: gentoo [03:51] figured [03:52] it was either going to be debian or gentoo, but you said compiling all day [03:52] yeah kinda narrows it down ;-) [03:52] haha [03:54] I'm unsure where the best performance is with arm [03:54] gentoo for me is a little heavy when you probably need to spend a week compiling everything needed for a desktop env [03:54] lilstevie: closer to two days [03:54] lilstevie: surely you can cross-compile anyway [03:54] So just do it on big iron [03:54] Zero_Chaos, heh thats on the a15 though right [03:55] then again i don't use kde so maybe a week for kde users [03:55] someone said it took 16-17 hours to compile chromium on the tf201 [03:55] Last time I tried to compile webkit I ran out of ram [03:55] heh [03:55] Probably because -g was on [03:56] I'm running fedora on my tf201 as an experiment for the time being and it seems alright, but no EGL/GLES stuff at this stage [04:00] Oh *that's* why my old x86 netbook is in the cupboard. It's btrfs-on-SSD shat itself [04:01] lol [04:02] I worked out how to recovery /home and /srv later, but / was gooooone [04:03] lol === XorA|gone is now known as XorA === chihchun is now known as zz_chihchun === zz_chihchun is now known as chihchun === chihchun is now known as zz_chihchun [09:35] hello all [09:38] i have a few questions about boot on android devices from uefi volumes === zz_chihchun is now known as chihchun [09:53] * ogra_ guesses you should better ask in an android channel then === chihchun is now known as zz_chihchun === zz_chihchun is now known as chihchun [11:20] . [11:22] , [12:01] imblaze: ping === prpplague is now known as prp^2 === calculu5 is now known as calculus === mrcan_ is now known as mrcan [15:11] anyone uses ubuntu in a chromebook xe303c12 here? === chihchun is now known as zz_chihchun === mhall119 is now known as mhall119|lunch === rsalveti_ is now known as rsalveti === mhall119|lunch is now known as mhall119 [20:02] I am trying to install wpa_supplicant 2.0 on ubuntu-arm server but it has too much dependencies. Once someone here told a command with aptitude to install dependencies automatically, does anyone know how I can do it? [20:04] dependencies are always installed automatically [20:04] angs: Are you building wpa_supplicant yourself, or getting it from a PPA, or...? [20:04] oh, yeah, i missed the 2.0 [20:04] angs: If it's not coming from an apt repository, apt (or aptitude) aren't going to be much help. [20:05] angs: Though, "apt-get build-dep wpasupplicant" might give you an approximation of the things you need to built it, if that's what you were looking for. [20:05] s/built/build/ [20:07] yes I am trying to build it myself [20:07] than you it install some packages now === rsalveti_ is now known as rsalveti