![](https://seccdn.libravatar.org/avatar/ac382cff46990fd2d473e23c3f2c71eb.jpg?s=120&d=mm&r=g)
Joseph Comfort wrote:
After doing a fresh install of Leap 42.2 on a computer that had been running v13.2, the system boots but the login screen does not show up, at the point where it should. I can log into the computer from another one and do essentially everything, including bringing up yast2 etc.
v13.2 had been running very well for some years. Before that, I was doing some experimenting with a solid state disk (SSD), and then used it for v13.2. I used the old-time partitioning system, and put / , swap, /usr, and /usr/local on the SSD. After the initial installation stage from the dvd, the system booted with a proper graphical display and I could log in and complete some tasks (e.g., network configuration). The graphical display fails on all subsequent reboots.
Some specs-- Motherboard: Gigabyte GA-970A-D3 (v1.1) Bios: Award F7 Graphics card: nVidia GT218 [GeForce 8400 GS, Rev.3] Driver: nouveau, with drm
The root / partition is on /dev/sda1, /usr is /dev/sda5, /usr/local is /dev/sda6, and /home is /dev/sdb1. These correspond to the hardware wirings. In the Yast2 bootloader app, I had to move /dev/sda1 up to the top of the list, and also adjust the optional kernel command line to that same point. Curiously, the /boot/grub2/grub.cfg file contains the line: set root='hd1,msdos5' .
(1) What is needed to get the graphical display to come up? (2) How does one set run levels now? (The screen goes black if I do a 'init 3', so there is at least some response.
Thank you. Joe
Runlevels are set in the directory: /usr/lib/systemd/system With symlinks like this: lrwxrwxrwx 1 root root 15 Jan 26 22:31 runlevel0.target -> poweroff.target lrwxrwxrwx 1 root root 13 Jan 26 22:31 runlevel1.target -> rescue.target drwxr-xr-x 1 root root 0 Jan 25 09:07 runlevel1.target.wants lrwxrwxrwx 1 root root 17 Jan 26 22:31 runlevel2.target -> multi-user.target drwxr-xr-x 1 root root 0 Jan 25 09:07 runlevel2.target.wants lrwxrwxrwx 1 root root 17 Jan 26 22:31 runlevel3.target -> multi-user.target drwxr-xr-x 1 root root 0 Jan 25 09:07 runlevel3.target.wants lrwxrwxrwx 1 root root 17 Jan 26 22:31 runlevel4.target -> multi-user.target drwxr-xr-x 1 root root 0 Jan 25 09:07 runlevel4.target.wants lrwxrwxrwx 1 root root 16 Jan 26 22:31 runlevel5.target -> graphical.target drwxr-xr-x 1 root root 0 Jan 25 09:07 runlevel5.target.wants lrwxrwxrwx 1 root root 13 Jan 26 22:31 runlevel6.target -> reboot.target So you should be able to do: systemctl runlevel5 etc. I think you should probably try starting an xserver from the consol as root and then see if there is a .xsession-errors Log in as root on the virtual console (ctrl-alt-f1) and then type: xinit -- :1 This will start an additional X display, or fail with some error. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org