public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: udev upgrade and non-working eth0
Date: Mon, 27 Nov 2006 15:26:09 +0000	[thread overview]
Message-ID: <20061127152609.6d6c734a@hactar.digimed.co.uk> (raw)
In-Reply-To: <op.tjoivcxwyguj3e@you.and.your.horse>

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

On Mon, 27 Nov 2006 09:36:38 -0500, 7v5w7go9ub0o wrote:

> FWIW, I also upgraded and find that my laptop, which previously had
> eth0 and eth1 for its two cards (one wired and one wireless) now has
> eth0 and eth2.

Do you have IEEE1394_ETH1394 set in your kernel? If so, it's possible
that eth1 is being set to your Firewire interface. You can use udev
rules to ensure that the interfaces are named as you wish. 


-- 
Neil Bothwick

Newsflash! Explosion at M$ beta testsite - Infinite number of monkeys
killed.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-11-27 15:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 13:58 [gentoo-user] udev upgrade and non-working eth0 Mrugesh Karnik
2006-11-27 14:10 ` Uwe Thiem
2006-11-27 14:15 ` blackhawk
2006-11-27 14:36 ` [gentoo-user] " 7v5w7go9ub0o
2006-11-27 15:26   ` Neil Bothwick [this message]
2006-11-27 16:59   ` Mrugesh Karnik
2006-11-27 17:12     ` Richard Fish
2006-11-27 20:57       ` Mrugesh Karnik
2006-11-27 22:46         ` Richard Fish
2006-11-28  0:50           ` Mrugesh Karnik
2006-11-28  1:08             ` Richard Fish
2006-11-28  1:41               ` Mrugesh Karnik
2006-11-28  2:01                 ` Richard Fish
2006-11-28  2:19                   ` Mrugesh Karnik
2006-11-29 17:33                     ` Richard Fish
2006-11-29 18:45                       ` Mick
2006-11-30  0:56                       ` Mrugesh Karnik

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=20061127152609.6d6c734a@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox