Installation and conection via SSH - troubles

[71GA]

I have been an desktop Archlinux user for a couple of years now, but this RPI is really something new to me. I installed it on my SSD card using the procedure described here (tab installation):

http://archlinuxarm.org/platforms/armv6/raspberry-pi

I did this in a minute and it is very well explained. Now what I want is to connect my RPI via UTP cable to my laptop (which allso has desktop Archlinux installed) and connect to it via SSH. At this time it seems like a mission impossible to me but let me first show you what I did.

1.) I connected the UTP cable between laptop and RPI
2.) I set my laptop's ip for ethernet card using:

$this->bbcode_second_pass_code('', 'sudo ip addr add 169.254.39.2/16 dev enp3s0')

3) I created the configuration file for netctl (name is 009-nastavitve) which looks like this:

$this->bbcode_second_pass_code('', 'Description='Nastavitev statičnega IP'
Interface=eth0
Connection=ethernet
IP=static
Address='169.254.39.3/16'
Gateway='169.254.39.2/16'
DNS='193.2.1.66' ')

4.) I inserted my SSD card which has Archlinux (for RPI) installed.
5.) On SSD card there is a system partition /dev/sde2 which I mounted into a folder /mnt/root
6.) I copied the netctl configuration file 009-nastavitve onto the SSD card's netctl folder:

$this->bbcode_second_pass_code('', 'sudo cp 009-nastavitev /mnt/root/etc/netctl')

7.) I made sure that when RPI wakes up and boots Archlinux it will also start netctl:

$this->bbcode_second_pass_code('', 'ln -s /usr/lib/systemd/system/netctl-auto@.service /mnt/root/etc/systemd/system/multi-user.target.wants/netctl-auto@eth0.service')

8.) I unmounted the SSD, put it into the RPI and powered it on.
9.) I tried to connect using SSH on my desktop Archlinux terminal and found out that RPI can't be seen:

$this->bbcode_second_pass_code('', 'sudo ssh root@169.254.39.3
ssh: Could not resolve hostname 169.254.39.3/16: Name or service not known')

10.) I tried to ping my RPI. Allso with no sucess:

$this->bbcode_second_pass_code('', 'ping -c2 169.254.39.3
PING 169.254.39.3 (169.254.39.3) 56(84) bytes of data.
From 169.254.39.2 icmp_seq=1 Destination Host Unreachable
From 169.254.39.2 icmp_seq=2 Destination Host Unreachable

--- 169.254.39.3 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1007ms
pipe 2
')

Can anyone please suggest what am I doing wrong?

[WarheadsSE]

The latest images come with systemd-networkd + dhcp on eth0, did you disable that?

[71GA]

I only did what i wrote. So what do I have to do and how?

[71GA]

Now I get it. I have to somehow blacklist this two daemons (dhcpcd.service, systemctl-networkd.service) so they won't mess with the netctl? I know how to do that for modules (blacklist them in /etc/modprobe.d) but not for daemons at boot... It is easy if you can login and execute systemctl disable comand, but I can't do that...

I will somehow have to remove the SSH and modify some file in order to block systemd-networkd.service and dhcpcd.service at boot... Any sugestions?

Do I have to remove some sybolic link or something?

[WarheadsSE]

dhcpcd is not enabled. Just disable systemd-networkd

[71GA]

Ok. Thanks for pointint this out. So I disabled the systemd-networkd.service by deleting it from SSD card like this:

$this->bbcode_second_pass_code('', '
sudo rm /mnt/root/etc/systemd/system/multi-user.target.wants/systemd-networkd.service
')

Is this even the right way to disable it? Still i can't connect via ssh or ping my Raspberry PI:

$this->bbcode_second_pass_code('', '
sudo ssh root@169.254.39.3
ssh: connect to host 169.254.39.3 port 22: No route to host
[root@Ziga-laptop configure]# ping -c2 169.254.39.3
PING 169.254.39.3 (169.254.39.3) 56(84) bytes of data.
From 169.254.39.2 icmp_seq=1 Destination Host Unreachable
From 169.254.39.2 icmp_seq=2 Destination Host Unreachable

--- 169.254.39.3 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 999ms
pipe 2
')

[sdjf]

You might try rebooting after making all these changes, if a daemon is running, I don't think it is going to stop running just because you delete the stuff that started it running.