Manjaro fails to boot (Nvidia hybrid)

Dear Manjaro Community,

I have Manjaro 24.0.5 installed, w/o proprietary drivers, on an ASUS N552VW (Geforce GTX 960M + Intel HD Graphics 530), but Manjaro shows me a black screen after boot (it only boots successfully via fallback).

in fallback mode, unfortunately journalctl doesn’t capture the failed boots.

I need to add that, this seems to be a universal Linux problem, I have already, tested, Ubuntu 22.04 and 24.04, Fedora 40 and now Manjaro, and pretty much get the same behavior.

I have already filled a bug, on Ubuntu:

But, the same issue happens on Ubuntu as well and journalctl fails to log failed boots needed to diagnose the issue.

I also tested removing “quiet splash” boot parameters, but it didn’t work.

Hi @xashyar,

As I have it, if it boots with the fallback image and not the standard one, it’s because the standard one has a kernel module missing.

I highly doubt if this’ll be any different, but you might be able to see from a chroot environment.

How to chroot

  1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

  2. Write/copy/dd the ISO to a USB thumb drive.

  3. When done, boot with the above mentioned USB thumb drive into the live environment.

  4. Once booted, open a terminal and enter the following command to enter the chroot environment:

manjaro-chroot -a
  1. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

When in the chroot environment, you should be able to get logs. If there aren’t, then it didn’t boot far enough to start the logging, and then I don’t know what to do. But check the logs first:

Finding errors for specific boot

journalctl --priority=warning..crit --no-pager --boot=-1

Where:

  • The --priority=warning..err argument limits the output to warnings and errors only;
  • and the --no-pager formats the output nicely for use here, on the forum;
  • the --boot=-1 argument limits the output to log messages from the previous boot. This can be adjusted to -2 for the boot before that, -3 to the boot before that, and so on and so forth.

:bangbang: Tip :bangbang:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:


:bangbang::bangbang: Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

1 Like

Have you checked how kms (kernel mode setting) has been configured ?

I had a ThinkPad T550 with - as I recall - the same configuration and it worked quite well using Intel.

Manjaro took a break from Plymouth back in 2017. I don’t recall when it returned - a couple of years perhaps, time moves fast in my age - but is started with Gnome (I think) and has slowly returned.

The configuration is important - it is not enough to remove quiet and splash - one needs also removing plymouth from mkinitcpio.conf

See these topics on configuring and removing respectively

1 Like

Hi @linux-aarhus, thanks for your help.

I followed your instructions, but I’m not sure I got them correctly, I’ve got Nouveau (didn’t opt in for proprietary Nvidia drivers) so I added:

But I got an error upon updating initramfs via minitcpio.

And also

But in the end no results, so should I upload the content as you suggested?

As a beginning I’d recommend not adding anyting to MODULES array as this is only for early kms.

Start slowly by ensuring kms is in HOOKS array

Your system has intel and Nvidia - you should be able boot with the Intel GPU before fiddling with Nvidia.

You can extract the info mentioned in the linked topic - then post the url in this topic. The mentioned topic is only for reference now.

1 Like

https://0x0.st/XV0M.txt

I just have to add that, kms was there by default so I didn’t have to add it. This is how it looks by default:

HOOKS=(base udev autodetect kms modconf block keyboard keymap consolefont plymouth filesystems fsck)

Secondly, I get a few warnings when running sudo mkinitcpio -P, here they are just in case:

==> WARNING: Possibly missing firmware for module: 'ast'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'

Hi @linux-aarhus, would you mind PTAL? I’ve uploaded the content. :vulcan_salute:

Maybe we could elevate this to a bug at least?

:question:

Please don’t use made-up abbreviations.

A simple search would return:
https://en.m.wiktionary.org/wiki/PTAL

And yes this is commonly used for code reviews, debugs etc.

OK, cool.

However, I think you should refrain from such things on the very public forum. But that’s probably just me. :man_shrugging:

@linux-aarhus, Can you at least let us know, where the issue is stemming from? i.e. Driver, Plymouth, Kernel etc. so I can investigate the issue further?

I have already uploaded the info you’ve described:
https://0x0.st/XV0M.txt

I thought it seemed a little flowery (PTAL) … although I’ve never seen this acronym used in the wild; or at all; so, not so commonly used.

I think the point was that nobody should have to guess at such vague abbreviations; let alone go searching the Internet for illumination; when simply writing please take a look would have been immediately understandable by all.

Remember that not everybody is as technically or socially literate as we presume them to be – there are also language barriers to contend with – take this under advisement before using uncommon acronyms, social media norms, or leet speak.

That is all. Cheers.

This thread does not lead to anything good, so I close it.

1 Like