[SOLVED] No network card after update (Unknown header type 08)

LyCC · 2018-08-26 16:08:19

Hi everyone,

after latest kernel update my ethernet card doesn't work any more, lspci -v reports the following:

04:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8161 (rev 10)
        !!! Unknown header type 08
        Kernel modules: r8169

any help please?

Thahk you.

Last edited by LyCC (2018-08-26 17:27:21)

loqs · 2018-08-26 16:17:22

What is the output of the following

pacman -Q linux
uname -r
dmesg
lspci -nnk

LyCC · 2018-08-26 16:28:52

pacman -Q linux
linux 4.18.5.arch1-1

uname -r
4.18.5-arch1-1-ARCH

dmesg: https://justpaste.it/4ol63
lspci -nnk: https://justpaste.it/728ay

ewaller · 2018-08-26 16:34:44

It appears you've two controllers. What are the output of ip link ?

loqs · 2018-08-26 16:37:26

That all looks fine. How is the interface configured / controlled manually or with some kind of service?
If a service what is the status of the service and any please provide any journal output for it from that current boot.
Also the output of `ip a`

LyCC · 2018-08-26 17:02:17

Yes, i activated the onboard controller as I could not get the other one to work. Before the update it was enp3s6, now it seems to changed to enp4s6.
I have the network-manager installed, but none of the config files are there (i set this up a couple of years ago an never touched it, will try to find the config).

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 1c:6f:65:24:92:ed brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.175/24 brd 192.168.1.255 scope global dynamic noprefixroute enp3s0
       valid_lft 258310sec preferred_lft 258310sec
    inet6 fe80::34ed:456f:6e16:b3c0/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp4s6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:5d:34:4a brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:5d:34:4a brd ff:ff:ff:ff:ff:ff

Edit:
What i found till now:
can't get the link up with the

ip link set enp4s6 up
RTNETLINK answers: Cannot assign requested address

the device gets ff:ff:.... MAC address, so i manually add a different MAC address, then the "up" command returns nothing,
but the interface is still reported down (btw i plugged the cable into the card). Once i rebooted, the MAC is again ff:ff....
PS: i have a dual boot machine, just tested under windows to rule out the card being dead, and there it works.

*** Final edit ***
Darn thing... the led on the card went out as i was "playing" with the mac address, so cleared DMI pool data, unpowered everything and works now, even the device
name got back to enp3s6.

03:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20, NUMA node 0
        I/O ports at ce00 [size=256]
        Memory at fd8ff000 (32-bit, non-prefetchable) [size=256]
        [virtual] Expansion ROM at fdf00000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
        Kernel driver in use: r8169
        Kernel modules: r8169

Thank you all for your help!

Last edited by LyCC (2018-08-26 17:27:45)

ewaller · 2018-08-26 17:29:05

Those debug steps are pretty much exactly what I would have suggested.

And in Windows, there exists a valid MAC address that maps to the vendor of your NIC https://macvendors.com/ ?

LyCC · 2018-08-26 18:23:59

I have no idea why it worked in windows and not in linux, guessing ???differences in driver implementation???, the
linux implementation was allergic to something (i don't have the in-depth knowledge to come up with an explanation of what
that could have been that a DMI data clear fixes). Bottom line, i guess a strange coincidence that this happened just as i rebooted after the update.

Anyway, a big thank you again for everyone that jumped in.

seth · 2018-08-26 19:17:37

Ftr, ensure to disable https://wiki.archlinux.org/index.php/Du … t_Start-Up

Arch Linux

#1 2018-08-26 16:08:19

[SOLVED] No network card after update (Unknown header type 08)

#2 2018-08-26 16:17:22

Re: [SOLVED] No network card after update (Unknown header type 08)

#3 2018-08-26 16:28:52

Re: [SOLVED] No network card after update (Unknown header type 08)

#4 2018-08-26 16:34:44

Re: [SOLVED] No network card after update (Unknown header type 08)

#5 2018-08-26 16:37:26

Re: [SOLVED] No network card after update (Unknown header type 08)

#6 2018-08-26 17:02:17

Re: [SOLVED] No network card after update (Unknown header type 08)

#7 2018-08-26 17:29:05

Re: [SOLVED] No network card after update (Unknown header type 08)

#8 2018-08-26 18:23:59

Re: [SOLVED] No network card after update (Unknown header type 08)

#9 2018-08-26 19:17:37

Re: [SOLVED] No network card after update (Unknown header type 08)

Board footer