Marc Chamberlin composed on 2017-07-18 16:30 (UTC-0700):
Felix Miata wrote: ... AFAIK from my Googling, plasma5 is part of the sddm display manager and SDDM seems to be the setting recommended on
All my Plasma 5 installations have either KDM or KDM3, neither lightdm nor sddm anywhere. For the 42.3 I did for my neighbor done Saturday night it's KDM3.
most of the websites I visited, to use as the display manager. There isn't any settings under either the DISPLAYMANGER or DEFAULT_WM that allow me to select "plasma5". Ditto for "kde5", under DEFAULT_WM I can only select either KDE or KDE4 if I want to use a KDE window manager. I tried both, and on a lark I also typed in KDE5 for the setting, but no joy on any of these... Please advise me on exactly what I should set> these two parameters to and/or if I am misunderstanding these settings.
Edit /etc/sysconfig/displaymanager and /etc/sysconfig/windowmanager directly. They are supposedly self-documenting, although the displaymanager I'm looking at ATM on TW, with kdm-4.11.22, for DISPLAYMANAGER= lists neither lightdm nor sddm as options; mine has "kdm" set. For Plasma 5 to be default set "kde-plasma" as DEFAULT_WM= in windowmanager.
...bigbang:/home/marc # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.74-18.20-default root=UUID=ebf32d3d-bbdd-4d70-99e5-c15735bcd81d ro resume=/dev/disk/by-uuid/befcf2d3-8c2c-484b-a196-55be5744a24f splash=silent quiet showopts
Hmmm, then your problem probably nothing to do with modesetting. You could try the other Xorg driver, but I do think '(EE) /dev/dri/card0' would apply to either. Xorg.0.log tells you which driver is in use, the large multiplicity of lines with INTEL(0) say intel driver, while MODESET(0) say integral modesetting driver in use. As long as mesa and kernel modesetting are not broken, Xorg will use intel if xf86-video-intel is installed, the integral driver if it is not. Probably we need to see more of Xorg.0.log....
if not see his entire Xorg.0.log, dmesg and journal to find more clues. It could be nomodeset found its way onto the cmdline, which blocks use of any Xorg driver supported with Intel gfxchips.
Oh wow! I think you are a gluten for punishment! LOL I am not sure how to send you, or the list that much info... Let me know what is best or how to trim it down....
A brief start would be journalctl | grep fail and dmesg ! grep fail For voluminous things like Xorg.0.log, journal or full dmesg, share via pastebin, either install (if it isn't already) and use the susepaste command, or use http://susepaste.org/ or http://pastebin.com/ or one of the many others, or the web space provided by your ISP.
Is the problem the same booting the previous (4.4.73) kernel? Yeah, I tried booting with the previous kernel to see if the desktop would come up, and it didn't... So something that is common to both is now broken...
:-( Is there also an older kernel than 4.4.73?
Did the just completed reinstallation and/or updates rebuild both/all initrds?
And you just went above my pay grade, I dunno how to answer this.....
Are the timestamps on /boot/initrd* all fresh? If there is one that is not, can you boot from its kernel and not have the black screen problem? What if anything does /var/lib/systemd/coredump/ contain? Is everything that is there timestamped since you did your updating? Does 'startx -- :1' from vtty login, either normally or as root, avoid the black screen? (I'm guessing not.) What about 'WINDOWMANAGER=/usr/bin/icewm startx -- :1'? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org