[13:25] <rtg> tseliot, I have a v4.4 kernel ppa:canonical-kernel-team/unstable - looks like fglrx-installer needs some love
[14:16] <tseliot> rtg: ok, I'll have a look at it, thanks
[14:16] <rtg> tsthanks
[14:16] <rtg> tseliot, thanks
[14:39] <soee_> hi, are there any plans to add 4.4 to Xenial ?
[14:40] <apw> soee_, yes, we are working on getting the surrouding packages sorted out for that
[14:41] <soee_> apw: ok, thank you
[14:41] <apw> soee_, we would hope to have it in sooner rather than later, within a week or so
[14:42] <soee_> that is great :)
[14:43] <apw> soee_, 4.4 is expected to be the release kernel version so we'd better get it in :)
[14:43] <soee_> 4.4 is LTS right ?
[14:44] <apw> soee_, this release is an LTS and yes, 4.4 is a stable mainline LTS, which is handy
[14:47] <soee_> thank you
[22:03] <xnox> apw, infinity and I were discussing the virtio modules, which packages, -udeb packages and d-i builds they should be in, and I've now copied the log into bug #1533382
[22:04] <xnox> in case we will go ahead with making virtio_net|blk to be =m
[22:04] <infinity> apw: Feel free to poke me for more context when you decide to tackle.
[23:27] <dsmythies> I am having touble understanding some kernel configuration file changes between mainline kernel 4.4-rc7 and 4.4-rc8. There seesm to be a dependent changes that is forcing CONFIG_SND_EMU10K1_SEQ and CONFIG_SND_EMU10K1 and CONFIG_SND_EMU10K1X to be disabled, even if one tries to set them to "module" again, they get disabled during compile. see also: http://paste.ubuntu.com/14481736/ 
[23:28] <dsmythies> A compile of mainline kernel 4.4 will have the modules if one just copies the -rc7 config file and uses it instead.
[23:31] <dsmythies> I did notice in yesterdays IRC logs a mention of this: CONFIG_ZONE_DEVICE=y
[23:32] <dsmythies> but am not sure if the context is related.
[23:40] <dsmythies> So, my question: Is it intentional that the emu10k1 modules be no longer available? Or is this an unintented side effect of another change?