[09:16]  * apw yawns
[09:16] <apw> henrix, moin ... it is going to be a quiet day today
[09:17] <henrix> apw: morning! yeah, i guess most of the people are off today :)
[09:17] <apw> you, paolo and myself i think
[09:29] <Kano> hi,could somebody update the ndiswrapper package with new upstream to support current kernels?
[10:37] <ogra_> Kano, you might have to ask in #ubuntu-motu ... bug 1076395 looks like it is gone since a while 
[10:37] <ubot2> Launchpad bug 1076395 in linux (Ubuntu Raring) "ndiswrapper module is not provided any more" [Low,Fix released] https://launchpad.net/bugs/1076395
[11:46] <janimo> ppisati, hi, do you know which is the latest nexus4 ubuntu kernel tree?
[12:07] <ppisati> janimo: i bet this one:
[12:07] <ppisati> janimo: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-saucy.git;a=shortlog;h=refs/heads/mako
[12:08] <ogra_> thats saucy though
[12:08] <ppisati> ogra_: i doubt we have a different kernel in T
[12:08] <ogra_> yeah, there was no upload 
[12:08] <ppisati> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=shortlog;h=refs/heads/mako
[12:08] <ogra_> (but i assume the branch was moved to trusty when the cycle started)
[12:08] <ppisati> indeed
[12:09] <ogra_> yeah :)
[12:09] <ppisati> same exact one
[12:13] <janimo> ppisati, thanks. I was confused by the presence of a separate and outdated linux-nexus4 repo
[12:26] <ogra_> janimo, that was for the desktop image 
[12:26] <ogra_> oh, no, that was linux-nexus7 actually :P
[12:30] <apw> yeah we need to wack those old repos and shove them over to archive sometime
[13:09]  * ppisati goes out for some food
[14:55] <brendand> if no network controller shows up in lspci, what could be the problem? this is a ideapad yoga 13
[14:55] <brendand> which i thought was supposed to have a realtek card, but nothing is showing up
[14:56] <brendand> rfkill shows an ideapad_wlan so there must be something there
[15:05] <apw> nothing in lspci at all for it?  that is unusual, has this worked ever ?
[15:06] <brendand> apw, do you think i should boot windows 8 and see if it enables the card?
[15:07] <brendand> apw, i just got this system now
[15:07] <apw> i was wondering if it has worked in other releases
[15:07] <brendand> apw, been trying saucy-live
[15:07] <brendand> apw, i also tried precise
[15:07] <apw> ok so likely 'never' worked
[15:08] <brendand> apw, yeah. like i said above it's *supposed* to have a realtek card
[15:08] <apw> it would be good to boot something which does recognise it if you can to find out wha tthe heck it actually is, what pci ids it has
[15:08] <apw> as normally we see things in pci even if we don't know what they are
[15:08] <brendand> apw, yeah
[15:09] <apw> though i would conjecture it is the other side of a host bridge that we do not configure right
[15:09] <apw> so we don't see it, but ... thats unexpected in anything new
[15:09] <brendand> apw, i'll boot windows 8 and find out the pci-id
[15:10] <apw> great, and then a buggy for it (if there is a device there)
[15:11] <apw> brendand, oh one thing, what state is the rfkill in
[15:11] <apw> as sometimes when devices are rfkill'd by switch they are 'turned off completely' so they don't appear
[15:12] <brendand> apw, it's not blocked
[15:12] <brendand> apw, i see ideapad_wlan and soft block and hard block are both 'no'
[15:12] <apw> ok not that then, though i would try flippnig it in case it is a lie and say inverted
[15:15] <brendand> apw, good idea!
[15:23] <Coder27> Hello. I've notices that the system run on a single CPU core after hibernation. Both cores work normally after regular boot. Please help/
[15:25] <Coder27> There are two messages about the problem in the syslog file: Nov 29 16:56:56 nbook kernel: [ 4140.670554] CPU1: Not responding. Nov 29 16:56:56 nbook kernel: [ 4140.670731] Error taking CPU1 up: -5
[15:26] <Coder27> The kernel is: 3.2.0-56-generic #86-Ubuntu SMP Wed Oct 23 17:31:43 UTC 2013 i686 athlon i386 GNU/Linux
[15:26] <Coder27> The hardware is Lenovo IdeaPad S205 (AMD E-350 APU)
[15:27] <Coder27> Please help me to repot this bug
[15:37] <brendand> apw, well windows 8 says it's the same realtek card i suspected. still trying to locate the pci id :P
[15:37] <brendand> (it's been soooooooooooo long since i use windows)
[15:38] <brendand> not the same pci id though
[15:39] <brendand> 0bda:1724 seems to be it
[15:45] <brendand> it's in lsusb :) that's it
[15:52] <brendand> apw, is that lspci id handled in linux-firmware?
[15:53] <brendand> apw, i just read that the rtl8723au driver makes it work. isn't that in linux-firmware now?
[15:54] <apw> brendand, doh of course ... usb ... a common connectivity for wlan these days
[15:54] <apw> that rings a bell, but that normally menas it is pretty new
[15:56] <apw> brendand, i dont see the au variant being mentioned in the main driver list as yet
[15:58] <apw> brendand, though the rtl8192*u drivers seem to mention that model number so hard to say
[15:58] <apw> what does dmesg say when you click it off and on again in rfkill, that normally disconnects the usb device and reinerts it
[15:59] <apw> and indeed what does lsusb -nnvv say for that device
[16:14] <brendand> apw, nothing much happens in dmesg. not sure what i should be looking for in lsusb
[16:18] <apw> pastebin the whole lsusb -nnvv output, and remind me of the ids you foudn in windows
[16:23] <brendand> apw, i'll need to get some kind of connectivity first. this is an ultrabook so no ethernet
[16:24] <apw> brendand, yeah they suck, i have a usb ethernet dongle lying about in my office for this issue
[17:10] <brendand> apw, https://lkml.org/lkml/2013/4/1/280 seems to be saying that the rtl8723au driver won't be included any time soon
[17:15] <apw> brendand, yeah, though at least there is progress
[17:34] <lfaraone> sigh. the openafs backport was rejected, as vorlon would prefer we just backport the module with the old userland, etc. 
[17:34] <lfaraone> I'm sceptical that is any safer, as nobody has validated the userland tools, PAM module, etc when mixing versions of the project.
[17:34] <lfaraone> slangasek, rather.
[17:44] <apw> lfaraone, well i guess that that at least is something we can do automatically, as in just copy that part out of one package into the other
[17:46] <lfaraone> apw: ah, okay. uh, do you have the rights to request a copy? 
[17:47] <lfaraone> I didn't think you could copy a binary package between dists easily. 
[17:50] <apw> lfaraone, ahh no i just meant we can just copy the source component for the kernel parts from the saucy package into the source package you have for P
[21:50] <hallyn> apw: hey - can you confirm whether my email from serge@hallyn.com (2 of em) this morning it the kernel-team list?
[22:03] <stgraber> hallyn: I didn't see any mail from you to kernel-team@lists.u.c, maybe stuck in moderation somehow?
[22:05] <hallyn> grr
[22:05] <hallyn> ok, thanks
[22:13] <hallyn> stgraber: now? :)
[22:15] <stgraber> hallyn: yep, I see two e-mails from you now
[22:15] <hallyn> thanks
[22:15] <hallyn> wish i'd thought to check on those in the morning
[22:28] <apw> hallyn, yes they were in the moderation queue, pushed
[22:30] <hallyn> apw: sorry.  (i resent from other address)
[22:30] <apw> oh heh, never mind