[opensuse] login screen does not appear after booting
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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
Richmond wrote:
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.
For errors I meant /var/log/Xorg.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/15/2017 01:52 PM, Richmond wrote:
Richmond wrote:
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.
For errors I meant /var/log/Xorg....
Thank you for the information; interesting and helpful. From the Xorg... file, I found a couple of missing system files and installed them. Things are better, but still not booting up right. Here are some lines from the Xorg file, with grep searches for AIGLX and VT. I have a second computer with the same hardware (except different disks), still running v13.2. Comparing the Xorg files on the two systems shows that the lines near time 50... are not listed on the 'good' computer. [ 9.792] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 9.793] (II) AIGLX: enabled GLX_ARB_create_context [ 9.793] (II) AIGLX: enabled GLX_ARB_create_context_profile [ 9.793] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile [ 9.793] (II) AIGLX: enabled GLX_INTEL_swap_event [ 9.793] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 9.793] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB [ 9.793] (II) AIGLX: enabled GLX_ARB_fbconfig_float [ 9.793] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float [ 9.793] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 9.796] (II) AIGLX: Loaded and initialized nouveau [ 50.112] (II) AIGLX: Suspending AIGLX clients for VT switch [ 9.537] (++) using VT number 7 [ 9.800] (II) NOUVEAU(0): NVEnterVT is called. [ 50.112] (II) AIGLX: Suspending AIGLX clients for VT switch [ 50.112] (II) NOUVEAU(0): NVLeaveVT is called. I have not seen other problems. I am tempted to update the system on the second computer, but fearful that I might sort-of lose it. I am thinking of reinstalling v42.2 on the 'bad' computer. I may have made some errors when adding additional rpms. I have very successfully installed v42.2 on 3 other computers with similar architectures, except that the graphix cards use radeon drivers. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/15/2017 03:16 PM, Joseph Comfort wrote:
(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.
Well I'd start by looking at the system logs. There is an option with the logs to look at the result of the last boot. That's "journalctl -b" But see the man page or an on-line description for more details that may be pertinent to your situation. I'd make sure there were no impediments to the boot sequence, that you are in fact coming up in 'graphical mode', before worrying about the XORG settings. The modern Xorg is pretty smart at probing :-) let it do its thing as best if can first of all, but tat isn't going to work if there are problems about getting there or setting up the context for it to work in. "Cart before the horse" and all that. See also systemd-sysctl(8), systemd-analyze(1) But Gee, people wonder why I'm concerned about "upgrading" from 13.2 to LEAP ... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Joseph Comfort composed on 2017-02-15 17:16 (UTC-0700):
After doing a fresh install of Leap 42.2 on a computer that had been ... Graphics card: nVidia GT218 [GeForce 8400 GS, Rev.3]
I have one PC using this gfxcard, but its 42.2 has TDM as login manager. It also has 42.1 with KDM3, TW with both KDM3 and KDM (two separate installations), 13.2 with KDM, 13.1 with KDM3, plus Mageia 5, Fedora 24/25/Rawhide, Debian Jessie, Stretch & Sid, and Kubuntu 14.10. I seriously your gfxcard is your problem if you're using KDE3, TDE or Plasma with KDM.
Driver: nouveau, with drm
You do have another FOSS driver option should the problem actually have anything to do with Xorg rather than your DE or [gdm/sddm/lightdm/...]. Uninstalling xf86-video-nouveau will cause a GT218 to use the modesetting driver that is integrated in the Xorg server. ...
(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.
If you boot with 3 appended to cmdline, then login on a vtty and try startx, do you succeed to reach a GUI desktop? If yes, which? Which DE is your preferred? -- "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
I have solved the problem. Apparently I made some mistakes when adding more rpms to my installation via yast2. I tend to export (save) the list of installed rpms and then import the list when upgrading the system. The core system is now installed and operates smoothly. I will be very careful with the additional rpms. Thanks to everyone for guiding me in the right direction. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
Felix Miata -
Joseph Comfort -
Richmond