[opensuse-factory] Plasma 5 incompatible with *-nvidiaG04-* packages (13.2)
Plasma 5 incompatible..!!! with 13.2 packages: x11-video-nvidiaG04, nvidia-glG04, nvidia-computeG04, nvidia-gfxG04-kmp-desktop, nvidia-uvm-gfxG04-kmp-desktop for Leap/tumbleweed we need updated packages or alternative packages..!! see bugreport #360376 https://bugs.kde.org/show_bug.cgi?id=360376 Bug #353520 is a Fedora bug so has nothing to do with Opensuse.... other (opensuse) users with same problem, please add logfiles/backtraces thank you... André -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
update: packages work great wirh Leap :) why not with TW, not sure... -- View this message in context: http://opensuse.14.x6.nabble.com/Plasma-5-incompatible-with-nvidiaG04-packag... Sent from the opensuse-factory mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On samedi, 19 mars 2016 14.17:09 h CET André Verwijs wrote:
update: packages work great wirh Leap :) why not with TW, not sure...
once you have updated TW to last snapshot, did you reinstall nvidia full stack ? There was a Mesa update (11.1.2-134.1) which is also one of the trouble with binary stuff -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
André Verwijs wrote:
Plasma 5 incompatible..!!! with 13.2 packages:
x11-video-nvidiaG04, nvidia-glG04, nvidia-computeG04, nvidia-gfxG04-kmp-desktop, nvidia-uvm-gfxG04-kmp-desktop
for Leap/tumbleweed we need updated packages or alternative packages..!!
see bugreport #360376 https://bugs.kde.org/show_bug.cgi?id=360376
Bug #353520 is a Fedora bug so has nothing to do with Opensuse....
other (opensuse) users with same problem, please add logfiles/backtraces The NVidia RPM packages are probably buggy for Leap/Tumbleweed (I did not tested them).
But I can recommend the "hard way". It's time consuming to manually shutdown X11, recompile NVidia driver etc. after each bigger Tumbleweed (or Leap X11/Mesa) update, but it works: https://en.opensuse.org/SDB:NVIDIA_the_hard_way#openSUSE_Tumbleweed_and_Leap Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op maandag 21 maart 2016 14:44:59 CET schreef Bjoern Voigt:
André Verwijs wrote:
Plasma 5 incompatible..!!! with 13.2 packages:
x11-video-nvidiaG04, nvidia-glG04, nvidia-computeG04, nvidia-gfxG04-kmp-desktop, nvidia-uvm-gfxG04-kmp-desktop
for Leap/tumbleweed we need updated packages or alternative packages..!!
see bugreport #360376 https://bugs.kde.org/show_bug.cgi?id=360376
Bug #353520 is a Fedora bug so has nothing to do with Opensuse....
other (opensuse) users with same problem, please add logfiles/backtraces
The NVidia RPM packages are probably buggy for Leap/Tumbleweed (I did not tested them).
But I can recommend the "hard way". It's time consuming to manually shutdown X11, recompile NVidia driver etc. after each bigger Tumbleweed (or Leap X11/Mesa) update, but it works:
You can make this easier by using options provided by the installer blob, like --no-x-check ( no need for the old "init 3" ) --no-nouveau-check (installer will run and do the job even though nouveau is loaded) --dkms ( dkms needs to be installed, but then a rebuild of the driver code is triggered )
https://en.opensuse.org/SDB:NVIDIA_the_hard_way#openSUSE_Tumbleweed_and_Leap
Greetings, Björn
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
thanks for relpy... installation of nvidia drivers is not really a problem, but if there's a update for Grub or graphics packages and/or x server, plasma 5 crashes on next boot. it would be safer to don't touch current configuration (with nvidia driver) of implement it with updates... André on 21-03-16 at 15:08 Knurpht - Gertjan Lettink wrote :
The NVidia RPM packages are probably buggy for Leap/Tumbleweed (I did not tested them).
But I can recommend the "hard way". It's time consuming to manually shutdown X11, recompile NVidia driver etc. after each bigger Tumbleweed (or Leap X11/Mesa) update, but it works:
You can make this easier by using options provided by the installer blob, like --no-x-check ( no need for the old "init 3" ) --no-nouveau-check (installer will run and do the job even though nouveau is loaded) --dkms ( dkms needs to be installed, but then a rebuild of the driver code is triggered )
https://en.opensuse.org/SDB:NVIDIA_the_hard_way#openSUSE_Tumbleweed_and_Leap
Greetings, Björn
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op maandag 21 maart 2016 20:38:50 CET schreef André Verwijs:
thanks for relpy...
installation of nvidia drivers is not really a problem, but if there's a update for Grub or graphics packages and/or x server, plasma 5 crashes on next boot. it would be safer to don't touch current configuration (with nvidia driver) of implement it with updates...
It doesn't. Not on a couple of 13.2 machines with NVIDIA's I administer. Since Plasma5 is not 13.2's KDE, I'm curious about your repos. Next to that, what's the NVIDIA model ? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Knurpht - Gertjan Lettink wrote:
You can make this easier by using options provided by the installer blob, like --no-x-check ( no need for the old "init 3" ) --no-nouveau-check (installer will run and do the job even though nouveau is loaded) --dkms ( dkms needs to be installed, but then a rebuild of the driver code is triggered ) Thanks. I already tried such options in the past.
But unfortunately they do not seem to work: In KDE Plasma desktop (of course with loaded NVidia driver) in openSUSE Tumbleweed (20160321): myuser@mybox:~> sudo -i mybox:~ # uname -a Linux mybox 4.5.0-3.g8ec3d36-default #1 SMP PREEMPT Fri Mar 18 14:49:10 UTC 2016 (8ec3d36) x86_64 x86_64 x86_64 GNU/Linux mybox:~ # cd /usr/src mybox:/usr/src # sh NVIDIA-Linux-x86_64-364.12.run --no-x-check --no-nouveau-check --dkms ERROR: An NVIDIA kernel module 'nvidia-drm' appears to already be loaded in your kernel. This may be because it is in use (for example, by an X server, a CUDA program, or the NVIDIA Persistence Daemon), but this may also happen if your kernel was configured without support for module unloading. Please be sure to exit any programs that may be using the GPU(s) before attempting to upgrade your driver. If no GPU-based programs are running, you know that your kernel supports module unloading, and you still receive this message, then an error may have occured that has corrupted an NVIDIA kernel module's usage count, for which the simplest remedy is to reboot your computer. OK If I add --skip-module-unload the same error message appears. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Bjoern Voigt <bjoernv@arcor.de> [03-22-16 14:49]: [...]
mybox:/usr/src # sh NVIDIA-Linux-x86_64-364.12.run --no-x-check --no-nouveau-check --dkms
ERROR: An NVIDIA kernel module 'nvidia-drm' appears to already be loaded in your kernel. This may be because
it is in use (for example, by an X server, a CUDA program, or the NVIDIA Persistence Daemon), but this
may also happen if your kernel was configured without support for module unloading. Please be sure to
exit any programs that may be using the GPU(s) before attempting to upgrade your driver. If no
GPU-based programs are running, you know that your kernel supports module unloading, and you still
receive this message, then an error may have occured that has corrupted an NVIDIA kernel module's usage
count, for which the simplest remedy is to reboot your computer.
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) ps:lines will wrap as you client doesn't wrap a <= 78 chars. -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
ps:lines will wrap as you client doesn't wrap a <= 78 chars. 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.
What is the preferred line wrap option for this mailing list? Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* 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
ps:lines will wrap as you client doesn't wrap a <= 78 chars. 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.
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. -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* 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
ps:lines will wrap as you client doesn't wrap a <= 78 chars. 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.
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! -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
participants (6)
-
André Verwijs -
André Verwijs -
Bjoern Voigt -
Bruno Friedmann -
Knurpht - Gertjan Lettink -
Patrick Shanahan