[04:42] <sim590> Anyone here using the TF101 under ubuntu or any linux distro? I'm wondering if you get in/out errors with file system on the micro SD card
[04:48] <infinity> sim590: That's going to be an issue with the card, not the OS.
[04:55] <sim590> infinity: I know. I'm presently runnin Debian on my tf101 with the SD card (in the keyboard). I'm having input/output errors and I suspect the reason would be the use of the SDcard port in the keyboard.. the connection could be interrupted sometimes because of the lack of stability between the keyboard and the tablet
[04:56] <sim590> so, I wanted to verify this hypotesis by asking people if they're having problem with the micro SD card (not in the keyboard) so that would solve my problem if I would use the micro SD card instead
[04:56] <infinity> sim590: Oh, yeah, I've heard bad things about the keyboard SD slot.
[04:56] <infinity> (Second-hand, since I don't own a transformer, but you wouldn't be the first to complain about it)
[04:57] <sim590> ok. I guess I'll try the micro SD card and pray for no problems.
[04:58] <sim590> Thanks for your time to think about my problem!
[04:58] <lilstevie> sim590, only if you ever let the device sleep
[05:02] <sim590> lilstevie: ok.. I thought that I have experienced that kind of problem too with my configuration
[05:02] <sim590> may be I can program something to make it shutdown instead of sleeping each time it wants to sleep
[05:03] <lilstevie> or tell it not to sleep :p
[05:03] <sim590> yeah, but if it runs out of battery..
[05:03] <sim590> it's going to hibernation
[05:03] <sim590> and I guess that would be bad too
[05:03] <lilstevie> it won't hibernate
[05:04] <lilstevie> it will shutdown
[05:05] <sim590> oh yeah right I remember.. it happenned to me once.. It shuts down but not in a kind way if I remember
[05:06] <sim590> like if there was no protection configured so that it would just run out of batery and shutting down without writing to the filesystem and journal
[05:06] <sim590> so we gotta e2fsck afterwards
[05:09] <sim590> Ok, so I guess I'll buy a micro sd card tommorrow wishing that everything goes well then. Thanks everyone! I hope not to see you again for that matter but other projects may be! ;)
[08:12] <dholbach> good morning
[08:19] <nils_> good morning
[08:21] <nils_> I have tried the nexus installer again. It works now ok in portrait mode. I only had to restart as the keyboard didn't work at the first go.
[08:23] <nils_> also I have noticed there are two bluetooth icons in the top notification bar. I don't remember seeing two before.
[09:48] <ogra> nils_, yeah, we are moving to a new bluetooth indicator, the old one wasnt removed yet
[09:49] <ogra> (the other bugs with the installer are known and being worked on)
[12:01] <phlipped> Hello
[12:11] <phlipped> I have a BeagleBoard-XM
[12:11] <phlipped> I've downloaded 12.04 Server image for OMAP3 - ubuntu-12.04-preinstalled-server-armhf+omap.img.gz
[12:11] <phlipped> unzipped and dd'd it to a 4Gb MMC card
[12:11] <phlipped> But it doesn't boot
[12:12] <phlipped> get's stuck at ...
[12:12] <phlipped> Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
[12:13] <phlipped> This isn't too surprising, because there is no /boot/uImage on the second partition of the MMC
[12:13] <phlipped> So I'm wondering ...
[12:13] <phlipped> Is this a bug?
[12:14] <ogra> this is definitely not something the ubuntu images do print
[12:14] <phlipped> Also, uboot tries to read uEnv.txt, not boot.scr
[12:14] <ogra> thats the default, yeah
[12:15] <phlipped> yet there's a boot.scr in the FAT partition
[12:15] <phlipped> I don't think uboot is even reading it
[12:16] <ogra> yes, it shouldnt
[12:16] <phlipped> oh ... so why is it there?
[12:16] <ogra> the "Loading file "/boot/uImage" from mmc device 0:2 (xxa2)" is simply not something an ubuntu image would print though
[12:17] <phlipped> no, it's not
[12:17] <ogra> so check if you accidentially dd'ed to the device (not to a partition) so that an old bootloader partition is around
[12:17] <phlipped> it's uboot pringint it
[12:17] <ogra> err, if you accidentially *not* dd'ed to the device
[12:18] <phlipped> definitely dd'd to the device
[12:18] <ogra> well, the ubuntu uboot setup doesnt load anything from a /boot dir and doesnt print such stuff
[12:19] <ogra> so there is something wrong with your SD
[12:19] <ogra> (did you change uEnv.txt, preEnv.txt or boot.scr from the defaults ?
[12:19] <ogra> )
[12:20] <phlipped> I've checked the img file I downloaded from Ubuntu (and checked the hash too), and inspected the partitions in the image file
[12:20] <ogra> right, but did you change anything ?
[12:20] <phlipped> They are the same files inside the image
[12:21] <phlipped> no didn't change anything
[12:21] <ogra> weird ... these images get tested before release ... quite a lot actually
[12:21] <phlipped> yeah, that's what I'm confused about
[12:21] <phlipped> I've downloaded it a second time just to be sure
[12:21] <ogra> it could indeed be that your XM is to new for the shipped kernel ...
[12:22] <ogra> but that still wouldnt explain why uboot prints such stuff
[12:22] <phlipped> Perhaps, but it's actually pretty old - a year or two
[12:22] <ogra> and it would then rather hang after the kernel was loaded
[12:22] <ogra> instead of searching in a non std place for it
[12:22] <phlipped> It seems to me that the problem is the default boot script is trying to load a file form /boot/uImage
[12:23] <phlipped> from*
[12:23] <phlipped> the boot script would get modified if uboot would read boot.scr
[12:23] <phlipped> but it doesn't
[12:24] <phlipped> This guy http://elinux.org/BeagleBoardUbuntu#boot.scr_-.3E_uEnv.txt shows a way where you can point uboot back to boot.scr by dropping in a small uEnv.txt
[12:25] <phlipped> I tried this and it looks like everything works again
[12:25] <ogra> thats wrong
[15:15] <turbo_ac100> janimo, what's the status of ac100 daily-preinstalled? Are there still changes to the image like newer kernels or similar?
[15:15] <janimo> turbo_ac100, no work done on newer kernels
[15:15] <janimo> the changes are from regular package updates only
[15:16] <turbo_ac100> so same version as 12.10 then? Is this the newest one?
[15:19] <janimo> turbo_ac100, yes
[15:19] <janimo> turbo_ac100, do you need a newer kernel for some specific reason?
[15:21] <turbo_ac100> janimo, well, I asked this on #ac100 some time ago. But my problem with the 12.10 kernel compared to the 12.04 one is that I couldn't set the amount of RAM used for graphics.
[15:22] <turbo_ac100> I reduced the mem to ~8-12 Mb in 12.04 and it was 64 or similar in 12.10. I downgraded.
[15:23] <turbo_ac100> And in 12.04 cdc_ether doesn't work.
[15:23] <ogra> did you file bugs ?
[15:24] <turbo_ac100> Lemme check
[15:25] <turbo_ac100> about cdc_ether definitely no, because #ac100 said it wouldn't build so i didn't bother
[15:27] <turbo_ac100> mem neither. It was common sense in #ac100 that the "old way" of using kernel-cli doesn't work anymore, nobody knew about an alternative
[15:44] <turbo_ac100> filed a bug about the memory now. https://bugs.launchpad.net/ubuntu/+source/linux-ac100/+bug/1116380
[15:44] <ubot2> Ubuntu bug 1116380 in linux-ac100 (Ubuntu) "Video Mem too much and not changeable trivially" [Undecided,New]
[15:44] <turbo_ac100> hehe
[16:04] <ogra> hrw!!!
[16:04] <ogra> armsoc !!!!
[16:04] <hrw> yes
[16:04] <hrw> someone digged it out of NEW
[16:15] <hrw> ogra: time to pdebuild new kernel and send to NEW as well
[16:15] <ogra> ++
[16:15] <ogra> i'll have to move to a sane install at some point
[16:16]  * ogra is still on the upgraded chrubuntu
[16:16] <mcurran> What's the difference between project and "ubuntu for ARM"?  Was this project built from the beginning with an intention of running in a chroot env.?
[16:16] <ogra> parse error ?
[16:16] <hrw> mcurran: rephrase?
[16:16] <hrw> ogra: never used chrubuntu
[16:17] <mcurran> I believe there would be huge market for handheld devices if ubuntu could be dual/multi-booted.
[16:17] <mcurran> ie. run natively
[16:17] <ogra> well, it was the variant that was around when i got my chromebook :)
[16:17] <hrw> mcurran: I never used ubuntu in chroot on arm devices
[16:17]  * ogra does all the time for building for different releases
[16:17] <ogra> but that doesnt differ from what i do on x86
[16:18] <hrw> ogra: but you do ubuntu-in-chroot under ubuntu so it does not count
[16:18] <ogra> mcurran, all official ubuntu arm images are native
[16:18] <ogra> hrw, ah, yeah, i didnt think about android crap setups that people might do
[16:18] <ogra> :)
[16:18] <hrw> mcurran: most of customer devices have crazy bootloader setups
[16:18]  * ogra doesnt touch such stuff
[16:19] <hrw> neither do I
[16:19] <hrw> mcurran: which device you want to run ubuntu on?
[16:20] <Tassadar> I have ubuntu chroot in Android, but it is the same installation which I also dual-boot, which is kinda great :)
[16:20] <ogra> yeah, but doesnt help the purpose of the n7 image much :)
[16:20] <ogra> it heps endusers to get a crappy UI though ;)+
[16:21] <ogra> *helps
[16:21] <Tassadar> not really, but I had debian in there before because native ssh in terminal emulator is often better than those android apps, now I at least don't have two installations
[16:21] <ogra> (alongside android)
[16:22] <ogra> did you fix the kernel upgrade issues btw ?
[16:22] <Tassadar> yes
[16:22] <ogra> awesome, how ?
[16:23] <Tassadar> I just create the initrd symlink during installation so the first boot works, and after the setup it is managed by Ubuntu, so it's okay.
[16:24] <ogra> you dont just set FLASH_KERNEL_SKIP ?
[16:24] <ogra> that wouldnt need any additional changes at all
[16:25] <Tassadar> I also had to disable flash-kernel by "export SKIP_FLASH_KERNEL=1"(or whatever is the right export), because if I do "hold" on uninstalled flash-kernel, it is removed during the setup wizard for whatever reason
[16:26] <ogra> yeah, you should be able to just add it to /etc/environment
[16:26] <Tassadar> that's what you said before, and that's what I did, thanks :)
[16:26] <ogra> (doesnt need "export" i thinnk)
[16:26] <Tassadar> yeah
[16:26] <Tassadar> ogra: I was talking about initrd, because the symlink is not created in the daily image, so I searched for "initrd-*" file instead of using the symlink
[16:26] <Tassadar> which was kinda dumb :/
[16:26] <ogra> great, so we can at least rely on the fact that people filing bugs have the right kernel
[16:31] <Tassadar> well, I can't be sure everybody properly updated
[16:31] <Tassadar>  but I think they did
[16:31] <hrw> ok, kernel sent to pbuilder
[16:32] <Tassadar> otherwise flash-kernel would overwrite their Android, which is kinda good reason to check the XDA thread
[16:32] <Tassadar> and the problem was only if they had older installation and new kernel was installed via apt-get dist-upgrade
[16:32] <Tassadar> if they got newer image, it should be okay
[16:33] <Tassadar> but anyway, sorry if it causes any false bugs :(
[16:33] <ogra> well, it causes bug noise for bugs that have been long fixed, not more
[16:57] <hrw> ogra, infinity, janimo: linux-chromebook sent to NEW
[16:58] <ogra> \o/
[16:58] <janimo>  /\
[16:58] <diwic> hrw, hey, have you bothered verifying your chromebook ucm stuff? I e flipping the SRU to verification done
[17:02] <diwic> hrw, https://bugs.launchpad.net/bugs/1085392
[17:02] <ubot2> Ubuntu bug 1085392 in Cross distro support for Samsung Chromebook (ARM based) "Merge Chromebook UCM profiles into ALSA packages" [Critical,Triaged]
[17:05] <hrw> diwic: was overloaded with other stuff. And I lost any hope on 'ubuntu on chromebook' lusers
[17:06] <diwic> hrw, fair enough. I have nothing else in the pipeline for SRUing alsa-lib/alsa-utils right now, but if I do, it would be stupid to already have a pending SRU for it
[17:07] <diwic> so it's not urgent
[17:07] <diwic> hrw, just mildly annoying :-)
[17:07] <hrw> diwic: good point.
[17:07] <hrw> diwic: good thing is that my changes do not affect other devices
[17:11] <diwic> all right, have a good evening
[17:40] <infinity> hrw: How much scary code on top of a 3.4.0 vanilla is in that chromebook, and how carefully am I going to have to review it for licensing oopses? :P
[19:06] <mjrosenb> can anyone help me get ubuntu on an sd card on my chromebook?
[19:38] <purezen> Hey guys..!! If I install Ubuntu on the samsung ARM chromebook.. will I be able to carry on my usual compilation tasks..? such as Android development, python scripting, C++...?
[19:38] <infinity> Sure.
[19:41] <purezen> infinity: You mean.. all of them..?
[19:41] <infinity> purezen: Well, Android development could depend on how you currently do it, and things might change.
[19:41] <infinity> As in, you can't use an x86 SDK on an ARM machine (obviously).
[19:41] <infinity> But python, C++, whatever, Ubuntu is self-hosting, so it can clearly build for any language.
[19:42] <purezen> infinity: Yeah..:) so the ARM version available on the site will do the job..?
[19:42] <infinity> purezen: Don't see why not.  I don't do Android development, though.
[19:42] <purezen> infinity: Ok.. didn't know that..:) never tried Linux on ARM yet..
[19:43] <purezen> infinity: Ok..
[19:43] <infinity> Well, stop calling it "Linux on ARM", and just call it "Linux", and you'll be doing well.
[19:43] <purezen> infinity: Ok.. even better..:)
[19:43] <infinity> The underlying architecture should make almost zero difference, unless you're trying to run precompiler binaries for the wrong CPU. :P
[19:43] <infinity> precompiled*
[19:45] <purezen> infinity: Ok.. that's great.. cause I am planning to get it.. and it'd be a big decision for me..
[19:46] <drizzy> i wish there was flash support for arm
[19:46] <drizzy> i have 32gb and i don't wanna use it all on music
[19:47] <drizzy> 32gb of storage
[19:47] <drizzy> actually like 20gb
[19:47] <drizzy> cause it's used up already
[19:47] <drizzy> on apps on the other partition
[19:47] <purezen> So anything I'd loose on Linux on one.. from a developers viewpoint..?
[19:48] <infinity> purezen: Compared to...?
[19:48] <infinity> purezen: You mean compared to running ChromeOS?
[19:48] <purezen> No.. no..
[19:48] <drizzy> heh
[19:48] <purezen> I mean the usual x64 processors..?
[19:49] <infinity> Speed, and proprietary software.
[19:49] <infinity> (See above with drizzy complaining about Flash)
[19:49] <drizzy> that's my only complaint
[19:49] <drizzy> no flash
[19:49] <drizzy> i use google play music
[19:49] <drizzy> it has like 20,000 songs
[19:49] <drizzy> if i put 20,000 songs on my nexus 7
[19:49] <drizzy> i'll be fucked
[19:50] <drizzy> with storage problems
[19:50] <purezen> infinity: Ok.. didn't know that..
[19:50] <drizzy> i guess i can use my external hdd
[19:50] <purezen> drizzy: Hey.. get it..:)
[19:50] <drizzy> for music
[19:50] <drizzy> i wonder if there's a html5 streaming service for cloud stuff?
[19:51] <drizzy> other then youtube
[19:51] <drizzy> and not mega.co.nz
[19:51] <drizzy> i'm so against kim dotcom
[19:57] <purezen> Hey.. I can't get any info. on the Chromebook being used for android development.. can anyone confirm here..?
[19:59] <infinity> purezen: If they offer an ARM SDK (ie: something that isn't an x86 cross-compiler), it should work.
[20:01] <purezen> infinity: Ok.. java shows an installer for ARM (there' one there right..?).. but I can't figure out if Android does the same..
[20:02] <purezen> infinty: can you tell from this: http://developer.android.com/sdk/index.html..?
[20:06] <infinity> purezen: The Sun Java on ARM isn't armhf.
[20:07] <infinity> purezen: But openjdk is in Ubuntu, most people who think they need Sun Java are wrong.
[20:07] <drizzy> there's not a android sdk for arm on that page purezen
[20:07] <drizzy> especially for the adt
[20:08] <purezen> infinity: Ok.. that'll do for the Java compilation part..:)
[20:08] <drizzy> adt bundle*
[20:08] <purezen> drizzy: Ok..
[20:08] <drizzy> although
[20:08] <drizzy> i wonder if you could run a vm on top of linux...
[20:08] <drizzy> wait, no it's stiill not x86
[20:09] <drizzy> i was gonna say run windows in a vm
[20:09] <drizzy> but no go
[20:10] <purezen> drizzy: so eclipse and stuff (android development image..?) is dependent on the platform..?
[20:10] <purezen> drizzy: or which part is..?
[20:11] <drizzy> i think you can use eclipse ide on arm
[20:12] <drizzy> let me see if i can install it
[20:12] <drizzy> i'm having problems with repos 404'ing
[20:13] <drizzy> anyone else on ubuntu-arm platform having these issues currently?
[20:13] <drizzy> i was trying to install audacious earlier
[20:13] <Tassadar> apt-get update is not helping?
[20:13] <drizzy> cause i fucked up my last ubuntu
[20:13] <drizzy> nope
[20:13] <drizzy> Tassadar: i did that earlier
[20:13] <drizzy> as soon as i finished installing
[20:13] <drizzy> i thought it was the wifi host
[20:13] <drizzy> so i switched networks
[20:14] <drizzy> i thought they were getting tired of me using up all their bandwidth
[20:14] <drizzy> but i'm getting the same from this wifi network
[20:14] <drizzy> purezen: eclipse is installing
[20:15] <purezen> drizzy: K..:)
[20:15] <Tassadar> android SDK is not only java, it uses native tools too
[20:15] <Tassadar> maybe it can be built for arm? dunno
[20:15] <drizzy> nexus7 32gb + otr usb + 4 port hub + usb keyboard + usb mouse = $300 awesome laptop
[20:16] <drizzy> just reminded myself to join a channel
[20:16] <drizzy> lolz
[20:20] <purezen> drizzy: so, the thing stopping here is the.. Platform image..?
[20:21] <drizzy> platform image for ubuntu ?
[20:22] <Tassadar> purezen: Android SDK does not use just java
[20:24] <purezen> drizzy: I meant.. corresponding to which the compilation takes place.. (maybe poorly expressing though..).. just guessing.. or what's stopping the ADK from being used then..?
[20:24] <purezen> Tassadar: ok..
[20:28] <purezen> Ok.. thanks guys for all the info.. Gotta go now..
[20:28] <purezen> BBye..:)
[20:28] <hrw> infinity: all new files have gpl headers in them
[20:29] <infinity> hrw: That's comforting.
[20:30] <hrw> patch against 3.4 is 9.8MB but looks strange as it removes 7MB
[20:30] <hrw>  1230 files changed, 13567 insertions(+), 257356 deletions(-)
[20:31] <hrw> have to check did I did it proper side
[20:32] <hrw> yep.
[20:32] <hrw> will read whole patch to confirm
[20:48] <drizzy> brb ditching xchat
[20:50] <hrw> infinity: ok. went though that 7MB - gpl headers in 99% of files
[20:50] <hrw> some had bsd like headers (atheros driver)