IMX233/ArchLinuxARM - Revision history

Xxcn: /* Generate a custom filesystem */

2013-05-06T21:27:41Z

‎Generate a custom filesystem

2013-05-06T21:25:07Z

‎Generate a custom filesystem

2013-05-06T20:08:28Z

‎Install the root filesystem

2013-05-06T19:49:52Z

‎Install the bootloader

2013-05-06T19:48:11Z

‎Install the root filesystem

2013-05-06T19:44:15Z

‎Partition the SD card

2013-05-06T19:41:07Z

‎ArchLinuxARM on iMX233-OLinuXino

2013-05-06T19:24:50Z

‎U-Boot enabled install

2013-05-06T19:10:17Z

‎The official image

2013-05-06T19:07:59Z

‎The official image

@@ Line 50: / Line 50: @@
 You can generate your own alarm root filesystem with the pacstrap tool. This can be done from within a running alarm installation, on an imx233-olinuxino, another more powerful board, or even from within qemu running alarm:
-  <nowiki> # as root
+  <nowiki># as root
 pacman -S arch-install-scripts
- # this creates the rootfs on a local disk, but the steps
+# this creates the rootfs on a local disk, but the steps
- # can be executed directly on a mounted sdcard partition
+# can be executed directly on a mounted sdcard partition
 mkdir rootfs
 pacstrap --help
@@ Line 60: / Line 60: @@
 # this will setup a new alarm root filesystem in ./rootfs and install the listed packages
 # this is possibly the absolute minimum for a working system with network
-pacstrap -cdGiM ./rootfs filesystem linux-olinuxino inetutils iputils nano vi netctl dialog openssh pacman ppp systemd-sysvcompat usbutils wireless_tools wpa_supplicant
+pacstrap -cdGiM ./rootfs filesystem linux-olinuxino \
 # install a custom kernel
 </nowiki>
 Beyond the bare minimum, you can install more packages to the newly created rootfs:
-  <nowiki>pacman -r ./rootfs -S bash-completion vim samba lighttpd git ...</nowiki>
+  <nowiki>pacman -r ./rootfs -S bash-completion vim samba lighttpd git</nowiki>

@@ Line 57: / Line 57: @@
 mkdir rootfs
 pacstrap --help
-pacstrap -cdGiM ./rootfs bash-completion cronie cryptsetup dhcpcd dialog inetutils iputils linux-olinuxino man-db man-pages nano netctl openssh pacman ppp systemd-sysvcompat usbutils vi  wireless_tools wpa_supplicant xfsprogs</nowiki>

@@ Line 45: / Line 45: @@
 tar -xzvpf ArchLinuxARM-olinuxino-latest.img.gz -C /mnt/rootfs
 sync
-umount /mnt/rootfs
+umount /mnt/rootfs</nowiki>
 ==== Generate a custom filesystem ====

@@ Line 33: / Line 33: @@
 Write it to the first partition at 2 kiB offset:
   <nowiki>dd if=u-boot.sb of=/dev/sdcardpartition_1 bs=512 seek=4</nowiki>
 === Install the root filesystem ===

@@ Line 36: / Line 36: @@
 === Install the root filesystem ===
-Download the [http://os.archlinuxarm.org/os/ArchLinuxARM-olinuxino-latest.img.gz rootfs tarball] from [http://os.archlinuxarm.org/os/ this listing on ofarchlinuxarm.org] and extract it on the mounted rootfs partition. It is important to do the extraction root, not with sudo.
+Download the [http://os.archlinuxarm.org/os/ArchLinuxARM-olinuxino-latest.img.gz rootfs tarball] from [http://os.archlinuxarm.org/os/ this listing on archlinuxarm.org] and extract it on the mounted rootfs partition. It is important to do the extraction root, not with sudo.
   <nowiki>wget http://os.archlinuxarm.org/os/ArchLinuxARM-olinuxino-latest.img.gz

@@ Line 17: / Line 17: @@
 === Partition the SD card ===
-Achieve the following partition layout:
+Achieve the following partition layout using parted, fdisk, cfdisk or something else:
   <nowiki>
     Device Boot      Start         End      Blocks   Id  System
@@ Line 23: / Line 23: @@
 /dev/sdd2            6144     3842047     1917952   83  Linux</nowiki>
-The first partition is of the special 0x53 type, used by the processor to boot. It will contain the bootloader and its environment.
+There are step by step instructions [http://www.eewiki.net/display/linuxonarm/iMX233-OLinuXino#iMX233-OLinuXino-SetupmicroSDcard here]. The first partition is of the special 0x53 type, 2 MiB are enough. It will contain the bootloader and its environment.
 The second is your rootfs partition. You may create additional ones if you like and edit  /etc/fstab to your liking.

@@ Line 25: / Line 25: @@
 The first partition is of the special 0x53 type, used by the processor to boot. It will contain the bootloader and its environment.
-The second is your root partition. You may create additional ones if you like.
+The second is your rootfs partition. You may create additional ones if you like and edit  /etc/fstab to your liking.
 === Install the bootloader ===
-Either find a prebuilt u-boot.sb file to flash, or follow the instructions [http://www.eewiki.net/display/linuxonarm/iMX233-OLinuXino#iMX233-OLinuXino-Bootloader here] to build one.
+Download a prebuilt u-boot.sb file or follow the instructions [http://www.eewiki.net/display/linuxonarm/iMX233-OLinuXino#iMX233-OLinuXino-Bootloader here] to build one.
-Write it to the first partition at 2 kb offset:
+Write it to the first partition at 2 kiB offset:
-  <nowiki>dd if=u-boot.sb of=/dev/yourfirstpartition bs=512 seek=4</nowiki>
+  <nowiki>dd if=u-boot.sb of=/dev/sdcardpartition_1 bs=512 seek=4</nowiki>
 === Install the root filesystem ===
 ==== Generate a custom filesystem ====

@@ Line 11: / Line 11: @@
 U-Boot makes the board much more hacker-friendly.
-== U-Boot enabled install ==
+== U-Boot install ==
 === Partition the SD card ===
 === Install the bootloader ===
 === Install the root filesystem ===

@@ Line 5: / Line 5: @@
 == The official image ==
-The easiest way to install alarm: just follow the [http://archlinuxarm.org/platforms/armv5/olinuxino official instructions]. The image is pre-partitioned and has everything in place. It uses bootlets, so any time the kernel cmdline or DT binary need to be changed the bootstream needs to be rebuilt and reflashed. It is essential that you hit "y" when asked "Do you want the new kernel flashed onto mmcblk0p1? [y|N]" when upgrading the kernel or installing a custom kernel package. U-Boot makes the board much more hacker-friendly.
+The easiest way to install alarm: just follow the [http://archlinuxarm.org/platforms/armv5/olinuxino official instructions]. The image is pre-partitioned and has everything in place. It uses bootlets, so any time the kernel cmdline or DT binary need to be changed the bootstream needs to be rebuilt and reflashed.
 == U-Boot enabled install ==