Patrick Shanahan wrote:
* Bjoern Voigt <bjoernv@arcor.de> [03-22-16 15:53]:
Patrick Shanahan wrote:
means "X" is running and nvidia will not install with active X.
systemctl isolate multi-user (or init 3) then sh NV....run -asq systemctl isolate graphical (or init 5) Of course, but Knurpht - Gertjan Lettink recommended the NVidia installer options for update/re-installation in desktop. And I personally would prefer the NVidia driver installation/update after each Tumbleweed update within KDE desktop. The options --no-x-check and --skip-module-unload are made for this, but they do not seem to work like expected.
The following common situation is relatively time consuming and uncomfortable
* Tumbleweed update o the update partially overwrites the NVidia libraries; therefore the desktop will crash soon without user actions o Kernel update o a full NVidia driver re-installation is necessary * NVidia driver can't be updated/re-installed in desktop (see above) * NVidia driver can't be updated/re-installed in text mode, because kernel-source does not match the running kernel version; options like --kernel-source-path=/usr/src/linux --kernel-install-path=/lib/modules/new-kernel-version are not compatible with DKMS * necessary reboot * the display manager starts in a low resolution (because of the missing NVidia module) * display manager must be stopped * manual NVidia update/re-installation * display manager must be started * have fun with a working desktop Tw update if mesa changes, drop to runlevel 3 and "sh NV....run -aqs", change to runlevel 5.
no reboot necessary, *unless* new kernel, then reboot is necessary anyway. reboot to runlevel 3, "sh NV....run -aqs", chg to runlevel 5
You make it much more difficult than it is!
You might also read the README on nvidia site and included within the NV...run file, hint: sh ./NV....run -x No, we do nearly the same. Instead of changing the runlevel I prefer "rcxdm stop/start". And instead of the automatic silent options "-aqs" I use the cursor and return keys to answer the NVidia installer questions. ;-)
ps:lines will wrap as you client doesn't wrap a <= 78 chars. This is not part of the "Mailing_list_netiquette". I hate URLs which with automatic line breaks. I hate broken patch files. And I prefer automatic line breaks on the reader's side. This are arguments for disabling automatic line breaks.
But I know, that every mailer behaves different. Many readers do not work with format=flowed correctly. And so line wrapping <= 78 and disabling format=flowed as sent format may be a compromise. These options work too for Mutt users with an 80 characters display. ;-) I change the options for next mail.
Yes, I disabled automatic line wrapping in my Seamonkey mailer. The NVidia error message was up to 110 characters long. Automatic line wrapping after c < 110 characters would result in ugly result too. So spend a moment of *your* time to reformat instead of imposing on those you are asking for help. Your few moments would be much less than each trying to read the *mess*, and perhaps result in more and better responses. OK.
What is the preferred line wrap option for this mailing list? What do you suppose, "<= 78 chars". Or you *could* refer to opensuse's published netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette
Much information may be learned by being a little curious.
ps: Please do NOT cc: me, I read the list or would not have seen your post and have NO NEED for duplicate copies of email, unless I choose to. Reading the mail list netiquette is really necessary! Yes, it's a personal preference too. I prefer to be Cc'ed.
Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org