Manjaro hangs on Dell logo during boot

[Aragorn]

Well, maybe it was the entropy after all?

[camokatu]

LOL, I don’t want to it restart now, have to do some work

[Aragorn]

Well, if you have the time later, then you can try again, and if it works, then we’ll know.

[camokatu]

Will do, but if it was supposed to work, wouldn’t it have worked on first try? It’s not like cranking and engine I hope

[Aragorn]

Logic suggests that it should indeed have worked the first time. I have no explanation for why it didn’t.

[camokatu]

Well at least it’s consistent. I had to restart again and it booted on 4th time. Not sure if it means anything.

[freggel.doe]

When the machine does boot up:

• check journal for errors from previous failed boots
• disable grub silent boot
  • edit /etc/default/grub
  • remove quiet from GRUB_CMDLINE_LINUX_DEFAULT
  • update-grub to re-generate grub.cfg

This should allow you to check messages on next (failing?) boot,

[yawanathan]

Hello,

Question, have you installed anything lately that after this problem started. Also have you check your logs in /var/log to see if there is something that may be causing the delay in booting?

When it comes to windows, until you install the proprietary drivers, it uses a generic video driver. Also windows uses virt drivers until you put the proprietary ones on the system which is why windows works, it really never touches bare metal until all manufacturer drivers are installed.

[Ciack404]

I have the same issue, except:

1. I had manjaro installed for just a few weeks before it started happening (a few days ago)
2. I’m using gnome
3. I am only using manjaro. I don’t have dual boot
4. I have to restart the laptop 10 or more times before I get to the login screen
5. I can consistently open grub and see the manjaro entry. But once I select it the dell logo flashes 3 times and then gets stuck

I will try to remove quiet from grub and after work I’ll see if that gives me any useful information.

[camokatu]

This is Xorg.0.log in /var/log, the only readable one. The other one is Calamares.log, not sure if it’s relevant, sorry I can’t post links for some reason - pastebin com/raw/9cY18Ztm

[Ciack404]

I found a temporary solution:

after removing quiet from grub I saw that there was no error reported: all steps were passing.
The last step before the booting stopped were either
Started TLP system startup/shutdown
or
Started CUPS scheduler

Thanks to this reddit post I found out that once it’s stuck there if I press ctrl-F2 and then ctrl-F1 I can get to the manjaro login screen.

I then tried to upgrade the kernel from version 5.7 to 5.8 but that didn’t solve the issue. I wasn’t able to downgrade to 5.4 (I can’t find out how to switch kernel: in grub I don’t see the different versions listed) so I can’t say about it.

[Aragorn]

Does this help?

@philm

System takes a long time to boot

If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here

Or this?

@philm

Update: If you can see the line
dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here:
systemctl disable org.cups.cupsd.service
systemctl enable org.cups.cupsd.socket

[Ciack404]

Ok finally installing kernel 5.4 (latest LTS) and removing 5.7 and 5.8 solved the issue.

I used
mhwd-kernel -li
and then
sudo mhwd-kernel -i linux54 rmc
after I made sure I only had 5.8 installed and running.

[chomsky]

Did you enable the service after installing the package?

[camokatu]

I only installed Docker, java and some development libraries. Nothing shows up in the logs.

[camokatu]

Yes, same thing.

[camokatu]

Can confirm this fix. After downgrading to 5.4 LTS the issue is fixed. I was tested by restarting 4 times and it was successful every time.

Note that if you want to drop from linux-latest to linux-lts you’ll have run

sudo pacman -Rcsnu linux-latest

As described in forum.manjaro. org/t/cannot-remove-linux57-breaks-dependency-required-by-linux-latest-something/7679 (can’t add links for some reason, may be because I am new)

Thank you @Ciack404!

[Tobster]

I’ve got the same problem, although the weird thing is that if I switch to another TTY and then back again, it continues booting just fine. For example, when I get stuck on the Dell logo, I can press: Ctrl + Alt + F2 followed by Ctrl + Alt + F1. The Dell logo then disappears and it shows the display manager like it should.

Edit: this was already mentioned above, I’m stupid.

[Aragorn]

@Tobster

I’ve got the same problem, although the weird thing is that if I switch to another TTY and then back again, it continues booting just fine. For example, when I get stuck on the Dell logo, I can press: Ctrl + Alt + F2 followed by Ctrl + Alt + F1. The Dell logo then disappears and it shows the display manager like it should.

This is without any doubt a consequence of your CPU developing too little entropy at boot time. Install haveged and you will be fine.

sudo pacman -Syyu haveged
sudo systemctl enable haveged --now