Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #178832

Re: New motherboard, no network

Show all headers | View raw

On Tue, Mar 14, 2017 at 04:12:15PM +0100, Hans wrote:
> Hi Tony, 
> > # PCI device 0x10ec:0x8169 (r8169)
> > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> > ATTR{address}=="6c:fd:b9:00:6f:76", ATTR{dev_id}=="0x0",
> > ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
> > 
> > # PCI device 0x10ec:0x8168 (r8169)
> > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> > ATTR{address}=="bc:ae:c5:29:77:d8", ATTR{dev_id}=="0x0",
> > ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

> You have twice the same entry, but one is pointing to eth0 and the second one 
> is naming the same as eth1. I suppose, one of it is the card from the old pc.

No, they're different.  The PCI ID comments are different (one ends
with 8169 and the other with 8168), the MAC addresses are different,
and the eth0/eth1 names are different.

> What happens, if you delete the orphaned entry manually?
> 
> You can delte it, and rename the last entry to "eth0" (if this is our primary 
> card). I am sure, you will know, hich MAC is the active one.

I have doubts about that being a good idea.

I'm more concerned with the fact that apparently some command or other
(I don't remember if he told us what commands he ran) only showed eth0
and not eth1.

Original poster, please include the actual shell commands that you
run along with their output.  You should be running commands such as:

ifconfig -a
ip addr list
dmesg | grep eth

(Although for dmesg, we may need to see some context around the matching
lines, even just showing the grep output would be a good start.)

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

New motherboard, no network Tony van der Hoff <tony@vanderhoff.org> - 2017-03-14 15:50 +0100
  Re: New motherboard, no network Dan Ritter <dsr@randomstring.org> - 2017-03-14 16:10 +0100
  Re: New motherboard, no network Hans <hans.ullrich@loop.de> - 2017-03-14 16:20 +0100
    Re: New motherboard, no network Greg Wooledge <wooledg@eeg.ccf.org> - 2017-03-14 16:40 +0100
      Re: New motherboard, no network Tony van der Hoff <tony@vanderhoff.org> - 2017-03-14 17:10 +0100
  Re: New motherboard, no network Gene Heskett <gheskett@shentel.net> - 2017-03-14 22:20 +0100

csiph-web