|
|
| (48 intermediate revisions by 12 users not shown) |
| Line 1: |
Line 1: |
| == Install Plasma Active on ARM Systems == | | = Plasma Active Images = |
|
| |
|
| === Mer Plasma Active ===
| | The Plasma Active team provides official Images based on Mer for some devices. |
| 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 [http://wiki.merproject.com/wiki/Community_Workspace Mer Wiki].
| |
|
| |
|
| You can also download the kernel boot image, the external MMC image and some additional helper scripts from basysKom download location [http://share.basyskom.com/contour/Deployment/latest-basyskom-plasma-active-tegra2-mer.html here].
| | == Supported == |
|
| |
|
| === Deploying a Plasma Active (MMC) raw Image to a MultiMediaCard === | | === WeTab / ExoPC === |
| A Installation description for MultiMediaCards could be found in the [http://wiki.meego.com/ARM/N900/Install/MMC MeeGo ARM Wiki].
| |
|
| |
|
| === Other Systems ===
| | The hardware is a little outdated but you will get the most polished Plasma Active experience on this device. |
| ==== Viewsonic Viewpad 10s / Advent Vega / Point of View tablets ====
| |
| Read [http://forum.kde.org/viewtopic.php?f=211&t=99154 KDE Forum page]
| |
|
| |
|
| = Install Plasma Active on x86 Systems =
| | * [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/basyskom-plasma-active-four-wetab-exopc-tablet-mer-release.iso Download ISO] |
| | * [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/basyskom-plasma-active-four-wetab-exopc-tablet-mer-release-iso.sha1 Checksum] (sha1: 51bd1ac2aea097d8e17503a92ce2781a6532491d) |
| | * [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/ Download Archive] |
|
| |
|
| == Live Images==
| | Take a look at the installation instructions [http://community.kde.org/Plasma/Active/WeTab here]. |
| 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 === | | == Preview == |
|
| |
|
| 1. Plug the flashdrive into the WeTab/ExoPC (In some cases WeTab only works with special flashed BIOS from ExoPC).
| | === Nexus 7 === |
|
| |
|
| 2. Get the WeTab/ExoPC running.
| | Even 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] |
|
| |
|
| 3. Press the power (top left underside) + softtouch (top left upperside) buttons until it reboots.
| | === Archos G9 === |
| | |
| 4. When it reboots, press "BBS" to display a boot menu.
| |
| | |
| 5. Choose the flash drive in the boot menu (press the softtouch button briefly to move to the next selection; press the softtouch button longer to emulate Enter).
| |
| | |
| 6. Choose in the boot menu using the softtouch button
| |
| | |
| === Balsam Professional live image (includes live installer) === | |
| [http://open-slx.de open-slx] creates regularly updated packages of Plasma Active which includes a preconfigured Balsam Professional. You can try the Live ISO from a USB stick. Download the Balsam Professional live image [http://download.open-slx.com/iso/12.1/plasma-active-2.iso download.open-slx.com/iso/12.1/plasma-active-2.iso] ([http://download.open-slx.com/iso/12.1/md5sums.txt checksum)].
| |
| | |
| The image plasma-active-2.iso is always the newest one and a link to the plasma-active-<xxx>.iso in the download repo. Please check the changelog and README. The images are also booting WeTabs without flashed BIOS. Remember WeTabs won't start normal usb-sticks. They need a special mbrid-configuration.
| |
| | |
| The image comes with a live-installer. This is currently availible via Konsole. This works:
| |
| | |
| - Download the image and put it on a stick. See also README and Changelog on download.open-slx.com/iso/12.1
| |
| | |
| - connect a usb-keyboard to the system
| |
| | |
| - Boot the stick and wait until Plasma Active is running
| |
| | |
| - Open a konsole and change to root via typing: su -
| |
| | |
| - Enter yast2 live-installer
| |
| | |
| - Follow the instructions. You can configure dualboot, user and partioning the native system
| |
| | |
| If this does not work please contact us on the active mailing list or direcly at open-slx to improve this description with an email:
| |
| | |
| | |
| === Kubuntu Active ===
| |
| | |
| Daily images of a Kubuntu remix with Plasma Active are at
| |
| | |
| http://cdimage.ubuntu.com/kubuntu-active/daily-live/
| |
| | |
| You can burn to CD (e.g. with k3b) or USB (e.g. with usb-creator-kde)
| |
| | |
| https://help.ubuntu.com/community/BurningIsoHowto#Kubuntu
| |
| | |
| It includes an installer '''ubiquity'''
| |
| | |
| === MeeGo live image===
| |
| [http://basyskom.com basysKom] creates regularly updated packages of Plasma Active based on MeeGo.
| |
| | |
| This image is an adaption of the public '''meego-tablet-ia32-pinetrail''' variant and it is bootable on x86 based devices like '''WeTab''', '''ExoPC''' or the '''Idea Pad'''. Login Data: User ''meego'' passwd ''meego''; User ''root'' passwd ''meego''
| |
| | |
| You can try the installable MeeGo Live ISO for a USB flash drive or CD/DVD from [http://share.basyskom.com/plasma-active/wetab.html basysKom download center].
| |
| | |
| === Mer Plasma Active Live (Installable) Image ===
| |
| | |
| [http://basyskom.com basysKom] creates updated packages of Plasma Active based on Mer for testing.
| |
| | |
| This image bootable on x86 based devices like '''WeTab''', '''ExoPC''' or the '''Idea Pad'''. Login Data: User mer passwd mer; User root passwd mer
| |
| | |
| You can try the installable Live ISO from a USB stick. Download the devel or testing iso images from [http://share.basyskom.com/contour/Deployment/mer_x86_usb_live_and_install_archive/ latest demo and stable release live image] ([http://share.basyskom.com/contour/Deployment/mer_x86_usb_live_and_install_archive/]).
| |
| | |
| | |
| <!--
| |
| === 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
| | Take a look at [http://ruedigergad.com/2013/02/24/plasma-active-archos-g9-armv7hl-rootfs-tarballs/ Ruedigers Blog] for more information. |
| 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>'''.
| | === Nokia N950 === |
|
| |
|
| 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).
| | Take a look at [http://www.osnews.com/story/25307/Nokia_N950_Running_Plasma_Active_on_Mer this OSnews article] for more information. |
|
| |
|
| == Running Plasma Active in a Virtual Machine == | | === VirtualBox === |
|
| |
|
| 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: | | 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 | | * 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 | | * 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. | | * 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 ===
| | For detailed installation instructions, see this [http://community.kde.org/Plasma/Active/VirtualBox installation manual]. |
|
| |
|
| Before you can start the image via '''VirtualBox''', please configure the virtual device
| | = Downstream Plasma Active = |
| as below.
| |
|
| |
|
| VirtualBox OSE Manager
| | Some distributions provide Images with Plasma Active for x86 Systems. |
| 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''
| | == Kubuntu Active == |
| ''' are runnable via VirtualBox'''.
| |
|
| |
|
| Please note, if you'd like to install our live image to an VirtualBox hard drive,
| | Current stable release of a Kubuntu remix with Plasma Active is available at |
| 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
| | http://cdimage.ubuntu.com/kubuntu-active/releases/13.04/release/ |
| └── 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''']].
| | Daily unstable images of a Kubuntu Active are at |
|
| |
|
| == Installation on Balsam Professional ==
| | http://cdimage.ubuntu.com/kubuntu-active/daily-live/ |
|
| |
|
| In order to install the latest development snapshots on [http://download.open-slx.com/balsam/professional/iso/12.1 Balsam Professional]. You have to add two repositories to your system.
| | You can burn image to CD (e.g. with k3b) or USB (e.g. with usb-creator-kde) |
|
| |
|
| Important: Since Balsam Professional 12.1 no special KDE updates are needed. Just use the plasma active repo from open-slx.
| | https://help.ubuntu.com/community/BurningIsoHowto#Kubuntu |
| | |
| === Installation Recipe ===
| |
| You can also install plasma active in fist installing a standard desktop environment, add plasma active to the installation and then change the starting UX. We explain this here with a KDE4 live-image that is later changed to plasma active ux.
| |
| | |
| === Preparation ===
| |
| For initial installation, a mouse is helpful and an external keyboard is essential.
| |
| | |
| | |
| As you are going to install packages from a different repository, or so-called "vendor", you can make your life easier by telling zypper to automatically resolve packages across vendors (Each repository is a new vendor). In /etc/zypp/zypp.conf, change the following line
| |
| | |
| solver.allowVendorChange = false
| |
| | |
| to
| |
| | |
| solver.allowVendorChange = true
| |
| | |
| (You don't need to perform the step above if you follow the YaST-based alternatives offered below.)
| |
| | |
| === Repository Setup ===
| |
| Register KDE:Active repositories:
| |
| <nowiki>
| |
| zypper addrepo --refresh \
| |
| http://download.open-slx.com/balsam/professional/distribution/plasma-active/12.1/ plasma-active
| |
| </nowiki>
| |
| | |
| Increase KDE:Active packages' priority, we want the KDE:Active versions that are built with Active-specific options (higher prio than Balsam Professional which is 99 by default):
| |
| <nowiki>
| |
| zypper modifyrepo --priority 90 plasma-active
| |
| </nowiki>
| |
| | |
| (Alternative: Use YaST's Software Repositories feature to add the repository http://download.open-slx.com/balsam/professional/distribution/plasma-active/12.1/, and set its priority to 90.)
| |
| | |
| | |
| === Installation ===
| |
| | |
| In order to install the Plasma Active specific packages and have the device boot into the Active workspace by default, do the following:
| |
| <nowiki>
| |
| zypper install plasma-contour-config plasma-declarative-widgets contour
| |
| </nowiki>
| |
| Make sure you install everything offered from the updated repositories. (The vendor change config option should already take care of that.)
| |
| | |
| == 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/
| |
| | |
| === 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.
| |
| | |
| == MeeGo Installation from meego repository==
| |
| | |
| === Installation ===
| |
| | |
| A repository of most of KDE components, including Plasma Active for MeeGo is at
| |
| https://build.pub.meego.com/project/show?project=Project%3AKDE%3ATrunk%3ATesting and is available for both i586 and ARM, which is added by running the following command if you are using MeeGo trunk | |
| | |
| <nowiki>
| |
| zypper ar http://repo.pub.meego.com/Project:/KDE:/Trunk:/Testing/Trunk/Project:KDE:Trunk:Testing.repo
| |
| </nowiki>
| |
| | |
| or for MeeGo 1.2 users:
| |
|
| |
| <nowiki>
| |
| zypper ar http://repo.pub.meego.com/Project:/KDE:/Trunk:/Testing/MeeGo_1.2_oss/Project:KDE:Trunk:Testing.repo
| |
| </nowiki>
| |
| | |
| To install the software run the following command:
| |
| | |
| <nowiki>
| |
| zypper install plasma-contour-config
| |
| </nowiki>
| |
| | |
| === UX Launch ===
| |
| | |
| uxlaunch is the MeeGo component that actually launches the shell. There are two ways of switching the default MeeGo Tablet UX shell to Plasma.
| |
| | |
| ==== Changing UX permanently ====
| |
| | |
| Edit /etc/sysconfig/uxlaunch and change the session key to "/usr/bin/startkde" (Plasma Active One) or "/usr/bin/startactive" (Plasma Active Two).
| |
| | |
| ==== Dynamic UX selection at boot ====
| |
| | |
| Finally, to switch to using the plasma tablet UX in MeeGo, use the uxselector project, following the instructions found here: http://wiki.meego.com/MeeGo_Desktop/Changing_Desktops#UXSelect_Switcher_Tool_.28alpha.29 - edit the /etc/xdg/aard/uxselect.conf file to include the following section:
| |
| | |
| <nowiki>
| |
| [plasma]
| |
| | |
| name=Plasma Active
| |
| | |
| description=The Plasma Active Tablet UX
| |
| | |
| # Use this in Plasma Active One
| |
| #path=/usr/bin/startkde
| |
| | |
| # Use this in Plasma Active Two
| |
| path=/usr/bin/startactive
| |
| </nowiki>
| |
| | |
| and add the text plasma text to the uxlist property in the General section.
| |
| | |
| ==== Known Issues ====
| |
| | |
| The Meego tablet UX installs a number of files in /etc/xdg/autostart that are also executed when running Plasma Active, resulting in elements of the Meego tablet UX showing up nevertheless. Workaround is to rename/remove that folder.
| |
|
| |
|
| === Installing Additional Software ===
| | It includes an installer '''ubiquity'''. |
|
| |
|
| There are a few KDE projects that have created touch friendly versions of their applications already. These versions are included in the MeeGo repository. Currently, these are:
| | == openSUSE == |
|
| |
|
| * Calligra Active - Install package calligra-active
| | PlasmaActive has been packaged for opensuse in the KDE:Active OBS Repository. |
| * Kontact Touch - Install package kontact-touch
| | Mind that it is ALPHA Quality. The apps that come with a Mer-based image might not be available and there may be bugs. Feel free to report (and fix) them or improve the packaging process. Help will be welcome! |
|
| |
|
| In addition, some applications already work quite well together with Active. The following is a list of applications that work ok on a touchscreen:
| | It can be installed as follows: |
|
| |
|
| * Okular - For viewing documents.
| | zypper ar http://download.opensuse.org/repositories/KDE:/Active/openSUSE_Factory PA |
| * Marble - Virtual globe, includes routing support.
| |
| * Konsole - Support for virtual keyboard
| |
|
| |
|
| == Other Systems ==
| | zypper ref && zypper install plasma-mobile declarative-plasmoids bodega-client |
| If you have installed Plasma Active on a system not yet listed here, please add detailed installation instructions in a new section.
| |
| | |
| === Archos G9 ===
| |
| Read http://basyskom.com/news/138-archos-plasma-active.html
| |
|
| |
|
| === HP Slate 500 ===
| | If the Maliit onscreen keyboard is wanted, additionally install maliit-framework maliit-plugins maliit-inputcontext-qt4 |
| * 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
| | Only i586 has been tested. To run PA4 the preferred method is to create a .xinitrc file in the home directory and add a line saying 'startactive'. Then a call to 'startx' will bring it up. |
| *** 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
| | There currently is an issue with plasma-desktop beeing started automatically so the file '/usr/share/autostart/plasma-desktop.desktop' needs to be (re)moved before running PlasmaActive. |
| *** 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"
| | There is also a LiveCD available at http://susestudio.com/a/GzMWEV/activesuse |
|
| |
|
| | = Get started after install = |
|
| |
|
| ** Step 4 Reboot
| | [http://community.kde.org/Plasma/Active/Info Suggestions, FAQ, additional information] |
| *** You should now boot directly into Plasma Active with working emgd driver.
| |
Plasma Active Images
The Plasma Active team provides official Images based on Mer for some devices.
Supported
WeTab / ExoPC
The hardware is a little outdated but you will get the most polished Plasma Active experience on this device.
Take a look at the installation instructions here.
Preview
Nexus 7
Even 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 Mer Wiki
Archos G9
Take a look at Ruedigers Blog for more information.
Nokia N950
Take a look at this OSnews article for more information.
VirtualBox
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
- 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.
For detailed installation instructions, see this installation manual.
Downstream Plasma Active
Some distributions provide Images with Plasma Active for x86 Systems.
Kubuntu Active
Current stable release of a Kubuntu remix with Plasma Active is available at
http://cdimage.ubuntu.com/kubuntu-active/releases/13.04/release/
Daily unstable images of a Kubuntu Active are at
http://cdimage.ubuntu.com/kubuntu-active/daily-live/
You can burn image to CD (e.g. with k3b) or USB (e.g. with usb-creator-kde)
https://help.ubuntu.com/community/BurningIsoHowto#Kubuntu
It includes an installer ubiquity.
openSUSE
PlasmaActive has been packaged for opensuse in the KDE:Active OBS Repository.
Mind that it is ALPHA Quality. The apps that come with a Mer-based image might not be available and there may be bugs. Feel free to report (and fix) them or improve the packaging process. Help will be welcome!
It can be installed as follows:
zypper ar http://download.opensuse.org/repositories/KDE:/Active/openSUSE_Factory PA
zypper ref && zypper install plasma-mobile declarative-plasmoids bodega-client
If the Maliit onscreen keyboard is wanted, additionally install maliit-framework maliit-plugins maliit-inputcontext-qt4
Only i586 has been tested. To run PA4 the preferred method is to create a .xinitrc file in the home directory and add a line saying 'startactive'. Then a call to 'startx' will bring it up.
There currently is an issue with plasma-desktop beeing started automatically so the file '/usr/share/autostart/plasma-desktop.desktop' needs to be (re)moved before running PlasmaActive.
There is also a LiveCD available at http://susestudio.com/a/GzMWEV/activesuse
Get started after install
Suggestions, FAQ, additional information
