Stuck on boot

Gamble · 2019-10-18 16:33:47

So I'm trying to start up arch and I can get through to the boot screen, but it just gets stuck there. I found out how to run without the desktop manager, and when I do that, it works just fine. Since that worked, I assumed that it was a problem with my desktop manager (sddm), so I disabled sddm. Having sddm disabled allows me to be able to boot in every time. I thought that if I update all the packages, something would work, however I'm not able to update packages at all and can't find a connection to do so either. What do I do?

Trilby · 2019-10-18 16:50:10

Gamble wrote:

What do I do?

Read these, then post some actual information:
http://catb.org/~esr/faqs/smart-questions.html
https://wiki.archlinux.org/index.php/Ge … leshooting

Gamble wrote:

I'm not able to update packages at all

Why not?

V1del · 2019-10-18 17:09:01

You need to in general post more information, what hardware are you trying this on, what journal logs get logged when failing to boot? https://wiki.archlinux.org/index.php/Sy … ing_output

FWIW since this is an often reccuring topic two things you can do is install and enable haveged and/or set up early KMS in that order.

Gamble · 2019-10-18 17:29:06

I can't update packages be I get because when I run pacman -Syu or Syyu, I get:

error: failed retrieving file ['core.db' 'extra.db' 'community.db' and 'multilib.db'] from . . .

when I try to ping google.com:

ping: google.com: Temporary failure in name resolution

ip link shows that my wireless state is dormant

WorMzy · 2019-10-18 17:50:45

So configure your networking.

Gamble · 2019-10-25 06:10:39

When I try to ping: google.com, I get 'Temporary failure in name resolution'
When running

 ip link set wlp1s0 up

my wireless shows state DORMANT and mode DEFAULT. Even after connection to ethernet, my ping google still shows 'Temporary failure in name resolution'.

 ping 8.8.8.8
connect: Network is unreachable

Last edited by Gamble (2019-10-25 06:11:00)

Trilby · 2019-10-25 12:08:49

 ip link set wlp1s0 up

This is not how you configure a wireless connection.

Gamble · 2019-10-25 17:21:40

Thanks Trilby! I think that my Network is configured. I don't think that's the issue anymore because even when I connect via Ethernet, I can't ping a website

xse · 2019-10-25 17:25:19

Gamble wrote:

Thanks Trilby! I think that my Network is configured. I don't think that's the issue anymore because even when I connect via Ethernet, I can't ping a website

How are you connecting via Ethernet ? Are you just plugging the cable in and hoping it'll work ?
It needs to be configured (ie static/dhcp, have a gw, a dns and such), there's several way to do it (see wiki)

loqs · 2019-10-25 17:28:24

What is the output of the following:

ip a
ip r
ping 8.8.8.8
ping www.google.com

Gamble · 2019-10-25 17:45:02

xse wrote:

How are you connecting via Ethernet ? Are you just plugging the cable in and hoping it'll work ?

I'm plugging in the Ethernet, then I do

 ip link set enp3s0 up

Which gives me a state of UP. Is this correct? dhcpcd is active, but I can't show you dhcpcd@enp3s0.service. Unfortunately I'm not near the Ethernet anymore to connect

Gamble · 2019-10-25 17:57:55

Sorry if ip a seems off, I can't copy and paste since I'm not actually in the desktop terminal, so I had to type out everything. If I accidentally missed something, I apologize

ip a
1: lo <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00
    inet 127.0.0/8 scope host lo
        valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 2c:60:0c:71:a8:4c brd ff:ff:ff:ff:ff:ff
3: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,LOWER_UP> mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000
    link/ether e6:f6:8f:7b:f6:1a brd ff:ff:ff:ff:ff:ff

ip r

shows nothing, just returns

ping 8.8.8.8
connect: Network is unreachable
ping www.google.com
ping: google.com: Temporary failure in name resolution

loqs · 2019-10-25 18:02:03

2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 2c:60:0c:71:a8:4c brd ff:ff:ff:ff:ff:ff

The NIC is up but has no IP address and it appears the cable is not connected.

Gamble · 2019-10-25 18:03:49

The NIC is up but has no IP address and it appears the cable is not connected.

Sorry, I forgot to mention. Since my post last night, I'm no longer near the Ethernet cable to connect. I'll get back to this later for more information to give you. Sorry about that

xse · 2019-10-25 18:30:30

Gamble wrote:

I'm plugging in the Ethernet, then I do
 ip link set enp3s0 up 
Which gives me a state of UP. Is this correct? dhcpcd is active, but I can't show you dhcpcd@enp3s0.service. Unfortunately I'm not near the Ethernet anymore to connect

To be sure i'd kill dhcpcd and explicitly start it from the console on the correct interface to have a look at the output.

For your wifi connection, you need to set your interface up like you did, but then you also need to associate it with the correct ssid and password (WPA/WEP if any) and then start dhcpcd on the correct interface (assuming you want dhcp and not a static ip).

Have a go at reading the wiki page: https://wiki.archlinux.org/index.php/Ne … n/Wireless
It clearly states:

Just like other network interfaces, the wireless ones are controlled with ip from the iproute2 package.
Managing a wireless connection requires a basic set of tools. Either use a network manager or use one of the following directly

This is off course something you can automate, and like always there's several different ways to automate it.

For example, my configuration uses wpa_supplicant and a systemd .network file to connect to my house unencrypted wifi (no neighbor here) :

xse@rpi ~ % cat /etc/systemd/network/25-wlan0.network
[Match]
Name=wlan0

[Network]
DHCP=yes
DNSSEC=no
DNS=8.8.8.8

[DHCP]
RouteMetric=20
xse@rpi ~ % cat /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
network={
        ssid="Livebox-4cb1"
        key_mgmt=NONE
}
xse@rpi ~ % systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-10-24 19:06:34 CEST; 1 day 1h ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 2845 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 987)
   Memory: 1.6M
   CGroup: /system.slice/systemd-networkd.service
           └─2845 /usr/lib/systemd/systemd-networkd

Oct 24 19:06:33 rpi systemd[1]: Starting Network Service...
Oct 24 19:06:34 rpi systemd-networkd[2845]: wlan0: Gained IPv6LL
Oct 24 19:06:34 rpi systemd-networkd[2845]: Enumeration completed
Oct 24 19:06:34 rpi systemd[1]: Started Network Service.
Oct 24 19:06:34 rpi systemd-networkd[2845]: wlan0: IPv6 successfully enabled
Oct 24 19:06:34 rpi systemd-networkd[2845]: eth0: IPv6 successfully enabled
Oct 24 19:07:41 rpi systemd-networkd[2845]: wlan0: Gained carrier
Oct 24 19:07:41 rpi systemd-networkd[2845]: wlan0: DHCPv4 address 192.168.1.22/24 via 192.168.1.1
xse@rpi ~ % systemctl status wpa_supplicant@wlan0.service
● wpa_supplicant@wlan0.service - WPA supplicant daemon (interface-specific version)
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant@.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2019-10-24 19:06:35 CEST; 1 day 1h ago
 Main PID: 2847 (wpa_supplicant)
    Tasks: 1 (limit: 987)
   Memory: 1.1M
   CGroup: /system.slice/system-wpa_supplicant.slice/wpa_supplicant@wlan0.service
           └─2847 /usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-wlan0.conf -iwlan0

Oct 24 19:06:35 rpi systemd[1]: Started WPA supplicant daemon (interface-specific version).
Oct 24 19:06:35 rpi wpa_supplicant[2847]: Successfully initialized wpa_supplicant
Oct 24 19:07:41 rpi wpa_supplicant[2847]: wlan0: Trying to associate with 5c:33:8e:03:d5:2b (SSID='Livebox-4cb1' freq=2412 MHz)
Oct 24 19:07:41 rpi wpa_supplicant[2847]: wlan0: Associated with 5c:33:8e:03:d5:2b
Oct 24 19:07:41 rpi wpa_supplicant[2847]: wlan0: CTRL-EVENT-CONNECTED - Connection to 5c:33:8e:03:d5:2b completed [id=0 id_str=]
Oct 24 19:07:41 rpi wpa_supplicant[2847]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 24 19:07:41 rpi wpa_supplicant[2847]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
xse@rpi ~ %

But you can go with any way you like the most, netctl, NetworkManager, wicd, ....

Last edited by xse (2019-10-25 18:39:50)

Gamble · 2019-10-25 19:04:33

To be sure i'd kill dhcpcd and explicitly start it from the console on the correct interface to have a look at the output

Sorry, but can you explain what you mean by this? When you mean kill, do you mean disable? And What do you mean by start from the console.

But you can go with any way you like the most, netctl, NetworkManager, wicd, ....

I've had a working network connection for the last six months and I used NetworkManager to set it up. Is there a reason why it stopped working all of a sudden? And back to my original issue, is there a reason why when I disable sddm, I'm able to login to a desktop-less system, but it really only gets stuck on boot when sddm is enable.

xse · 2019-10-25 19:12:26

Gamble wrote:

Sorry, but can you explain what you mean by this? When you mean kill, do you mean disable? And What do you mean by start from the console.

I just meant launching "dhcpcd enp3s0" as root when your cable is plugged in, and if it complains about being already active killing it. It's output may provide more information.

Gamble wrote:

Is there a reason why it stopped working all of a sudden?.

No clue there could be a few, how do you used to launch NetworkManager ?
Having a glance at all the relevant logs could be helpful.

Last edited by xse (2019-10-25 19:16:12)

Arch Linux

#1 2019-10-18 16:33:47

Stuck on boot

#2 2019-10-18 16:50:10

Re: Stuck on boot

#3 2019-10-18 17:09:01

Re: Stuck on boot

#4 2019-10-18 17:29:06

Re: Stuck on boot

#5 2019-10-18 17:50:45

Re: Stuck on boot

#6 2019-10-25 06:10:39

Re: Stuck on boot

#7 2019-10-25 12:08:49

Re: Stuck on boot

#8 2019-10-25 17:21:40

Re: Stuck on boot

#9 2019-10-25 17:25:19

Re: Stuck on boot

#10 2019-10-25 17:28:24

Re: Stuck on boot

#11 2019-10-25 17:45:02

Re: Stuck on boot

#12 2019-10-25 17:57:55

Re: Stuck on boot

#13 2019-10-25 18:02:03

Re: Stuck on boot

#14 2019-10-25 18:03:49

Re: Stuck on boot

#15 2019-10-25 18:30:30

Re: Stuck on boot

#16 2019-10-25 19:04:33

Re: Stuck on boot

#17 2019-10-25 19:12:26

Re: Stuck on boot

Board footer