Jump to content

arch - lost internet after update

alphaomega

By alphaomega
in Bruno's All Things Linux

 Share

Recommended Posts

alphaomega

alphaomega

Posted
Posted

After updating Arch (10/31) I can no longer get on the internet.

Not sure what happened. The network was working prior to the update.

I am posting from the same machine now but I am in Slackware.

 

# lspci -k

02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
Subsystem: Gateway, Inc. Device 6047
Kernel driver in use: 8139too
Kernel modules: 8139cp, 8139too

 

# dmesg | grep 8139too

[ 12.924260] 8139cp 0000:02:02.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
[ 13.049585] 8139too: 8139too Fast Ethernet driver 0.9.28
[ 13.052420] 8139too 0000:02:02.0 eth0: RealTek RTL8139 at 0xf800e000, 00:16:76:5d:0a:9b, IRQ 21
[ 14.045925] 8139too 0000:02:02.0 enp2s2: renamed from eth0

 

I'm not seeing a line like the following to indicate the link is up:

[ 15.276083] 8139too 0000:02:02.0 enp2s2: link up, 100Mbps, full-duplex, lpa 0x45E1

 

# ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:16:76:5d:0a:9b brd ff:ff:ff:ff:ff:ff

 

# cat /etc/netctl/ethernet-static

Description='A basic static ethernet connection'
Interface=enp2s2
Connection=ethernet
IP=static
Address='192.168.1.118/24'
Gateway='192.168.1.1'
DNS='192.168.1.1'

 

I can't bring the link up:

# ip link set enp2s2 up

RTNETLINK answers: Invalid argument

 

# netctl start ethernet-static

Job for netctl@ethernet\x2dstatic.service failed. See 'systemctl status netctl@ethernet\x2dstatic.service' and 'journalctl -xn' for details.

 

# journalctl -xn

-- Logs begin at Sun 2013-05-19 01:05:48 CDT, end at Fri 2014-10-31 18:20:56 CDT. --
Oct 31 18:20:24 emachinesw3503.localdomain network[412]: Failed to bring the network up for profile 'ethernet-static'
Oct 31 18:20:24 emachinesw3503.localdomain systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, s
Oct 31 18:20:24 emachinesw3503.localdomain systemd[1]: Failed to start Networking for netctl profile ethernet-static.
-- Subject: Unit netctl@ethernet\x2dstatic.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@ethernet\x2dstatic.service has failed.
--
-- The result is failed.
Oct 31 18:20:24 emachinesw3503.localdomain systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
Oct 31 18:20:51 emachinesw3503.localdomain network[477]: Starting network profile 'ethernet-static'...
Oct 31 18:20:56 emachinesw3503.localdomain network[477]: Failed to bring interface 'enp2s2' up
Oct 31 18:20:56 emachinesw3503.localdomain network[477]: Failed to bring the network up for profile 'ethernet-static'
Oct 31 18:20:56 emachinesw3503.localdomain systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, s
Oct 31 18:20:56 emachinesw3503.localdomain systemd[1]: Failed to start A basic static ethernet connection.
-- Subject: Unit netctl@ethernet\x2dstatic.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@ethernet\x2dstatic.service has failed.
--
-- The result is failed.
Oct 31 18:20:56 emachinesw3503.localdomain systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
lines 1-25/25 (END)

 

$ ping 192.168.1.1

connect: Network is unreachable

 

 

Anyone have any ideas on what the problem might be?

Thanks in advance.

 

I am going to try and downgrade back to the previous kernel.

 

dmesg 10/31/14

http://pastebin.com/9QN2Rd2K

 

pacman.log last 3 updates

http://pastebin.com/cpvvDM68

Link to comment
Share on other sites
alphaomega

alphaomega

Posted
  • Author
Posted

Downgraded the kernel and I'm back online (posting from Arch now)

No clue what the problem is.

[2014-11-01 11:49] [PACMAN] Running 'pacman -U linux-3.16.4-1-i686.pkg.tar.xz'
[2014-11-01 11:50] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-11-01 11:50] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Starting build: 3.16.4-1-ARCH
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Starting build: 3.16.4-1-ARCH
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-11-01 11:50] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2014-11-01 11:50] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-11-01 11:50] [PACMAN] downgraded linux (3.17.1-1 -> 3.16.4-1)

Anyone have any ideas?

Link to comment
Share on other sites
alphaomega

alphaomega

Posted
  • Author
Posted (edited)

Not sure if this matters.

In kernel 3.17 the nic is on irq 21

[ 13.052420] 8139too 0000:02:02.0 eth0: RealTek RTL8139 at 0xf800e000, 00:16:76:5d:0a:9b, IRQ 21

In kernel 3.16 the nic is on irq 9

[ 12.699709] 8139too 0000:02:02.0 eth0: RealTek RTL8139 at 0xf800e000, 00:16:76:5d:0a:9b, IRQ 9

Edited by alphaomega
Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

Perhaps your network interface name changed with the last systemd update from a week or so ago? Have you tried running ip link show to check the device's names?

Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

Basically all of your errors indicate that the device enp2s2 doesn't exist and that is causing your profiles to fail.

 

Since your posting from Slackware the device numbers will not be the same.

Link to comment
Share on other sites
alphaomega

alphaomega

Posted
  • Author
Posted

Perhaps your network interface name changed with the last systemd update from a week or so ago? Have you tried running ip link show to check the device's names?

 

This is from Arch when I could not get the network to work with kernel 3.17

# ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:16:76:5d:0a:9b brd ff:ff:ff:ff:ff:ff

 

This is from Arch with the network working after downgrading back to kernel 3.16

# ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 00:16:76:5d:0a:9b brd ff:ff:ff:ff:ff:ff

Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

Ok. I am on limited computing power right now (see this post: http://forums.scotsnewsletter.com/index.php?showtopic=73316entry410836 ) till moday but I will try to research more.

 

Well the issue is the network device:

ip link set enp2s2 up

 

RTNETLINK answers: Invalid argument

 

and everything afterwards points to that issue. So basically we need to figure out why the device is not able to turn on.

Link to comment
Share on other sites
alphaomega

alphaomega

Posted
  • Author
Posted

Kernel 3.17.2-1 was available today.

Upgraded everything with pacman -Syu.

Encountered the same issue I had with kernel 3.17.1-1.

Downgraded back to 3.16.4-1.

And I can get back online again.

 

Link to comment
Share on other sites
alphaomega

alphaomega

Posted
  • Author
Posted (edited)

If you do not figure it out, I'll be back to full speed tomorrow sometime.

I think I might be getting somewhere.

 

I thought the issue might be because of the different irqs being used.

Looked to see if there was a config file I could edit to get it to use the same irq.

Apparently there are no driver options available for this driver.

 

Doing a google search I came across a post which mentioned

a problem with irq sharing and to append noapic to the kernel line.

 

Upgraded the system with pacman -Syu

Appended noapic to the kernel append line.

And I'm online now in Arch with kernel 3.17.2-1.

# uname -a

Linux emachinesw3503.localdomain 3.17.2-1-ARCH #1 SMP PREEMPT Thu Oct 30 20:31:16 CET 2014 i686 GNU/Linux

 

At boot I am getting the following message:

BIOS bug, no explicit IRQ entries, using default mptable. (tell your hw vendor)

Not sure if that is a bad thing.

Edited by alphaomega
Link to comment
Share on other sites
sunrat

sunrat

Posted
Posted

I had the same problem since 3.15. Turned out there was a regression in the ath9k_htc driver for my usb wireless adapter. Adding nohwcrypt to module options fixed it. I haven't tried 3.17 without adding the option yet.

I made a file ath9k_htc.conf in /etc/modprobe.d/ with this -

options ath9k_htc nohwcrypt=1

 

Obviously not related if you don't have Atheros wireless using ath9k_htc.

  • Like 1
Link to comment
Share on other sites
  • 2 weeks later...
alphaomega

alphaomega

Posted
  • Author
Posted

The noapic option is no longer needed with the new kernel.

$ uname -a
Linux emachinesw3503.localdomain 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 22:56:01 CET 2014 i686 GNU/Linux

 

 

  • Like 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...