You are not logged in.
Pages: 1
Topic closed
Hello,
I'm doing a fresh Arch install from the recent 2015.05.01 release. I left my system too long without updates and felt like it needed a fresh start. So I've done this in the past and never had any network problems during installation.
But now this time I can't get connected to the network.
I boot up the installation medium, with a wire connection and as soon as it's done booting I try to ping google, and I get this:
ping: www.google.com: Name or service not known
I can ping localhost normally though.
Then I check if everything is loaded correctly. Here's the output of "lspci -v", showing both the WiFI and network card modules:
07:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Wireless-N 7260
Flags: bus master, fast devsel, latency 0, IRQ 32
Memory at d3600000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 0c-8b-fd-ff-ff-ab-ad-f6
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
0f:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: Hewlett-Packard Company Device 1966
Flags: bus master, fast devsel, latency 0, IRQ 26
I/O ports at 3000 [size=256]
Memory at d3500000 (64-bit, non-prefetchable) [size=4K]
Memory at d3400000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
Capabilities: [170] Latency Tolerance Reporting
Kernel driver in use: r8169
Kernel modules: r8169
And both of them properly loaded (I think), with 'dmesg":
[ 2.721341] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 2.721347] r8169 0000:0f:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 2.728139] r8169 0000:0f:00.0 eth0: RTL8168g/8111g at 0xffffc90000016000, a0:1d:48:6b:67:ad, XID 0c000800 IRQ 27
[ 2.728142] r8169 0000:0f:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 7.168728] r8169 0000:0f:00.0 eno1: renamed from eth0
[ 9.042912] r8169 0000:0f:00.0 eno1: link down
[ 9.042913] r8169 0000:0f:00.0 eno1: link down
[ 10.701008] r8169 0000:0f:00.0 eno1: link up
[ 7.339343] iwlwifi 0000:07:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
[ 7.710386] iwlwifi 0000:07:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[ 7.910590] iwlwifi 0000:07:00.0: Detected Intel(R) Wireless N 7260, REV=0x144
[ 7.910662] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[ 7.910923] iwlwifi 0000:07:00.0: L1 Enabled - LTR Enabled
[ 8.131706] iwlwifi 0000:07:00.0 wlo1: renamed from wlan0
And also check if interfaces are up with 'ip link':
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether a0:1d:48:6b:67:ad brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 0c:8b:fd:ab:ad:f6 brd ff:ff:ff:ff:ff:ff
Now, I check if the dhcpcd deamon is running, with 'systemctl --type=service' and here it shows that it has failed:
UNIT LOAD ACTIVE SUB DESCRIPTION
dbus.service loaded active running D-Bus System Message Bus
● dhcpcd@eno1.service loaded failed failed dhcpcd on eno1
getty@tty1.service loaded active running Getty on tty1
haveged.service loaded active running Entropy Harvesting Daemon
kmod-static-nodes.service loaded active exited Create list of required static device nodes for the current kernel
ldconfig.service loaded active exited Rebuild Dynamic Linker Cache
pacman-init.service loaded active exited Initializes Pacman keyring
systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight:intel_backlight
systemd-hwdb-update.service loaded active exited Rebuild Hardware Database
systemd-journal-catalog-update.service loaded active exited Rebuild Journal Catalog
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-sysusers.service loaded active exited Create System Users
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-done.service loaded active exited Update is Completed
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
user@0.service loaded active running User Manager for UID 0
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
27 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
.
Finally, the results from 'journalctl', showing that connection timed out:
Userspace start-up required 45287 microseconds.
May 05 10:40:52 archiso systemd[1]: Started User Manager for UID 0.
-- Subject: Unit user@0.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user@0.service has finished starting up.
--
-- The start-up result is done.
May 05 10:40:52 archiso login[456]: ROOT LOGIN ON tty1
May 05 10:41:17 archiso dhcpcd[441]: timed out
May 05 10:41:17 archiso dhcpcd[441]: dhcpcd exited
May 05 10:41:17 archiso systemd[1]: dhcpcd@eno1.service: Control process exited, code=exited status=1
May 05 10:41:17 archiso systemd[1]: Failed to start dhcpcd on eno1.
-- Subject: Unit dhcpcd@eno1.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dhcpcd@eno1.service has failed.
--
-- The result is failed.
May 05 10:41:17 archiso systemd[1]: dhcpcd@eno1.service: Unit entered failed state.
May 05 10:41:17 archiso systemd[1]: dhcpcd@eno1.service: Failed with result 'exit-code'.
May 05 10:41:17 archiso systemd[1]: Reached target Network.
-- Subject: Unit network.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.target has finished starting up.
--
-- The start-up result is done.
May 05 10:41:17 archiso systemd[1]: Startup finished in 5.752s (kernel) + 33.196s (userspace) = 50.728s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
I also tried WiFI connection, which in the past has worked for me right after installation boot up, with 'wifi-menu -o wlo1', but I get an error right away from the 'wifi-menu' dialog, saying connection failed.
To rule out HW problems with my computer or with my home router, I am able to connect to both wired and wireless network with Windows on the same computer and same router.
Could anyone give me a hand on this? Thank you in advance.
Last edited by leandroaveiro (2016-05-27 11:04:49)
Offline
Just for fun I booted the installation medium from release 2016.02, and I get the same problem. That is really weird, because I had installed this release before and it worked just fine.
Offline
Just booted GParted Live distribution and it successfully connected using DHCP. So the problem is very likely with Arch, however I have no clue why a the 2016.02 release which worked for me in the past now shows the same problem as the new release.
Offline
Sorry for pieces of information at a time, but I'm trying multiple things here.
Here's the output of journalctl when I try to restart dhcpcd. It seems to be stuck in waiting for something related to IPv6.
-- Unit dhcpcd@eno1.service has finished shutting down.
May 05 13:22:05 leandroaveiro systemd[1]: Starting dhcpcd on eno1...
-- Subject: Unit dhcpcd@eno1.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dhcpcd@eno1.service has begun starting up.
May 05 13:22:05 leandroaveiro dhcpcd[805]: DUID 00:01:00:01:1e:be:03:b5:a0:1d:48:6b:67:ad
May 05 13:22:05 leandroaveiro dhcpcd[805]: eno1: IAID 48:6b:67:ad
May 05 13:22:05 leandroaveiro dhcpcd[805]: eno1: soliciting a DHCP lease
May 05 13:22:05 leandroaveiro dhcpcd[805]: eno1: soliciting an IPv6 router
May 05 13:22:05 leandroaveiro dhcpcd[805]: eno1: Router Advertisement from fe80::ee1a:59ff:feca:50b4
May 05 13:22:05 leandroaveiro dhcpcd[805]: eno1: soliciting a DHCPv6 lease
May 05 13:22:35 leandroaveiro dhcpcd[805]: timed out
May 05 13:22:35 leandroaveiro dhcpcd[805]: dhcpcd exited
May 05 13:22:35 leandroaveiro systemd[1]: dhcpcd@eno1.service: Control process exited, code=exited status=1
May 05 13:22:35 leandroaveiro systemd[1]: Failed to start dhcpcd on eno1.
-- Subject: Unit dhcpcd@eno1.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dhcpcd@eno1.service has failed.
--
-- The result is failed.
Offline
The installation media starts the dhcpcd.service automatically? I did not think it did.
What happens if you reboot the install media, and just enter dhcpcd. Don't start it as a service for this little experiment.
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
Offline
Thanks for your reply. According to the Beginner's guide, it is started automatically. So I had to stop it first.
Then, I entered 'dhcpdc' and got this:
dev: loaded udev
no interfaces have a carrier
forked to background, child pid 637
If I enter the same command again and again, I get this (the above is only for the first time):
sending commands to master dhcpcd process
From the output, it looks like issuing 'systemctl stop dhcpcd@eno1.service' did not have much effect, however it's not listed anymore when running 'systemctl --type=service'.
My network is still down.
Offline
Okay, here comes the stupid question..... Is the cable connected?
The most common cause for no carrier is a loose connection someplace. Check both ends of the Ethernet cable, try a different cable, check that the link lights at both ends of the cable come on when you connect it (assuming you are connecting to a router or switch. If you are connecting to a Ethernet outlet in your building, are you sure that outlet is alive?
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
Offline
There are no such thing as stupid quetions!! . but yes, cabling is OK.... if I simply reboot it and let it go into Windows, connection works normally. Both wired and wireless.
I have just reset my laptop firmware to factory defaults, but still no connection...
I've tried moving to netctl also. No good either.
Offline
I have just proved there are really no stupid questions... the cable was disconnected after all!! I had removed it to try WiFI and forgot to put it back in.... anyway this is the result of starting dhcpcd manually (summary, I could not send this output to a file to paste it here)... still no connection.
dev: loaded udev
DUID: 00:01:00:etc...
eno1: IAID 48:6b:67:ad
wlo1: waiting for carrier
eno1 soliciting an IPv6 router
eno1: Router Advertisement from fe80::ee1a:etc...
eno1: soliciting a DHCPv6 lease
eno1: soliciting a DHCP lease
timed out
forked to background, child pid 844
Offline
I've also found some instructions in Arch wiki regarding a known problem where Windows NIC driver shuts down the NIC at shutdown. I don't believe this problem applies to this case, because I can see the link light coming up at Arch boot process, so the driver is probably newer than the ones discussed in the article.
In any case I enable LAN boot and disable the Shutdown Wake-On-LAN property in the Windows driver.
Still no results.
Offline
I was able to get a wired connection with 'connman'. Switching back to dhcpdc returns to the old problem. I'm continuing the installation with connman until I can get a working system to continue the investigation.
Offline
Marking it as solved. It works with connman and I did not try switching back to NetworkManager.
Offline
Hello, it's 2018, and I'm making a fresh install from the 2018.04.01 image. I'm having the exactly same problem you described (same r8169 module and getting stuck at DHCP v6 lease).
Any chance you were able to make it work by now with dhcpcd?
Thanks!
Offline
As the thread has been marked [SOLVED] is there anything preventing you from going the same route?
That said, a lot has changed in 2 years and it's unclear if you really have the same issue. If you want assistance post information from your own system in your own thread.
Closing.
Last edited by V1del (2018-04-25 07:03:19)
Offline
Pages: 1
Topic closed