Manjaro will only boot with fallback-initramfs. not even LTS kernel works

Since few stable updates ago, manjaro won’t boot with first grub option.

It reached grub screen, after I selected first entry, it just goes blank. And I disabled my silent boot, usually there is text, but there were no text. The screen is lit up but blank (black).

To boot to the system I need to select the fallback initramfs option. The second one.

I am not sure if this related but other thing that changed is that now I cannot run waifu2x-ncnn-vulkan
It says

vkEnumeratePhysicalDevices failed -3
invalid gpu device

Usually I can, I used that command quite often. It’s from aur and it’s up to date.

I did stable update to the now latest and problem still happening. Earlier I though the problem was magically fixed but turns out it just grub remembering the last entry I picked.

Output of mkinitcpio -P (I forgot where I read about this command but I think there is forum post that tell to do this.)

==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'default'
  -> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64.img
==> ERROR: '/lib/modules/5.7.19-2-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'fallback'
  -> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64-fallback.img -S autodetect
==> ERROR: '/lib/modules/5.7.19-2-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
  -> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: '/lib/modules/5.8.18-1-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
  -> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> ERROR: '/lib/modules/5.8.18-1-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'default'
  -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img
==> Starting build: 5.9.10-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'fallback'
  -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect
==> Starting build: 5.9.10-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64-fallback.img
==> Image generation successful
OS: Manjaro Linux x86_64 
Host: X456UQ 1.0 
Kernel: 5.9.11-3-MANJARO 
Shell: bash 5.0.18 
DE: GNOME 3.38.1 
CPU: Intel i5-6200U (4) @ 2.800GHz 
GPU: Intel Skylake GT2 [HD Graphics 520] 
GPU: NVIDIA GeForce 940MX 
Memory: 6292MiB / 19917MiB

The gpu driver I am using is the propietary one. video-hybrid-intel-nvidia-440xx-prime

I am not sure what to do from here.

Sorry about the sentence if it’s hard to read, my brain is not doing well at the moment.

see this for kernels

1 Like

I’m sorry, after reading that post, I don’t quite understand the relation of that with my problem and what am I supposed to do.
My grub shows like normal. All the manjaro and windows entry are there. The problem doesn’t appear because of windows update but manjaro stable update. (I haven’t used windows back then).

The problem is I cannot boot to regular manjaro entry. I need to select the initramfs (second option in advanced mode grub entry).
Hmm… maybe I should just use manjaro LTS version if that could make it easier for me.

Another thing I just found out. I cannot run prime-run anymore. Maybe it has something to do with nvidia?. I forgot the output, I have uninstalled my manjaro (currently reinstalling, who knows it might magically work)

see in previous link about file preset
how many file preset
and

sudo mhwd-kernel -li

numbers kernels and file preset must match

check also if you have a file /etc/mkinitcpio.conf.pacnew

in this case

sudo diff -y /etc/mkinitcpio.conf /etc/mkinitcpio.conf.pacnew
1 Like

I just reinstalled. And it magically fixed at first, I can run prime-run with first boot entry. But then I start installing packages and the next day I cannot boot to my first boot entry anymore.
I need to select fallback-initramfs, again. Same effect. blank after selecting first grub entry.

Is it file inside /etc/mkinitcpio.d/ ? There is only one: linux59.preset
I still don’t understand what happened in the other post though.

sudo mhwd-kernel -li                              Min 06 Des 2020 07:33:29 
[sudo] password for ifrit: 
Currently running: 5.9.11-3-MANJARO (linux59)
The following kernels are installed in your system:
   * linux59

I think it match. There is only one in both.

No, there is not. Maybe it’s because I do fresh reinstall?


being a fresh install now the nvidia driver is using the video-hybrid-intel-nvidia-455xx-prime one.
Not sure if that is relevant.

I’ll install LTS kernel now. I’ll just mark it as solved as long as it works.

i think is version hibrid-nvida drivers
only version 450xx and 455xx series works with linux59

alright I just finished installing LTS kernel. I tried to boot with regular linux54 (non fallback initramfs) the problem is still there.
So… looks like it’s not the kernel.

sudo journalctl -b                                                                                                                                  49.1s  Min 06 Des 2020 09:22:25 
-- Logs begin at Sun 2020-12-06 02:29:20 WIB, end at Sun 2020-12-06 16:22:29 WIB. --
Des 06 16:02:07 manjaro kernel: Linux version 5.9.11-3-MANJARO (builduser@development) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP PREEMPT Sat Nov 28 09:08:57 UTC 2020
Des 06 16:02:07 manjaro kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.9-x86_64 root=UUID=d72dfe86-a3cc-40e7-bd2b-2b3a8d00862e rw quiet splash apparmor=1 security=apparmor udev.log_priori>
Des 06 16:02:07 manjaro kernel: KERNEL supported cpus:
Des 06 16:02:07 manjaro kernel:   Intel GenuineIntel
Des 06 16:02:07 manjaro kernel:   AMD AuthenticAMD
Des 06 16:02:07 manjaro kernel:   Hygon HygonGenuine
Des 06 16:02:07 manjaro kernel:   Centaur CentaurHauls
Des 06 16:02:07 manjaro kernel:   zhaoxin   Shanghai  
Des 06 16:02:07 manjaro kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Des 06 16:02:07 manjaro kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Des 06 16:02:07 manjaro kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Des 06 16:02:07 manjaro kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Des 06 16:02:07 manjaro kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Des 06 16:02:07 manjaro kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Des 06 16:02:07 manjaro kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Des 06 16:02:07 manjaro kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Des 06 16:02:07 manjaro kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Des 06 16:02:07 manjaro kernel: BIOS-provided physical RAM map:
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000071dc9fff] usable
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000071dca000-0x0000000071dcafff] ACPI NVS
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000071dcb000-0x0000000071df4fff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000071df5000-0x000000007520dfff] usable
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x000000007520e000-0x0000000075eedfff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000075eee000-0x0000000076586fff] usable
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000076587000-0x0000000077126fff] ACPI NVS
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000077127000-0x0000000077f87fff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000077f88000-0x0000000077ffdfff] type 20
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000077ffe000-0x0000000077ffefff] usable
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000078000000-0x00000000780fffff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Des 06 16:02:07 manjaro kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000583ffffff] usable
Des 06 16:02:07 manjaro kernel: NX (Execute Disable) protection: active
Des 06 16:02:07 manjaro kernel: efi: EFI v2.40 by American Megatrends
Des 06 16:02:07 manjaro kernel: efi: ESRT=0x77ec7e18 ACPI=0x7668b000 ACPI 2.0=0x7668b000 SMBIOS=0x776e1000 SMBIOS 3.0=0x776e0000 
Des 06 16:02:07 manjaro kernel: SMBIOS 3.0.0 present.
Des 06 16:02:07 manjaro kernel: DMI: ASUSTeK COMPUTER INC. X456UQ/X456UQ, BIOS X456UQ.202 02/15/2016
Des 06 16:02:07 manjaro kernel: tsc: Detected 2400.000 MHz processor
Des 06 16:02:07 manjaro kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Des 06 16:02:07 manjaro kernel: e820: remove [mem 0x000a0000-0x000fffff] usable

but now I can use my nvidia gpu even if I boot using fallback-initramfs on linux59 so I guess that’s fine with me. For now.

can you provide

inxi -Mxa

have you updated EFI Bios ?

 ~  inxi -Mxa                                                       Min 06 Des 2020 09:45:43 
Machine:   Type: Laptop System: ASUSTeK product: X456UQ v: 1.0 
           serial: <superuser/root required> 
           Mobo: ASUSTeK model: X456UQ v: 1.0 serial: <superuser/root required> 
           UEFI: American Megatrends v: X456UQ.202 date: 02/15/2016 

eh… no no, I never updated bios ever since I bought this laptop. Which around 6 years ago

Did you manage to resolve this?
My laptop (ASUS UX305C) only boots occasionally on the default grub option (kernel 5.4 and on 5.10). If I enter grub and select backup-initramfs it boots every time. While that is a good workaround, I’d like to get it fixed.
Thanks!

As of today, this problem is still present. I really don’t know what caused it and where to start.

Mine is ASUS too
X456UQ

Maybe it’s the bios like Mr Stephane mentioned, I looked for how to update it but I searched X456UQ (or just using keyword 456) in ASUS download Center and it does not exist.

This seems to be the relevant BIOS for your laptop: hxxps://www.asus.com/supportonly/X456UQ/HelpDesk_BIOS/. (I’m not allowed to include links yet, I think)

I actually managed to resolve my issues!
I updated my BIOS to the latest version. This did not resolve the issues, and booting would still be hit or miss.
However, something new had arisen. After the upgrade, I would get a warning on every boot:

Secure Boot Violation

Invalid signature detected. Check Secure Boot Policy in Setup.

[OK]

I quickly researched what secure boot is/does, and decided to disable it. After that, no more issues and it boots straight to the login screen every time!
So I don’t think the BIOS update resolved it but that secure boot was giving me issues, as I know for a fact that it was turned on before the update, too.

That is not to say I won’t advise you to update your BIOS, running the latest version is always a good idea!