I can't connect via ethernet

English Network/Internet
1

Hello,
I can’t connect via ethernet. I think this is due to the fact I can’t see the eth0 in ifconfig:

mango:/home/zaldo # ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host                                                                                                                                                        
          UP LOOPBACK RUNNING  MTU:65536  Metric:1                                                                                                                                              
          RX packets:52 errors:0 dropped:0 overruns:0 frame:0                                                                                                                                   
          TX packets:52 errors:0 dropped:0 overruns:0 carrier:0                                                                                                                                 
          collisions:0 txqueuelen:0                                                                                                                                                             
          RX bytes:3048 (2.9 Kb)  TX bytes:3048 (2.9 Kb)                                                                                                                                        

wlp2s0    Link encap:Ethernet  HWaddr 40:F0:2F:A7:26:71  
          inet addr:192.168.43.97  Bcast:192.168.43.255  Mask:255.255.255.0
          inet6 addr: fe80::42f0:2fff:fea7:2671/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15164 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14905 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6192519 (5.9 Mb)  TX bytes:2936210 (2.8 Mb)

I don’t know what to do.

2

No. There is no eth0 by default, interfaces are named differently nowadays (since openSUSE 13.1)…

Your interface is called wlp2s0, it is up and has an IP address, so it should be working.

The first question is, what do you mean with “I can’t connect via ethernet”?
How exactly are you trying to connect, and to where?

As said above, your ethernet is connected, so you probably mean you can’t call a web page in your browser?
Maybe “just” a DNS problem.
Can you reach hosts via IP address?
Try this and post the output:

ping 8.8.8.8

And/or try to type http://130.57.66.6 into your browsers address field. You should get a page, right?
(it will say that the page is down for maintenance, but that doesn’t matter; the important thing is that you get that message from the server and not your browser…)

3

Oops, sorry! Now I got confused myself it seems. :shame:

wlp2s0 is of course a wireless device.

So apparently your ethernet card is not even detected. I suppose it doesn’t show up in YaST->Network Devices->Network Settings->Overview either, right?

Can you please post the output of “/sbin/lspci -nnk”?

4

Thank you for the reply.
Yes, right now I am connected via wireless tethering with the mobile phone and that is fine.
My problem is that I am trying to using ethernet at work and it does not work. And honestly I don’t know what should happen when I plug in the cable (some popups?). In network manager, the wired option is also grayed out and I can only add wireless connections.
I actually see eth0 in YaST->Network Devices->Network Settings->Overview.


mango:/home/zaldo # /sbin/lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: i915
        Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Device [8086:0a0c] (rev 09)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation Lynx Point-LP HECI #0 [8086:9c3a] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:1b.0 Audio device [0403]: Intel Corporation Lynx Point-LP HD Audio Controller [8086:9c20] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI Express Root Port 3 [8086:9c14] (rev e4)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI Express Root Port 4 [8086:9c16] (rev e4)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.4 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI Express Root Port 5 [8086:9c18] (rev e4)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB EHCI #1 [8086:9c26] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation Lynx Point-LP LPC Controller [8086:9c43] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: lpc_ich
        Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] [8086:9c03] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation Lynx Point-LP SMBus Controller [8086:9c22] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel modules: i2c_i801
01:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM57786 Gigabit Ethernet PCIe [14e4:16b3] (rev 01)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
01:00.1 SD Host controller [0805]: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader [14e4:16bc] (rev 01)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]
        Kernel driver in use: sdhci-pci
        Kernel modules: sdhci_pci
02:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
        Subsystem: Lite-On Communications Inc Device [11ad:0632]
        Kernel driver in use: ath9k
        Kernel modules: ath9k
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon R7 M265] [1002:6604]
        Subsystem: Acer Incorporated [ALI] Device [1025:0776]
5

In yast I can see:
Ethernet Network Card DHCP eth0
Broadcom Ethernet Controlled not configured

Clicking on it, it says: unable to configure the network card because the kernel device (eth0, wlan0) is not present.

6

Well, as long as no kernel module, i.e. “driver”, is loaded, your card won’t work at all.
This is your ethernet card, but it doesn’t have a “Kernel driver in use” line:


mango:/home/zaldo # /sbin/lspci -nnk
...
01:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM57786 Gigabit Ethernet PCIe [14e4:16b3] (rev 01)
        Subsystem: Acer Incorporated [ALI] Device [1025:0775]

The strange thing is that this should be supported out of the box by the tg3 kernel module…

Does the interface appear if you run this?

sudo modprobe tg3

If not, please post the following output afterwards:

dmesg | tail
dmesg | grep -i tg3

And check that you have kernel-firmware installed. I’m not sure whether it’s needed in this case, and your problem doesn’t seem to be related to it missing, but anyway.

And a silly question:
You don’t have deactivated the card in the BIOS or something like that?

Yes, that’s because no driver for it is loaded.

7

No, no UEFI (BIOS) deactivation done.

sudo modprobe tg3

Nothing happens.

mango:/usr/src/packages # dmesg | tail
 9153.202120] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:42f0:2fff:fea7:2671 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=410 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=370                                                                                                                                                                        
 9154.561440] mce: [Hardware Error]: Machine check events logged                                                                                                                               
 9183.698724] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:42f0:2fff:fea7:2671 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44                                                                                                                                                                          
 9215.713482] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:42f0:2fff:fea7:2671 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44                                                                                                                                                                          
 9279.742050] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:42f0:2fff:fea7:2671 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44                                                                                                                                                                          
 9407.796984] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:42f0:2fff:fea7:2671 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44                                                                                                                                                                          
 9663.905492] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:42f0:2fff:fea7:2671 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44                                                                                                                                                                          
 9689.793205] pps_core: LinuxPPS API ver. 1 registered                                                                                                                                         
 9689.793209] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>                                                                                         
 9689.795006] PTP clock support registered                                                                               


dmesg | grep -i tg3

Outputs nothing

8

Hm. And what openSUSE/kernel version are you using? (I thought you wrote 13.2, but that must have been in a different thread…)

In 13.2 (kernel 3.16.7) the tg3 module definitely specifies it supports this chip, so it should at least be listed as available “Kernel modules” in the lspci output.
Maybe yours is too old? I don’t know since when this is supported.
In that case installing a newer kernel from http://download.opensuse.org/repositories/Kernel:/stable/standard/ should help.

OTOH, installing a newer kernel might not be a good idea if you use the fglrx driver. But you seem to use the intel chip only anyway (are you?), and if you installed the fglrx packages from the repo (or using Sebastian Siebert’s Script) they should include a patch for Kernel 3.19 too.

9 
mango:~ # cat /etc/os-release
NAME=openSUSE
VERSION="13.1 (Bottle)"
VERSION_ID="13.1"
PRETTY_NAME="openSUSE 13.1 (Bottle) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"

mango:~ # uname -a
Linux mango.site 3.11.10-25-desktop #1 SMP PREEMPT Wed Dec 17 17:57:03 UTC 2014 (8210f77) x86_64 x86_64 x86_64 GNU/Linux

I installed the fglrx, but it broke my system and I needed to install suse again. So I kept the intel.

10

Ok, so it is indeed 13.1.

Well, then try to install the latest kernel:

sudo rpm -i http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/kernel-desktop-3.19.3-1.1.gf10e7fc.x86_64.rpm

Or if you’d rather want to try 13.2’s kernel 3.16.7 (not so much of a version jump…):

sudo rpm -i http://download.opensuse.org/repositories/Kernel:/openSUSE-13.2/standard/x86_64/kernel-desktop-3.16.7-61.1.g9b25387.x86_64.rpm

After a reboot, the ethernet should hopefully work.

If the newer kernel gives you problems (e.g. your system doesn’t boot), you should still be able to boot the older one via “Advanced Options” in the boot menu.

11

Wow, thanks.
Now I have the driver and the wired option in network manager.
Only problem encountered so far is the mouse pointer disappearance.

12

Good to hear. So the problem is indeed that 13.1’s kernel is just too old and doesn’t support this device yet.

Only problem encountered so far is the mouse pointer disappearance.

Hm. The kernel contains part of the intel driver, the other part, the Xorg driver, is in xf86-video-intel.
Maybe the (old) Xorg driver included in 13.1 has problems with the latest intel kernel module?
As mentioned before, you could try the 13.2 kernel too.
To boot specific kernel versions, use “Advanced Options” in the boot menu (by default the one with the highest version is booted).
To uninstall specific kernel versions, use YaST’s “Versions” tab, or specify the exact version to rpm:

sudo rpm -e kernel-desktop-3.19.3

OTOH, upgrading Xorg, Mesa and its drivers to the latest versions should help as well:

sudo zypper ar http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_13.1 xorg
sudo zypper dup --from xorg

(just upgrading the intel driver isn’t possible unfortunately AFAIK)

But then you might as well consider an upgrade to openSUSE 13.2…

13

Ok thanks. Strange thing is the fact that sometimes I have the pointer, others I don’t. I would say 50-50.
While the ethernet is working perfectly.