Editing Mer/Documentation/Installation

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
{{Mer}}
 
-
 
This article sums up the different ways to install Mer on different types of computers (VMWare, chroot, on device, etc.). Please feel free to add/edit. The original information is taken from [[Mer/Releases/0.9]].
This article sums up the different ways to install Mer on different types of computers (VMWare, chroot, on device, etc.). Please feel free to add/edit. The original information is taken from [[Mer/Releases/0.9]].
Line 19: Line 17:
# Installing all the needed packages for installing VirtualBox additions:
# Installing all the needed packages for installing VirtualBox additions:
#* I had to install the following packages by:
#* I had to install the following packages by:
-
#* sudo apt-get install build-essential linux-headers-*kernel-version*-generic
+
#* sudo apt-get install gcc build-essential kernel-headers-*kernel-version*-generic
#*(replace *kernel-version* with the currently installed kernel-version on the virtual machine)
#*(replace *kernel-version* with the currently installed kernel-version on the virtual machine)
#*(you can simply find out which kernel-version you have, by executing "uname -r" in Mer's XTerminal)
#*(you can simply find out which kernel-version you have, by executing "uname -r" in Mer's XTerminal)
# Installing the additions:
# Installing the additions:
#*First of all you have to mount the CD-Image with the additions emulated as a cdrom-device into the virtual machine running mer.
#*First of all you have to mount the CD-Image with the additions emulated as a cdrom-device into the virtual machine running mer.
-
#* Mount the VboxAdditions.iso by: Devices -> mount CD-ROM image -> select VboxGuestAdditions.iso
 
#* Create a new folder with root rights by:
#* Create a new folder with root rights by:
#*sudo mkdir /media/cdrom
#*sudo mkdir /media/cdrom
Line 30: Line 27:
#*sudo mount /dev/scd0 /media/cdrom
#*sudo mount /dev/scd0 /media/cdrom
#* If no errors are appearing you can install the additions by:
#* If no errors are appearing you can install the additions by:
-
#*sudo /media/cdrom/VBoxLinuxAdditions-x86.run
+
#*sudo /media/cdrom/VBoxLinuxAdditions[Tab]
 +
#* (please the [Tab]-key instead of [Tab] :) )
# Rebooting the virtual machine:
# Rebooting the virtual machine:
#* Now, when the installation of the additions has finished, you can reboot the vm simply by:
#* Now, when the installation of the additions has finished, you can reboot the vm simply by:
Line 51: Line 49:
<pre>
<pre>
-
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb 2>/dev/null 1>&2 &
+
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite 2>/dev/null 1>&2 &
sudo mount --bind /tmp/.X11-unix tmp/.X11-unix
sudo mount --bind /tmp/.X11-unix tmp/.X11-unix
sudo mount --bind /dev/pts dev/pts
sudo mount --bind /dev/pts dev/pts
Line 71: Line 69:
The developers of Mer implemented an installer, which leads through all the steps of installation. In order to use the installer you need to open:
The developers of Mer implemented an installer, which leads through all the steps of installation. In order to use the installer you need to open:
-
[http://trac.tspre.org/merinstaller.install .install file] with your device, which will prompt you to install the file (about 2.5MB) and add the Extras, Extras-devel and tspre.org repositories if they were not added already.
+
[http://bsd.tspre.org/~stskeeps/merinstaller.install .install file] with your device, which will prompt you to install the file (about 2.5MB) and add the Extras, Extras-devel and tspre.org repositories if they were not added already.
After the download and the installation go to Settings -> Application Manager -> Utilities -> Browse Installable Applications -> Other and system and you will find a program "Install Bootmenu" and "Merinstaller". If you did not install those by pressing "OK" before, do it now.
After the download and the installation go to Settings -> Application Manager -> Utilities -> Browse Installable Applications -> Other and system and you will find a program "Install Bootmenu" and "Merinstaller". If you did not install those by pressing "OK" before, do it now.
-
The Simple Install will create a bootmenu entry for you. However, for more advanced installations - eg if you already have multiple booting OSes - you might want to read about its [[Mer/Documentation/Bootmenu|configuration]] - you may need to make a .item if you have a clone-to-SD copy of Maemo or Deblet. You can also find out how to change the default boot menu item and other bootmenu tricks.
+
The Simple Install will create a bootmenu entry for you. However, for more advanced installations - eg if you already have multiple booting OSes - you might want to read about its [[Mer/Documentation/Bootmenu|configuration]] - you may need to make a .item if you have a clone-to-SD copy of Maemo or Deblet. Other bootmenu tricks like: Booting Mer instead of Maemo as a default are also found under the link.
Assuming you created all the .item files you wanted, go ahead, and start the bootmenu installer from Utilities -> Install Bootmenu. Its advised to close all other applications and network connections, but the installer will tell you all relevant information.
Assuming you created all the .item files you wanted, go ahead, and start the bootmenu installer from Utilities -> Install Bootmenu. Its advised to close all other applications and network connections, but the installer will tell you all relevant information.
Line 91: Line 89:
Now start the Merinstaller via Utilities -> Install Mer. Follow the instructions. When prompted for the URL= you can point it to any rootfs image you want. Check at [[Mer/Releases]] or ask at #mer.
Now start the Merinstaller via Utilities -> Install Mer. Follow the instructions. When prompted for the URL= you can point it to any rootfs image you want. Check at [[Mer/Releases]] or ask at #mer.
-
Once the installer puts the extracted rootfs to your device you can reboot and chose the partition where you put Mer. Please contribute by filing bugs on [https://bugs.maemo.org/ bugs.maemo.org]
+
Once the installer puts the extracted the rootfs to your device you can reboot and chose the partition where you put Mer. Please contribute by filing bugs on [https://bugs.maemo.org/ bugs.maemo.org]
=== Flashable Image ===
=== Flashable Image ===
-
'''NOTE: Very experimental, because it doesn't use the Maemo initfs; only install if you want to help test it.'''
+
'''NOTE: Experimental'''
Grab a kernel and rootfs image of Mer and flash them directly to the device by:<BR>
Grab a kernel and rootfs image of Mer and flash them directly to the device by:<BR>
Line 106: Line 104:
== 770 Install ==
== 770 Install ==
-
'''(these instructions need testing)'''
+
(these instructions need testing)
You will need at least a 1gb MMC, and these instructions are based on OS2008HE kernel. 48mhz kernel is highly recommended
You will need at least a 1gb MMC, and these instructions are based on OS2008HE kernel. 48mhz kernel is highly recommended
Line 231: Line 229:
</pre>
</pre>
-
== Touch Book (Experimental) ==
+
== SmartQ5 ==
-
'''Until there's a Touch Book image, use SmartQ5 image.'''
+
To install, put the firmware image on a SD card, on the first partition, a FAT32 one, and name the firmware image SmartQ5. Then, hold down + button and insert charger.
-
First, make sure your SD card's geometry is 63 / 255 . Otherwise the Touch Book won't recognice it. To set the correct geometry, put the SD in your host-computers card-reader and open up a terminal. Type:
+
It will be accessible over USB networking on IP 192.168.2.2 ([http://wiki.maemo.org/USB_networking#Host_USB_Network_Configuration see instructions here]) with a SSH server, login root, password rootme
-
<pre>
+
-
bash:$ sudo fdisk /dev/<yoursdcard>
+
-
Command (m for help): [x]
+
It will not show a splash screen, but it will after darkness then make the screen white, and eventually, show the Mer background and first boot wizard.
-
Expert command (m for help): [s]
+
* There is currently a problem with closing dialogs (will be fixed in testing4).
-
Number of sectors : [63]
+
-
Expert command (m for help): [h]
+
To get wireless networking to work (from https://wiki.ubuntu.com/Marvell8686Firmware):
-
Number of heads : [255]
+
-
Expert command (m for help): [w]
+
1. Grab the firmware package from Marvell here: http://www.marvell.com/drivers/driverDisplay.do?driverId=203 and copy it to your computer.
-
</pre>
+
-
'''Formatting the SD card:'''
+
2. Extract the downloaded zip file, then extract SD-8686-FEDORA26FC6-SYSKT-GPL-9.70.3.p24-26409.P45.tar within it. Extract the FwImage folder.
-
* The first partition needs to be formatted as FAT32 ''and have the boot flag''. 30Mb size is fine.
+
3. Inside there are two files, helper_sd.bin and sd8686.bin. Rename helper_sd.bin to sd8686_helper.bin and copy to your SD card
-
* Format the second partition as ext3, at least 512Mb size.
+
-
* If you want, you can also create one more partition for swap.
+
-
This is easy to do with linux host-computer.
+
4. In Mer on SmartQ, open X-Terminal and:
-
GParted is easy to use graphical Partition Editor.
+
-
'''Installation'''
 
-
 
-
Download Mer image and unpack it in the second partition.
 
-
 
-
Copy a few files from AI OS for better hardware support:
 
-
 
-
/lib/firmware
 
-
 
-
/lib/modules
 
-
 
-
/etc/Wireless
 
-
 
-
/etc/fstab
 
-
 
-
== SmartQ ==
 
-
Dual booting doesn't seem to work at the moment.
 
-
 
-
You'll need an SD card with a FAT32 as the first partition and more than 140MB free.
 
-
 
-
Download the correct firmware image and rootfs image from the Released Images table.  Copy both of them to the root of the FAT32 partition on the SD card.
 
-
 
-
Rename the firmware image to either 'SmartQ5' or 'SmartQ7' according to your device.
 
-
 
-
You may also want to download some additional software to our SD card for after Mer is installed.<br>
 
-
To use Wifi, you'll need the Marvell Wifi Firmware blobs
 
-
* Browse [http://www.marvell.com/support.html here] and select in the drivers colum for os "Fedora 2.6" and click search. After that, get a zip file called starting whit SD-8686
 
-
* Extract the downloaded zip file, then extract SD-8686-FEDORA26FC6-SYSKT-GPL-9.70.3.p24-26409.P45.tar within it. Extract the FwImage folder to your PC.
 
-
* Inside there are two files, helper_sd.bin and sd8686.bin. Rename helper_sd.bin to sd8686_helper.bin and copy to your SD card
 
-
 
-
The commands to extract and copy it might look like this:
 
-
cd /tmp
 
-
unzip SD-8686-LINUX26-SYSKT-9.70.3.p24-26409.P45-GPL.zip
 
-
tar xf SD-8686-FEDORA26FC6-SYSKT-GPL-9.70.3.p24-26409.P45.tar
 
-
cp FwImage/helper_sd.bin /path_to_SD_CARD/sd8686_helper.bin
 
-
cp FwImage/sd8686.bin /path_to_SD_CARD/sd8686.bin
 
-
 
-
 
-
Wifi WPA2 fix
 
-
* Download the [http://www.daimi.au.dk/~cvm/kernel-smartq5-modules_2.6.24.7-smartq5-050509_all.deb SmartQ5] or [http://download.opensuse.org/repositories/Maemo://Mer:/Devel:/HW:/SmartQ:/Devel/MerDevel_Ubuntu_9.04/all/kernel-smartq7-modules_2.6.24.7-smartq7-20090729_all.deb SmartQ7] WPA2-fixed driver to your SD card.
 
-
 
-
Now unmount the SD card and eject it.
 
-
 
-
Power off the SmartQ totally (wait for the LED to go out) and insert the SD card.
 
-
 
-
===SmartQ5===
 
-
Press and hold the + button and insert the charger.
 
-
The device will begin to boot; the LED will be green/yellow.
 
-
A series of chinese characters will appear ending with '...' if all is going well.  Once you see them, you can release the + button.  Next there will be
 
-
a progress bar.  Once it completes, the device will automatically reboot.
 
-
 
-
===SmartQ7===
 
-
Press and hold the 'menu' key (bottom key on front) and insert the charger.
 
-
The device will begin to boot; the LED will be a different colour - green/yellow. You can release the menu key. Some chinese symbols appear and then a progress bar ticks (slowly) up to 100%.  Once it completes, the device will automatically reboot.
 
-
 
-
===both===
 
-
After this a calibration screen will appear and shortly after you are in Mer.
 
-
 
-
If you have connected it to a computer via USB, it will be accessible over USB networking on IP 192.168.2.15 ([http://wiki.maemo.org/USB_networking#Host_USB_Network_Configuration see instructions here]) with a SSH server, login root, password rootme
 
-
 
-
It will not show a splash screen, but it will after darkness then make the screen white, and eventually, show the Mer background and first boot wizard.
 
-
 
-
=== To mount your SD card ===
 
-
In Mer on SmartQ, open X-Terminal and type (tab-completion is your friend):
 
<pre>
<pre>
-
$ sudo mount -t vfat /dev/mmcblk1p1 /media
+
$ sudo mount -t vfat /dev/mmcblk1p1 /media
-
</pre>
+
(password is the one you used when installing)
-
When prompted for a password, enter the one you set when you first started.
+
$ sudo cp /media/sd8686.bin /lib/firmware/sd8686.bin
-
Note that the above device name has one lower-case L character and then two number one characters (these can look quite similar in some fonts).
+
$ sudo cp /media/sd8686_helper.bin /lib/firmware/sd8686_helper.bin
-
 
+
$ sudo umount /media
-
=== To get wireless networking (including WPA2) to work===
+
-
 
+
-
In order to get wireless networking to work, you are going to have to install the Marvell firmware you copied onto your SD card, and to get WPA2 working, you'll also need to install the .deb.  The first step is to mount your SD card (see the section just above this, if you haven't already mounted it).
+
-
 
+
-
So, in Mer on SmartQ, open X-Terminal and type (tab-completion is your friend):
+
-
<pre>
+
-
$ sudo cp /media/sd8686.bin /lib/firmware/
+
-
(if prompted, the password is the one you set when you first started)
+
-
$ sudo cp /media/sd8686_helper.bin /lib/firmware/
+
-
</pre>
+
-
And then either, for the SmartQ5 [Note: The following step may not be necessary as the 0.16-5 firmware automatically installs the most current file from the SD card during bootup. The confirmation message is "wifi firmware installation successful". Verified on Q5.]
+
-
<pre>
+
-
$ sudo dpkg -i /media/kernel-smartq5-modules_2.6.24.7-smartq5-*_all.deb
+
-
</pre>
+
-
or for the SmartQ7 [Note: The following step may not be necessary as the 0.16-5 firmware automatically installs the most current file from the SD card during bootup. The confirmation message is "wifi firmware installation successful". Verified on Q7.]
+
-
<pre>
+
-
$ sudo dpkg -i /media/kernel-smartq7-modules_2.6.24.7-smartq7-*_all.deb
+
-
</pre>
+
-
 
+
-
Now that you've enabled networking, you should close the gaping security hole which is part of the default configuration by changing the root password from its default, which is "rootme".
+
-
<pre>
+
-
$ sudo passwd
+
-
Password:  (enter your user password)
+
-
Enter new UNIX password:  (enter any hard to guess password you want)
+
-
Retype new UNIX password:  (same one again)
+
-
</pre>
+
-
 
+
-
Next you should reboot.
+
-
<pre>
+
-
$ sudo /sbin/reboot
+
-
</pre>
+
-
 
+
-
Once it reboots, you should be able to see wireless networks on the menu and select them.
+
-
 
+
-
=== Booting from SD card ===
+
-
(this was taken from [http://alone-in-the-light.zenvoid.org/2009/06/boot-smartq-5-from-sd-card.html zenvoid's blog])
+
-
 
+
-
In order to boot from the SD card, it is simply a matter of creating a partition on the SD card large enough to hold the mer distribution, but leaving enough unpartitioned space at the end of the card for the bootloader to sit.
+
-
 
+
-
* Download install-smartq-qi.sh, qi-smartq-20090612.bin from http://zenvoid.org/software/qi-smartq
+
-
 
+
-
* Create at least one ext2/ext3 Partition your SD card (and optionally a swap partition), but always '''remember to reserve 1 MiB of free, unpartitioned space at the end of the SD card'''. To be precise, at least the last 2048 blocks (512 bytes each) must be reserved.
+
-
* Untar (tar --numeric-owner -zxvf) the rootfs for your device onto the partition you created on your SD card (make sure it isn't mounted with any no* options, e.g. nodev, noexec, ..)
+
-
* Rename or copy the kernel file (/boot/zImage<something>)  to /boot/linux-SMDK6410.bin
+
-
* Run
+
-
<pre>
+
-
./install-smartq-qi.sh /dev/SD_CARD_DEVICE qi-smartq-20090612.bin
+
-
</pre>
+
-
 
+
-
To boot from the SD card, keep the "move"/fullscreen button (Q5) or right-hand-most button on the top which looks like a target symbol (Q7) pressed and then press the "power" button.
+
-
 
+
-
Q5 Boot stages:
+
-
* Red LED: First stage - bootloader is loading itself into memory.
+
-
* Yellow LED: Second stage - bootloader running, trying to locate and loading a kernel image.
+
-
* Green LED: Linux kernel loaded and running.
+
-
* Blinking yellow LED: A critical error while reading from the SD card.
+
-
* Blinking green LED: No kernel found.
+
-
 
+
-
Q7 Boot:
+
-
 
+
-
Keep in mind that the LEDs colours are reversed on the Q7, i.e. a green LED on the Q5 is a red one on the Q7 (the list above is for the Q5)
+
-
 
+
-
There is no battery check at the moment.
+
-
 
+
-
 
+
-
 
+
-
 
+
-
==== Alternate SD booting method using the OF bootloader ====
+
-
(as desribed on the Smartqmid forum:
+
-
http://www.smartqmid.com/phpBB3/viewtopic.php?f=2&t=150)
+
-
 
+
-
'''works only with OF installed on the device'''
+
-
 
+
-
in short:
+
-
*the first partition must be fat32 and the other primary partitions must be ext3
+
-
*on the first (fat) partition must be a folder named boot, that contains a menu.lst file and the kernel image (zimage)
+
-
*the menu.lst should be formated like this:
+
-
<pre>
+
-
title sdcard # name of the entry
+
-
kernel /boot/zimage # kernel image location
+
-
param root=/dev/mmcblk1p2 rootwait # location of the root fs, this is
+
-
                                  # the second primary partition on SD
+
-
                                  # the internal memory is mmcblk0,
+
-
                                  # first internal partition = mmcblk0p1
+
-
 
+
</pre>
</pre>
-
With all this in place, the device shows a simple boot menu when turned on wit the SD card inside, you can select the entry with +,- buttons on the left and booting is triggered with middle button on the upper left.
+
5. Reboot. There is a problem with WPA2 networks (they're greyed out, feel free to find out why).
-
Theoretically you can multiboot up to 5 different systems (internal + on the fat partition + three ext3 partitions, '''not tested''').
+
[[Category:Mer]]

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page: