Arch linux reached target graphical interface

Arch Linux, «hang» on «Reached target Graphical Interface»

EDIT: I just tried gnome and gdm and it worked flawlessly. So something with the virtualbox packages and the SDDM package seems to not work. At first this question looks like this one (Arch Linux stuck at boot (reached target Graphical Interface)), however, I can still change to a different TTY. Anyways, the following used to work before, but results in a core dump of sddm since recently. Interestingly enough, systems I simply update, which used this install method, do still work, but new installations lead to the issues below. When installing Arch Linux in VirtualBox with Windows 10 as host system, I use this minimum [non]working example that is based on the official Arch Installer guide and used to work:

parted mklabel GPT mkpart ESP fat32 1MiB 513MiB mkpart primary ext4 513MiB 100% set 1 boot on quit mkfs.ext4 /dev/sda2 mkfs.fat -F32 /dev/sda1 mount /dev/sda2 /mnt mkdir -p /mnt/boot mount /dev/sda1 /mnt/boot pacstrap /mnt base base-devel \ virtualbox-guest-modules-arch \ virtualbox-guest-utils \ sddm plasma arch-chroot /mnt bootctl --path=/boot install cat /mnt/boot/loader/entries/arch.conf title Arch Linux linux /vmlinuz-linux initrd /initramfs-linux.img options root=PARTUUID=$( blkid -s PARTUUID -o value /dev/sda2 ) rw END cat /mnt/boot/loader/loader.conf default arch timeout 4 editor 0 END genfstab -pU /mnt >> /mnt/etc/fstab arch-chroot /mnt systemctl enable sddm arch-chroot /mnt useradd -m -G wheel -s /bin/bash bob 

It hangs on «reached target Graphical interface» but I can still use ctrl+alt+F2 in contrast to this question (Arch Linux stuck at boot (reached target Graphical Interface)) and calling journalctl -b -p err yields: And here with more info:

3 Answers 3

It seems that SDDM/KDE no longer pulls xorg-server packages automatically. So if one adds the xorg-server package it works.

I had the same (or a very similar issue). It would stop at reached target graphical interface and I could switch tty. Fom there I could restart gdm and after a couple of tries it would start.

If you are using the proprietary nvidia graphics drivers with xorg you can use this solution. To fix this, open /etc/gdm/custom.conf and uncomment #WaylandEnable=false .

I had an issue with similar symptoms after migrating some disks to new hardware, but could see nothing fishy in the logs after enabling debug logging. The machine also had no dm software installed. I also noticed that some services weren’t starting.

It turns out some of the target files under /etc (eg /etc/systemd/system/multi-user.target.wants/sshd.service were not symlinks as they are meant to be, and may have just had stale code in them. I fixed my issue by removing all non-symlink target files and recreating them with systemctl enable or just manually linking to the appropriate target under /usr/lib/systemd/ — The specific target that was causing my failure was a stale /etc/systemd/system/getty.target.wants/getty@tty1.service

You must log in to answer this question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.7.13.43531

Linux is a registered trademark of Linus Torvalds. UNIX is a registered trademark of The Open Group.
This site is not affiliated with Linus Torvalds or The Open Group in any way.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Зависает arch на Reached target Graphical interface после установки драйверов Nvidia

Доброго времени суток! Установлен arch c KDE и sddm. После установки драйверов Nvidia стал зависать во время включения на строке Reached target Graphical interface. В чем может быть причина?

В логах иксов что? Или опять понаставили арчей и не знают где брать диагностическую информацию?

А где взять эту самую диагностическую информацию? Арч недавно поставил.

Ты просто взял и поставил его? Не читая его официальной вики? Не ознакомившись с его особенностями?

Deleted ( 23.05.19 19:54:57 MSK )
Последнее исправление: Deleted 23.05.19 19:57:20 MSK (всего исправлений: 3)

Загрузись с флешки, сделай arch-chroot и проверяй логи и что там не доставил.

Можно же просто переключиться в другую консоль. Вероятно для ТСа «зависает» это «не показывает рабочий стол».

Переключить в другой терминал (ctrl alt f2) залогинься и удали драйвера nvidia перегрузи комп.

Воистину поиск в интернете творит чудеса! (не, ну если Вера или Таня или . запрещают пользоваться google или другими богомерзкими сервисами. тогда да, только ЛОР)

О чём это я? Ах, да вот весьма поучительная притча о «Reached target Graphical interface», Аrch-е и новичках*. Настоятельно рекомендую к ознакомлению.

—-
А может ну его этот Arch. Накатишь KaliLinux, придёшь снова на ЛОР — «wifi не работает. ». Мы тебе «забанься», ты нам «пацаны помагите». Романтика короче. Ты подумай.

Источник

Arch Linux

Hello! After installing the arch, after a short time after turning off, a black screen began to appear. If I start with nomodeset and radeon.modeset=0, then loading stucks at [ok] Reached target graphical interface. I can login to tty with this. The first time I solved it with

command, but the third time none of these worked. I use xorg, refind, my graphics card is rx 590, dualbooting with win10.

Last edited by rad95 (2022-07-12 16:01:46)

#2 2022-07-05 09:07:38

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

Uhm, Okay, the system somehow started up when I remove nomodeset and radeon.modeset=0, and before that it was black without them. But I think it might happen again.

Last edited by rad95 (2022-07-05 09:08:28)

#3 2022-07-05 10:11:04

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

And yeah, again black screen

#4 2022-07-05 10:25:25

Lone_Wolf Member From: Netherlands, Europe Registered: 2005-10-04 Posts: 11,067

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

You have disabled windows fastboot & hibernation as described at https://wiki.archlinux.org/title/Dual_b … ibernation ?

Welcome to archlinux forums

Last edited by Lone_Wolf (2022-07-05 10:26:00)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

#5 2022-07-05 14:44:00

ewaller Administrator From: Pasadena, CA Registered: 2009-07-13 Posts: 19,346

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

Also, if/when it happens again, see if you can change to a different console use Ctrl-Alt- F3. Try all Fn where n = 1 -> 6 (I think 6 is the last console — I could be wrong)

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#6 2022-07-05 16:26:08

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

Its ok now, i try an installation 4 hours ago and have same error, now 1 hour ago mkinitcpio just get an update and problem solved. No more warning generating modules .

#7 2022-07-05 18:24:46

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

You have disabled windows fastboot & hibernation as described at https://wiki.archlinux.org/title/Dual_b … ibernation ?

If yes, try configuring early kms loading.
see https://wiki.archlinux.org/title/Kernel … _KMS_start

Thanks, i disabled windows fastboot and hibernation, but the problem remained. When I did mkinitсpio, I didn’t pay attention to some of the warnings. It turned out to be a bug that was fixed in the new version. I updated it and I hope everything will be fine now.

#8 2022-07-05 18:26:00

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

Its ok now, i try an installation 4 hours ago and have same error, now 1 hour ago mkinitcpio just get an update and problem solved. No more warning generating modules .

Thanks for the tip, updated it and now I hope everything will be fine (i also have no warnings)

#9 2022-07-05 18:27:05

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

Also, if/when it happens again, see if you can change to a different console use Ctrl-Alt- F3. Try all Fn where n = 1 -> 6 (I think 6 is the last console — I could be wrong)

Yes, i can(f6 is actually last). They are working without ctrl btw, is it good?:D

#10 2022-07-05 18:35:06

ewaller Administrator From: Pasadena, CA Registered: 2009-07-13 Posts: 19,346

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

Yes and no. It means that the boot did not hang and actually finished normally. Apparently as part of the boot process, when the graphical target started, an Xorg (or Wayland) session was supposedly started, but is not working, and is not displaying anything.
So — no need to look at the boot process, and time to start diagnosing the problem with Xorg (or Wayland)

You can change to one of the consoles and log in, then look at the journal, and at the output of commands such as systemctl status to figure out what is, and isn’t working.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#11 2022-07-06 08:50:43

Re: [SOLVED] Bootup hangs at [ok] Reached target graphical interface

So i got black screen again and was able to boot correctly with «amdgpu.dc=0». Waiting again if an error occurs. If someone have the same problem also try to run with «amdgpu.runpm=0».

After successful boot in Xorg.0.log, before the successful loading of amdgpu, it says that ati module could not be loaded. As far as I understand, this error can be ignored? Because I already have amdgpu installed, and ati is needed for outdated video cards.
Also it says that fbdev is not loaded. As far as I understand, this is also an «optional» package, because instead of it, I successfully load vesa. Someone else on the forum said that fbdev will be faster than vesa, is that true?
And last one is «AMDGPU(0): Failed to make import prime FD as pixmap: 22». I did not found any info about this.
(i can’t login to the console when i get a black screen, these are the logs from a successfully started system)

Last edited by rad95 (2022-07-06 09:23:56)

Источник