=== hatch__ is now known as hatch
=== wmp is now known as Guest29040
[07:39] <ra123445555> SIOCGIFHWADDR means
=== kbingham_ is now known as kbingham
[07:47] <ra123445555> ifconfig says my wifi interface is not available but if i give ifconfig -a then i am getting why so?
=== kbingham__ is now known as kbingham
[08:54] <apw> dannf, yeah that must be fixed i am sure, someone in there
[09:07] <smb> apw, Go away! You are not supposed to be here
[09:09] <cking> +1 ^^
=== psivaa_ is now known as psivaa
[09:49] <Kaloz> I should have waited for feedback on 14.04 :P
[09:50] <Kaloz> sound sis gone, deja-dup-monitor is eating all resources, NM's gui greys out every option and manual configuration is gone
[10:01] <infinity> Kaloz: apt-get update, dist-upgrade, and reboot.  Most of all of that was caused by a broken logind upload.
[10:02] <infinity> Kaloz: You want systemd-services 204-5ubuntu17 or higher.
[10:03] <Kaloz> infinity: thanks, I give it a shot :)
[10:22] <apw> smb, cking, nothing to see here
[10:32] <smb> apw, nope, that is why you should not bother to look. ;)
[10:36] <apw> smb, heh like i would do that
[10:38] <smb> apw, hope dies last :-P
[10:38]  * apw is suitibly beaten, and wanders off for FUN
[10:39] <smb> +1 to that
[10:40] <Kaloz> infinity: thanks, worked. was reasing throught everything i915/alsa related, never would have thought it's systemd
[10:40] <Kaloz> s/reasing/reading/
[10:42] <infinity> Kaloz: Turns out that when logind crashes consistently and doesn't give you any XDG_*_DIR environment, the modern desktop world goes a bit sideways.
=== Guest29040 is now known as wmp
[14:54] <brendand> if a system supports hybrid s3, is that a seperate state in /sys/power/state?
[14:55] <brendand> or do we need to check somewhere else to see if it's supported
[14:57] <brendand> is that 'freeze'?
[14:57] <mjg59> brendand: What do you mean by hybrid s3?
[14:58] <mjg59> If it's supported by the firmware then it doesn't (currently) appear in /sys/power/state
[14:58] <mjg59> The other implementation I know of is in uswsusp
[14:58] <brendand> http://en.wikipedia.org/wiki/Sleep_mode#Hybrid_sleep
[14:58] <brendand> mjg59, i guess i'm talking about fw implementation
[14:59] <mjg59> brendand: I think that's an article written by someone who doesn't understand the technology
[15:01] <mjg59> But I think the answer is /sys/power/disk contains "suspend"
[15:01] <brendand> mjg59, so what i mean is, what pm-suspend-hybrid does
[15:03] <mjg59> brendand: Right, check whether /sys/power/disk contains "suspend"
[15:03] <brendand> mjg59, it sure does
[15:04] <mjg59> Then it's supported
[15:05] <brendand_> mjg59, pm-suspend-hybrid kills my system, so i just wanted to check it's not related to hybrid s3 being unsupported
[15:06] <mjg59> It ought to fail if it's unsupported
[15:06] <mjg59> All it does is (effectively):
[15:06] <mjg59> echo suspend >/sys/power/disk
[15:06] <mjg59> ehco disk >/sys/power/state
=== brendand_ is now known as brendand
=== hatch__ is now known as hatch
[16:26] <jsalisbury> rtg, apw, Should I ask paolo to take a look at bug 1302245 ?  It's an ARM config change request.
[16:26] <ubot2> Launchpad bug 1302245 in linux (Ubuntu) "mmap_min_addr blocks armhf binary support on arm64" [Medium,Confirmed] https://launchpad.net/bugs/1302245
[16:28] <bjf> jsalisbury, i don't think either of them are around today
[16:28] <jsalisbury> bjf, ahh, right.  I'll send email then.  thanks