You are not logged in.

#1 2018-02-06 22:06:25

Batou
Member
Registered: 2017-01-03
Posts: 259

New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

I updated everything today and after a reboot, I'm greeted with black screen and a mouse pointer when I boot. X server clearly doesn'l like something.
I have mdm setup to load up cinnamon but that's clearly not working. How do I troubleshoot this?
Thanks.

PS: LTS kernel also boots to black screen... it too was in the update I installed. I'm basically stuck with Windows for now.


Please vote for all the AUR packages you're using. You can mass-vote for all of them by doing: "pacman -Qqm | xargs aurvote -v" (make sure to run "aurvote --configure"  first)

Offline

#2 2018-02-06 23:06:04

loqs
Member
Registered: 2014-03-06
Posts: 17,194

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

Ctrl+Alt+F2 to switch to another terminal then disable mdm you can then examine the journal and xorg.log.  If you can not change terminal
Change the default target to multi-user.target should stop mdm from starting.
edit:
multi-user.target not mult-user.target

Last edited by loqs (2018-02-06 23:06:55)

Offline

#3 2018-02-06 23:24:43

Batou
Member
Registered: 2017-01-03
Posts: 259

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

Hmm... Here's the .xsession-errors. Is blueman / blueman-applet killing my session? During today's update, lots of python libs were updated. Other than this, I don't see what could be causing this.

syndaemon: no process found
/etc/mdm/Xsession: Beginning session setup...
/etc/mdm/Xsession: Setup done, will execute: /bin/ssh-agent -- cinnamon-session-cinnamon
cinnamon-session[3083]: EggSMClient-WARNING: t+0.01445s: Desktop file '/home/batou/.config/autostart/nvdock.desktop' has malformed Icon key 'nvdock.png'(should not include extension)
** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
=== xinerama setup Configuration ===
  Clone: false
  Output: (null) attached to DVI-D-0
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-0
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-1
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: SAMSUNG 40" attached to HDMI-0
     status: on
     width: 3840
     height: 2160
     rate: 60
     primary: false
     position: 0 0
  Output: (null) attached to DP-2
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-3
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-4
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-5
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
=== Applying Configuration Configuration ===
  Clone: false
  Output: (null) attached to DVI-D-0
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-0
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-1
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: SAMSUNG 40" attached to HDMI-0
     status: on
     width: 3840
     height: 2160
     rate: 60
     primary: true
     position: 0 0
  Output: (null) attached to DP-2
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-3
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-4
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
  Output: (null) attached to DP-5
     status: off
     width: -1
     height: -1
     rate: -1
     primary: false
     position: -1 -1
18:08:17 [32m[INFO][0;1m Systems icon theme is: "MacBuntu-OS"[0m
(uint32 1,)
18:08:17 [32m[INFO][0;1m Loading extension "org.albert.extension.applications"[0m
18:08:17 [32m[INFO][0;1m Start indexing applications.[0m
18:08:17 [32m[INFO][0;1m Loading extension "org.albert.extension.calculator"[0m
18:08:17 [32m[INFO][0;1m Loading extension "org.albert.extension.kvstore"[0m
18:08:17 [32m[INFO][0;1m Loading extension "org.albert.extension.ssh"[0m
18:08:17 [32m[INFO][0;1m Loading extension "org.albert.extension.system"[0m
18:08:17 [32m[INFO][0;1m Loading extension "org.albert.extension.terminal"[0m
18:08:17 [33m[WARN][0;1m Application has not been terminated graciously.[0m
Cjs-Message: JS LOG: About to start Cinnamon
Initializing nemo-image-converter extension
** Message: nemo-desktop: session is cinnamon, establishing proxy
18:08:18 [32m[INFO][0;1m Indexed 196 applications.[0m
St-Message: cogl npot texture sizes SUPPORTED
Cjs-Message: JS LOG: Cinnamon started at Tue Feb 06 2018 18:08:18 GMT-0500 (EST)
/usr/lib/python3.6/site-packages/caffeine/main.py:59: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
  from gi.repository import AppIndicator3
INFO:caffeine.core:Caffeine is starting up...
Cjs-Message: JS WARNING: [/home/batou/.local/share/cinnamon/applets/tracker@glebihan/applet.js 169]: assignment to undeclared variable menuItem
Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
Cinnamon warning: Log level 8: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Cinnamon warning: Log level 8: cr_declaration_parse_list_from_buf: assertion 'parser' failed

(cinnamon:3675): St-WARNING **: Ignoring length property that isn't a number at line 967, col 11
Cjs-Message: JS WARNING: [/usr/share/cinnamon/js/ui/popupMenu.js 1908]: reference to undefined property children[childAfterIndex]._delegate
openGL version 3.1 detected (GL3 Cogl Driver)
Cjs-Message: JS LOG: Invalid network device type, is 14
Cjs-Message: JS LOG: network applet: Found connection for active

(nvdock:3950): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 'private->update_and_descendants_freeze_count > 0' failed

(autokey-gtk:3771): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(caffeine:3770): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(alarm-clock:3786): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 'private->update_and_descendants_freeze_count > 0' failed

(clipit:3796): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 'private->update_and_descendants_freeze_count > 0' failed

(nemo-desktop:3825): Gtk-WARNING **: Allocating size to NemoWindowPane 0x55d47d0993c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Nemo-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled

/usr/lib/python3.6/site-packages/blueman/plugins/applet/AppIndicator.py:8: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
  from gi.repository import AppIndicator3 as girAppIndicator
blueman-applet version 2.0.5 starting
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 175, in activate_name_owner
    return self.get_name_owner(bus_name)
  File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 361, in get_name_owner
    's', (bus_name,), **keywords)
  File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.bluez': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/bin/blueman-applet", line 121, in <module>
    BluemanApplet()
  File "/bin/blueman-applet", line 63, in __init__
    self.Plugins.Load()
  File "/usr/lib/python3.6/site-packages/blueman/main/PluginManager.py", line 90, in Load
    __import__(self.module_path.__name__ + ".%s" % plugin, None, None, [])
  File "/usr/lib/python3.6/site-packages/blueman/plugins/applet/DBusService.py", line 12, in <module>
    from blueman.main.applet.BluezAgent import AdapterAgent
  File "/usr/lib/python3.6/site-packages/blueman/main/applet/BluezAgent.py", line 23, in <module>
    from blueman.bluez.Agent import Agent, AgentMethod
  File "/usr/lib/python3.6/site-packages/blueman/bluez/Agent.py", line 48, in <module>
    class Agent(dbus.service.Object):
  File "/usr/lib/python3.6/site-packages/blueman/bluez/Agent.py", line 56, in Agent
    @AgentMethod
  File "/usr/lib/python3.6/site-packages/blueman/bluez/Agent.py", line 38, in AgentMethod
    if BlueZInterface.get_interface_version()[0] < 5:
  File "/usr/lib/python3.6/site-packages/blueman/bluez/BlueZInterface.py", line 16, in get_interface_version
    obj = dbus.SystemBus().get_object('org.bluez', '/')
  File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python3.6/site-packages/dbus/proxies.py", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
[2018-02-06T23:08:47] [ERR] Key file does not have key “alarm_high_threshold” in group “lmsensor coretemp-isa-0000 Package id 0”
[2018-02-06T23:08:47] [ERR] Key file does not have key “alarm_low_threshold” in group “lmsensor coretemp-isa-0000 Package id 0”

(psensor:16588): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Cinnamon warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00003 (Authentica)
Cinnamon warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00003 (Authentica)

(cinnamon:3675): Clutter-WARNING **: clutter-offscreen-effect.c:207: Unable to create an Offscreen buffer

Please vote for all the AUR packages you're using. You can mass-vote for all of them by doing: "pacman -Qqm | xargs aurvote -v" (make sure to run "aurvote --configure"  first)

Offline

#4 2018-02-07 08:34:54

Pillgar
Member
Registered: 2017-07-05
Posts: 41

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

I had the same issue also Batou.  Using XFCE with lightDM.  The best I could do to get it working again was to downgrade to kernel 4.14 with nvidia 387.

cd /var/cache/pacman/pkg/
sudo pacman -U nvidia-387.34-21-x86_64.pkg.tar.xz nvidia-utils-387.34-5-x86_64.pkg.tar.xz linux-4.14.15-1-x86_64.pkg.tar.xz linux-headers-4.14.15-1-x86_64.pkg.tar.xz

There's nothing more worse then being stuck in Windows!

Offline

#5 2018-02-07 11:20:56

Batou
Member
Registered: 2017-01-03
Posts: 259

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

Pillgar wrote:

I had the same issue also Batou.  Using XFCE with lightDM.  The best I could do to get it working again was to downgrade to kernel 4.14 with nvidia 387.

cd /var/cache/pacman/pkg/
sudo pacman -U nvidia-387.34-21-x86_64.pkg.tar.xz nvidia-utils-387.34-5-x86_64.pkg.tar.xz linux-4.14.15-1-x86_64.pkg.tar.xz linux-headers-4.14.15-1-x86_64.pkg.tar.xz

There's nothing more worse then being stuck in Windows!

Same. I rolled back everything to Feb 4. Now everything works.

This new kernel is cancer. I've tried it in a Vbox on another machine and was getting same errors. Even on a new install, nothing worked. There were no real error messages either. Programs were segfaulting in all kinds of libraries. Even after removing packages and installing older libs, things were still breaking. I disabled mdm and just used startx to get the DE up. But even then it was locking up.

I actually managed to get Cinnamon going through "---replace" mechanism but couldn't boot directly into it. Even then, Nvidia driver was crapping out and everything was lagging too. My mouse was stuttering when loading an image-heavy website. Even when logging into my company's VPN, the nm client was segfaulting. Absolute nightmare.

Stay away from 4.15 for few releases until they fix all the issues. That kernel should not have been pushed out of testing.

Last edited by Batou (2018-02-07 11:35:49)


Please vote for all the AUR packages you're using. You can mass-vote for all of them by doing: "pacman -Qqm | xargs aurvote -v" (make sure to run "aurvote --configure"  first)

Offline

#6 2018-02-07 12:49:48

Krakonos
Member
Registered: 2017-07-19
Posts: 4

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

Hi!

Just a quick heads up: this might be a problem with Intel graphics as well. Also, I noticed a few stacktraces in dmesg (ssh'd in from my laptop).

Feb 07 12:53:58 gazelle kernel: Call Trace:
Feb 07 12:53:58 gazelle kernel:  intel_ddi_pre_enable+0x18c/0x7d0 [i915]
Feb 07 12:53:58 gazelle kernel:  ? fwtable_write32+0x46/0x230 [i915]
Feb 07 12:53:58 gazelle kernel:  intel_encoders_pre_enable.isra.58+0x62/0x80 [i915]
Feb 07 12:53:58 gazelle kernel:  haswell_crtc_enable+0x16e/0x7f0 [i915]
Feb 07 12:53:58 gazelle kernel:  intel_update_crtc+0x39/0x90 [i915]
Feb 07 12:53:58 gazelle kernel:  skl_update_crtcs+0x24b/0x270 [i915]
Feb 07 12:53:58 gazelle kernel:  intel_atomic_commit_tail+0x218/0xd20 [i915]
Feb 07 12:53:58 gazelle kernel:  intel_atomic_commit+0x268/0x2a0 [i915]
Feb 07 12:53:58 gazelle kernel:  drm_atomic_helper_set_config+0x80/0x90 [drm_kms_helper]
Feb 07 12:53:58 gazelle kernel:  __drm_mode_set_config_internal+0x67/0x110 [drm]
Feb 07 12:53:58 gazelle kernel:  drm_mode_setcrtc+0x3fb/0x5b0 [drm]
Feb 07 12:53:58 gazelle kernel:  ? i915_gem_execbuffer2+0x248/0x390 [i915]
Feb 07 12:53:58 gazelle kernel:  ? drm_mode_getcrtc+0x170/0x170 [drm]
Feb 07 12:53:58 gazelle kernel:  drm_ioctl_kernel+0x5b/0xb0 [drm]
Feb 07 12:53:58 gazelle kernel:  drm_ioctl+0x2d5/0x370 [drm]
Feb 07 12:53:58 gazelle kernel:  ? drm_mode_getcrtc+0x170/0x170 [drm]
Feb 07 12:53:58 gazelle kernel:  do_vfs_ioctl+0xa4/0x630
Feb 07 12:53:58 gazelle kernel:  ? __do_page_fault+0x29d/0x500
Feb 07 12:53:58 gazelle kernel:  SyS_ioctl+0x74/0x80
Feb 07 12:53:58 gazelle kernel:  ? do_page_fault+0x32/0x110
Feb 07 12:53:58 gazelle kernel:  entry_SYSCALL_64_fastpath+0x20/0x83

Downgrading to linux-4.14.15-1-x86_64.pkg.tar.xz fixed the issue.

Hardware: i7-7700K with integrated graphics.

Offline

#7 2018-02-07 13:18:38

Batou
Member
Registered: 2017-01-03
Posts: 259

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

Krakonos wrote:

Hi!

Just a quick heads up: this might be a problem with Intel graphics as well.

4.15 made some massive changes in the way memory and userspace is managed.  Errors I was seeing were bizarre and not all of them were graphics related. It's just that when something fails in the graphics driver, you notice it immediately. NetworkManager and OpenVPN were also segfaulting under 4.15 on my machine.


Please vote for all the AUR packages you're using. You can mass-vote for all of them by doing: "pacman -Qqm | xargs aurvote -v" (make sure to run "aurvote --configure"  first)

Offline

#8 2018-02-14 04:48:38

Pillgar
Member
Registered: 2017-07-05
Posts: 41

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

After some digging, I found that disabling the "Force Composition Pipeline" option in xorg.conf, allowed the system to boot up into the desktop with out issue under kernel 4.15 with nvidia 390. 25.  Enabling it on boot (full or not), produces the same black screen and mouse pointer Batou described originally.   No lag or stutters either.  Just the occasional screen tear.  Oh well, back to compton until this gets fixed.

Offline

#9 2018-02-14 12:56:58

Batou
Member
Registered: 2017-01-03
Posts: 259

Re: New 4.15 kernel + Nvidia = Black screen when mdm starts into Cinnamon

Pillgar wrote:

After some digging, I found that disabling the "Force Composition Pipeline" option in xorg.conf, allowed the system to boot up into the desktop with out issue under kernel 4.15 with nvidia 390. 25.  Enabling it on boot (full or not), produces the same black screen and mouse pointer Batou described originally.   No lag or stutters either.  Just the occasional screen tear.  Oh well, back to compton until this gets fixed.

Yep. That's the issue. I've documented it in this thread as well: https://bbs.archlinux.org/viewtopic.php … 9#p1767949

BTW, screen issues aren't that bad on my setup. Noticed slowdown once when playing a YT video but it went away.

Last edited by Batou (2018-02-14 13:41:31)


Please vote for all the AUR packages you're using. You can mass-vote for all of them by doing: "pacman -Qqm | xargs aurvote -v" (make sure to run "aurvote --configure"  first)

Offline

Board footer

Powered by FluxBB