[00:08] <mjrosenb> lilstevie: how do you install them?
[00:08] <mjrosenb> lilstevie: I asked in #fedora-arm, and they denied its existence.
[00:08] <lilstevie> um give me a sec
[00:08] <lilstevie> mjrosenb, I got the package name from fedoras own wiki 0.o
[00:09] <lilstevie> gcc-arm-linux-gnu.x86_64 : Cross-build binary utilities for arm-linux-gnu
[00:09] <lilstevie> straight from the yum search
[00:35] <sbaugh> I guess Bluetooth is working :)
[00:40] <sbaugh> And so is dwm! awesome!
[00:40] <sbaugh> Thank you Ubuntu Nexus 7 porters! I have a new netbook!
[00:41] <lilstevie> mjrosenb, find it?
[05:29] <infinity> lilstevie: Oh shiny.  I was lied to.  Not running Fedora personally, I had to accept that lie as tentative truth.  Thanks for the correction. :)
[05:29] <lilstevie> infinity, np :)
[05:30] <lilstevie> FC18 fwiw
[05:30] <lilstevie> I can't comment on earlier versions
[05:30] <infinity> Yeah, I just assume latest release and/or rawhide as a general rule.  Older Fedora releases are worth anyone's time about as much as older Ford Pintos.
[05:32] <lilstevie> fair enough
[05:32] <lilstevie> fedoras current recommended setup is to use distcc with arm guests and an x86 server
[05:33] <lilstevie> which I find a little overkill
[05:33] <infinity> Just a tad. :)
[05:33] <lilstevie> if something only builds native, I'll build it native otherwise I'll crossbuild, and packaging is always done native for me
[06:33] <sbaugh> What script/service is doing the rotation on the Ubuntu Nexus 7 port?
[08:11]  * Snark wonders how easy it can be to use an arm chromebook with qwerty keyboard... in french...
[08:45] <marvin24> ogra_: https://launchpadlibrarian.net/133791292/flash-kernel_3.0~rc.4ubuntu29_3.0~rc.4ubuntu29-tegra.diff.gz
[08:46] <marvin24> ^ this still misses a remove script
[08:51] <ogra_> marvin24, hmm, doesnt your u-boot support uEnv/preEnv.txt ? we gave up supporting booot.scr quite a while ago, so that we could use plain text files and /etc/default/flash-kernel to seed the cmdline
[08:52] <marvin24> ogra_: yes, as I said before, uEnv/preEnv is an uboot macro implemented in the omap config
[08:52] <marvin24> I can look into it again, but I don't see what's the problem with boot.scr
[08:53] <ogra_> consistency
[08:53] <marvin24> you still need to run mkimage on vmlinuz and initrd
[08:54] <marvin24> I'll think about it to add uEnv support to tegra
[08:54] <ogra_> i.e. telling people "please edit /etc/default/flash-kernel and run sudo flash-kernel" is the std way to change your commandline with all other u-boot supported devices in ubuntu nowadays
[08:54] <marvin24> yes, editing something in /usr/share isn't nice
[08:55] <ogra_> it is mainly for systems that use SD cards indeed, so that you can just edit a txt file instead of being forced to have mkimage installed
[08:56] <ogra_> we just tried to get away from that requirement ... the /etc/default stuff is just a convenient extra to make it more like grub
[09:21] <hrw> Snark: you can load AZERTY keymap - just do not look at keys ;D
[09:26] <Snark> hrw, hmmm... wouldn't it be easier to keep the keyboard as qwerty but enable some dead key to obtain accentuated chars?
[09:26] <hrw> Snark: no idea. Polish keyboard is based on US one
[09:27] <hrw> and I have UK keyboard in chromebook... but I do not look at keys
[09:28] <ogra_> there are kbd stickers you could use
[10:21] <qwertyuiop_v1> Hello!
[10:31] <qwertyuiop_v1> Do we have support for USB DVB Cards in Ubuntu Raring Ringtail (armhf) ? WinTV-Nova-T Stick is supported (linux-firmware-nonfree) but nothing happens (no smsusb probing done) when I plugged it in my Nexus 7... ;D
[10:35] <ogra_> qwertyuiop_v1, files a bug and ask for the kernel option to be enabled, its not intentional :)
[10:35] <ogra_> apw, ppisati ^^^^^
[10:35] <ogra_> *file even
[10:37] <apw> ogra_, may well not be on indeed, but yes file a bug and we can look into it
[10:38] <ogra_> i doubt it is ... i think there is a bug to enable all possible USB module options though
[10:39] <qwertyuiop_v1> ogra_, apw: thanks for your prompt response, I will file a bug
[11:23] <davmor2> ogra_: the phablet-flash command do you find you need to run it a couple of times if you haven't for a while?  the first seems to just error out and the second work flawlessly
[11:24] <davmor2> ogra_: phablet-flash -l I should say
[11:29] <ogra_> davmor2, i never used it :)
[11:29]  * ogra_ just copies both zips in place with the bootloader 
[11:29] <davmor2> ogra_: fair enough
[11:30] <ogra_> ask in #ubuntu-touch ... probably when rsalveti is around, i think he knows that script
[11:30]  * ogra_ doesnt have a supported phone so i have to do it manually anyway for my SGS2 port
[12:40] <davmor2> ogra_`: :(
[12:40] <ogra_`> ?
[12:42] <davmor2> ogra_`: to the non-supported phone sorry just playing catch up
[12:42] <ogra_`> non supported phone ?
[12:42] <ogra_`> you mean the guy wanting a raspberry Pi port of ubuntu touch ?
[12:43] <ogra_`> oh, you mean my galaxy SGS2
[12:43] <ogra_`> well, we only suppport nexus devices officiallly :)
[12:43]  * ogra_` thought you refer to his current ML discussion on ubuntu-phone
[12:44] <infinity> ogra_`: After having JUST flashed a GS2 literally an hour ago and discovering that they don't need unlocking or any other madness, I suspect that getting ubuntu-phone going on one would be dangerously close to trivial.
[12:44] <infinity> ogra_`: I'd do it myself, but I have to give this phone back to its owner now that I've unbricked it for her.
[12:44] <ogra_`> infinity, it runs absolutely perfect here since the weekend on my SGS2
[12:44] <infinity> ogra_`: (A Samsung OTA update bricked it, so I opted to just say "eff samsung" and reimage it with CM10)
[12:45] <infinity> ogra_`: Ahh, cool, you're already on it.  Awesome.
[12:45] <ogra_`> yeah, ubuntu touch isnt much hardewr once you have the HW issues sorted
[12:45] <ogra_`> wlan was a bit tricky since there are two firmwares for the same device ...
[12:45] <ogra_`> took me a while to figure that  out
[12:45] <rsalveti> davmor2: that's because adb
[12:46] <rsalveti> davmor2: it seems we need to add some sort of delay from the first time adb is initialized
[12:46] <ogra_`> and it didnt work with the recent mali android drivers ... but someone patched that bit to use the former version
[12:46] <infinity> ogra_`: Yeah, there are actually a whole bunch of SGS2 models, from what I discovered doing her recovery.
[12:46] <ogra_`> now its working as good as a nexus here :)
[12:47] <infinity> ogra_`: Hers being the "Rogers/AT&T LTE" variety.  skyrocket.
[12:47] <ogra_`> i havent tried GSM yet since i dont want to actually unlock my SIm
[12:47] <ogra_`> ugh, yeah, i thinnk vanhoof is also still struggling to get his verizon variant to work
[12:48] <ogra_`> mine is luckily a plain GT-I9100
[12:49] <ogra_`> i think slangasek also has one of tehse weirdos that were modified for a network provider
[12:49] <davmor2> rsalveti: ah thanks
[12:49] <ogra_`> rsalveti, definitely between adb root and adb shell calls
[12:49] <rsalveti> bug 1143946
[12:49] <ubot2> Launchpad bug 1143946 in Phablet Tools "phablet-flash fails on first run" [Undecided,New] https://launchpad.net/bugs/1143946
[12:49] <rsalveti> yeah
[12:50] <ogra_`> i even run into issues with that manually
[12:50] <infinity> ogra_`: My favourite part about the skyrocket variant is that they're identical at the hardware level, but for whatever crazy reason, the volume/power combinations for accessing recovery/download modes are DIFFERENT between Rogers and AT&T phones.
[12:50] <infinity> ogra_`: Can't fathom how that came to be, or why anyone thought that was a good idea.
[12:51] <ogra_`> oh my
[12:51] <ogra_`> i bet that took a while to figure out, eh ? :)
[12:51] <infinity> It took a lot of angry button-mashing when all the AT&T-centric HOWTOs were wrong for me, yes. :P
[12:51] <ogra_`> *sigh* why the heck do people want to run ubuntu touch on their RPi !
[12:52] <ogra_`> that thread starts to annoy me
[12:52] <infinity> But, much like fighting games on the SNES, if you mash enough buttons randomly, eventually you win.
[12:52] <ogra_`> haha
[13:06] <lilstevie> lol
[13:07] <lilstevie> ogra_`, it is quite simple, people purchased the rpi thinking that it would be the go-to hardware
[13:07] <ogra_`> yeah, i still wonder what made them think that
[13:07] <lilstevie> because they don't understand the whole ARMvX issue
[13:07] <lilstevie> ogra_`, pricepoint
[13:07] <ogra_`> right
[13:07] <lilstevie> ogra_`, everyone has this notion that if something is cheap, it will become the standard
[13:08] <ogra_`> heh, so "ceapest" *must* be good ... indeeed :)
[13:08] <ogra_`> *cheapest
[13:09] <ogra_`> well, i was hoping to not have any RPi discussions anymore, but somehow that crap is re-occuring every few months
[13:09] <lilstevie> yeah
[13:09] <Snark> ogra_`, hrw eh, I don't mind using a qwerty as long as I have convenient access to dead keys...
[13:10] <ogra_`> yeah, thats tricky on the chromebook ...
[13:10] <ogra_`> there are so many keys missing
[13:10]  * ogra_` really misses delete
[13:10] <lilstevie> I did a whole rant the other day about how people still insist on releasing armv6 devices in another chan,  and how I will only consider something if it is armv7 but even then there are conditions, and the first thing someone asked me was if I owned a rpi, and if not am I planning to
[13:10] <hrw> ogra_`: I have Del on F10
[13:11] <ogra_`> hrw, i have vol up there (as labeled)
[13:11] <ogra_`> the three volume keys are actually mapped like labeled for me
[13:11] <ogra_`> (indeed i could change that but would have to re-map the volume stuff elsewhere)
[13:12] <ogra_`> and wheer del usually sits there is the power key ...
[13:20] <hrw> ogra_`: Esc F1 F2 F5 F11 F4 VolDown VolUp PgUp PgDown Delete Power - my setup
[13:21] <hrw> lilstevie: devices <cortex-a15 are below my radar of interest
[13:30] <xnox> ogra_`: does the rpi discussion frequency matches the batch rpi shipments arrival from china?
[13:30] <ogra_`> heh, no idea, i try to stay away as far as i can from the RPi :)
[13:31] <ogra_`> its just crappy proprietary HW
[13:31] <xnox> OpenCrap (tm)
[13:31] <ogra_`> heh
[13:32] <ogra_`> its like a broadcom wlan card that expanded to a whole PC
[13:32] <hrw> ;)
[13:33] <hrw> marvin24: on which devices you checked your flash-kernel for DT devices patch?
[13:34] <marvin24> hrw: ac100
[13:34] <marvin24> but should work on all tegra2/3/4
[13:34] <hrw> on chromebook I do not produce /lib/firmware/KERNELVER/ libs
[13:35] <marvin24> libs? or device-tree?
[13:35] <hrw> device-tree
[13:35] <hrw> sory
[13:35] <infinity> hrw: Well, you should start. :)
[13:35] <marvin24> this actually comes from the ubuntu raring kernel (3.8)
[13:35] <infinity> hrw: The distro mainline kernels do.
[13:35] <hrw> infinity: maybe one day when I switch to uboot chainload
[13:36] <marvin24> hrw: does /proc/cpuinfo contain "Flattened Device Tree" at all?
[13:36] <hrw> marvin24: Hardware        : SAMSUNG EXYNOS5 (Flattened Device Tree)
[13:36] <marvin24> ok
[13:37] <hrw> infinity: kernel packaging is weird enough already
[13:42]  * xnox notices that pxz and busybox compatability has been fixed now.
[13:42]  * xnox TODO merge busybox
[13:42] <ogra_`> \o/
[13:42] <ogra_`> damned, so i wont have any excuse anymore to not implement xz tarballs
[14:03] <ppisati> lp 1126836
[14:03] <ubot2> Launchpad bug 1126836 in ubuntu-nexus7 "The error "df: warning: cannot read table of mounted filesystems: No such file or directory" is shown. Splash screen appears, then black screen." [Wishlist,Confirmed] https://launchpad.net/bugs/1126836
[14:03] <ppisati> this is exactly what happens to me
[14:04] <ogra_`> which is still unexplainable to me
[14:04] <ppisati> at least i'm not the only one
[14:05] <ogra_`> ppisati, no, thats the whoopsie bug that was fixed the same week
[14:05] <ppisati> ogra_`: tried yesterday img, still there
[14:05] <ogra_`> it exposed the exact same behavior
[14:05] <ogra_`> yes, you said so
[14:06] <ogra_`> but it is definitely not realted to that one
[14:06] <ogra_`> everyone who had that issue confirmed it fixed after the whoopsie fix
[14:06] <ogra_`> and it was weeks ago
[14:07] <ogra_`> i'm pretty sure what you see is kernel/HW related
[14:08] <ppisati> can we have the serial console on usb?
[14:08] <ppisati> i se network manager keeps trying to bring up usb0
[14:08] <ppisati> so i guess kernel is still alive
[14:09] <ogra_`> ppisati, there is a serial console on usb ... in parallel to the usb0 iface
[14:10] <ogra_`> check your dmesg
[14:10] <ogra_`> the prob is that yu first need to modify the bootimg to boot with init=/bin/bash, then set a root PW, drop the init= again to be able to log in
[14:10] <ppisati> ogra_`: no new ttyUSB* here
[14:11] <ogra_`> its ttyAMA or some such
[14:11]  * ogra_` forgot how the composite gadget calls it
[14:11] <ppisati> ok
[14:11] <ppisati> i see the serial
[14:11] <ogra_`> you should get a login
[14:11] <ppisati> yep
[14:11] <ogra_`> but there is no user or root pw
[14:12] <ppisati> ogra_`: can't we set a default user? ubuntu/ubuntu?
[14:13] <ogra_`> not without horrid hackery, nope
[14:13] <ppisati> :(
[14:38] <Snark> ogra_, hrw the chromebook keyboard doesn't seem really usable... I'm wondering if a nexus10 + bt keyboard wouldn't be better (though three times more expensive)
[14:38] <hrw> Snark: depends what you need
[14:43] <ogra_> depnds if you want to sit in a comfy chair with the thing on your lap or not
[14:43] <ogra_> if you always have a table its no issue to use an nx10
[14:49] <Snark> ogra_, http://www.cdiscount.com/informatique/clavier-souris-webcam/bluestork-clavier-bluetooth-avec-support-tablette/f-10702151616-bskbpadbtf.html ?
[14:50] <ogra_> well, i guess it will be wobbly and loose ... but try it
[14:50] <ppisati> ogra_: the nexus7 img, what kind of archive is that? tgz? squash?
[14:50] <ogra_> i used my nx7 for a while with wireless kbd ... and its slightly painful to always have to search a place to have it stand on
[14:51] <ogra_> ppisati, a special fastboot ext4 based sparse file format .... containing a rootfs tarball
[14:52] <ppisati> ogra_: can i "open" it in some way?
[14:52] <ogra_> you can convert it with simg2img from android-fsutils
[14:52] <ogra_> then you can loop mount it
[18:12]  * Snark wonders when the new batch of arm tablets will get out... april? may?
[18:47] <RoyK> Snark: what tablets?
[18:54] <Snark> RoyK, hmmm... isn't it the right word?
[18:56] <Snark> http://en.wikipedia.org/wiki/Tablet_computer <- it's the right word
[18:56] <Snark> RoyK, I don't understand your question, then
[18:56] <RoyK> what arm tablets are you talking about?
[19:00] <infinity> Snark: They don't tend to release in batches, I think is the confusion.  Manufacturers release products when they release products...
[19:01] <Snark> there are generally points in time where they make big announces
[19:02] <Snark> and my question is : when is the next occasion they have to make such?
[19:07] <infinity> Snark: You'd have to ask every manufacturer that.
[19:08] <infinity> My calendar doesn't have a "big tablet announcement day" on it.
[19:10] <Neko> infinity, generally CES is the big tablet announcement day ;)
[19:11] <Neko> except it's more like a weekend. Google IO is the "we weren't ready at CES" fallback. But they do tend to announce them all at once to get one-up on each other, at CES, and then go silent (and usually don't produce) for the rest of the year.
[19:11] <Neko> Snark, so you gotta wait until January basically
[19:12] <Neko> the "new batch" came out already, got zero traction because the Nexus 7+10 beat the shit out of them.
[19:38] <Snark> ok
[19:44] <lilstevie> and asus, who are usually pretty vocal about their refreshes haven't done one yet, probably cause their weird lifecycle with tf201/tf300t/tf700 + n7
[21:16] <angeloc> Hi guys, I'm building a minimal image for sabre lite
[21:17] <angeloc> everything boots correctly, but cannot make ethernet working
[21:18] <angeloc> there is no eth0, and ifup eth0 raise an error
[21:18] <angeloc> bootlog shows no signs of ethernet device?!
[21:20] <angeloc> ogra_: have you some hints?
[21:34] <angeloc> anybody here?
[21:46] <angeloc> I think I solved my problem
[21:46] <angeloc> it related to an invalid mac address in  uboot
[21:47] <angeloc> bug 817315
[21:47] <ubot2> Launchpad bug 817315 in Linaro U-Boot "eth0 doesn't get a valid MAC address on startup" [High,Fix released] https://launchpad.net/bugs/817315
[21:48] <angeloc> bye, thank you