Page 1 of 1
arch won't boot after install via PINN
Posted: Mon Feb 13, 2017 6:36 pm
by carsten888
I want to install Arch on pi2. I installed it via PINN. Installation went fine, but after reboot nothing happens. PI2 gives red led light.
Is there an .img I can download of arch for pi2?
How to fix this?
Re: arch won't boot after install via PINN
Posted: Mon Feb 13, 2017 10:58 pm
by fruitoftheloom
carsten888 wrote:I want to install Arch on pi2. I installed it via PINN. Installation went fine, but after reboot nothing happens. PI2 gives red led light.
Is there an .img I can download of arch for pi2?
How to fix this?
Welcome, Arch Linux Arm stopped offering .IMG files a lomg time ago. They assume you have a Linux Machine to create a bootable SD Card:
https://archlinuxarm.org/platforms/armv ... berry-pi-2
Though I am surprised you are unable to get PINN to function, therefore if you provide details of what RPi 2B revision you have, hopefully the developer can look into whether it is a PINN issue or not:
http://elinux.org/RPi_HardwareHistory
viewtopic.php?f=63&t=142574
Re: arch won't boot after install via PINN
Posted: Mon Feb 13, 2017 11:58 pm
by procount
Hmmm that's surprising. It worked last time I tried it.
The Arch image I use for PINN is the one published directly on the Archlinuxarm website (so the same one you would use if you installed it manually), but it is constantly changing.
I'll do a retest and make sure it is currently working.
Edit: I just tried installing Arch with PINN on a Pi3B and it worked fine.
Re: arch won't boot after install via PINN
Posted: Tue Feb 14, 2017 7:51 am
by carsten888
I've seen that, but am on windows, so downloaded from the url at 5, unpacked and wacked that on the sd card. same result.
Though I am surprised you are unable to get PINN to function
PINN worked. I got an alert on boot telling me some txt file could not be read. But then it installed arch no prob.
OOOPS.
I think I'm on to something... On further inspection it turns out to be a raspberry pi 1 model b. Might that be why its not correctly installing/running?

Re: arch won't boot after install via PINN
Posted: Tue Feb 14, 2017 8:41 am
by procount
Unless you modified the cmdline, PINN will only show you the OSes suitable for your model of Pi, so Arch1 for Pi1, B+ and PiZero, Arch2 for Pi2 & Pi3.
Re: arch won't boot after install via PINN
Posted: Tue Feb 14, 2017 5:12 pm
by carsten888
3 hours working on this, stuck at step 2 from this tut.
https://archlinuxarm.org/platforms/armv ... berry-pi-2
Code: Select all
First sector (2048-3963204, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-3963204, default 3963204): +100M
Created a new partition 1 of type 'Linux' and of size 100 MiB.
Command (m for help): t
Selected partition 1
Partition type (type L to list all types): c
Changed type of partition 'Linux' to 'W95 FAT32 (LBA)'.
Command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2): 2
First sector (206848-3963204, default 206848):
Last sector, +sectors or +size{K,M,G,T,P} (206848-3963204, default 3963204):
Created a new partition 2 of type 'Linux' and of size 1.8 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Invalid argument
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
mint@mint ~ $ mkfs.vfat /dev/mmcblk0p1
mkfs.fat 3.0.28 (2015-05-16)
/dev/mmcblk0p1: Permission denied
mint@mint ~ $ sudo mkfs.vfat /dev/mmcblk0p1
mkfs.fat 3.0.28 (2015-05-16)
mkfs.vfat: /dev/mmcblk0p1 contains a mounted filesystem.
mint@mint ~ $ mkdir boot
mint@mint ~ $ mount /dev/mmcblk0p1 boot
mount: only root can do that
mint@mint ~ $ root
The program 'root' is currently not installed. You can install it by typing:
sudo apt install root-system-bin
What for the life of me am I doing wrong?
Re: arch won't boot after install via PINN
Posted: Wed Feb 15, 2017 4:45 am
by fruitoftheloom
Total and utterly confused as you now state you have a Raspberry Pi 1 but following a Raspberry Pi 2 Tutorial !!
Also you need a Linux Operating System to create a bootable SD Card:
https://archlinuxarm.org/platforms/armv6/raspberry-pi
Re: arch won't boot after install via PINN
Posted: Wed Feb 15, 2017 6:34 am
by carsten888
sorry, posted wrong link. I did indeed this one for pi 1
https://archlinuxarm.org/platforms/armv6/raspberry-pi
I used a linux mint cd to do this. Might that be why its not doing its thing?
Re: arch won't boot after install via PINN
Posted: Wed Feb 15, 2017 7:35 pm
by pepedog
Maybe mint is automounting things?
Re: arch won't boot after install via PINN
Posted: Thu Feb 16, 2017 12:33 am
by ktb
Pepedog makes a good point, but if the following is the error, then use 'sudo' as in
sudo mount /dev/mmcblk0p1 boot. Before you run the commands which follow partitioning the card with fdisk, just make sure the partition is unmounted by using
sudo umount /dev/mmcblk0p1
BTW, are you sure the sd card is located at /dev/mmcblk0 and not something like /dev/sda or /dev/sdb? Just checking...
Code: Select all
mint@mint ~ $ mkdir boot
mint@mint ~ $ mount /dev/mmcblk0p1 boot
mount: only root can do that
mint@mint ~ $ root
The program 'root' is currently not installed. You can install it by typing:
sudo apt install root-system-bin
The Arch Linux ARM RPI installation instructions have always been poor in that whoever wrote them assumes a user knows which of those commands require root privileges. I suppose you trying to use a non-existent 'root' command was just you guessing and giving it your best shot.
Re: arch won't boot after install via PINN
Posted: Mon Feb 20, 2017 4:03 pm
by carsten888
tried again. Now I'm stuck on 2c.
2. At the fdisk prompt, delete old partitions and create a new one:
a. Type o. This will clear out any partitions on the drive.
b. Type p to list partitions. There should be no partitions left.
c. Type n, then p for primary, 1 for the first partition on the drive, press ENTER to accept the default first sector, then type +100M for the last sector.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-204799, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-204799, default 204799): +100m
Value out of range.
Last sector, +sectors or +size{K,M,G,T,P} (2048-204799, default 204799): +100M
Value out of range.
It won't accept +100M.
Re: arch won't boot after install via PINN
Posted: Mon Feb 20, 2017 7:48 pm
by ktb
Alright, I'll run through the steps on Ubuntu 17.04. I'll update this post.
Code: Select all
ktb@KTBMacMini:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop1 7:1 0 76.7M 0 loop /snap/core/1079
loop3 7:3 0 76M 0 loop /snap/core/1222
loop4 7:4 0 76M 0 loop /snap/core/1240
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 200M 0 part /boot/efi
├─sda2 8:2 0 46.6G 0 part
├─sda3 8:3 0 229.7G 0 part
├─sda4 8:4 0 619.9M 0 part
├─sda5 8:5 0 619.9M 0 part
├─sda6 8:6 0 619.9M 0 part
├─sda7 8:7 0 619.9M 0 part
├─sda8 8:8 0 177G 0 part /
└─sda9 8:9 0 9.3G 0 part [SWAP]
sdb 8:16 1 14.9G 0 disk
sr0 11:0 1 1024M 0 rom
ktb@KTBMacMini:~$ sudo fdisk /dev/sdb
Welcome to fdisk (util-linux 2.29).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): o
Created a new DOS disklabel with disk identifier 0x3ee40bfb.
Command (m for help): p
Disk /dev/sdb: 14.9 GiB, 16021192704 bytes, 31291392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3ee40bfb
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-31291391, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-31291391, default 31291391): +100M
Created a new partition 1 of type 'Linux' and of size 100 MiB.
Command (m for help): t
Selected partition 1
Partition type (type L to list all types): c
Changed type of partition 'Linux' to 'W95 FAT32 (LBA)'.
Command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2): 2
First sector (206848-31291391, default 206848):
Last sector, +sectors or +size{K,M,G,T,P} (206848-31291391, default 31291391):
Created a new partition 2 of type 'Linux' and of size 14.8 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
ktb@KTBMacMini:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop1 7:1 0 76.7M 0 loop /snap/core/1079
loop3 7:3 0 76M 0 loop /snap/core/1222
loop4 7:4 0 76M 0 loop /snap/core/1240
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 200M 0 part /boot/efi
├─sda2 8:2 0 46.6G 0 part
├─sda3 8:3 0 229.7G 0 part
├─sda4 8:4 0 619.9M 0 part
├─sda5 8:5 0 619.9M 0 part
├─sda6 8:6 0 619.9M 0 part
├─sda7 8:7 0 619.9M 0 part
├─sda8 8:8 0 177G 0 part /
└─sda9 8:9 0 9.3G 0 part [SWAP]
sdb 8:16 1 14.9G 0 disk
├─sdb1 8:17 1 100M 0 part
└─sdb2 8:18 1 14.8G 0 part
sr0 11:0 1 1024M 0 rom
ktb@KTBMacMini:~$ sudo mkfs.vfat /dev/sdb1
mkfs.fat 4.0 (2016-05-06)
ktb@KTBMacMini:~$ mkdir boot
ktb@KTBMacMini:~$ sudo mount /dev/sdb1 boot
ktb@KTBMacMini:~$ sudo mkfs.ext4 /dev/sdb2
mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 3885568 4k blocks and 972944 inodes
Filesystem UUID: 3b427c3d-e674-490b-88e5-d0a497b78301
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
ktb@KTBMacMini:~$ mkdir root
ktb@KTBMacMini:~$ sudo mount /dev/sdb2 root
ktb@KTBMacMini:~$ wget http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz
--2017-02-20 15:01:33-- http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz
Resolving os.archlinuxarm.org (os.archlinuxarm.org)... 50.116.36.110
Connecting to os.archlinuxarm.org (os.archlinuxarm.org)|50.116.36.110|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://co.us.mirror.archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz [following]
--2017-02-20 15:01:33-- http://co.us.mirror.archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz
Resolving co.us.mirror.archlinuxarm.org (co.us.mirror.archlinuxarm.org)... 72.13.197.87
Connecting to co.us.mirror.archlinuxarm.org (co.us.mirror.archlinuxarm.org)|72.13.197.87|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 294803039 (281M) [application/x-gzip]
Saving to: ‘ArchLinuxARM-rpi-latest.tar.gz’
ArchLinuxARM-rpi-latest.tar 100%[========================================>] 281.15M 18.0MB/s in 16s
2017-02-20 15:01:50 (17.5 MB/s) - ‘ArchLinuxARM-rpi-latest.tar.gz’ saved [294803039/294803039]
ktb@KTBMacMini:~$ sudo bsdtar -xpf ArchLinuxARM-rpi-latest.tar.gz -C root
ktb@KTBMacMini:~$ sudo sync
ktb@KTBMacMini:~$ sudo mv root/boot/* boot
ktb@KTBMacMini:~$ sudo sync
ktb@KTBMacMini:~$ sudo umount boot root
ktb@KTBMacMini:~$ rm -r boot root