OpenSUSE 13.2: Booting GUI for kernel 3.16.6-2 fails, kernel 3.11.10-21 fine

English Install/Boot/Login
1

Hi,

I upgraded my OpenSuse 13.1 to 13.2 and to my surprise starting up using the default kernel (3.16.6-2-desktop) is not working in a sense that the GUI does not come up while I can boot with an older kernel (3.11.10-21-desktop). Checked grub.cfg and the menuentries are the same except for the kernel versions…

I diffed the logs (/var/log/messages) for the two boot-ups and see quite some similarity up to and including the USB enumeration and:

kernel:     5.922538] audit: type=1400 audit(1417805297.279:2): apparmor="STATUS" operation="profile_load" name="/{usr/,}bin/ping" pid=636 comm="apparmor_parser"
kernel:     5.954631] audit: type=1400 audit(1417805297.312:3): apparmor="STATUS" operation="profile_load" name="/sbin/klogd" pid=643 comm="apparmor_parser"
kernel:     6.018920] audit: type=1400 audit(1417805297.376:4): apparmor="STATUS" operation="profile_load" name="/sbin/syslog-ng" pid=647 comm="apparmor_parser"
kernel:     6.079553] audit: type=1400 audit(1417805297.436:5): apparmor="STATUS" operation="profile_load" name="/sbin/syslogd" pid=651 comm="apparmor_parser"
kernel:     6.320501] audit: type=1400 audit(1417805297.677:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/apache2/mpm-prefork/apache2" pid=656 comm="apparmor_parser"
kernel:     6.320607] audit: type=1400 audit(1417805297.677:7): apparmor="STATUS" operation="profile_load" name="DEFAULT_URI" pid=656 comm="apparmor_parser"
kernel:     6.320736] audit: type=1400 audit(1417805297.678:8): apparmor="STATUS" operation="profile_load" name="HANDLING_UNTRUSTED_INPUT" pid=656 comm="apparmor_parser"
kernel:     6.320949] audit: type=1400 audit(1417805297.678:9): apparmor="STATUS" operation="profile_load" name="phpsysinfo" pid=656 comm="apparmor_parser"
kernel:     6.415612] audit: type=1400 audit(1417805297.772:10): apparmor="STATUS" operation="profile_load" name="/usr/lib/colord" pid=660 comm="apparmor_parser"
kernel:     6.441948] audit: type=1400 audit(1417805297.799:11): apparmor="STATUS" operation="profile_load" name="/usr/lib/dovecot/anvil" pid=664 comm="apparmor_parser"
kernel:     6.514354] audit: type=1400 audit(1417805297.871:12): apparmor="STATUS" operation="profile_load" name="/usr/lib/dovecot/auth" pid=668 comm="apparmor_parser"
kernel:     6.571965] audit: type=1400 audit(1417805297.929:13): apparmor="STATUS" operation="profile_load" name="/usr/lib/dovecot/config" pid=672 comm="apparmor_parser"

This looks allmost the same for the old log

Just after that I see the first message indicating problems:

systemd[1]: Failed to start Create static device nodes in /dev.

and somewhat later:


kernel:    58.533250] NET: Registered protocol family 17
kernel:    58.564886] audit_printk_skb: 105 callbacks suppressed
kernel:    58.564888] audit: type=1400 audit(1417805349.910:49): apparmor="DENIED" operation="mknod" profile="/usr/sbin/nscd" name="/run/nscd/passwd" pid=964 comm="nscd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
kernel:    58.564940] audit: type=1400 audit(1417805349.910:50): apparmor="DENIED" operation="mknod" profile="/usr/sbin/nscd" name="/run/nscd/group" pid=964 comm="nscd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
kernel:    58.565011] audit: type=1400 audit(1417805349.910:51): apparmor="DENIED" operation="mknod" profile="/usr/sbin/nscd" name="/run/nscd/services" pid=964 comm="nscd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
kernel:    58.565025] audit: type=1400 audit(1417805349.910:52): apparmor="DENIED" operation="mknod" profile="/usr/sbin/nscd" name="/run/nscd/netgroup" pid=964 comm="nscd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
kdm[905]: Quitting Plymouth with transition

(Note: The kernel time-stamp indicates 52 seconds between the two sets of audit messages but the log time stamps (not shown) indicate they are within a second)

Any tips on how to debug this?

2

Video and if AMD or NVIDIA did you reinstall the drivers??

3

> Video and if AMD or NVIDIA did you reinstall the drivers??

Not using AMD nor NVIDIA but a Intel Haswell Integrated Graphics Controller.

Doing some more experiments I see, sometime what is reported above, sometimes usb errors, and sometimes:

ModemManager[765]: <warn>  failed to create PolicyKit authority: 'Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: The connection is closed'
systemd-logind[800]: Failed to fully start up daemon: Connection reset by peer
systemd-hostnamed[798]: Failed to register name: Connection reset by peer

but nothing that seems to be related to video driver.

Like written, everything is fine with kernel 3.11.10-2 but 3.16.6-2 fails.

4

Ok then how did you upgrade exactly it may be you did not get the complete 13.2 and have mixed versions

5

I did upgrade following the instructions on https://en.opensuse.org/SDB:System_upgrade

6

An update:

New kernel updates came in but all had the same problem until the lastest kernel, Linux 3.16.7-21-desktop which works again.

So:

  • Linux 3.16.7-21-desktop - fine
  • Linux 3.16.7-7-desktop - problem
  • Linux 3.16.6-2-desktop - problem
  • Linux 3.11.10-21-desktop - fine
7

Thanks for the heads-up. I was having the same problem, X not starting upon installation of 13.2. Reinstalled 13.1. Saw you update, tried again, and no problems this time. My rig:

Machine: System: Gigabyte product: Z87X-UD4H
Mobo: Gigabyte model: Z87X-UD4H-CF version: x.x Bios: American Megatrends version: 10b date: 06/12/2014
CPU: Quad core Intel Core i5-4590 CPU (-MCP-) clocked at 3698.062 MHz
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
X.org: 1.16.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 126x38
Network: Card: Intel Ethernet Connection I217-V driver: e1000e
Drives: HDD Total Size: 500.1GB (5.7% used)
Info: Processes: 207 Uptime: 1:28 Memory: 1189.1/15122.6MB Runlevel: 5 Client: Shell inxi: 1.7.24

8

What do you mean on top of Win 10??? You mean dual boot or are you running in a VM?? or what??

9

This is a complete new subject. Please start a thread of your own and do not hijack someones elses thread. That will create a huge confusion.

I will remove your post above in due time, thus if you want to copy the text for your new thread be quick.

Others! Please do NOT answer here on the new question. Stay on the subject started by the OP here.

10

There was a new subject started here. It is now moved to a new thread. Reactions on it are deleted to keep this thread clean.

Please answer in the new thread.