* 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!

=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 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.

+

{{admon/warning|IMPORTANT | You must use firmware "[http://trimslice.com/download/firmware-updater/v2010.09-1.03/firmware-updater.img.zip v2010.09-1.03]" to boot the Fedora 18 Trimslice image. <b>Failure to do so will result in a non-booting system.</b>}}

−

ssh root@fedora-arm (or IP)

+

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 IP address. Use SSH to connect to the root account.

+

ssh root@<ip-of-host>

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

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

−

=Updating to the 3.7.X Kernel=

−

{{admon/warning|IMPORTANT | When upgrading to the 3.7.X kernel, the Trimslice will require a new version of U-Boot and a Device Tree Binary (.dtb). Follow the below directions for use. <b>Failure to do so will result in a non-booting system.</b>}}

−

As of the 3.7.X kernel, the Trimslice will require the latest version of [http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#v2012.04-1.01 U-Boot] that supports Device Tree and the use of a Device Tree Binary blob (.dtb). To successfully upgrade to the latest kernel:

+

=Updating to the 3.7+ Kernel=

+

{{admon/warning|IMPORTANT | When upgrading to the 3.7+ kernel, the Trimslice will require a new version of U-Boot and a Device Tree Binary (.dtb). Follow the below directions for use. <b>Failure to do so will result in a non-booting system.</b>}}

+

+

As of the 3.7+ kernel, the Trimslice will require the latest version of [http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#v2012.04-1.01 U-Boot] that supports Device Tree and the use of a Device Tree Binary blob (.dtb). To successfully upgrade to the latest kernel:

yum update kernel-tegra

yum update kernel-tegra

The kernel package will also install a subdirectory in '/boot/dtb-<kernel-version>' that will include the Device Tree Binary blob for the Trimslice. In order to use this 'dtb' file, create a symbolic link as follows:

The kernel package will also install a subdirectory in '/boot/dtb-<kernel-version>' that will include the Device Tree Binary blob for the Trimslice. In order to use this 'dtb' file, create a symbolic link as follows:

Line 65:

Line 67:

* Images were composed using tools in Fedora 17 due to continuing work on Fedora 18.

* Images were composed using tools in Fedora 17 due to continuing work on Fedora 18.

* When using this image the system will automatically reboot to repartition the root filesystem on first boot. This will expand the size of the root partition to use all available space on the device. To prevent this, delete the '.rootfs-repartition' flag in '/' or pass a kernel command line argument of 'nofsresize'.

* When using this image the system will automatically reboot to repartition the root filesystem on first boot. This will expand the size of the root partition to use all available space on the device. To prevent this, delete the '.rootfs-repartition' flag in '/' or pass a kernel command line argument of 'nofsresize'.

−

* When upgrading the to 3.7.X kernel on the Trimslice you will require a new version of U-Boot that supports Device Tree.

+

* When upgrading the to 3.7.X kernel on the Trimslice you will require a new version of U-Boot that supports Device Tree, and a Device Tree Binary (.dtb) file.

−

** The latest version of U-Boot on the Trimslice reduces the available memory to 512M. (This has been reported to CompuLaband should be fixed in a future release)

+

** Version v2012.04-1.01, which provides DTB support also has a bug reducing available memory to 512M (This has been reported to CompuLab should be fixed in a future release).

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 #fedora-arm on Freenode. You can also contact us on the mailing list - arm@lists.fedoraproject.org

Trimslice

The Trim Slice is a small, fanless, nettop computer in an all metal case, manufactured by CompuLab. It is based on the NVIDIA Tegra 2 processor. It features a variety of connectivity options. At this time there is no support in Fedora for a display on the Trim Slice, so it boots to a serial console.

Running Fedora on a Trimslice

This page will give you detailed instructions for running Fedora 18 on your Trimslice. The image is prepared to boot from SD card by default, but can be easily modified to boot from the internal SATA connection (USB) by using the appropriate boot script (boot.scr.usb).

Download the image

The first step is to download the Fedora 18 image. The prebuilt image includes everything you will need and can be written directly to SD Card, USB, or SATA drive and will require a minimum of 4GB. There are two images available for the Trimslice, a hardware floating point (armhfp) image, and a software floating point (arm) image. If you are unsure of which to choose, the armhfp image is recommended, and will be used in the examples below (adjust accordingly for 'arm'):

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 4GB. 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.

Windows Users

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!

Using Fedora on the Trimslice

IMPORTANT You must use firmware "v2010.09-1.03" to boot the Fedora 18 Trimslice image. Failure to do so will result in a non-booting system.

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 IP address. Use SSH to connect to the root account.

ssh root@<ip-of-host>

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

Updating to the 3.7+ Kernel

IMPORTANT When upgrading to the 3.7+ kernel, the Trimslice will require a new version of U-Boot and a Device Tree Binary (.dtb). Follow the below directions for use. Failure to do so will result in a non-booting system.

As of the 3.7+ kernel, the Trimslice will require the latest version of U-Boot that supports Device Tree and the use of a Device Tree Binary blob (.dtb). To successfully upgrade to the latest kernel:

yum update kernel-tegra

The kernel package will also install a subdirectory in '/boot/dtb-<kernel-version>' that will include the Device Tree Binary blob for the Trimslice. In order to use this 'dtb' file, create a symbolic link as follows:

ln -s /boot/dtb-<kernel-version> /boot/dtbs

For example for 'kernel-tegra-3.7.5-202.fc18.armv7hl'

ln -s /boot/dtb-3.7.5-202.fc18.armv7hl.tegra /boot/dtbs

Shutdown your device, and follow the instructions on the Compulab website to update the firmware on the Trimslice. Once the firmware is installed, boot the Fedora 18 installation.

Release Notes

Images were composed using tools in Fedora 17 due to continuing work on Fedora 18.

When using this image the system will automatically reboot to repartition the root filesystem on first boot. This will expand the size of the root partition to use all available space on the device. To prevent this, delete the '.rootfs-repartition' flag in '/' or pass a kernel command line argument of 'nofsresize'.

When upgrading the to 3.7.X kernel on the Trimslice you will require a new version of U-Boot that supports Device Tree, and a Device Tree Binary (.dtb) file.

Version v2012.04-1.01, which provides DTB support also has a bug reducing available memory to 512M (This has been reported to CompuLab should be fixed in a future release).

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