Display Issues on Boot
Hey all,
I recently installed Kubuntu 19.10 Eoan Ermine on my ThinkPad T495 and am enjoying it so far, but I've run into what seems like some driver issues.
Often times, after Kubuntu starts booting, I see the splash screen briefly which cuts out to a console which blinks for a few seconds. The cursor then appears and I'm able to move it with the touchpad, but after several seconds the display cuts out indefinitely and I have to press and hold the power button and restart. The following is the end snippet of a systemd log of one of these occurrences:
To mitigate this, I append nomodeset to the kernel boot parameters; however, if I do this, I cannot change the brightness in Plasma nor does suspend/resume work.
Furthermore, this doesn't occur consistently: sometimes I start up my laptop and everything works fine. But a lot of other times, it won't.
The above leads me to believe there is some sort of driver problem, but I'm not sure how to proceed. Would anyone be able to help me with this? I can provide more info/logs if necessary.
I recently installed Kubuntu 19.10 Eoan Ermine on my ThinkPad T495 and am enjoying it so far, but I've run into what seems like some driver issues.
Often times, after Kubuntu starts booting, I see the splash screen briefly which cuts out to a console which blinks for a few seconds. The cursor then appears and I'm able to move it with the touchpad, but after several seconds the display cuts out indefinitely and I have to press and hold the power button and restart. The following is the end snippet of a systemd log of one of these occurrences:
Code:
Nov 12 12:18:30 dev-t495 sddm-greeter[1204]: Connected to the daemon.
Nov 12 12:18:30 dev-t495 sddm[1043]: Message received from greeter: Connect
Nov 12 12:18:30 dev-t495 mpd[1202]: exception: Failed to open '/etc/mpd.conf': Permission denied
Nov 12 12:18:30 dev-t495 systemd[1179]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Nov 12 12:18:30 dev-t495 systemd[1179]: mpd.service: Failed with result 'exit-code'.
Nov 12 12:18:30 dev-t495 systemd[1179]: Failed to start Music Player Daemon.
Nov 12 12:18:30 dev-t495 dbus-daemon[861]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.51' (uid=121 pid=1203 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
Nov 12 12:18:30 dev-t495 systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Nov 12 12:18:30 dev-t495 dbus-daemon[861]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Nov 12 12:18:30 dev-t495 systemd[1]: Started RealtimeKit Scheduling Policy Service.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Successfully called chroot.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Successfully dropped privileges.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Successfully limited resources.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Running.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Canary thread running.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Watchdog thread running.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 rtkit-daemon[1221]: Supervising 0 threads of 0 processes of 1 users.
Nov 12 12:18:30 dev-t495 systemd[1179]: Started Sound Service.
Nov 12 12:18:30 dev-t495 systemd[1179]: Reached target Main User Target.
Nov 12 12:18:30 dev-t495 systemd[1179]: Startup finished in 825ms.
Nov 12 12:18:30 dev-t495 bluetoothd[871]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc
Nov 12 12:18:30 dev-t495 bluetoothd[871]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc
Nov 12 12:18:30 dev-t495 kernel: Bluetooth: RFCOMM TTY layer initialized
Nov 12 12:18:30 dev-t495 kernel: Bluetooth: RFCOMM socket layer initialized
Nov 12 12:18:30 dev-t495 kernel: Bluetooth: RFCOMM ver 1.11
Nov 12 12:18:32 dev-t495 kernel: failed to write reg 28b4 wait reg 28c6
Nov 12 12:18:33 dev-t495 kernel: failed to write reg 1a6f4 wait reg 1a706
Nov 12 12:18:33 dev-t495 sddm-greeter[1204]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Nov 12 12:18:33 dev-t495 sddm-greeter[1204]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffcd2add2e0), parent's thread is QThread(0x55cfd50e0190), current thread is QThread(0x55cfd515ff20)
Nov 12 12:18:33 dev-t495 sddm-greeter[1204]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffcd2add2e0), parent's thread is QThread(0x55cfd50e0190), current thread is QThread(0x55cfd515ff20)
Nov 12 12:18:33 dev-t495 sddm-greeter[1204]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffcd2add2e0), parent's thread is QThread(0x55cfd50e0190), current thread is QThread(0x55cfd515ff20)
Nov 12 12:18:33 dev-t495 sddm-greeter[1204]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Nov 12 12:18:34 dev-t495 sddm-greeter[1204]: Cannot watch QRC-like path ":/icons/hicolor/index.theme"
Nov 12 12:18:34 dev-t495 dbus-daemon[861]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.95' (uid=121 pid=1204 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-wNyIKO" label="unconfined")
Nov 12 12:18:34 dev-t495 systemd[1]: Starting Daemon for power management...
Nov 12 12:18:34 dev-t495 upowerd[1233]: energy_full (51.480000) is greater than energy_full_design (50.500000)
Nov 12 12:18:34 dev-t495 dbus-daemon[861]: [system] Successfully activated service 'org.freedesktop.UPower'
Nov 12 12:18:34 dev-t495 systemd[1]: Started Daemon for power management.
Nov 12 12:18:35 dev-t495 sddm-greeter[1204]: Adding view for "eDP" QRect(0,0 1920x1080)
Nov 12 12:18:37 dev-t495 kernel: failed to write reg 28b4 wait reg 28c6
Nov 12 12:18:39 dev-t495 kernel: failed to write reg 1a6f4 wait reg 1a706
Nov 12 12:18:42 dev-t495 snapd[920]: autorefresh.go:385: Cannot prepare auto-refresh change due to a permanent network error: persistent network error: Get https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD?max-format=3: dial tcp: lookup api.snapcraft.io: Temporary failure in name resolution
Nov 12 12:18:42 dev-t495 snapd[920]: stateengine.go:150: state ensure error: persistent network error: Get https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD?max-format=3: dial tcp: lookup api.snapcraft.io: Temporary failure in name resolution
Nov 12 12:18:48 dev-t495 systemd[1]: systemd-fsckd.service: Succeeded.
Nov 12 12:18:49 dev-t495 systemd[1]: systemd-hostnamed.service: Succeeded.
Nov 12 12:18:49 dev-t495 kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
Nov 12 12:18:49 dev-t495 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=15, emitted seq=17
Nov 12 12:18:49 dev-t495 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process sddm-greeter pid 1204 thread sddm-greet:cs0 pid 1208
Nov 12 12:18:49 dev-t495 kernel: [drm] GPU recovery disabled.
Furthermore, this doesn't occur consistently: sometimes I start up my laptop and everything works fine. But a lot of other times, it won't.
The above leads me to believe there is some sort of driver problem, but I'm not sure how to proceed. Would anyone be able to help me with this? I can provide more info/logs if necessary.