Re: New motherboard, no network
On Tuesday 14 March 2017 10:24:29 Tony van der Hoff wrote:
> After many years, my faithful ASUS motherboard died, so I've replaced
> it with a Gigabyte GA-F2A68HM-HD2. t booted up fine from my existing
> disk set into Jessie, but networking is inoperative. The board has an
> on-board network interface, plus an extra PCI network board. Neither
> seem to be working, although they are recognised by lspci -v:
>
> ###
> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
> Subsystem: Gigabyte Technology Co., Ltd Motherboard
> Flags: bus master, fast devsel, latency 0, IRQ 74
> I/O ports at e000 [size=256]
> Memory at fea0 (64-bit, non-prefetchable) [size=4K]
> Memory at d080 (64-bit, prefetchable) [size=16K]
> Capabilities: [40] Power Management version 3
> Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Endpoint, MSI 01
> Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
> Capabilities: [d0] Vital Product Data
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [140] Virtual Channel
> Capabilities: [160] Device Serial Number
> 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance
> Reporting
> Kernel driver in use: r8169
>
> 02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169
> PCI Gigabit Ethernet Controller (rev 10)
> Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family
> PCI Gigabit Ethernet NIC
> Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
> I/O ports at d000 [size=256]
> Memory at fe92 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at fe90 [disabled] [size=128K]
> Capabilities: [dc] Power Management version 2
> Kernel driver in use: r8169
> ###
>
> ifconfig only lists one board, which appears inactive:
>
> eth0 Link encap:Ethernet HWaddr 6c:fd:b9:00:6f:76
> inet addr:192.168.1.7 Bcast:192.168.1.255
> Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> loLink encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:2124 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2124 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:208935 (204.0 KiB) TX bytes:208935 (204.0 KiB)
>
>
>
> /etc/udev/70-persistent-net.rules presumably contains the addresses
> for the old motherboard:
>
> # This file was automatically generated by the
> /lib/udev/write_net_rules # program, run by the
> persistent-net-generator.rules rules file. #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
>
> # 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"
>
>
>
> So, how do I get the network active?
>
> Thanks,
Udev, seeing the existing configs, helpfully renamed the new interfaces
for you. There is a fix, google can probably find it. Its bit me
several times, at long enough intervals I've forgotten the fix. When
theres 8 decades on ones wet ram it tends to forget the small stuff.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page
Re: New motherboard, no network
On 14/03/17 15:33, Greg Wooledge wrote:
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.)
OK, thanks all for your help. It set me on the path to fixing the
problem. I ended up deleting all the rules in
udev/rules.d/70-persistent-net.rules, and rebooting. Both interfaces
came up as desired, so I'm back on-line.
(I actually tried systemctlrestart networking.service before I rebooted,
but that had no effect - wierd)
So, thanks again for the input.
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |
Re: New motherboard, no network
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.)
Re: New motherboard, no network
Hi Tony,
> /etc/udev/70-persistent-net.rules presumably contains the addresses for
> the old motherboard:
>
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
>
> # 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"
>
>
>
> So, how do I get the network active?
>
> Thanks,
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.
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.
Good luck!
Hans
Re: New motherboard, no network
On Tue, Mar 14, 2017 at 02:24:29PM +, Tony van der Hoff wrote:
> After many years, my faithful ASUS motherboard died, so I've replaced it
> with a Gigabyte GA-F2A68HM-HD2. t booted up fine from my existing disk
> set into Jessie, but networking is inoperative. The board has an
> on-board network interface, plus an extra PCI network board. Neither
> seem to be working, although they are recognised by lspci -v:
>
> ###
> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
> Subsystem: Gigabyte Technology Co., Ltd Motherboard
> Kernel driver in use: r8169
>
> 02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI
> Gigabit Ethernet Controller (rev 10)
> Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family
> PCI Gigabit Ethernet NIC
> Kernel driver in use: r8169
> ###
>
> ifconfig only lists one board, which appears inactive:
>
> eth0 Link encap:Ethernet HWaddr 6c:fd:b9:00:6f:76
> inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> # 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"
>
>
>
> So, how do I get the network active?
Step 1. Check the cabling.
Step 2. Check the link: mii-tool eth0 or ethtool eth0
You want to see something like this:
eth0: negotiated 1000baseT-HD flow-control, link ok
Step 3. Check your switch/hub/link partner to see if it also
recognizes the link
Step 4. Try eth1, as well.
Step 5. Check for firewalling (iptables -L) or routing (ip r)
anomalies.
-dsr-
