In your bootline, the last charackter is an 5 with a blank charakter to the last before.
Try ro delete this 2 charackters.
Runlevel is managed by systemd, so see, what is the default:
For me, it is garphical.target (Runlevel 5):
That is good, you have not blacklisted nouveau......

Thats my fault, better was:
That shows all installed stuff with nvidia or nouveau in the name.
But there should be no! y/n question at the end.
If you get one, please post it here.

Also post your Repos:
Make a screenshot and post it on https://pix.toile-libre.org

--> sddm.service - Simple Desktop Dispaly Manager
--> loaded: loaded ( /usr/lib/systemd/system/sddm.service; disabled ; vendor preset; disabled )
--> active: inactive ( dead )
--> Docs: man: sddm(1)
--> : man: sddm.conf(5)

--> graphical.target

--> reading installed packages
( shows a table with 3 lines: headings are: s Name Type Version Arch Repository)
--> i Mesa-dr-nouveau Package 18.3.2-lp151.22.4 x86_64
--> i libdrm_nouveau2 Package 2.4.97-lp151.1.1 x86_64
--> i libvdpa_nouveau Package 18.3.2-lp151.22.4

Again I tried
I get full list of packages, over a full screens worth.
( there was no y/n question - that was my scribbled notes -sorry. )

gives me a table will all my repositories, sorry no screenshot, I can't seem to get one , but here is the table
11 lines with headings : # Alias Name Enabled GPG Check ( and the http locations which I left out )
1 openSUSE-leap-15.1 openSUSE-leap-15.1 No --
2 Repo-debug
3 Repo-debug-non-oss
4 Repo-debug-update
5 Repo-debug-update-non-oss
6 Repo-non-oss
7 Repo-oss
8 Repo-source
9 Repo-source-non-oss
10 Repo-update
11 Repo-update-non-oss

Only items 6,7,10,11 show as enabled with a GPG showing "(r) yes"

Runlevel.
When I edit the boot command line I need to add "3" to the end of the line.
If I omit the "3" or if I add a "5" I do not get to my console window. The system hangs showing the last 2 or 3 lines
[OK] target multi user system
[OK] reached graphical target
[OK] .. UTMI abort system runlevel change

and then my system hangs, just showing my mouse pointer.

and selecting the sddm option, followed by a restart, might be all that is required to end your travails. 42.3 used content in /etc/sysconfig for managing the DM default, while 15.1 switched to /etc/alternatives. The transition between them from upgrading doesn't always work right, since skipping over 15.0 from 42.3 to 15.1 is not officially supported.

1 members found this post helpful.

Hi Mrmazda, and Thanks.
I'm doing a clean install onto a brand new virgin HDD using a downloaded .iso image of leap 15.1
I am using leap 42.3 just now, but I am installing Leap 15.1 onto this new HDD. ( same computer box, motherboard etc, but I'm switching between HDD's ).
I am not upgrading from leap 42.3
This is what is causing me so much confusion and frustration. I have been using Suse for about 15 yrs or longer, going back to v8.0 and I have never had an issue like this before.

When I enter your code I get
--> There are 4 choices :
0* /usr/lib/X11/displaymanagers/sddm ( Priority 25 ) status automode
1 /usr/lib/X11/displaymanagers/console ( Priority 5 ) status manual mode
2 /usr/lib/X11/displaymanagers/lightdm ( Priority 15 ) status manual mode
3 /usr/lib/X11/displaymanagers/sddm ( Priority 25 ) status manual mode
4 /usr/lib/X11/displaymanagers/xdm ( Priority 10 ) status manual mode

I see that sddm is already the default, so I chose "3" which also shows "sddm"

on reboot, I do not get any change. So I tried again putting it back to the default, but again no change.
Everything same as before.

SuSE 8.0 was my first SuSE too.

If /etc/sysconfig/displaymanager still exists, it might be good to remove it. It's no longer owned by any package, so shouldn't be missed. Simply removing it probably won't affect anything immediate, if ever.

Something worth a try would be use update-alternatives to select LightDM. If it works, you should be fine to leave it. If it doesn't, try XDM. If that too fails, after the switch to it, remove SDDM from the system, including any files it might leave behind in /etc/sddm/. Then reboot for good measure, then install SDDM and reboot again. Installation should reset it in /etc/alternatives, and hopefully make it work.

? ? ? PROGRESS ? ? ?

returned prompt.

Chose option 2 , ( lightdm ) and re-booted : No change.

Tried again and chose option 4 ( xdm ) and re-booted : Voila ! I get a log-in window.
The main display is still black, bit the icetea ( or whatever it is called ) log-in window same as in Leap 42.3 appears.
However,
I cannot log-in. I tried my "Username" and I tried "root", I switched to an older US style keyboard layout that I have, still nothing.

I'm not there yet, but this seems positive. I have yet to try removing sddm, ( I'm not exactly sure about how to go about that )
Is it ? ?

some zypper shortcuts:

• rm for remove
• in for install
• ref for refresh
• se for search
• lr for repos # list configured repos
• up for update
• dup for dist-upgrade
• ve for verify

These are all included inThese can be performed through YaST text mode as well if you aren't comfortable using zypper.

Thx. Zypper is new to me, but I think I can get a handle on it.

OK. returned :
--> Warning: No repositories defined. Operating only with the installed resolvables.
--> Nothing can be installed.
--> Reading installed packages.
--> Resolving package dependencies
--> The following 2 packages are going to be removed: sddm sddm-branding-openSuse
--> additional rpm warning:
--> Alternatives /usr/lib/X11/displaymanagers/sddm ( part of link group default-displaymanagers ) doesn't exist.
--> Removing from list of alternatives.
--> "go ahead y/n ?" I Chose "y", then hit enter.

Then Shutdown and re-boot.

Then Shutdown and re-boot.

On re-start I get to my icetea login window, but still cannot log-in. Does not accept my login.
I see the screen flicker, and then comes back to give me a fresh log-in window.

Since this was an unsupported upgrade, let's look for 42.3 packages that should have been replaced or removed:If you redirect to a fileyou can cut and paste here from the file, if the output is only a small amount. If it's big, upload it to a pastebin as instructed for Xorg.0.log in comment #10.

I've been forgetting to ask for an important diagnostic, the journal. If the search for old packages (comment #24) turns up nothing relevant, please upload the file this generates (as in comment #10):If you run it without the redirect, you can scan screen output yourself looking for possible clues to why sddm does not work.

I did confirm 'systemctl status xdm' should should be enabled, and (of) sddm should be disabled.

Hello MrMazda, thanks for staying with me on this.
returns command prompt
returns command prompt

Note: You say am I misunderstanding what you mean here ?

This was NOT an Upgrade by my understanding. This was a fresh install of a 15.1 .iso image onto a virgin harddrive.
Leap 42.3 has never been on this drive, so there cannot be any leap42.3 packages on it, hidden or not.

So here is my journal, I had a look through it, but it is 1300 lines of code, and nothing leaps( pardon the pun ) out at me.
Maybe to the trained observer it will make more sense.
https://susepaste.org/49686386

On it you have this:nouveau.modeset=0 blocks the use of the nouveau kernel driver, as if it had been blacklisted. There are only two valid uses for it: 1-troubleshooting; 2-NVidia driver installation requires it. It has the same impact as nomodeset. A fresh installation without NVidia driver tainting should not need it, so remove it using the E key at the Grub menu and see how things go. At the same time also remove the 3, as it prevents any GUI from automatically starting. If you now get a nice SDDM GUI, use YaST2 bootloader to remove both nouveau.modeset=0 and 3.

Normally when nouveau.modeset=0 is present you should have a crudely working GUI based upon the FBDEV or VESA driver. Doesshow that xf86-video-fbdev and/or xf86-video-vesa are installed?

returns a table with 3 lines showing :
xf86-video-fbdev 0.5.0-lp151.1.2
xf86-video-nouveau 1.0.15-lp151.4.1
xf86-video-vesa 2.4.0-lp151.2.3
all packages shown as being in the main repository.

With regard to Editing grub, I need to include the "3" in order to get to a command prompt.
If I omit the "3", I do not get a command prompt, but instead I get a login window. ( with no background gui )
When I enter my username and password into this log-in window, I get a quick flash of the screen, showing some coding and then I get returned to the same log-in window.
I have tried to get passed this using various pw Log-in as root etc, but it has so far proven to be a dead end for me.

That was before. Is it still that way now?

It needs to be tried again without nouveau.modeset=0 and with plymouth.enable=0 and without 3. Are you still unable to Ctrl-Alt-F3 from the GUI login screen to reach a shell prompt? If so, please provide via pastebinning a today's Xorg.0.log generated while booted with this =0, =0 and not 3 combination. Do Xorg.0.log.old if necessary because you can't get to a shell prompt on the current boot. Also pastebin another journal from the same boot as the log, or this way if can't do it without another reboot:If you need to reboot twice, then use a 2 instead of a 1. If you get an error message about missing persistent journal, root or sudo may need to create directory /var/log/journal and rebooting again.

OK.
I re-booted and at Grub, I entered E to edit.
I then appended "plymouth.enable=0" to the end of the linux line, and then booted with ctrl+x.
I get to the log-in window, but it will not accept my log-in Username or password.
So I do Crtl + Alt + F3 and I get to the command prompt.
I log in as root.
I mount my usb drive and copy the Xorg.0.log file onto it
It is uploaded here:
https://susepaste.org/65630028

Then I enter
I get an error message about missing persistant journal. So I made the directory
I then shutdown and re-boot.
Re-boot as before, appending the plymouth.enable=0 to the Grub.
I have then copied the journal to my usb and uploaded it here :
https://susepaste.org/48523790