Page 1 of 4 123 ... LastLast
Results 1 to 10 of 35

Thread: No ethernet connection: hardware fault?

  1. #1
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default No ethernet connection: hardware fault?

    Hi,

    On my HTPC running Leap 15 my network connection has gone. Yast gives "Not connected" for the ethernet device, does permit configuring of it, but no connection is made.
    I added a second Ethernet adapter, but that also gives the same result.

    It's not the cable: if I connect that to a raspberry, the connection is fine.

    I don't see anything regarding this in dmesg, apart from the finding that the connection is not available.

    I've configured network devices through Yast many times, and never encountered this. Can I have overlooked something, or is it definitively a hardware thing?
    Something that affects both the Ethernet device on the mb itself, and the second device in the PCI-slot?

    Like to have your opinion!

    regards, jehojakim

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,007
    Blog Entries
    1

    Default Re: No ethernet connection: hardware fault?

    Some hardware information would be useful to start with...
    Code:
    /usr/sbin/hwinfo --netcard
    Observe the kernel output from
    Code:
    dmesg --follow
    when first plugging in an ethernet cable.
    openSUSE Leap 15.0; KDE Plasma 5

  3. #3
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: No ethernet connection: hardware fault?

    The result of hwinfo --netcard is

    Code:
    18: PCI 500.0: 0200 Ethernet controller
      [Created at pci.378]
      Unique ID: JNkJ.qQIprdItMR3
      Parent ID: Rgik.DFXWmiC9JE1
      SysFS ID: /devices/pci0000:00/0000:00:15.0/0000:05:00.0
      SysFS BusID: 0000:05:00.0
      Hardware Class: network
      Model: "Intel Gigabit CT Desktop Adapter"
      Vendor: pci 0x8086 "Intel Corporation"
      Device: pci 0x10d3 "82574L Gigabit Network Connection"
      SubVendor: pci 0x8086 "Intel Corporation"
      SubDevice: pci 0xa01f "Gigabit CT Desktop Adapter"
      Driver: "e1000e"
      Driver Modules: "e1000e"
      Device File: eth1
      Memory Range: 0xfeac0000-0xfeadffff (rw,non-prefetchable)
      Memory Range: 0xfea00000-0xfea7ffff (rw,non-prefetchable)
      I/O Ports: 0xc000-0xcfff (rw)
      Memory Range: 0xfeae0000-0xfeae3fff (rw,non-prefetchable)
      Memory Range: 0xfea80000-0xfeabffff (ro,non-prefetchable,disabled)
      IRQ: 16 (1497 events)
      HW Address: 68:05:ca:16:37:7b
      Permanent HW Address: 68:05:ca:16:37:7b
      Link detected: no
      Module Alias: "pci:v00008086d000010D3sv00008086sd0000A01Fbc02sc00i00"
      Driver Info #0:
        Driver Status: e1000e is active
        Driver Activation Cmd: "modprobe e1000e"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #15 (PCI bridge)
    
    36: PCI 100.0: 0200 Ethernet controller
      [Created at pci.378]
      Unique ID: rBUF.5rbhBgx50x4
      Parent ID: 8otl.G5Dfw+ssufC
      SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:01:00.0
      SysFS BusID: 0000:01:00.0
      Hardware Class: network
      Model: "Gigabyte Onboard Ethernet"
      Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
      Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
      SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
      SubDevice: pci 0xe000 "Onboard Ethernet"
      Revision: 0x06
      Driver: "r8169"
      Driver Modules: "r8169"
      Device File: eth0
      I/O Ports: 0xe000-0xefff (rw)
      Memory Range: 0xd0004000-0xd0004fff (ro,non-prefetchable)
      Memory Range: 0xd0000000-0xd0003fff (ro,non-prefetchable)
      IRQ: 43 (no events)
      HW Address: 94:de:80:06:30:cf
      Permanent HW Address: 94:de:80:06:30:cf
      Link detected: no
      Module Alias: "pci:v000010ECd00008168sv00001458sd0000E000bc02sc00i00"
      Driver Info #0:
        Driver Status: r8169 is active
        Driver Activation Cmd: "modprobe r8169"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #34 (PCI bridge)
    dmesg --follow gives nothing when plugging in an ethernet cable, on neither of the interfaces.

    I've tried it after booting without the cable attached (which is I think you mean by "first plugging in"), and after booting with the cable already attached, then removing and re-inserting it.

    In all cases the result is the same.

  4. #4
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,582
    Blog Entries
    14

    Default Re: No ethernet connection: hardware fault?

    What happens if you boot a previous kernel?
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #5
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: No ethernet connection: hardware fault?

    Alas, there is no previous kernel, since it's a fresh install of Leap 15.0 And, since I don't have internet connection, update is not possible...

    There's a hole in the bucket, dear Liza...

  6. #6
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,580

    Default Re: No ethernet connection: hardware fault?

    So never had network connection???

    What NIC chip do you have some realtek chips require a special driver.

    lspci as root should show you the hardware

  7. #7
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,796

    Default AW: No ethernet connection: hardware fault?

    Please post:
    Code:
    ping -c1 8.8.8.8
    Code:
    ping -c1 google.com

  8. #8
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,007
    Blog Entries
    1

    Default Re: No ethernet connection: hardware fault?

    Both ethernet devices show no link detected. In any case, when you connect a known good ethernet cable between your router and one of the NICs, observe the output from

    1) For the Gigabyte Onboard Ethernet (Realtek chipset)
    Code:
    /usr/sbin/ethtool eth0
    2) For the Intel NIC
    Code:
    /usr/sbin/ethtool eth1
    openSUSE Leap 15.0; KDE Plasma 5

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,007
    Blog Entries
    1

    Default Re: No ethernet connection: hardware fault?

    Your Realtek NIC is currently using the r8169 driver...
    Code:
    Model: "Gigabyte Onboard Ethernet"
    Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
    Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
    SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
    SubDevice: pci 0xe000 "Onboard Ethernet"
    Revision: 0x06
    Driver: "r8169"
    Driver Modules: "r8169"
    Device File: eth0
    Instead, install the r8168 Realtek driver (for Leap 15)...

    https://software.opensuse.org/package/r8168
    openSUSE Leap 15.0; KDE Plasma 5

  10. #10
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: AW: No ethernet connection: hardware fault?

    Quote Originally Posted by Sauerland View Post
    Please post:
    Code:
    ping -c1 8.8.8.8
    Network unreachable
    Code:
    ping -c1 google.com
    Name or service unkknown

Page 1 of 4 123 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •