|
|
| Line 1: |
Line 1: |
| == Download Plasma Active 3 official release == | | == Plasma Active Images == |
| You can find the operating system image for the official release of Plasma Active 3 at this link at [http://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/ basysKom download center]
| |
|
| |
|
| == Install Plasma Active on ARM Systems ==
| | The Plasma Active team provides official Images based on Mer for some devices: |
|
| |
|
| === Advent Vega and Point of View TAB-TEG-10-1-4GB-3G Mer Plasma Active MMC raw image=== | | == Supported == |
| The [http://merproject.com Mer] project creates a Plasma Active [http://bug10738.openaos.org/images/tegra2/ MMC Image] which is build for the armv7hl target devices like the ARM Tegra 2 tablet. For more details please see the related [https://wiki.merproject.org/wiki/Main_Page Mer Wiki].
| |
|
| |
|
| You can also download the kernel boot image, the external MMC image and some additional helper scripts from [http://share.basyskom.com/plasma-active/nvidia_tegra2.html basysKom download center].
| | === WeTab / ExoPC === |
|
| |
|
| ===Archos gen9 Mer Plasma Active root filesystem tarballs===
| | Download: |
|
| |
|
| basysKom creates weekly Plasma Active Mer development and testing tarballs for the Archos gen9.
| | Installation: |
|
| |
|
| There are tarballs with and without hardware acceleration available and also different kernel images to setup an dual boot system with Plasma Active. Login Data: User ''mer'' password ''mer''; User ''root'' password ''mer''
| | == Preview == |
|
| |
|
| You can try the Archos gen9 Plasma Active Mer root filesystem tarballs from [http://share.basyskom.com/plasma-active/archos_gen9.html basysKom download center].
| | ==== Nexus 7 ==== |
|
| |
|
| Read http://basyskom.com/news/138-archos-plasma-active.html for additional information
| | Event though very much already works reasonably well, there are still some glitches. So, please don’t expect a 100% working system. For detailed installation instructions, see the article on the [https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_installation Mer Wiki] |
|
| |
|
| === Other Systems === | | === Archos G9 === |
| ==== Viewsonic Viewpad 10s / Advent Vega / Point of View tablets ====
| |
| Read [http://forum.kde.org/viewtopic.php?f=211&t=99154 KDE Forum page]
| |
|
| |
|
| === Deploying a Plasma Active (MMC) raw Image to a MultiMediaCard ===
| | Take a look at [ http://ruedigergad.com/2013/02/24/plasma-active-archos-g9-armv7hl-rootfs-tarballs/ Ruediger Blog ] for more information. |
| A Installation description for MultiMediaCards could be found in the [http://wiki.meego.com/ARM/N900/Install/MMC MeeGo ARM Wiki].
| |
|
| |
|
| === Plasma Active for Nexus 7 === | | === VirtualBox === |
| There is a testing release of [http://ruedigergad.com/2012/12/21/plasma-active-for-nexus-7-running-the-touch-optimized-plasma-active-linux-distribution-on-nexus-7/ Plasma Active for Nexus 7]. Event though very much already works reasonably well, there are still some glitches. So, please don’t expect a 100% working system.
| |
|
| |
|
| For detailed installation instructions, see the article on the [https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_installation Mer Wiki]
| | When running Plasma Active in a virtual machine, consider that performance will not be as good as when it runs naively on the devices it has been designed for. For testing, we strongly recommend running Plasma Active on a device. The following limitations need consideration when using a virtual machine instead of a real device: |
| | | * Performance, especially graphics, boot and application startup might be reduced |
| = Install Plasma Active on x86 Systems =
| | * Advanced visual effects might not be available or work correctly in the virtual machine. This can lead to degradation of certain features, performance, visual effects and possibly stability |
| | | * User interfaces designed for touch-screens often work less efficiently for mouse and keyboard based input methods, or feel less natural. |
| == Live Images==
| |
| Live-Images of plasma active are provided. Installation sources are mentioned below and how to use them. For plasma active images are provided to run native on the system like ARM-Image or as a boot-stick imaga that can be used to play around an then probably install it on your system.
| |
| These images are probably the easies and fastest way to get the plasma active user experience, play around, first app development, demos and show cases.
| |
| | |
| === Booting the Live Image on a WeTab/ExoPC ===
| |
|
| |
|
| 1. Plug the flashdrive into the WeTab/ExoPC (In some cases WeTab only works with special flashed BIOS from ExoPC).
| |
|
| |
|
| 2. Press the power button
| | For detailed installation instructions, see this [http://community.kde.org/Plasma/Active/VirtualBox installation manual]. |
|
| |
|
| 3. Once the WeTab starts to boot (Blue LED on WeTab lights up or LED on stick lights up) press power button together with softtouch button (round area in top left corner of touch screen) for approximately 1 second (longer press will shut it down again)
| |
|
| |
|
| 4. Press the softtouch button until it boots
| |
|
| |
|
| ''Alternative instructions: Put usb stick in tablet and boot up, press BBS (on the touchscreen). You can go through the bootloader using the button in the top left corner of the screen, short press to move to the next entry, long press to boot it. A USB keyboard is needed to select the options during the install"
| | == Downstream Plasma Active Images == |
|
| |
|
| ==== Installation with USB keyboard ====
| | Some distributions provide Images with Plasma Active for x86 Systems. |
| | |
| 1. Connect a USB keyboard to the WeTab
| |
| | |
| 2. Follow steps 1-3 above to get to the boot menu
| |
| | |
| 3. Press the softtouch button shortly to select "Installation"
| |
| | |
| 4. Hold the softtouch button until the boot procedure starts
| |
| | |
| 5. When the boot procedure stops, press enter on the USB keyboard and a message saying "Select one disk to install" will appear
| |
| | |
| 6. Type the number of the local SSD and hit <Enter>
| |
| | |
| 7. Select "Full disc install" <Enter>
| |
| | |
| 8. Confirm with <y> <Enter>
| |
| | |
| 9. After the installation has finished, remove the USB stick and USB keyboard and press the power button until it shuts down.
| |
| | |
| ==== Installation without USB keyboard ====
| |
| Please choose via 6 second tab on frontside sensor button the 'Boot MeeGo' instead of 'Installation' entry. Wait until Plasma Active is boot completely into the user interface. Open the 'Konsole' application from the peek area by pulling down the top bar. Enter following commands via virtual keyboard to call the installer (password is 'mer'):
| |
| | |
| <nowiki>
| |
| su
| |
| export PATH=${PATH}:/sbin:/usr/sbin
| |
| installer-shell
| |
| reboot
| |
| </nowiki>
| |
|
| |
|
| === Kubuntu Active === | | === Kubuntu Active === |
| Line 94: |
Line 52: |
|
| |
|
| It includes an installer '''ubiquity'''. | | It includes an installer '''ubiquity'''. |
|
| |
| === Mer Plasma Active Live (Installable) Image ===
| |
|
| |
| [http://basyskom.com basysKom] creates weekly Plasma Active Mer development and testing images.
| |
|
| |
| This image bootable on x86 based devices like '''WeTab''', '''ExoPC''' or the '''Idea Pad'''. Login Data: User ''mer'' password ''mer''; User ''root'' password ''mer''
| |
|
| |
| You can try the installable Mer Live ISO for a USB flash drive or CD/DVD from [http://share.basyskom.com/plasma-active/wetab.html basysKom download center].
| |
|
| |
| <!--
| |
| === Validate and Deploy on Microsoft Windows ===
| |
| On Windows you can compare the hash on equality between image and related checksum file by the [http://support.microsoft.com/kb/841290 fciv.exe] tool. You will find all needed information about
| |
| usage on this site.
| |
|
| |
| With the [https://launchpad.net/win32-image-writer win32-image-writer] tool you can easily deploy a plasma active image to a USB Flashdrive. For a detailed description how to work with this tool please see the MeeGo [https://meego.com/devices/netbook/installing-meego-netbook/windows-instructions Windows instructions]. -->
| |
|
| |
|
| |
| On Linux you can compare the hash between the image and related checksum file using the following command (with both the image and the checksum file in the same directory):
| |
|
| |
| user@host# '''sha1sum -c ''<checksum file>'''''
| |
|
| |
| user@host# '''md5sum -c ''<checksum file>'''''
| |
|
| |
| If the command returns "<image name>: FAILED", please download the image one more time and check again.
| |
|
| |
|
| |
| After validation feel free to deploy the image to a '''not mounted''' USB flashdrive. In the following example we use the tool 'dd' for this:
| |
|
| |
| root@host# '''dd if=''<image file>'' of=/dev/''<USB flashdrive>'' bs=1M'''
| |
|
| |
| '''Please note, the usage of this tool is potentially dangerous! In case of a mistaken output device, all data on it will be irrecoverably lost'''.
| |
|
| |
| '''To get the correct output device for this tool, please follow the steps below:'''
| |
|
| |
| 1. Remove all mobile flashdrives from your host system.
| |
|
| |
| 2. Enter the command below and note the output.
| |
| user@host# '''cat /proc/partitions'''
| |
|
| |
| major minor #blocks name
| |
| 8 0 3000000 sda
| |
| 8 1 2999998 sda1
| |
|
| |
| 3. Plug the Flashdrive for deploying into the host system.
| |
|
| |
| 4. Enter the following command and note the output again.
| |
| user@host# '''cat /proc/partitions'''
| |
|
| |
| major minor #blocks name
| |
| 8 0 30000000 sda
| |
| 8 1 29999998 sda1
| |
| 8 16 3872256 '''sdb'''
| |
| 8 17 594944 sdb1
| |
|
| |
| 5. In this example the correct dd parameter is '''sdb''' in the position of '''<USB flashdrive>'''.
| |
|
| |
| If you prefer you can disable connman and [http://community.kde.org/Plasma/Active/Info/FAQ#Installing_Plasma_NetworkManagement_on_Mer_x86_images install Plasma NetworkManagement] to manage your network devices (wireless for example).
| |
|
| |
| == Running Plasma Active in a Virtual Machine ==
| |
|
| |
| When running Plasma Active in a virtual machine, consider that performance will not be as good as when it runs natively on the devices it has been designed for. For testing, we strongly recommend running Plasma Active on a device. The following limitations need consideration when using a virtual machine instead of a real device:
| |
| * Performance, especially graphics, boot and application startup might be reduced
| |
| * Advanced visual effects might not be available or work correctly in the virtual machine. This can lead to degradation of certain features, performance, visual effects and possibly stability
| |
| * User interfaces designed for touch-screens often work less efficiently for mouse and keyboard based input methods, or feel less natural.
| |
|
| |
| We have found VirtualBox to basically work, albeit in some cases the above problems have been noted. Read on for instructions on how to have a first look at Plasma Active, even without suitable hardware.
| |
|
| |
| === Virtual Box ===
| |
|
| |
| Before you can start the image via '''VirtualBox''', please configure the virtual device
| |
| as below.
| |
|
| |
| VirtualBox OSE Manager
| |
| Settings
| |
| ├── General
| |
| │ └── Basic
| |
| │ ├── Name --> e.g. Plasma-contour
| |
| │ ├── Operating System --> Linux
| |
| │ └── Version --> Linux 2.6
| |
| ├── System
| |
| │ ├── Motherboard
| |
| │ │ ├── Boot Order
| |
| │ │ │ ├── CD/DVD-ROM
| |
| │ │ │ └── Hard Disk
| |
| │ │ └── Base Memory --> 1024MB
| |
| │ └── Processor
| |
| │ └── Enable PAE/NX
| |
| ├── Display
| |
| │ └── Video
| |
| │ ├── Video Memory --> 128 MB
| |
| │ └── Enable 3D Acceleration
| |
| └── Storage
| |
| ├── IDE Controller
| |
| │ └── IDE Secondary Master
| |
| │ └── Set up the virtual CD/DVD drive
| |
| │ └── <ISO image>
| |
| └── SATA Controller
| |
| └── Hard Disk
| |
| └── Set up the virtual hard disk
| |
| ├── Dynamically expanding storage
| |
| └── Virtual Size --> 8.00 GB
| |
|
| |
| '''Please note, only live images since ''2011-07-20-10-50-meego-plasma-contour-in-progress-USB-live.iso''
| |
| ''' are runnable via VirtualBox'''.
| |
|
| |
| Please note, if you'd like to install our live image to an VirtualBox hard drive,
| |
| you have to remove the live image from the virtual CD/DVD-ROM after installation.
| |
| This will be done after '''Power off the machine''' via VirtualBox OSE Manager.
| |
|
| |
| Settings
| |
| └── System
| |
| └── Motherboard
| |
| └── Boot Order
| |
| ├── CD/DVD-ROM --> disable
| |
| └── Hard Disk
| |
|
| |
| Once MeeGo/Plasma Active is installed, you may want to [[Plasma/Active/Info/FAQ#How_do_I_get_a_Mouse_Cursor.3F | '''enable the mouse cursor''']].
| |
|
| |
| == Installation of Plasma Active from sources (developer only)==
| |
|
| |
| While the recommended way to test Plasma Active is with the above recipe using the binary packages, it is possible to build Plasma Active from the source repository, anyone who wants to try the versions or get the bleeding edge from the repository can build plasma-mobile from sources.
| |
| The recommended way is to follow the usual kde from sources [http://techbase.kde.org/Getting_Started build instructions]. It is also possible to use the binary kde packages as a base.
| |
|
| |
| It is necessary to install some packages (and their dependencies) to have a working development environment:
| |
| <nowiki>
| |
| sudo zypper install gcc gcc-c++ git cmake, kdelibs-devel
| |
| </nowiki>
| |
|
| |
| === Released Versions ===
| |
|
| |
| Released versions are on the KDE FTP server
| |
| ftp://ftp.kde.org/pub/kde/stable/active/
| |
|
| |
| === Dependencies ===
| |
|
| |
| Those following git repositories are not needed in case of development, but they are needed if you want to package Plasma Active for your distribution:
| |
|
| |
| * StartActive: git://anongit.kde.org/startactive
| |
| * Plasma Mobile config: git://anongit.kde.org/plasma-mobile-config.git
| |
| * Maliit on screen keyboard: git://gitorious.org/maliit/maliit-framework.git
| |
| * Maliit plugin for Plasma Active: git://anongit.kde.org/plasma-active-maliit.git
| |
|
| |
| === Revision Control ===
| |
|
| |
| The latest sources are in KDE's Git repository. Clone the plasma mobile source repository and build:
| |
| <nowiki>
| |
| git clone git://anongit.kde.org/plasma-mobile
| |
| cd plasma-mobile
| |
| mkdir build
| |
| cd build
| |
| cmake .. -DCMAKE_INSTALL_PREFIX=/usr
| |
| make
| |
| sudo make install
| |
| </nowiki>
| |
|
| |
| === Installing Additional Software ===
| |
|
| |
| There are a few KDE projects that have created touch friendly versions of their applications already. These versions are included in the plasma-active repository. Currently, these are:
| |
|
| |
| * Calligra Active - Install package calligra-active
| |
| * Kontact Touch - Install package kontact
| |
| * Bangarang - Install package bangarang
| |
|
| |
| In addition, some applications already work quite well together with active. The following is a list of applications that work ok on a touchscreen:
| |
|
| |
| * Okular - For viewing documents.
| |
| * Marble - Virtual globe, includes routing support.
| |
| * Bangarang - Media player, uses Nepomuk for listing media.
| |
| * Dolphin - File manager.
| |
|
| |
| == Other Systems ==
| |
| If you have installed Plasma Active on a system not yet listed here, please add detailed installation instructions in a new section.
| |
|
| |
| === HP Slate 500 ===
| |
| * Install Instruction:
| |
| This Installaion Procedure is really a mess as you have to patch some files in a unusual way.
| |
|
| |
| ** Step 1 Meego System:
| |
| ***Follow the Instruction at [http://wiki.meego.com/Image_Creation wiki.meego.com/Image_Creation] to build the Meego System using this kickstart file: [[File:Meego-tablet.ks.tar.gz]]. Either install the Image to the Device or build a liveusb image.
| |
|
| |
| ** Step 2 Install kernel
| |
| *** Now we have to compile the kernel i do this from runlevel 3 you get into it by either passing 3 to the kernel boot options or entering "#: init 3". Warning make sure you have your Power Cord plugged in during this, else you have to install the system again in the worst case, after that follow this steps:
| |
| **** 1. first make sure you dont have any kernel images around rpm -e kernel.
| |
| **** 1. cd /root
| |
| **** 2. wget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.2.2.tar.bz2
| |
| **** 3. tar -jxvf linux-3.2.2.tar.bz2 -C /usr/src
| |
| **** 4. cd /usr/src/linux-3.2.2
| |
| **** 5. download the config file [[File:Config-kernel-slate500-1.0.gz]]
| |
| **** 6. run /<path-to-config>/Config-kernel-slate500-1.0.gz > gzip | echo >> /usr/src/linux-3.2.5/.config
| |
| **** 7. make oldconfig
| |
| **** 8. make ARCH=x86 -j2
| |
| **** 9. make ARCH=x86 -j2 modules
| |
| **** 10. make ARCH=x86 -j2 modules_install
| |
| **** 11. make ARCH=x86 -j2 install
| |
| **** 12. cd /boot
| |
| **** 13. /usr/libexec -f /boot/initrd.img-3.2.2 3.2.2
| |
| **** 14. ln -s vmlinuz-3.2.5 extlinux/vmlinuz-3.2.2
| |
| **** 15. ln -s initrd.img-3.2.5 extlinux/initrd-3.2.2
| |
| **** 16. modify extlinux.conf and create a entry to the kernel and pass initrd=initrd-3.2.2 to the "append" Line
| |
| **** For Wifi you have to place the brcm firmware under /lib/firmware you can get it from here [http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git linux-firmware.git]
| |
|
| |
| ** Step 3 Install EMGD
| |
| *** You can download the emgd-1.10 package from [http://www.intel.com/p/en_US/embedded/hwsw/software/emgd Intel] and patch it yourself you can find the patches in [http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/refs/heads yocto-project]. Or you can download this patched emgd driver [http://ultrashare.net/hosting/fl/c93fc80dc5/IEMGD_HEAD_Linux.tar Download]. After Unpacking / Patching run "sh install.sh in the Utilities folder.
| |
|
| |
| *** Xorg configuration Download [[File:09-emgd.conf.tar.gz]] and run "cat 09-emgd.conf.tar.gz > gzip | echo >> /etc/X11/xorg.conf.d/09-emgd.conf"
| |
|
| |
|
| |
| ** Step 4 Reboot
| |
| *** You should now boot directly into Plasma Active with working emgd driver.
| |
