|
|
Line 1: |
Line 1: |
- | rescueOS is a rescue solution for the N900, distributed as a tarball and as an initrd image. It has several features, most notable:
| + | Previous information in this wiki page is outdated. |
- | | + | The official documentation is here: https://raw.github.com/NIN101/N900_RescueOS/master/documentation.txt |
- | * Mounting maemo root filesystem
| + | |
- | * Mounting EMMC partitions (maemo home and MyDocs)
| + | |
- | * USB mass-storage mode
| + | |
- | * USB networking
| + | |
- | * WiFi Support
| + | |
- | * Battery charging
| + | |
- | | + | |
- | = Installation & Booting =
| + | |
- | == tarball ==
| + | |
- | The installation of the tarball is rather easy and is in many ways compareable with the installation of meego-ce. The only difference is that a microsd card won't get completely overwritten as we only need one partition and do not overwrite the whole card and it's partition table.
| + | |
- | While it is recommended to create an ext4 partition, the kernel can actually handle ext2 and ext3.
| + | |
- | | + | |
- | We assume that you only need this if maemo is broken on your device, therefore we do not want to describe how to install it on the N900.
| + | |
- | | + | |
- | # Plug your microsd (through an adapter) into your computer.
| + | |
- | # Find the device node of the first partition. For example, if it /dev/sdf1, run mkfs.ext4 /dev/sdf1. WARNING: All data on this partition will be deleted. It is possible to use a different partition. If you use the second, replace the "mmcblk0p1" in the kernel command line to mmclbk0p2.
| + | |
- | # mount /dev/sdf1 /mnt/
| + | |
- | # tar xfvjp rescueOS-0.X.tar.bz2 -C /mnt/
| + | |
- | # umount /mnt/
| + | |
- | | + | |
- | | + | |
- | That's it! You can now proceed with "Booting"
| + | |
- | | + | |
- | === Booting tarball ===
| + | |
- | After you have unpacked the tarball, we can boot it. You need [[flasher|flasher-3.5]].<pre>
| + | |
- | flasher-3.5 -l -k 2.6.37 -b"root=/dev/mmcblk0p1 rootwait rw console=ttyO2,115200n8 console=tty0 mtdoops.mtddev=2" wait for "suitable device not found"...</pre>
| + | |
- | Connect your N900 with USB to your computer.
| + | |
- | Once the kernel is send, unplug the USB. RescueOS is booting now.
| + | |
- | | + | |
- | == initrd ==
| + | |
- | <pre>flasher-3.5 -k 2.6.37 -n initrd.img -l -b"rootdelay root=/dev/ram0"</pre>
| + | |
- | Connect your N900 with USB to your computer.
| + | |
- | Once the kernel is sent, unplug the USB. RescueOS should be booting now.
| + | |
- | | + | |
- | | + | |
- | = Releases =
| + | |
- | New versions are released from time to time.
| + | |
- | | + | |
- | === Current version: 0.4 (2011-09-02) ===
| + | |
- | e2fsprogs and dosfstools.
| + | |
- | | + | |
- | '''Download'''<br>
| + | |
- | [http://nin101.uni.cx/N900/rescueOS/rescueOS-0.4.tar.bz2 tarball] [http://nin101.uni.cx/N900/rescueOS/rescueOS-0.4.tar.bz2.sig sig]
| + | |
- | | + | |
- | [http://nin101.uni.cx/N900/rescueOS/resos-0.4.img initrd]
| + | |
- | | + | |
- | [http://nin101.uni.cx/N900/rescueOS/2.6.37 Kernel] [http://nin101.uni.cx/N900/rescueOS/2.6.37.sig Sig]
| + | |
- | | + | |
- | = Usage =
| + | |
- | ''To be written''
| + | |
- | | + | |
- | You basically get a bash shell right after the bootup. However, some scripts in the directory /rescueOS/ want to simplify some tasks. Currently most of them are in an early stage, so if in doubt, '''do not rely''' on them.
| + | |
- | | + | |
- | '''Shutdown'''<br>
| + | |
- | * unmount the maemo rootfs if you mounted it
| + | |
- | * detach it (ubidetach -m 5)
| + | |
- | * poweroff -f
| + | |
- | | + | |
- | '''WiFi support'''<br>
| + | |
- | It has wpa_supplicant, but without EAP support. This should be ok for most home networks which use a PSK.
| + | |
- | | + | |
- | Give the following a try:
| + | |
- | | + | |
- | <pre>wpa_passphrase [essid] [password] > /wlan.conf
| + | |
- | sh /rescueOS/setup-wpa-wifi.sh</pre>
| + | |
- | | + | |
- | For DHCP, use udhcpc -i wlan0.
| + | |
- | | + | |
- | '''Charging'''<br>
| + | |
- | bash /rescueOS/charge21.bash
| + | |