[00:58] <twb> lilstevie: have you seen this? http://paste.ubuntu.com/770683/
[00:58] <twb> "fakeroot, while creating message channels: Function not implemented This may be due to a lack of SYSV IPC support."
[00:59] <lilstevie> that I have not
[00:59] <lilstevie> twb: also, LP0 fixed
[00:59] <twb> coo
[00:59] <twb> ...l
[01:00] <twb> lilstevie: does "fakeroot pwd" work for you?
[01:01] <infinity> I would hope so...
[01:01] <twb> WTF have I done
[01:01]  * lilstevie doesn't even have fakeroot installed
[01:02] <twb> lilstevie: it's mainly used when building packages
[01:02] <lilstevie> yeah I know
[01:02] <lilstevie> I have it on the trim
[01:02] <lilstevie> where I build my packages
[01:02] <infinity> Who's sending me a trim for Christmas?
[01:02] <infinity> Anyone? :)
[01:02]  * infinity hears crickets.
[01:02] <lilstevie> lol
[01:04] <twb> lilstevie: it works if I update-alternatives and change it to use fakeroot-tcp instead
[01:05] <lilstevie> lol
[01:05] <twb> Which is Bad Juju because IIRC that breaks something else
[01:05] <lilstevie> I currentlly have no wifi on my tf101 so I cant install fakeroot to tell you my result
[01:05] <twb> k
[01:57] <twb> lilstevie: FYI, guy next to me can reproduce fakeroot-sysv issue on his tf101
[01:59] <lilstevie> ok
[02:01] <infinity> twb: Kernel built without sysvipc?
[02:01] <infinity> CONFIG_SYSVIPC=y
[02:01] <infinity> CONFIG_SYSVIPC_SYSCTL=y
[02:02] <infinity> CONFIG_SYSVIPC_COMPAT=y
[02:02] <infinity> Probably want all of those for fakeroot to not be a sad panda.
[02:03] <twb> infinity: I didn't build the kernel
[02:03]  * twb points at lilstevie!
[02:03] <twb> scary monkey style
[02:04] <twb> There's no /boot/config either :-(
[02:04] <doko> \o/ it's done: https://launchpad.net/builders:  armhf	11	empty
[02:04] <twb> Aha, /proc/config.gz tho
[02:04] <twb> Yep, sysvipc is off.  FAIL.
[02:04] <lilstevie> not set
[02:04] <lilstevie> will fix later
[02:04] <twb> No rush, fakeroot-tcp works for now
[02:05] <lilstevie> I really don't give an f right now :)
[02:05] <infinity> doko: \o/
[02:05] <twb> I will have to ring up your girlfriend and tell her bad things about you so she leaves you and you have more time for work
[02:05] <infinity> doko: I'll see if there are any obvious things I can unsnag tomorrow.  And keep an eye on stuff here and there while I'm on VAC.
[02:06] <lilstevie> twb: lol. I don't give an f because I am working on something else on the project right now so that would acomplish nothing
[02:07] <twb> Okey dokey
[02:07]  * twb puts down the phone
[02:08] <twb> No more underground boxing matches with baby seal pups for you
[05:23] <twb> 16:20 <twb> mikef: battery stats per hour, gave it power just after penultimate entry http://paste.debian.net/149276/
[05:24] <twb> So the TF101 (running Ubuntu) has a discharge rate of 12% to 14% per hour (of the onboard battery).  That works out to be about 7.14 hours of life.  The dock is half as much battery again, so that comes to about 10.7 hours of life with my current config.
[05:24] <twb> *without* sleeping or screen blanking on inactivity
[05:25] <twb> brightness is at 157/255 (default at boot time)
[05:33] <twb> lilstevie: ^^
[05:33] <twb> Anybody riced up stuff to save power on the TF yet?  powertop doesn't look to be very helpfu
[05:36] <lilstevie> twb: my average consumption is 10% per hour
[05:36] <twb> The only thing it recommends that I can see is /proc/sys/vm/dirty_writeback_centisecs
[05:36] <twb> Which is 6000 and it thinks 1500 is better, but it isn't
[05:36] <twb> lilstevie: hum
[05:37] <twb> lilstevie: well, I am using an offboard keyboard, and wifi
[05:38] <twb> http://www.lesswatts.org/tips/disks.php et al
[05:38] <lilstevie> I get 19hours 40 with no power management
[05:38] <lilstevie> wifi on
[05:38] <lilstevie> but using the dock keyboard
[05:38] <twb> Be interesting to know what else is different
[05:39] <lilstevie> with LP0 suspend to ram though :p
[05:39] <twb> There is autosuspend for the keyboard power, but if you turn it on, the keyboard won't wake from sleep :-(
[05:39] <lilstevie> you probably don't want to know
[05:40] <lilstevie> also my wake is based off the dock "lid open switch"
[05:40] <twb> Surely the 19.6 hrs doesn't count the hours that it's suspended to ram
[05:40] <twb> In which case suspend to ramdoesn't matter
[05:41] <lilstevie> 19.6hours was without LP0
[05:42] <twb> The dock battery is half the size of the tablet battery, right?
[05:42] <lilstevie> no
[05:42] <lilstevie> same size
[05:42] <lilstevie> identical
[05:42] <twb> Oh, OK
[05:42] <twb> In that case I should get ~14 hours atm
[05:43] <lilstevie> last 4.4h used 1% battery
[05:43] <lilstevie> :)
[05:45] <lilstevie> only issue with LP0 I can see at the moment is the battery does not charge from the dock while in that mode
[05:45] <twb> so you think it's like a car, where the "empty" mark is WAY above the actual empty level?
[05:46] <lilstevie> the dock does not drain past 3%
[05:46] <twb> Well yeah, not counting that
[05:46] <lilstevie> and not "way above"
[05:46] <lilstevie> but still a little bit above
[05:47] <lilstevie> just not all batterys are created equal
[05:48] <lilstevie> batteries even
[05:56] <twb> Is irqbalance useful on tf?
[05:57] <twb> Also for some reason my load average never drops below 1
[06:01] <cmcmanis> Greetings ubuntu-arm, is it a known bug that the current build has EXT4 journal corruption bugs?
[06:01] <twb> cmcmanis: current build on what platform?
[06:01] <cmcmanis> sorry pandaboard
[06:01] <cmcmanis> Got a new Pandaboard-ES and put the current Ubuntu on it
[06:02] <cmcmanis> It corrupts the EXt4 journal and then I have to reboot. I can reproduce by just dding from /dev/zero to a file
[06:04] <infinity> cmcmanis: Define "current Ubuntu".
[06:05] <infinity> cmcmanis: But I have no such issues on my Panda.  Is this running on an SD card?
[06:05] <infinity> cmcmanis: (If so, I'd suspect your SD is dying)
[06:05] <cmcmanis> sorry, the build that is referenced off the pandaboard.org site one sec
[06:06] <cmcmanis> ubuntu-11.10-preinstalled-server-armel+omap4.img.gz
[06:06] <cmcmanis> SD is brand new, kingston class 10
[06:06] <infinity> New doesn't mean much. :/
[06:07] <infinity> I can tell you for sure that a fresh install of oneiric shows no such weirdness on any Pandas here.
[06:07] <cmcmanis> fair enough
[06:08] <infinity> I actually only have on card I've never managed to kill.  And I suspect that's more luck than anything else.
[06:08] <infinity> SD and random access don't really get along.
[06:08] <cmcmanis> true that
[06:08] <infinity> (If you have a USB HDD for your Panda, I'd recomend grabbing a netboot image, stuffing that on an SD, and installing to a hard drive)
[06:09] <cmcmanis> Hmmm that is an interesting idea.
[06:16] <twb> 17:02 <cmcmanis> It corrupts the EXt4 journal and then I have to reboot. I can reproduce by just dding from /dev/zero to a file
[06:16] <twb> That sounds to me more like the filesystem is bigger than the disk or something
[06:16] <twb> Or the blocks where teh journal lives aer toast
[06:17] <lilstevie> twb: it would be the latter rather than the former
[06:17] <lilstevie> cause unless the SD card is <2GB that wouldn't happen
[06:17] <cmcmanis> aye, that would cause it but I've checked the partition multiple times, and can read and write both the first and last blocks (tested using dd)
[06:18] <twb> I just prefer to blame users, not hw :P
[06:18] <cmcmanis> Its and 8g card btw
[06:18] <cmcmanis> It came in a twin pack and I'm putting Android ICS on the other one we'll see if it has a similar issue
[09:22]  * ogra_ scratches head about the eglibc build
[09:25] <ogra_> i wonder why the same package is built on two different builders
[09:36] <ppisati> ogra_: becasue you keep hammering those poor builders and they are revolting againt you now! :)
[09:37] <ogra_> haha
[09:37] <ppisati> ogra_: stop harassing the builders!
[09:37] <ogra_> the hammering seems to have stopped last night
[09:37] <ogra_> queue is largely empty
[09:43] <ppisati> ogra_: btw, did you sort out the ac100 "non booting kernel" problem? i read it could be toolchain related
[10:18] <ogra_> ppisati, well, in the package we have there are some issues with devices having hynix RAM, the micron ones seem to work fine ... with the new checkout that was rolled with gcc 4.6.2 it seems everything is broken
[10:26] <ppisati> ogra_: crap
[10:26] <ogra_> yeah
[13:17] <ogra> hmm, lubuntu-desktop isnt installable yet on armhf
[14:56] <ogra_> ************* REMINDER ARM meeting in #ubuntu-meeting in 5min ******************
[14:57] <infinity> But I don't wanna go to school today mom.
[14:57] <lilstevie> heh
[14:58]  * ogra_ swings the cane 
[14:58] <ogra_> :)
[14:59] <doko> infinity, could you run a check for universe packages not present on armhf, but present on armel?
[15:00] <infinity> suit-diff should work...
[15:00] <infinity> suite, too.
[15:00] <infinity> But meeting time.
[15:03] <infinity> doko: http://lucifer.0c3.net/~adconrad/universe-armel-armhf_differences
[21:07] <kyleN> my oneiric sys has now hung twice, even after scheduler