[05:39] thanks apw [05:39] I hope to have a new virtualbox before 4.7 [05:39] because the kernel module has some build failures here [07:50] Hello again [07:50] rtg apw : I have installed the recompiled 4.7 (201608021801), and the dell modules are there now [07:51] dell_led, dell_wmi, dell_laptop, dell_smbios, dell_rbtn [07:52] however, unlike 4.6.x, the radio-off hotkey (which is Fn+PrtScr on my keyboard) does not work. [07:52] in 4.6.x, it just cause a killswitch event which worked fine with network manager [07:53] in 4.7, it just gives me: "atkbd serio0: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0)" in syslog [07:54] from a few initial powertop measurements, it seems as if 4.7 uses a slight bit less energy in idle though === JanC is now known as Guest88920 === JanC_ is now known as JanC [14:08] will code in https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/+ref/master-next be added to 4.4.0-34? or is that for 4.4.0-35, etc? [14:09] specifically interested in what release will land 4.4.16 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607404 [14:09] Launchpad bug 1607404 in linux (Ubuntu) "Xenial update to v4.4.16 stable release" [Undecided,New] [14:13] gQuigs, Ubuntu-4.4.0-35.54 [14:13] rtg: thanks! [14:59] dannf, could you boot the test kernel referenced in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/comments/12 ? [14:59] Launchpad bug 1608854 in linux (Ubuntu Trusty) "[arm64] nova instances can't boot with 3.13.0-92" [Undecided,In progress] === apb1963_ is now known as apb1963 [15:07] rtg: will take a look after this meeting [15:35] rtg: so the plan is to back out the arm64/EFI support in trusty? [15:35] dannf, yup [15:35] rtg: was that breaking something? [15:36] dannf, according to the bug it regressed boot in a Nova VM [15:37] 3.13 never had EFI support for arm64 anyway [15:37] rtg: yeah it did, i backported it :) [15:38] rtg: the way i read the bug, it was disabling the CONFIG_EFI setting that regressed it (which, sine the user is booting in EFI mode AFAICT, that would) [15:39] rtg: it isn't clear to me why LP: #1566221 required disabling CONFIG_EFI on arm64 [15:39] Launchpad bug 1566221 in linux (Ubuntu Yakkety) "linux: Enforce signed module loading when UEFI secure boot" [Undecided,Fix released] https://launchpad.net/bugs/1566221 [15:39] dannf, I disabled EFI on arm64 when backporting the UEFI signed modules patches failed to compile. Lemme recheck what UI've reverted., [15:40] rtg: ok - but i'm guessing that's the regression - the user was previously booting 3.13 in EFI mode, and they can't any more [15:41] dannf, damn, those are your commits. Guess I'm gonna have to think about this harder. [15:42] rtg: ok - let me know if you need any help w/ the compile failure [15:44] dannf, will do === JanC is now known as Guest94529 === JanC_ is now known as JanC === ghostcube_ is now known as ghostcube [23:57] Hello. I am trying to fill a bug report. Accordingly with the Ubuntu documentation, this bug should be reported against the kernel, as it happens when booting the Live USB. [23:57] I'm just trying to understand what more do I need to include to make it usefl [23:57] I already have the ubuntu-bug kernel info [23:58] The bug is not being able to go past the Ubuntu logo screen on the Live USB due to the presence of a btrfs formatted partition on the local hard drive [23:58] After deleting the partition the Live USB boots just fine.