<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - KDE hangs and system freezes while journalctl lists complains of kernel (nouveau). Nvidia graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=92962#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - KDE hangs and system freezes while journalctl lists complains of kernel (nouveau). Nvidia graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=92962">bug 92962</a> from <a class="email" href="mailto:pierre.morrow@free.fr" title="Pierre Moreau <pierre.morrow@free.fr>"> Pierre Moreau</a> <pre>(In reply to stakanov from <a href="show_bug.cgi?id=92962#c3">comment #3</a>) > A bit embarrassing but I do not really know what to ask there. > > I think I know how to blacklist nouveau: > > # echo "blacklist nouveau" >> /etc/modprobe.d/50-blacklist.conf && mkinitrd > && reboot That should do it. (In reply to stakanov from <a href="show_bug.cgi?id=92962#c3">comment #3</a>) > Then, if I do understand rightly: > > cat /dev/kmsg > kmsgresult.txt > > Then > > modprobe nouveau > > (from the CLI) and then again? > > cat /dev/kmsg > kmsgresult2.txt cat /dev/kmsg > kmsgresult.txt& modprobe nouveau startx would be one way to go, as `cat` will continue its job until it get killed. And then when you reboot, you can access the file (which hopefully didn't end up corrupted). Maybe `journalctl -k -b -1` will contain all the information as well (given that the previous boot, was one that froze)?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>