Arch Linux

uberben

Member

Registered: 2010-08-18

Posts: 78

Boot sequence stops an "Reached target Graphical Interface"

After some recent updates, my Arch install on my desktop has been failing to load up a GUI. I have been using Gnome and GDM on this machine successfully prior to this issue. This computer is all quite new hardware with SSD, so I am used to seeing it boot in a few seconds, but since this issue started it has taken a couple minutes to start up. This seems to be largely due to it trying to pull a dynamic IP and failing after a 1.5 minute timeout, as indicated in the one initialization line. I can not figure out why it is trying to use DHCP as I have it configured to only use a static IP using netctl, and the dhcpcd systemctl service is disabled.

The final line I see in the boot sequence is "Reached target Graphical Interface", at which point the computer seems unresponsive. Another thread I found suggesting I could press a key to get to a prompt, but that is not the case for me. After some time, the screen will go black and I can press a key to bring back the boot sequence output, but I can't seem to get into any other virtual terminals or anything like that. Thankfully, my static IP address is functional after most (but not all) reboots, so I am able to SSH in.

I have tried running updates several times in hopes that there was just a bad pairing of programs, but so far this has not resolved my issue. Some threads I found indicated it could be a graphics driver issue. I have reinstalled my graphics driver (I am using catalyst-total from the AUR) without success.

I'm at the point where I'm not sure what to do next. Any suggestions for places to look or things to try would be much appreciated.

Edit: the boot sequence step and error I associated with DHCP is as follows:

[ ***  ] A start job is running for sys-subsystem-net-devices-eth0.device (Xs / 1min 30s)
[ TIME ] Timed out waiting for device sys-subsystem-net-devices-eth0.device
[DEPEND] Dependency failed for dhcpcd on eth0.

Edit 2: I just issues another reboot and noticed another error message in the boot sequence:

[    2.525665] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6.

I'm not sure if this error is showing up asychronously or not, but I saw it twice, once after

[  OK  ] Started Login Service
         Starting GNOME Display Manager

and once after

[  OK  ] Started GNOME Display Manager.
         Starting accounts Service...
         Starting Authorization Manager...

Last edited by uberben (2014-05-08 14:44:22)

loqs

Member

Registered: 2014-03-06

Posts: 19,114

Re: Boot sequence stops an "Reached target Graphical Interface"

try

$ systemctl list-dependencies --before sys-subsystem-net-devices-eth0.device

to see which units want that device

uberben

Member

Registered: 2010-08-18

Posts: 78

Re: Boot sequence stops an "Reached target Graphical Interface"

% systemctl list-dependencies --before sys-subsystem-net-devices-eth0.device
sys-subsystem-net-devices-eth0.device
● └─dhcpcd@eth0.service

It looks like I might have disabled the main dhcpcd service, but not the service for the specific interface. I don't even have an eth0 on this device (my main ethernet interface is eno1) so I'm not sure how it got there to begin with.

Anyway, I have now removed that service and I no longer get the long timeouts (thank you!), but I am still not getting my desktop environment at the end of the boot sequence.

loqs

Member

Registered: 2014-03-06

Posts: 19,114

Re: Boot sequence stops an "Reached target Graphical Interface"

Try journalctl , the gdm logs under /var/log/gdm and the X server log at /var/log/Xorg.0.log could also try switching display driver / downgrade packages to see which upgrade caused the issue.

uberben

Member

Registered: 2010-08-18

Posts: 78

Re: Boot sequence stops an "Reached target Graphical Interface"

I found this in journalctl:

May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: Initializing built-in extension XFree86-DRI
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: Initializing built-in extension DRI2
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (II) "glx" will be loaded by default.
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (II) LoadModule: "glx"
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (II) Module glx: vendor="Advanced Micro Devices, Inc."
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: compiled for 6.9.0, module version = 1.0.0
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: Loading extension GLX
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (II) LoadModule: "fglrx"
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: compiled for 1.4.99.906, module version = 14.10.2
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: Module class: X.Org Video Driver
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE)
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) Backtrace:
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x48) [0x584b08]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 1: /usr/bin/Xorg (0x400000+0x1887f9) [0x5887f9]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 2: /usr/lib/libpthread.so.0 (0x7f751534b000+0xf4b0) [0x7f751535a4b0]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 3: /usr/lib/xorg/modules/drivers/fglrx_drv.so (0x7f75110bc000+0x40a7b4) [0x7f75114c67b4]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 4: /usr/lib/xorg/modules/drivers/fglrx_drv.so (0x7f75110bc000+0x40a34f) [0x7f75114c634f]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 5: /usr/bin/Xorg (0x400000+0x66ecc) [0x466ecc]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 6: /usr/bin/Xorg (xf86LoadModules+0xba) [0x47684a]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 7: /usr/bin/Xorg (InitOutput+0x7bf) [0x47707f]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 8: /usr/bin/Xorg (0x400000+0x398bb) [0x4398bb]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 9: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f7513fb8000]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) 10: /usr/bin/Xorg (0x400000+0x2507e) [0x42507e]
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE)
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) Segmentation fault at address 0x0
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE)
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: Fatal server error:
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) Caught signal 11 (Segmentation fault). Server aborting
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE)
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE)
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: Please consult the The X.Org Foundation support
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: at http://wiki.x.org
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: for help.
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) Please also check the log file at "/dev/null" for additional information.
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE)
May 08 12:23:13 bendesktop gdm-Xorg-:5[350]: (EE) Server terminated with error (1). Closing log file.

The most recent log file in /var/log/gdm/ is from April 27, which I believe was the last day my system started up fine. There doesn't appear to be anything interesting in there.

Similarly, my latest /var/log/Xorg.0.log is from April 27. Again, nothing really interesting looking in there.

I'll try switching to the open source AMD graphics driver and see if that helps.

uberben

Member

Registered: 2010-08-18

Posts: 78

Re: Boot sequence stops an "Reached target Graphical Interface"

It looks like my issue is that GDM 3.12 isn't compatible with the AMD Catalyst drivers. I switched the LightDM and I am able to get into my system again.

https://wiki.archlinux.org/index.php/GD … D_Catalyst

It seems some others are working on the segfaulting issue here: https://bbs.archlinux.org/viewtopic.php?id=57084&p=263