Installed updates -> reboot -> black screen

Support System Updates
1

Hello,

Yesterday I installed the latest updates and then it prompted me to reboot. After the reboot I typed in the passphrase to unlock my encrypted drive, slot 0 is opened, and then nothing happens.

Pressing Ctrl-Alt-Delete works, but that just gets me into this reboot loop.

I have dug up my old USB-stick with my old Manjaro installer and booted through that and in a terminal I did the following command:

[manjaro@manjaro ~]$ inxi --filter --verbosity=8
System:
  Kernel: 5.9.16-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us 
  tz=UTC misobasedir=manjaro misolabel=MANJARO_KDE_2021 quiet 
  systemd.show_status=1 apparmor=1 security=apparmor driver=free 
  nouveau.modeset=1 i915.modeset=1 radeon.modeset=1 
  Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: Acer model: Predator G5920 serial: <filter> 
  BIOS: American Megatrends v: P11-A0 date: 08/31/2012 
Memory:
  RAM: total: 15.6 GiB used: 1.62 GiB (10.4%) 
  RAM Report: 
  permissions: Unable to run dmidecode. Root privileges required. 
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: Quad Core model: Intel Core i7-3770K bits: 64 type: MT MCP 
  arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21 
  L2 cache: 8 MiB bogomips: 55898 
  Speed: 1597 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 1597 
  2: 1596 3: 1597 4: 1597 5: 1599 6: 1596 7: 1597 8: 2365 
  Flags: acpi aperfmperf apic arat arch_perfmon avx bts clflush cmov 
  constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts 
  epb ept erms est f16c flexpriority flush_l1d fpu fsgsbase fxsr ht ibpb 
  ibrs ida lahf_lm lm mca mce md_clear mmx monitor msr mtrr nonstop_tsc 
  nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni popcnt pse 
  pse36 pti pts rdrand rdtscp rep_good sep smep ss ssbd sse sse2 sse4_1 
  sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_deadline_timer 
  vme vmx vnmi vpid xsave xsaveopt xtopology xtpr 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, 
  SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  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: Full generic retpoline, IBPB: 
  conditional, IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ASUSTeK 
  driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:13c2 
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 
  driver: nouveau unloaded: modesetting alternate: fbdev,nv,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: DVI-D-1 res: 1920x1080 hz: 60 dpi: 82 
  size: 598x336mm (23.5x13.2") diag: 686mm (27") 
  OpenGL: renderer: NV124 v: 4.3 Mesa 20.3.1 direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:1e20 
  Device-2: NVIDIA GM204 High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fbb 
  Sound Server: ALSA v: k5.9.16-1-MANJARO 
Network:
  Device-1: Intel 82579V Gigabit Network vendor: Acer Incorporated ALI 
  driver: e1000e v: kernel port: f040 bus ID: 00:19.0 chip ID: 8086:1503 
  IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: dynamic noprefixroute scope: global 
  IP v6: <filter> type: noprefixroute scope: link 
  WAN IP: <filter> 
Logical:
  Message: No LVM data was found. 
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 
  port: f020 bus ID: 00:1f.2 chip ID: 8086.2822 rev: 04 
Drives:
  Local Storage: total: 247.4 GiB used: 172.2 MiB (0.1%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB 
  size: 232.89 GiB block size: physical: 512 B logical: 512 B 
  speed: 6.0 Gb/s serial: <filter> rev: 1B6Q 
  ID-2: /dev/sdb maj-min: 8:16 type: USB model: USB Disk 2.0 
  size: 14.51 GiB block size: physical: 512 B logical: 512 B 
  serial: <filter> rev: 2.00 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
  Optical-1: /dev/sr0 vendor: ATAPI model: DVD A DH16ACSH rev: JA11 
  dev-links: cdrom 
  Features: speed: 48 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
Partition:
  ID-1: / raw size: N/A size: 11.7 GiB used: 172.2 MiB (1.4%) 
  fs: overlay source: ERR-102 label: N/A uuid: N/A 
Swap:
  Alert: No Swap data was found. 
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 300 MiB fs: vfat label: N/A 
  uuid: EED5-364A 
  ID-2: /dev/sdb1 maj-min: 8:17 size: 3 GiB fs: iso9660 
  label: MANJARO_KDE_2021 uuid: 2021-01-03-09-07-36-00 
  ID-3: /dev/sdb2 maj-min: 8:18 size: 4 MiB fs: vfat label: MISO_EFI 
  uuid: 7B2D-7571 
USB:
  Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip ID: 1d6b:0002 
  Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip ID: 8087:0024 
  Device-1: 1-1.3:3 info: Logitech USB Keyboard type: Keyboard,HID 
  driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s 
  chip ID: 046d:c34b 
  Device-2: 1-1.4:4 info: Logitech M105 Optical Mouse type: Mouse 
  driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s 
  chip ID: 046d:c077 
  Device-3: 1-1.5:5 info: Realtek USB2.0-CRW type: Mass Storage 
  driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s 
  chip ID: 0bda:0181 serial: <filter> 
  Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 
  speed: 480 Mb/s chip ID: 1d6b:0002 
  Device-1: 2-3:2 info: USB Disk 2.0 type: Mass Storage 
  driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s 
  chip ID: 23a5:5786 serial: <filter> 
  Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip ID: 1d6b:0002 
  Hub: 3-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 
  speed: 480 Mb/s chip ID: 8087:0024 
  Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 
  speed: 5 Gb/s chip ID: 1d6b:0003 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau 
  temp: 56.0 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0 
Repos:
  Packages: pacman: 1264 lib: 375 flatpak: 0 
  Active pacman repo servers in: /etc/pacman.d/mirrorlist 
  1: https://mirrors.shuosc.org/manjaro/stable/$repo/$arch
  2: http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
  3: http://mirror.rise.ph/manjaro/stable/$repo/$arch
  4: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
  5: http://pet.inf.ufsc.br/mirrors/manjarolinux/stable/$repo/$arch
  6: https://mirror.cedia.org.ec/manjaro/stable/$repo/$arch
  7: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
  8: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
  9: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
  10: https://manjaro.cu.be/stable/$repo/$arch
  11: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
  12: https://mirrors.sjtug.sjtu.edu.cn/manjarostable/$repo/$arch
  13: http://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
  14: https://mirrors.netix.net/manjaro/stable/$repo/$arch
  15: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
  16: http://mirror.dacentec.com/manjaro/stable/$repo/$arch
  17: https://mirror.philpot.de/manjaro/stable/$repo/$arch
  18: http://mirror.chmuri.net/manjaro/stable/$repo/$arch
  19: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
  20: https://mirror.tuchola-dc.pl/manjaro/stable/$repo/$arch
  21: http://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
  22: http://manjaro.dcc.uchile.cl/stable/$repo/$arch
  23: http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
  24: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
  25: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
  26: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
  27: http://mirror.catn.com/pub/manjaro/stable/$repo/$arch
  28: http://distro.ibiblio.org/manjaro/stable/$repo/$arch
  29: http://ftp.caliu.cat/manjaro/stable/$repo/$arch
  30: http://ftp.linux.org.tr/manjaro/stable/$repo/$arch
  31: http://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
  32: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
  33: http://mirror.inode.at/manjaro/stable/$repo/$arch
  34: https://mirror.zetup.net/manjaro/stable/$repo/$arch
  35: https://manjaro.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
  36: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
  37: http://free.nchc.org.tw/manjaro/stable/$repo/$arch
  38: http://manjaro.melbourneitmirror.net/stable/$repo/$arch
  39: http://repo.manjaro.org.uk/stable/$repo/$arch
  40: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
  41: http://manjaro.mirror.ac.za/stable/$repo/$arch
  42: http://kibo.remi.lu/stable/$repo/$arch
  43: http://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
  44: http://mirror.ragenetwork.de/manjaro/stable/$repo/$arch
  45: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
  46: https://mirror.netzspielplatz.de/manjaro/packages/stable/$repo/$arch
  47: http://mirrors.serverhost.ro/manjaro/packages/stable/$repo/$arch
  48: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
  49: http://ftp.riken.jp/Linux/manjaro/stable/$repo/$arch
  50: http://mirror.infotronik.hu/mirrors/pub/manjaro/stable/$repo/$arch
  51: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
  52: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
  53: http://mirror.ventraip.net.au/Manjaro/stable/$repo/$arch
  54: https://osmirror.org/manjaro/stable/$repo/$arch
  55: http://ftp.cuhk.edu.hk/pub/Linux/manjaro/stable/$repo/$arch
  56: https://mirror.espoch.edu.ec/manjaro/stable/$repo/$arch
  57: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
  58: http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
  59: https://repo.sadjad.ac.ir/manjaro/stable/$repo/$arch
  60: https://manjaro.moson.eu/stable/$repo/$arch
  61: http://manjaro.telecoms.bg/stable/$repo/$arch
  62: https://mirrors.shu.edu.cn/manjaro/stable/$repo/$arch
  63: https://download.nus.edu.sg/mirror/manjaro/stable/$repo/$arch
  64: http://ftp.belnet.be/mirrors/manjaro/stable/$repo/$arch
  65: http://mirror.xeonbd.com/manjaro/stable/$repo/$arch
  66: http://linorg.usp.br/manjaro/stable/$repo/$arch
  67: http://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
  68: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
  69: https://mirror.koddos.net/manjaro/stable/$repo/$arch
  70: https://www.uex.dk/public/manjaro/stable/$repo/$arch
  71: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
  72: https://mirror.clarkson.edu/manjaro/stable/$repo/$arch
  73: http://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
  74: http://manjaro.barata.pt/stable/$repo/$arch
  75: http://mirror.upb.edu.co/manjarostable/$repo/$arch
  76: https://repo.rhindon.net/manjaro/stable/$repo/$arch
  77: http://kambing.ui.ac.id/manjaro/stable/$repo/$arch
  78: https://mirrors.zju.edu.cn/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 232 
  1: cpu: 9.5% command: firefox pid: 1845 mem: 322.1 MiB (2.0%) 
  2: cpu: 4.5% command: xorg pid: 1185 mem: 68.9 MiB (0.4%) 
  3: cpu: 3.5% command: firefox pid: 2067 mem: 179.8 MiB (1.1%) 
  4: cpu: 1.9% command: kwin_x11 pid: 1345 mem: 127.1 MiB (0.7%) 
  5: cpu: 1.4% command: konsole pid: 3274 mem: 99.5 MiB (0.6%) 
  Memory top: 5 of 232 
  1: mem: 322.1 MiB (2.0%) command: firefox pid: 1845 cpu: 9.5% 
  2: mem: 232.1 MiB (1.4%) command: plasmashell pid: 1515 cpu: 0.9% 
  3: mem: 179.8 MiB (1.1%) command: firefox pid: 2067 cpu: 3.5% 
  4: mem: 147.5 MiB (0.9%) command: firefox pid: 1991 cpu: 0.1% 
  5: mem: 143.0 MiB (0.8%) command: firefox pid: 2133 cpu: 0.1% 
Info:
  Processes: 232 Uptime: 15m wakeups: 0 Init: systemd v: 247 Compilers: 
  gcc: N/A Shell: Bash v: 5.1.0 running in: konsole inxi: 3.2.01

I hope this is helpful for fixing my issue…

What else do I need to now to solve this problem of mine?

1 Like
2

Nvidia driver happened. If you were using the previous rolling driver at 580xx then your GPU went from supported to unsupported.

You will need unlock and mount your luks partition, then enter a chroot environment

→ [root tip] [recovery] Basic Manjaro Linux Rescue and Recovery

Run the script to get a hint of what driver Nvidia recommends

nvidia-driver-assistant
2 Likes
4

I think that is the old ISO the system is booted from - and thus not really relevant for the system inside the luks container.

The hardware info is relevant - but software is irrelevant.

1 Like
8

Couldn’t some script have been made, which checks the NVidia driver and when the driver is one of the old ones: prevent a layman like me from installing this fatal update? Sigh… I know hindsight is 20/20, but this oversight is causing a lot of problems.

Yesterday-me decided to postpone the rescue & recovery and made it a tomorrow-problem. Now it is tomorrow for me and I am cursing yesterday-me, because when I start up the pc with the old USB-stick plugged in the following error message appears:

error: failure reading sector 0x0 from ‘hd0’.

Looks like I have to flash a new USB-stick after all… :enraged_face:

Have the new ISOs for installation of the required Manjaro XFCE build been published yet? Or will any XFCE build work on my older aged desktop PC system?

9

I sorry for the inconvenience - we have made the possible inconvenience a part of several announcements at least on testing and stable branch.

Yes - see Announcements > Releases

1 Like
10

For consideration:

1 Like
11

Okay I burned a Ventoy USB and this is an amazing application. I experimented a bit and tried to remove an ISO file from the Ventoy USB stick, however, it did not give back the free space unfortunately, so it is still kind of an one time thing only, but it will save some USB sticks being wasted nonetheless, which I really appreciate.

Anyway, I tried to boot with the Ventoy USB stick, but I got the exact same behavior from my good old faithful desktop computer as with the old Manjaro KDE stick. This took days for me to figure out, but turns out the old desktop BIOS didn’t perceive the USB-sticks as removable devices, and the BIOS detected them as hard-drives instead! :sweat_smile:

Once I made that discovery I could set the priorities correctly (which resets to default setting after shutdown, hence why I couldn’t figure it out what went wrong), and the USB-sticks were working fine even the old Manjaro KDE one.

I tried following @linux-aarhus advise:

However, I got stuck at the command:

luksOpen $root cryptroot

The error message I received was:

Device /dev/sda2 does not exist or access denied.

So tried to access the desktop’s main hard-drive through the Thunar file manager and there it was possible to use my passphrase to get access. Backed up all my files and folders and I guess I am going to reinstall my operating system now, starting with a new clean slate so to say.

I have used Manjaro for years now and I have never read any announcements before applying an update, since I am not that much of a forumdweller and thus far it went always fine over the years, because I thought Manjaro was the foolproof Arch Linux for laymen gamers like me. Still my thanks for all the support on this forum, it is really fast in replies and during this journey I learned a couple of lessons & things too, which I really appreciate as well, thank you. :grin:

1 Like
12

I was wrong, it does give space back! I just had to unplug & insert the Ventoy USB stick back in to update the free space available, so it isn’t a one time only thing at all, this is fantastic! :smiley:

2 Likes
13

A well-maintained system can usually avoid many issues, but – sooner or later – an issue reveals itself that can only be dealt with by the system administrator (you) taking action.

You don’t frequent the forum much – that’s fine – however, monitoring the Update Announcements are nonetheless important and can make all the difference between a smooth or broken experience.

Do you have a Feed Reader application of some kind?

If you use Thunderbird for email, you already have that capability, otherwise there are several dedicated applications available.

The reason I ask is that many categories in the Manjaro forum can be converted to a feed reader friendly link simply by adding .rss to the end of the URL.

For example;
the link to the Stable Update Announcements index page:

  • https://forum.manjaro.org/c/announcements/stable-updates/12.rss

Drop that into (most) feed readers available, and it should notify you of the update when it’s available, and you can visit the page directly.

We all wasted many USB disks before something like Ventoy became available – it’s quite unique.

I use a 256 GB USB for Ventoy; large enough to store many ISOs as well as run NomadBSD from a separate partition (it took some trickery).

Regards.

1 Like
14

Make sure you do a sync first! :wink: … this makes sure all data is written before you unplug the device.

1 Like