From: Ondrej Zary <linux@rainbow-software.org>
To: Lukas Razik <linux@razik.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] RTL8169/8139 based network card
Date: Mon, 15 Oct 2007 23:15:42 +0200 [thread overview]
Message-ID: <200710152315.43795.linux@rainbow-software.org> (raw)
In-Reply-To: <fac9621a7d6bd667a2e879c344e7f8a5@mb8-2.1blu.de>
On Monday 15 October 2007 19:05:18 Lukas Razik wrote:
> 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?
udev - persistent network rules in /etc/udev/rules.d/
--
Ondrej Zary
prev parent reply other threads:[~2007-10-15 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 17:05 [BUG] RTL8169/8139 based network card Lukas Razik
2007-10-15 21:15 ` Ondrej Zary [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710152315.43795.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@razik.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.