[01:25] <lilstevie> infinity, ok
[01:25] <lilstevie> I did notice it only happens on HF
[01:26] <lilstevie> precise updated from oneiric doesn't give me the suspend warning
[01:26] <lilstevie> but the hf precise image I have on my sdcard does
[02:01] <michaelh1> Hey, does anyone know who in Ubuntu creates the ARM UEC images http://uec-images.ubuntu.com/precise/current/ and the tool used?
[02:10] <infinity> lilstevie: That's probably less to do with el versus hf and more to do with upgrade versus fresh, I'd guess.
[02:11] <infinity> lilstevie: As in, maybe the old gnome-power-manager got it right, and its settings were carried over on upgrade (thanks to them being in your ~)
[02:11] <infinity> lilstevie: Could test that theory with your old ~ on a fresh precise/hf image, probably.
[02:12] <infinity> michaelh1: Not sure exactly where those come from, you might try asking smoser.
[02:13] <lilstevie> infinity, fair enough, oneiric never displayed the battery stats correctly anyway (stupid android driver) but the new power-manager or upower compensates
[02:14] <lilstevie> infinity, I guess the other bug I have experienced is pulse audio crashing
[02:14] <michaelh1> infinity: ta, I'll send him an email
[02:15] <lilstevie> had to remove pulse just for lightdm to not die
[02:16] <twb> meh, that just reinforces my low opinion of pcmanfm's work
[02:20] <lilstevie> twb, ?
[02:30] <twb> never mind
[02:31] <twb> (pcmanfm makes most of the LXDE bits)
[02:37] <lilstevie> the issue isn't lightdm it is pulseaudio
[02:37] <twb> Yeah well I like lennart even less :-)
[02:37] <lilstevie> any process that outputs sound with it will either crash, or go haywire
[02:42] <infinity> lilstevie: Reproduce, file bugs, etc.
[02:42] <infinity> lilstevie: Better still if you can reproduce on x86 too, but if it really is arm-specific, we should still deal with it. :P
[02:43] <lilstevie> infinity, ok, I just don't know exactly how to get the bug, or reproduce bug, it is probably my kernel
[02:43] <infinity> lilstevie: Well, if it's your kernel, I might care less about a bug filing. :P
[02:43] <lilstevie> I can reliably reproduce on both tf101 and tf201
[02:43] <lilstevie> but it would have been observed on the panda
[02:44] <lilstevie> or well, any device :p
[02:44] <infinity> Speaking of the TF... Are we still in "no way in hell" land on trying to do a unified -tegra kernel?
[02:44] <lilstevie> well, with mtype hacks we could
[02:44] <lilstevie> someone did something creative with boot.img creation that dynamically patched the mtype
[02:45] <infinity> That sounds vile.
[02:45] <lilstevie> heh
[02:45] <lilstevie> yeah
[02:45] <infinity> Wait, binary patched the kernel, or just mangled something else in the abootimg?
[02:45] <lilstevie> I have no idea
[02:45] <lilstevie> I wasn't too interested cause it sounded vile
[02:45] <lilstevie> :p
[02:45] <infinity> Cause if we could get one KERNEL to work, but just needed different boot images, that's easily done.
[02:46] <lilstevie> let me check
[02:46] <lilstevie> yeah, if it just mangles abootimg I'm sure kernel-img.conf could have the device mtype
[02:46] <infinity> I'd happily ship two boot images (and let flash-kernel sort it for upgrades), if we could have a unified kernel.
[02:46] <lilstevie> yeah
[02:46] <infinity> flash-kernel, not kernel-img.conf, but yeah.
[02:47] <lilstevie> well I am almost certain with a little work that tf101 and tf201 should be able to share a kernel
[02:47] <lilstevie> that is tegra2/tegra3
[02:47] <infinity> And AC100, and that Toshiba tablet that was similar, and...? ;)
[02:48] <infinity> Well, anything that's fastboot+tegra should, in theory, be doable.  One would hope.
[02:48] <lilstevie> I mean without hacks
[02:48] <lilstevie> tf101 does not fastboot
[02:48] <infinity> uBoot tegra platforms (like the Trimslice) might be a bit more of a pipe dream for a unified kernel.
[02:48] <infinity> Oh, tf101 doesn't?
[02:48] <lilstevie> no, well it uses the "fast boot" bootloader
[02:48] <infinity> abootimg kinda implies fastboot, doesn't it?
[02:48] <lilstevie> but there is no fast boot access
[02:49] <lilstevie> nvflash access is your only way of manipulating images
[02:49] <infinity> Well, sure.  That's true of the ac100 as well.
[02:49] <lilstevie> also Trimslice isn't that pipedream
[02:50] <lilstevie> I recently saw on the u-boot mailing list a bootz patch
[02:50] <lilstevie> to boot zImage
[02:50] <lilstevie> and really
[02:50] <infinity> Yeahp.
[02:50] <infinity> Don't know if we'll land that for precise.
[02:50] <lilstevie> that would solve the problem
[02:50] <infinity> And even if we do, probably won't go an ditch all th uImages.
[02:50] <lilstevie> certainly not for precise
[02:50] <infinity> But it's a sane way forward.
[02:50] <lilstevie> precise is only like what a week away
[02:50] <lilstevie> :p
[02:50] <lilstevie> well a few weeks
[02:50] <infinity> A month.
[02:50] <infinity> But yeah, "soon".
[02:51] <infinity> Too soon.
[02:51] <infinity> These cycles always seem so long for non-LTS releases, and so damn short when I'm trying to make everything "just right" for an LTS. :/
[02:52] <lilstevie> https://github.com/astarasikov/mkbootimg-mtype-hacked
[02:52] <lilstevie> takes mtype as an arg
[02:53] <lilstevie> looks like it patches the zImage
[02:54] <infinity> Yeah, I just got there.
[02:54] <infinity> So much for that idea.
[02:54] <lilstevie> I guess the only other way is generic board that heuristically determines the platform
[02:55] <infinity> I wonder if one could parse mtype from the cmdline, or if we need it too early to be able to.
[02:55] <lilstevie> hm
[02:55] <infinity> Well, obviously, the real solution is being able to detect, yes.
[02:55] <infinity> But I'm trying to think of quick hacks. ;)
[02:55] <lilstevie> heh
[02:56] <infinity> cmdline parsing happens pretty damned early, though.
[02:56] <infinity> So, that should be doable.
[02:56] <lilstevie> yeah the question is if it happens quite early enough
[02:56] <lilstevie> there are certain fuse structures that could be used for the tf101
[02:57] <infinity> Well, given that you need it early enough for nosmp to rewrite spinlocks, and for mem= to blacklist regions, it's got to be... Early.
[02:57] <lilstevie> heh actually that is a good point
[03:02] <lilstevie> when is memory blacklisting done?
[03:03] <lilstevie> actually I guess I should find the routine that parses the command line
[03:20] <lilstevie> infinity, this may be viable
[03:21] <lilstevie> infinity, it looks like the command line is parsed before mtype is processed
[03:22] <lilstevie> so using that you could add something like mtype= and patch it
[04:00] <lilstevie> infinity, I guess the biggest question right now is how many tegra devices do we have
[04:00] <lilstevie> and how many mtypes
[04:01] <lilstevie> cause ac100 is harmony mtype, tf101 is ventana, and tf201 is cardhu
[04:15] <student_needing_> can someone help me get ubuntu to boot on my beaglebone? i make an sdcard with the premade 11.10 image and looking at screen i am stuck on "PHY 0:01 not found" and it won't go any farther
[04:28] <infinity> lilstevie: As long as they don't have any mutually exclusive drivers, then, this may be entirely viable.
[04:29] <lilstevie> infinity, well thats where we could probably hack around a bit
[04:29] <infinity> student_needing_: You might want to try a 12.04 omap image.
[04:29] <infinity> student_needing_: Though I don't have a Beaglebone, so I can't be much help.
[04:29] <lilstevie> try to make it a little more modular
[04:30] <student_needing_> i can try out the new image, didn't know how stable it is though
[04:31] <infinity> student_needing_: In general, I'm happier with precise than with oneiric.  And this is a good time to avoid churn, as we're in a beta freeze, so the most recent dailies are fairly sane.
[04:31] <student_needing_> sounds good, downloading that image right now
[04:45] <student_needing_> one other question about ubuntu on the beaglebone, does it have access to the gpio pins like angstrom would, being able to read and set values on them?  is it the same process as angstrom?
[04:58] <michaelh1> student_needing_: here's my notes on the BeagleBone: http://juju.net.nz/michaelh/notes/bone.html
[05:36] <twb> I have a PHP weenie who is currently running PHP lucene and OOMing the resources he has been allocated.
[05:36] <twb> He wants to migrate to "solr", but AFAICT that needs a full JVM *and* tomcat on top of that, so I'm not convinced it'll be much of a win.
[05:36] <twb> Oops, this isn't #ubuntu-server
[05:36] <lilstevie> lol'
[05:52] <need_help> so im still trying to boot my beaglebone into ubuntu and im running into a lot of trouble
[05:53] <need_help> right now on /dev/ttyUSB0 when i press a key it tries to start up ubuntu on /dev/ttyUSB1 (i'm using screen into both) but always fails, gets stuck at "PHY 0:01 not found"
[05:54] <need_help> now my /dev/ttyUSB1 has a login prompt for Ubuntu precise but doesn't respond to keystrokes, only /dev/ttyUSB0 responds to keystrokes
[05:56] <need_help> i also just saw on /dev/ttyUSB1 that i get this error a little before the other error - "init: ureadahead main process (176) terminated with status 5"
[10:32] <hrw> http://marcin.juszkiewicz.com.pl/2012/03/26/ubuntu-12-04-precise-and-cross-compilation-of-arm-kernels/ - refreshed instructions for precise
[10:36] <LetoThe2nd> hrw: ah nice
[10:37] <LetoThe2nd> hrw: does dpkg-buildpackage in this context accept a local .config, or does it have to be added to some patchset before?
[10:39] <ogra_> hrw, you should add a step "make your changes here" or some such, i doubt anyone will just rtebuild the kernel package for fun without making any changes
[10:39] <LetoThe2nd> ogra_: thats the consequence ;)
[10:39] <hrw> ogra_: that part is left for reader. I do not remember when last time I understood how ubuntu kernels are maintained
[10:40] <hrw> I prefer 'make uImage modules -j44'
[10:40] <ogra_> LetoThe2nd, fakeroot debian/rules editconfigs; dpkg-builpackage -b -aarmhf
[10:40] <LetoThe2nd> ogra_: *note*
[10:40] <hrw> ogra_: feel free to add comment ;)
[10:40] <ogra_> (that brings up menuconfig with the configs from the debian dir)
[10:41]  * suihkulokki finds it annoying how debian/ubuntu kernels make a simple kernel build process very complicated
[10:41] <suihkulokki> although I understand why it ends up being so complex
[10:41] <ogra_> suihkulokki, how is that complicated ?
[10:42] <hrw> ogra_: providing own kernel config needs more work then it is worth?
[10:42] <LetoThe2nd> same here, given the addition from ogra i see no more complexity than in a manual biuld.
[10:42] <ogra_> fakeroot debian/rules editconfigs; dpkg-builpackage -b -aarmhf .... vs. .... make menuconfig; make ... i dont see much difference apart from the convenience of having a package with the first one (which also brongs the proper postinst handling for flash-kernel etc)
[10:43] <ogra_> *brings
[10:43] <hrw> flash-kernel... I hope that it will die ugly death sooner the later
[10:43] <ogra_> it never will (sadly)
[10:43] <ogra_> but it will get better in 12.10
[10:44] <ogra_> well, fsvo never ... once we have arm support in grub it wont be flash-kernel but update-grub ;)
[10:44] <hrw> finally rewrite?
[10:44] <ogra_> yeah
[10:44] <ogra_> its already in debian testing ... but needs some massive changes for ubuntu
[10:44] <hrw> ogra_: for me it can be ubmaumba even as long as it works the same on each machine
[10:44] <ogra_> thats why i say grub ;)
[10:45] <hrw> and that on mx53 it cares of uImage/uInitrd but not boot.scr which it cares of on omap3 with saying 'not supported' on pandaboard at same time
[10:45] <ogra_> well, get the venros on UEFI and you wont have these probs ;)
[10:45] <ogra_> *vendors
[10:46] <suihkulokki> then we'll have all the problems we can read about in matthew garrets blog
[10:46] <suihkulokki> ya!
[10:46] <ogra_> indeed, a new system introduces new issues
[10:47] <ogra_> but it wont differ that much from x86 anymore, will be easier to adapt for people
[10:56] <lilstevie> is there any new documentation on building packages for kernel
[15:11] <GrueMaster> janimo`: Question on mongodb.  There is no arm build, and I don't see in launchpad where arm is even enabled for it.  Can you check that?
[15:17] <janimo`> GrueMaster, I have been working on mongo/arm on and off for the past weeks
[15:17] <janimo`> trying to make and send patches upstream
[15:17] <GrueMaster> ok.
[15:18] <janimo`> at the moment there's no ARM pkg enabled - although I consider adding my WIP to Precise to get the arm binaries rolling at least, and maybe the finishing touches as SRU
[15:18] <janimo`> GrueMaster, has it come up in server talks?
[15:18] <GrueMaster> Yes.  Some of the tests we are working on run on mongodb apparently.
[15:19] <janimo`> ok, I'll upload my changes these days - but mongo on ARM will FTBFS due to failed tests
[15:19] <janimo`> anyway good to know there is interest I'll boost the prio
[15:20] <GrueMaster> Yea, I just double-checked.  There is interest, but no rush.
[15:34] <steev> how... how do you change font settings in 12.04?
[15:34] <steev> specifically, need to see if subpixel AA is on, and if so, disable it.
[15:56] <ogra_> steev, i dont think you easily can switch that around anymore (gnome upstream dropped it), you can switch the fontsize in the acceesibility settings though
[16:11] <steev> ogra_: hm, okay
[16:12] <steev> ogra_: well in gnome3, you can use gnome-tweak-tool, would the same work in unity?
[16:12] <ogra_> no idea, try it :)
[17:47] <steev> ogra_: nope, gnome-tweak-tool requires gnome-shell 3.3.2 which won't be installed
[18:02] <steev> blargh
[18:02] <steev> no gnome-tweak-tool, and no dconf-editor
[18:17] <steev> ogra_: okay, looks like i can do it manually with gsettings, would be nice to have dconf-editor or gnome-tweak-tool for a pretty gui though
[18:18] <ogra_> well, nothing stops you from installing it :)
[19:50] <steev> ogra_: gnome-tweak-tool requires gnome-shell but gnome shell can't be installed.  dconf-editor doesn't seem to exist
[20:25] <micahg> steev: wfm, is your mirror and apt-cache up to date?
[20:40] <steev> micahg: which one works?
[20:41] <micahg> oh, arm, sorry :)
[20:41] <micahg> yeah, it's broke ATM
[20:48] <steev> micahg: no, not arch, i meant which? g-t-t or d-e
[20:48] <micahg> gnome-tweak-tool, but I"m on amd64 (this and the ubuntu+1 channel are right next to each other in my IRC client :))
[20:51] <steev> i'm on precise on the arm box
[20:53] <micahg> steev: you want dconf-tools
[20:53] <steev> micahg: ah, okay
[20:53] <steev> command-not-found didn't suggest it
[20:54] <steev> and apt-cache search dconf-editor didn't show anything either
[21:37] <GrueMaster> steev: I see the package on launchpadlibrarian https://launchpad.net/ubuntu/+source/d-conf/0.11.7-0ubuntu1/+build/3300937  Not sure why it isn't in the pool.
[21:40] <GrueMaster> steev: I just ran apt-get update && apt-cache search dconf-tools and it shows up now.
[21:53] <steev>     GrueMaster right, i searched for dconf-editor
[21:53] <steev> i should have just searched for dconf
[21:53] <GrueMaster> Ah.
[21:54] <GrueMaster> That's ok.  We'll probably rename it in a couple of cycles, just to keep users guessing.  :P
[21:54] <steev> heh
[21:57]  * ogra_ votes for calling it "frank"
[22:00] <GrueMaster> Considering it was called gconf-editor last cycle...
[22:01] <ogra_> no, that was another app
[22:01] <ogra_> (still exists)
[22:02] <GrueMaster> Different app, same function (configuring unity crap).
[22:02]  * GrueMaster needs a break.
[22:12] <steev> GrueMaster: true, but they serve different purposes (upstream at least, dconf is for stuff that's done converted to the new dconf, gconf is for legacy ish)