Black screen after new update

The computer boots to black screen, because of kernel 5.9, which is EOL.

I have the same problem: black screen after yesterday’s upgrade.(KDE). I need a step by step way of getting out if this. What a pain

Currently I don’t have the time to test it myself, but maybe this would help: Nvidia Drivers Not Working - #4 by bogdancovaciu

At least this is the next step, I’ll gonna try as soon as I can.

Can you post some information about your system ?
Fdsik -l, blkid, inxi -Fza, …

ystem:
Kernel: 5.10.36-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64
root=UUID=d783a58b-db39-43b8-9fa0-9e5ac4936521 rw quiet nohibernate
apparmor=1 security=apparmor
resume=UUID=a4e6a4d2-70f4-4b85-8082-35492fd4461c udev.log_priority=3
Desktop: KDE Plasma 5 tk: Qt 5.15.2 wm: kwin_x11 vt: 7 dm: LightDM 1.30.0
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: Notebook product: NL40_50CU v: N/A serial:
Chassis: type: 10 serial:
Mobo: Notebook model: NL40_50CU serial: UEFI: INSYDE v: 1.07.13
date: 10/27/2020
Battery:
ID-1: BAT0 charge: 47.7 Wh (100.0%) condition: 47.7/48.3 Wh (98.8%)
volts: 17.0 min: 15.2 model: Notebook BAT type: Li-ion serial:
status: Full
CPU:
Info: Dual Core model: Intel Core i3-10110U bits: 64 type: MT MCP
arch: Kaby Lake note: check family: 6 model-id: 8E (142) stepping: C (12)
microcode: DE cache: L2: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 20810
Speed: 800 MHz min/max: 400/4100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800
4: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds mitigation: TSX disabled
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:9b41 class-ID: 0300
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-7:4
chip-ID: 5986:9102 class-ID: 0e02
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver:
loaded: modesetting unloaded: intel alternate: fbdev,vesa display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6")
diag: 395mm (15.5")
OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 21.0.3
direct render: Yes
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS vendor: CLEVO/KAPOK
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci
bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403
Sound Server-1: ALSA v: k5.10.36-2-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.27 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 3000 bus-ID: 01:00.1
chip-ID: 10ec:8168 class-ID: 0200
IF: enp1s0f1 state: down mac:
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 3000
bus-ID: 02:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp2s0 state: up mac:
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-10:5 chip-ID: 8087:0029 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
Local Storage: total: 247.32 GiB used: 31.52 GiB (12.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M8250G
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 rotation: SSD serial: rev: S5Z42105 temp: 25.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Kingston
model: DataTraveler 3.0 size: 14.44 GiB block-size: physical: 512 B
logical: 512 B serial: rev: PMAP scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 223.79 GiB size: 219.28 GiB (97.98%)
used: 31.52 GiB (14.4%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 198 Uptime: 18m wakeups: 1 Memory: 11.4 GiB
used: 3.89 GiB (34.2%) Init: systemd v: 247 tool: systemctl Compilers:
gcc: 10.2.0 clang: 11.1.0 Packages: pacman: 1649 lib: 435 flatpak: 0
Shell: Bash v: 5.1.8 running-in: yakuake inxi: 3.3.04

Is any solution I run to this problem today. I 've used the manjaro LiveUSB I did manjaro-chroot -a and connected as a manjaro user, I’ve install linux510 with mhwd --install but I couldn’t remove linux-59 I got error can’t remove kernel. So I removed it with packman -R linux-59 but black screen continues to occur. Please any help? I’m one step before format the shit out of it and move to my old linux DistrOS, I’ve so much work to do this sh** is not what I need right now.

When I run mhwd-kernel --listinstalled I got
Currently running 5.9.16-1 -Manjaro (linux59)
but shows the following kernels are installed in your system * linux510

You can also remove the kernel manually.
Mount /boot and remove the kernel.
Then invoke update-grub.

I’m struggling here, my live version of Manjaro does not have any office applications so cannot copy from Konsole and paste into a document to transfer to working distro and paste on the forum.
Also I am unable to log into forum through live environment ‘username, email or password not recognised’ so cannot paste it in directly.
It appears that chroot only functions from a live environment so,

I have a second install of Manjaro on a separate SSD in the same computer which is what I am using right now but it hasn’t been updated in a while and I was about to delete it to free up space until this happened.
Is there a way to deal with the problem from this installation ?

You should, in theory at least, be able to chroot from such an installation, yes. I did it a few days ago. The command is the same.

Open a terminal, and run:

manjaro-chroot -a

And it should chroot into the other installation.

it says ‘command not found’

Then I’m afraid I don’t have anything else for you, except to copy everything you could possibly imagine you’d need to a seperate flash drive, like all password into text files, and so on. Then boot into the live ISO environment and go from there.

Then plug thee extra/other flash drive in, and use the data on it to access this forum with the username and password saved in the plain text file(s).

Ok, sorry. This didn’t help at all.

I’ve managed to figure out a solution forget about liveUSB and manjaro-chroot, during boot time press Cntrl + Alt + F2 login with your username/password and work with sudo and after removing old linux59 with
sudo mhwd-kernel -r linux59

then , do

sudo pacman -Syyu

sudo mhwd-kernel -i linux510
if you want you can add one more linux kernel like 511 to have. And then update-grub and reboot. I’ve tested with linux511 and worked.

If you have problems with your nvidia graphics check this:

Gpu drivers fix

The GPU drivers fix didn’t work for me either, but I’ve installed 390xx packages instead:

sudo mhwd -i pci video-nvidia-390xx

Now the computer is booting again without issues. My card is a 1060gtx, is it maybe a bit too old for the latest drivers?

Thanks for your input, I really appreciate it but I’m not sure what you mean by ‘during boot time’.
I have a multi boot system with my main system on an NVMe drive which is giving me the black screen issue.
During boot time I’m given a Grub menu with all 3 systems on, do I select the system first then Ctrl + Alt + F2 and logon ?
While I’m in the shell I cannot access my pc or the forum.

Did you try CTRL + ALT +F1 from the login screen of the shell?

I also get a black screen if I just boot up the system and have to resort to keep hitting ALT + F2 (I’m on Gnome using the Wayland Windowing System after changing from the Proprietary NVIDIA driver to the Open Source Driver in the course of the update) to get a shell login screen but once there I hit ALT + F1 which brings me to the graphical login screen and I can login successfully and everything is working fine then.

I feel obliged to comment, as I had the same problem, more or less, as the OP, and after following many threads - but especially this one, I finally managed to get back into my system normally.

After encountering the black screen, I rebooted with a live manjaro from a usb stick and started to work from chroot, as described. Just as clarkeian340 described, I could not remove my linux59-kernel, either, using mhwd-kernel from the chroot environment. This apparently (I think) also made the process of trying to get the up-to-date compatible-with-linux510-kernel nvidia-drivers fail. I finally managed to remove the superfluous linux59 with pacman instead (“pacman -R linux59” instead of “mhwd-kernel --remove linux59”) and after that, when linux510 was the only installed kernel, getting the up-to-date nvidia drivers went through without problems. And now I’m on my machine normally again. So thank you so much, Mirdarthos, for the step by step, and OP for the thread, and everyone else who chipped in! I hope this might help someone.

(Btw, I am very much a happy amateur and this is my first post here.)

As soon as you press the start button keep pressing

Ctrl + Alt +F2

till tty opens. Then use your username and password [ the username and password that you normally use when doing sudo etc].

You are very welcome! Very happy you managed!