Serial of your pi can be found with this command: cat /sys/firmware/devicetree/base/serial-number|tail -c 9 Setup Mikrotik DHCP and optional TFTP server:ġ92.168.0.28 – is the TFTP server form linux, but you can use TFTP server that is already installed on mikrotik router.

Alternatively, you can debug/test the PXE boot with QEMU.*You also need another machine to provide NFS share. Now if you boot over PXE, you should eventually be awarded with a ‘Welcome to Arch Linux!’ message. INITRD boot/intel_ucode.img,boot/x86_64/archiso.imgĪPPEND archisobasedir = arch archiso_nfs_srv = $:/srv/archlinux MENU LABEL Boot Arch Linux (x86_64 ) (NFS ) It allows you to install Arch Linux or perform system maintenance. You need to also point the PXE/NFS -mount to that folder: $ grep -A10 arch64_nfs /srv/archlinux/boot/syslinux/archiso_pxe64.cfgīoot the Arch Linux (x86_64 ) live medium (Using NFS ). Raspberry: $ service rpcbind restart # This was needed on my raspbmc $ apt-get install nfs-kernel-server boot/syslinux/archiso.cfg pxelinux.cfg/defaultįinally, the root filesystem from the Arch image has to be transferred somehow. $ ln -s boot/syslinux/lpxelinux.0 pxelinux.0 $ cp -r /mnt/archlinux/arch/x86_64 /srv/archlinux/arch/ $ cp -r /mnt/archlinux/arch/boot /srv/archlinux/ One way of doing this is to just copy the contents of the image and modify them: $ mkdir -p /srv/archlinux This coupled with the obscure fact that dhcp-option-force seems not to work when running proxyDHCP leaves no option but to manually configure the PXE-boot options of the image. However, the default Arch Linux image has its boot configuration elsewhere than the pxelinux.cfg, which PXE boot will automatically look for. Pxe-service =x86PC, 'Boot from network', /pxelinux A typical configuration for PXE boot would look something like: $ grep '^' /etc/nfĭhcp-range =192.168.1.0,proxy,255.255.255.0 In this case, you can turn dnsmasq to behave as a proxyDHCP, effectively only serving the PXE-specific information to the client. Install dnsmasq: $ apt-get install dnsmasqĪs the case often is, there might already be a DHCP-server running in your intranet and you might not have root access to it. $ mount -o loop,ro archlinux-2015.02.01-dual.iso /mnt/archlinux Start by downloading the Arch Linux image to the raspberry and mounting it: $ wget Luckily, instead of installing separate packages of tftp-server and dhcpd in your setup, dnsmasq offers the whole PXE-boot functionality in one seemingly clean package.

PXE utilizes TFTP and DHCP to serve the installation media over the network. So over the weekend I had the great idea of reinstalling my Linux setup, mainly to incorporate LVM and LUKS to the installation from the get-go.Īnd as if installing and configuring a new *NIX environment is not time consuming enough, I decided to boot the installation image from PXE. Booting Arch Linux from PXE (Raspberry Pi)

Raspi tftp server starten