** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joe Abt (neondiscobrn)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use
Looks like everything is ok now in 2018; closing that report.
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-375 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
** Also affects: virtualbox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
-fno-PIE builds (Sebastian Siewior and Borislav Petkov). This is
not a kernel regression, but one of the Debian gcc package.
Nevertheless, it's quite annoying, so I think it should go into
mainline and stable now"
** Changed in: gcc-defaults (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
The patch in comment #39 or the env var in comment #38 both work for me.
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use
>this is not a gcc bug. this is an ubuntu management specific arrogance
(and perhaps some cash from redmond with love) - of course it is
completely wrong to patch the kernel makefile because they decided to
ship a gcc unable to build the kernel itself (with wrong
defaults/specs). but like they
this is not a gcc bug. this is an ubuntu management specific arrogance
(and perhaps some cash from redmond with love) - of course it is
completely wrong to patch the kernel makefile because they decided to
ship a gcc unable to build the kernel itself (with wrong
defaults/specs). but like they said
cerebellum-ukr, is there any place to track for upstreaming necessary
patches? Quite boring to do this every time I want to build kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
Why isn't this a bug in gcc 6? It doesn't seem right that we have to
patch the kernel makefile to get it to build.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot
Thank you, works for me on upstream 4.8-rc2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
not
Nazar Mokrynskyi
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc2/
this patch what you need
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc2/0002-UBUNTU-SAUCE-no-up-disable-pie-when-gcc-has-it-enabl.patch
--
You received this bug notification because you are a member of Kernel
I'm having this issue again after upgrade to GCC 6 from GCC 5 recently. I've
being able to compile custom kernel with just `KCFLAGS="-fno-pie"`, now it
fails with error mentioned in this bug report.
Any ideas why? Am I alone here?
--
You received this bug notification because you are a member
I've come across this bug on linux 4.4.0-28-generic on Ubuntu 16.04 when
trying to install a network card called Netis AD1103 with Realtek 8168.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
looks good to me!
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
Feedback: installing kernel 4.4.0−23 (without other kbuild∕makefile tweak)
- no crasher at installation
- reboot with no black screen
* Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not
supported by compiler (LP: #1574982)
- SAUCE: (no-up) disable -pie when gcc has
Already mentioned, of course, but to sum it up ^
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
not
Fix:
Needed to add in
EXTRA_CFLAGS += -fno-pie -fno-stack-protector
to /usr/src/nvidia-364-364.19/Kbuild
And to top /usr/src/bbswitch-0.8/Makefile
EXTRA_CFLAGS := -fno-pie -fno-stack-protector
Then issue a command:
ls /usr/src/linux-headers-* -d | sed -e 's/.*linux-headers-//' | sort -V | tac
Debian answer & possible solution:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823869#10
its an Ubuntu problem, and Debian will probably change nothing to their
dkms version.
** Bug watch added: Debian Bug tracker #823869
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823869
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
** Changed in: gcc-defaults (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
** Also affects: gcc-defaults (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Will mentioned patch have potential to go upstream?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
Ok, we now have a minimal patch for the kernel to disable PIE. This
reflects into the headers packages so that DKMS packages building
against those will also have PIE disabled. Will send to kernel-team@
for review once it passes final testing.
--
You received this bug notification because you
You need to build the whole virtualbox, not only the host drivers.
I suspect you took the virtualbox-source package and did some module-assistant
tricks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For virtualbox you should modify Makefile under following subdirectories
only: boxdrv, vboxnetapd, vboxnetflt and vboxpci.
The fix in #19 should be complete, since I'm currently on vanilla kernel
4.6.0-rc7 compiled with similar tweak and all modules compiled with
mentioned patches and Nvidia,
Feedback_2
Try to boot with the 4.4.0-22 kernel: as the nvidia-361 module has been well
compiled, i've made a cold boot.
The process goes well until the lightdm login screen: the password validation
fails to load the nvidia graphic process, and bounce back to the login screen.
So the changes
Feedback
Following the #19 comment above, both nvidia-xxx and bbswitch compile as
expected. But virtualbox (from oracle, as the ubuntu one is unistallable) fails:
- inserted "EXTRA_CFLAGS := -fno-pie -fno-stack-protector" into the many
'Makefile' from /usr/src/... and /var/lib/dkms/ ; they
Hi Nazar, I failed to make a vbox patch.
it fails now with some
"error: Missing # define g_kLdrRdrFileOps"
can you please share your patch?
thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This error is somehow associated with this bug?
Additonal test failures with --enable-default-pie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70150
11 test regressions when building GCC 6 with --enable-default-ssp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70230
** Bug watch added: GCC
No, solution was incomplete.
Correct is following:
EXTRA_CFLAGS += -fno-pie -fno-stack-protector
Otherwise it compiles, but afterwards doesn't work and complains with
"Unknown symbol __stack_chk_fail (err 0)"
For all other modules (tried with bbswitch-0.8, tuxedo-wmo-1.5.1,
virtualbox-5.0.18)
Thanks Nazar, your solution works fine. Still need a solution for the
bbswitch-dkms é virtualbox crashes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use
I've added:
EXTRA_CFLAGS += -fno-pie
In /usr/src/nvidia-364-364.19/Kbuild before line 59 and compilation of
Nvidia module using dkms succeeded.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I was able to compile HHVM and Nvidia binary driver by reverting GCC
package to older version, now Xenial uses newer packages by default,
which makes compilation out of the box impossible.
This doesn't feel like dkms-specific issue, since HHVM is very different
thing and suffers from the same
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa
linux - 4.6.0-2.3
in Makefile
# force no-pie for distro compilers that enable pie by default
KBUILD_CFLAGS += $(call cc-option, -fno-pie)
KBUILD_CFLAGS += $(call cc-option, -no-pie)
KBUILD_AFLAGS += $(call cc-option, -fno-pie)
@David
Matthias have set gcc-defaults to 'invalid' (#7); maybe needs to set gcc-6
instead (or gcc-5; does not know which one is used in that case)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This seems to be a bug in gcc itself. It should automatically disable
PIE when -mcmodel=kernel or when __KERNEL__ is passed in a header.
Attempts to compile using no PIE command line flags don't work either.
It's as if it's not allowing it to be turned back off.
--
You received this bug
dpkg still needs to be used with the good flags Bug #1576915
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
Got a new dpkg that should help resolving that issue:
dpkg (1.18.4ubuntu2) yakkety; urgency=medium
* No-change rebuild to pick up -fPIE on amd64 and ppc64el.
-- Matthias Klose Fri, 29 Apr 2016 13:53:32
+0200
then i ran a kernel 4.4.0-22 reinstallation: but still got the same crashes
** Changed in: dkms (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
** Package changed: ubuntu (Ubuntu) => dkms (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
My comment was sarcastic. The build flags for dkms packages are
invisible to the end user and there is no easy way to change them. This
is either a packaging error with the kernel module or the gcc default
flags are erroneous. In either case this is not something the end user
solves by changing
@David
Please ask on askubuntu to get a dev answer; here it is only for report,
not asking. Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use
Please explain how I am going to build with -no-pie when apt-get and
dkms automates the entire process here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use
you have to build with -no-pie. Please read the Yakkety Yak opening
announcement.
** Changed in: gcc-defaults (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-defaults (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
** Description changed:
- Installing the latest 4.4.0-22 kernel ends with that error logged into
- dkmsbuildlog
+ Installing the latest 4.4.0-22 kernel ends with that error logged into
dkmsbuildlog
+ (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)
** Tags added: apport-collected
** Description changed:
Installing the latest 4.4.0-22 kernel ends with that error logged into
dkmsbuildlog
make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
That issue has been met also by other distros many times; and nvidia
says its a kernel toolchain problem; so opening a 'linux' issue too.
https://devtalk.nvidia.com/default/topic/902950/linux/-solved-faulty-340
-9x-drivers-with-kernels-4-2-x-and-4-3-x/
** Also affects: ubuntu (Ubuntu)
57 matches
Mail list logo
