Manjaro stopped booting

I had some issues with installing manjaro some time ago but I had gotten it figured out now, a few weeks later it stopped booting with the following error :

IMG_20180613_110628

Specs :
4.17. 02
Nvidia 1050ti laptop
Intel 8750h

Thanks already

Ray

Does the same with other kernels ? did you try with 4.14 ?

Are you able to switch to a text console (CTRL-ALT-F2) and log in?

If so, perform a full update to rule that out as an issue:

sudo pacman-mirrors -f3
sudo pacman -Syyu

You'll also be able to check on the various logs that are requested for this sort of thing.


(I resized and compressed the photo to reduce the file size from ~800KB to 13KB)

With 4.14 it runs until the login page but will get stuck after I enter the data.

After trying to load 4.14 and then trying to load 4.17 afterwards it ran through. But this will happen again. I got it to run a few times already, but I need like 10 minutes to get it it working each time.

The logs:

System:    Host: ray-laptop Kernel: 4.17.0-2-MANJARO x86_64 bits: 64 Desktop: N/A 
           Distro: Manjaro Linux 17.1.10 Hakoila 
Machine:   Type: Laptop System: Notebook product: N8xEJEK v: N/A serial: <root required> 
           Mobo: Notebook model: N8xEJEK serial: <root required> UEFI: American Megatrends v: 5.13 
           date: 04/13/2018 
Battery:   ID-1: BAT0 charge: 58.8 Wh condition: 58.8/59.9 Wh (98%) 
CPU:       6-Core: Intel Core i7-8750H type: MT MCP speed: 800 MHz min/max: 800/4100 MHz 
Graphics:  Card-1: Intel driver: i915 v: kernel 
           Card-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nouveau v: kernel 
           Display: x11 server: N/A driver: modesetting unloaded: fbdev,intel,nouveau,nv,vesa 
           resolution: <xdpyinfo missing> 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 18.1.1 
Network:   Card-1: Intel driver: iwlwifi 
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
Drives:    HDD Total Size: 232.89 GiB used: 23.37 GiB (10.0%) 
Info:      Processes: 317 Uptime: 1h 52m Memory: 15.52 GiB used: 5.16 GiB (33.3%) Shell: bash inxi: 3.0.10 

Dmesg: https://pastebin.com/r67VXjPc

Journalctl:

jun 01 04:51:10 ray-laptop kernel: Linux version 4.14.44-1-MANJARO (builduser@development) (gcc version 8.1.0 (GCC)) #1 SMP PREEMPT Fri May 25 18:35:5>
jun 01 04:51:10 ray-laptop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.14-x86_64 root=UUID=5de21949-b52f-4d7b-be5b-889d147efb45 rw quiet acpi_osi>
jun 01 04:51:10 ray-laptop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
jun 01 04:51:10 ray-laptop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
jun 01 04:51:10 ray-laptop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
jun 01 04:51:10 ray-laptop kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
jun 01 04:51:10 ray-laptop kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
jun 01 04:51:10 ray-laptop kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
jun 01 04:51:10 ray-laptop kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
jun 01 04:51:10 ray-laptop kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
jun 01 04:51:10 ray-laptop kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
jun 01 04:51:10 ray-laptop kernel: e820: BIOS-provided physical RAM map:
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000078743fff] usable
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x0000000078744000-0x000000007988afff] reserved
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x000000007988b000-0x0000000079fc2fff] usable
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x0000000079fc3000-0x000000007a106fff] ACPI NVS
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x000000007a107000-0x000000007ab43fff] reserved
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x000000007ab44000-0x000000007ac0dfff] type 20
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x000000007ac0e000-0x000000007ac0efff] usable
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x000000007ac0f000-0x000000007fffffff] reserved
jun 01 04:51:10 ray-laptop kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ray@ray-laptop sportsticker-web-client]$ journalctl -p3 -b -1
-- Logs begin at Fri 2018-06-01 04:51:10 -03, end at Wed 2018-06-13 10:10:04 -03. --
jun 13 08:11:34 ray-laptop kernel: ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
jun 13 08:11:34 ray-laptop kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170728/psparse-550)
jun 13 08:11:34 ray-laptop kernel: ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
jun 13 08:11:34 ray-laptop kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170728/psparse-550)
jun 13 08:11:34 ray-laptop kernel: ACPI Error: [_SB_.PCI0.RP13.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
jun 13 08:11:34 ray-laptop kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20170728/psparse-550)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
jun 13 08:11:34 ray-laptop kernel: tpm tpm0: TPM self test failed
jun 13 08:11:34 ray-laptop kernel: iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]
jun 13 08:11:37 ray-laptop kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 409800 [ TIMEOUT ]
jun 13 08:11:39 ray-laptop kernel: nouveau 0000:01:00.0: gr: init failed, -16
jun 13 08:11:55 ray-laptop kernel: nouveau 0000:01:00.0: i2c: aux 0008: begin idle timeout bad00100
jun 13 08:11:56 ray-laptop kernel: nouveau 0000:01:00.0: i2c: aux 0008: begin idle timeout bad00100

I tried to get to (CTRL-ALT-F2)
But it doesn't do anything.

1 Like

It appears from your dmesg logs that you're trying to use both nvidia and nouveau drivers:

[    3.262298] nvidia-nvlink: Nvlink Core is being initialized, major device number 237
[    3.262446] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[    3.262446] NVRM: This can occur when a driver such as:
               NVRM: nouveau, rivafb, nvidiafb or rivatv
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[    3.262447] NVRM: Try unloading the conflicting kernel module (and/or
               NVRM: reconfigure your kernel without the conflicting
               NVRM: driver(s)), then try loading the NVIDIA kernel module
               NVRM: again.
[    3.262447] NVRM: No NVIDIA graphics adapter probed!

To use the nvidia driver you'll have to blacklist the nouveau driver.

Did everything it said about blacklisting this but the result is the same as previously

Although the message changed slightly 152899329617270460830

Now I can't even boot to console anymore, I have to put init=/bin/bash

It gets stuck after started Accounts service

Strangely if I add quiet and 3 it boots to the console. Without quiet it doesn't.

15289987793291641770482

check in you bios
desactive secureboot ( tmp )

Can you boot into a live installer environment?

If you can, you must have made a change since installing. If you can find and undo that change it should get you up-and-running again.

Also, you should probably check the various logs again after making the change to blacklist nouveau.

Only with a livedisk I should be able to do that.
Actually, I had issues with the login since the start because of nvidia, I was able to make it working barely, before it went bad now again.
I checked the logs (dmesg etc) but I only got the above error there as well.

You have to describe what were the issues and how you fixed them.
Show us these

mhwd -li
cat /etc/X11/xorg.conf.d/*.conf
cat /etc/modules-load.d/*.conf
cat /etc/modprobe.d/*.conf
cat /etc/mkinitcpio.conf | grep -ve ^#

After installation it was stuck at the login screen, so I had to install it using this guide:


And then I upgraded the kernel to 4.17 to make it work.

After that, it worked for a while, but after a bunch of system updates, it became worse. And now it doesn't start anymore.

I will provide you the logs in a bit.

Describe please..

Describe please…: After a few times doing sudo pacman -Syu.
About the logs:

mhwd-li:

video-nvidia 2018.05.04 false PCI
No installed USB configs!

cat /etc/X11/xorg.conf.d/*.conf:

IMG_20180614_184054

cat /etc/modules-load.d/*.conf:

nvidia
nvidia-drm

cat /etc/modprobe.d/*.conf:

blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

remove nvidia modprobe -r --ignore-remove nvidia-drm nvidia-modeset=1

blacklist nouveau
blacklist ttm
blacklist drm_kms_helper
blacklist drm
options nouveau modeset=0

cat /etc/mkinitcpio.conf | grep -ve ^#

MODULES = ""
BINARIES = ()
FILES=""
HOOKS="base udev autodetect modconf block keyboard keymap filesystem fsck"

Do you know how this line is here? If not comment it out.
Also try to remove duplicates to keep configuration simple.
Make sure of the basics, as advised in other posts, disable secure boot, remember what you did.
The linked tutorial you said you followed is for bumblebee and you now have plain nvidia. Have you configured PRIME by any chance? If so, re-do that configuration.
Check if you have grub additional commands

cat /var/log/Xorg.0.log | grep vmlinuz

Thanks for the help already.

So, I tried to configure prime again using this: https://classicarchived.forum.manjaro.org/index.php?topic=31575.0

And I also remembered to disable the systemctl service bumblebeed.service.

Nonetheless, it still gets stuck with the errors I described above.

cat /var/log/Xorg.0.log | grep vmlinuz returns empty.

OK, so it looks like you've copied every possible thing from every thread into this file. :slight_smile:

All you should need to blacklist nouveau is

blacklist nouveau

Remove all of the other lines and try again.

Also it seem you installed the video-nvidia when you have

What is your desktop/DM?

inxi -Sxx

Forum kindly sponsored by