Comment # 56 on bug 935993 from Walther Pelser

Now a normal comment

My Os was broken. So I had to install a new tumbleweed-OS. As expected it is
booting normally. Because of problems with my DVB-USB-Stick after hibernation I
have to use again a self-compiled kernel with built-in module and built-in
firmware. Which dracut-loglevel should I use, to get all changes in dracut. if
there is there are changes during installation of a new kernel, while my own
kernel is booted.
It is obvious for me that dracut works fine, if a new own kernel is installed
from a booted SUSE-Kernel. But the problems came up, when a SUSE-kernel was
installed from a booted own kernel. So the SUSE-specifications in systemd and
dracut may cause the problems. Dracut seems to have problems with them, when
installing a new kernel, when the system was booted by my own kernel. So there
should be some visible changes in the dracut-logs, if I have to to do so.

The requested logs from comment 54 are impossible right now, but maybe seen
sometime later on.

I am open for another kind of approach to this problem, if You have a better
one.