[Ubuntu-x-swat] [Bug 1427107] [NEW] The DKMS building of the nvidia-304 kernel module fails on kernel-3.19

2015-03-02 Thread kary
Public bug reported: I'm running Vivid Vervet including nvidia-304, 304.125-0ubuntu1. A usual update batch containing kernel-3.19.0-7 just became available and I upgraded to it. The net result was, that after boot I got a black screen. In other words the X-server failed to start, because it

[Ubuntu-x-swat] [Bug 1427107] Re: The DKMS building of the nvidia-304 kernel module fails on kernel-3.19

2015-03-02 Thread kary
** Also affects: nvidia Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1427107 Title: The DKMS building of the nvidia-304

[Ubuntu-x-swat] [Bug 1409190] Re: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build [error: ‘struct file’ has no member named ‘f_dentry’]

2015-03-04 Thread kary
This Bug #1409190 is about nvidia-graphics-drivers-304 and nvidia-graphics-drivers-331-updates . The Bug #1427924 is about nvidia-graphics-drivers-304 and ubuntu-drivers-common autopkgtests. The nvidia-graphics-drivers-304 parts are duplicates of each other and a fix was released through Bug

[Ubuntu-x-swat] [Bug 1409190] Re: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build [error: ‘struct file’ has no member named ‘f_dentry’]

2015-03-03 Thread kary
ROOT CAUSE: In kernel headers, a feature that nvidia code depends on, has been removed in kernel 3.19: $ diff linux-headers-3.18.0-13/include/linux/fs.h linux-headers-3.19.0-7/include/linux/fs.h | grep f_dentry #define f_dentry f_path.dentry WORKAROUND: Make nvidia code live

[Ubuntu-x-swat] [Bug 1409190] Re: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build [error: ‘struct file’ has no member named ‘f_dentry’]

2015-03-03 Thread kary
** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1409190 Title: nvidia-331-updates

[Ubuntu-x-swat] [Bug 1427924] Re: autopkgtest failures if nvidia dkms module fails to build

2015-03-04 Thread kary
I'm not sure, what this discussion is about. But as far as i know, you could fix Nvidia drivers: In bug Bug #1409190 I wrote: ROOT CAUSE: In kernel headers, a feature that nvidia code depends on, has been removed in kernel 3.19: $ diff linux-headers-3.18.0-13/include/linux/fs.h

[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module

2016-11-07 Thread kary
Also I tested nvidia-304, version 304.132-0ubuntu2. I did it from zesty archive. It seems to me, that THIS bug is fixed. The module got loaded into kernel, there are no longer unsatisfied global references. But like others have have commented, something else seems to be wrong. In my case (I am

[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module

2016-11-02 Thread kary
To wrap up my previous couple of comments and hopefully bisect the problem, I can state the following (thanks to BTRFS): This problem didn't / does not exist with: Description:Ubuntu Yakkety Yak (development branch) Linux acer07 4.8.0-21-generic #23-Ubuntu SMP Tue Oct 4 18:27:25 UTC 2016

[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module

2016-11-03 Thread kary
I did a little bit of more triaging: Staying on my Linux acer07 4.8.0-21-generic #23-Ubuntu SMP Tue Oct 4 18:27:25 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux and only upgrading from "nvidia-304 304.131-0ubuntu5" to "nvidia-304 304.132-0ubuntu1" brings up this problem. On the other hand,

[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module

2016-11-02 Thread kary
This was/is working in: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Codename: yakkety $ uname -a Linux acer07 4.8.0-21-generic #23-Ubuntu SMP Tue Oct 4 18:27:25 UTC 2016 x86_64 x86_64

[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module

2016-11-02 Thread kary
kari@acer07:~$ dpkg -l nvidia-304 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description

[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module

2016-11-02 Thread kary
Thanks Mario, but for me, that doesn't help: model: C61 [GeForce 6100 nForce 405] vendor : NVIDIA Corporation driver : nvidia-304 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin nvidia-304 is the problem and I've tried Nouveau earlier with no

[Ubuntu-x-swat] [Bug 1711758] Re: artful: nvidia-304 unknown symbol init_mm

2017-08-25 Thread kary
I have the same problem. It seems, that the problem came with kernel 4.12. Nvidia-304 has worked without problems for me in artful with kernels up till 4.11. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.

[Ubuntu-x-swat] [Bug 1751147] Re: nvidia-304 kernel module failed to build with new bionic kernel [error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’?]

2018-02-22 Thread kary
I saw the same problem. Similar discussion can be found: https://devtalk.nvidia.com/default/topic/1026876/patch-for-387-34-and- linux-4-15-0-rc1/ . I tested a similar fix and was able to get the kernel module built and running. My fix attached. ** Attachment added: "fix-for-4.15-timer-change"