https://bugzilla.suse.com/show_bug.cgi?id=1217417 https://bugzilla.suse.com/show_bug.cgi?id=1217417#c16 --- Comment #16 from Joe S <jmscdba@gmail.com> --- (In reply to Takashi Iwai from comment #15)

Check the entries in /sys/bus/pci/devices/*, and whether the given one "0000:05:00.0" is present and it's for your Realtek device. If the device is present and still bind fails, you might see something in the kernel log.

Ok here are the commands I did and the results modprobe r8169 lsmod | grep r8169 r8169 114688 0 mdio_devres 12288 1 r8169 libphy 245760 3 r8169,mdio_devres,realtek echo -n "10ec 8126 ffff ffff 0 0 0" > /sys/bus/pci/drivers/r8169/new_id echo -n "0000:05:00.0" > /sys/bus/pci/drivers/r8169/bind -bash: echo: write error: No such device ls -al '/sys/bus/pci/devices/0000:05:00.0' lrwxrwxrwx 1 root root 0 Dec 22 23:23 /sys/bus/pci/devices/0000:05:00.0 -> ../../../devices/pci0000:00/0000:00:1c.3/0000:05:00.0 cat '/sys/bus/pci/devices/0000:05:00.0/device' 0x8126 I also ran journalctl -b -xef while doing the 2 echo commands and no messages were shown. So it seems to see the 0000:05:00.0 device as the 8126 so I don't understand why your second echo says "No such device" -- You are receiving this mail because: You are on the CC list for the bug.