Debian Wheezy Instructions

From odroid US
Revision as of 18:02, 19 April 2013 by Osterluk (Talk | contribs) (Availability)

Jump to: navigation, search


Several SD-Card images and root file system images are available for the odroid-u2 board. The root file system images <should> work for other odroid models, but they would have to be merged with the "stock" SD Card image and the kernel modules would have to be pulled from the "foriegn" kernel build. If this doens't make sense, please ask on the forum.

Versions available:

  • minimal system (base) - console(server type) only version with SSH or USART-kit connection
  • system with visual desktop (gnome, xfce) - recommended for new users
  • larger development version (devel) - includes a native GCC compiler and all locales
  • root filesystem only (rootfs) image - see note below

The .img means it is a SD card image and .xz shows the file compression type.

See Extracting and writing Image to SD card for instructions on how to prepare your SD-card for odroid.

Standard armhf Images

You should use the standard images that support hard-floating point. These will be faster than the soft-float versions.

Alternate armel Images

A secondary set of images that are armel based, using soft floating point, are stored here:

You can't easily mix soft-float compiled and hard-float compiled binaries on the same system.

Note: For each of the versions exists a root filesystem only release (rootfs) if you just want to update system files.
The tarball with the -rootfs.tgz suffix is just the content of the rootfs partition of the SD card.

If you have flashed the Ubuntu SD-Card image and want to try the Debian system, you can just mount the partition, delete all the files and then extract the tarball onto the SD card.

See this tutorial for step-by-step instructions: Updating from Root File System Images


Writing the base SD-card image and booting will give you a completely up-to-date, headless Debian 7.0 system.
Headless, meaning only the Linux console is active -- not the HDMI display.

The network will come up automatically, using DHCP.

The login is: user/password or root/root. Specifically, this means username: user and password: password will get you in. Or you can use username: root, password: root.

If you log in as user, you can use command su to become root.

Checking archive Integrity with md5sum

  • Files next to SD images (with the .md5sum extensions) give you an easy way to check validity after downloading, using md5sum like this:
md5sum -c odroidu2_20130104-debian-wheezy-3.img.xz.md5sum 
# odroidu2_20130104-debian-wheezy-3.img.xz: OK

The Image structure

The non-filesystem area, including the bootloader(s) generally follow the HardKernel ubuntu images, like odroidu2_20130125-linaro-ubuntu-desktop-uSDeMMC.img.xz. The partition layout is the same, the bootloaders are the same.

The boot partition holds the kernel, initrd and u-boot boot scripts. These will not exactly track the HK releases.

Revision History

See here for all revision history.

Security Issues and Initialization

When you use an existing image, you pick up some keys that you should change for security reasons. Once you boot your system the first time do this: (as root)

rm /etc/ssh/*.pub /etc/ssh/*_key
#images starting at debian-wheezy-base-6.1 should have openssh-server installed
# re-generate the host ssh keys
dpkg-reconfigure openssh-server

It is best to set a unique persistent MACID. This script will do it:

echo $( ifconfig | grep HWaddr | awk '{ print $5 }' ) >/etc/smsc95xx_mac_addr

Debian Tips

This page is for Debian Tips Debian Tips

Image Creation Details

You can compile a custom version of Debian root filesystem image, just read here.