After updating the system I was prompted for a reboot. Upon reboot loading Manjaro gets stuck at loadkmap: short read
This is on a second PC system I have, and my main system also runs Manjaro. Kinda concerned about updating that now and having two systems down. Both are running KDE Plasma. Any clues to solving it would be much appreciated
EOL kernel maybe?
We can only guess without more information.
That shouldnāt be the case as itās certainly not an older kernel. What more information do you need? It was fine before updating
Maybe the logs from the failed start?
Or just a inxi -Farz for system info.
OK Iāll try the various function keys and try to get to terminal. Might be fun trying to get results of inxi -Farz from one computer to this one Iām communicating on. Iāll be honestā¦ Iām well out my depth even though Iāve used Manjaro for years. I just donāt break it and use the GUI mostly. Been rock solid till now.
This may be helpful.
No joy getting a terminal via any function key. F4 brings up Grub menu with fallback initramfs etc. Choosing to boot Manjaro UEFI or not or fall back results in same.
Anything else there only allows command line access to editing grub.
Thereās a couple of other clues as to what could be part of the problem perhaps?
When I mentioned āloadkmap: short readā the only time I see that ābrieflyā is from turning the monitor off and on otherwise itās black and no display.
Now, going through all the function keys one by one all except F4 displays the boot process line by line and where it stopsā¦ More often than not itās halting on CUPS Scheduler. Iām aware of the latest security vulnerability with regards to CUPS. Has Manjaro initiated a patch or fix in the latest updates? Seems strangely coincidental.
TTY is only one approach to gaining interactivity and assumes something or other boots.
I would suggest runlevel 3 as it does not require gfx.
I have a similar problem. After update, sddm wonāt start. systemctl status sddm reveals failed to read display number from pipe. Running startplasma-wayland brings desktop, but nvidia drivers are not available. I there a config file I can alter to get my machine running as before update?
EOL kernel?
Unsupported packages?
Incomplete upgrade?
We dont know without information.
See above.
No.
If you used something like btrfs+timemachine and ran automatic backups ā¦ then ā¦ you could boot into that. Otherwise you should gain control somehow (see above), and if you dont know what else to do ā¦ then share information on the system. Possibly beginning with inxi -Farz.
I eventually got into TTY via CTL ALT F3
Still not sure how to grab all the output from inxi -Farz and send it to one of those links in the guide via command line. Iām going to stop for now lest I really stuff something up. I pulled an all nighter gaming and havenāt slept yet, so Iāll stop for now. Thanks for your help so far itās appreciated. Iāll come back to it with a fresh mind.
Iām trying to post the contents of inxi -Farz but it says āsorry canāt include links in your postā
inxi -Farz | curl -F 'file=@-' https://0x0.st
And we get a link. And so on.
This is due to forum security.
Just quote or enclose it in tics or similar.
`www.link.com`
System:
Kernel: 6.9.12-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.9-x86_64
root=UUID=5dc1effe-7e1f-4ade-8bdc-9eb68119cb97 rw quiet splash
udev.log_priority=3 intel_iommu=on iommu=pt
Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.5.0
wm: kwin_wayland vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop System: Micro product: G444 v: 1.0
serial: <superuser required>
Mobo: Micro-Star model: PRO Z690-A WIFI DDR4(MS-7D25) v: 1.0
serial: <superuser required> part-nu: 561183 uuid: <superuser required>
UEFI: American Megatrends LLC. v: 1.M9 date: 03/03/2023
CPU:
Info: model: 12th Gen Intel Core i7-12700KF bits: 64 type: MST AMCP
arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 2
microcode: 0x36
Topology: cpus: 1x dies: 1 clusters: 9 cores: 12 threads: 20 mt: 8 tpc: 2
st: 4 smt: enabled cache: L1: 1024 KiB desc: d-4x32 KiB, 8x48 KiB; i-8x32
KiB, 4x64 KiB L2: 12 MiB desc: 8x1.2 MiB, 1x2 MiB L3: 25 MiB
desc: 1x25 MiB
Speed (MHz): avg: 800 min/max: 800/4900:5000:3800 scaling:
driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 bogomips: 144440
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling mitigation: Clear Register File
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
conditional; RSB filling; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070] vendor: Micro-Star MSI driver: N/A
alternate: nouveau non-free: 550.xx+ status: current (as of 2024-09)
arch: Lovelace code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2786
class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: N/A failed: nvidia gpu: N/A
display-ID: 0
Monitor-1: Unknown-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
wayland: drv: swrast x11: drv: swrast inactive: gbm
API: OpenGL v: 4.5 vendor: mesa v: 24.2.2-arch1.1 glx-v: 1.4
direct-render: yes renderer: llvmpipe (LLVM 18.1.8 256 bits)
device-ID: ffffffff:ffffffff memory: 30.47 GiB unified: yes
display-ID: :0.0
API: Vulkan Message: No Vulkan data available.
Audio:
Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
Device-2: NVIDIA AD104 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:22bc class-ID: 0403
API: ALSA v: k6.9.12-3-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7af0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Micro-Star MSI driver: igc
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 04:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Info: services: NetworkManager, smbd, sshd, systemd-timesyncd
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:6 chip-ID: 8087:0033
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 1.82 TiB used: 276.13 GiB (14.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD Blue SN570 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 234110WD temp: 35.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD Blue SA510
2.5 1000GB size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 8100 scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 915.53 GiB (98.32%)
used: 100.5 GiB (11.0%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 931.51 GiB size: 915.82 GiB (98.32%)
used: 175.63 GiB (19.2%) fs: ext4 dev: /dev/sda1 maj-min: 8:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 46.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: 1681 pm: pacman pkgs: 1659 libs: 446 tools: pamac,yay pm: flatpak
pkgs: 22
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: http://mirror.fcix.net/manjaro/stable/$repo/$arch
2: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
3: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
4: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
5: https://mirror.funami.tech/manjaro/stable/$repo/$arch
Info:
Memory: total: 32 GiB available: 31.2 GiB used: 3.46 GiB (11.1%)
Processes: 359 Power: uptime: 38m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 13 Shell: Zsh v: 5.9
default: Bash v: 5.2.32 running-in: konsole inxi: 3.3.36
It would have been better to just share the link.
Or in the case of code then use the </> button on the forum or enclose the whole thing like
```
Code and stuff
```
Ill fix it this time 
ā¦ And as I suspected at least on obvious thing wrong is that kernel 6.9 is EOL, dead, gone, no longer exists in the repositories, and is unsupported.
You should endeavor to install and boot into a supported kernel like 6.6 or 6.10, and remove 6.9.
Iām sure this was compounded by your nvidia drivers as ā¦ there would not be the correct modules/packages for 6.9 ā¦ which also begs the question ā¦ how did your upgrade complete? Did it actually complete? Did you pull AUR packages?
The update completed with a notice to reboot. Upon rebooting, sddm did not start. I was not aware that 6.9 was deprecated until this thread. I would think that an update from the system would have taken that into account. I now have to go through and remove and install a kernel, somehow install nvidia drivers compatible with that kernel, and hope everything somehow works. Iāll keep you posted.
sudo mhwd-kernel -i linux66
sudo mhwd-kernel -i linux610
OR
sudo pacman -S linux66 linux610
When you boot into a new kernel you will want to remove 69
If you have problems you might have to manually remove something like
sudo pacman -Rns linux69-nvidia
and/or
sudo pacman -Rns $(pacman -Qsq linux69)
Anyways ā¦ with 69 removed and running a supported kernel then you can reinstall your drivers to be sureā¦
sudo mhwd -f -i pci video-nvidia
Who knows maybe a mirror sort and update
sudo pacman-mirrors --continent && sudo pacman -Syu
The system did what you told it to do.
I dont know why you were running 6.9.
I dont know if you have some sort of notifier for those things.
I dont know what the output was from the package manager during your upgrade.
Every other example of people having 6.9 encountered obvious errors and stopped.
Besides which its been echoed all over the forum for months. It was deprecated on all other branches for a long time, and obviously on kernel.org since before it was removed here.
Ok, this is what happened:
When there is a kernel EOL and got removed a different kernel should have been on the system. We will look into a solution which would automatically install needed kernels if a running kernel got removed. We might also check to prevent any updates in that case until a supported kernel is installed.
So this can fix the issue:
sudo mhwd -i linux66
sudo pacman -S linux66-nvidia
sudo mhwd -i linux610
sudo pacman -S linux610-nvidia
See also here: NVIDIA driver update broke NVIDIA drivers?
6.9 kernel was the default kernel of 24.0 ISOs. Not all users maintain their kernels, they simply update and expect the system to run. So we might reintroduce some like linux-latest we had before, so EOL kernels get automatically removed and replaced via pacman.
Thank you. Due being able to grab that inxi -Farz output to a text file I noted the same problem Kwall has, ie the 6.9 kernel.
A combination of the commands both you and philm posted allowed me to eventually get to the desktop and fix the rest. Again, thank you for the time and patience.