Architectures/ARM/Trimslice

From FedoraProject

< Architectures | ARM(Difference between revisions)
Jump to: navigation, search
 
(Upgrading to the 3.7 Kernel)
(21 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[File:pandastack2.jpg|right|200px|thumb|A Pandastack used at Seneca College to build Fedora 17 GA. There are eleven stacked Pandaboards in this configuration]]
+
[[Category:Fedora ARM]][[Category:Fedora 17 GA]][[Category:Fedora ARM Hardware]]
 +
[[File:fedora-trimslice.jpg|right|300px|thumb|A Trimslice proudly wearing a "Powered by Fedora" case badge.]]
 
=Trimslice=
 
=Trimslice=
The Trimslice is one of the most popular ARM devices available and provides users with a very powerful ARM device for use on the network.  
+
The Trimslice is one of the most powerful ARM devices available and features a variety of connectivity options. At this time there is no support for a display and the Trimslice boots to a serial console.
 
===Technical Specifications===
 
===Technical Specifications===
 
* 1 GHz  NVIDA Tegra 2 (dual-core ARM Cortex A9)
 
* 1 GHz  NVIDA Tegra 2 (dual-core ARM Cortex A9)
 
* 1 GB DDR2-667 RAM
 
* 1 GB DDR2-667 RAM
* HDMI 1080P capable
+
* HDMI 1.3 max resolution 1920 x 1080
 
* Gigabit Ethernet (Realtek RTL8111DL)
 
* Gigabit Ethernet (Realtek RTL8111DL)
* 802.11n Wireless connectivity
+
* 802.11 b/g/n WiFi
  
 
For more information on the Trimslice visit their [http://trimslice.com website].
 
For more information on the Trimslice visit their [http://trimslice.com website].
Line 13: Line 14:
 
= Running Fedora on a Trimslice =
 
= Running Fedora on a Trimslice =
  
This page will give you detailed instructions for running Fedora 17 GA on your Trimslice. There are two images to choose from on the Trimslice, choose the appropriate image for your target media - SD card or SATA/USB drive.
+
This page will give you detailed instructions for running Fedora 17 GA on your Trimslice. There are two images to choose from on the Trimslice please choose the appropriate image for your target media - SD card or SATA/USB drive.
  
 
= Download the image =
 
= Download the image =
The first step is to download the Fedora 17 image. The prebuilt images include kernels and can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Both images require a minimum of 2GB and boot to a serial console.
+
The first step is to download the Fedora 17 image. The prebuilt images include kernels and can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Both images require a minimum of 2GB and boots to a serial console.
  
* [http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0.img.xz SD Image]
+
* [http://secondary.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0.img.xz SD Image]
* [http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda.img.xz SATA/USB Image]
+
* [http://secondary.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda.img.xz SATA/USB Image]
  
 
=Writing the Image=
 
=Writing the Image=
 
===Linux Users===
 
===Linux Users===
You can write the image to media of your choosing but it does have to meet the minimum size requirements noted above (2GB for the serial image, 4GB for the XFCE Desktop). Connect the media to your computer and make note of the drive. To write the image to your media run the following command, changing the drive to the location of your media.  
+
You can write the image to media of your choosing but it does have to meet the minimum size requirement of 2GB. Connect the media to your computer and make note of the drive. To write the image to your media run the following command, changing the drive to the location of your media.  
  
 
For the SD Image:
 
For the SD Image:
  xzcat Fedora-17-armhfp-trimslice-mmcblk0.img.xz> /dev/<location-of-your-media>
+
  xzcat Fedora-17-armhfp-trimslice-mmcblk0.img.xz> /dev/<location-of-your-SD-card>
  
 
For the SATA/USB Image:
 
For the SATA/USB Image:
  xzcat Fedora-17-armhfp-trimslice-sda.img.xz > /dev/<location-of-your-media>
+
  xzcat Fedora-17-armhfp-trimslice-sda.img.xz > /dev/<location-of-your-SATA/USB>
  
 
Once completed run the below command to ensure the entire image is written to the device:
 
Once completed run the below command to ensure the entire image is written to the device:
 
  sync
 
  sync
 +
 
===Windows Users===
 
===Windows Users===
 
* You will need to download [https://launchpad.net/win32-image-writer  Win32 Image Writer] as well as a tool to extract the image such as [http://www.7-zip.org 7-Zip].
 
* You will need to download [https://launchpad.net/win32-image-writer  Win32 Image Writer] as well as a tool to extract the image such as [http://www.7-zip.org 7-Zip].
 
* Once downloaded and installed right click on the disk image and select "7-Zip->Extract files here"
 
* Once downloaded and installed right click on the disk image and select "7-Zip->Extract files here"
 
* Launch Win 32 Disk Imager and select the extracted disk image and the device you would like to write the files to. Click "Write". Be very careful during this step - all data on the selected drive will be lost!
 
* Launch Win 32 Disk Imager and select the extracted disk image and the device you would like to write the files to. Click "Write". Be very careful during this step - all data on the selected drive will be lost!
 +
===Mac Users===
 +
* Please note that the Default Archive Utility.app will not extract the .xz file. A third party app will have to be used to decompress it. There are multiple options for that
 +
*# There is a Free App available in the App Store called Unarchiver.
 +
*# If [http://mxcl.github.com/homebrew/ mac homebrew] or [http://www.macports.org macport] is already installed, then the xz utility can be downloaded and installed using one of those.
 +
*# The xz utils .pkg for mac can be downloaded and installed directly from [http://tukaani.org/xz/ xz utils]
 +
* Once the xz utility is installed, open a terminal and make a note of the current drives.
 +
ls /dev/disk?
 +
* Connect the SD card to the mac and make a note of the drive.
 +
* Open Disk Utility and make sure that the card and all the partitions in the card (if any) is unmounted
 +
* In the terminal change to the directory where the .xz file is located
 +
* If xz was installed from the .pkg or macport or homebrew then run the following command
 +
xzcat Fedora-17-armhfp-trimslice-mmcblk0.img.xz > /dev/<location-of-the-SD-card>
 +
* If the Unarchiver app from App Store was used then just click and decompress the .xz file and then run the following (may require ''sudo'')
 +
dd if=Fedora-17-armhfp-trimslice-mmcblk0.img.xz of=/dev/<location-of-the-SD-card>
 +
* Click and eject the SD card
  
 
=Using Fedora on the Trimslice=
 
=Using Fedora on the Trimslice=
Connect the newly created media to your Trimslice and power on. No further steps are required and your system should boot to a serial console log in prompt. If you do not have a serial cable to connect your Trimslice, you can watch you DHCP server for the newly connected device. After a few minutes you should be able to see the host "fedora-arm'. Use SSH to connect to the root account.
+
Connect the newly created media to your Trimslice and power on. No further steps are required and your system should boot to a serial console log in prompt. If you do not have a serial cable to connect your Trimslice, you can watch your DHCP server for the newly connected device. After a few minutes you should be able to see the host "fedora-arm'. Use SSH to connect to the root account.
 
  ssh root@fedora-arm (or IP)
 
  ssh root@fedora-arm (or IP)
The default root password is "fedoraarm". This should be changed immediately.  
+
The default root password is "fedoraarm". This should be changed immediately.
 +
==Known Issues==
 +
* Yum requires the system time be correct for HTTPS to function.  If yum updates are not working check your clock.
 +
* The tar.xz rootfs archives do not preserve SELinux information or file capabilities.  If you use these to create your own filesystem image it is recommended that you switch SELinux to use warnings instead of enforcing for first boot, then relabel and reinstall packages that rely upon filesystem capabilities such as glibc-common and ping.
 +
* Images are designed to be written to a minimum of 2GB SD cards, SATA Disks, and SSD drives. On first boot the partition will be resized to the maximum allowable amount.  On the second boot the filesystem will be resized to fill the expanded partition.  This works for SD cards, SATA Disks, and SSD drives.
 +
* [[Common_F17_bugs|Known release issues]]
 +
==Upgrading to the 3.7 Kernel==
 +
In order to upgrade to the 3.7 kernel is Fedora 17 you will need to first make some manual changes to your configuration.
 +
* Change the load address for the initramfs (uInitrd) to accommodate larger kernels.
 +
*Boot up the Trimslice and install the 3.7 kernel from updates. Do not reboot the system until you make the following changes.
 +
<pre>yum update kernel-tegra</pre>
 +
* Change to the boot directory and use your favorite editor to edit '/boot/armhfp-trimslice-sda-<mmc/usb>-boot.cmd.(Note you will need to choose the appropriate file depending on your boot device, mmc or usb).
 +
<pre>
 +
setenv bootargs console=${console} root=LABEL=rootfs ro rootwait
 +
ext2load usb 0:1 4880000 uInitrd-tegra
 +
ext2load usb 0:1 4080000 uImage-tegra
 +
ext2load usb 0:1 5880000 dtbs/tegra20-trimslice.dtb
 +
bootm 4080000 4880000 5880000
 +
</pre>
 +
* Regenerate the boot script by running the following command:
 +
mkimage -A arm -O linux -T script -C none -d armhfp-trimslice-sda-usb-boot.cmd armhfp-trimslice-sda-usb-boot.scr
 +
* Copy the boot script to be used on the next boot:
 +
cp armhfp-trimslice-sda-usb-boot.scr boot.scr
 +
* A Trimslice Device Tree Binary (.dtb) available here [http://ausil.us/dtb/3.7/tegra20-trimslice.dtb tegra20-trimslice.dtb].
 +
mkdir -p /boot/dtbs
 +
cd /boot/dtbs
 +
wget http://ausil.us/dtb/3.7/tegra20-trimslice.dtb
 +
* Shutdown the system.
 +
* Upgrade to a new version of U-Boot ([http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#v2012.04-1.01 U-Boot 2012.04.01-1.01]). Follow the instructions on the Trimslice Wiki.
 +
* Once completed, your system will now boot to the 3.7 kernel.
  
=Additional Support=
+
= Additional Support =  
There are Fedora ARM users all around the globe - if you need assistance, would like to provide feedback or contribute to Fedora ARM please visit us on the IRC - we can be found in #fedora-arm on Freenode. You can also contact us on the mailing list - arm@lists.fedoraproject.org
+
There are Fedora ARM users all around the globe - if you need assistance, would like to provide feedback or contribute to Fedora ARM please visit us on the IRC - we can be found in {{fpchat|#fedora-arm}} on Freenode. You can also contact us on the mailing list - {{fplist|arm}}

Revision as of 22:04, 19 February 2013

A Trimslice proudly wearing a "Powered by Fedora" case badge.

Contents

Trimslice

The Trimslice is one of the most powerful ARM devices available and features a variety of connectivity options. At this time there is no support for a display and the Trimslice boots to a serial console.

Technical Specifications

  • 1 GHz NVIDA Tegra 2 (dual-core ARM Cortex A9)
  • 1 GB DDR2-667 RAM
  • HDMI 1.3 max resolution 1920 x 1080
  • Gigabit Ethernet (Realtek RTL8111DL)
  • 802.11 b/g/n WiFi

For more information on the Trimslice visit their website.

Running Fedora on a Trimslice

This page will give you detailed instructions for running Fedora 17 GA on your Trimslice. There are two images to choose from on the Trimslice please choose the appropriate image for your target media - SD card or SATA/USB drive.

Download the image

The first step is to download the Fedora 17 image. The prebuilt images include kernels and can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Both images require a minimum of 2GB and boots to a serial console.

Writing the Image

Linux Users

You can write the image to media of your choosing but it does have to meet the minimum size requirement of 2GB. Connect the media to your computer and make note of the drive. To write the image to your media run the following command, changing the drive to the location of your media.

For the SD Image:

xzcat Fedora-17-armhfp-trimslice-mmcblk0.img.xz> /dev/<location-of-your-SD-card>

For the SATA/USB Image:

xzcat Fedora-17-armhfp-trimslice-sda.img.xz > /dev/<location-of-your-SATA/USB>

Once completed run the below command to ensure the entire image is written to the device:

sync

Windows Users

  • You will need to download Win32 Image Writer as well as a tool to extract the image such as 7-Zip.
  • Once downloaded and installed right click on the disk image and select "7-Zip->Extract files here"
  • Launch Win 32 Disk Imager and select the extracted disk image and the device you would like to write the files to. Click "Write". Be very careful during this step - all data on the selected drive will be lost!

Mac Users

  • Please note that the Default Archive Utility.app will not extract the .xz file. A third party app will have to be used to decompress it. There are multiple options for that
    1. There is a Free App available in the App Store called Unarchiver.
    2. If mac homebrew or macport is already installed, then the xz utility can be downloaded and installed using one of those.
    3. The xz utils .pkg for mac can be downloaded and installed directly from xz utils
  • Once the xz utility is installed, open a terminal and make a note of the current drives.
ls /dev/disk?
  • Connect the SD card to the mac and make a note of the drive.
  • Open Disk Utility and make sure that the card and all the partitions in the card (if any) is unmounted
  • In the terminal change to the directory where the .xz file is located
  • If xz was installed from the .pkg or macport or homebrew then run the following command
xzcat Fedora-17-armhfp-trimslice-mmcblk0.img.xz > /dev/<location-of-the-SD-card>
  • If the Unarchiver app from App Store was used then just click and decompress the .xz file and then run the following (may require sudo)
dd if=Fedora-17-armhfp-trimslice-mmcblk0.img.xz of=/dev/<location-of-the-SD-card>
  • Click and eject the SD card

Using Fedora on the Trimslice

Connect the newly created media to your Trimslice and power on. No further steps are required and your system should boot to a serial console log in prompt. If you do not have a serial cable to connect your Trimslice, you can watch your DHCP server for the newly connected device. After a few minutes you should be able to see the host "fedora-arm'. Use SSH to connect to the root account.

ssh root@fedora-arm (or IP)

The default root password is "fedoraarm". This should be changed immediately.

Known Issues

  • Yum requires the system time be correct for HTTPS to function. If yum updates are not working check your clock.
  • The tar.xz rootfs archives do not preserve SELinux information or file capabilities. If you use these to create your own filesystem image it is recommended that you switch SELinux to use warnings instead of enforcing for first boot, then relabel and reinstall packages that rely upon filesystem capabilities such as glibc-common and ping.
  • Images are designed to be written to a minimum of 2GB SD cards, SATA Disks, and SSD drives. On first boot the partition will be resized to the maximum allowable amount. On the second boot the filesystem will be resized to fill the expanded partition. This works for SD cards, SATA Disks, and SSD drives.
  • Known release issues

Upgrading to the 3.7 Kernel

In order to upgrade to the 3.7 kernel is Fedora 17 you will need to first make some manual changes to your configuration.

  • Change the load address for the initramfs (uInitrd) to accommodate larger kernels.
  • Boot up the Trimslice and install the 3.7 kernel from updates. Do not reboot the system until you make the following changes.
yum update kernel-tegra
  • Change to the boot directory and use your favorite editor to edit '/boot/armhfp-trimslice-sda-<mmc/usb>-boot.cmd.(Note you will need to choose the appropriate file depending on your boot device, mmc or usb).
setenv bootargs console=${console} root=LABEL=rootfs ro rootwait
ext2load usb 0:1 4880000 uInitrd-tegra
ext2load usb 0:1 4080000 uImage-tegra
ext2load usb 0:1 5880000 dtbs/tegra20-trimslice.dtb
bootm 4080000 4880000 5880000
  • Regenerate the boot script by running the following command:
mkimage -A arm -O linux -T script -C none -d armhfp-trimslice-sda-usb-boot.cmd armhfp-trimslice-sda-usb-boot.scr
  • Copy the boot script to be used on the next boot:
cp armhfp-trimslice-sda-usb-boot.scr boot.scr
mkdir -p /boot/dtbs
cd /boot/dtbs
wget http://ausil.us/dtb/3.7/tegra20-trimslice.dtb
  • Shutdown the system.
  • Upgrade to a new version of U-Boot (U-Boot 2012.04.01-1.01). Follow the instructions on the Trimslice Wiki.
  • Once completed, your system will now boot to the 3.7 kernel.

Additional Support

There are Fedora ARM users all around the globe - if you need assistance, would like to provide feedback or contribute to Fedora ARM please visit us on the IRC - we can be found in #fedora-arm[?] on Freenode. You can also contact us on the mailing list - arm