[10:16] <PaulePanter> Hi. How do I get the latest Intel Microcode updates for Kaby Lake systems (Dell XPS 13 9360) on Ubuntu 16.04.2?
[10:16] <PaulePanter> https://packages.ubuntu.com/search?keywords=intel-microcode
[10:17] <PaulePanter> Only 3.20151106.1 is available.
[10:21] <ogra_> PaulePanter, Bug #1700373
[10:33] <PaulePanter> ogra_: Thank you.
[11:39] <magicline> @tomreyn seems to work quite well
[11:39] <magicline> software IO TLB [mem 0xc7f80000-0xcff80000] (128MB)
[13:05] <JPelletier> Hi, I'm currently trying to build latest zesty Kernel to enable CONFIG_USB_SERIAL_CONSOLE but I can't find int in the Kernel Configuration
[13:15] <JPelletier> Damn I was searching with a typo... found it
[13:22] <JPelletier> When searching for: CONFIG_USB_SERIAL_CONSOLE I find "Prompt: USB Serial Console device support"  but it's not in the list ounder "USB Serial Converter support" what I'm missing?
[14:04] <JPelletier> Anyone can help me enabling CONFIG_USB_SERIAL_CONSOLE ?
[14:17] <LocutusOfBorg> apw, in artful-proposed you have the new vbox shiny kernel modules!
[14:53] <apw> LocutusOfBorg, thanks ... sforshee ^ we need to resync those
[14:53] <LocutusOfBorg> <3
[14:54] <sforshee> LocutusOfBorg: yes thank you. I guess this one has fixes for 4.12?
[14:55] <LocutusOfBorg> and 4.13
[14:55] <apw> sweet
[14:55] <LocutusOfBorg> Linux hosts / guests: Linux 4.12 fixes (bugs #16725, #16800)  Linux hosts / guests: Linux 4.13 fix (bug #16887) 
[14:55] <LocutusOfBorg> not sure how much 4.13 will change the api, but meh
[14:55] <LocutusOfBorg> it should be good until RC1
[14:57] <sforshee> LocutusOfBorg: yeah, working on the rebase to 4.13-rc1 as we speak. Fyi, we will be trying to get 4.13 into artful quicker than 4.12, at the late -rc stage.
[14:57] <LocutusOfBorg> nice!
[14:57] <LocutusOfBorg> there is a big ongoing porting of such modules in the mainline kernel
[14:57] <LocutusOfBorg> so, hopefully they will go upstream one day
[14:58] <sforshee> that would be great
[17:08] <chiluk> apw is the k-team meeting cancelled today?
[17:08] <chiluk> can you make sure the http://fridge.ubuntu.com/calendars  is correct?
[17:09] <apw> chiluk, we haven't had a meeting for a year i don't think
[17:09] <apw> chiluk, noone ever attended other than us ...
[17:09] <chiluk> hmm I was wondering about that.. 
[17:10] <chiluk> apw.. well I'm interested in attending now..
[17:10] <chiluk> apw which you may or may not care about.
[17:10] <chiluk> apw either way the fridge calendar should get updated.
[17:10] <apw> chiluk, well don't stand on ceremony, just come here and discuss whatever you care to, whenever
[17:10] <apw> chiluk, yep, passing that baton to someone to resolve
[17:11] <chiluk> yep thanks apw.. any thoughts on the intel-microcode upload?  Has the sru team earmarked anyone in particular to review it?  I'm expecting it will be rbasak.
[17:12] <apw> chiluk, i have not heard anyone specific being in the frame no, it is a risky update and causes the fear in most of us
[17:13] <chiluk> apw yeah.. I figured as much... apw if it makes you feel any better it appears as if most of the firmware stays constant for arches other than skylake and kabylake.
[17:13] <chiluk> unless of course intel just decided not to bump the revision.
[17:17] <rbasak> chiluk: I expect it'll be me. My SRU day is tomorrow.
[17:17] <apw> chiluk, yeah one would hope
[17:18] <chiluk> rbasak apw, the other thing I was curious about was if we would / should backport the skylake /kabylake graphics firmware blobs into linux-firmware... thoughts?
[17:19] <chiluk> rbasak apw ... specifically https://01.org/linuxgraphics/downloads/firmware 
[17:20] <chiluk> the two I think we should consider are the DMC and HUC as both should have power savings.
[17:20] <apw> sforshee, ^
[17:21] <chiluk> I wish I had a contact inside intel to confirm or get comment from about this.
[17:22] <chiluk> the page is really not technically verbose so it's hard to tell what they're really doing.
[17:23] <chiluk> alright off to food with me.
[17:33] <sforshee> chiluk: backport to which release? Artful at least looks to be up to date
[17:42] <rbasak> chiluk: I'm not sure. What would we gain from doing that?
[19:14] <flocculant> jsalisbury: hi - on bug 1704470 you've asked me to test against v4.12 and pointed me to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/ - is 4.13-rc1 what you want me to test against?
[19:19] <patrik> Hi guys, how do I best (easiest, quickest) go about building the 4.13-rc1 kernel + custom patch?
[19:20] <jsalisbury> flocculant, yes it is.  Sorry 4.13-rc1 just came out and I didn't update my email template form 4.12 properly.  I'll fix that.
[19:20] <patrik> I've tried the https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel guide but can't find a way to get 4.13-rc1 sources with that approach.
[19:20] <jsalisbury> thanks for the heads up
[19:20] <flocculant> jsalisbury: ok - cool, will grab and test that now (ish
[19:20] <patrik> Can I just clone the vanilla source and copy the "debian" dir in there? I'm assuming it's not that easy.. :)
[19:21] <jsalisbury> patrik, you could use the artful master-next branch, but it's not at 4.13 as of yet, still 4.12 based.
[19:23] <patrik> jsalisbury, yeah I noticed that, thanks. Although I do need 4.13-rc1 since this patch is based off it and specific ACPI/PM changes. I've been asked by the dev to try it out on my hardware.
[19:24] <patrik> https://bugzilla.kernel.org/show_bug.cgi?id=192591#c101
[19:24] <jsalisbury> patrik, in the kteam-tools repository, there is a script called mainline-build-one.  It can be used to build the latest mainline kernel and it "Debianizes" it.
[19:25] <jsalisbury> patrik, kteam-toosl is in this git repo:
[19:25] <jsalisbury> git://git.launchpad.net/~canonical-kernel/+git/kteam-tools
[19:26] <patrik> Oh cool, thanks a lot! So I just download the 4.13-rc1 tarball, that script, and run it and I'll end up with a nice .deb? :)
[19:26] <jsalisbury> patrik, the script is in ~kteam-tools/mainline-build
[19:26] <jsalisbury> patrik, if you need help building a kernel, you can open a Launchpad bug and I can try building it for you.
[19:27] <patrik> That would be amazing, are we talking in upcoming minutes or days? :)
[19:28] <jsalisbury> patrik, I could build it today.  Just open a bug and post the patch you need built into 4.13-rc1 and I'll build it, package it into a deb and post it for you.
[19:29] <patrik> Oh great, on it!
[19:29] <jsalisbury> patrik, just post the bug number here, in case I don't get to the new bug email timely
[19:32] <patrik> https://bugs.launchpad.net/ubuntu/+source/linux/+filebug ?
[19:33] <jsalisbury> patrik, you could use the web interface, or from a terminal run "ubuntu-bug linux"
[19:37] <flocculant> jsalisbury: ok - updated that bug now, not convinced it's the kernel tbh (but I'm just a van driver ...) 
[19:37] <patrik> jsalisbury, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099
[19:38] <jsalisbury> patrik, thanks, I'll build the kernel and post it in a bit.
[19:38] <jsalisbury> flocculant, thanks for testing.  I'll review the bug.
[19:39] <flocculant> jsalisbury: ok - thanks - I did mark a similar alsa bug as a dupe (reported it there when apport wouldn't let me report kernel, was using kernel from proposed)
[19:40] <jsalisbury> flocculant, ok, thanks
[19:42] <flocculant> didn't touch tags btw as now I'm not sure what the bug is in
[20:42] <jsalisbury> patrik, There is a test kernel available at: http://kernel.ubuntu.com/~jsalisbury/lp1705099/
[20:43] <patrik> jsalisbury, thanks I'll have a look
[20:45] <patrik> switching to this machine so I can reboot :)
[20:52] <patrik> jsalisbury, thanks a lot! kernel worked great and it even proved the feature!
[21:27] <jsalisbury> patrik, great news