After system update can't boot

Hi
After recent update system hangs (will post picture below).
I can access TTY thus the terminal under my user.
I never experienced this before.
I spend limited time using the laptop where it happened so some guidance on how to fix it quickly is appreciated.
Thanks


Moderator edit: Removed useless photo

If you can access the TTY then please show us whats going on.

Maybe start with system info?

inxi -Farz | curl -F 'file=@-' https://0x0.st

(this will produce a link with the paste)

1 Like

Please define “Manjaro DE”. Notice I’ve removed it from your topic title. We already know you’re using Manjaro, however we don’t know what DE you’re currently using.

Note that I’ve also removed your useless photo you took in portrait mode from your phone. It does not help us help you and only makes the forum storage and backups larger.

Logs, please.

1 Like

I’m using XFCE

If you can access the terminal, then you probably booted fine. There’s a decent chance your desktop manager failed to launch your compositor and desktop environment, whether it’s X11/Wayland/DE-specific configuration, GPU module related, libinput, or whatever.

The errors you probably want to see are in your journalctl logs. e.g.: journalctl -b -p3 for all the errors system wide, since your last boot.

To get more specific, the output of @cscs’s inxi command provides everyone helpful info to help troubleshoot.

He mentioned that way since you are stuck in TTY mode (with no copy/paste). If you don’t want to use that pastebin type service, you can always just: inxi -Farz > inxi.out

Then copy that inxi.out file off to somewhere where you can copy/paste.

https://0x0.st/X6Q2.txt
System:
  Kernel: 6.6.54-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: hpet
    avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=bcf193ee-4a85-4d7a-af9a-2608b263d116 rw apparmor=1 security=apparmor
    udev.log_priority=3 bootsplash.bootfile=/bootsplash-themes/manjaro/bootsplash
  Console: tty 2 DM: LightDM v: 1.32.0 Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: TOSHIBA product: Satellite L40 v: PSL48E-01T00GPT
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: TOSHIBA model: Satellite L40 v: 1.0 serial: <superuser required>
    uuid: <superuser required> BIOS: American Megatrends v: 1.50 date: 08/21/2007
Battery:
  ID-1: BAT0 charge: 13.1 Wh (99.2%) condition: 13.2/44.0 Wh (30.0%) volts: 12.2 min: 11.1
    model: TOSASU NS2P3SZPHIWR type: Li-ion serial: N/A status: not charging
CPU:
  Info: model: Intel Pentium Dual T2310 bits: 64 type: MCP arch: Core2 Merom level: v1
    built: 2006-09 process: Intel 65nm family: 6 model-id: 0xF (15) stepping: 0xD (13)
    microcode: 0xA4
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 2 smt: <unsupported> cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 1024 KiB desc: 1x1024 KiB
  Speed (MHz): avg: 798 min/max: 800/1467 scaling: driver: acpi-cpufreq governor: schedutil
    cores: 1: 798 2: 798 bogomips: 5854
  Flags: ht lm nx pae sse sse2 sse3 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not
    affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Toshiba driver: i915 v: kernel
    arch: Gen-4 process: Intel 65n built: 2006-07 ports: active: LVDS-1 empty: VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:2a02 class-ID: 0300
  Display: unspecified server: X.org v: 1.21.1.13 driver: X: loaded: vesa gpu: i915 tty: 160x50
  Monitor-1: LVDS-1 model: LG Philips 0xdd00 built: 2006 res: 1280x800 dpi: 98 gamma: 1.2
    size: 331x207mm (13.03x8.15") diag: 390mm (15.4") ratio: 16:10 modes: 1280x800
  API: OpenGL Message: GL data unavailable in console, glxinfo missing.
Audio:
  Device-1: Intel 82801H HD Audio vendor: Toshiba driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:284b class-ID: 0403
  API: ALSA v: k6.6.54-2-MANJARO status: kernel-api with: aoss type: oss-emulator
    tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.2.5 status: off tools: pw-cli
  Server-4: PulseAudio v: 17.0 status: off with: 1: pulseaudio-alsa type: plugin
    2: pulseaudio-jack type: module tools: pacat,pactl,pavucontrol
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter vendor: Toshiba driver: 8139too
    v: 0.9.28 modules: 8139cp port: c800 bus-ID: 05:07.0 chip-ID: 10ec:8139 class-ID: 0200
  IF: enp5s7 state: down mac: <filter>
  Device-2: Realtek RTL8187B Wireless Adapter driver: rtl8187 type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 3-2:2 chip-ID: 0bda:8197 class-ID: 0000 serial: <filter>
  IF: wlp0s26f7u2 state: up mac: <filter>
  Info: services: NetworkManager,wpa_supplicant
Drives:
  Local Storage: total: 111.79 GiB used: 76.17 GiB (68.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s tech: SSD serial: <filter> fw-rev: 61K1
    scheme: MBR
Partition:
  ID-1: / raw-size: 35.78 GiB size: 34.92 GiB (97.60%) used: 25.09 GiB (71.8%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes compressor: zstd
    max-pool: 20%
  ID-1: swap-1 type: partition size: 3 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4
    maj-min: 8:4
Sensors:
  System Temperatures: cpu: 52.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: 1406 pm: pacman pkgs: 1384 libs: 432 tools: pamac,yay pm: flatpak pkgs: 22
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    5: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
Info:
  Memory: total: 3 GiB available: 2.9 GiB used: 354.7 MiB (12.0%)
  Processes: 109 Power: uptime: 13m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 1.15 GiB
    Init: systemd v: 256 default: graphical tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Bash (login) v: 5.2.37 running-in: tty 2
    inxi: 3.3.36

This stands out as odd.
We dont use bootsplash anywhere do we?
Did you add this yourself?

If you dont use bootsplash then I would probably suggest to remove that option.
I honestly dont know whether the path is reasonable or not even if you do use bootsplash.

I dont know for sure, but if all of your options are in the same original place that would mean editing /etc/default/grub. ex:

sudo micro /etc/default/grub

Whether after that change or not I would suggest rebuilding your initramfs and grub.

sudo mkinitcpio -P && sudo update-grub

I am also interested in a few other possibilities.

pacdiff -o
mhwd -li -l
cat /etc/mkinitcpio.conf

(you can also send these to pastes like above)

The output of that command says:

Failed to start Light Display Manager.

Then I add to my previous asks

systemctl status lightdm
journalctl -u lightdm --since="yesterday"

(again you can send these to pastes using a pipe; | curl -F 'file=@-' https://0x0.st)

This laptop dual boots Manjaro with Zorin Lite. Zorin works fine.
I use Manjaro GRUB.
I’m sorry but I have to take picture of those commands to type them in the laptop and come back to this laptop to show the output.

Ă— lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Sat 2024-10-12 01:05:44 WEST; 36min ago
   Duration: 108ms
 Invocation: 770d82bca4fb4c8dadd2c1c2bbeb4a31
       Docs: man:lightdm(1)
    Process: 926 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
   Main PID: 926 (code=exited, status=1/FAILURE)

out 12 01:05:44 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Start request repeated too quickly.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:44 T2310 systemd[1]: Failed to start Light Display Manager.
out 12 01:05:41 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:41 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:41 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:41 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:41 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
out 12 01:05:41 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:42 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
out 12 01:05:42 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:42 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:42 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
out 12 01:05:43 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:43 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
out 12 01:05:43 T2310 systemd[1]: Starting Light Display Manager...
out 12 01:05:43 T2310 systemd[1]: Started Light Display Manager.
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
out 12 01:05:43 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Start request repeated too quickly.
out 12 01:05:44 T2310 systemd[1]: lightdm.service: Failed with result 'exit-code'.
out 12 01:05:44 T2310 systemd[1]: Failed to start Light Display Manager.

Looks like LightDM is failing…

pacdiff -o command:

/etc/pacman.conf.pacnew
/etc/makepkg.conf.d/rust.conf.pacnew
/etc/systemd/journald.conf.pacnew

mhwd -li -l command

e[1me[31m> e[mInstalled PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
            video-vesa            2017.03.12                true            PCI
     video-modesetting            2020.01.13                true            PCI


e[1me[31mWarning: e[mNo installed USB configs!
e[1me[31m> e[m0000:00:02.1 (0380:8086:2a03) Display controller Intel Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI


e[1me[31m> e[m0000:00:02.0 (0300:8086:2a02) Display controller Intel Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI

That would definitely be a problem.

sudo mhwd -r pci video-vesa
sudo mhwd -f -i pci video-linux

I wonder how it works now?

systemctl reboot

First command removed driver.
Second gave this output:

Rebooting with last command…

Ok Sir I was able to boot to DE XFCE.
Thank you very much.

Is there a problem of not removing the other driver?

[jesuslinux@T2310 ~]$ sudo mhwd -f -i pci video-linux
[sudo] password for jesuslinux: 
> Removing video-linux...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/local/pci/video-linux/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0380
Processing classid: 0302
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing libva-mesa-driver breaks dependency 'libva-mesa-driver' required by lib32-libva-mesa-driver
Error: pacman failed!
Error: script failed!

That is an error of the script.
You can remove that lib32 package before re-entering the command.
You can then optionally re-add lib32 packages associated with mesa.

I was messing this menu before all this happened:

How do I remove the package?

Yes, and installed vesa. :no_good_woman:

Remove, rerun mhwd, install the lib32 package again:

sudo pacman -R lib32-libva-mesa-driver
sudo mhwd -f -i pci video-linux
sudo pacman -Syu lib32-libva-mesa-driver

PS.
I moved the solve because the issue was vesa, so the post highlighting and removing that probably makes the most sense.

I applied your commands and all updates and rebooted and it’s BACK again!
WOW gosh!
Everything appears to be working like before.

Also I would like to publicly say a BIG THANK YOU to you Sir for taking the time to help me out.
I learned a thing or two today thanks to you :slight_smile:

Thank you very much

De nada, de rien, no worries. :slight_smile:

Glad you are back.

A little extra info:

Pretty much vesa is a very generic driver. It could be seen as a sort of fall-back at one time … though in many cases today it simply breaks gfx. And thats what happened in your case - vesa was added and then graphics failed to work properly.

2 Likes