ppenSUSE 13.2 black screen after login

English Install/Boot/Login
1

Hi all, I did a fresh installation of openSuse 13.2 from the DVD in a HP 240 Notebook.

However, after login with the user I created during the installation I get a black screen and can’t do anything. I can only use my openSuse in recovery mode.

This is my hardware info

uname -a
Linux kde.kde.org 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) x86_64 x86_64 x86_64 GNU/Linux

lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 55
Model name: Intel(R) Celeron(R) CPU N2840 @ 2.16GHz
Stepping: 8
CPU MHz: 3100.804
CPU max MHz: 3100.0000
CPU min MHz: 600.0000
BogoMIPS: 4326.40
Virtualization: VT-x
L1d cache: 24K
L1i cache: 32K
L2 cache: 1024K
NUMA node0 CPU(s): 0,1

sudo /sbin/lspci -nnk | grep VGA -A2
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)
Subsystem: Hewlett-Packard Company Device [103c:220f]
Kernel modules: i915

sudo /sbin/lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
00:13.0 SATA controller: Intel Corporation Device 0f23 (rev 0e)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB xHCI (rev 0e)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
00:1c.0 PCI bridge: Intel Corporation Device 0f48 (rev 0e)
00:1c.1 PCI bridge: Intel Corporation Device 0f4a (rev 0e)
00:1c.2 PCI bridge: Intel Corporation Device 0f4c (rev 0e)
00:1c.3 PCI bridge: Intel Corporation Device 0f4e (rev 0e)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
00:1f.3 SMBus: Intel Corporation Device 0f12 (rev 0e)
02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ether

Here is my xorg.0.log: http://paste.opensuse.org/57032184
and my kdm.log: http://paste.opensuse.org/65658553

Please, I really need your help. I am trying to solve this in many ways. I created another user as suggested in other forums, then login, but I get the black screen again and nothing seems to work.

Thanks

David

2

That’s from recovery mode, and doesn’t help much in identifying the problem.
Do a normal boot, then reboot to recovery mode and post /var/log/Xorg.0.log.old (that’s the log from the previous boot).

Have you installed all updates? There have been some fixes to the intel driver.
But as you are using Kernel 3.16.7-21, you probably have.

Btw, when having the “black screen”, do you still see the mouse pointer?
That would mean that “only” plasma-desktop crashed. You should still be able to launch applications via the Alt+F2 dialog (KRunner).

Would probably be helpful to get the ~/.xsession-errors-:0 file, this is recreated from scratch on each login though, so you’d have to post it from inside the broken KDE session, or rename it before logging in again.

3

Hi. Yes, I installed the updates.

I did what you said. Here is the xorg.0.log.old: SUSE Paste
and the .xsession-errors file: SUSE Paste (I don’t know how to login from inside the kde broken session, this is from recovery mode after login).

I can’t see the mouse pointer and run krunner. Now, I even get the black screen before login.

Thanks for your help.

David

4

Ok, good.

I did what you said. Here is the xorg.0.log.old: SUSE Paste

Hm, I don’t see anything wrong in there…

and the .xsession-errors file: SUSE Paste (I don’t know how to login from inside the kde broken session, this is from recovery mode after login).

That’s useless. As mentioned, this file gets recreated from scratch on every login.

I can’t see the mouse pointer and run krunner. Now, I even get the black screen before login.

Well, then it’s not a KDE issue, and the .xsession-errors file is irrelevant anyway.

If you suddenly have the problem even before login (where it worked earlier I suppose), this rather sounds like a hardware issue unfortunately (graphics card overheating or dying).

But let’s try something to see whether it is related to the graphics card/driver.
Please add “nomodeset” to the boot options in normal boot (i.e. not recovery mode), by pressing ‘e’ in the boot menu, looking for a line starting with “linux” (or “linuxefi”) and appending that to the end (without the quotes). Then press ‘F10’ to boot.
If the problem persists, something else is wrong.

And another thing: can you still switch to text mode (with Ctrl+Alt+F1) when you get the black screen?
If not, your system probably crashed completely.

5

Hi

I added nomodeset, then login successfully and realized that this is only for one session. So reading other forums, I go to Yast -> Bootloader -> Kernel Parameters and then added nomodeset. Now I can login in normal boot without any problems. Thank you very much for that, but can you please explain me, what is the effect of nomodeset?

Thanks for your time.

David

6

nomodset loads a generic video driver which is not great at performance. It really should only be used for special case where the regular driver fails. You can use it but your graphics performance will be sub-par

According to earlier posts you have an Intel GPU (graphics processor) Which should just work. Have you installed all the updates? There have been several updates to the Intel driver and the kernel since 13.2 was released that may fix the problem

7

Yes, I installed all the updates and tried different ways to solve the problem, but nothing worked except the nomodeset thing.

Cheers

David

8

Yes, but it’s still better than using recovery mode, which disables other performance settings as well.

At least that proves that the culprit is really the graphics card/driver.
As mentioned, I do suspect a hardware issue, since the problem got worse by itself.
The generic driver doesn’t use the card to its full potential, so that’s probably why it works fine then.

Another thing you could try is switching to the older, but more stable UXA acceleration method:
https://en.opensuse.org/SDB:Switch_xf86-video-intel_to_UXA
You have to remove the “nomodeset” option again first though.