On Sunday 13 July 2008, Walter Dnes wrote:
On Wed, Jul 09, 2008 at 08:44:51AM +0100, Neil Bothwick wrote
chip *ALWAYS* comes up as eth1.
Udev is doing this. If you have removed the second card,
delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit
the file to switch the
On Sat, 12 Jul 2008 19:55:56 -0400, Walter Dnes wrote:
Udev is doing this. If you have removed the second card,
delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit the
file to switch the assignments for the two NICs.
Thanks. A new and improved helpfull feature that
On Wed, Jul 09, 2008 at 08:44:51AM +0100, Neil Bothwick wrote
chip *ALWAYS* comes up as eth1.
Udev is doing this. If you have removed the second card,
delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit the file
to switch the assignments for the two NICs.
Thanks. A new and
On Tue, 8 Jul 2008 23:21:22 -0400, [EMAIL PROTECTED] wrote:
I finally stumbled across the *REAL* reason I couldn't get it working.
I always tried configuring eth0 for it... silly me. Apparently, the
chip *ALWAYS* comes up as eth1.
Udev is doing this. If you have removed the second card,
I got a Dell last summer, in which I couldn't get the network chip
running, so I bought a cheap Via Rhine PCI network card and used that
for almost a year. I finally got the built-in chip working today on the
older 530. This post is being sent on it. It's a bastardized Intel
chip that shows
5 matches
Mail list logo
