I can't test this 3.13 kernel, as it has multiple other problems.
What I was talking about was the 4.4 Xenial kernel compiled with the
Trusty config / compiler, so my modules will build against:
Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-
protector-strong not supported by compiler.
So on Trusty with HWE Xenial I get:
$ grep CONFIG_CC_STACKPROTECTOR_STRONG /boot/config-4.4.0-111-generic
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
while on Xenial I have
$ grep CONFIG_CC_STACKPROTECTOR_STRONG /boot/config-4.4.0-112-generic
Sorry for not being explicit enough.
BTW: I manually compiled the Ubuntu kernel source with my attached
patch, the config from /boot as .config and a make oldconfig etc. and it
worked as expected.
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Support rfkill-any led trigger for Fujitsu u727
Status in linux package in Ubuntu:
Status in linux source package in Trusty:
Status in linux source package in Xenial:
I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based
on Skylake hardware.
It has a single rfkill button and a single LED for wlan and bluetooth. Both
device driver currently provide a single rfkill trigger, so the led could just
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led
trigger to correctly handle the led with multiple rfkill devices. That was
added by one of the fujitsu-laptop maintainers and the driver sets it as the
Author: Michał Kępień <ker...@kempniu.pl>
Date: Fri Jan 6 07:07:47 2017 +0100
rfkill: Add rfkill-any LED trigger
Normally I would simply patch the affected modules using DKMS, like the
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW
without messing with the kernel packages.
I'm currently waiting for some reviews, like
But the rfkill support is compiled in, so I can't patch it using DKMS.
So my first proposed fix would be to include a backport of this patch.
Alternatively rfkill can be compiled as a module, so I can patch it
and provide an updated module.
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-111-generic i686
Date: Wed Jan 24 10:48:28 2018
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp