as I was distro-hopping, I also tried Manjaro. All 3 major spins share the same issue on my intel based laptop:
The boot process is halted very early - before you can switch consoles or whatever. It simply stalls.
I found this to happen even with the Manjaro installation image when booting from an USB-Stick.
It does boot when no external monitor is connected (or is switched off). Problem is: I use a docking station and my ext. monitor is present most of the time.
It also reboots fine most of the time.
It happens on all Manjaro spins - so it is not related to KDE or GNOME.
For the time being, I switched to Pop!_OS, but since this is also Ubuntu-based I'd rather use Manjaro .
From initial post, but later found it was not related to the problem thanks to the heads-up from the two gents answering below:
Today I experimented with editing the boot parameters of the installation and it seems that my laptop boots when I delete the AMD-part out of the initrd line:
Default, does not boot if ext. monitor present:
linux /boot/vmlinuz-$2 initrd /boot/amd_ucode.img /boot/intel_ucode.img /boot/initramfs-x86_64.img
Changed to, does boot:
linux /boot/vmlinuz-$2 initrd /boot/intel_ucode.img /boot/initramfs-x86_64.img
Since I do not know if the PC really boots because I cancelled out the amd_ucode.img or because it boots differently because of me using the editor before actually booting...can anybody confirm this bug/behaviour? .
- Is this a common issue on intel-based systems or is it just my Dell Latitude E7440? (Intel HD 4400, i5 Gen4U)
- If it is common, it would be very benefitial to change the default boot configuration of Manjaro.
- If it is just my laptop - can you point me to a tutorial on how to change the boot entries of the finished install of Manjaro, please
- Dell E-Dock plus docking station was the issue. Connecting the monitor directly to the laptop showed no issues
- deleting "quiet" from GRUB boot parameters also resulted in successful booting even when using the docking station