linux-kernel - [BUG] RTL8169/8139 based network card

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Oct 2007 19:05:18 +0200
From:	Lukas Razik <linux@...ik.name>
To:	linux-kernel@...r.kernel.org
Subject: [BUG] RTL8169/8139 based network card

Kernel Version: 2.6.22.9 (and others)

Hello!

I've an issue with a RTL8169 based network card (the same with a RTL8139
card and another system)

# lspci -v :
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
Gigabit Ethernet (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit
Ethernet
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 12
        I/O ports at e000 [size=256]
        Memory at f9fdd000 (32-bit, non-prefetchable) [size=256]
        [virtual] Expansion ROM at 10000000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2

At system startup I get the following messages:
# dmesg :
...
r8169 Gigabit Ethernet driver 2.2LK loaded
eth0: RTL8169sb/8110sb at 0xc4830000, 00:0c:76:a0:05:92, IRQ 12
...

But if I try to ifconfig the eth0 interface, I get these error messages:
# ifconfig eth0 192.168.0.2
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device

But if I try to ifconfig eth1 then it configures my network device which
was detected as eth0 at boot time...
ifconfig eth1 192.168.0.2

This leads to errors with other ethernet interfaces...
Any ideas what there's going wrong?
Many thanks for any answers!!!

Regards,
Lukas


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/