[opensuse] Re: installing the proprietary nvidia drivers (was: MSI GE72 2QC Apache with Nvidia GTX960 ...)
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist.
I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver. Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says? -- Per Jessen, Zürich (4.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Idézet (Per Jessen <per@computer.org>):
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist.
I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
-- Per Jessen, Zürich (4.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Well, Im quite but not absolutely sure. Installation said it could not symlink to /usr/lib/libGL.so.1, libGL.so and libGLX_nvidia.so.0. And in a second sentence: Reason: "file exists". I would experiment with the driver, if I knew how to revert without much pain to nouveau, i.e a working system. BTW the final step of installation is to run mkinitrrd, but it hangs for me. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
oszko@chem.u-szeged.hu wrote:
Idézet (Per Jessen <per@computer.org>):
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist.
I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
-- Per Jessen, Zürich (4.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Well, Im quite but not absolutely sure. Installation said it could not symlink to /usr/lib/libGL.so.1, libGL.so and libGLX_nvidia.so.0. And in a second sentence: Reason: "file exists".
That sounds like it couldn't create the symlink because it already exists.
I would experiment with the driver, if I knew how to revert without much pain to nouveau, i.e a working system.
When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd.
BTW the final step of installation is to run mkinitrrd, but it hangs for me.
That's a serious problem - you're it's hanging and not just taking longer the normal? At which stage does it appear to be hanging? -- Per Jessen, Zürich (4.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14/03/16 23:31, Per Jessen wrote:
oszko@chem.u-szeged.hu wrote:
Idézet (Per Jessen <per@computer.org>):
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist. I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
-- Per Jessen, Zürich (4.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Well, Im quite but not absolutely sure. Installation said it could not symlink to /usr/lib/libGL.so.1, libGL.so and libGLX_nvidia.so.0. And in a second sentence: Reason: "file exists". That sounds like it couldn't create the symlink because it already exists.
I would experiment with the driver, if I knew how to revert without much pain to nouveau, i.e a working system. When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd.
Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot.
BTW the final step of installation is to run mkinitrrd, but it hangs for me. That's a serious problem - you're it's hanging and not just taking longer the normal? At which stage does it appear to be hanging?
BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.4.5-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 2016-03-14 14:28, Basil Chupin wrote:
I would experiment with the driver, if I knew how to revert without much pain to nouveau, i.e a working system. When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd.
Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot.
If you don't, the initrds still contains the nouveau module, it gets loaded, and nvidia module refuses to load. And viceversa. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 15/03/16 00:44, Carlos E. R. wrote:
On 2016-03-14 14:28, Basil Chupin wrote:
I would experiment with the driver, if I knew how to revert without much pain to nouveau, i.e a working system. When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd. Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot. If you don't, the initrds still contains the nouveau module, it gets loaded, and nvidia module refuses to load. And viceversa.
You have to compile the nVidia driver to work with the kernel you are using and when you go to compile it with the nouveau driver installed you get an error message and the nVidia driver will NOT compile until the nouveau driver is removed. I use the kernel in the .../Kernel:/stable/standard repository and have to compile the driver every time the kernel is upgraded -- sometimes on a daily basis. I don't run mkinitrd and I don't have any problems with compiling the driver. BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.4.5-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 2016-03-15 05:28, Basil Chupin wrote:
On 15/03/16 00:44, Carlos E. R. wrote:
On 2016-03-14 14:28, Basil Chupin wrote:
I would experiment with the driver, if I knew how to revert without much pain to nouveau, i.e a working system. When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd. Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot. If you don't, the initrds still contains the nouveau module, it gets loaded, and nvidia module refuses to load. And viceversa.
You have to compile the nVidia driver to work with the kernel you are using and when you go to compile it with the nouveau driver installed you get an error message and the nVidia driver will NOT compile until the nouveau driver is removed.
Yes, I did that, nvidia driver loaded fine, tested startx, I rebooted, and it failed to load. Nouveau was loaded again. I checked, run mkinird, rebooted, and it was ok, nividia.
I use the kernel in the .../Kernel:/stable/standard repository and have to compile the driver every time the kernel is upgraded -- sometimes on a daily basis. I don't run mkinitrd and I don't have any problems with compiling the driver.
Because you were not running nouveau the previous time, thus no need to remove it again. It is the first time, when you do the switch, that you have to do all those things. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 15/03/16 20:49, Carlos E. R. wrote:
On 2016-03-15 05:28, Basil Chupin wrote:
On 2016-03-14 14:28, Basil Chupin wrote:
I would experiment with the driver, if I knew how to revert without much pain to nouveau, i.e a working system. When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd. Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot. If you don't, the initrds still contains the nouveau module, it gets loaded, and nvidia module refuses to load. And viceversa. You have to compile the nVidia driver to work with the kernel you are using and when you go to compile it with the nouveau driver installed you get an error message and the nVidia driver will NOT compile until
On 15/03/16 00:44, Carlos E. R. wrote: the nouveau driver is removed. Yes, I did that, nvidia driver loaded fine, tested startx, I rebooted, and it failed to load. Nouveau was loaded again. I checked, run mkinird, rebooted, and it was ok, nividia.
I use the kernel in the .../Kernel:/stable/standard repository and have to compile the driver every time the kernel is upgraded -- sometimes on a daily basis. I don't run mkinitrd and I don't have any problems with compiling the driver. Because you were not running nouveau the previous time, thus no need to remove it again.
It is the first time, when you do the switch, that you have to do all those things.
Jesus, Carlos, let's look at what has been written and then make comments shall we? Someone wrote: "When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd." To which I replied: "Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot." Now, is there anything clearer and articulate than what I wrote in the above paragraph: "I just compile/install the driver and reboot"? "But", you say, "what about the nouveau driver?" to which I already said that the nVidia driver will not compile until the bloody thing is removed! So what is left? "I just compile/install the driver and reboot." Something still missing in the translation? Then please let me know. BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.4.5-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
Op dinsdag 15 maart 2016 22:30:43 CET schreef Basil Chupin:
On 15/03/16 20:49, Carlos E. R. wrote:
On 2016-03-15 05:28, Basil Chupin wrote:
On 15/03/16 00:44, Carlos E. R. wrote:
On 2016-03-14 14:28, Basil Chupin wrote:
> I would experiment with the driver, if I knew how to revert without > much pain to nouveau, i.e a working system.
When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd.
Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot.
If you don't, the initrds still contains the nouveau module, it gets loaded, and nvidia module refuses to load. And viceversa.
You have to compile the nVidia driver to work with the kernel you are using and when you go to compile it with the nouveau driver installed you get an error message and the nVidia driver will NOT compile until the nouveau driver is removed.
Yes, I did that, nvidia driver loaded fine, tested startx, I rebooted, and it failed to load. Nouveau was loaded again. I checked, run mkinird, rebooted, and it was ok, nividia.
I use the kernel in the .../Kernel:/stable/standard repository and have to compile the driver every time the kernel is upgraded -- sometimes on a daily basis. I don't run mkinitrd and I don't have any problems with compiling the driver.
Because you were not running nouveau the previous time, thus no need to remove it again.
It is the first time, when you do the switch, that you have to do all those things.
Jesus, Carlos, let's look at what has been written and then make comments shall we?
Someone wrote:
"When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd."
To which I replied:
"Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot."
Now, is there anything clearer and articulate than what I wrote in the above paragraph: "I just compile/install the driver and reboot"?
"But", you say, "what about the nouveau driver?" to which I already said that the nVidia driver will not compile until the bloody thing is removed!
So what is left? "I just compile/install the driver and reboot."
Something still missing in the translation? Then please let me know.
BC
1. The nvidia driver compile doesn't care whether nouveau or whatever is loaded. The installer does, but this can be overruled with options, like the --no-nouveau-check, --no-x-check. 2. If nouveau is loaded per initrd, one needs to rebuild the initrd after blacklisting nouveau. Whether it is depends on previously taken actions where reconfiguring / rebuilding initrd was involved. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/03/16 23:22, Knurpht - Gertjan Lettink wrote: > Op dinsdag 15 maart 2016 22:30:43 CET schreef Basil Chupin: >> On 15/03/16 20:49, Carlos E. R. wrote: >>> On 2016-03-15 05:28, Basil Chupin wrote: >>>> On 15/03/16 00:44, Carlos E. R. wrote: >>>>> On 2016-03-14 14:28, Basil Chupin wrote: >>>>>>>> I would experiment with the driver, if I knew how to revert without >>>>>>>> much pain to nouveau, i.e a working system. >>>>>>> When you want the proprietary driver, blacklist 'nouveau', when you >>>>>>> want >>>>>>> nouveau, un-blacklist it. Rebuild initrd. >>>>>> Strange -- I have never done this (rebuilding initrd). I just >>>>>> compile/install the driver and reboot. >>>>> If you don't, the initrds still contains the nouveau module, it gets >>>>> loaded, and nvidia module refuses to load. And viceversa. >>>> You have to compile the nVidia driver to work with the kernel you are >>>> using and when you go to compile it with the nouveau driver installed >>>> you get an error message and the nVidia driver will NOT compile until >>>> the nouveau driver is removed. >>> Yes, I did that, nvidia driver loaded fine, tested startx, I rebooted, >>> and it failed to load. Nouveau was loaded again. I checked, run mkinird, >>> rebooted, and it was ok, nividia. >>> >>>> I use the kernel in the .../Kernel:/stable/standard repository and have >>>> to compile the driver every time the kernel is upgraded -- sometimes on >>>> a daily basis. I don't run mkinitrd and I don't have any problems with >>>> compiling the driver. >>> Because you were not running nouveau the previous time, thus no need to >>> remove it again. >>> >>> It is the first time, when you do the switch, that you have to do all >>> those things. >> Jesus, Carlos, let's look at what has been written and then make >> comments shall we? >> >> Someone wrote: >> >> "When you want the proprietary driver, blacklist 'nouveau', when you >> want nouveau, un-blacklist it. Rebuild initrd." >> >> To which I replied: >> >> "Strange -- I have never done this (rebuilding initrd). I just >> compile/install the driver and reboot." >> >> Now, is there anything clearer and articulate than what I wrote in the >> above paragraph: "I just compile/install the driver and reboot"? >> >> "But", you say, "what about the nouveau driver?" to which I already said >> that the nVidia driver will not compile until the bloody thing is removed! >> >> So what is left? "I just compile/install the driver and reboot." >> >> Something still missing in the translation? Then please let me know. >> >> >> BC > 1. The nvidia driver compile doesn't care whether nouveau or whatever is > loaded. Of course I do not have the knowledge or the expertise which you seem to have, or at least express that you have, but the nVidia compiler DOES care if the nouveau driver is installed because it just won't continue with the compile until the nouveau is disabled. Are you saying all this from experience or from some theoretical concept? > The installer does, but this can be overruled with options, like the > --no-nouveau-check, --no-x-check. > 2. If nouveau is loaded per initrd, one needs to rebuild the initrd after > blacklisting nouveau. READ MY LIPS! I have NEVER had to rebuild initrd after compiling the nVidia driver. YES, as I said, FOR CHRISSAKE, the nouveau driver HAS to be disabled before the nVidia driver will compile but after that I have NEVER HAD TO REBUILD INITRD. HAVE I MADE THIS CLEAR OR NOT?! > Whether it is depends on previously taken actions where > reconfiguring / rebuilding initrd was involved. Read what I wrote above. BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.4.5-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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-03-15 14:29, Basil Chupin wrote: > On 15/03/16 23:22, Knurpht - Gertjan Lettink wrote: >> Op dinsdag 15 maart 2016 22:30:43 CET schreef Basil Chupin: >>> On 15/03/16 20:49, Carlos E. R. wrote: >>> Someone wrote: >>> >>> "When you want the proprietary driver, blacklist 'nouveau', >>> when you want nouveau, un-blacklist it. Rebuild initrd." >>> >>> To which I replied: >>> >>> "Strange -- I have never done this (rebuilding initrd). I just >>> compile/install the driver and reboot." >>> >>> Now, is there anything clearer and articulate than what I wrote >>> in the above paragraph: "I just compile/install the driver and >>> reboot"? >>> >>> "But", you say, "what about the nouveau driver?" to which I >>> already said that the nVidia driver will not compile until the >>> bloody thing is removed! >>> >>> So what is left? "I just compile/install the driver and >>> reboot." >>> >>> Something still missing in the translation? Then please let me >>> know. >>> >>> >>> BC >> 1. The nvidia driver compile doesn't care whether nouveau or >> whatever is loaded. > > Of course I do not have the knowledge or the expertise which you > seem to have, or at least express that you have, but the nVidia > compiler DOES care if the nouveau driver is installed because it > just won't continue with the compile until the nouveau is > disabled. > > Are you saying all this from experience or from some theoretical > concept? > >> The installer does, but this can be overruled with options, like >> the --no-nouveau-check, --no-x-check. 2. If nouveau is loaded per >> initrd, one needs to rebuild the initrd after blacklisting >> nouveau. > > READ MY LIPS! > > I have NEVER had to rebuild initrd after compiling the nVidia > driver. > > YES, as I said, FOR CHRISSAKE, the nouveau driver HAS to be > disabled before the nVidia driver will compile but after that I > have NEVER HAD TO REBUILD INITRD. > > HAVE I MADE THIS CLEAR OR NOT?! Please calm down. And I told you that I had to rebuild initrd or my system failed to start nvidia on the first boot after compiling the driver. This is correctly explained in the wiki. How do you figure it out? I know why, but you don't seem to understand. /YOU/ do not need to rebuild initrd because you are not switching to the nvidia driver, you are just compiling it again. Your case is different. Me, I was using nouveau. I compiled the driver. It worked. Rebooted. It did not work. I saw that nouveau was loaded. Yes, it was blacklisted, yet it was loaded. Why? Because I did not built initrd. I did, novueau got removed from it, the blaklist was inserted in the archive image, rebooted, and now, yes, I got nvidia working. Not before. Do you understand that? The next time I will only need to compile the driver. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlboMCIACgkQja8UbcUWM1x5dQD/Qhp2O1OWFrQvJhKnzVOsXcB7 LvALELy/HIIjPcLp39QA/3beL+4I4msDWzQwxtIiRw7VsL/WQM+g7OY5Yk6OEryE =IPoX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/03/16 02:54, Carlos E. R. wrote: > On 2016-03-15 14:29, Basil Chupin wrote: > > On 15/03/16 23:22, Knurpht - Gertjan Lettink wrote: > >> Op dinsdag 15 maart 2016 22:30:43 CET schreef Basil Chupin: > >>> On 15/03/16 20:49, Carlos E. R. wrote: > > > >>> Someone wrote: > >>> > >>> "When you want the proprietary driver, blacklist 'nouveau', > >>> when you want nouveau, un-blacklist it. Rebuild initrd." > >>> > >>> To which I replied: > >>> > >>> "Strange -- I have never done this (rebuilding initrd). I just > >>> compile/install the driver and reboot." > >>> > >>> Now, is there anything clearer and articulate than what I wrote > >>> in the above paragraph: "I just compile/install the driver and > >>> reboot"? > >>> > >>> "But", you say, "what about the nouveau driver?" to which I > >>> already said that the nVidia driver will not compile until the > >>> bloody thing is removed! > >>> > >>> So what is left? "I just compile/install the driver and > >>> reboot." > >>> > >>> Something still missing in the translation? Then please let me > >>> know. > >>> > >>> > >>> BC > >> 1. The nvidia driver compile doesn't care whether nouveau or > >> whatever is loaded. > > > Of course I do not have the knowledge or the expertise which you > > seem to have, or at least express that you have, but the nVidia > > compiler DOES care if the nouveau driver is installed because it > > just won't continue with the compile until the nouveau is > > disabled. > > > Are you saying all this from experience or from some theoretical > > concept? > > >> The installer does, but this can be overruled with options, like > >> the --no-nouveau-check, --no-x-check. 2. If nouveau is loaded per > >> initrd, one needs to rebuild the initrd after blacklisting > >> nouveau. > > > READ MY LIPS! > > > I have NEVER had to rebuild initrd after compiling the nVidia > > driver. > > > YES, as I said, FOR CHRISSAKE, the nouveau driver HAS to be > > disabled before the nVidia driver will compile but after that I > > have NEVER HAD TO REBUILD INITRD. > > > HAVE I MADE THIS CLEAR OR NOT?! > > Please calm down. I AM calm ... until I am pushed..... > And I told you that I had to rebuild initrd or my system failed to > start nvidia on the first boot after compiling the driver. This is > correctly explained in the wiki. > > How do you figure it out? I know why, but you don't seem to understand. > > /YOU/ do not need to rebuild initrd because you are not switching to > the nvidia driver, you are just compiling it again. Your case is > different. > > Me, I was using nouveau. I compiled the driver. Groan.... here we go again :-( . I repeat: READ MY LIPS! The nVidia driver will NOT compile if the nouveua driver is installed! The nVidia driver compiler detects that the nouveau driver is installed, stops compiling and asks you if you want it disabled/removed/whatever. > It worked. It couldn't have worked. What worked was the nouveau driver and not the nVidia driver. > Rebooted. > It did not work. I saw that nouveau was loaded. Exactly. > Yes, it was > blacklisted, yet it was loaded. Why? Because I did not built initrd. I > did, novueau got removed from it, the blaklist was inserted in the > archive image, rebooted, and now, yes, I got nvidia working. Not before. > > Do you understand that? Of course I understand this! But what I am trying to get across is that *I* -- for whatever reason -- have never had to re build initrd for the nVidia driver to work. Maybe I am just a lucky guy or have the magic touch or there is an angel sitting on my shoulder working things for me but *I* have never had to run mkinitrd to create a new intird. Do you understand that? > > The next time I will only need to compile the driver. BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.5.0-2 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
Op woensdag 16 maart 2016 00:29:13 CET schreef Basil Chupin:
On 15/03/16 23:22, Knurpht - Gertjan Lettink wrote:
Op dinsdag 15 maart 2016 22:30:43 CET schreef Basil Chupin:
On 15/03/16 20:49, Carlos E. R. wrote:
On 2016-03-15 05:28, Basil Chupin wrote:
On 15/03/16 00:44, Carlos E. R. wrote:
On 2016-03-14 14:28, Basil Chupin wrote: >>> I would experiment with the driver, if I knew how to revert without >>> much pain to nouveau, i.e a working system. >> >> When you want the proprietary driver, blacklist 'nouveau', when you >> want >> nouveau, un-blacklist it. Rebuild initrd. > > Strange -- I have never done this (rebuilding initrd). I just > compile/install the driver and reboot.
If you don't, the initrds still contains the nouveau module, it gets loaded, and nvidia module refuses to load. And viceversa.
You have to compile the nVidia driver to work with the kernel you are using and when you go to compile it with the nouveau driver installed you get an error message and the nVidia driver will NOT compile until the nouveau driver is removed.
Yes, I did that, nvidia driver loaded fine, tested startx, I rebooted, and it failed to load. Nouveau was loaded again. I checked, run mkinird, rebooted, and it was ok, nividia.
I use the kernel in the .../Kernel:/stable/standard repository and have to compile the driver every time the kernel is upgraded -- sometimes on a daily basis. I don't run mkinitrd and I don't have any problems with compiling the driver.
Because you were not running nouveau the previous time, thus no need to remove it again.
It is the first time, when you do the switch, that you have to do all those things.
Jesus, Carlos, let's look at what has been written and then make comments shall we?
Someone wrote:
"When you want the proprietary driver, blacklist 'nouveau', when you want nouveau, un-blacklist it. Rebuild initrd."
To which I replied:
"Strange -- I have never done this (rebuilding initrd). I just compile/install the driver and reboot."
Now, is there anything clearer and articulate than what I wrote in the above paragraph: "I just compile/install the driver and reboot"?
"But", you say, "what about the nouveau driver?" to which I already said that the nVidia driver will not compile until the bloody thing is removed!
So what is left? "I just compile/install the driver and reboot."
Something still missing in the translation? Then please let me know.
BC
1. The nvidia driver compile doesn't care whether nouveau or whatever is loaded.
Of course I do not have the knowledge or the expertise which you seem to have, or at least express that you have, but the nVidia compiler DOES care if the nouveau driver is installed because it just won't continue with the compile until the nouveau is disabled.
You're barking up the wrong tree. There is no such thing as the nVidia compiler. An installer, yes, which unpacks sources and lets the already installed tools compile these sources against the ( running ) kernel. This all hidden behind an ncurses interface.
Are you saying all this from experience or from some theoretical concept?
The installer does, but this can be overruled with options, like the
--no-nouveau-check, --no-x-check. 2. If nouveau is loaded per initrd, one needs to rebuild the initrd after blacklisting nouveau.
READ MY LIPS!
I have NEVER had to rebuild initrd after compiling the nVidia driver.
YES, as I said, FOR CHRISSAKE, the nouveau driver HAS to be disabled before the nVidia driver will compile
Packagers of various nvidia driver packages think differently. They create packages that can be installed from a running desktop and do nothing but pull in the NVIDIA....run, run the installer with a variety of options hence triggering the local compilation of the kernel module(s), i.e. the driver.
From a desktop using the nouveau driver. Which, by the same package gets blacklisted, but can't be unloaded yet since X is using it to display the desktop. Some of these might even trigger a rebuild of the initrd ( can be done from a package ) to stop nouveau from already being loaded through the initrd. The .run installer will not.
but after that I have NEVER HAD TO REBUILD INITRD.
Like said, that may have been triggered from a package you used.
HAVE I MADE THIS CLEAR OR NOT?!
Whether it is depends on previously taken actions where
reconfiguring / rebuilding initrd was involved.
Read what I wrote above.
Please read what I wrote -without "shouting"- too.
BC
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/03/16 02:56, Knurpht - Gertjan Lettink wrote: > Op woensdag 16 maart 2016 00:29:13 CET schreef Basil Chupin: >> On 15/03/16 23:22, Knurpht - Gertjan Lettink wrote: >>> Op dinsdag 15 maart 2016 22:30:43 CET schreef Basil Chupin: >>>> On 15/03/16 20:49, Carlos E. R. wrote: >>>>> On 2016-03-15 05:28, Basil Chupin wrote: >>>>>> On 15/03/16 00:44, Carlos E. R. wrote: >>>>>>> On 2016-03-14 14:28, Basil Chupin wrote: >>>>>>>>>> I would experiment with the driver, if I knew how to revert without >>>>>>>>>> much pain to nouveau, i.e a working system. >>>>>>>>> When you want the proprietary driver, blacklist 'nouveau', when you >>>>>>>>> want >>>>>>>>> nouveau, un-blacklist it. Rebuild initrd. >>>>>>>> Strange -- I have never done this (rebuilding initrd). I just >>>>>>>> compile/install the driver and reboot. >>>>>>> If you don't, the initrds still contains the nouveau module, it gets >>>>>>> loaded, and nvidia module refuses to load. And viceversa. >>>>>> You have to compile the nVidia driver to work with the kernel you are >>>>>> using and when you go to compile it with the nouveau driver installed >>>>>> you get an error message and the nVidia driver will NOT compile until >>>>>> the nouveau driver is removed. >>>>> Yes, I did that, nvidia driver loaded fine, tested startx, I rebooted, >>>>> and it failed to load. Nouveau was loaded again. I checked, run mkinird, >>>>> rebooted, and it was ok, nividia. >>>>> >>>>>> I use the kernel in the .../Kernel:/stable/standard repository and have >>>>>> to compile the driver every time the kernel is upgraded -- sometimes on >>>>>> a daily basis. I don't run mkinitrd and I don't have any problems with >>>>>> compiling the driver. >>>>> Because you were not running nouveau the previous time, thus no need to >>>>> remove it again. >>>>> >>>>> It is the first time, when you do the switch, that you have to do all >>>>> those things. >>>> Jesus, Carlos, let's look at what has been written and then make >>>> comments shall we? >>>> >>>> Someone wrote: >>>> >>>> "When you want the proprietary driver, blacklist 'nouveau', when you >>>> want nouveau, un-blacklist it. Rebuild initrd." >>>> >>>> To which I replied: >>>> >>>> "Strange -- I have never done this (rebuilding initrd). I just >>>> compile/install the driver and reboot." >>>> >>>> Now, is there anything clearer and articulate than what I wrote in the >>>> above paragraph: "I just compile/install the driver and reboot"? >>>> >>>> "But", you say, "what about the nouveau driver?" to which I already said >>>> that the nVidia driver will not compile until the bloody thing is >>>> removed! >>>> >>>> So what is left? "I just compile/install the driver and reboot." >>>> >>>> Something still missing in the translation? Then please let me know. >>>> >>>> >>>> BC >>> 1. The nvidia driver compile doesn't care whether nouveau or whatever is >>> loaded. >> Of course I do not have the knowledge or the expertise which you seem to >> have, or at least express that you have, but the nVidia compiler DOES >> care if the nouveau driver is installed because it just won't continue >> with the compile until the nouveau is disabled. > You're barking up the wrong tree. There is no such thing as the nVidia > compiler. An installer, yes, which unpacks sources and lets the already > installed tools compile these sources against the ( running ) kernel. This all > hidden behind an ncurses interface. > >> Are you saying all this from experience or from some theoretical concept? >> >>> The installer does, but this can be overruled with options, like the >>> >>> --no-nouveau-check, --no-x-check. >>> 2. If nouveau is loaded per initrd, one needs to rebuild the initrd after >>> blacklisting nouveau. >> READ MY LIPS! >> >>> I have NEVER had to rebuild initrd after compiling the nVidia driver. > > >> YES, as I said, FOR CHRISSAKE, the nouveau driver HAS to be disabled >> before the nVidia driver will compile > Packagers of various nvidia driver packages think differently. They create > packages that can be installed from a running desktop and do nothing but pull > in the NVIDIA....run, run the installer with a variety of options hence > triggering the local compilation of the kernel module(s), i.e. the driver. > >From a desktop using the nouveau driver. Which, by the same package gets > blacklisted, but can't be unloaded yet since X is using it to display the > desktop. Some of these might even trigger a rebuild of the initrd ( can be > done from a package ) to stop nouveau from already being loaded through the > initrd. The .run installer will not. Oh, my god..... Look, just for your edification, afer a new kernel in installed (such as the one this morning, kernel 4.5.0-2) I install/compile the nVidia driver by executing such as the following on a command line as root in level #3 in the konsole: cd /data/Nvidia-361-28 ; sh ./NVIDIA-Linux-x86_64-361.28.run -a Is the above the *.run installer/compiler or not which you state will not do what I say it does? > but after that I have NEVER HAD TO > REBUILD INITRD. > Like said, that may have been triggered from a package you used. > >> HAVE I MADE THIS CLEAR OR NOT?! >> >>> Whether it is depends on previously taken actions where >>> >>> reconfiguring / rebuilding initrd was involved. >> Read what I wrote above. > Please read what I wrote -without "shouting"- too. I have read what you wrote -- but have you read what I wrote? > > >> >> >> BC BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.5.0-2 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 2016-03-14 12:33, oszko@chem.u-szeged.hu wrote:
BTW the final step of installation is to run mkinitrrd, but it hangs for me.
Hangs or takes VERY long? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Per Jessen wrote:
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist. I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says? I have such warnings too every single time. You probably see the warnings, if you choose to install the 32Bit libraries. I think, the warnings are harmless.
The links for NVidia driver 361.28 look like these (in /usr/lib): lrwxrwxrwx 1 root root 15 11. Mär 14:47 libGL.so.1 -> libGL.so.361.28 lrwxrwxrwx 1 root root 23 11. Mär 14:47 libGLX_nvidia.so.0 -> libGLX_nvidia.so.361.28 [...] Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14/03/16 20:17, Per Jessen wrote:
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist. I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
Yes, those are the 3 messages one gets when installing the latest nVidia drivers. Simply ignore them and press "Continue with the installation". BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.4.5-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
2016-03-14 14:24 keltezéssel, Basil Chupin írta:
On 14/03/16 20:17, Per Jessen wrote:
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist. I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
Yes, those are the 3 messages one gets when installing the latest nVidia drivers. Simply ignore them and press "Continue with the installation".
BC
In the meantime I also realized that the 3 messages refer to installing 32 stuff. So I gave it another nad again, I badly failed. Perhaps I did something wrong, but have no idea what. Here is asystem, I can reach CLI with CTR-Alt-F1 and that is all, I mean neither nouveau, nor nvidia loads. Maybe yet another Leap install again? I tried Ubunti 15.10 but even the trial does not start. Debian and Mint have older kernels. So I am bit disappointed now
Op dinsdag 15 maart 2016 17:22:57 CET schreef Oszkó Albert:
2016-03-14 14:24 keltezéssel, Basil Chupin írta:
On 14/03/16 20:17, Per Jessen wrote:
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist.
I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
Yes, those are the 3 messages one gets when installing the latest nVidia drivers. Simply ignore them and press "Continue with the installation".
BC
In the meantime I also realized that the 3 messages refer to installing 32 stuff. So I gave it another nad again, I badly failed. Perhaps I did something wrong, but have no idea what. Here is asystem, I can reach CLI with CTR-Alt-F1 and that is all, I mean neither nouveau, nor nvidia loads. Maybe yet another Leap install again? I tried Ubunti 15.10 but even the trial does not start. Debian and Mint have older kernels. So I am bit disappointed now
Nouveau may still be blacklisted. Do sudo rm /etc/modprobe.d/50-blacklist-nouveau.conf sudo dracut -f That should bring the nouveau driver back in play. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2016-03-15 20:43 keltezéssel, Knurpht - Gertjan Lettink írta:
Op dinsdag 15 maart 2016 17:22:57 CET schreef Oszkó Albert:
2016-03-14 14:24 keltezéssel, Basil Chupin írta:
On 14/03/16 20:17, Per Jessen wrote:
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist. I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says? Yes, those are the 3 messages one gets when installing the latest nVidia drivers. Simply ignore them and press "Continue with the installation".
BC In the meantime I also realized that the 3 messages refer to installing 32 stuff. So I gave it another nad again, I badly failed. Perhaps I did something wrong, but have no idea what. Here is asystem, I can reach CLI with CTR-Alt-F1 and that is all, I mean neither nouveau, nor nvidia loads. Maybe yet another Leap install again? I tried Ubunti 15.10 but even the trial does not start. Debian and Mint have older kernels. So I am bit disappointed now Nouveau may still be blacklisted. Do sudo rm /etc/modprobe.d/50-blacklist-nouveau.conf sudo dracut -f That should bring the nouveau driver back in play.
Thanks, I did not know of this dracut command. So finally again installed Leap from USB stick. Before that I read and modified the blacklist list and interestingly, I did not find nouveau item. Insteead I found nividiafb.
Op woensdag 16 maart 2016 09:43:26 CET schreef Albert, Oszkó:
2016-03-15 20:43 keltezéssel, Knurpht - Gertjan Lettink írta:
Op dinsdag 15 maart 2016 17:22:57 CET schreef Oszkó Albert:
2016-03-14 14:24 keltezéssel, Basil Chupin írta:
On 14/03/16 20:17, Per Jessen wrote:
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist.
I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
Yes, those are the 3 messages one gets when installing the latest nVidia drivers. Simply ignore them and press "Continue with the installation".
BC
In the meantime I also realized that the 3 messages refer to installing 32 stuff. So I gave it another nad again, I badly failed. Perhaps I did something wrong, but have no idea what. Here is asystem, I can reach CLI with CTR-Alt-F1 and that is all, I mean neither nouveau, nor nvidia loads. Maybe yet another Leap install again? I tried Ubunti 15.10 but even the trial does not start. Debian and Mint have older kernels. So I am bit disappointed now
Nouveau may still be blacklisted. Do sudo rm /etc/modprobe.d/50-blacklist-nouveau.conf sudo dracut -f That should bring the nouveau driver back in play.
Thanks, I did not know of this dracut command. So finally again installed Leap from USB stick. Before that I read and modified the blacklist list and interestingly, I did not find nouveau item. Insteead I found nividiafb. That's correct. Nouveau is being used by default, so it shouldn't be blacklisted. And it won't be through 50-blacklist.conf, when installing the nvidia packages, but have it's own 50-blacklist-nouveau.conf
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/03/16 03:22, Oszkó Albert wrote:
2016-03-14 14:24 keltezéssel, Basil Chupin írta:
On 14/03/16 20:17, Per Jessen wrote:
Oszkc3b3 Albert wrote:
Opensuse's SDB says Nvidia linux drivers work "flawlessly" with Leap and installation is "trivial". Well, it is not. First one has to install gcc, kernel-sources and kernel-devel, but it is not a big deal. But at the end of installation Nvidia tells you that it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist. And it is right. I tried to delete them, but it still insists that those files exist. I went through the exercise on my Leap desktop machine, I don't recall any such issues. Maybe because I needed an older nvidia driver.
Your description "it could not symlink to /usr/lib/libGL.so.1 and two other files because they exist." doesn't sound correct - are you sure that's what it says?
Yes, those are the 3 messages one gets when installing the latest nVidia drivers. Simply ignore them and press "Continue with the installation".
BC
In the meantime I also realized that the 3 messages refer to installing 32 stuff.
Umm, are you sure -- re the 32-bit stuff? There is a question asking if you want 32-bit module to be compiled but that's all. The 3 "Warning" msgs are about having the symlinks to the nvidia drivers already being present and these are the ones which I ignore and go ahead and complete the installation.
So I gave it another nad again, I badly failed. Perhaps I did something wrong, but have no idea what. Here is asystem, I can reach CLI with CTR-Alt-F1 and that is all, I mean neither nouveau, nor nvidia loads. Maybe yet another Leap install again? I tried Ubunti 15.10 but even the trial does not start. Debian and Mint have older kernels. So I am bit disappointed now
BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.5.0-2 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
participants (8)
-
Albert, Oszkó -
Basil Chupin -
Bjoern Voigt -
Carlos E. R. -
Knurpht - Gertjan Lettink -
oszko＠chem.u-szeged.hu
-
Oszkó Albert
-
Per Jessen