Problem with Kernel 4.19.6 Blackscreen

[Lurgenda]

Hello everyone,

I have some trouble using the Kernel 4.19.6, I installed it using ukuu without any problems.
After the reboot i was presented a black screen (ukuu warned me about it).
What I've done after that was changiny the tty with ctrl + alt + the F-keys which worked fine.
I logged in and tried entering a command when suddenly i was greeted by my login screen.
So i ran what i found online:

Code: Select all

systemd-analyze blame

here is the output:

Code: Select all

  6.398s NetworkManager-wait-online.service
           567ms dev-sda3.device
           333ms NetworkManager.service
           281ms systemd-logind.service
           264ms virtualbox.service
           247ms systemd-journal-flush.service
           227ms systemd-resolved.service
           227ms udisks2.service
           217ms systemd-fsck@dev-disk-by\x2duuid-BCD9\x2d8607.service
           212ms ubuntu-system-adjustments.service
           190ms ModemManager.service
           181ms accounts-daemon.service
           164ms networkd-dispatcher.service
           157ms tlp.service
           150ms keyboard-setup.service
           148ms systemd-timesyncd.service
           142ms swapfile.swap
           136ms apport.service
           108ms upower.service
           106ms gpu-manager.service
           104ms systemd-modules-load.service
            96ms systemd-udev-trigger.service
            93ms lightdm.service
            92ms systemd-udevd.service
            89ms avahi-daemon.service
            88ms plymouth-quit-wait.service
            87ms grub-common.service
            77ms lvm2-monitor.service
            71ms alsa-restore.service
            71ms apparmor.service
            63ms systemd-journald.service
            59ms lm-sensors.service
            57ms speech-dispatcher.service
            53ms wpa_supplicant.service
            53ms polkit.service
            53ms rsyslog.service
            51ms systemd-tmpfiles-setup-dev.service
            48ms thermald.service
            43ms networking.service
            43ms dns-clean.service
            40ms geoclue.service
            32ms user@1000.service
            32ms packagekit.service
            31ms binfmt-support.service
            28ms setvtrgb.service
            25ms systemd-tmpfiles-clean.service
            23ms systemd-tmpfiles-setup.service
            21ms systemd-sysctl.service
            20ms plymouth-read-write.service
            19ms colord.service
            19ms plymouth-start.service
            17ms sys-kernel-debug.mount
            17ms systemd-random-seed.service
            16ms systemd-remount-fs.service
            15ms dev-mqueue.mount
            15ms hddtemp.service
            14ms blk-availability.service
            13ms boot-efi.mount
            12ms ufw.service
            11ms pppd-dns.service
            11ms kerneloops.service
            10ms proc-sys-fs-binfmt_misc.mount
            10ms systemd-update-utmp.service
             8ms systemd-user-sessions.service
             8ms dev-hugepages.mount
             6ms kmod-static-nodes.service
             6ms systemd-backlight@leds:tpacpi::kbd_backlight.service
             5ms bluetooth.service
             5ms sys-fs-fuse-connections.mount
             5ms ureadahead-stop.service
             5ms rtkit-daemon.service
             5ms systemd-update-utmp-runlevel.service
             5ms console-setup.service
             4ms systemd-backlight@backlight:intel_backlight.service
             3ms sys-kernel-config.mount
             1ms openvpn.service

what are the next steps i can do to solve my problem?
Systemspecs as follow:

Code: Select all

System:    Host: lukas-ThinkPad-X240 Kernel: 4.19.6-041906-generic x86_64
           bits: 64 gcc: 8.2.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu1)
           Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: LENOVO product: 20AMS2QD0C v: ThinkPad X240 serial: N/A
           Mobo: LENOVO model: 20AMS2QD0C v: 0B98401 PRO serial: N/A
           UEFI: LENOVO v: GIET94WW (2.44 ) date: 09/20/2018
Battery    BAT0: charge: 10.3 Wh 56.8% condition: 18.1/23.2 Wh (78%)
           model: SANYO 45N1773 status: Discharging
           BAT1: charge: 3.5 Wh 5.4% condition: 64.7/71.3 Wh (91%)
           model: SANYO 45N1777 status: N/A
CPU:       Dual core Intel Core i5-4300U (-MT-MCP-) 
           arch: Haswell rev.1 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9976
           clock speeds: max: 2900 MHz 1: 1103 MHz 2: 1024 MHz 3: 932 MHz
           4: 980 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.11hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile
           version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio:     Card-1 Intel 8 Series HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Haswell-ULT HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.19.6-041906-generic
Network:   Card-1: Intel Ethernet Connection I218-LM
           driver: e1000e v: 3.2.6-k port: 3080 bus-ID: 00:19.0
           IF: enp0s25 state: down mac: <filter>
           Card-2: Intel Wireless 7260 driver: iwlwifi bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: <filter>
Drives:    HDD Total Size: 180.0GB (28.1% used)
           ID-1: /dev/sda model: INTEL_SSDSC2BF18 size: 180.0GB temp: 0C
Partition: ID-1: / size: 165G used: 48G (31%) fs: ext4 dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 46.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 3058
Info:      Processes: 225 Uptime: 17 min Memory: 1324.2/7853.5MB
           Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56 

[Lurgenda]

So, it appears that the GUI is only starting after i login,
I do that through the TTY and immediately it starts working.

I guess there is something wrong with my boot? could it be a missing permission or something similiar?

[Moem]

That's a kernel that's not supported on Mint. Any specific reason why you installed it?

[kukamuumuka]

https://sites.google.com/site/easylinux ... almistakes

UKUU (Ubuntu Kernel Update Utility)
6.3.2. UKUU (Ubuntu Kernel Update Utility) is intended for one goal only: testing new kernels. Which is of course OK. But don't abuse it: the kernels it offers are not supported, and are not appropriate for production use.

UKUU's mainline kernels aren't reliable enough for everyday use. Furthermore: as these are pure upstream kernels (built using Ubuntu kernel configuration files), they do not include any Ubuntu/Mint-specific drivers or patches, nor any proprietary modules or restricted binary drivers.

Even if you know how to boot from an older kernel in case of kernel failure: you risk losing important work because of an unstable and unreliable kerne

[gm10]

I'm always temped to create some image memes for the Ukuu crowd, but let's stay friendly.

OP, that kernel will corrupt your filesystem. Good choice!

[KuJo]

OP, that kernel will corrupt your filesystem. Good choice!

Only if he uses an EXT4 file system. In this case, the fix for the EXT4 error (which is actually a BLK-MQ error) will be included in point release 4.19.8:
-> https://www.phoronix.com/scan.php?page= ... BLK-MQ-Fix

That's a kernel that's not supported on Mint. Any specific reason why you installed it?

The reasons can be complex.

I have e.g. until the above mentioned EXT4 error occurred and I read about it using the kernel 4.19.1 (and then changed back to the still installed 4.18.8 for security reasons).

The reason is very simple: I am a gamer with an AMD RX 580 and use the free Mesa drivers on AMDGPU, together with the Padoka PPA. And since the kernel 4.15.x the development has progressed a lot concerning the AMDGPU performance.

Another reason could be the rye-support after 4.15.x. I don't have Ryzen yet ... but it is on my wish list for the next hardware update. That's also why I would update the kernel.

Of course the kernel is not officially supported. But hey - not only the software should be open. Also in my decisions I am open.

I don't know the reasons for the OP, but I can understand why you try something like this. It's just annoying if you don't know how to help yourself ...

Translated with www.DeepL.com/Translator

[AndyMH]

I'm always temped to create some image memes for the Ukuu crowd, but let's stay friendly

Having used UKUU to install a 4.4 kernel in LM19.0 on one laptop (solve some video issues) is there a 'proper' way to install kernels, noting that update manager is only showing me 4.15 kernels on my other laptop?

PS only slight deviation from the thread topic

[gm10]

OP, that kernel will corrupt your filesystem. Good choice!

Only if he uses an EXT4 file system. In this case, the fix for the EXT4 error (which is actually a BLK-MQ error) will be included in point release 4.19.8:
-> https://www.phoronix.com/scan.php?page= ... BLK-MQ-Fix

Incorrect. The bug had nothing to do with ext4, it's in the scsi driver, and that's the one his inxi tells us he's using.

The fix to 4.19 is expected with 4.19.8 though, correct.

I'm always temped to create some image memes for the Ukuu crowd, but let's stay friendly

Having used UKUU to install a 4.4 kernel in LM19.0 on one laptop (solve some video issues) is there a 'proper' way to install kernels, noting that update manager is only showing me 4.15 kernels on my other laptop?

The problem isn't with the tool as such but with the mainline kernel ppa. 4.18 mainline brought a massive memory leak for my realtek mainstream wifi chip, 4.19 through 4.20 brought the beautiful filesystem corruption, etc., so you're riding on the wild side if you go with those. As to your old 4.4 kernel, personally I'd add the xenial-updates repo for that and install it from there, get's you Ubuntu's version along with automatic updates via Update Manager.

[KuJo]

(...) Incorrect. The bug had nothing to do with ext4, it's in the scsi driver, and that's the one his inxi tells us he's using. (...)

As i wrote it:

(...) (which is actually a BLK-MQ error) (...)

[AndyMH]

As to your old 4.4 kernel, personally I'd add the xenial-updates repo for that and install it from there,

Apologies for being dumb, how would I do that? Would it be adding the following to 'additional repositories' in software sources:

Code: Select all

deb http://us.archive.ubuntu.com/ubuntu/ xenial main restricted
deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates main restricted

[gm10]

Apologies for being dumb, how would I do that? Would it be adding the following to 'additional repositories' in software sources:

Code: Select all

deb http://us.archive.ubuntu.com/ubuntu/ xenial main restricted
deb http://us.archive.ubuntu.com/ubuntu/ xenial-updates main restricted

Yep, although you only need the second line and you can remove the restricted part, the kernels are in the main pocket.

[AndyMH]

Thanks

[KuJo]

Kernel 4.19.8 with the BLK-MQ fix is now available:
-> https://www.phoronix.com/scan.php?page= ... 8-Released

[Maxxarcade]

I actually ran into this problem, on both Ubuntu and Manjaro. I found that moving the mouse or pressing some keys will let the boot process continue.

Apparently the problem is something to do with "random-crng" or something like that? I ended up installing a package called haveged, and now the system boots right away. At least on Ubuntu 18.10 and 4.19.9.

I haven't been using Mint lately because the 4.15 kernel is too old for my Ryzen 2400G system. But if I can get it to be stable after upgrading with Ukuu, I'd love to go back. Especially with 19.1 around the corner. Mint has always been my favorite distro.