I have been working perfect with Opensuse 13.1 for some time now, and a couple of days ago, when I switched on the laptop I could not get the logging screen.
All I was getting was the black screen of console mode…
# uname -a
Linux linux-diy5.site 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) i686 athlon i386 GNU/Linux
So I decided as a normal user to start X. This did not work.
So I decided to start X as a root, and it worked.
This is the output to startx
hostname: Nombre o servicio desconocido
xauth: file /root/.serverauth.1734 does not exist
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.14.3.901 (1.14.4 RC 1)
Release Date: 2013-10-26
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux linux-diy5.site 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.10-21-desktop root=UUID=9331a315-f706-4d97-9de6-f4e7be4b4436 resume=/dev/disk/by-id/ata-ST9250827AS_5RG2H8WQ-part5 splash=silent quiet showopts
Build Date: 17 April 2014 05:37:34AM
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 25 18:56:17 2014
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(II) [KMS] Kernel modesetting enabled.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale es_ES.UTF-8 ...
Checking for a default input method in /etc/X11/xim.d/es/
sourcing /etc/X11/xim.d/es/40-ibus ...
/etc/X11/xim.d/es/40-ibus started sucessfully
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Compat map for group 2 redefined
> Using new definition
> Warning: Compat map for group 3 redefined
> Using new definition
> Warning: Compat map for group 4 redefined
> Using new definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Compat map for group 2 redefined
> Using new definition
> Warning: Compat map for group 3 redefined
> Using new definition
> Warning: Compat map for group 4 redefined
> Using new definition
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Compat map for group 2 redefined
> Using new definition
> Warning: Compat map for group 3 redefined
> Using new definition
> Warning: Compat map for group 4 redefined
> Using new definition
Errors from xkbcomp are not fatal to the X server
(II) AIGLX: Suspending AIGLX clients for VT switch
And this is the ouput to startx as a normal user:
hostname: Nombre o servicio desconocido
xauth: file /home/rpanes/.serverauth.3441 does not exist
(EE)
Fatal server error:
(EE) Cannot move old log file "/var/log/Xorg.0.log" to "/var/log/Xorg.0.log.old"
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
-------------------------------------------------------------------------------------------
xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local
Any ideas how I can get back the logging screen to normal users and nay reasons why this could have happened?
Does “Recovery Mode” work? (“Advanced Options” in the boot menu)
Which graphics card and driver are you using? How did you install the driver?
There was a kernel update recently. If you installed a proprietary driver manually, you have to re-install it after every kernel update.
So I decided as a normal user to start X. This did not work.
A normal user cannot run “startx” in the standard openSUSE set up.
Have a look at /etc/permissions.local for how to change this, but it would be a security risk.
You don’t need startx anyway, normally a display manager (= login screen) is used to start X.
The output you got from startx told you that:
-------------------------------------------------------------------------------------------
xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local
And another thing:
Please do a normal boot. When you drop to text mode, run “sudo systemctl status xdm” and post the output (maybe make a picture).
Then reboot to recovery mode (or run “startx” as root) and post the file /var/log/Xorg.0.log.old (use http://susepaste.org or similar).
You should be able to have an internet connection as root as well, and be able to use an internet browser.
Just ignore all warnings people might give you, for now.
You would possibly have to re-configure it if it is a wireless connection though. But it should work…
2.- This is my graphics card version
/sbin/lspci -nnk | grep VGA -A2
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] [1002:9612]
Subsystem: Hewlett-Packard Company Device [103c:30f1]
Kernel driver in use: radeon
Well, this should rule out any graphics driver problem due to the kernel update.
So, does recovery mode work?
You can start X as root, as you say. Can you do this and then post the file /var/log/Xorg.0.log.old, please?
Note that this file only contains the log from the previous start of X, so you should post it immediately after the start fails and you log in as root (or rebooting to recovery mode, if possible, would work as well).
But that output from “systemctl” that I requested earlier might be significant as well…
Continuing with the problem, please find attached some other issues wich were asked about:
3.- Recovery mode.
I have tried to log in as a normal user and as root in recovery mode and it does not work either.
After I put the user name in the terminal, I do not even get the message “password”, but a message saying time out.
This would provide a clue, though.
It doesn’t say anything about “failed” or similar. This rather looks like xdm (i.e. the graphical interface) is not started at all.
Could it be that you somehow changed the default target to “multi-user” or “runlevel3” by mistake?
Please post the output of:
systemctl get-default
It should be “runlevel5” or “graphical”.
If it is not, use this to correct that:
sudo systemctl set-default graphical
Or verify/rectify that in YaST->System->Services Manager (you can run yast in text mode as well).
5.- This is the content of the file Xorg.0.log.old
This doesn’t contain any error. It is from your last successful start of X apparently.
If my above suspicion is true, it would explain this of course, as X would be not even started on boot.
Right. runlevel4 was never really defined in (open)SUSE, but X is only started in runlevel5.
systemd doesn’t have runlevels any more, but runlevelX.target are defined for compatibility.
runlevel4.target is in fact just a symlink to multi-user.target, which is the same as the old runlevel3, i.e. multi-user system with network running in text mode.
So I entered
sudo systemctl set-default graphical
to get it changed to runlevel 5. But it didn’t work.
It should have been “sudo systemctl set-default graphical.target”, sorry.
So I went into YaST->System->Services Manager and I changed to runlevel5.
…and the best thing is that it worked !
So, problem solved. Now I have back my logging screen.
Good!
Thank you very much for taking the time to guide me through the process of solving this issue.
