<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Project AmigaOne/Teron CX/PX Linux support</title><link>https://sourceforge.net/p/amigaone-linux/</link><description>Recent changes to Project AmigaOne/Teron CX/PX Linux support</description><atom:link href="https://sourceforge.net/p/amigaone-linux/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 25 Jan 2015 16:41:26 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/amigaone-linux/feed.rss" rel="self" type="application/rss+xml"/><item><title>Debian kernel packages now available in a Debian repository</title><link>https://sourceforge.net/p/amigaone-linux/news/2015/01/debian-kernel-packages-now-available-in-a-debian-repository/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There's now a Debian repository whose address can be added to your's system &lt;em&gt;/etc/apt/sources.list&lt;/em&gt; file to get all the Debian kernel packages provided for a specific Debian release. Please take a look at the readme text in the &lt;a class="" href="https://sourceforge.net/projects/amigaone-linux/files"&gt;Files&lt;/a&gt; section for more information.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Sun, 25 Jan 2015 16:41:26 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netfd436f7124d464b097fa366265056ed591e0fb62</guid></item><item><title>Debian_Linux_Kernel_Package_Installation modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/Debian_Linux_Kernel_Package_Installation/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v5
+++ v6
@@ -2,49 +2,79 @@

 Please take a look at the [amigaworld.net](http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;amp;topic_id=26623&amp;amp;forum=34&amp;amp;start=340&amp;amp;viewmode=flat&amp;amp;order=0#698652) forum for the installation instructions at the moment.

-This wiki article will be updated as soon as possible.
-
-[[download_button]]
-
-
-The following script can be used with the AmigaOne Debian kernel packages to build a suitable boot image that consists of the cuImage and a generated initrd image:
+However the following script can be used with the AmigaOne Debian kernel packages to build suitable boot images that consist of a cuImage and a generated initrd image:

 ~~~~~
 #!/bin/sh

 if [ -e "/etc/issue.net" ]; then
-    ISSUE=`cat /etc/issue.net`
+    issue=`cat /etc/issue.net`
 else
-    ISSUE="Linux boot image"
+    issue="Linux boot image"
 fi

+#
 # Generate boot images.
+#

-for CUIMAGE in /boot/cuImage.amigaone-*
-do
-    IMAGE=`mkimage -l "${CUIMAGE}"`
+for cuimage in /boot/cuImage.amigaone-*; do
+    image=`mkimage -l "$cuimage"`

-    COMP=`echo "${IMAGE}" | grep "uncompressed"`
-    LOADADDR=`echo "${IMAGE}" | grep "Load Address" | cut -f 3 -d ' '`
-    ENTRYADDR=`echo "${IMAGE}" | grep "Entry Point" | cut -f 4 -d ' '`
-    RAWCUIMAGE="/boot/cuImage.amigaone.img-${CUIMAGE#*-}"
-    INITRDIMG="/boot/initrd.img-${CUIMAGE#*-}"
-    BOOTIMG="/boot/boot.img.amigaone-${CUIMAGE#*-}"
+    compression=`echo "$image" | grep "uncompressed"`
+    #  could be replaced with 
+    loadaddr=`echo "$image" | grep "Load Address" | cut -f3 -d' '`
+    #  could be replaced with 
+    entryaddr=`echo "$image" | grep "Entry Point" | cut -f4 -d' '`
+    rawcuimage="/boot/cuImage.amigaone.img-${cuimage#*-}"
+    initrd="/boot/initrd.img-${cuimage#*-}"
+    bootimg="/boot/boot.img.amigaone-${cuimage#*-}"

-    if [ -z "${COMP}" ]; then
-        echo "Warning: ignoring ${CUIMAGE}, because it is a compressed image!"
+    if [ -z "$compression" ]; then
+        echo "Warning: ignoring ${cuimage}, because it is a compressed image!"
         continue
     fi
-    if [ ! -e "${RAWCUIMAGE}" ]; then
-        echo "Error: couldn't find raw image for ${CUIMAGE}!"
+    if [ ! -e "$rawcuimage" ]; then
+        echo "Error: couldn't find raw image for ${cuimage}!"
         continue
     fi
-    if [ ! -e "${INITRDIMG}" ]; then
-        echo "Error: couldn't find initrd image for ${CUIMAGE}!"
+    if [ ! -e "$initrd" ]; then
+        echo "Error: couldn't find initrd for ${cuimage}!"
         continue
     fi

-    mkimage -A ppc -O Linux -T multi -C none -a ${LOADADDR} -e ${ENTRYADDR} \
-        -n "${ISSUE}" -d "${RAWCUIMAGE}":"${INITRDIMG}" "${BOOTIMG}"
+    mkimage -A ppc -O Linux -T multi -C none -a $loadaddr -e $entryaddr \
+            -n "$issue" -d "$rawcuimage":"$initrd" "$bootimg"
 done
+
+#
+# Install boot images in corresponding boot directory.
+#
+
+# Gather UUID of root filesystem with blkid command.
+root=`mount | grep " / " | cut -d' ' -f1`
+fs=`blkid "$root" | cut -d' ' -f2- | tr -d '"'`
+
+installed=false
+
+for keyvalue in $fs; do
+    key=`echo "$keyvalue" | cut -d'=' -f1`
+    value=`echo "$keyvalue" | cut -d'=' -f2`
+
+    if [ "$key" = "UUID" ]; then
+        if [ -e "/boot/a1boot/${value}" ]; then
+            cp -a /boot/boot.img.amigaone-* "/boot/a1boot/${value}/"
+            installed=true
+            break
+        fi
+    fi
+done
+
+if ! $installed ; then
+    echo "Error: Couldn't find boot directory for this installation!"
+    exit 100
+fi
 ~~~~~
+
+This wiki article will be updated as soon as possible.
+
+[[download_button]]
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Wed, 21 Aug 2013 21:31:24 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6caabe552ace9a57a837b8728a94affc8d0e4b89</guid></item><item><title>Debian_Linux_Kernel_Package_Installation modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/Debian_Linux_Kernel_Package_Installation/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v4
+++ v5
@@ -5,6 +5,7 @@
 This wiki article will be updated as soon as possible.

 [[download_button]]
+

 The following script can be used with the AmigaOne Debian kernel packages to build a suitable boot image that consists of the cuImage and a generated initrd image:

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Fri, 16 Aug 2013 15:25:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netee2ba5f9562022c38d44850416738b3b5da53ca1</guid></item><item><title>Debian_Linux_Kernel_Package_Installation modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/Debian_Linux_Kernel_Package_Installation/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v3
+++ v4
@@ -5,3 +5,45 @@
 This wiki article will be updated as soon as possible.

 [[download_button]]
+
+The following script can be used with the AmigaOne Debian kernel packages to build a suitable boot image that consists of the cuImage and a generated initrd image:
+
+~~~~~
+#!/bin/sh
+
+if [ -e "/etc/issue.net" ]; then
+    ISSUE=`cat /etc/issue.net`
+else
+    ISSUE="Linux boot image"
+fi
+
+# Generate boot images.
+
+for CUIMAGE in /boot/cuImage.amigaone-*
+do
+    IMAGE=`mkimage -l "${CUIMAGE}"`
+
+    COMP=`echo "${IMAGE}" | grep "uncompressed"`
+    LOADADDR=`echo "${IMAGE}" | grep "Load Address" | cut -f 3 -d ' '`
+    ENTRYADDR=`echo "${IMAGE}" | grep "Entry Point" | cut -f 4 -d ' '`
+    RAWCUIMAGE="/boot/cuImage.amigaone.img-${CUIMAGE#*-}"
+    INITRDIMG="/boot/initrd.img-${CUIMAGE#*-}"
+    BOOTIMG="/boot/boot.img.amigaone-${CUIMAGE#*-}"
+
+    if [ -z "${COMP}" ]; then
+        echo "Warning: ignoring ${CUIMAGE}, because it is a compressed image!"
+        continue
+    fi
+    if [ ! -e "${RAWCUIMAGE}" ]; then
+        echo "Error: couldn't find raw image for ${CUIMAGE}!"
+        continue
+    fi
+    if [ ! -e "${INITRDIMG}" ]; then
+        echo "Error: couldn't find initrd image for ${CUIMAGE}!"
+        continue
+    fi
+
+    mkimage -A ppc -O Linux -T multi -C none -a ${LOADADDR} -e ${ENTRYADDR} \
+        -n "${ISSUE}" -d "${RAWCUIMAGE}":"${INITRDIMG}" "${BOOTIMG}"
+done
+~~~~~
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Fri, 16 Aug 2013 15:23:24 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0f1d6c365b9f8818e167002febcabc255bc060ab</guid></item><item><title>AmigaOne_Linux_Bootloader_Specification modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/AmigaOne_Linux_Bootloader_Specification/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v11
+++ v12
@@ -75,3 +75,10 @@
 ub2lb is also known as "parthenope" for ACube Systems' Sam boards.

 To be continued...
+
+Things to consider:
+
+* Use root filesystem UUID as name for subdirectory?
+- Use dpkg-divert to rename kernel images to subdirectory?
+- Can the System.map and kernel config file be found on booting?
+- Can the vmlinuz file be found on a kexec event?
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Thu, 11 Jul 2013 18:45:52 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netcae45933ecbfe8d5eaa883850efd721dfebdc444</guid></item><item><title>AmigaOne_Linux_Bootloader_Specification modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/AmigaOne_Linux_Bootloader_Specification/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v10
+++ v11
@@ -1,4 +1,8 @@
 # AmigaOne Linux Bootloader Specification #
+
+## Preface ##
+
+This documents describes the bootloaders available on the AmigaOne platform to boot Linux. Furthermore a common rule set is specified based on the usage and restrictions of the bootloaders, which can be used to implement corresponding Debian bootloader packages. These bootloades packages should largely free the user from manual intervention, whenever an installation is made bootable or the boot configuration is changed due to system upgrades.

 ## Available Bootloaders for the AmigaOne ##

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Sat, 13 Apr 2013 16:02:32 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net4edf8d60474ac40f7900b235cd1de63742373f50</guid></item><item><title>AmigaOne_Linux_Bootloader_Specification modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/AmigaOne_Linux_Bootloader_Specification/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v9
+++ v10
@@ -41,12 +41,30 @@

 ~~~~~~
 ; Comments start with a semicolon
-boot_entry_name /path/to/bootimage kernel option1 option2 option3...
+boot-entry-name /path/to/bootimage kernel option1 option2 option3...
 ~~~~~~

-The `` should not contain any spaces or tabs, as parts of it would otherwise be interpreted as path to the boot image. While the bootloader does not restrict the length of the boot entry name in the configuration file, it also only provides limited space in the boot menu to display the boot entry name. Thus the name should be kept relatively short so that the user can read the full name.
+The `` should not contain any spaces or tabs, as parts of it would otherwise be interpreted as path to the boot image or kernel options. While the bootloader does not seem to restrict the length of the boot entry name in the configuration file, the name should not be longer than approximately 60 characters. Nevertheless this should be enough to give the boot entry a unique name. For example:

-Least but not least the number of displayed boot entries is limited to around 16 entries, because the booloader doesn't scroll the list. However it still allows to select invisible boot entries.
+~~~~~~
+Debian-Squeeze-3.2.0-0.bpo.4-book3s.amigaone+-recovery-sda5
+~~~~~~
+
+Where:
+
+* "Debian" is the vendor of the installed distribution,
+- "Squeeze" is the distribution's release codename,
+- "3.2.0-0.bpo.4-book3s.amigaone+" is the kernel version used to boot the installation,
+- "recovery" is an optional part, which specifies a runlevel used for system recovery and
+- "sda5" is an another optional part used to distinguish installations, if there are multiple installations of the exact same distribution.
+
+Alternatively a release number may be used instead of the release codename:
+
+~~~~~~
+Ubuntu-10.04-3.2.0-0.bpo.4-book3s.amigaone+
+~~~~~~
+
+Least but not least the number of displayed boot entries is limited to around 16 entries, because the booloader doesn't scroll the list. However it allows to select invisible boot entries.

 #### ub2lb ####

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Sat, 13 Apr 2013 11:11:49 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net06092cd478fc083af54edcbe53de0e3bf6defb5c</guid></item><item><title>AmigaOne_Linux_Bootloader_Specification modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/AmigaOne_Linux_Bootloader_Specification/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v8
+++ v9
@@ -29,13 +29,13 @@
     The bootloader only seems to scan for Linux partitions after it found a first AmigaOS4 partition. Therefore the best approach is to put the Linux boot partition right after the AmigaOS4 Workbench partition, which is usually the first partition on the first harddisk.

 + the boot partition is formatted as ext2 or ext3 filesystem
-    The bootloader can read ext2/3 filesystems with a fixed inode size of 128 bytes. Support for larger inode sizes in the ext2/3 filesystem was added in kernel 2.6.10 and thus succeeds the slb_v2 bootloader. mke2fs creates 256 bytes inodes by default nowadays, thus the inode size has to be explicitly forced for the file system of the boot partition:
+    The bootloader can read ext2/3 filesystems with a **fixed inode size of 128 bytes**. Support for larger inode sizes in the ext2/3 filesystem was added in kernel 2.6.10 and thus succeeds the slb_v2 bootloader. Most distributions configure mke2fs (in /etc/mke2fs.conf) to create 256 bytes inodes by default nowadays, thus the inode size has to be explicitly forced for the file system of the boot partition:

     ~~~~~~
     $ mkfs.ext3 -I 128 /dev/sdxy
     ~~~~~~

-    Other block sizes or filesystem features like dir_index, ext_attr, filetype, large_file and resize_inode don't seem to confuse the bootloader. Features like extent, flex_bg and journal_dev haven't been tested so far. However they are either ext4 specific or generally not enabled by default in /etc/mke2fs.conf.
+    Other block sizes or filesystem features like dir_index, ext_attr, filetype, large_file and resize_inode don't seem to confuse the bootloader. Features like extent, flex_bg and journal_dev haven't been tested so far. However they are either ext4 specific, or generally not enabled by default in /etc/mke2fs.conf.

 As mentioned above the slb_v2 reads a single configuration file, where every non-commented line is a separate boot entry. A boot entry itself is specified in this format:

@@ -52,4 +52,4 @@

 ub2lb is also known as "parthenope" for ACube Systems' Sam boards.

-
+To be continued...
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Sat, 13 Apr 2013 10:19:42 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netfa0e57b09bfeaf4f6345609322ccc4fc48583368</guid></item><item><title>WikiPage AmigaOne_Linux_Bootloader_Specification modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/AmigaOne_Linux_Bootloader_Specification/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v7
+++ v8
@@ -29,7 +29,7 @@
     The bootloader only seems to scan for Linux partitions after it found a first AmigaOS4 partition. Therefore the best approach is to put the Linux boot partition right after the AmigaOS4 Workbench partition, which is usually the first partition on the first harddisk.

 + the boot partition is formatted as ext2 or ext3 filesystem
-    The bootloader can read ext2 and ext3 filesystems with a fixed inode size of 128 bytes. Support for larger inode sizes in the ext2/3 filesystem was added in kernel 2.6.10 and thus came after the slb_v2 bootloader was written. mke2fs creates 256 bytes inodes by default nowadays, thus the inode size has to be explicitly forced for the file system of the boot partition:
+    The bootloader can read ext2/3 filesystems with a fixed inode size of 128 bytes. Support for larger inode sizes in the ext2/3 filesystem was added in kernel 2.6.10 and thus succeeds the slb_v2 bootloader. mke2fs creates 256 bytes inodes by default nowadays, thus the inode size has to be explicitly forced for the file system of the boot partition:

     ~~~~~~
     $ mkfs.ext3 -I 128 /dev/sdxy
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Thu, 28 Mar 2013 19:49:16 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net8961f608ccd2bea199183aed63ef97db68efd842</guid></item><item><title>WikiPage AmigaOne_Linux_Bootloader_Specification modified by Gerhard Pircher</title><link>https://sourceforge.net/p/amigaone-linux/wiki/AmigaOne_Linux_Bootloader_Specification/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v6
+++ v7
@@ -29,7 +29,13 @@
     The bootloader only seems to scan for Linux partitions after it found a first AmigaOS4 partition. Therefore the best approach is to put the Linux boot partition right after the AmigaOS4 Workbench partition, which is usually the first partition on the first harddisk.

 + the boot partition is formatted as ext2 or ext3 filesystem
-    Generally ext2 should be preferred for the boot partition to avoid compatibility issues with newer ext3 features. However the slb_v2 bootloader sometimes even misses properly formatted ext2 boot partitions and thus doesn't show any Linux boot entries in its boot menu. It is suspected that this may have to do something with the version of the mk2fs command used to format the partition, but investigations are still ongoing.
+    The bootloader can read ext2 and ext3 filesystems with a fixed inode size of 128 bytes. Support for larger inode sizes in the ext2/3 filesystem was added in kernel 2.6.10 and thus came after the slb_v2 bootloader was written. mke2fs creates 256 bytes inodes by default nowadays, thus the inode size has to be explicitly forced for the file system of the boot partition:
+
+    ~~~~~~
+    $ mkfs.ext3 -I 128 /dev/sdxy
+    ~~~~~~
+
+    Other block sizes or filesystem features like dir_index, ext_attr, filetype, large_file and resize_inode don't seem to confuse the bootloader. Features like extent, flex_bg and journal_dev haven't been tested so far. However they are either ext4 specific or generally not enabled by default in /etc/mke2fs.conf.

 As mentioned above the slb_v2 reads a single configuration file, where every non-commented line is a separate boot entry. A boot entry itself is specified in this format:

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerhard Pircher</dc:creator><pubDate>Thu, 28 Mar 2013 19:41:30 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net83da3f67fa82447423cc3e3ae2d667dbb562159f</guid></item></channel></rss>