Arch Linux, âhangâ on âReached target Graphical Interfaceâ
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
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 <<-END > /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 <<-END > /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:
arch-linux desktop display-manager
add a comment |Â
up vote
1
down vote
favorite
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 <<-END > /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 <<-END > /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:
arch-linux desktop display-manager
2
unfortunately my VBox currently produces the same error...
â GPMueller
Dec 19 '16 at 19:55
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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 <<-END > /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 <<-END > /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:
arch-linux desktop display-manager
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 <<-END > /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 <<-END > /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:
arch-linux desktop display-manager
arch-linux desktop display-manager
edited Apr 13 '17 at 12:36
Communityâ¦
1
1
asked Dec 18 '16 at 15:12
NOhs
12819
12819
2
unfortunately my VBox currently produces the same error...
â GPMueller
Dec 19 '16 at 19:55
add a comment |Â
2
unfortunately my VBox currently produces the same error...
â GPMueller
Dec 19 '16 at 19:55
2
2
unfortunately my VBox currently produces the same error...
â GPMueller
Dec 19 '16 at 19:55
unfortunately my VBox currently produces the same error...
â GPMueller
Dec 19 '16 at 19:55
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
It seems that SDDM/KDE no longer pulls xorg-server packages automatically. So if one adds the xorg-server
package it works.
Found solution here: https://github.com/sddm/sddm/issues/605#issuecomment-275938076
add a comment |Â
up vote
0
down vote
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
.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
It seems that SDDM/KDE no longer pulls xorg-server packages automatically. So if one adds the xorg-server
package it works.
Found solution here: https://github.com/sddm/sddm/issues/605#issuecomment-275938076
add a comment |Â
up vote
2
down vote
accepted
It seems that SDDM/KDE no longer pulls xorg-server packages automatically. So if one adds the xorg-server
package it works.
Found solution here: https://github.com/sddm/sddm/issues/605#issuecomment-275938076
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
It seems that SDDM/KDE no longer pulls xorg-server packages automatically. So if one adds the xorg-server
package it works.
Found solution here: https://github.com/sddm/sddm/issues/605#issuecomment-275938076
It seems that SDDM/KDE no longer pulls xorg-server packages automatically. So if one adds the xorg-server
package it works.
Found solution here: https://github.com/sddm/sddm/issues/605#issuecomment-275938076
answered Jan 30 '17 at 20:20
NOhs
12819
12819
add a comment |Â
add a comment |Â
up vote
0
down vote
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
.
add a comment |Â
up vote
0
down vote
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
.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
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 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
.
answered Aug 31 at 14:59
Florens
11
11
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f331233%2farch-linux-hang-on-reached-target-graphical-interface%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
unfortunately my VBox currently produces the same error...
â GPMueller
Dec 19 '16 at 19:55