[03:35] <Psil0Cybin> hey guys i have a few questions about how kernels work, I upgraded my Ubuntu system and the new kernel is causing a blackscreen where no parameters fix the issue
[03:35] <Psil0Cybin> how can i go about creating a proper report so i can help people working on the new kernels to look at my issue
[03:36] <Psil0Cybin> do you think it is fine to use an outdated kernel? would new kernels have a potential of fixing my issue and i should sit this kernel update that is causing the problems out?
[06:54] <Psil0Cybin> hey guys i have a few questions about how kernels work, I upgraded my Ubuntu system and the new kernel is causing a blackscreen where no parameters fix the issue
[06:54] <Psil0Cybin> do you think it is fine to use an outdated kernel? would new kernels have a potential of fixing my issue and i should sit this kernel update that is causing the problems out?
[06:54] <Psil0Cybin> hey guys i have a few questions about how kernels work, I upgraded my Ubuntu system and the new kernel is causing a blackscreen where no parameters fix the issue
[06:54] <Psil0Cybin> woops wrong button sorry. 
[10:53] <ppisati> robher: Rob, don't know if you saw my email, but we are still waiting your comments about the xgmac learning patch
[10:54] <ppisati> robher: subject: "Re: [PATCH 4/5] UBUNTU: SAUCE: net: calxedaxgmac: add mac address learning"
[11:55] <brendand> cking, is there an fwts test for backlight?
[11:55] <cking> brendand, no
[11:55] <brendand> cking, any reason?
[11:56] <cking> no one never requested it (yet)
[11:56] <brendand> cking, fair enough :)
[11:56] <cking> brendand, you could file a bug and i'll chat to hwe to see what is doable 
[11:56] <brendand> cking, i think there should be since the firmware interface seems to be the preferred method of updating the backlight by gsd
[11:57] <brendand> cking, i can file a bug of course
[11:57] <cking> brendand, more tests is always good ;-)
[12:02] <brendand> cking, https://bugs.launchpad.net/bugs/1250429
[12:02] <ubot2> Launchpad bug 1250429 in Firmware Test Suite "FWTS should have a test to check that ACPI backlight interface works correctly" [Undecided,New]
[12:02] <brendand> cking, cheers
[12:06] <cking> brendand, I'll get around to it in the next week or so
[14:26] <rtg> ppisati, any feedback on the xmac MAC learning patch ?
[14:27] <ppisati> rtg: nope, i pinged rob today, let's see if he answer
[14:27] <rtg> ack
[14:41] <rtg> apw, I'm gonna start an unstable branch in trusty so I can start going through all of the new config options in 3.13
[14:47] <apw> rtg, makes a lot of sense to me, will help me with my endevours too
[15:18] <ppisati> mumble failure
[15:22] <rtg> ppisati, I'm rebasing against 3.13 merge window. WTF is ARM_ARCH_TIMER_EVTSTREAM ?
[15:22] <ppisati> rtg: hold on
[15:22] <rtg> even afterreading the help text I'm confused
[15:28] <ppisati> rtg: i had the same reaction...
[15:28] <ppisati> rtg: https://lkml.org/lkml/2013/9/18/125
[15:28] <ppisati> rtg: looks like timeout support for wfe (enter/exit low-power standby) or evern programming error events
[15:28] <rtg> ppisati, hmm, I wonder why its being built for x86'en. seems like some Kconfig patches are in order.
[15:30] <ppisati> rtg: i doubt it attaches there, they probably let it build on x86 to extend toolchain exposure trying to catch as many bugs as possible
[15:37] <cking> brendand, i've just responded to that brightness test fwts bug, can you follow it up?
[15:40] <hallyn_> apw: stgraber: so there's a weird issue (https://github.com/lxc/lxc/issues/25) with avahi-daemon in a container.  it drops caps then clones.  Outside a container the clone works, but inside a container the clone only works if you hack it to not drop CAP_SYS_RESOURCE.
[15:40] <hallyn_> (clone fails with -EAGAIN)
[15:42] <hallyn_> running the container unconfined does not change things;  running outside a container in a hand-built cgroup does not change things;  so i'm having a hard time figuring out why there is anydifference in the privilege level
[15:44] <hallyn_> ooooh, wiat
[15:44] <apw> hallyn_, ... waiting
[15:44] <hallyn_> the uid is in use on the host
[15:45] <hallyn_> i bet using a unique uid will fix it
[15:45] <hallyn_> not really a satisfactory fix, but it would at least explain it
[15:45]  * apw hmms isn't that meant to be fixed by uid spaces
[15:46] <brendand> cking - ok i did
[15:46] <cking> ta
[15:46] <hallyn_> apw: yeah, but those are not yet in use in most places
[15:46] <brendand> cking, i think i probably shouldn't raise any more of these bugs before the years end, else i'll have to buy you a christmas present
[15:47] <brendand> (at this stage i probably already should)
[15:47] <cking> brendand, heh, it's no problem really
[15:48] <hallyn_> apw: yeah so that fixes it.  sorry for the noise.  (not sure what to do about it, but it's not a kernel issue :)
[15:49] <cking> brendand, i think I will call it "autobrightness" if that's OK
[15:49] <brendand> cking, backlight?
[15:49] <brendand> cking, your call
[15:56] <ppisati> bug 1250495
[15:56] <ubot2> Launchpad bug 1250495 in flash-kernel (Ubuntu) "armhf: highbank: relocate initrd to make room for a bigger kernel" [Undecided,New] https://launchpad.net/bugs/1250495
[15:56] <ppisati> infinity: you might be interested in it ^
[16:00] <apw> ppisati, approved noms
[16:02] <rtg> apw, pushed unstable, starting build tests
[16:18] <apw> rtg, ta
[16:54] <robher> ppisati, infinity: we've adjusted the initrd and kernel addresses in the u-boot env to fix this issue. It should be part of 2.4.x firmware.
[17:15] <infinity> ppisati: Erk.  Fun.  Can you remind me about it in a few days?  I'm about to run and catch a plane today and lose all context.
[17:15] <infinity> robher: Adjusting it in firmware means we don't need to care about the boot.scr hack, or...?
[18:16]  * apw wanders to another room
[19:22]  * rtg -> lunch
[21:52] <Psil0Cybin> hey guys i have a question about kernels i am so ocnfused maybe someone can shoot me in the right direction
[22:02] <apw> Psil0Cybin, you will do well to actually ask that question
[22:03] <apw> then we can work out who knows etc 
[22:14] <Psil0Cybin> okay
[22:14] <Psil0Cybin> i have kernel number 3.2.0-55-generic-pae
[22:14] <Psil0Cybin> apw: my question is i used dist-upgrade got a new kernel, it caused a blackscreen i tried nomodeset
[22:14] <Psil0Cybin> did not work i tried all other paremeters did not work
[22:14] <Psil0Cybin> someone suggested to ry a mainline kernel
[22:15] <Psil0Cybin> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/
[22:15] <Psil0Cybin> is this the newest kernel for my build?
[22:16] <rtg> Psil0Cybin, its the newest one you want to try. anything newer is getting pretty steamy.
[22:16] <Psil0Cybin> okay perfect so im installing it
[22:16] <Psil0Cybin> and im getting this
[22:16] <Psil0Cybin> http://pastebin.com/nE5xGHee
[22:16] <Psil0Cybin> is that normal or is it because i did not instead the headers yet?
[22:17] <rtg> Psil0Cybin, its benign (unless you have an rtl device that requires this firmware)
[22:17] <Psil0Cybin> okay thanks
[22:17] <Psil0Cybin> jesus im new :P so im trying to learn ahah
[22:17] <Psil0Cybin> you guys are so helpful i wish i could get everyone @ #ubuntu a giftbasket.
[22:17] <rtg> then we'd all get fat :)
[22:18] <Psil0Cybin> hahahahahha
[22:18] <Psil0Cybin> okay so now im installing the headers
[22:18] <Psil0Cybin> and im set to test :)
[22:23] <Psil0Cybin> rtg: i installed the header and im getting this messages
[22:23] <Psil0Cybin> http://pastebin.com/wDhkxQGF
[22:24] <Psil0Cybin> Error! Bad return status for module build on kernel: 3.12.0-031200-generic (i686)
[22:24] <Psil0Cybin> Consult /var/lib/dkms/cedarview-drm/20120717/build/make.log for more information.
[22:25] <rtg> Psil0Cybin, I don't know what cedarview-drm is, but it clear;y doesn't like those kernel headers
[22:25] <Psil0Cybin> cedarview is my graphic driver
[22:25] <Psil0Cybin> which is why i am getting a blackscreen i assume
[22:25] <rtg> likely
[22:25] <Psil0Cybin> darn
[22:26] <Psil0Cybin> so it looks like no kernel will work for me other then what i am using now
[22:26] <Psil0Cybin> 3.2.0-55-generic-pae
[22:26] <rtg> yeah, its unlikely kernels newer then 3.2 will work.
[22:27] <Psil0Cybin> so what do i do..if i have an acer aspire one, d270-1628 i do not want new features
[22:27] <Psil0Cybin> but i want to make sure i am always secure
[22:27] <Psil0Cybin> when it comes to security issues.
[22:27] <rtg> 3.2 is supported for 5 years from 12.04
[22:27] <Psil0Cybin> oh eally for now?
[22:28] <Psil0Cybin> so im fine for 5 years
[22:28] <Psil0Cybin> just i should save up for better hardware?
[22:28] <rtg> indeed
[22:28] <Psil0Cybin> sigh
[22:28] <Psil0Cybin> alright
[22:28] <Psil0Cybin> so now next question if i go out and buy a laptop what laptop can i buy to insure that i get good quality support from ubuntu
[22:28] <Psil0Cybin> when it comes to kernel and drivers.
[22:28] <rtg> system76
[22:29] <Psil0Cybin> system76?
[22:29] <rtg> dell pre-installed
[22:29] <Psil0Cybin> oh really dell?
[22:29] <Psil0Cybin> is a good machine for ubuntu?
[22:29] <rtg> only those that come pre-insatlled with ubuntu
[22:29] <Psil0Cybin> okay but lets say i get a pre installed version does it come with the drivers on a usb or something incase i want to format later?
[22:30] <Psil0Cybin> or just the hardware is really good one those when it comes to support
[22:30] <Psil0Cybin> for the linux community.
[22:30] <rtg> a little of both
[22:30] <Psil0Cybin> alright sigh i wish i knew this before hand
[22:31] <Psil0Cybin> i just got this laptop...and now i find out when it comes to linux its garbage because intel is shittay
[22:31] <Psil0Cybin> its small netbook i wanted to run xubuntu on forever :)
[22:31] <rtg> well, whats wrong with the bits that came on it ? you're good until 17.04
[22:31] <rtg> anyway, I'm EOD
[22:32]  * rtg -> EOD