Wired interface not detected until plugged with USB adaptator

ninjaconcombre · 11-24-2018, 06:58 AM

Hi.
I am using Debian 4.9.130-2 over a laptop I would have though that ip a output would show the wired interface, whether or not it is plugged, since the card seem to be on board(see dmidecode). All the command I will show will be running while not being plugged to the port (USB or Ethernet)

dmidecode:

Code:

root@poirot:/usr/lib/NetworkManager# dmidecode -t baseboard
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: X751MA
	Version: 1.0       
	Serial Number: BSN12345678901234567
	Asset Tag: ATN12345678901234567
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: MIDDLE              
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0008, DMI type 10, 10 bytes
On Board Device 1 Information
	Type: Video
	Status: Enabled
	Description:  VGA
On Board Device 2 Information
	Type: Ethernet
	Status: Enabled
	Description:  GLAN
On Board Device 3 Information
	Type: Ethernet
	Status: Enabled
	Description:  WLAN

ip a:

Code:

root@poirot:/usr/lib/NetworkManager# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 30:52:cb:05:62:28 brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.118/24 brd 192.168.43.255 scope global dynamic wlp2s0
       valid_lft 2278sec preferred_lft 2278sec
    inet6 fe80::9aaa:efa5:bd68:b09b/64 scope link 
       valid_lft forever preferred_lft forever

Here is lspci -k output:

Code:

lspci -k
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register
	Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display
	Kernel driver in use: i915
	Kernel modules: i915
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor E3800 Series SATA AHCI Controller
	Kernel driver in use: ahci
	Kernel modules: ahci
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Power Control Unit
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e)
	Subsystem: ASUSTeK Computer Inc. Atom Processor E3800 Series SMBus Controller
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
	Subsystem: Lite-On Communications Inc RTL8723BE PCIe Wireless Network Adapter
	Kernel driver in use: rtl8723be
	Kernel modules: rtl8723be

Should'nt it contain the Ethernet port hardware?

Here is the lshw in case you need it:

Code:

root@poirot:/usr/lib/NetworkManager# lshw -c Network
  *-network                 
       description: Interface réseau sans fil
       produit: RTL8723BE PCIe Wireless Network Adapter
       fabriquant: Realtek Semiconductor Co., Ltd.
       identifiant matériel: 0
       information bus: pci@0000:02:00.0
       nom logique: wlp2s0
       version: 00
       numéro de série: 30:52:cb:05:62:28
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rtl8723be driverversion=4.9.0-8-amd64 firmware=N/A ip=192.168.43.118 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       ressources: irq:18 portE/S:e000(taille=256) mémoire:d0600000-d0603fff

As I said, I thought the interface should show up (but not running) even when not plugged in.
I first thought it could be because of the allow-hotplug in etc/network/interfaces:
see https://lists.debian.org/debian-doc/.../msg00010.html

Then, I thoudht I may be a problem of conflict betwen nm and ifupdown. I tried to let NetWorkManager do all the work:
My current interfaces file:

Code:

# The loopback network interface
auto lo
iface lo inet loopback

#auto eth0
#    allow-hotplug eth0
#    iface eth0 inet dhcp

My current NM configuration file:

Code:

cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
dhcp=dhclient
dns=dnsmasq
[ifupdown]
managed=false

My Net-Work manager version is 1.6.2.

I would like to be sure, is that normal that I can't see my Ethernet interface except when it work?(when plugged with USB adapter). If it's normal, do you have any idea to fix the problem?

When I am pluging-in an ethernet cable in the ethernet port directly, nothing happens. Nothing is logged in journalctl.

When I use a USB adaptor, everything work as expected instantly and automatically (journalctl shows the plug event, interface show up and is running, net works perfectly).

I have no ethernet modem in my apartment. So it could take sometimes before I can run commands while the cable is being plugged.
Thanks for your time, and sorry for my English,
Have a nice day.

ondoho · 11-25-2018, 03:53 AM

i don't understand.
all your output suggests that your computer does not have a wired network connection.
are you saying you are using a USB ethernet (wired) adaptor?
if so, maybe

Code:

lsusb

can shed some light.

ninjaconcombre · 11-25-2018, 03:45 PM

All the commands below were executed while my cable was not plugged, either in the ethernet port, or the usb port. But I think (I am not sure), from other posts, even when the cable is not pluged in I should see the Ethernet interface in ip a command. I would like confirmation/infirmation by a guy who know that for a fact. Then, should not lspci output contain an antry for my ethernet port (like for the usb one)?

Here is lsusb output:

Code:

root@poirot:/boot# lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 046d:c012 Logitech, Inc. Mouseman Dual Optical
Bus 001 Device 004: ID 0bda:b722 Realtek Semiconductor Corp. 
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 0bda:57bc Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Thanks for your time. Should I post in the hardware section, to get more replies?

ondoho · 11-26-2018, 01:41 AM

Quote:

Originally Posted by ninjaconcombre

should not lspci output contain an antry for my ethernet port

yes, it should, but it doesn't, hence my statement/confusion.
your lsusb output shows 2 realtek devices, those are usually (but not always) network interfaces.

tbh i still don't understand your problem description, and your output suggests that you simply do not have a wired network interface on your machine, neither the hardware nor an actual connection.
are you sure you are plugging in a networking cable into a suitable port?
do you know the difference between a network and a USB cable/port?

are you using a USB ethernet adaptor, i.e. a USB dongle that has a ethernet plug at the other end?

ninjaconcombre · 11-27-2018, 12:49 PM

Well, sorry if I haven't been clear. All the command output you saw were taken without any cable plugged in. But I do have an ethernet port in my laptop. This is what I call an ethernet adapter.

https://www.officeworks.com.au/shop/...aptor-cou3gbad

My ethernet connexion work automatically and nicely when I use this adaptator.

I can guarantee you that my laptop has an ethernet port XD. Yes, I know the difference between an USB cable/port and an Ethernet one (next year I will have a master's degree in computer science, so I am not THAT bad ^^)

Also, about the 2 lsusb Realtek output, here are the verboses outputs:

Code:

lsusb -v -s2

Bus 001 Device 002: ID 0bda:57bc Realtek Semiconductor Corp. 
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         2 ?
  bDeviceProtocol         1 Interface Association
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0x57bc 
  bcdDevice            0.03
  iManufacturer           3 
  iProduct                1 
  iSerial                 2 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          503
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          4 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass         14 Video
      bFunctionSubClass       3 Video Interface Collection
      bFunctionProtocol       0 
      iFunction               5

This go on whith many video streaming stuff.

Code:

lsusb -v -s4

Bus 001 Device 004: ID 0bda:b722 Realtek Semiconductor Corp. 
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0xb722 
  bcdDevice            2.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          177
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               1

So again no ethernet stuff here

ondoho · 11-29-2018, 01:36 AM

Quote:

Originally Posted by ninjaconcombre

https://www.officeworks.com.au/shop/...aptor-cou3gbad

so it is a USB ethernet adaptor.
and your machine (laptop?) does not have its own ethernet port.
please provide the output of

Code:

sudo lsusb -v

for that device only.
you can trial-and-error by plugging it out and in until you know which one it is.
you can try the same with 'dmesg'.
if all that doesn't yield results, then the adaptor or the USB socket is broken.

ninjaconcombre · 12-01-2018, 01:38 PM

I will try explain my situation better.

1: I have an ethernet port. When I plug an ethernet cable to it, it do not work.

2: I have 3 USB port. When I use theses ports whith the usb adaptator and an ethernet cable, every think work normally

3: When I dont use ethernet (ie no cable, only wifi), the interface is not present in ip a. I thought I should see the wired connexion, even if cable not pluged in, cause I saw some people in that case. I would like to really know if this is normal.

All the command you saw were taken while case 3.