User Tools
installing_a_system_image
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
installing_a_system_image [2012/12/18 12:06] jussi_liukkonen |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | You can find release images, preview snapshots, and nightly development builds of the system from [[http://download.tizen.org|download.tizen.org]]. You can also build your own image following the instructions [[building_custom_system_images_here|]]. No matter how you obtained the system image, follow these steps to install it to your target system. | ||
| - | |||
| - | In the following instructions, we assume that the image //ivi-dev-auto-tizen_20121005.1// has been downloaded. Your image may have a different version number, but it will always end with //sdb.raw.bz2//. Use the //auto// images for the VTC-1000, and the //pc// images for Pinetrail based netbooks. | ||
| - | |||
| - | |||
| - | ==== Installing on the Nexcom VTC-1000: creating the install media ==== | ||
| - | |||
| - | |||
| - | This device cannot be flashed directly. You need to create a bootable USB media (USB disk or USB stick), and use it to boot the system and install the target system image onto the internal drive. | ||
| - | |||
| - | Connect a USB media to your development system. Check from _dmesg_ output which drive it appears as; typically, ///dev/sdb//. //dmesg// output will contain something like this: //\[sdb\] Attached SCSI removable disk//. | ||
| - | |||
| - | Use the correct device name (/dev/sda, /dev/sdb or similar) for your environment in the following commands: | ||
| - | |||
| - | | ||
| - | $ bzip2 -d ivi-dev-auto-tizen_20121005.1-sbd.raw.bz2 | ||
| - | $ sudo dd if=ivi-dev-auto-tizen_20121005.1-sbd.raw of=/dev/sdb bs=64k | ||
| - | # Enter your password for sudo | ||
| - | | ||
| - | |||
| - | You now have a bootable and runnable, minimal Tizen IVI image on the USB media. Next, we partition and format the remaining available space on the USB media, and copy the //same image// to the new USB media partition: | ||
| - | |||
| - | | ||
| - | $ sudo fdisk /dev/sdb | ||
| - | Command (m for help): n | ||
| - | p | ||
| - | [hit ENTER] | ||
| - | [hit ENTER] | ||
| - | w | ||
| - | | ||
| - | |||
| - | You will need to remove and reattach the USB device for the partitioning change to take effect. When you have re-attached the USB media, continue with formatting the new partition, and copying the target system image to it: | ||
| - | |||
| - | | ||
| - | $ sudo mkfs -t ext4 /dev/sdb4 | ||
| - | $ sudo mount /dev/sdb4 /mnt | ||
| - | $ sudo cp ivi-dev-auto-tizen_20121005.1-sbd.raw /mnt/ | ||
| - | $ sudo eject /dev/sdb | ||
| - | | ||
| - | |||
| - | You now have a bootable USB media, which also contains the system image to be installed to the target device. | ||
| - | |||
| - | |||
| - | ==== Installing on the Nexcom VTC-1000: installation to target ==== | ||
| - | |||
| - | |||
| - | Plug the USB media in to the Nexcom VTC-1000. Connect a USB keyboard, display, and power supply. Switch on the VTC-1000. | ||
| - | |||
| - | Press //\[DEL\]// to enter BIOS setup. In the //Boot// section, select //Hard Drive BBS Priorities//, and select your USB device to be the first priority boot device. Exit and save. The system should now reboot, and boot Tizen IVI from the USB media. | ||
| - | |||
| - | When the system is booted, press ALT+F2 to enter a free console and log in. Username is //root//, password is //tizen//. | ||
| - | |||
| - | In the VTC-1000, the internal SSD is always ///dev/sda//, and the USB media is ///dev/sdb//. Use the following instructions to install the system image to the internal SSD, and reconfigure the system to boot from the SSD: | ||
| - | |||
| - | | ||
| - | # mount /dev/sdb4 /mnt | ||
| - | # dd if=/mnt/ivi-dev-auto-tizen_20121005.1-sdb.raw of=/dev/sda bs=64k | ||
| - | # umount /mnt | ||
| - | # mount /dev/sda1 /mnt | ||
| - | # cd /mnt/extlinux/ | ||
| - | # sed -i "s/sdb/sda/g" extlinux.conf | ||
| - | # cd - | ||
| - | # umount /mnt | ||
| - | # shutdown -h now | ||
| - | | ||
| - | |||
| - | Remove the USB media. The system is now ready and will boot to Tizen IVI from the internal SSD when you switch it on. | ||
| - | |||
| - | Note that on developer images where the SSH service is installed, the SSH service may take a long time to generate the system's unique SSH keys on first boot after installation. The key generation process can be speeded up by pressing keys to generate entropy. | ||
| - | |||
| - | |||
| - | ==== Installing on the Nexcom VTC-1000: setting up the graphics system ==== | ||
| - | |||
| - | |||
| - | The pre-built images contain the //minimal system image//. If you want to use graphical applications, you also need to install one of the two available windowing systems: wayland or X. You can only install one or the other, not both. | ||
| - | |||
| - | To install a graphics system, connect Ethernet to a network providing a DHCP address and Internet connectivity. Start the device, press ALT+F2 to enter a free virtual console, and log in as //root// (password is still //tizen//). | ||
| - | |||
| - | Note: if you are using a developer (//dev//) image (instead of the minimal //min// image), you can check what IP address your device has with command //ifconfig eth0//, and then use //ssh root@ip.add.re.ss// from your developer system to log in remotely. This allows you to copy-paste the commands below. It is easier than typing everything in by hand. | ||
| - | |||
| - | If you need to use a proxy for Internet access, run the following commands after logging in: | ||
| - | |||
| - | | ||
| - | # export http_proxy=http://YOUR_PROXY_ADDRESS:PORT | ||
| - | # export https_proxy=https://YOUR_PROXY_ADDRESS:PORT | ||
| - | | ||
| - | |||
| - | **Installing X**: | ||
| - | |||
| - | | ||
| - | # zypper refresh | ||
| - | # zypper update | ||
| - | # zypper install -t pattern ivi-x-auto | ||
| - | | ||
| - | |||
| - | When using X on the VTC-1000 with the VMD-1000 display, you also need to create configuration files to set up and provide calibration values for the touch screen. Execute (or copy-paste) the following commands: | ||
| - | |||
| - | | ||
| - | # cd /etc/X11/xorg.conf.d | ||
| - | # ln -s /opt/etc/X11/xorg.conf.d/evdev.conf . | ||
| - | # cat <<EOF >80-touch.conf | ||
| - | Section "InputClass" | ||
| - | Identifier "DIALOGUE INC PenMount USB" | ||
| - | MatchProduct "DIALOGUE INC PenMount USB" | ||
| - | MatchDevicePath "/dev/input/event*" | ||
| - | Driver "evdev" | ||
| - | EndSection | ||
| - | EOF | ||
| - | # cat <<EOF >90-calibration.conf | ||
| - | Section "InputClass" | ||
| - | Identifier "calibration" | ||
| - | MatchProduct "DIALOGUE INC PenMount USB" | ||
| - | Option "SwapAxes" "1" | ||
| - | Option "Calibration" "17 1260 27 1647" | ||
| - | EndSection | ||
| - | EOF | ||
| - | | ||
| - | |||
| - | The calibration values may differ slightly between display units, and are obtained using the //xinput_calibrator// tool. You can install the tool from the Tizen rpeositories with //zypper install xinput_calibrator//. | ||
| - | |||
| - | **Installing Wayland**: | ||
| - | |||
| - | | ||
| - | # zypper refresh | ||
| - | # zypper update | ||
| - | # zypper install -t pattern ivi-wayland-auto | ||
| - | | ||
| - | |||
| - | Wayland does not require additional configuration. | ||
| - | |||
| - | In either case, you are now ready! | ||
installing_a_system_image.1355832382.txt.gz ยท Last modified: 2012/12/18 12:06 by jussi_liukkonen
Page Tools
