17 Mar
2016
17 Mar
'16
12:56
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