Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
JK, the link you need to fully unsubscribe is well hidden: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1431753/+subscriptions, and then the bottom link, assuming that you are signed in to launchpad. HTH R. On 15/08/15 02:33, J K Cunningham wrote: On 08/14/2015 01:46 PM, teo1978 wrote: Are you aware that each comment triggers THOUSAND of emails to other users? Are you aware that you can unsubscribe if you want to? I unsubscribed from this bug report days ago and it's still sending me your silly tirades. Would you please STFU? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Much obliged. --Jeff On 08/15/2015 03:03 AM, Robin wrote: JK, the link you need to fully unsubscribe is well hidden: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1431753/+subscriptions, and then the bottom link, assuming that you are signed in to launchpad. HTH R. On 15/08/15 02:33, J K Cunningham wrote: On 08/14/2015 01:46 PM, teo1978 wrote: Are you aware that each comment triggers THOUSAND of emails to other users? Are you aware that you can unsubscribe if you want to? I unsubscribed from this bug report days ago and it's still sending me your silly tirades. Would you please STFU? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 14-08-15 10:52:23, teo1978 wrote: This, while unfortunate, is not a bug, Yes it is. You are only giving a diagnosis of the exact cause of the bug (which by the way I already knew), but that doesn't make it less of a bug. The alternatives switched back to automatic mode, and in automatic mode the nvidia alternative has a higher priority than mesa's (which is what you want). You can either select the mesa alternative, call ldconfig, and update the initramfs, or uninstall the nvidia package (as I recommended). and we cannot change it, due to the way alternatives work. I seriously doubt that's IMPOSSIBLE to fix. It may not be easy, but if you can do it manually, it can be done automatically. You only need to produce a script that looks at the settings (alternatives, or whatever) before uninstalling the old package, and then applies them (with all the necessary remappings and modifications) after installing the new one. It may be a lot of work but it's NECESSARY and it was part of fixing this issue. A part that hasn't been done. Such work is not necessary, as yours is really an unsupported corner case. If you insist on keeping the nvidia driver installed and disabled, against what we recommend, that is your problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Unfortunately, to get newer versions and hopefully out of Nvidia kernel update hell, I went from LTS to the next regular unsupported, hoping to go beyond that one to contemporary, but all went astray into unstable and unbootable, probably in the filing to upgrade multiple times, repository problems and bugs in same... Possibly waiting a bit on 15.10alpha to mature and upgrade nonbootable disk from cdr/dvdr/usbstick/netboot to get back to a working system. Waiting for godot was too frustrating. On Fri, Aug 14, 2015, 09:36 teo1978 teo8...@gmail.com wrote: If you have a machine that works, and you run automatic updates, and your machine stops working, there's a bug. If there's anything wrong in the machine configuration when you are updating, it must be detected, a warning given, and the option to continue at your own risk or skip that update. -- You received this bug notification because you are subscribed to a duplicate bug report (1405597). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Invalid Status in nvidia-graphics-drivers-331-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 13-08-15 16:50:40, teo1978 wrote: By design a driver will be enabled if you install it. However, if it is disable when you UPGRADE the driver, it shouldn't be reenabled. Right, that usually doesn't happen when you upgrade to a new version of the same driver (for example upgrading nvidia-331 from 331.19 to 331.25). However, when you are migrated to a different driver package, e.g. from nvidia-331 to nvidia-340, you will lose your settings, because they are different packages and they provide different alternatives (note: the alternatives are what allows you to enable or disable a driver). This, while unfortunate, is not a bug, and we cannot change it, due to the way alternatives work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 13-08-15 16:45:47, teo1978 wrote: 2) Optimus is supported by the NVIDIA driver. That's not what NVidia told me. I asked for support and they told me it's officially unsupported on Linux. And what I can tell for sure is that it doesn't work. The screen switching issue is well known. That only means that, if something goes wrong, you're on your own (at least as far as NVIDIA are concerned). Support for Optimus is something that we provide using our own system. What the NVIDIA driver supports is part of the RandR 1.4, which we use for Optimus. I won't comment on the screen switching issue, unless I see the relevant logs (in a separate bug report), as it could depend on a number of things (including your hardware configuration). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 14-08-15 13:24:50, teo1978 wrote: Such work is not necessary, as yours is really an unsupported corner case. If you insist on keeping the nvidia driver installed and disabled, against what we recommend, that is your problem. And how was I supposed to know what you recommend? Back in the days when I installed Ubuntu on my machine, there was a friendly interface somewhere like Software Updates Additional Drivers or something, where I could choose to install and use the NVidia drivers. Then, when I saw they wouldn't work, I went to the same interface and chose not to use them. No warning appeared telling me that was not recommended or that I should uninstall the drivers. Different use cases were supported in 12.04. For example, you could have multiple nvidia drivers installed at the same time. That changed after 12.04. And also, if a piece of software is designed in such a way that if you stop using it yoy have to uninstall it otherwise it may be harmful, it is badly designed. Ok, that implies that all drivers are badly designed. It's your opinion. This, however, is a bug report. Now please stop posting, as this bug report is closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Guys it's a closed source driver. I'm being a hypocrite here, but chillax. On 14 Aug 2015 21:16, teo1978 teo8...@gmail.com wrote: And also, if a piece of software is designed in such a way that if you stop using it yoy have to uninstall it otherwise it may be harmful, it is badly designed. Ok, that implies that all drivers are badly designed. It's your opinion. Don't pretend you are stupid when you aren't. This driver used to have an option (nicely accessible through user interface) which allowed to just not use it. It was *designed* to be either used or not used. And when not used, it would do nothing and interfere with nothing. So, the newer version doesn't that anymore? Then you can't replace one version with another without performing some check. The update is incomplete and buggy if it does that. -- You received this bug notification because you are subscribed to a duplicate bug report (1411195). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Invalid Status in nvidia-graphics-drivers-331-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 08/14/2015 01:46 PM, teo1978 wrote: Are you aware that each comment triggers THOUSAND of emails to other users? Are you aware that you can unsubscribe if you want to? I unsubscribed from this bug report days ago and it's still sending me your silly tirades. Would you please STFU? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Teo, the Optimus issue is definitely a *separate bug*, requiring its own resolution. R. On 13/08/15 14:48, teo1978 wrote: Or should we file a separate bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 11-08-15 22:45:43, teo1978 wrote: So, will my 331 drivers be automagically replaced with 340, or with whatever version fixes the bug? (or perhaps they have already?) Because otherwise, the bug is not fixed for me nor for the millions of people having ubuntu 14.04 with 331 drivers. Anyway, if that's not going to be automatic, what should I do to get that? Yes, 331 will be replaced by 340 through a system update. If you prefer 346 you can install it manually from our repositories (as long as your graphics card is supported). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 12-08-15 13:33:31, teo1978 wrote: Yes, 331 will be replaced by 340 through a system update. Nice, but is it possible that it not only replaces 331 by 340 but ALSO ENABLES THEM? Because I'm under the impression that that just happened to me, and that's a bug. Ages ago, when I first enabled NVidia drivers, I had this problem that every time I would connect and disconnect an external screen, the computer would start to randomly freeze at any moment. It turned out it was because the lack of support of NVidia drivers for Optimus technology on Linux. So I SWITCHED TO NOUVEAU, and had never been using NVidia drivers ever since, which was/is the only option for those like me who have an Optimus device. And that issue disappeared (though the NVidia drivers were still installed and gave me the compile error at every kernel upgrade). Now, THE FREEZING ISSUE HAS REAPPEARED. I suspect the update not only replaced 331 with 340 drivers, but also enabled them while I had explicitly disabled them in favour of Nouveau. Please how do I disable them again? And please change back the status of this bug until this part is fixed too. If you uninstall the drivers, you won't get any updates. Also, this bug report shouldn't affect you at all if the nvidia drivers are not installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
I flagged as security, since holds back kernel updates which escalated sec probs, if not causes them. Ianal On Aug 11, 2015 3:21 AM, ciro santoro 1431...@bugs.launchpad.net wrote: I installed last updates on my ubuntu 14.04 and, after reboot, it starts and remains with a black screen.. I listened the ubuntu welcome sound and nothing appens :( 2015-08-08 20:51 GMT+02:00 Nathanaël Naeri 1431...@bugs.launchpad.net: Packages nvidia-331-* are now transitional packages for version 340 where this bug has been fixed, so I guess they can be marked as Fix Released too. Thanks everyone involved esp. Alberto for your work. -- You received this bug notification because you are subscribed to a duplicate bug report (1409930). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Ciro Santoro -- You received this bug notification because you are subscribed to a duplicate bug report (1405597). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
I installed last updates on my ubuntu 14.04 and, after reboot, it starts and remains with a black screen.. I listened the ubuntu welcome sound and nothing appens :( 2015-08-08 20:51 GMT+02:00 Nathanaël Naeri 1431...@bugs.launchpad.net: Packages nvidia-331-* are now transitional packages for version 340 where this bug has been fixed, so I guess they can be marked as Fix Released too. Thanks everyone involved esp. Alberto for your work. -- You received this bug notification because you are subscribed to a duplicate bug report (1409930). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Ciro Santoro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
I had the same experience. It turned out thet my xorg.conf file had been renamed with a .back suffix. I copied it back and restarted, and all was good. On August 11, 2015 9:14:05 AM CEST, ciro santoro 1431...@bugs.launchpad.net wrote: I installed last updates on my ubuntu 14.04 and, after reboot, it starts and remains with a black screen.. I listened the ubuntu welcome sound and nothing appens :( 2015-08-08 20:51 GMT+02:00 Nathanaël Naeri 1431...@bugs.launchpad.net: Packages nvidia-331-* are now transitional packages for version 340 where this bug has been fixed, so I guess they can be marked as Fix Released too. Thanks everyone involved esp. Alberto for your work. -- You received this bug notification because you are subscribed to a duplicate bug report (1409930). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Ciro Santoro -- You received this bug notification because you are subscribed to a duplicate bug report (1410245). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 31-05-15 03:23:09, KennoVO wrote: Nice! Will this work with the 3.13 kernel in 14.04 ? Also, do you have any idea when it will be available to end-users? Yes, the update is available in 14.04, and works with the kernels 14.04 ships with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Yeah (*pff*) De: josh joshuaglennmur...@gmail.com Para: el_gallo_a...@yahoo.com Enviado: Miércoles 12 de agosto de 2015 9:16 Asunto: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation Dude no one cares this is a bug reporting place not an opinion catcher. On 12 Aug 2015 11:46, teo1978 teo8...@gmail.com wrote: Please keep your subjective comments to yourself I think my comments were pretty objective. Ubuntu fails at providing a decent user experience, and it's getting worse. Ubuntu sucks at supporting NVidia (which is probably mostly NVidia's fault, but other distros do better nonetheless). Ubuntu spends very little effort in improving its desktop operating system since their interest have moved to mobile. Ubuntu fails at fixing bugs in a decent time. Now all of this may well be OT here, but they are facts, with little margin of subjectivity. -- You received this bug notification because you are subscribed to a duplicate bug report (1412043). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are subscribed to a duplicate bug report (1401725). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Dude no one cares this is a bug reporting place not an opinion catcher. On 12 Aug 2015 11:46, teo1978 teo8...@gmail.com wrote: Please keep your subjective comments to yourself I think my comments were pretty objective. Ubuntu fails at providing a decent user experience, and it's getting worse. Ubuntu sucks at supporting NVidia (which is probably mostly NVidia's fault, but other distros do better nonetheless). Ubuntu spends very little effort in improving its desktop operating system since their interest have moved to mobile. Ubuntu fails at fixing bugs in a decent time. Now all of this may well be OT here, but they are facts, with little margin of subjectivity. -- You received this bug notification because you are subscribed to a duplicate bug report (1412043). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
After routine kernel-update yesterday, today blank screen like KennoVO, bongos rumbling on start but without video. After booting with previous kernel I applied the solutions KennoVO suggested, (2)-(3)-(4) but not (1) as I didn't know what I was doing and didn't understand how it had to be done. But in the end after reboot it worked. No errors or other failures. I must say that while Ubuntu 10 and 12 were simply great, rapid booting, almost no bugs, this 14.04 has caused me a lot of grievance - slow on boot, updates that cause more problems than they solve, updates almost every time I turn on the computer (just like Windows...). Iif I didn't have an allergy towards Windows I would long have turned my back on Ubuntu. And if You add to it that Chromium has a sloppy Flash-player that doesn't work half the times, and the alternative Firefox is pretty slow. Takes a lot of passion to stick to Ubuntu... 2015-07-27 1:35 GMT+02:00 KennoVO ubu...@kenno.org: Fix confirmed on 2 very different machines both running Ubuntu 14.04 Trusty with the 3.13 kernel. Detailed notes: AMD workstation with only a discrete nvidia GPU (nothing else) Synaptic complained about conflicts when selecting updated driver from trusty-proposed (something involving nvidia-libopencl1-* vs nvidia-opencl-icd-* IIRC). Installing through aptitude worked better. No further issues when rebooting, updating the kernel and rebooting again. Intel laptop running bumblebee == Blank screen after updating. Solutions tried: (1) starting the kernel with nogpumanager and removing /etc/X11/xorg.conf generated by gpu-manager (2) removing the newly created file /etc/prime-discrete (3) sudo sed -i 's/-current/-346-updates/g' /etc/bumblebee/bumblebee.conf (4) adding lines for 340 and 346 to /etc/modprobe.d/bumblebee.conf Applying all of the above fixed the problem, and (1)-(3) without (4) didn't, so it's very likely that (4) is necessary. What I cannot tell is which of (1)-(3) are also necessary and which are optional.(*) Bottom line is that special precautions should be taken to prevent bumblebee from breaking when rolling this out. (*) I could of course figure that out by reverting the changes one-by- one, but this bug already robbed me of an outrageous amount of my time and all of my goodwill, so you're on your own. Thanks a lot for finally fixing it, though. -- You received this bug notification because you are subscribed to a duplicate bug report (1411919). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Committed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Dr. M. Tiede Clausola di Riservatezza Si fa presente che tutte le notizie (nomi, fatti, notizie sanitarie, etc) contenute in questo messaggio sono sottoposte alla normativa sulla tutela della riservatezza (D. Lgs 196/2003) e in particolare sulla
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
What I don't understand, the proposed drivers are they already implemented in the routine update (I thought they had to be updated manually)? Otherwise I might have had a completely different problem with the bumblebee and nvidia drivers, solved by chance with Your approach. 2015-07-27 18:33 GMT+02:00 KennoVO ubu...@kenno.org: Mat, I am happy you got past your blank-screen problem, even though the things mentioned in my previous post may or may not have played a role in solving it. To be perfectly clear toward other people who come across this discussion, the points (1)-(4) in my previous post DO NOT represent a step-by-step solution for getting a graphical desktop back after running a routine kernel upgrade. They are a few things *I* tried for the specific case of APPLYING THE DRIVERS FROM TRUSTY-PROPOSED TO AN EXISTING BUMBLEBEE SETUP. And it's quite likely some of them are not useful or even harmful. -- You received this bug notification because you are subscribed to a duplicate bug report (1411919). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Committed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Dr. M. Tiede Clausola di Riservatezza Si fa presente che tutte le notizie (nomi, fatti, notizie sanitarie, etc) contenute in questo messaggio sono sottoposte alla normativa sulla tutela della riservatezza (D. Lgs 196/2003) e in particolare sulla tutela dei dati sensibili. E' pertanto richiesta ai destinatari della presente la massima riservatezza nel trattare la documentazione. Se il ricevente non è il destinatario diretto del presente messaggio è pregato di contattare l'originario mittente e di cancellare questo messaggio ed ogni suo allegato dal sistema di posta, sono vietati l'uso, la riproduzione e la stampa di questo messaggio e di ogni suo allegato, nonché la diffusione del loro contenuto a qualsiasi altro soggetto. This e-mail message and any files transmitted with it may contain confidential information intended only for the person(s) to whom it is addressed. If you are not the intended recipient, you are hereby notified that any use or distribution of this e-mail is strictly prohibited: please notify the sender and delete the original message. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
My Bug problem has also been solved. How can I stop receiving these but reports? Many regards. Sent from my ASUS Original Message From:Marc Peña 1431...@bugs.launchpad.net Sent:Sat, 25 Jul 2015 20:35:46 +0200 To:macbu...@hotmail.de Subject:[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation Installed the nvidia-340 package from trusty-proposed and it did solve the bug. Didn't observe any regressions in my 3.13 kernel installation. Thanks a lot! -- You received this bug notification because you are subscribed to a duplicate bug report (1410036). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Committed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Thank you Zewbie Best Regards, Nima Soltani -- Graduate Student of Physical Chemistry Department of Chemistry, Sharif University of Technology. = On Sat, Jun 20, 2015 at 1:07 AM, Nima Soltani nima@gmail.com wrote: Thanks alot Best Regards, Nima Soltani -- Graduate Student of Physical Chemistry Department of Chemistry, Sharif University of Technology. = On Fri, Jun 19, 2015 at 11:29 PM, Pablo pablo...@gmail.com wrote: Nima, I moved to SteamOS. I am afraid you have to format your OS drive though. For me is important my NVidia works correctly for games and work projects. I know they will take care of that part. In general I like Debian or Debian variants. They have a huge number of packages. -- You received this bug notification because you are subscribed to a duplicate bug report (1268257). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Hello how can I unsubscribe this? On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com wrote: I am already working on it (I've been busy with other work). There's no need to make this any more complicated than it needs to be. -- You received this bug notification because you are subscribed to a duplicate bug report (1395993). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
You may remove yourself from this thread at anytime, since you have seemed to have resolved this issue thanks and all the best. Sent from my Sprint Samsung Galaxy S® 6. Original message From: Jonners59 1431...@bugs.launchpad.net Date: 06/19/2015 5:49 AM (GMT-07:00) To: zew...@yahoo.com Subject: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation Please stop this banter, clogging my emails up. I sorted my PCs and laptops out with the following fix for now. Not had ANY issues since doing below: Card driver http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk nVidia Boot and after GRUB… Control+ALT+F1 Sudo su sudo update-pciids sudo lspci -v -s 01:00.0 Sudo service lightdm stop (stopping lightdm) sudo apt-get clean apt-get autoclean apt-get autoremove (a little cleaning) sudo apt-get update apt-get install –f (update source and fix) sudo apt-get purge libvdpau-va-gl1 bumblebee* nvidia* OR dpkg -l | grep nvidia lists everything installed for nvidia then remove everything except nvidia-cg-toolkit (if it or equivellent exists) nvidia-common sudo apt-get purge nvidia- (where is anything from the list) sudo apt-get autoremove sudo dpkg-reconfigure nvidia-common (should return a message does not exist) sudo apt-get install nvidia-352 nvidia-settings nvidia-prime nvidia-current nvidia-cg-toolkit nvidia-common OR Sudo apt-get install --reinstall nvidia-xxx-updates-uvm (install nvidia-xxx where xxx is driver version: 304, 331, 340, 349, 352 or current) sudo apt-get install xserver-xorg-video-nouveau sudo apt-get install linux-headers-generic sudo apt-get clean apt-get autoclean apt-get autoremove sudo apt-get apt-get upgrade update apt-get install –f sudo update-alternatives --config x86_64-linux-gnu_gl_conf sudo ldconfig -n sudo update-initramfs -u sudo shutdown –r now Let the devs get on and do perm fix in the meantime. -- You received this bug notification because you are subscribed to a duplicate bug report (1382608). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Scroll to the very bottom and follow the link Sent from my Sprint Samsung Galaxy S® 6. Original message From: Umut Yazgan umut@gmail.com Date: 06/19/2015 6:06 AM (GMT-07:00) To: zew...@yahoo.com Subject: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation Hello how can I unsubscribe this? On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com wrote: I am already working on it (I've been busy with other work). There's no need to make this any more complicated than it needs to be. -- You received this bug notification because you are subscribed to a duplicate bug report (1395993). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are subscribed to a duplicate bug report (1382608). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Friends, are you kidding? It is enough, please do not pollute this thread any longer! If you wonder anything, please google it first. If you cannot find anything, open a new issue in a related place. Be more responsive please! Sorry, I have also made dirty the mail thread but these were necessary to tell. Scroll to the very bottom and follow the link Sent from my Sprint Samsung Galaxy S® 6. Original message From: Umut Yazgan umut@gmail.com Date: 06/19/2015 6:06 AM (GMT-07:00) To: zew...@yahoo.com Subject: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation Hello how can I unsubscribe this? On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com wrote: I am already working on it (I've been busy with other work). There's no need to make this any more complicated than it needs to be. -- You received this bug notification because you are subscribed to a duplicate bug report (1395993). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are subscribed to a duplicate bug report (1382608). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Thanks! On Jun 19, 2015 15:31, Zewbie 1431...@bugs.launchpad.net wrote: Scroll to the very bottom and follow the link Sent from my Sprint Samsung Galaxy S® 6. Original message From: Umut Yazgan umut@gmail.com Date: 06/19/2015 6:06 AM (GMT-07:00) To: zew...@yahoo.com Subject: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation Hello how can I unsubscribe this? On Jun 16, 2015 13:41, Alberto Milone alberto.mil...@canonical.com wrote: I am already working on it (I've been busy with other work). There's no need to make this any more complicated than it needs to be. -- You received this bug notification because you are subscribed to a duplicate bug report (1395993). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are subscribed to a duplicate bug report (1382608). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS
RE: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Try fedora 21 not 22 Sent from my Sprint Samsung Galaxy S® 6. Original message From: Nima nima@gmail.com Date: 06/19/2015 3:43 AM (GMT-07:00) To: zew...@yahoo.com Subject: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation I want to go to another linux distribution , Can any body give me a hint about it? CentOS or Opensuse? Which one is better? which one has a full resource of software like ,for example ubuntu software center? Thanks for any help in advance -- You received this bug notification because you are subscribed to a duplicate bug report (1382608). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
OSX is the way to go for sure...sorry for the annoying email alert On Fri, Jun 19, 2015 at 4:32 AM Camil Staps i...@camilstaps.nl wrote: Zewbie, what is wrong with you? Did you not read #29 and #35? Do you have any idea how many people are getting an email when you comment on this bug? Have a little responsibility. -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Nima this really isn't the place for that talk. Will EVERYONE please keep this thread on topic about this bug and only this bug please On 19 Jun 2015 21:51, Nima nima@gmail.com wrote: I want to go to another linux distribution , Can any body give me a hint about it? CentOS or Opensuse? Which one is better? which one has a full resource of software like ,for example ubuntu software center? Thanks for any help in advance -- You received this bug notification because you are subscribed to a duplicate bug report (1412043). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
No vendor cares about linux On Thu, Jun 18, 2015 at 11:46 AM Heath heathnay...@gmail.com wrote: This seems to me like a trivial bug fix, is this just nVidia not wanting to devote time to a fix? -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Just use Debian. No one considers Ubuntu secure any more after the privacy violations embedded by Canonical. On Thu, Jun 18, 2015 at 12:41 PM rbscy...@yahoo.ca rbscy...@yahoo.ca wrote: That may be so. However, I care. I use Linux as my everyday computer at home for everything. I use the LTS version because I expect less problems, and don't really know a hell-of-a-lot about the underneath workings of Linux. If this means I have to go to another distribution, so be it. On 15-06-18 03:09 PM, Kristian Erik Hermansen wrote: No vendor cares about linux On Thu, Jun 18, 2015 at 11:46 AM Heath heathnay...@gmail.com wrote: This seems to me like a trivial bug fix, is this just nVidia not wanting to devote time to a fix? -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ** Attachment added: ronnie6.png https://bugs.launchpad.net/bugs/1431753/+attachment/4416893/+files/ronnie6.png -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Can you guys not litter the bug report? On Fri, Jun 19, 2015 at 6:18 AM, Kristian Erik Hermansen kristian.herman...@gmail.com wrote: Just use Debian. No one considers Ubuntu secure any more after the privacy violations embedded by Canonical. On Thu, Jun 18, 2015 at 12:41 PM rbscy...@yahoo.ca rbscy...@yahoo.ca wrote: That may be so. However, I care. I use Linux as my everyday computer at home for everything. I use the LTS version because I expect less problems, and don't really know a hell-of-a-lot about the underneath workings of Linux. If this means I have to go to another distribution, so be it. On 15-06-18 03:09 PM, Kristian Erik Hermansen wrote: No vendor cares about linux On Thu, Jun 18, 2015 at 11:46 AM Heath heathnay...@gmail.com wrote: This seems to me like a trivial bug fix, is this just nVidia not wanting to devote time to a fix? -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ** Attachment added: ronnie6.png https://bugs.launchpad.net/bugs/1431753/+attachment/4416893/+files/ronnie6.png -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are subscribed to a duplicate bug report (1412105). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
That may be so. However, I care. I use Linux as my everyday computer at home for everything. I use the LTS version because I expect less problems, and don't really know a hell-of-a-lot about the underneath workings of Linux. If this means I have to go to another distribution, so be it. On 15-06-18 03:09 PM, Kristian Erik Hermansen wrote: No vendor cares about linux On Thu, Jun 18, 2015 at 11:46 AM Heath heathnay...@gmail.com wrote: This seems to me like a trivial bug fix, is this just nVidia not wanting to devote time to a fix? -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ** Attachment added: ronnie6.png https://bugs.launchpad.net/bugs/1431753/+attachment/4416893/+files/ronnie6.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
I want zero downtime, top tier speed, and zero cost. On Thu, Jun 18, 2015 at 2:09 PM, Kristian Erik Hermansen kristian.herman...@gmail.com wrote: No vendor cares about linux On Thu, Jun 18, 2015 at 11:46 AM Heath heathnay...@gmail.com wrote: This seems to me like a trivial bug fix, is this just nVidia not wanting to devote time to a fix? -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are subscribed to a duplicate bug report (1399042). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Thanks, -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Can't fix binaries without patching On Thu, Jun 18, 2015 at 4:35 PM Pablo pablo...@gmail.com wrote: Could you fix it? -- You received this bug notification because you are subscribed to a duplicate bug report (1405694). https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
SO, since I don't know that much . On one of my computers (HP s3720f) my display disappeared completely. I tried a bunch of things. The last thing I tried seem to work: $ sudo apt-get --purge remove xserver-xorg-video-nouveau $ sudo ubuntu-drivers devices A list of drivers will appear. Pick a driver to install and... sudo apt-get install nvidia-172 (for example) Interestingly enough, this computer (HP s3720f) has not complained about any updates since ... at least not yet!!! On 15-06-17 09:49 AM, Todd wrote: hahah couldnt agree more @pabloa98 -- ** Attachment added: ronnie6.png https://bugs.launchpad.net/bugs/1431753/+attachment/4416334/+files/ronnie6.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
