New motherboard, no network

[Tony van der Hoff <tony@vanderhoff.org>]

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 fea00000 (64-bit, non-prefetchable) [size=4K]
        Memory at d0800000 (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 fe920000 (32-bit, non-prefetchable) [size=256]
        Expansion ROM at fe900000 [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)

lo        Link 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,
-- 
Tony van der Hoff  | mailto:tony@vanderhoff.org