https://techbase.kde.org/api.php?action=feedcontributions&user=Lengau&feedformat=atomKDE TechBase - User contributions [en]2024-03-29T01:24:01ZUser contributionsMediaWiki 1.40.2https://techbase.kde.org/index.php?title=Projects/Mobile/KDE4_on_n810&diff=42874Projects/Mobile/KDE4 on n8102009-07-02T02:51:20Z<p>Lengau: /* Install KDE4 */ Corrected libphonon conflict command</p>
<hr />
<div>The flash memory which stores the maemo operating system on the n810 is too small to install KDE or do program development. In order to install KDE, you need to copy the maemo system from flash to the SD card, and enable booting from there.<br />
==Flash your n810 with the R&D version of Nokia OS==<br />
Update the n810 to the latest version of the operating system and software development environment:<br />
* Optional: Create backup on internal storage device (original state)<br />
* Download [http://tablets-dev.nokia.com/d3.php flasher-3.0] and [http://tablets-dev.nokia.com/nokia_N810.php Nokia OS2008] to the computer you will be flashing the n810 from<br />
* You will need your Product ID (MAC address) to download the Nokia OS. It can be found on your n810 in the Control Panel in About the product, or printed on your battery.<br />
* Turn off your n810 and unplug the power supply; be sure it is fully charged<br />
* Attach the USB cable to your n810 and computer.<br />
* Flash with diablo<br />
sudo ./flasher-3.0 -F RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin -f -R<br />
* When you get the message "Suitable USB device not found, waiting", plug the power supply in to the n810. The flashing will commence.<br />
* When prompted, reboot the n810. You can also disconnect the USB cable.<br />
<br />
==Set Up Partitions and Boot Menu==<br />
Partition the SD card, clone the maemo system to it, and set up a boot menu:<br />
'''WARNING:''' This will erase all existing data on the SD card.<br />
* After booting in to the freshly flashed system...<br />
* Setup networking on the device; this may involve typing your WPA key if it is a secure network.<br />
* '''Do NOT''' install the Nokia Operating System update that's offered by the flashing button in the top bar, that will cause a mismatch in the initfs version and you won't get the boot menu (for a dual boot method that works with updated OS too see the tutorial at http://wiki.maemo.org/Booting_from_a_flash_card)<br />
* Open the Application manager and enable the maemo Extras repository<br />
* Install openssh and set root password<br />
* Optional: Create another backup (mainly as shortcut for enabling the extras repository<br />
* As root, ssh into the n810. /sbin/ifconfig will tell you the associated IP address if you don't know it.<br />
* Install wget and download console-tools.deb in to /root<br />
apt-get install wget<br />
cd /root<br />
wget http://penguinbait.com/console-tools.deb<br />
* Unmount your external media card; if they are not already mounted you don't have to do this<br />
umount /media/mmc1<br />
umount /media/mmc2<br />
* Install the n810 console-tools:<br />
dpkg -i console-tools.deb<br />
* Disable virtual memory if active, in the Control Panel.<br />
* The next step is to repartition and format your SD card. NOTE: This will '''ERASE''' all the data on it, so be careful when doing it.<br />
* Run pbeasy in an X-terminal on the n810, as a user (not root). Select the Partition option, and for a 1920 Mb SD card, enter 120 Mb for both VFAT and swap partitions, which leaves the rest for an EXT3 partition which will be used for the software development system. After partitioning, it will reboot.<br />
* After the reboot, run pbeasy again, and select the Clone option. This formats the new partitions, clones the maemo system from the flash onto the SD card's EXT3 partition and sets up a boot menu to allow either flash or SD card system to be selected at boot time.<br />
* Reboot the n810 and you should now see boot menu options.<br />
* Select the Internal MMC card option and check that it boots successfully. If not, try repeating the Clone process - it should work on the second attempt.<br />
<br />
==Install KDE4==<br />
* During the boot up, hold the memory key (lower left on the drawer keyboard, right under the direction pad) and you'll get a boot menu. Choose the third option (External MMC card) to boot from SD, the first one will boot from flash.<br />
* From your computer, use Kwrite or Kate, and point it to sftp://root@192.168.1.14/etc/apt/sources.list.d/hildon-application-manager.list and add Marijn's repos. Alternatively you can ssh in to the n810 and edit the file with vi. Here is my complete list of repositories:<br />
<br />
deb http://catalogue.tableteer.nokia.com/certified/ diablo user<br />
deb http://catalogue.tableteer.nokia.com/non-certified/ diablo user<br />
deb http://catalogue.tableteer.nokia.com/updates/diablo/ ./<br />
deb http://repository.maemo.org/extras/ diablo free non-free<br />
deb http://repository.maemo.org/extras-devel/ diablo free non-free<br />
deb http://93.157.1.37/~marijn/maemo binary/<br />
deb http://qt4.garage.maemo.org/ diablo extras<br />
<br />
* SSH in to the n810 and update the package list<br />
apt-get update, <br />
* Remove the install tools since you don't need them anymore<br />
dpkg --purge install-tools-n810e <br />
* Install KDE4. This should pull in all the necessary dependencies (75MB of packages) as well. I had to force install kdebase-workspace to start plasma on the device. You can do that from a remote ssh session with su user and setting the display export DISPLAY=:0.<br />
apt-get install kdebase-workspace kdebase-runtime kdeplasma-addons<br />
<br />
* If you get a conflict between libqt4-phonon and libphonon4 you have to go to the /var/cache/apt/archives directory and install one manually via <br />
dpkg --force-overwrite --install libphonon4_4\%3a4.3.0-1_armel.deb<br />
<br />
* If that all works, you can replace the hildon desktop with plasma. At the moment it crashes and reboots the n810, so you might not want to do this. <br />
cd /usr/bin/ && mv hildon-desktop hildon-desktop-real && ln -s plasma hildon-desktop<br />
* Have fun!<br />
<br />
This is an updated version of [http://vizzzion.org/stuff/howto-dualboot.txt Sebas' HowTo].</div>Lengauhttps://techbase.kde.org/index.php?title=Schedules/KDE4/4.0_Release_Schedule&diff=15186Schedules/KDE4/4.0 Release Schedule2007-10-30T21:27:59Z<p>Lengau: Moved Release Freeze (2007-10-24) and Development Platform (2007-10-30 [today]) to Past Milestones section</p>
<hr />
<div>All dates given here are subject to revision, but we will try our best to stick to them if possible.<br />
Note that "Tagging" that the codebase is closed for this release on the date mentioned. The tarballs<br />
and packages are then being prepared and released approximately one week later.<br />
The KDE Release Team is acting as the coordinator for the 4.0 release.<br />
<br />
Note the release is done in two portions: the '''KDE Development Platform 4.0''' and the '''KDE Desktop 4.0'''. See the [[#KDE_Components|KDE Components Definition]] for details what SVN modules the two portions include. Note the earlier freeze date for the platform and make sure you don't miss the deadline to get your fixes in.<br />
<br />
Milestones help guide us toward a final release, and the '''dates are subject to change'''. For more details see our [[Schedules/KDE4/4.0_Release_Roadmap|roadmap]].<br />
<br />
All deadlines are due 23:59 in your local timezone.<br />
<br />
If in doubt about any milestones please ask the [mailto:release-team@kde.org release team] or your module maintainer.<br />
<br />
= KDE 4.0 Release Schedule =<br />
<br />
== Definitions ==<br />
<br />
=== KDE Components ===<br />
* '''Platform''' (libraries and runtime dependencies): kdelibs, kdepimlibs, kdebase-runtime, kdebindings<br />
* '''Workspace''' (desktop infrastructure, window manager, plasma): kdebase-workspace, extragear-plasma<br />
* '''Applications''' (core applications): kdeaccessibility, kdeadmin, kdeartwork, kdebase-apps, kdeedu, kdegames, kdegraphics, kdemultimedia, kdenetwork, kdepim, kdesdk, kdetoys, kdeutils<br />
* '''Desktop''': Workspace and Applications<br />
<br />
=== Freeze States ===<br />
<br />
* '''Soft Freeze''': no new features, bufixes only, incomplete features are disabled<br />
* '''Hard freeze''': as soft freeze plus: only patches which have been reviewed on the relevant mailing lists, no new or changed messages<br />
* '''Tagging Freeze''': only allowed changes: compile fixes, reviewed fixes of blocker bugs, changes needed to build the release tarballs<br />
<br />
== Upcoming milestones ==<br />
<br />
These are the upcoming milestones. When they have been passed move them to the top of the [[#Past_Milestones|Past Milestones]] section.<br />
<br />
=== 14 November 2007: Tagging RC 1 ===<br />
* Hard freeze Desktop<br />
* Message Freeze<br />
* Workspace interface freeze (source and binary compatibility until KDE 4.1)<br />
* Tagging freeze until tarballs are ready<br />
* Tag Platform 4.0.0<br />
* Tag Desktop 3.96 (RC 1)<br />
<br />
=== 20 November 2007: Release KDE Development Platform 4.0.0 and KDE Desktop 4.0 RC 1 ===<br />
* Announce release<br />
* Make tarballs available on download servers<br />
<br />
=== 5 December 2007: Tagging RC 2 (final) ===<br />
* decide if RC 3 is needed, if it is, add another RC to the cycle, if not proceed with the following:<br />
* Create 4.0 branch<br />
* Hard freeze on the 4.0 branch<br />
* Tagging freeze on the branch until release tarballs are ready<br />
* Tag Platform 4.0.1<br />
* Tag Desktop 4.0.1 (RC 2)<br />
* Trunk is unfrozen and open for 4.1 development<br />
<br />
=== 11 December 2007: Release KDE 4.0 ===<br />
* Announce release<br />
* Make tarballs available on download servers<br />
* Party<br />
<br />
=== Tentatively early January 2008: first bugfix release (4.0.2) ===<br />
<br />
=== 18 January 2008: KDE 4 Launch Event ===<br />
<br />
== Past Milestones ==<br />
<br />
These milestone have already been passed. They are listed in reverse chronological order to keep the most recent milestones at the top of the list.<br />
<br />
=== 30 October 2007: Release KDE Development Platform 4.0 RC 1 and KDE Desktop 4.0 Beta 4 ===<br />
* Announce release<br />
* Make tarballs available on download servers<br />
<br />
=== October 24, 2007: KDE 4 Release Freeze === <br />
<br />
* Platform interface freeze (source and binary compatibility until KDE 5)<br />
* Hard freeze Platform<br />
* Soft freeze Desktop<br />
* Release Freeze until release tarballs are ready (estimated two days)<br />
* Tag Platform 3.95 (RC 1)<br />
* Tag Desktop 3.95 (Beta 4)<br />
<br />
=== October 8, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Beta_Cycle|Beta3]] ===<br />
Beta 3 is prepared, initially tested and released on October 18.<br />
<br />
=== October 8, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Beta_Cycle|KDE Development Platform frozen solid]] ===<br />
The KDE Development Platform is frozen. For the modules that are included in the KDE Development Platform, only patches reviewed on the development lists are permitted. If in doubt, contact the release coordinator. The ''KDE Development Platform'' covers kdesupport, kdelibs, kdepimlibs, kdebase/runtime and kdebindings (Ruby and Python bindings only).<br />
<br />
=== August 29, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Beta_Cycle|Beta2]] ===<br />
[http://dot.kde.org/1189078926/ Beta 2] is prepared and released after some initial testing.<br />
<br />
Trunk is frozen for feature commits. i18n string changes are allowed.<br />
<br />
=== July 26, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Beta_Cycle|Beta1]] ===<br />
Beta 1 is prepared and released after some initial testing.<br />
<br />
=== July 24, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Core_Library_API_Freeze|Core Library Freeze]] ===<br />
The core library APIs are frozen solid.<br />
<br />
=== June 27, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Alpha2_Release|Alpha2 Tagging]] ===<br />
The Alpha2 will be source only -- without translations.<br />
<br />
=== June 1, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Module_Freeze|trunk/KDE is module frozen]] ===<br />
Trunk is frozen for new or resurrected applications.<br />
<br />
A list of main modules that will be included in the final release will be made.<br />
<br />
=== May 3, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Alpha_Release_Tagged|Alpha Tagging]] ===<br />
The Alpha will be source only -- without translations.<br />
<br />
=== May 1, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_kdelibs_Soft_API_Freeze|kdelibs Soft Freeze]] ===<br />
The kdelibs API is "soft-frozen", meaning that changes can be made but only with the consent of the core developers.<br />
<br />
=== April 2, 2007: [[Schedules/KDE4/4.0_Release_Roadmap#Milestone:_Subsystem_Freeze|Subsystem Freeze]] ===<br />
From this date forward, no new KDE subsystem or major changes can be committed to kdelibs.<br />
<br />
The buildsystem requirements (i.e. cmake version) are fixed.<br />
<br />
=== February 2007: Technical Preview 3 ===<br />
The [http://dot.kde.org/1172249109/ third technical preview], a developer release.<br />
<br />
The kdelibs API will remain as stable as possible after that, so that application developers (in particular those not having their code in the KDE SVN) can start porting towards a stable kdelibs API.<br />
<br />
Of course the applications in the KDE SVN will have been ported all along, and it will possible to alpha-test them at this stage.<br />
<br />
=== November 2006: Technical Preview 2 ===<br />
The [http://dot.kde.org/1162475911/ second technical preview], a developer release.<br />
<br />
=== August 2006: Technical Preview 1 ===<br />
The [http://dot.kde.org/1155935483/ first technical preview], a developer release.</div>Lengau