You are not logged in.
Hi there.
I've been using Arch on a VM for a while and decided to install it on my main PC a few days ago. All went well and it has been running smoothly for two days. But today I got a notification in GNOME telling me that updates were available when I wanted to reboot.
After installing the updates, stuff started going wrong. First, a 3 min start job ran before booting into the display manager and the internet connection was down. I decided to reboot again and now it's stuck at the message "Reached target Graphical Interface.", and also no network connectivity (I am unable to ping google or my gateway, even after restarting the dhcpcd service).
Also, the resolution is lower than usual (possibly indicating a problem with the nouveau driver).
The code lines appended with "# ***" exceed my screen's width.
The output of
systemctl status dhcpcd contains the log
dhcpcd[10803]: Starting dhcpcd on all interfaces...
dhcpcd[10803]: dev: loaded udev
dhcpcd[10803]: no valid interfaces found # this one is colored red
dhcpcd[10803]: forked to background, child pid 10805
dhcpcd[10803]: Started dhcpcd on all interfaces.(time stamps omitted for brevity)
Its status is shown as "active (running)".
The output of
ip link is
1: lo: <LOOPBACK, UP, LOWER_UP> mtu 655536 qdisc noqueue state UNKNOWN mode DEFAULT #***
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00The output of
systemctl status gdm.service also shows it as active (running) and contains the following log
gdm[340]: Unable to kill session worker process
gdm[340]: Child process -10685 was already dead
gdm[340]: Child process 10674 was already dead
gdm[340]: Unable to kill session worker process
gdm[340]: GdmDisplay: display located at 0.189357 seconds
gdm[340]: Could not start command '/usr/lib/gdm/gdm-session # ***
gdm[340]: GLib: g_child_watch_add_full: assertuion 'pid > # *** this one is colored red
gdm[340]: Child process -10699 was already dead
gdm[340]: Child process 10689 was already dead
gdm[340]: Unable to kill session worker processAttempting to restart GDM causes a flickering for a while.
Edit: The PC's name shows up in my router's list of clients, but attempting to ping the gateway or the PC's IP address both return "connect: Network is unreachable". After restarting the router, the PC no longer shows up in its list.
tracepath 192.168.1.1returns "send failed".
Last edited by MrcJkb (2017-10-12 18:03:31)
Offline
But today I got a notification in GNOME telling me that updates were available when I wanted to reboot.
After installing the updates, stuff started going wrong.
Something under gnome performed automatic system updates?
Offline
What is the output of `uname -a` and `pacman -Q linux`?
Offline
Thanks for the quick replies!
MrcJkb wrote:But today I got a notification in GNOME telling me that updates were available when I wanted to reboot.
After installing the updates, stuff started going wrong.Something under gnome performed automatic system updates?
It appears so. The same thing happened on my VM today, too (but nothing went wrong there).
What is the output of `uname -a` and `pacman -Q linux`?
'uname -a' outputs:
Linux homepc 4.13.4-1-ARCH #1 SMP PREEMPT Thu Sep 28 08:39:52 CEST 2017 x86_64 GNU/Linuxand 'pacman -Q linux' returns
linux 4.13.5-1Thanks for the hint!
Downgrading to linux 4.13.4-1 fixed the GDM issue.
The network issue is still there though.
Last edited by MrcJkb (2017-10-12 17:49:43)
Offline
That most likely means that your boot partition wasn't mounted when you updated. Either that or you have your bootloader looking in the wrong place.
Offline
That most likely means that your boot partition wasn't mounted when you updated. Either that or you have your bootloader looking in the wrong place.
That could be it.
I had modified the fstab in an attempt to change the ownership of my second HDD today. But I didn't make any changes to the sda entries.
Offline
Downgrading the linux package fixed the GDM issue, but the network connectivity problems still persist.
Edit: After resetting the dhcpcd service and rebooting, the network connections work again.
Thanks again for your help!
Last edited by MrcJkb (2017-10-12 18:02:07)
Offline
You still do not have your boot partition mounted correctly unless you fixed that also without telling us. The next time you do an update to the system, things will fail again. You need to search the forums and the Wiki on setting the UEFI boot partition to the correct mount point.
Matt
"It is very difficult to educate the educated."
Offline
You still do not have your boot partition mounted correctly unless you fixed that also without telling us. The next time you do an update to the system, things will fail again. You need to search the forums and the Wiki on setting the UEFI boot partition to the correct mount point.
I added the missing line to /etc/fstab, mounting my boot partition at /boot
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=6ca051f1-c4a3-4d6b-9c1e-20d00307cb6b /boot ext4 rw,relatime,errors=remount-ro 0 2After rebooting and calling 'pacman -Syu', the display manager loaded successfully.
Offline