I just bought a new Dell G15, installed Manjaro Gnome from the latest iso using the entire disk, deleteing all particions.
The installaion went throught, but on restarting the system hangs on the Dell logo for minutes. If I switch it off, a manjaro logo comes up below the Dell logo for a second.
I reinstalled Manjaro just in case, but it is the same.
If you’re sure, then there’s only one other thing I can suggest to check.
Make sure whether the system is using UEFI or Legacy (BIOS) mode and is installed accordingly. Other than that, I have no idea what’s going on.
I don’t know if this’ll work or make a difference, but you COULD boot with the Live ISO, enter a chroot environment and updating the system, providing any errors you get.
That may work, and it also might not. But it is all I can think of. Oh, that, and if there’s no danger of losing anything, just reinstalling it.
you have nvdia video card do you have nonfree driver install ?
I found when i use the newest ISO to install .I haven’t the grub tmenu o display. it has long black screen an direct goes into gnome desktop . then I make the grub config to display in graphical terminal then it goes right.
manjaro-chroot -a  ✔
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
==> Mounting (ManjaroLinux) [/dev/nvme0n1p1]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
pamac checkupdates && pamac upgrade
Your system is up-to-date.
Preparing...
Synchronizing package databases...
https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/core/x86_64/core.db: Error resolving “www.mirrorservice.org”: Name or service not known
http://kartolo.sby.datautama.net.id/manjaro/stable/core/x86_64/core.db: Error resolving “kartolo.sby.datautama.net.id”: Name or service not known
http://mirror.dacentec.com/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.dacentec.com”: Name or service not known
https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.nluug.nl”: Name or service not known
https://ba.mirror.garr.it/mirrors/manjaro/stable/core/x86_64/core.db: Error resolving “ba.mirror.garr.it”: Name or service not known
https://download.nus.edu.sg/mirror/manjaro/stable/core/x86_64/core.db: Error resolving “download.nus.edu.sg”: Name or service not known
http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/core/x86_64/core.db: Error resolving “ftp.rz.tu-bs.de”: Name or service not known
https://manjaro.cu.be/stable/core/x86_64/core.db: Error resolving “manjaro.cu.be”: Name or service not known
https://ftp.lysator.liu.se/pub/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.lysator.liu.se”: Name or service not known
https://mirror.clarkson.edu/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.clarkson.edu”: Name or service not known
https://osmirror.org/manjaro/stable/core/x86_64/core.db: Error resolving “osmirror.org”: Name or service not known
http://mirror.upb.edu.co/manjarostable/core/x86_64/core.db: Error resolving “mirror.upb.edu.co”: Name or service not known
http://manjaro.barata.pt/stable/core/x86_64/core.db: Error resolving “manjaro.barata.pt”: Name or service not known
https://mirrors.shuosc.org/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.shuosc.org”: Name or service not known
http://mirror.truenetwork.ru/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.truenetwork.ru”: Name or service not known
http://ftp.linux.org.tr/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.linux.org.tr”: Name or service not known
https://mirror.philpot.de/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.philpot.de”: Name or service not known
http://kibo.remi.lu/stable/core/x86_64/core.db: Error resolving “kibo.remi.lu”: Name or service not known
https://mirror.tuchola-dc.pl/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.tuchola-dc.pl”: Name or service not known
http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.tu-chemnitz.de”: Name or service not known
https://mirror.yandex.ru/mirrors/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.yandex.ru”: Name or service not known
https://mirror.math.princeton.edu/pub/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.math.princeton.edu”: Name or service not known
https://mirror.cedia.org.ec/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.cedia.org.ec”: Name or service not known
http://linorg.usp.br/manjaro/stable/core/x86_64/core.db: Error resolving “linorg.usp.br”: Name or service not known
http://ftp.belnet.be/mirrors/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.belnet.be”: Name or service not known
http://manjaro.mirror.ac.za/stable/core/x86_64/core.db: Error resolving “manjaro.mirror.ac.za”: Name or service not known
http://ftp.riken.jp/Linux/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.riken.jp”: Name or service not known
https://mirror.netcologne.de/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.netcologne.de”: Name or service not known
https://manjaro.ipacct.com/manjaro/stable/core/x86_64/core.db: Error resolving “manjaro.ipacct.com”: Name or service not known
http://ftp.caliu.cat/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.caliu.cat”: Name or service not known
http://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.tuna.tsinghua.edu.cn”: Name or service not known
http://manjaro.melbourneitmirror.net/stable/core/x86_64/core.db: Error resolving “manjaro.melbourneitmirror.net”: Name or service not known
http://ftp.cuhk.edu.hk/pub/Linux/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.cuhk.edu.hk”: Name or service not known
https://repo.rhindon.net/manjaro/stable/core/x86_64/core.db: Error resolving “repo.rhindon.net”: Name or service not known
http://mirror.ventraip.net.au/Manjaro/stable/core/x86_64/core.db: Error resolving “mirror.ventraip.net.au”: Name or service not known
https://mirrors.ustc.edu.cn/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.ustc.edu.cn”: Name or service not known
http://distro.ibiblio.org/manjaro/stable/core/x86_64/core.db: Error resolving “distro.ibiblio.org”: Name or service not known
http://pet.inf.ufsc.br/mirrors/manjarolinux/stable/core/x86_64/core.db: Error resolving “pet.inf.ufsc.br”: Name or service not known
https://mirror.netzspielplatz.de/manjaro/packages/stable/core/x86_64/core.db: Error resolving “mirror.netzspielplatz.de”: Name or service not known
http://free.nchc.org.tw/manjaro/stable/core/x86_64/core.db: Error resolving “free.nchc.org.tw”: Name or service not known
http://kambing.ui.ac.id/manjaro/stable/core/x86_64/core.db: Error resolving “kambing.ui.ac.id”: Name or service not known
http://mirror.is.co.za/mirrors/manjaro.org/stable/core/x86_64/core.db: Error resolving “mirror.is.co.za”: Name or service not known
http://mirror.rise.ph/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.rise.ph”: Name or service not known
https://mirrors.ocf.berkeley.edu/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.ocf.berkeley.edu”: Name or service not known
http://mirror.chmuri.net/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.chmuri.net”: Name or service not known
http://ftp.snt.utwente.nl/pub/linux/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.snt.utwente.nl”: Name or service not known
https://mirror.dkm.cz/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.dkm.cz”: Name or service not known
http://mirror.catn.com/pub/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.catn.com”: Name or service not known
http://mirror.infotronik.hu/mirrors/pub/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.infotronik.hu”: Name or service not known
https://mirror.espoch.edu.ec/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.espoch.edu.ec”: Name or service not known
http://mirror.inode.at/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.inode.at”: Name or service not known
https://www.uex.dk/public/manjaro/stable/core/x86_64/core.db: Error resolving “www.uex.dk”: Name or service not known
https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.cc.uoc.gr”: Name or service not known
https://manjaro.moson.eu/stable/core/x86_64/core.db: Error resolving “manjaro.moson.eu”: Name or service not known
http://mirror.xeonbd.com/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.xeonbd.com”: Name or service not known
https://ftp.halifax.rwth-aachen.de/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.halifax.rwth-aachen.de”: Name or service not known
http://repo.manjaro.org.uk/stable/core/x86_64/core.db: Error resolving “repo.manjaro.org.uk”: Name or service not known
http://manjaro.mirrors.uk2.net/stable/core/x86_64/core.db: Error resolving “manjaro.mirrors.uk2.net”: Name or service not known
https://mirrors.ucr.ac.cr/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.ucr.ac.cr”: Name or service not known
https://manjaro.c3sl.ufpr.br/stable/core/x86_64/core.db: Error resolving “manjaro.c3sl.ufpr.br”: Name or service not known
https://mirrors.dotsrc.org/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.dotsrc.org”: Name or service not known
https://manjaro.mirror.garr.it/mirrors/manjaro/stable/core/x86_64/core.db: Error resolving “manjaro.mirror.garr.it”: Name or service not known
http://manjaro.telecoms.bg/stable/core/x86_64/core.db: Error resolving “manjaro.telecoms.bg”: Name or service not known
https://mirror.koddos.net/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.koddos.net”: Name or service not known
http://manjaro.dcc.uchile.cl/stable/core/x86_64/core.db: Error resolving “manjaro.dcc.uchile.cl”: Name or service not known
https://mirrors.sjtug.sjtu.edu.cn/manjarostable/core/x86_64/core.db: Error resolving “mirrors.sjtug.sjtu.edu.cn”: Name or service not known
https://repo.sadjad.ac.ir/manjaro/stable/core/x86_64/core.db: Error resolving “repo.sadjad.ac.ir”: Name or service not known
http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/core/x86_64/core.db: Error resolving “ftp.tsukuba.wide.ad.jp”: Name or service not known
http://mirror.ragenetwork.de/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.ragenetwork.de”: Name or service not known
https://ct.mirror.garr.it/mirrors/manjaro/stable/core/x86_64/core.db: Error resolving “ct.mirror.garr.it”: Name or service not known
http://mirror.datacenter.by/pub/mirrors/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.datacenter.by”: Name or service not known
https://mirrors.shu.edu.cn/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.shu.edu.cn”: Name or service not known
https://mirrors.zju.edu.cn/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.zju.edu.cn”: Name or service not known
http://mirror.ufam.edu.br/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.ufam.edu.br”: Name or service not known
http://mirrors.serverhost.ro/manjaro/packages/stable/core/x86_64/core.db: Error resolving “mirrors.serverhost.ro”: Name or service not known
https://mirror.zetup.net/manjaro/stable/core/x86_64/core.db: Error resolving “mirror.zetup.net”: Name or service not known
http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/core/x86_64/core.db: Error resolving “ftp.free.org”: Name or service not known
https://mirrors.netix.net/manjaro/stable/core/x86_64/core.db: Error resolving “mirrors.netix.net”: Name or service not known
Failed to synchronize databases
Nothing to do.
Transaction successfully finished.
Can you rule out the vmd module and other steps that are afflicting modern systems?
I provided step by step instructions in here:
If you need help applying them, let me know. Make sure to apply all three modifications.
(You likely only have "/" and "/boot/efi" partitions, so skip the line about mounting "/boot" and just do "/" and "/boot/efi" before continuing to the “manjaro-chroot /mnt” part. Though it seems 'manjaro-chroot -a" works fine for you, so you can just use that again.)
Further references,
When you get the chance, can you provide you system specs from a live USB session?
cat /etc/default/grub
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet nvme_load=YES splash apparmor=1 security=apparmor udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
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=(vmd)
# 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 wmodules 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 block autodetect modconf keyboard keymap plymouth 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="zstd"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
Alright, looks good. Can you reboot, and when it gets “stuck” for about a minute, see if you are able to switch to another TTY like this: CTRL + ALT + F3
If so, you don’t have to do anything just yet, wanting to rule something else out. (You can login with your username/password, and run sudo systemctl reboot.) Not sure if you’re on another PC to use this forum. If so, you can leave it at the TTY screen without rebooting.)
edit /etc/default/grub , to chang grub in graphical mode
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_GFXMODE=auto // chang to your resolusion,or use auto
save it ,and `update-grub’
edit /etc/mkinitcpio.conf, add nouveau module to load video card
MODULES=“nouveau …” //if you want use intel card here to use i915
save it. then do mkinitcpio -p linux513 //linux513 is 1 preset, which can find in /etc/mkinitcpio.d/
maybe this can resolve it.