Description of problem: I downloaded the sta2 DVD iso and burned it to a USB memory drive. That part went just fine. Booting the installation I chose to install Plasma, MATE, GNOME, Cinnamon and the only setting I touched in the Summary was the Screen resolution and the Firewall to open the port to SSH. After that I rebooted to a working SDDM login session and I logged into MATE. That worked fine. After that I added the medias (except for Testing and Backports) for Cauldron and ran the update process in the terminal and no fail that I could see. As I rebooted the computer I noticed that the latest kernel 4.9.17 couldn't boot to SDDM for some odd reason. I recall that I could try to boot the kernel into Recovery mode and then I decided to reboot into Recovery mode and run systemctl default and that way I could boot to SDDM login session.
Version-Release number of selected component (if applicable): 4.9.17
How reproducible: Every boot.
Steps to Reproduce:
1. Boot the installation of the sta2 DVD iso.
2. Install GNOME, Plasma, Cinnamon, MATE as DE's.
3. Reboot and the first boot will work just fine.
4. Update using all the medias except Testing and Backports.
6. Voila! The kernel 4.9.17 won't boot unless you boot it into recovery mode and run systemctl default as root.
The computer just seems to freeze when you boot normally. I waited at least 45 minutes to see if the kernel was unusually slow, but nothing happened.
What log files do you need?
I tested the previous kernels and I got the same result.
(In reply to Kristoffer GrundstrÃ¶m from comment #2)
> What log files do you need?
So the only boot that worked fine, was the first one, and the second one went wrong?
Please attach good.txt that is the result of running, as root:
journalctl -ab1 > good.txt
and attach bad.txt that is the result of running as root:
journalctl -ab2 > bad.txt
(or attach a more recent "bad one")
New RPM package request =>
I don't know why, but I can boot normally again if I remove the noiswmd and nomodeset (I added the nomodeset part to the kernel boot command line to solve a previous graphics problem as I wasn't sure if it has been resolved yet) and modprobe.blacklist=nouveau .
Weird, but true.
So, who can add that workaround to the next kernel?