strange problem, I have no since several month nvidia optimus running on my notebook, and it basically works,
I use Davnici Resolve to render videos from time to time, just hobby
but every now and than there is a update, that updates the kernel and the bumblebee packages, and than Davinc stops working due to some openCL problem
Than I have to wait for some time, until the next bumblebee update, like I had today, and than it works again,
This is now since 8 month so, every now and than, for one or 2 weeks I can not use the app.
I assume that generaly everything is OK, but the way how I make the updates, or the order, influence if Davinci breaks or not
But I simply run zypper update from the command line,
how can I find out what the problem is, and how to install the updates so that I get rid of these non working states, since they they are somehow stressful,
What you describe seems related to the new kernel not finding a matching module or driver until the next update.
Maybe a matching bumblebee is only released a few days or weeks after a new kernel is released; if so, you may boot the old kernel until a matching bumblebee is released.
Or, especially if you are using the proprietary driver with dkms, the new modules are only built upon the first boot of the new kernel and maybe the initrd is not rebuilt until the next update.
If this is the problem, when running the new kernel issue in a terminal:
dracut --hostonly --force
or if you prefer:
sudo mkinitrd
to rebuild the initrd and that might fix your problem.
From what you wrote I don’t think there is something wrong in the way you update your system.
will. if it break again, try it with a mkinitrd, or the dracut version, after a reboot with the new setup , maybe this is the thing
my kernel is 4.12.14-lp150.12.61-default, until next week where we have some tech talks I will edit and render I will not do any updates anymore
but just got an bbswitch bbswitch-kmp-default update, what I installed, will reboot now and hope everything still works,
but usually these are not the problems that break the video editor
I do not read the packages so closely, but meanwhile I see the pattern when I have the list of packages to update on the terminal,
when I have more than 2 weeks nothing to do with vides, I just install them because until now, over the last monthns since I am on 15.0 , it always was fixed through a following update
is there a zypper history ? so I can get the package combinations that break davinic, and the follow up updates that fix it?
maybe this could help to tell me whats actually going on
but a bit hard to read/parse, to simply get a list of packages per update from the last N update runs
I wonder if such functionality not already exists some where, zypper history or so …
There’s a “history” menu item on the “Extras” menu in Yast Software Management. It really just displays the history file, but perhaps it’s presented in a more readable format.
I am pretty surprised, positively, by the fact that I disabled the bumblebee repo, run the update to Leap 15.1, and after the reboot nividia and optimus are working
wow
it seems I can make it like this, install bumblebee, than when it is working disable it, and from time to time make an update
but I still would like to understand all they whys included in this
