<steev>
GekkePrutser: it works fine, you need to use patchram to get the bluetooth/wifi working, and we (as in non-chrome) will need to some up with something for the flip portion for disabling the keyboard and trackpad, but i've already got a regular linux install running on mine
markm has quit [Ping timeout: 276 seconds]
markm has joined #linux-rockchip
<GekkePrutser>
Steev: so you've got a c100 already?? I didn't think it was out yet
<GekkePrutser>
And thanks for your answer!
<steev>
GekkePrutser: yes, it's not, apparently amazon screwed up and shipped mine earlier (i'm not complaining)
<GekkePrutser>
Hah great! Is it good?
<steev>
aside from the flip portion needing to be written and me sucking at maths, there's only one minor issue i've discovered so far
<steev>
for some reason, it doesn't un-suspend properly from suspend to ram when opening up, instead of being opened
<steev>
performance wise, it's great
<steev>
chromeos flip portion works really well
<GekkePrutser>
Sounds great, I can't wait till I can get one here in Europe. Knowing Asus it shouldn't take too long
<steev>
GekkePrutser: http://sprunge.us/RhNU there's the script i use to build Kali Linux for it, if you use something debian based, it shouldn't be too hard to modify the script
<steev>
if you use something not debian based, it shouldn't be too hard from the script to figure out what you need
<GekkePrutser>
Oh yeah I can see that being a great machine for Kali too.
<GekkePrutser>
I got nethunter on my old nexus 7 but without a keyboard it's cumbersome.
<GekkePrutser>
But I'd definitely go for something Debian based
<GekkePrutser>
Maybe Debian itself even
<steev>
just change the kali bits to debian, and you should be able to build the image
<GekkePrutser>
Thanks I'll give that a try!
<steev>
oh
<steev>
you need the minnie first, because you need the firmware files
<steev>
but, it should still be possible to build the image, you just won't have the wifis
<steev>
GekkePrutser: fwiw, i'm using it to do some docker stuff, seems to work fine (that's why i'm using btrfs)
<GekkePrutser>
Ahh ok I have to read up on that patchram stuff
<GekkePrutser>
So you're even running docker on it? Nice
<GekkePrutser>
This really sounds like a great machine on the go
<steev>
the build quality is..... not fucking plastic
<steev>
so that's nice
<steev>
oh, sorry if we can't drop fbombs in here
<GekkePrutser>
:) doesn't bother me
<steev>
GekkePrutser: i just kicked off a fresh build, hitting my local mirror, i think it takes ~17 minutes to run the debootstrap stuff to create an image/import it
<GekkePrutser>
I always wished my old iPad had a keyboard and ran a real OS and this seems just the thing
<steev>
the only minor issue - but i've had it across all chromebooks, is that occasionally wifi gets stuck/drops, but a quick suspend/resume kick starts it again
<amstan>
steev: this doesn't sound like fun
<GekkePrutser>
Yes I read that, it's mainly under heavy load right?
<GekkePrutser>
I probably wouldn't use it like that much anyway
<steev>
amstan: what isn't fun?
<amstan>
unstable wifi
<steev>
amstan: it only happens outside chromeos, i really have nfi
<steev>
maybe because i'm not downloading 800mb-1.3gb worth of files while in chromeos so never see that
<GekkePrutser>
It doesn't sound too bad. I wouldn't download big stuff that much anyway
<amstan>
steev: i regularly do that on netflix
<steev>
amstan: but do you really? i mean is it starting and stopping over and over, resolving
<amstan>
sure
<amstan>
but it'll definitelly do that in 1 hour
<steev>
actually...
<steev>
now that i think about it, i'm not sure i've actually run into the issue with minnie
<steev>
but dear god please don't let that mean a switch to using brcm
<steev>
amstan: and you still haven't said, wtf is the deal with /system/etc/firmware/AM... firmware
<amstan>
i don't know
<steev>
it's the AP3351 firmware or whatever chillin in veyron overlay
<steev>
AP6335-wifi-bin
Astralix` has joined #linux-rockchip
Astralix|away has quit [Ping timeout: 264 seconds]
<bashintosh>
amstan: I solved VGA-out only on the Firefly - it was indeed "disabled" at the HDMI node in the Firefly kernel DT. I am really not sure of why it wasn't working before, but after rebuilding the kernel from scratch with clean config all was good. Thanks for the advice BTW :)