[07:30] <ppisati> moin
[08:29] <xnox> ppisati: morning. Yeah, overlay works fine here afterall =)
[08:29] <ppisati> xnox: thanks, i saw your email
[08:30] <ppisati> xnox: i'll send a pull req today
[08:30] <xnox> kk.
[08:30] <ppisati> xnox: thanks for testing :)
[08:30] <xnox> \o/ awesome.
[08:30] <ppisati> i realy would like to get my nexus7 back in shape
[08:33] <xnox> ppisati: well, there is a way to repack .bootimg & add preseed and wifi config with the hope for it to come up with wifi network and ssh server installed.
[08:33] <ppisati> xnox: any doc around?
[08:33] <xnox> as i understand it's the screen brightness that is preventing you from installing?
[08:33] <ppisati> xnox: yesterday i played a bit with .img
[08:33] <ppisati> xnox: modified it, repacked and reflashed
[08:33] <xnox> ppisati: http://blog.surgut.co.uk/2013/02/flash-nexus7-like-rock-star.html
[08:34] <ppisati> xnox: but flash didn't go well
[08:34] <xnox> that auto packs a presseed (modify as wanted) & copies network-manager's wifi config.
[08:34] <xnox> this does not have a success-command to install ssh server though. I'll try to add that today for you ;-)
[08:35] <ppisati> lp1126836
[08:35] <ppisati> uh?
[08:35] <ppisati> bug 1126836
[08:35] <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
[08:35] <ppisati> this is exactly my problem
[08:38]  * smb yawns
[08:39] <xnox> ppisati: ouch, I flashed with 11th march image last, and it was fine here with a 16gb wifi model here.
[08:42] <smb> ppisati, You sound like having fun with the n7... not
[08:53] <ppisati> smb: eh
[08:53] <ppisati> xnox: did you try the phablet img?
[08:54] <xnox> ppisati: yeah, that works fine as well.
[08:54] <ppisati> xnox: here too
[08:54] <ppisati> xnox: i can go back to android or to the phablet img
[08:54] <ppisati> xnox: the only one NOT working, is the ubntu desktop one :(
[08:55] <ppisati> xnox: anyhow, coffe, overlayfs pull req and than i'll play with your script
[08:55] <apw> ppisati, how far does it get
[08:55] <ppisati> apw: desktop img on nexus?
[08:56] <apw> ppisati, yes
[08:56] <ppisati> apw: dies after plymouth
[08:56] <ppisati> apw: completely black screen
[08:56] <ppisati> exactly like in lp1126836
[08:56] <apw> ppisati, so the kernel is up and working, does serial work at that point ?
[08:56] <apw> bug 1126836   
[08:56] <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
[08:57] <smb> apw, or even ssh (remember the fb fun)
[08:57] <ppisati> apw: yes, but there's no user defined
[08:57] <ppisati> apw: that's why i need to roll a custom img and flash it
[08:57] <ppisati> apw: it's still an unconfigured ubuntu installation
[08:57] <apw> didn't rtg complain about the same thing, and say that 1/10 reboots it worked and then he could customise it, and then it was fine ?
[08:58] <ppisati> apw: dunno
[08:58] <apw> worth a try
[08:59] <apw> smb, yeah it does feel a little like that, but i don't think we have an old framebuffer in these devices to tickle the issue
[09:00] <smb> apw, true. just something about the symptoms. though clearly can be anything else after and in the bug report ppisati mentions the title sounds like the fs is a problem and mountall
[09:01]  * smb tries to understand the sentence he just wrote
[09:05] <apw> heh
[09:57] <ppisati> back in a bit
[11:26] <apw> ppisati, ok i have my n7 up and working with the latest kernel
[11:26] <apw> ppisati, on the ubuntu desktop image
[11:27] <ppisati> apw: nice
[11:28] <apw> so it must be an installation issue i think
[11:28] <apw> which fits with rtg's experience
[11:31] <ogra_> whats rtg's experience ?
[11:45] <ogra_> apw, ^^
[11:46]  * ogra_ still looks for somoebody that can reproduce ppisati's black screen issue
[11:47] <ppisati> ogra_: rtg has it
[11:50] <ogra_> ppisati, did he also have phablet installed before ?
[11:50] <ppisati> ogra_: dunno
[11:51] <ppisati> ogra_: let's see when he awakes if he can confirm those issues
[11:51] <ppisati> ogra_: btw, people reported it in the past, i asked if they experience it with latest images
[11:51] <ppisati> ogra_: let's see if they respond
[11:51] <ogra_> i'll prepare an initrd for you with init=/bin/bash so you can set a rootpw 
[11:51] <ogra_> i saw your comment on the whoopsie bug, yeah
[11:52] <ogra_> i highly doubt thats related to your issue
[11:52] <tseliot> apw: do you think it would be wrong if I made kmod treat "alias $module_name off" as a "blacklist $module_name"?
[11:54] <tseliot> apw: as it would solve bug #1073062
[11:54] <ubot2> Launchpad bug 1073062 in kmod (Ubuntu) "modprobe: Assertion `kmod_module_get_initstate(m) == KMOD_MODULE_BUILTIN' failed" [Undecided,Confirmed] https://launchpad.net/bugs/1073062
[12:04] <tseliot> apw: I guess it wouldn't be the same...
[12:15] <apw> tseliot, hmmm, thinking
[12:15] <apw> no i don't think it would be the same at all
[12:16] <tseliot> apw: I think we should just make sure that the installation command is set to /bin/true when alias is set to off, as the old module-init-tools did
[12:16] <apw> that might work
[12:16] <apw> we should fix kmod ... sigh
[12:17] <apw> i have a patch here somewhere as well
[12:19] <ogra_> ppisati, use fastboot flash to flash http://people.canonical.com/~ogra/tegra/nexus7/boot-bin-bash.img ....  have a keyboard attached and set a root pw ... then use fastboot flash with http://people.canonical.com/~ogra/tegra/nexus7/boot.img and log in via serial to debug
[12:20] <apw> ogra_, could we not have a default user on these images which is removed when oem-config does its thing
[12:20] <ogra_> apw, no, that woould mean lots of ugly extra hackery
[12:25] <ogra_> apw, oem-config actually drops you to a root shell if it fails so you can do everything you need ... but if you dont have a display at all thats tricky (but also a very special case ... and ut of about 20 people doing installls the last days onlly ppisati (and now rtg)  seemed to have that issue
[12:25] <ogra_> )
[12:26] <apw> bjf also reported it iirc, he was the one who said "keep rebooting it" to solve it
[12:26] <ogra_> how would keep rebooting fix the display ... 
[12:26]  * ogra_ is confused
[12:27] <ogra_> it seems nobody who only had installed the desktop image can reproduce it so i'm still blaming the phablet images until someone reports to see it who only ever had the desktop image installed
[12:31] <ogra_> but lets see what ppisati finds :)
[12:34] <apw> ogra_, that seems unlikely give we zap both flashes with new stuff
[12:35] <apw> ogra_, but as you say ... we'll see
[12:37] <ogra_> well, i suspect the phablet kernel or surfaceflinger get the device in a state that either our kernel or xserver dont get along with
[12:37] <apw> ogra_, even though we go through a flash and full reboot?  i am sceptical
[12:38] <apw> i would love to be able to blame phablet obviously
[12:38] <ogra_> are you 100% the device is completely been powered off ?
[12:38]  * ppisati is reflashin with today's img
[12:39] <ogra_> a reboot will likely not clear everything 
[12:39] <ppisati> and will try to reboot 10 times in a row
[12:39] <ogra_> ppisati, well, it would have been nice if yoou used the above boot.img's to debug the issue with the broken image you had ... 
[12:39] <apw> is there any way to pwoer down that device if you cannot boot it
[12:40] <ogra_> zep, from the bootloader
[12:40] <ogra_> *yep even
[12:40] <ogra_> phablet doesnt power it down completely 
[12:40] <ogra_> even with reboot -p it will still drain the battery as if it fully runs (see the release notes)
[12:42] <apw> quality
[12:43] <ogra_> android :)
[12:50] <smb> lets take the battery out for 5 minutes... oh wait ...
[12:51]  * ogra_ hands smb a hammer
[12:51] <ogra_> nothing we couldnt fix ;)
[12:51] <smb> ogra_, Luckily I am blessed with _no_ pahblet
[13:44] <tseliot> apw: the solution to the problem is much much easier than I thought
[13:47] <apw> tseliot, oh, which is
[13:49] <tseliot> apw: modprobe looks for the module (which in this case is aliased as "off") in /sys and raises an error if it doesn't find it
[13:50] <tseliot> apw: and I wouldn't expect to find anything like "off" in /sys...
[13:52] <tseliot> apw: assert(kmod_module_get_initstate(m) == KMOD_MODULE_BUILTIN);
[13:52] <tseliot> apw: and we shouldn't do this if the alias is "off"
[13:52] <tseliot> that's it
[13:54] <apw> tseliot, right the fix for kmod is pretty simply i think, we should do it for 'null' and 'off'
[13:54] <apw> as those are both official aliases for not doing anything
[13:54] <tseliot> apw: ah, null? Where is it documented?
[13:56] <tseliot> apw: ah, here: http://ccrma.stanford.edu/planetccrma/man/man5/modules.conf.5.html
[13:56] <tseliot> apw: ok, let me rework my patch and then I'll send it upstream to debian
[14:06] <tseliot> apw: shall I do it for things like "alias iso9660 isofs" too?
[14:18] <bjf> apw, since we respun quantal, we need a new lowlatency spun
[14:18] <bjf> ppisati, same for ti-omap4
[14:18] <ppisati> bjf: ack
[14:23] <zequence> apw: Just a reminder: new quantal kernel in ppa:ubuntustudio-kernel/linux-lowlatency-sru
[14:24] <apw> zequence, thanks
[14:25] <apw> tseliot, great thanks
[14:29] <ppisati> ogra_: both in userdata, right?
[14:32] <ogra_> ppisati, no, boot
[14:33] <ogra_> fastboot flash boot boot-bin-bash.img
[14:33] <ppisati> ack
[14:39]  * ogasawara back in 20
[14:49] <rtg_> apw, Linus is pushing Al to include overlayfs
[14:49] <apw> rtg_, yeah i saw indeed.  al seemed to be saying bring them alll on it
[14:50] <rtg_> aufs includes :)
[14:50] <rtg_> included*
[14:50] <rtg_> though I don't think _that_ will happen soon
[14:52] <apw> no i suspect there was more than a little irony in there
[14:53] <rtg_> apw, ah, dentry_open is a new handler. That is why I couldn't figure it out yesterday, I thought it had morphed into atomic_open
[14:55] <apw> rtg_, they did add atomic_open but it has odd semantics
[15:15] <ppisati> ogra_: (WW) TEGRA(0): LVDS-1: Error querying display modes: No such device.
[15:15] <ogra_> no prob
[15:15] <ppisati> ogra_: it's the only warning i see in X
[15:15] <ogra_> thats normal 
[15:15] <ppisati> X is up&running
[15:15] <ppisati> still i got a blackscreem
[15:15] <ppisati> n
[15:15] <ogra_> sudo service luxd stop
[15:15] <ppisati> yep
[15:15] <ogra_> (you still dont have a lamp in your house i suppose ?)
[15:16] <ppisati> nope
[15:16] <ppisati> [compiz] <defunct>
[15:17] <ogra_> aha !
[15:17]  * ogra_ wonders if italians go to bed early then ... no lamps at all ... scary
[15:18] <ppisati> ogra_: not really, but i don't need lamps :)
[15:19] <ogra_> so try something like rm /etc/init/luxd.conf
[15:19] <ogra_> then reboot and see if that changes anything
[15:21] <ogra_> (so we can rule out the backlight from the issue)
[15:22] <ppisati> ogra_: guess what? :()
[15:22] <ppisati> ogra_: :)
[15:23] <ogra_> works ?
[15:23] <ppisati> yes :)
[15:24] <ogra_> ok
[15:24] <ogra_> so that means after phablet was installed 0 is actually 0
[15:24] <ogra_> while with our kernel 0 is actually 40% or so
[15:24] <ogra_> (for the brightness)
[15:24] <ogra_> so something redefines that value in a weird way
[15:25]  * ogra_ will drop luxd for a start ... but thats a bug we need to inspect deeper
[15:25] <ogra_> definitely something between the two kernels
[15:27] <ppisati> mv /etc/init/luxd.conf /etc/init/foorbar.conf
[15:27] <ppisati> reboot
[15:27] <ppisati> and it worked
[15:27] <ogra_> yes
[15:27] <ppisati> i shall try to put it back
[15:27] <ppisati> and see what happens
[15:27] <ogra_> that means the 0 value is different after you installed phablet
[15:27] <ogra_> or the ambient sensor doesnt work anymore 
[15:28] <rtg_> ogra_, is there a config option for the ambient sensor driver ? perhaps it isn't enabled.
[15:28] <ogra_> well, it definitely is, else luxd would never have worked
[15:28] <ogra_> luxd is a dumb script that just shortcuts the two devices
[15:29] <ogra_> ambient -> some computation  -> brightness
[15:30] <jamon> any BTRFS folks around? I have an impossible to rm file on a BTRFS volume
[15:31] <ogra_> rtg_, http://paste.ubuntu.com/5610989/ 
[15:32] <jamon> btrfsck sees the file and references to others that were deleted, but this one won't go
[15:32] <ogra_> rtg_, if you never used the phablet image that works just fine 
[15:32] <rtg_> ogra_, yeah, I've yet to install it.
[15:32] <ogra_> i assume after you use the phablet image /sys/bus/i2c/drivers/al3010/2-001c/show_lux returns 0 
[15:32] <ogra_> constantly 
[15:33] <ogra_> (just a theroy though)
[15:33] <ogra_> i would suspect there is a firmware in android that triggers this 
[15:33] <ogra_> behavior
[15:34] <rtg_> ogra_, lemme look at teh driver to see if it requests firmware
[15:35] <ogra_> since italians have no lamps its hard to get some values from ppisati though ... to see if the value changes if you apply some bright light 
[15:36] <rtg_> ogra_, maybe we don't pay him enough to own a lamp ?
[15:37] <ogra_> ah that might be it 
[15:37] <ogra_> should i mail leann to ask about giving him a $10 bonus to buy a desk lamp ?
[15:37] <ogra_> :)
[15:38] <rtg_> ogra_, no firmware, but there is a calibration file: "/data/lightsensor/AL3010_Config.ini"
[15:38] <ogra_> ah
[15:38] <ogra_> so it gets recalibrated then
[15:39] <rtg_> looks like it scans a single integer, 'sscanf(buf,"%d\n", &calibration_value);'
[15:41] <rtg_> ppisati, maybe you can disk around with that ? See calibration_regs in drivers/hwmon/al3010.c
[15:41] <rtg_> dick*
[15:43] <ppisati> rtg_: i'll do
[15:44] <jamon> is there anywhere else i should go to report/debug issues with BTRFS?
[15:44] <rtg_> ppisati, though it looks like the defaults ought to work.
[15:44] <ppisati> well, i can reinstall phablet
[15:44] <ppisati> see what it reportas
[15:45] <ppisati> *reports
[15:45] <ppisati> reinstall desktop and compare
[15:45] <rtg_> ppisati, you can get a console under android ?
[15:45] <ppisati> rtg_: yes
[15:45] <xnox> jamon: #btrfs ?
[15:45] <ppisati> rtg_: sshd and i cant access / from there
[15:45] <ogra_> rtg_, yup, adb :)
[15:46] <ogra_> or you can install ssh ... 
[15:46] <xnox> jamon: their mailing list is very good for low level debugging and fixing stuff. See their homepage for details.
[15:46] <jamon> that's an idea, hope they don't send me back here, but thanks, will take the slow and deliberate debugging approach
[15:53] <jsalisbury> bjf, fyi, I'm chatting on #is about our broken bots/scripts on cranberry.  Seems they did some python updates this morning.
[15:54]  * ppisati -> gym
[15:54] <ppisati> back later
[16:41] <apw> jsalisbury, yay for updates
[16:41] <jsalisbury> apw, \o/
[17:25]  * rtg_ -> lunch
[17:32] <apw> zequence, this package seems to have been built without the .orig.tar.gz
[17:32] <apw> is that intentional
[17:32] <apw> zequence, 25.25 seems have been with
[17:37] <apw> zequence, plus when you build the source one should use -v<version in -release/-updates> to get the full changelog
[17:38] <apw> zequence, yeah -26.26 also used and orig.  so perhaps we should rebuild a -26.28 which is built using the orig and the -v3.5.0-17.18
[17:41] <zequence> apw: Ok. My bad. Going to rebuild it then.
[17:46] <apw> zequence, it will upload a heck of a lot faster with an .orig as well
[17:47] <apw> zequence, let me know when the source is in as i do not need the binaries for our purposes
[17:56] <zequence> apw: I'm wondering about how I should do with the changelog. Should I just change the upload number on the current last entry,  make a git commit and the rebuild, or do I need to create a new entry in the changelog completely?
[17:56] <zequence> ..since I'm not really changing anything in the source other than the changelog
[17:57] <apw> zequence, i would normally make a new section none the less, and just put like
[17:57] <apw>  * no change rebuild with .orig.
[17:57] <zequence> ok, will do
[17:59] <apw> zequence, don't forget the -v<version> on the dpkg-buildpackage -S
[18:08] <zequence> apw: Haven't used that one before. Changes before version? Last version, or the last orig version?
[18:08] <rtg_> zequence, the last version in -updates
[18:09] <zequence> Aha
[18:10] <zequence> Learning debian packaging fully is on my todo list. This is really awful
[18:16] <apw> zequence, last version in -updates indeed
[18:22] <zequence> Ok, so I need to use versione each time we do an non ABI update
[18:23] <zequence> apw: It's in the ppa now
[18:23] <rtg_> zequence, you should do it every time you upload
[18:24] <zequence> rtg_: But, if the previous upload ended up in -updates?
[18:26] <rtg_> zequence, the rule is simple. every time you package for an upload you specify the version of the package in -updates. that is what creates the diff in launchpad.
[18:28] <zequence> ok
[18:29] <manjo> apw, patch upstreamed .. thanks for pointing that out 
[18:29] <manjo> apw, patch upstreamed .. and you are cced too 
[18:32] <apw> manjo, cool
[18:37] <manjo> rtg_, trying to speak but mumble is not working 
[18:41] <manjo> mumble sucks
[18:41] <rtg_> manjo, its more likely to be pulseaudio
[18:42] <manjo> I need to try my laptop ... might be the mic on the webcam 
[18:46] <ohsix> thankfully the desktop mixer shows sources and levels!
[19:01] <antarus> infinity: ping
[19:02] <infinity> antarus: Sup?
[19:02] <antarus> so apt-get autoremove
[19:02] <antarus> is that supopsed to work...?
[19:02] <antarus> it wants to remove weird stuff on my system
[19:03] <antarus> and my debian developer co-workers are all like 'oh that thing is totally unsafe'
[19:03] <infinity> It's supposed to work, yes.  Define "weird stuff".
[19:05] <antarus> it wants to remove rake
[19:05] <antarus> but I hav epuppet and rails installed, which depend on rake
[19:06] <antarus> also my precious linux-tools-package (that installs the kernel 'perf' binary)
[19:06] <antarus> I'm fairly sure is just a 'recommends'
[19:06] <antarus> infinity: basically for the kernel pruner, they inquire as to why we do not just prune the packages directly, instead of marking them for autoremove
[19:07] <infinity> Erm, I'd want to see the output of that.  autoremove can't remove anything that's depended on, unless it also removes the other package.
[19:08] <infinity> And, indeed, I see rails -> ruby-rails-2.3 -> rake here as a dependency chain.
[19:08] <infinity> Now, if rails itself was never marked manually installed (was it a dep of something else that you've since removed?), then autoremove is doing its job if it pulls out rails.
[19:09] <antarus> it is a dep of puppet
[19:09] <infinity> No it's not.
[19:09] <infinity> And there's no reason it should be.
[19:09] <antarus> s/dep/suggest/
[19:09] <antarus> our puppet is extra special, probably
[19:09] <antarus> ;p
[19:09] <antarus> i   puppetmaster        Depends  puppetmaster-common (= 2.7.18-2gg21)
[19:09] <antarus> i A puppetmaster-common Suggests rails (>= 1.2.3-2) 
[19:09] <antarus> see ;p
[19:10] <antarus> I'm guessing we do not always trigger 'manual installs' properly
[19:10] <antarus> so we just cannot trust apt-get autoremove at all
[19:10] <infinity> Possibly not.  Shame.
[19:10]  * antarus has no idea how manual isntalls work
[19:10] <infinity> Well, you could duplicate the same logic in the autoremove-kernels snippet to just do it yourself.
[19:10] <antarus> yeah
[19:11] <antarus> we probably will
[19:11] <infinity> Things are marked manually installed if you either manually install them (say, apt-get install foo) or if they're a direct dependency of something in the "metapackages" section.
[19:11] <infinity> Any dep pulled in lower than that is marked auto.
[19:13] <antarus> so dpkg debs are not manual?
[19:13] <antarus> because dpkg and apt don't chat with each other?
[20:05] <MoPac> Hello; I'm looking for some help with configuration of hooks or modules when creating initrd images for my kernel.  After repairing a kernel from a live USB, the boot process "forgot" that it needed to open my LUKS container to find the boot partition.  I have restored an old kernel image that works, but I'm worried that this is going to happen again on next kernel upgrade / image build.  What do?
[20:08] <rtg_> MoPac, I think everything in /etc/modules gets bundled into the initrd.
[20:09] <MoPac> So do I just add lines that say "dmcrypt" or "cryptsetup" or somesuch?  No need to actually direct it to a particular drive or make a script to open a given container?
[20:09]  * rtg_ -> EOD
[23:06] <electronplusplus> Hi. I'm learning unix and kernel programming. One thing the I want to do is to code a complete unix command. my question is: What kind of command, that are useful, are missing in linux?