[opensuse] Kernel 4.2.0 + Nvidia driver
The latest Nvidia drivers (x.30 & *.41) will not compile with the new kernel 4.2.0-1. If you are going to install the latest kernel take steps to make sure that you can still boot into your system - eg, make a backup of /boot before running the upgrade. BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.2.0-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/01/2015 11:56 PM, Basil Chupin wrote:
The latest Nvidia drivers (x.30 & *.41) will not compile with the new kernel 4.2.0-1.
If you are going to install the latest kernel take steps to make sure that you can still boot into your system - eg, make a backup of /boot before running the upgrade.
BC
Actually there has been a problem since the 3.18.17 kernel. At least with the 304-125 version. Not sure why nvidia hasn't fix it yet. Haven't tried the 4.2 kernel yet but this works on a 4.1.x kernel. diff -urN nvidia-304.125/nv.c nvidia-304.125a/nv.c --- nvidia-304.125/nv.c 2015-06-05 08:04:00.626286552 -0400 +++ nvidia-304.125a/nv.c 2015-04-20 14:47:35.917787839 -0400 @@ -2026,7 +2026,11 @@ unsigned long i_arg ) { +#if LINUX_VERSION_CODE < KERNEL_VERSION(3,19,0) return nv_kern_ioctl(file->f_dentry->d_inode, file, cmd, i_arg); +#else + return nv_kern_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg); +#endif } long nv_kern_compat_ioctl( @@ -2035,7 +2039,11 @@ unsigned long i_arg ) { +#if LINUX_VERSION_CODE < KERNEL_VERSION(3,19,0) return nv_kern_ioctl(file->f_dentry->d_inode, file, cmd, i_arg); +#else + return nv_kern_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg); +#endif } /* diff -urN nvidia-304.125/nv-pat.c nvidia-304.125a/nv-pat.c --- nvidia-304.125/nv-pat.c 2015-06-05 08:04:00.629619775 -0400 +++ nvidia-304.125a/nv-pat.c 2015-07-21 10:59:04.364708418 -0400 @@ -35,8 +35,13 @@ unsigned long cr0 = read_cr0(); write_cr0(((cr0 & (0xdfffffff)) | 0x40000000)); wbinvd(); - *cr4 = read_cr4(); - if (*cr4 & 0x80) write_cr4(*cr4 & ~0x80); +#if LINUX_VERSION_CODE < KERNEL_VERSION(3,18,17) + *cr4 = read_cr4(); + if (*cr4 & 0x80) write_cr4(*cr4 & ~0x80); +#else + *cr4 = __read_cr4(); + if (*cr4 & 0x80) __write_cr4(*cr4 & ~0x80); +#endif __flush_tlb(); } @@ -46,7 +51,11 @@ wbinvd(); __flush_tlb(); write_cr0((cr0 & 0x9fffffff)); - if (cr4 & 0x80) write_cr4(cr4); +#if LINUX_VERSION_CODE < KERNEL_VERSION(3,18,17) + if (cr4 & 0x80) write_cr4(cr4); +#else + if (cr4 & 0x80) __write_cr4(cr4); +#endif } static int nv_determine_pat_mode(void) Regards Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/09/15 23:00, Mark Hounschell wrote:
On 09/01/2015 11:56 PM, Basil Chupin wrote:
The latest Nvidia drivers (x.30 & *.41) will not compile with the new kernel 4.2.0-1.
If you are going to install the latest kernel take steps to make sure that you can still boot into your system - eg, make a backup of /boot before running the upgrade.
BC
Actually there has been a problem since the 3.18.17 kernel. At least with the 304-125 version. Not sure why nvidia hasn't fix it yet. Haven't tried the 4.2 kernel yet but this works on a 4.1.x kernel.
[pruned] Thanks for the patch. Sorry for not replying earlier but I couldn't boot into my main system (desktop) after I shut down even though I warned others about making sure to do a backup of /boot before upgrading to kernel 4.2 :-( . Replying now using the laptop - it's a long story! :-) . I have had NO problems with compiling earlier versions of the Nvidia driver (from Nvidia) using the earlier versions of the kernel. The driver you mention looks to me like quite an old one. BTW, I just looked at the Nvidia site and there is a new driver available - 355.11, released 31 August - which, I hope has been massaged to compile with kernel 4.2. I'll try it later. BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 04.09.2015 um 04:34 schrieb Basil Chupin:
On 02/09/15 23:00, Mark Hounschell wrote:
On 09/01/2015 11:56 PM, Basil Chupin wrote:
The latest Nvidia drivers (x.30 & *.41) will not compile with the new kernel 4.2.0-1.
BTW, I just looked at the Nvidia site and there is a new driver available - 355.11, released 31 August - which, I hope has been massaged to compile with kernel 4.2. I'll try it later.
no, it will NOT compile! it is a problem from the kernel: http://rglinuxtech.com/?p=1550 https://devtalk.nvidia.com/default/topic/849913/driver-fails-to-compile-on-4... https://forums.geforce.com/default/topic/849487/linux-v4-2-uses-gpl-only-sym... you have to downgrade to kernel 4.1.6 until this is fixed in the kernel. maybe kernel 4.2.1 will fix it. there was a fix in kernel 4.2-rc5 but it was removed after rc5. -- Best Regards | Liebe Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales Rainer Klier Research & Development SIGNificant Signature Solutions GmbH (a xyzmo company) Haider Straße 23 | 4052 Ansfelden | Austria Phone: +43 7229 88060 -707 Website: https://www.xyzmo.com/ Support: https://www.xyzmo.com/contact/support Get documents signed. Anywhere. At any time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/15 19:35, Rainer Klier wrote:
Am 04.09.2015 um 04:34 schrieb Basil Chupin:
On 02/09/15 23:00, Mark Hounschell wrote:
On 09/01/2015 11:56 PM, Basil Chupin wrote:
The latest Nvidia drivers (x.30 & *.41) will not compile with the new kernel 4.2.0-1.
BTW, I just looked at the Nvidia site and there is a new driver available - 355.11, released 31 August - which, I hope has been massaged to compile with kernel 4.2. I'll try it later.
no, it will NOT compile!
it is a problem from the kernel:
http://rglinuxtech.com/?p=1550
https://devtalk.nvidia.com/default/topic/849913/driver-fails-to-compile-on-4...
https://forums.geforce.com/default/topic/849487/linux-v4-2-uses-gpl-only-sym...
you have to downgrade to kernel 4.1.6 until this is fixed in the kernel. maybe kernel 4.2.1 will fix it. there was a fix in kernel 4.2-rc5 but it was removed after rc5.
Thank you Rainer for this information. I note that kernel 4.2.0-2 is now available. Do you know if this one now has the "fix"? (My main system [desktop] is now so messed up that I am not moving back or forward until I am sure that the kernel is OK; I am using working bits on the laptop and some working bits on the desktop to get by at the moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it with BTFRS, or whatever that disaster is called, even though I told the partitioner not to touch that partition.) BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.09.2015 um 09:51 schrieb Basil Chupin:
On 04/09/15 19:35, Rainer Klier wrote:
I note that kernel 4.2.0-2 is now available. Do you know if this one now has the "fix"?
i have downloaded the rpm file and checked the changelog, but there is nothing in it which has anything to do with this fix. i think, we will have to wait at least for kernel 4.2.1... :-(
moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it
uahh! -- Best Regards | Liebe Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales Rainer Klier Research & Development SIGNificant Signature Solutions GmbH (a xyzmo company) Haider Straße 23 | 4052 Ansfelden | Austria Phone: +43 7229 88060 -707 Website: https://www.xyzmo.com/ Support: https://www.xyzmo.com/contact/support Get documents signed. Anywhere. At any time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/09/15 18:20, Rainer Klier wrote:
Am 08.09.2015 um 09:51 schrieb Basil Chupin:
On 04/09/15 19:35, Rainer Klier wrote:
I note that kernel 4.2.0-2 is now available. Do you know if this one now has the "fix"?
i have downloaded the rpm file and checked the changelog, but there is nothing in it which has anything to do with this fix.
Thank you for this info.
i think, we will have to wait at least for kernel 4.2.1... :-(
Groan..... but I now see that 4.2.0-3 is out. Any cause for a bit of a heart flutter? :-)
moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it
uahh!
Yes..... :-( . BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 09.09.2015 um 09:20 schrieb Basil Chupin:
On 08/09/15 18:20, Rainer Klier wrote:
Am 08.09.2015 um 09:51 schrieb Basil Chupin:
On 04/09/15 19:35, Rainer Klier wrote:
i think, we will have to wait at least for kernel 4.2.1... :-(
Groan..... but I now see that 4.2.0-3 is out. Any cause for a bit of a heart flutter? :-)
i think we are lucky. look at the changelog for kernel 4.2.0-5.1.g82076fa from the http://download.opensuse.org/repositories/Kernel:/HEAD/standard repo: * Mo Sep 07 2015 jslaby@suse.cz - workqueue: Make flush_workqueue() available again to non GPL modules. - commit 82076fa this seems to be our case! i am currently downloading and trying.... -- Best Regards | Liebe Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales Rainer Klier Research & Development SIGNificant Signature Solutions GmbH (a xyzmo company) Haider Straße 23 | 4052 Ansfelden | Austria Phone: +43 7229 88060 -707 Website: https://www.xyzmo.com/ Support: https://www.xyzmo.com/contact/support Get documents signed. Anywhere. At any time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 09.09.2015 um 15:16 schrieb Rainer Klier:
Am 09.09.2015 um 09:20 schrieb Basil Chupin:
On 08/09/15 18:20, Rainer Klier wrote:
Am 08.09.2015 um 09:51 schrieb Basil Chupin:
On 04/09/15 19:35, Rainer Klier wrote:
* Mo Sep 07 2015 jslaby@suse.cz - workqueue: Make flush_workqueue() available again to non GPL modules. - commit 82076fa
this seems to be our case!
i am currently downloading and trying....
WORKING! :-D -- Best Regards | Liebe Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales Rainer Klier Research & Development SIGNificant Signature Solutions GmbH (a xyzmo company) Haider Straße 23 | 4052 Ansfelden | Austria Phone: +43 7229 88060 -707 Website: https://www.xyzmo.com/ Support: https://www.xyzmo.com/contact/support Get documents signed. Anywhere. At any time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Or we could ask openSUSE kernel maintainers to cherrypick
1dadafa86a779884f14a6e7a3ddde1a57b0a0a65
(https://lkml.org/lkml/2015/9/3/411) from mainline until next 4.2
release.
2015-09-08 11:20 GMT+03:00 Rainer Klier
Am 08.09.2015 um 09:51 schrieb Basil Chupin:
On 04/09/15 19:35, Rainer Klier wrote:
I note that kernel 4.2.0-2 is now available. Do you know if this one now has the "fix"?
i have downloaded the rpm file and checked the changelog, but there is nothing in it which has anything to do with this fix.
i think, we will have to wait at least for kernel 4.2.1... :-(
moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it
uahh!
-- Best Regards | Liebe Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales
Rainer Klier Research & Development
SIGNificant Signature Solutions GmbH (a xyzmo company)
Haider Straße 23 | 4052 Ansfelden | Austria
Phone: +43 7229 88060 -707 Website: https://www.xyzmo.com/ Support: https://www.xyzmo.com/contact/support
Get documents signed. Anywhere. At any time.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Basil Chupin
(My main system [desktop] is now so messed up that I am not moving back or forward until I am sure that the kernel is OK; I am using working bits on the laptop and some working bits on the desktop to get by at the moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it with BTFRS, or whatever that disaster is called, even though I told the partitioner not to touch that partition.)
What is the bug number? Must make sure that this does not happen here. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/09/15 21:33, Patrick Shanahan wrote:
* Basil Chupin
[09-08-15 03:53]: [...] (My main system [desktop] is now so messed up that I am not moving back or forward until I am sure that the kernel is OK; I am using working bits on the laptop and some working bits on the desktop to get by at the moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it with BTFRS, or whatever that disaster is called, even though I told the partitioner not to touch that partition.) What is the bug number? Must make sure that this does not happen here.
Oh, don't YOU start with this "what is the bug report number" thing! :-) One doesn't cry 'wolf' on the first balls-up so one posts here and sees if someone else had similar problem. Another thing, reporting bugs has an entry which "asks" if the balls-up is reproducible and I am not about to try and 'reproduce' it on whatever remains of my working system. And in any case I don't have the time to even restore my system/systems because of other activities requiring my attention. So there. :-) BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Basil Chupin
On 08/09/15 21:33, Patrick Shanahan wrote:
* Basil Chupin
[09-08-15 03:53]: [...] (My main system [desktop] is now so messed up that I am not moving back or forward until I am sure that the kernel is OK; I am using working bits on the laptop and some working bits on the desktop to get by at the moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it with BTFRS, or whatever that disaster is called, even though I told the partitioner not to touch that partition.) What is the bug number? Must make sure that this does not happen here.
Oh, don't YOU start with this "what is the bug report number" thing! :-)
One doesn't cry 'wolf' on the first balls-up so one posts here and sees if someone else had similar problem.
Another thing, reporting bugs has an entry which "asks" if the balls-up is reproducible and I am not about to try and 'reproduce' it on whatever remains of my working system.
You cannot answer that you don't know and will not attempt?
And in any case I don't have the time to even restore my system/systems because of other activities requiring my attention.
You have time to complain here and rant about ...., but no time to attempt to get corrections made to the system that others might not face the same problems as you. Sounds a bit selfish or perhaps just an opportunity to cast derision upon the works of other.
So there.
so here
:-)
:^?? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/09/15 21:59, Patrick Shanahan wrote:
* Basil Chupin
[09-09-15 03:32]: On 08/09/15 21:33, Patrick Shanahan wrote:
* Basil Chupin
[09-08-15 03:53]: [...] (My main system [desktop] is now so messed up that I am not moving back or forward until I am sure that the kernel is OK; I am using working bits on the laptop and some working bits on the desktop to get by at the moment. The kernel is only partly to blame: I tried to recover the system on the desktop by installing the latest tumbleweed but this wiped out one of my main partitions with all my data on it by formatting it with BTFRS, or whatever that disaster is called, even though I told the partitioner not to touch that partition.) What is the bug number? Must make sure that this does not happen here. Oh, don't YOU start with this "what is the bug report number" thing! :-)
One doesn't cry 'wolf' on the first balls-up so one posts here and sees if someone else had similar problem.
Another thing, reporting bugs has an entry which "asks" if the balls-up is reproducible and I am not about to try and 'reproduce' it on whatever remains of my working system. You cannot answer that you don't know and will not attempt?
There are a number of reasons why any attempt to recover did not occur - but may now occur in the next day or so. When you have your wife getting all excited about the delivery of her new car, preparing for an interstate trip, plus a few other matters, and in the middle of all this one gets a stuff up of your system which was working almost without a hitch for years, the mind goes into "safety first" mode :-) . When I was working I was able to handle, say, a dozen problems at the same time... but no more nowadays :-) . Just dealing with the wife on a daily basis is enough. But then add something like kernel 4.2.0 and then end-of-August release of Tumbleweed and ...... :'( .
And in any case I don't have the time to even restore my system/systems because of other activities requiring my attention. You have time to complain here and rant about ...., but no time to attempt to get corrections made to the system that others might not face the same problems as you. Sounds a bit selfish or perhaps just an opportunity to cast derision upon the works of other.
I cast no derision "upon the works of other[s]". Never have, never willl - so do not put words into my mouth or provide others who may have read your post with such demeaning information. Your wording actually is a criticism of anyone who raises a question about or disagrees with anything being put forward in any of the openSUSE software. Of course you are not the only one expressing such ideas. I have dealt with programmers - when they were actually called programmers, which they are, before they started calling themselves "engineers" ("engineers", for Chrissake!) - but I won't mention here what the last one I had to deal cost the organisation I was with because HE knew what was best for the end user and not what we asked him what we wanted. Are the little bells about KDE5,also known as Plasma 5, starting to tinkle?
So there.
so here
Which, of course reminds me of the skit by Abbott and Costello where Abbott bets Costello $10 that he (Abbott) can prove that Costello in not here - that is, in front of Abbott. Naturally Costello accepts this be as he simply cannot lose this bet! And so (with pardons to the original version which I am paraphrasing) ..... ABBOTT (to Costello): Are in Paris? COSTELLO: No! ABBOTT: Are in London? COSTELLO: No! ABBOTT: Are in Tokyo? COSTELLO: No! ABBOTT: Well, if you are not in Paris and not in London and not in Tokyo then you must be somewhere else, right? COSTELLO: Yes, right! ABBOTT: Well, if you are somewhere else then you cannot be here, right? Now give me the $10.
:-) :^??
Sorry, but what exactly does ":^??" convert to as an emoticon? BC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Dziahel
-
Basil Chupin
-
Mark Hounschell
-
Patrick Shanahan
-
Rainer Klier