Am Sonntag, 29. März 2015, 17:33:32 schrieb Cristian Rodríguez:
On Sun, Mar 29, 2015 at 5:27 PM, Emil Stephan <Emil.Stephan@t-online.de> wrote:
Am Sonntag, 29. März 2015, 17:01:40 schrieb Cristian Rodríguez:
On Sun, Mar 29, 2015 at 4:55 PM, Emil Stephan <Emil.Stephan@t-online.de>
wrote:
Do You get similar messages?
Yes, but this messages are informative/harmless and got nothing to do with the problem in question.
Hello Cristian,
even, if "systemctl isolate <new-target>" does not change anything and the system stays in the current target.
Works for me.. does it happen with both systemd 210 and 219 ?
Hard to say. I got the update from 210 to 219 today at 13:27. I have used runlevel resp. target changes to install the nvidia drivers to create a mmio trace. And this i have done yesterday too, since i tried several versions of the nvidia drivers. And i think, i had these behaviour yesterday too, but this was not my first level concern in that case. I have just checked, whether i can go back to 210. I have it on the DVD from the eleventh of march. I'll give it a try, and report later. Regards Emil
Regards, Emil
P.S.: You do not like runlevels, do You?
There are no runlevels in the sysvinit-sense when using systemd, there is a minimal compatibility that provides at least the illusion of runlevels.
-- Registered Linux User since 19940320 ---------------------------------------------------------- Emil Stephan, Albersloher Weg 571A, 48167 Münster, Germany Accelerate Windows: 9.80665 m/sec^2 would be adequate -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org