LocutusOfBorgthanks apw 05:39
LocutusOfBorgI hope to have a new virtualbox before 4.705:39
LocutusOfBorgbecause the kernel module has some build failures here05:39
JanDrewesHello again07:50
JanDrewesrtg apw : I have installed the recompiled 4.7 (201608021801), and the dell modules are there now07:50
JanDrewesdell_led, dell_wmi, dell_laptop, dell_smbios, dell_rbtn07:51
JanDreweshowever, unlike 4.6.x, the radio-off hotkey (which is Fn+PrtScr on my keyboard) does not work.07:52
JanDrewesin 4.6.x, it just cause a killswitch event which worked fine with network manager07:52
JanDrewesin 4.7, it just gives me: "atkbd serio0: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0)" in syslog07:53
JanDrewesfrom a few initial powertop measurements, it seems as if 4.7 uses a slight bit less energy in idle though07:54
=== JanC is now known as Guest88920
=== JanC_ is now known as JanC
gQuigswill 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:08
gQuigsspecifically interested in what release will land 4.4.16 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/160740414:09
ubot5Launchpad bug 1607404 in linux (Ubuntu) "Xenial update to v4.4.16 stable release" [Undecided,New]14:09
rtggQuigs, Ubuntu-4.4.0-35.5414:13
gQuigsrtg: thanks!14:13
rtgdannf, could you boot the test kernel referenced in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/comments/12 ?14:59
ubot5Launchpad bug 1608854 in linux (Ubuntu Trusty) "[arm64] nova instances can't boot with 3.13.0-92" [Undecided,In progress]14:59
=== apb1963_ is now known as apb1963
dannfrtg: will take a look after this meeting15:07
dannfrtg: so the plan is to back out the arm64/EFI support in trusty?15:35
rtgdannf, yup15:35
dannfrtg: was that breaking something?15:35
rtgdannf, according to the bug it regressed boot in a Nova VM15:36
rtg3.13 never had EFI support for arm64 anyway15:37
dannfrtg: yeah it did, i backported it :)15:37
dannfrtg: 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:38
dannfrtg: it isn't clear to me why LP: #1566221 required disabling CONFIG_EFI on arm6415:39
ubot5Launchpad bug 1566221 in linux (Ubuntu Yakkety) "linux: Enforce signed module loading when UEFI secure boot" [Undecided,Fix released] https://launchpad.net/bugs/156622115:39
rtgdannf, I disabled EFI on arm64 when backporting the UEFI signed modules patches failed to compile. Lemme recheck what UI've reverted.,15:39
dannfrtg: ok - but i'm guessing that's the regression - the user was previously booting 3.13 in EFI mode, and they can't any more15:40
rtgdannf, damn, those are your commits. Guess I'm gonna have to think about this harder.15:41
dannfrtg: ok - let me know if you need any help w/ the compile failure15:42
rtgdannf, will do15:44
=== JanC is now known as Guest94529
=== JanC_ is now known as JanC
=== ghostcube_ is now known as ghostcube
cknavigatorHello. 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
cknavigatorI'm just trying to understand what more do I need to include to make it usefl23:57
cknavigatorI already have the ubuntu-bug kernel info23:57
cknavigatorThe 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 drive23:58
cknavigatorAfter deleting the partition the Live USB boots just fine.23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!