When I’m trying to boot Manjaro I get the line »dev/sda11 clean, […] files, […] blocks« (as usual), but then the screen goes blank with a only a text cursor in top left corner. And nothing else happens. (I’m still able to return to GRUB by pressing Ctrl+Alt+Del.)
I tried different kernels and fall back images – every time the same problem.
I haven’t done any changes to the system since the last successful boot (as far as I remember …)
When you get back to that screen, pressing Ctrl+Alt+f7 may open up the gui. If not
If not, pressing Ctrl+Alt+f2 should take you to a terminal where you can login and do a system update with sudo pacman -Syu.
That sounds like a graphic card driver issue. It is hard to tell without enough information from your environment though. I would recommend you take a look at this thread first:
There is a very good guide for setting up the graphic cards on the Wiki
I would go the EKMS route. It will ensure the video driver is loaded early enough before GDM starts.
If I’m not wrong, some people prefer to add delay to the GDM service unit in systemd so that it loads after the video driver. IMO, that’s not an optimal solution as you’d be adding delay to the overall boot time.
Can you post the output of the following commands?: sudo mhwd -li sudo cat /etc/mkinitcpio.conf
For EKMS to work, the output should look something like this:
sudo mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-modesetting 2020.01.13 true PCI
~ >>> sudo cat /etc/mkinitcpio.conf [1]
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=(i915)
Looking at your previous posts, I can tell that you were not elevating any of the commands with sudo.
Note that most administration tasks like dealing with configuration files need to be run adding sudo as regular user accounts normally don’t have the ability to do so.
$sudo mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-vesa 2017.03.12 true PCI
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
network-r8168 2016.04.20 true PCI
Warning: No installed USB configs!
$sudo cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=(i915)
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
I would uninstall video-vesa and video-linux as they might be just redundant. IMO, the advantage of using kernel modesetting is that it will persist across system upgrades. You’ll get also the latest firmware for your hardware along with the kernel updates. The disadvantage is that any failure with KMS may cause a kernel panic. I haven’t had any issues so far like this, though.
Once you have removed the drivers, try to regenerate the initramfs again (sudo mkinitcpio-P)
