Arch Linux

fettouhi

Member

Registered: 2007-05-07

Posts: 745

[SOLVED] Moving Old Arch Linux Install to New Hardware

I have a Arch Linux 64 bit install that is about 5+ years old. Originally I installed this on an old DELL workstation I bought back in december 2008. In 2012 I moved it to new custom build machine with a i7-2600k cpu and a GTX 580 nvidia graphics card. The install is using software raid. Where the boot partition is mirrored and the root and home partition are running RAID 0. I just build a new PC again with a i7-6700k (no GPU for now a GTX 1080 will be added later) and I checked the ethernet controller on motherboard and it is a I219-V Intel ethernet controller. Is that supported out of the box in the Arch Linux kernel? The install has kernel 4.6.3 by the way. Last time I moved the disks the machine just booted without issue. Is there anything I should be worried about? It has been so long since my last Arch Linux install...

Last edited by fettouhi (2016-07-08 16:43:33)

fettouhi

Member

Registered: 2007-05-07

Posts: 745

Re: [SOLVED] Moving Old Arch Linux Install to New Hardware

Well everything booted up. I just had to replace the nvidia driver with intel driver and my installation was up and running again on a Skylake 6700k at 4,5 GHz (clocked from 4,0). The ethernet controller was already in the kernel so I had internet from the get go. But I have one small thing I don't understand. I run my machine with dhcp and via my router I make sure thast it gets the same ip at every boot. But if I run

[af@andre ~]$ ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:1f:bc:0f:3b:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.2/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.0.10/24 brd 192.168.0.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::21f:bcff:fe0f:3b20/64 scope link
       valid_lft forever preferred_lft forever

I see two entries for eth0. Why are there two? The ip address eth0 should have is 192.168.0.10, why is there a entry for 192.168.0.2?

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: [SOLVED] Moving Old Arch Linux Install to New Hardware

Most common cause* of this seems to be multiple dhcp client processes, or a [locally configured] static ip and a dhcp client process.

But I wonder if this could be something on the router side. Presumably you configured static dhcp IP based on MAC address. Did you reconfigure the router for the new NIC? I wonder if it's providing the .2 address based on normal dynamic dhcp for unknown client and the .10 based on hostname. Or maybe cached information; did you try turning it (router) off and on again?

* Which is not to say it's actually common; I googled "inet secondary" and only got a few useful hits.

Last edited by alphaniner (2016-07-08 15:10:33)

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

fettouhi

Member

Registered: 2007-05-07

Posts: 745

Re: [SOLVED] Moving Old Arch Linux Install to New Hardware

Yes I have reconfigured my router with the new machine. The second line

inet 192.168.0.10/24 brd 192.168.0.255 scope global secondary eth0

is exactly that. I did have the machine running static ip a few years back. Many it could leftovers of that.

fettouhi

Member

Registered: 2007-05-07

Posts: 745

Re: [SOLVED] Moving Old Arch Linux Install to New Hardware

I was a leftover. I had both dnsmasq and dhclient installed. The dhclient was running static ip. I removed it and now everything is ok.