OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: ShiroiKuma on December 30, 2005, 12:50:44 pm
-
KDE 3.5 as compiled by Sash for beta1 runs fine but is too big for the internal memory.
I've made a squashfs image of the complete KDE packages from Sash stripped of some stuff I consider unnecessary. This image is slightly over 50 megs.
Now I run KDE from the internal RAM and it runs super smoothly. It's much faster than from an SD or CF and everything is fine, you can suspend, resume, no probs...
I'll post the image with instructions how to install it after the weekend when I can upload.
In the meantime, Sash can you post the Kde headers and includes, so that we can compile for KDE too? I wanted to try compile skim for KDE, but can't do it without the headers and includes...
Later,
ShiroiKuma
-
Great! I will surely go for this one!
Well, should I force myself to stop saying any more "Thanks!", "Very nice!", "Great!", etc, because I find myself doing this so much in this forum these days...
-
screenshots ?
-
Well done for this. What have you removed from it? Would be useful to know, just in case it is vital for someone!
-
anyone smart enough to prepare a pdaxrom-setup for kde? something similar to what we have seen for fwwm and icewm, or detailed instruction like those by Chero for xfce4? KDE is not that slow, but lacks some useful customization.
-
KDE 3.5 seems to be a hell of a lot faster than the 3.4 package provided with rc10.
What I miss is a battery-applet, is it just me, or is it really missing.
I created a seperate "startkde2" and "xinitrc.kde", the same way as I did for xfce4. Now I can choose (startx, startxfce4 or startkde2).
I'm not really a kde-fan, but it's nice to show off !! I went to a meeting of the local linux-user-group, I think a few Z's are going to be bought in the upcoming weeks.
Have fun,
Chero.
-
KDE 3.5 seems to be a hell of a lot faster than the 3.4 package provided with rc10.
What I miss is a battery-applet, is it just me, or is it really missing.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109199\"][{POST_SNAPBACK}][/a][/div]
It is a hell-of-a-lot faster.
For battery use mb-applet-battery. It also has the advantage that this way the Light & Power settings work, i.e. if you set it to suspend after a period of inactivity it'll work. Without the mb-applet-battery, it doesn't.
-
OK, here goes. Here is the KDE 3.5 package which you can run off the internal flash. BTW it is for the SL-C860, didn't test on any other machine, so don't blame me if it doesn't work.
1. Don't install any of the KDE packages found in the feed, if already installed, uninstall them before proceeding.
2. mkdir /usr/lib/kde3. mkdir /usr/lib/kde/kde3.54. mkdir /usr/lib/kde/kde3.5additional5. Download the KDE 3.5 stripped package (http://shiroikuma.com/peiji/hoka/peiji/linazau/peiji/sofuto/kde_3.5.0_stripped.squashfs) and put it in /usr/lib/kde
It's 60 meg so you need to have this much space in the internal flash.
6. Download the KDE 3.5 additional package (http://shiroikuma.com/peiji/hoka/peiji/linazau/peiji/sofuto/kde_3.5.0_additional.squashfs) and put it somewhere on an SD. It contains all the stuff taken out by me from the full install, i.e. kstars, kgeography, and basically all the stuff which I deemed I'm never likely to use. You don't have to use this package if you don't want to. If you do, you will have the full KDE 3.5 installation where this additional stuff is gonna run off of the SD.
7. Install squashfs utils from the pdaXrom unstable feed (http://www.pdaxrom.org/ipk_feed.php?menuid=11&getfile=kernel-modules-and-util-squashfs_2.4.18_armv5tel.ipk&ipkname=kernel-modules-and-util-squashfs&ipktable=unstableipkfeed).
8. Install KDE 3.5 stripped symlinks ipkg (http://shiroikuma.com/peiji/hoka/peiji/linazau/peiji/sofuto/kde-symlinks-stripped_3.5.0-1_armv5tel.ipk). Install it to internal flash.
9. If you want to use the additional package from step 6, install the KDE 3.5 additional symlinks ipkg (http://shiroikuma.com/peiji/hoka/peiji/linazau/peiji/sofuto/kde-symlinks-additional_3.5.0-1_armv5tel.ipk). Install it to internal flash.
10. Edit the startkde file. If you don't know where it is, find it by which startkdeAt the beginning of the file, right after #!/bin/sh add the following line mount -t squashfs - o loop /usr/lib/kde/kde_3.5.0_stripped.squashfs /usr/lib/kde/kde3.5at the complete end of the file add the following line umount /usr/lib/kde/kde3.511. If you want to use the additional package from step 6, edit the startkde file again an at the beginning of the file add the following line mount -t squashfs - o loop /mnt/sd/kde_3.5.0_additional.squashfs /usr/lib/kde/kde3.5additional assuming you put the package in /mnt/sd/
at the complete end of the file add the following line umount /usr/lib/kde/kde3.5additional
And that's it, now you can start KDE by startkde
You will really feel the difference in how much smoother it'll run, compared with running from an SD.
The first time it starts it'll be very slow, because it'll bring up the language etc. configuration dialog. After that, no probs.
Let me know how it works for you.
-
Cool! This thread should be pinned, right?
It seems the kernel-modules-and-util-squashfs_2.4.18_armv5tel.ipk is for Cxx0 and not the Cxk, which should be 2.4.20, right? But I don't see it in the feeds...
-
Cool! This thread should be pinned, right?
It seems the kernel-modules-and-util-squashfs_2.4.18_armv5tel.ipk is for Cxx0 and not the Cxk, which should be 2.4.20, right? But I don't see it in the feeds...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109208\"][{POST_SNAPBACK}][/a][/div]
I'm using them on an 860. Don't know if you can use it on the 6000 or 3100.
-
I've made a Japanese locale ipk for KDE 3.5. The above squashfs image already contains it, so no need to install it. You can select either a US English or a Japanese locale in it.
For users of the KDE ipks from the feed, you can download the locale ipk here (http://shiroikuma.com/peiji/hoka/peiji/linazau/peiji/sofuto/kde-i18n-japanese_3.5.0_armv5tel.ipk) and install it regularly.
-
wow -- thanks again!
mirrored: http://zaurus.spy.org/feeds/cacko/pdaXrom/...-7x0-860/kde35/ (http://zaurus.spy.org/feeds/cacko/pdaXrom/1.1.0/beta1/Zaurus-7x0-860/kde35/)
-
Problem:
In #10, startkde is not found.
/usr/lib/kde/bin/startkde is symlinked to /usr/lib/kde/kde3.5/bin/startkde, but the latter does not exist. /usr/lib/kde/kde3.5/bin/ is empty.
updated:
/usr/lib/kde/kde3.5/bin/startkde is in the squashfs image, which is read only, so there is no way to edit it.
Any idea? Thanks!
-
updated:
/usr/lib/kde/kde3.5/bin/startkde is in the squashfs image, which is read only, so there is no way to edit it.
Any idea? Thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109245\"][{POST_SNAPBACK}][/a][/div]
OK, I will fix this when I can upload again. In the meantime, the fix is:
1. rm /usr/lib/kde/bin/startkde2. Mount the image by mount -t squashfs - o loop /usr/lib/kde/kde_3.5.0_stripped.squashfs /usr/lib/kde/kde3.53. cp /usr/lib/kde/kde3.5/bin/startkde /usr/lib/kde/bin/4. umount /usr/lib/kde/kde3.5
Now you can edit the startkde as per point 10 above and start KDE regularly.
-
Thanks! It works now.
I'm trying to use KDE as the default by doing:
ln -sf /usr/lib/kde/bin/startkde ~/.xinitrc
startxNeed to turn on swap (64MB on SD) coz KDE seems to eat up a lot of system memory.
Continue exploring ...
Great job! ShiroiKuma and Laze!
-
Some notes:
-- Need to install pcre to get Konqueror to run;
-- Konqueror run quite fast (compared to Firefox), but seems not to be able to take my own unicode TTF.
-- Knotes, KOrganizer, etc, complain about missing libqui.so.1 and cannot be launched.
-- Fn key does not work (even though it is mapped in xmodmap.corgi
-
Some screenshots:
(1) Loading for the first time (set as the default WM and run directly from the console), with great expectations and excitement!
[ You are not allowed to view attachments ]
(2) Oops... WOE is this Crash Handler? (but gone once configured the desktop).
[ You are not allowed to view attachments ]
(3) First things first. Tune the desktop a little bit now. The setup screens themselves are already quite some eye candies.
[ You are not allowed to view attachments ]
(4) KDE desktop in the initial state. Looks cool even without much decoration and tweaking.
[ You are not allowed to view attachments ]
(5) Test run #1: AbiWord ... [OK]
[ You are not allowed to view attachments ]
(6) Test run #2: Konqueror ... [OK] (need pcre package; load in about 1 minute, but smooth afterwards; doesn't seem to like my unicode TTF fonts?)
[ You are not allowed to view attachments ]
-
Some screenshots:
(1) Loading for the first time (set as the default WM and run directly from the console), with great expectations and excitement!
[ You are not allowed to view attachments ]
(2) Oops... WOE is this Crash Handler? (but gone once configuring the desktop).
[ You are not allowed to view attachments ]
(3) First things first. Tune the desktop a little bit now. The setup screens themselves are already quite some eye candies.
[ You are not allowed to view attachments ]
(4) KDE desktop in the initial state. Looks cool even without much decorations and tweaking.
[ You are not allowed to view attachments ]
(5) Test run #1: AbiWord
[ You are not allowed to view attachments ]
(6) Test run #2: Konqueror (need pcre package; load in about 1 minute, but smooth afterwards; doesn't seem to like my unicode TTF fonts?)
[ You are not allowed to view attachments ]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109316\"][{POST_SNAPBACK}][/a][/div]
nice screens!
expect of pic 3... it isnt working.
cant await to get beta1 with kde on my c3100... but i need a bigger sd card before.
-
Sorry I previouly put up a wrong gif. Now corrected with the desired animated one.
-
So would Laze and other kindheaterd people please compile a kernel-modules-and-util-squashfs for Cxk (2.4.20), so that everyone can run (or just try) this ultimate giant killer on pdaX?
-
I'm having trouble resolving shiroikuma.com - could someone post the IP address please?
EDIT: Sorry, I missed ScottYelich's mirror - thanks very much for this. Still can't resolve the original links though
PS MONVMENTVM - you can remove the label telling you how to rotate the screen on your Z, you know
-
-- Knotes, KOrganizer, etc, complain about missing libqui.so.1 and cannot be launched.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109302\"][{POST_SNAPBACK}][/a][/div]
Install libqui from the feed, they all work fine.
-
Thanks again. It's working now.
-
Hello,
This is exciting!
Does anyone else run out of installable memory on a C1000 to the point where they can't install anything after they've copied the squashfs file?
Knowing me, I'm doing something simple, wrong.
-
Thanks again. It's working now.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109336\"][{POST_SNAPBACK}][/a][/div]
Does KOrganizer load faster than KO-PI using matchbox ?
-
(6) Test run #2: Konqueror ... [OK] (need pcre package; load in about 1 minute, but smooth afterwards; doesn't seem to like my unicode TTF fonts?)
[ You are not allowed to view attachments ]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109316\"][{POST_SNAPBACK}][/a][/div]
..not for me on 860! From a 40x Lexar SD Card it loads in approx 15 secs.
You probably didn't have pcre and Konqueror was struggling...
Ant
P.S. I have also 64 MB swap
-
(6) Test run #2: Konqueror ... [OK] (need pcre package; load in about 1 minute, but smooth afterwards; doesn't seem to like my unicode TTF fonts?)
[ You are not allowed to view attachments ]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109316\"][{POST_SNAPBACK}][/a][/div]
..not for me on 860! From a 40x Lexar SD Card it loads in approx 15 secs.
You probably didn't have pcre and Konqueror was struggling...
Ant
P.S. I have also 64 MB swap
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109371\"][{POST_SNAPBACK}][/a][/div]
Oh, really? I did have the pcre_5.0_armv5tel.ipk package installed but it still takes such a long time to load. Or did I miss something here? I also have 64MB swap on SD.
Konqueror just has a central place in KDE, it would be wonderful it can run that fast ...
-
Thanks again. It's working now.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109336\"][{POST_SNAPBACK}][/a][/div]
Does KOrganizer load faster than KO-PI using matchbox ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109366\"][{POST_SNAPBACK}][/a][/div]
Frankly, KOrganizer and other KDE PIM stuff are loading rather slowly in my case. Still wondering why...
Also the Fn key cannot function as Mode_switch, which may be a stopper for many (including me, maybe )
-
[Frankly, KOrganizer and other KDE PIM stuff are loading rather slowly in my case. Still wondering why...
Also the Fn key cannot function as Mode_switch, which may be a stopper for many (including me, maybe )
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109403\"][{POST_SNAPBACK}][/a][/div]
FYI I formatted without user partition: only 121mb root.
Till now it looks promising...
Ant
-
Same here. I flashed 1.1.0 with 121MB root partition.
Ant, could you tell me if there's any trick to make Konqueror run faster? Thanks!
[Update: Found a solution to perhaps a non-question. I installed both pcre3_3.4-1.1_armv5tel.ipk and pcre_5.0_armv5tel.ipk. Removing the former and Konqueror loads faster within 30 seconds (close to about 15, right?) Or am I mistaken? ]
[Update 2: After trying a few times Konqueror recognizes my TTF. But I read from the official site FAQ (http://#ThestartuptimeofKonqEisveryslowwhenusingQtEmbeddedIsthereahiddenturboboostconfiswitchtoaccelerateittolightspeed) that the browser will spend a lot of time reading TTF fonts and it is recommended to use qpf instead. But this may not apply to pdaX, which uses TTF generally.
http://www.konqueror.org/embedded/ (http://www.konqueror.org/embedded/)
Then I tried the Configuring Konqueror > Performance > Preloading and checked "Preload an instance after KDE startup" . It then reduced the startup time to about 16 seconds.]
KOrganizer loads in around 1 minute 30 seconds. And it always loads together with the KOrganizer Reminder Client, which I guess may slow down things a bit. I tested again by closing KOrganizer and restarted it with the Reminder Client still opened, and it took 1 minute.
Found another issue:
The last line, umount /use/lib/kde/bin/startkde , in startkde fails to execute. Upon logging out a KDE session and returning to the console, it reads device is busy and so /use/lib/kde/kde3.5 cannot be umounted. Need to umount manually. If not then it will be mounted multiple times.
-
Same here. I flashed 1.1.0 with 121MB root partition.
Ant, could you tell me if there's any trick to make Konqueror run faster? Thanks!
Found another issue:
The last line, umount /use/lib/kde/bin/startkde , in startkde fails to execute. Upon logging out a KDE session and returning to the console, it reads device is busy and so /use/lib/kde/kde3.5 cannot be umounted. Need to umount manually. If not then it will be mounted multiple times.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109409\"][{POST_SNAPBACK}][/a][/div]
Let me back home in an hour or so...
I remember I installed bluetooth libs, hostapd and wpa-supplicant.
Then I read your posts and installed pcre and libqui, then created a swapfile.
Just this...nothing special.
Oh, YES, there is the issue with the squashfs: workaround is to mount the partitions by hand and then the symlink to startkde works.
Me too I created the symlink: ln -sf /usr/lib/kde/bin/startkde /home/root/.xinitrc, this way after the mount I simply type startx.
I'll create a script and post it later on.
In the meanwhile I guess ShiroiKuma is already working on the issue...and posting a new how-to!
Thanks Shiroi-Guy!
Ant
-
I tried this and Fn seems to kinda work in KDE.
I copy this from the .xinitrc created by matchbox to startkde, directly under the mount line and before all the KDE startup stuff: (well of course only the lines for corgi.xmodmap matters here but I'm just doing it in a sloppy way)
#!/bin/sh
mount -t squashfs - o loop /usr/lib/kde/kde_3.5.0_stripped.squashfs /usr/lib/kde/kde3.5
case "$MODEL" in
 SL-C860|SL-C760|SL-C750|SL-7500|SL-C700)
test -f /etc/X11/kb/corgi.xmodmap && xmodmap /etc/X11/kb/corgi.xmodmap
;;
 SL-6000)
test -f /etc/X11/kb/tosa.xmodmap && xmodmap /etc/X11/kb/tosa.xmodmap
;;
 SL-C1000|SL-C3000|SL-C3100)
test -f /etc/X11/kb/akita.xmodmap && xmodmap /etc/X11/kb/akita.xmodmap
;;
 *)
cat /proc/cpuinfo | grep 'Sharp-Collie' 2>/dev/null >/dev/null && test -f /etc/X11/kb/collie.xmodmap && xmodmap /etc/X11/kb/collie.xmodmap
;;
esac
test -f /etc/X11/kb/userdefined.xmodmap && xmodmap /etc/X11/kb/userdefined.xmodmap
#
# DEFAULT KDE STARTUP SCRIPT ( KDE-3.5 )
...
...
So the reason for the previouly Fn-key-not-working issue seems to be that xmodmap, including the userdefined.xmodmap, is not (properly) referenced to in the original startkde. Maybe I am just wrong here.
Anyways now I regain control of the Fn key and it can type all the 'blue' chars such as underscore, although zooming and backlight (Fn+1-4) are not working (or perhaps will not?).
-
A few more things:
-- Xpad is a very good replacement of KNotes.
The original KNotes is running not fast enough. Then I use Xpad, which runs much faster and eats less memory than KNotes, and it can even be automatically docked to the panel as an applet along with clipboard. Double click/tap it will open a new sticky note, which comes very handy.
-- The PIM apps as separate packages?
I wonder if the road can go further down by stripping away the KDE pim stuff (KOrganizer, Kontact, etc) as separate packages, because they are too slow and resource-hungry to be usable on Z. Also they take up no small space in the image, i guess?
-- App icons on cards?
Apps installed on my SD lost their icons in the paths. And the Menu Editor doesn't accept icons from external media.
So far my impression: indeed KDE3.5 is pretty heavy on Z, even though it is now installed to the internal memory. But I believe there are some ways to fine-tune it (e.g. further strip down things) to make it more usable and less demanding on Z.
By the way, is there anyone also trying/testing/using it here?
-
Yes it is indeed heavy.
I'm sed to report that after some use Konqueror loads now slower, in 40 seconds approx.
Stability of the KDE interface is very good, and the eye-candies are there!
I have some glitches after resuming from suspend (I have to resume 3 times, doesn't wake up well on first try!). Should try with mb-applet.
BTW I couldn't find anything Bluetooth-related in the Shiroi image AND in the KDE from the feed.
Stripped out?
-
Hello,
This is exciting!
Does anyone else run out of installable memory on a C1000 to the point where they can't install anything after they've copied the squashfs file?
Knowing me, I'm doing something simple, wrong.Â
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109357\"][{POST_SNAPBACK}][/a][/div]
Yes, it's one of biggest moments ever in my pdaX experience.
I flashed 1.1.0 Beta, and then set up KDE3.5 immediately before installing any other apps. After this there remains about 12MB (forgot exactly how much) in the internal memory.
I'm sure we can have a lot more space if we can do without the PIM apps...
-
I have some glitches after resuming from suspend (I have to resume 3 times, doesn't wake up well on first try!). Should try with mb-applet.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109468\"][{POST_SNAPBACK}][/a][/div]
Yes, I begin to experience the same issue. Resuming sometimes fails and it goes to sleep very quickly. The workaround is to tap on some icons fast enough before it gets dark again ... This is more obvious with AC plugged in. I can verify now that it is an issue with KDE, not 1.1.0 Beta, as this doesn't happen in matchbox.
-
Yes, it's one of biggest moments ever in my pdaX experience.
Ditto... I did pretty much the same (finally) on my new SL-C3100. Put pdaxrom on, repartitioned the HD (and setup swap), and installed KDE 3.5
Error free, looks great, and I had to show everyone at work. Problem is each time I clicked on anything I had to say "wait... wait... hold on..." and shorlty realized this is just too heavy for my little pda to handle.
Totally awesome that it works, but the realistic performance is a very big dissapointment, esp since I upgraded to the SL-C3100 just to do this.
-
Walt, do you use the packages or the squashfs image?
I'm also curious to know how fast is it running in hdd in your C3100, e.g. desktop startup, konqueror, korganizer, etc? Thanks!
P.S.
Actually what I wanted to say is: Yes, it's one of "biggest" moments ever in my pdaX experience.
-
Yet another question:
How to map the applications keys? It seems running inputsetup.py in KDE does not take any effect. Thanks!
-
Yet another question:
How to map the applications keys? It seems running inputsetup.py in KDE does not take any effect. Thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109605\"][{POST_SNAPBACK}][/a][/div]
Sorry... this happens again! I forgot how many times I got a blink right after asking a stupid question.
Go to Control Center > Regional and Accessibility > Keyboard Shortcuts > Command Shortcuts (in the right pane), select the application you want to assign a key to, and then click the 'custom' bullet. When done, press 'Apply' to save your settings.
-
Walt, do you use the packages or the squashfs image?Â
I'm also curious to know how fast is it running in hdd in your C3100, e.g. desktop startup, konqueror, korganizer, etc? Thanks!
I installed from the packages... actually just the base, lib, and pim. 128meg swap partition enabled as well on hdd.
Desktop Startup : 1 minute 50 seconds (after waiting for ipkg to finish up because that takes forever)
Konqueror : 50 seconds (including default Conquer your desktop! page load)
Konqueror 2nd : 22 seconds (including default Conquer your desktop! page load)
Konsole : 10 seconds
Konqueror 3rd : 30 seconds (including default Conquer your desktop! page load)
I need to add some lib to get korganizer working and will up date this post with those times later tonight.
UPDATE:
Korganizer : 55 seconds
Abiword : 30 seconds
Kmail : 50 seconds
-
So it seems our results are very close.
I just use mrxvt instead of Konsole for it runs a hell lot faster, plus the multi-tabs.
Still hoping for separating the KDE PIM stuff from the rest. Way too heavy for Z.
Perhaps a 'KDE Lite' isn't really a bad idea, is it?
-
Walt, do you use the packages or the squashfs image?
I'm also curious to know how fast is it running in hdd in your C3100, e.g. desktop startup, konqueror, korganizer, etc? Thanks!
I installed from the packages... actually just the base, lib, and pim. 128meg swap partition enabled as well on hdd.
Desktop Startup : 1 minute 50 seconds (after waiting for ipkg to finish up because that takes forever)
Konqueror : 50 seconds (including default Conquer your desktop! page load)
Konqueror 2nd : 22 seconds (including default Conquer your desktop! page load)
Konsole : 10 seconds
Konqueror 3rd : 30 seconds (including default Conquer your desktop! page load)
I need to add some lib to get korganizer working and will up date this post with those times later tonight.
UPDATE:
Korganizer : 55 seconds
Abiword : 30 seconds
Kmail : 50 seconds
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109647\"][{POST_SNAPBACK}][/a][/div]
And for me the same .
(installed on hdd - 64Mb swap)
BTW : why so much fuss about load-time. I leave the apps I need open and just suspend.
I agree it's a bit heavy for a little Z, but it works !!
For daily use I'll stick to xfce, but next time I go to a meeting of the local linux-user-group, I'll start kde and some apps before I leave home, then suspend, and resume at the meeting to show off. Let's just hope nothing freezes.
Have fun,
Chero.
-
BTW : why so much fuss about load-time. I leave the apps I need open and just suspend.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=109666\")
Yeah, that's what I do too. Basically, I have 6 desktops on KDE, divided thematically into what I use - language study, pim, konsole, etc. and it works fine while up and running. Starting KDE itself, or Firefox is a drag, but once up it works.
I use a 512 meg swap on a CF, with it it works fine.
The only problem I had was the time synchronization bug on suspend and resume, which I've taken care of as [a href=\"https://www.oesf.org/forums/index.php?showtopic=14655&hl=hwclock]described here[/url].
Zdevil, I think this might also be the case for your crashes on resume that you mention. I've never had such a crash with KDE, but have had the time-lag problem. Now it's gone.
-
Anybody else having problems with kaddressbook? It seems that when there are no contacts, i.e. I delete the vcf file, it loads fine and runs. When I enter even one contact though, then save, close, and restart, it loads the main stcreen, shows no contacts and gets stuck forever, as if running something in the background.
If you switch to another app and then come back you only see a white window.
What's the problem here?
-
Alright, let's talk 'big'.
Walt, do you use the packages or the squashfs image?Â
I'm also curious to know how fast is it running in hdd in your C3100, e.g. desktop startup, konqueror, korganizer, etc? Thanks!
I installed from the packages... actually just the base, lib, and pim. 128meg swap partition enabled as well on hdd.
Desktop Startup : 1 minute 50 seconds (after waiting for ipkg to finish up because that takes forever)
Konqueror : 50 seconds (including default Conquer your desktop! page load)
Konqueror 2nd : 22 seconds (including default Conquer your desktop! page load)
Konsole : 10 seconds
Konqueror 3rd : 30 seconds (including default Conquer your desktop! page load)
I need to add some lib to get korganizer working and will up date this post with those times later tonight.
UPDATE:
Korganizer : 55 seconds
Abiword : 30 seconds
Kmail : 50 seconds
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=109647\")
Here are my results of some less casual timing.
Setup: ShiroiKuma's squashfs image + 64MB swap on SD
-- KDE desktop and Kwin:
1st run = a few minutes,
Afterwards = ~1 min 20 secs
Comment: Well, the xnest KDE on my ibook even takes longer to start!
-- Abiword: starts just as fast as in other wms
Normal run = 15secs!
Comment: Darn impressive. This can really be used to impress/scare people, even to other non-pdaX users
-- Konqueror:
1st run = a bit more than 1 minute
With preloading 1st time = ~20 secs
Restart after closing = ~30 secs.
Comment: Not bad, at least way better than Firefox.
-- Konsole:
Normal run = 18 secs
Comment: It's a 'big' deal! mrxvt loads in less the 2 secs only, and with multi-tabs!!
-- Kwrite:
Normal run = ~ 35 sec
Comment: No way for fast note-taking. Thoughts can easily slip away at any moment during this time lag. Leafpad would be a very good lightweight alternative. 3 secs. What else can you ask for?
-- KNote:
Normal run = ~ 25 secs
Comment: Use Xpad. It starts in less than 10 secs together with gcin/scim, and automatically docks as an applet just like Knotes.
-- KOrganizer:
1st run loads automatically with KOrganizer Reminder Client = 1 min 40 sec ..
Reopening with Reminder already on = ~ 1 min
Comment: Even heavier than Konqueror. What an amazing record. I'm using JPilot instead.
Nonetheless all the above KDE apps are running fine and fully usable once launched.
But come on check out this guy:
--Kontact:
1st run loads automatically with KOrganizer Reminder Client = 2 min 35 sec!
Subsequent startup with Reminder already on = 2 min 10 sec
Comment: A super app indeed, but this one may be an exception to Chero's method. It's linked to so many parts in the PIM system and as a result it does run extremely sluggish. Very basic actions in Kontact such as tapping the buttons in the left pane and exiting the app makes you wait for yet a few more ages, which is downright beyond any point of being usable.
BTW, shall we call for some informal benchmarking for this?
BTW : why so much fuss about load-time. I leave the apps I need open and just suspend.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109666\"][{POST_SNAPBACK}][/a][/div]
Yeah, that's what I do too. Basically, I have 6 desktops on KDE, divided thematically into what I use - language study, pim, konsole, etc. and it works fine while up and running. Starting KDE itself, or Firefox is a drag, but once up it works.
I use a 512 meg swap on a CF, with it it works fine.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109669\"][{POST_SNAPBACK}][/a][/div]
And for me the same .
(installed on hdd - 64Mb swap)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109666\"][{POST_SNAPBACK}][/a][/div]
So far 64MB seems to be already enough in my case, as I've never seen it filling up, if I'm not doing compiling in it. And there's a theory saying that using swap can actually slow things down as the system is busy with throwing stuff back and forth between ram and the card. Any convincing evidence for or against this?
The only problem I had was the time synchronization bug on suspend and resume, which I've taken care of as [a href=\"https://www.oesf.org/forums/index.php?showtopic=14655&hl=hwclock]described here[/url].
Zdevil, I think this might also be the case for your crashes on resume that you mention. I've never had such a crash with KDE, but have had the time-lag problem. Now it's gone.
Thanks for the pointer. However, my /usr/bin/apm looks very different from the script posted there, so I dare not try it out yet. Setting suspend times (both battery and AC) to 0 min resolves the problem, though. [Update: It turned out to be my illusion. Setting them to 0 doesn't help. Still need to wake it up from sleep 3 times religiously. ]
So, ShiroiKuma, got any plan for the next stage?
I was just wondering if the current image can be further stripped or separated in to a few images. I suppose not everyone is happy with the performance of the PIM apps and may choose not to use them at all (for example, KO/Pi definitely runs better than KOrganizer I bet). What do you think?
Oh yes, one very stupid off-topic question: I've installed some apps on my 256MB SD and use them with my C860, but now I am planning to move all the stuff to a 1GB card and use them with my C1000 (still running Sharp rom and is about to collect dust if I don't flash it to pdaX soon). Is there a way to restore/preserve the symlinks created for the apps?
-
Oh yes, one very stupid off-topic question: I've installed some apps on my 256MB SD and use them with my C860, but now I am planning to move all the stuff to a 1GB card and use them with my C1000 (still running Sharp rom and is about to collect dust if I don't flash it to pdaX soon). Is there a way to restore/preserve the symlinks created for the apps?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109685\"][{POST_SNAPBACK}][/a][/div]
# ipkg-link mount /mnt/card creates the links to the packages installed on SD.
Have fun,
Chero.
-
Thanks for the pointer. However, my /usr/bin/apm looks very different from the script posted there, so I dare not try it out yet. Setting suspend times (both battery and AC) to 0 min resolves the problem, though. [Update: It turned out to be my illusion. Setting them to 0 doesn't help. Still need to wake it up from sleep 3 times religiously. ]
So does mine, what I did is find the line $APM --suspendand just before it add the two lines/usr/bin/sethwclock
/sbin/sltime -setSo, ShiroiKuma, got any plan for the next stage?
I was just wondering if the current image can be further stripped or separated in to a few images. I suppose not everyone is happy with the performance of the PIM apps and may choose not to use them at all (for example, KO/Pi definitely runs better than KOrganizer I bet). What do you think?
It can definitely be done, though it's not gonna make anything faster, but it'll leave more space on the internal flash.
Anyhow, I have decided to go and ditch KDE since it is way too slow. When in XFCE4 everything is snappy, so I don't plan to be modifying anything... But you can do it, it's pretty easy, just time consuming, took a couple of hours, to cut everything out, symlink, pack it...
-
Ok, let me try and see if I can come up with something this weekend, and see how long KDE can keep my interest or how long I will keep it.
ShiroiKuma, many many thanks for your great work!
-
Hello,
This is exciting!
Does anyone else run out of installable memory on a C1000 to the point where they can't install anything after they've copied the squashfs file?
Knowing me, I'm doing something simple, wrong.Â
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109357\"][{POST_SNAPBACK}][/a][/div]
Yes, it's one of biggest moments ever in my pdaX experience.
I flashed 1.1.0 Beta, and then set up KDE3.5 immediately before installing any other apps. After this there remains about 12MB (forgot exactly how much) in the internal memory.
I'm sure we can have a lot more space if we can do without the PIM apps...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109474\"][{POST_SNAPBACK}][/a][/div]
Hiya,
How did you get it to work? On my C1000 I flashed the beta1. The copied the squashfs file to the right place and then tried to install the squashfs tools using the graphical installer within pdaXrom. But it kept saying there is insufficient memory.
The root was 0mb and the user was 12mb and everytime I tried to flip between the two and try and install it, nothing happened.
Any ideas what I'm doing wrong?
-
Was just wondering if, in the future, there would be a build of pdaXrom that comes prebuilt with a working KDE? Assuming enough people actually are keen to have KDE rather than the other desktop environments on their Z.
-
I did nothing special here. I tried it on my C860. Reflashed it to 1.1.0 beta and simply followed ShiroiKuma's how-to and it worked.
Upon flashing only 40+MB are used, and the squashfs image takes about 60MB, so there should be enough space.
For C1000, you have to use squashfs_2.2r2_armv5tel.ipk (https://www.oesf.org/forums/index.php?showtopic=16946) provided by pgas.
p.s. Forgot to mention that I flashed with 121MB root partition.
-
Did it!
A million thanks to ShioriKuma for his generous tips and his extremely useful symlink package, which turns building up the symlinks into a matter of a blink. You are such a great guy!
What I did is actually nothing new. I just squashed Laze's (kudos to you too! ) KDE packages, kdebase and kdelibs, unstripped. So no PIM and other extra stuff, but you can always install the other KDE packages in the feeds as usual afterwards.
It's now 42.8MB only! So upon a clean reflash with this image installed, there are still about 30MB left. Tested it a few times on my C860. Very smooth and no issues.
To distinguish this image from ShioriKuma's, it's called 'KDE Lite'. Maybe you can think of a nicer name. I'm just a sloppy guy.
Download link here: (Link removed. Please refer to Post #91 for new links and new symlinks package)
The zip file includes the squashfs image and a new symlinks package.
The download link will expire in 30 days if nobody is interested in it . If someone is interested to host it, please do.
Good news: Dunno why, this image runs even much faster than the stripped one, responsiveness close to other wms now. Also got more free RAM left when inside KDE. Previously there are very likely 1 or 2 MB remaining, now there are 6~7MB free.
Just follow ShioriKuma's how-to posted on the first page of this thread. Same method, except use the new image and symlinks package.
Remember -- For the very first time you load KDE3.5, you'll go through the Desktop Setting Wizard. (See my third screenshot FYI).
In the 3rd screen, which asks you how many eye candies you want to see there, choose wisely.
[Editied: well you can always go back to this wizard whenever for further fine-tuning ]
For instance, first I turned to the lowest rank from the left, and checked these options manually:
Desktop Wallpaper, Display Contents in Moving/Resizing Windows, File Manager Background Picture, File Manager, Icon Highlighting, Panel Background Pictures, Panel Icon Popups, Smoothed Fonts (Antialiasing), Window Moving/Resizing Effects.
I also have a feeling that this wizard setting is one of the keys to fine-tune and improve the overall performance.
Some initial test results:
First loading of KDE -- as slow as before, but
Subsequent loading -- 1 minute 10 seconds only.
Konqueror -- 35 seconds, no preloading.
Hope someone here will still be brave and interested enough to try out this.
Have a nice weekend with KDE3.5!
-
I installed kdelibs in flash memory and everything else on the harddrive and it works preety smooth (except kontact which takes forever to load even if i install kdepim in flash memory).
However I have a problem with kicker that is crashing or is dissapearing when I resume after a long suspend. Am I the only one who has this problem?
Did anybody compiled kdenetwork? I miss Kopete
PuthreGuy
-
Hi everybody, i have installed KDE from the feed of 1.1.0 beta 1 (http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/).
It is working but very slow on my SL3000 with RC12b1 (on hard drive of course, NAND is too small ). Slow mean a lack memory in my Zaurus. (i use a swap )
If i use ShiroiKuma stripped feed on my SL 3000, it could be more speed .? (more customize etc ..)
New pdaXrom version 1.1.0 beta 1 is require to be optimize with KDE ? (any improvement in kernel or something like this)
Thanks a lot
-
Hi everybody, i have installed KDE from the feed of 1.1.0 beta 1 (http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/).
It is working but very slow on my SL3000 with RC12b1 (on hard drive of course, NAND is too small ). Slow mean a lack memory in my Zaurus. (i use a swap )
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109825\"][{POST_SNAPBACK}][/a][/div]
You may want to have a go with the "Lite" version I squashed. Feels faster and uses less memory (storage and system).
-
Some more user experience for the non-nerds:
-- Disabling KTips on startup makes KDE load even faster, now 1 minute 5 seconds only!
-- You can do many things in the Control Center. But it is not necessary to launch the whole Control Center itself. Just open up K Menu (i.e. the desktop main launch menu), go to Settings > Control Center > and then blah blah blah, which will load pretty fast and get to exactly where you want to go.
-- To get your "Win" key (nothing to do with 'that' name actually), which I need so badly,
just go to Control Center (again, no need to start Control Center itself!), K Menu > Control Center > Regional & Accessibility > Keyboard Shortcuts,
then go to the first tab 'Shortcut Schemes',
then the first sub-tab 'Global Shortcuts',
under 'Action', scroll all the way down to Panel,
find 'Popup Launch Menu', tap on it,
below the 'Action' pane, choose 'Custom'
for instance, I map the Meun key on my C860 to this, which is XF86Start,
finally 'Apply' and 'OK', now you get the handy KDE Win key.
-- Another very useful shortcut is the 'Run Command', which brings you a lovely small popup dialog window for you to issue a command without calling up a terminal.
Follow the same track of fixing the KDE Win key as described above, and in the 'Action' pane go further down to 'Desktop', customize your favourite shortcut key there.
For me, I map the Mail key (XF86LaunchC) to mrxvt, and Shift-Mail to Run Command. Super useful and convenient.
-- Still have issues with apm. Doing three times of resuming religiously can bring it back, but sometimes it may fail with a blackout with only the cursor left. Adding the two lines as suggested by ShiroiKuma in /usr/bin/apm doesn't seem to help. Read that other users not using KDE also experience this. So perhaps this is an 1.1.0 beta issue?
So far I've found that a bit customizing in Desktop Setting Wizard and Control Center does help improve the overall performance.
A few questions:
-- I load the matchbox battery applet and it docks alongside the KDE clipboard. But it doesn't seem to show the battery level faithfully, as once (i did it once only) it didn't signal 'charging' even though it's already being fed by AC. Any hint?
-- Are there any cpu and ram monitor applets? I would be very interested to take a look at how grotty KDE is.
How about the other KDE users here? Any good tips for fine-tuning this amazing big boy on Z?
Will try to post some feedback here every now and then, if the experts don't mind this stupid dummy kind of actions.
-
does anyone have a link to zdevil's kde-lite?
I need to be able to wget a url -- the rapidshare javascript/ticket/hiding prevents
me from being able to grab the file directly.
Scott
-
-- Still have issues with apm. Doing three times of resuming religiously can bring it back, but sometimes it may fail with a blackout with only the cursor left. Adding the two lines as suggested by ShiroiKuma in /usr/bin/apm doesn't seem to help. Read that other users not using KDE also experience this. So perhaps this is an 1.1.0 beta issue?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109890\"][{POST_SNAPBACK}][/a][/div]
Update: No, it actually works in matchbox, as I see the clock resetting itself upon resume, but KDE seems to fail to do this. Any solution?
Update 2:: The context of the problem becomes more obvious to me now. Resume from time-out suspend is working. The real problem seems to be related to suspend by pressing the Off button and the device has to go through the triple resume ritual (and this may fail sometimes) The same seems to apply to ShioriKuma's image as well.
-
So far I've found that a bit customizing in Desktop Setting Wizard and Control Center does help improve the overall performance.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109890\"][{POST_SNAPBACK}][/a][/div]
Good news: Further playing with these options now reclaim more than 10MB free RAM free for the first time! My fear of this big boy gets smaller now.
-
So far I've found that a bit customizing in Desktop Setting Wizard and Control Center does help improve the overall performance.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109890\"][{POST_SNAPBACK}][/a][/div]
Good news: Further playing with these options now reclaim more than 10MB free RAM free for the first time! My fear of this big boy gets smaller now.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109924\"][{POST_SNAPBACK}][/a][/div]
Would you be so kind to reveal these settings?
-
I ran KDE 3.5 on a C860, full install on a 1Gb SD. It was impressive in that the Z could run KDE at all, however it was unusably slow as mentioned in several other posts. I have just taken delivery of a C3100 and flashed it with PdaX 1.1.0 beta 1. General impressions are its much 'snappier' than the C860, but before I get too far off topic - I am not sure if it is down to the PXA270 processor or the apps from the C1000/C3100 feed being built to take advantage of the processors features (or both). My point is, has anyone made a build of KDE 3.5 targeted specifically at the PXA270 processor - would the improvements be enough to make it realistically useable ?
-
I think you are crippling yourself by installing it on an SD card instead of internal flash - most of the time it's reading the card, which is very slow (the Z can't use the high speed capabilities of the SD, as I understand it). This is why it's been packaged as a compressed file system, so that it will fit in the internal flash.
-
So far I've found that a bit customizing in Desktop Setting Wizard and Control Center does help improve the overall performance. [div align=\"right\"][a href=\"index.php?act=findpost&pid=109890\"][{POST_SNAPBACK}][/a][/div]
Good news: Further playing with these options now reclaim more than 10MB free RAM free for the first time! My fear of this big boy gets smaller now.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109924\"][{POST_SNAPBACK}][/a][/div]
Would you be so kind to reveal these settings?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109934\"][{POST_SNAPBACK}][/a][/div]
It's no secret and no hacking at all. Just turn off as many eye-candies as you don't really need after having seen them.
And using the squashfs in the internal memory also feels snappier than installing the ipks on cards.
-
Some tests on apm today:
-- The KDE display power management is not working. It cannot turn off the screen or suspend the device.
[Partly solved -- Just set the time in Light & Power to 0. Then I enabled Standby, Suspend and Power Off in Display Power Management one at a time. All seem to work and the device can resume normally (from time-out suspend, not by pressing On/Off button). But I have yet to find out the difference among the three. Use On/Off key to suspend results in either the triple-resume phenomenon or the disappearance of the KDE panel/icons in K Menu/command paths (most command fail to execute except logout).]
-- Launch KDE inside an xterm under tvm. The weird thing is the tvm xterm frame appears both on top and at the bottom of the KDE screen. KDE panel is floating and movable. Suspend and resume fails in the same way as launching KDE directly.
-- Launch KDE under matchbox. KDE can start properly. Suspend and resums works, but at a cost: upon resume the matchbox panel will raise on top of the KDE one and replaces it. The KDE panel disappears and fails to come back in focus. Another anomaly is that the KDE clipboard applet shows up in the matchbox panel but it is not responsive at all. On some occasions the screen jumps back to the matchbox desktop while KDE is still running in the background and cannot be focused again...
So far I've seen the only possible way to run KDE with normal apm behaviour is to launch it inside a window manager such as matchbox. But this is simply not resource-friendly.
Laze and sashz, would there be any solution to this? Many thanks!
-
i am using the "lite" version on my C1000 and i don`t have any suspend problems and i don`t use Swap and still can open xmms,kate and konqueror all togther
-
i am using the "lite" version on my C1000 and i don`t have any suspend problems and i don`t use Swap and still can open xmms,kate and konqueror all togther
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110001\"][{POST_SNAPBACK}][/a][/div]
That's good news. Could you tell me if KDE can resume after a "Off button" suspend? Also what is your Light & Power setting? Thanks!
I've been testing without swap either.
-
I'm pretty sure that when I had KDE (not "lite") on my 860, the charge light never went off. Now I've re-flashed without KDE, it behaves properly again.
-
So far I've seen the only possible way to run KDE with normal apm behaviour is to launch it inside a window manager such as matchbox. But this is simply not resource-friendly.
Laze and sashz, would there be any solution to this? Many thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109997\"][{POST_SNAPBACK}][/a][/div]
The solution I found is: don't use KDE's apm.
Start KDE regularly, not from a WM or so.
Then in it run mb-applet-battery. When mb-applet-battery is running, pdaXrom's power settings and apm will work.
-
The solution I found is: don't use KDE's apm.
Start KDE regularly, not from a WM or so.
Then in it run mb-applet-battery. When mb-applet-battery is running, pdaXrom's power settings and apm will work.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110023\"][{POST_SNAPBACK}][/a][/div]
Thanks for the tip. But the situation remains the same.
I unmounted the image and losetup -d /dev/loop0, deleted the dir in ~/.kde, plus deleted the kde dirs in /tmp, so KDE really started anew. Then I tried this solution a few times, but got the same result even though the mb battery applet is loaded.
The symptoms:
1st resume: Screen goes off in about a second.
2nd resume: Screen turns on but with a blank desktop and panel, then goes off again in a second.
3rd resume: Screen may come back with everything intact. But it may also resume with some icons and command missing, or simply a dark screen only with the cursor left. Reboot is necessary.
So could anyone verify these? Or is it just a particular problem with my device or squashfs image? Thanks!
-
yep when i say suspend i mean from the oof/on button.
my light&power settings are the default ones but now i am working with no suspend(0 time) and one mintue for screen power off.
-
-- Still have issues with apm. Doing three times of resuming religiously can bring it back, but sometimes it may fail with a blackout with only the cursor left. Adding the two lines as suggested by ShiroiKuma in /usr/bin/apm doesn't seem to help. Read that other users not using KDE also experience this. So perhaps this is an 1.1.0 beta issue?
I'm running KDE using the packages in feed and have the same problem in resuming. I notice that when I resume (ie press the ON button) the Z is in fact powered up - I can see the display but the front/backlight isn't on. So I plugged it into the network and logged in to the Z via ssh. Running "ps ax" I find that these processes are still running:
29776 root 1112 S < /bin/sh /usr/bin/apm --suspend
29781 root 1088 S < /bin/bash /etc/apm/suspend.d/900cardctl suspend
29782 root 452 S < cardctl eject 0
Killing these processes results in the Z suspending itself again and on the next resume it resumes properly. Could it be that because cardctl eject 0 is somehow not exiting correctly (actually not exiting at all) it is causing the resume process to fail? Taking a stab in the dark I would point the finger at KDE's handling of removable media, maybe it's hanging onto the CF card causing cardctl eject 0 to fail? Any experts care to comment ?
-- cheers
-
need koffice and skim ( http://www.scim-im.org/downloads/skim_download (http://www.scim-im.org/downloads/skim_download) )!!
can someone have interest to compile them?
-
if some one can compile this:
kdenetwork(or kopete)
Koffice would be nice
kdegames
kdeutils-kcalc,ark very useful
thx
-
Yet another question:
How to map the applications keys? It seems running inputsetup.py in KDE does not take any effect. Thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109605\"][{POST_SNAPBACK}][/a][/div]
Sorry... this happens again! I forgot how many times I got a blink right after asking a stupid question.
Go to Control Center > Regional and Accessibility > Keyboard Shortcuts > Command Shortcuts (in the right pane), select the application you want to assign a key to, and then click the 'custom' bullet. When done, press 'Apply' to save your settings.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109606\"][{POST_SNAPBACK}][/a][/div]
Any idea how to map the silkscreen buttons? Do they even work at all? The hardware buttons work (ie are mappable). When I "click" on the silkscreen buttons all that happens is that the mouse pointer gets pushed all the way to the right of the screen. I've even tried manually editing the silkscreen buttons in the khotkeys config file, but still no joy.
-- cheers
-
how you maps other buttons to run programs?
-
ok found it
-
Any can post the actual .xinitrc file?
-
Any can post the actual .xinitrc file?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110253\"][{POST_SNAPBACK}][/a][/div]
Do you mean /usr/lib/kde/bin/startkde or /usr/bin/mbsession?
-
I'm running KDE using the packages in feed and have the same problem in resuming. I notice that when I resume (ie press the ON button) the Z is in fact powered up - I can see the display but the front/backlight isn't on. So I plugged it into the network and logged in to the Z via ssh. Running "ps ax" I find that these processes are still running:
29776 root    1112 S < /bin/sh /usr/bin/apm --suspend
29781 root    1088 S < /bin/bash /etc/apm/suspend.d/900cardctl suspend
29782 root     452 S < cardctl eject 0
Killing these processes results in the Z suspending itself again and on the next resume it resumes properly. Could it be that because cardctl eject 0 is somehow not exiting correctly (actually not exiting at all) it is causing the resume process to fail? Taking a stab in the dark I would point the finger at KDE's handling of removable media, maybe it's hanging onto the CF card causing cardctl eject 0 to fail? Any experts care to comment ?
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110085\"][{POST_SNAPBACK}][/a][/div]
Oh at last! We've got the culprit now. But the question is how to kill these guys? Is it possible to modify the original apm and then tell KDE to use the mod one instead of the original?
-
Any can post the actual .xinitrc file?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110253\"][{POST_SNAPBACK}][/a][/div]
Do you mean /usr/lib/kde/bin/startkde or /usr/bin/mbsession?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110300\"][{POST_SNAPBACK}][/a][/div]
I mean, the /usr/lib/kde/bin/startkde for use Fn keys... and mbsession for load applets....
-
just edit the original .xinitrc and remove all the stuff about matchbox and gconf and add startkde before the end of the file
-
Hello all,
I have a weird problem with xrandr on Kde3.5/ Pdaxrom 1.1.0 beta/ 3100.
If I rotate the screen with "xrandr -o 1" everything works well but when I want to switch back to normal ("xrandr -o 0") kde screen is indeed with the normal orientation but it acts like the screen resolution is 480x640 instead of 640x480. (It does not render the desktop in the right side of the screen and the taskbar is not visible because it tries to render it below the screen). I cannot revert the screen back without restarting the X server.
Also, even if I run xrandr with no parameters (in the moment when KDE is rendering fine) it displays:
#xrandr
SZ: Pixels Physical Refresh
*0 480 x 640 (163mm x 217 mm)
1 240 x 320 (163mm x 217 mm)
which I believe it's wrong (it should be 640 x 480).
I also changed the $defaultserverargs variable from the startx script "-screen 480x640@270" => "-screen 640x480@270" but it behaves the same.
Does anybody else have this problem.
Thanks,
PuthreGuy
-
To distinguish this image from ShioriKuma's, it's called 'KDE Lite'. Maybe you can think of a nicer name. I'm just a sloppy guy.
Download link here: http://rapidshare.de/files/10517484/KDE_Lite_3.5.0.zip.html (http://rapidshare.de/files/10517484/KDE_Lite_3.5.0.zip.html)
The zip file includes the squashfs image and a new symlinks package.
Hope someone here will still be brave and interested enough to try out this.
OK I was brave enough to try it Installed everything and followed instructions as per ShiroiKuma's post.
After I installed your updated symlinks package I examined what it had done and was surprised to see that all the symlinks were of the form: /usr/lib/kde/bin/appletproxy -> /mnt/card/kde/usr/lib/kde/bin/appletproxy
Predictably enough trying to start KDE brings up an error saying "Could not start kstartupconfig. Check your installation", and a whole bunch of "not found" errors after that.
I'm not sure but shouldn't the symlinks be something like: /usr/lib/kde/bin/appletproxy -> /usr/lib/kde/kde3.5/bin/appletproxy
If so is there a quick and easy way to convert those dodgy symlinks?
-- cheers
-
10. Edit the startkde file. If you don't know where it is, find it by which startkdeAt the beginning of the file, right after #!/bin/sh add the following line mount -t squashfs - o loop /usr/lib/kde/kde_3.5.0_stripped.squashfs /usr/lib/kde/kde3.5at the complete end of the file add the following line umount /usr/lib/kde/kde3.5[div align=\"right\"][a href=\"index.php?act=findpost&pid=109207\"][{POST_SNAPBACK}][/a][/div]
I suggest that the umount command be changed to:
umount -d /usr/lib/kde/kde3.5otherwise the loop device won't be freed and after you run KDE a couple of times the mount command will fail because there are no more loop devices.
-- cheers
-
Can anybody share kde-lite? I can't download from RapidShare...
-
Thanks desertrat for pointing this out. I'll look into the package I uploaded and corrected it this evening.
I'm also going to upload the kde-lite files to another place soon that is easier to download.
-
For all those, who like to enjoy all the nice kde programs, but feel kde desktop a little bit heavy on the Z, here are two screenshots of running kde applications on the wonderful fast ROX session environment with pinboard.
I did some tests with different kinds of kde installations and finally installed on the sdcard of my 860, because I need more internal flash left for additional programs than I can get with the compressed internal installation. I also use a 64 MB swapfile on sd.
I wrote some simple scripts to start ROX or KDE directly with the xserver, but for me personally the combination with ROX seems to be the fastest und best usable solution and I can use all he standard features of the pdaxrom.
With ROX I get approx. half the startup times for kde programs than with KDE desktop, f.i. 25 secs for konqueror against 50 secs in KDE. This is (nearly~~~) acceptable...
Lots of thanks and an extra donation for the pdaxrom team for this great edition! [ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
-
I'm not sure but shouldn't the symlinks be something like: /usr/lib/kde/bin/appletproxy -> /usr/lib/kde/kde3.5/bin/appletproxy
If so is there a quick and easy way to convert those dodgy symlinks?
After a marathon session with mc[1] I managed to redo all the symlinks and am happy to report that this KDE-Lite squashfs image works. Thanks ZDevil, ShiroiKuma and sashz
Speed wise, it seems about the same as when I had installed the official feed packages onto microdrive.
I've made a tarball of the corrected symlinks. It corrects an omission in the original, in that the original had a symlink kde3.5 pointing to a non-existent directory causing mount to complain.
To use:
cd /
tar zxf /path/to/kde_lite_symlinks_3.5.0-1.tgz
[1] Only joking, I hacked up a script to do the dirty work.
-- cheers
-
For all those, who like to enjoy all the nice kde programs, but feel kde desktop a little bit heavy on the Z, here are two screenshots of running kde applications on the wonderful fast ROX session environment with pinboard.
I did some tests with different kinds of kde installations and finally installed on the sdcard of my 860, because I need more internal flash left for additional programs than I can get with the compressed internal installation. I also use a 64 MB swapfile on sd.
I wrote some simple scripts to start ROX or KDE directly with the xserver, but for me personally the combination with ROX seems to be the fastest und best usable solution and I can use all he standard features of the pdaxrom.
With ROX I get approx. half the startup times for kde programs than with KDE desktop, f.i. 25 secs for konqueror against 50 secs in KDE. This is (nearly~~~) acceptable...
Lots of thanks and an extra donation for the pdaxrom team for this great edition!
Hello wowo123,
can you explain how you got rox and kde-apps working?
On my c 1000 all apps are crashing due start or short after coming up!
thanks, Denis
-
Sorry for the hassle! Here is the new KDE Lite symlinks package and a new KDE installation procedure that involves fewer steps.
What's new:
-- Checked the links and now they are all linked properly.
-- Added a separate startkde in /usr/lib/kde/kde3.5 which is not linked to /usr/lib/kde/kde3.5/startkde. This separate binary has the mounting and umounting script, plus the reference to xmodmap, so Fn key also works in KDE without manual tweaking. My reason of doing this is you can always remove this separate startkde and copy a new one from /usr/lib/kde/kde3.5 and tweak it to suit your need.
KDE lite 3.5.0 Installation procedure
#1 Install the symlinks package to the main memory
#2 Copy kde_lite_3.5.0.squashfs to /usr/lib/kde
#3 ln -s /usr/lib/kde/bin/startkde ~/.xinitrc (Use rm -f ~./xinitrc if necessary)
#4 startx
I have removed the older rapidshare download link to avoid confusion.
The KDE Lite squashfs together with the symlinks package will appear in http://mail.pdaxrom.org/contrib/ (http://mail.pdaxrom.org/contrib/) shortly (many thanks, pgas! )
-
New startup time records!
KDE: 1 minute 5 seconds
Konqueror (normal): 25 seconds
Konqueror (preloaded): 15 seconds only!
BTW, has anyone got any solution to the apm and suspend/resume problem?
-
One issue:
-- startkde cannot be run directly but has to be symlinked to ~/.xinitrc. But executing startx the image will be mounted twice to /usr/lib/kde/kde3.5 (i.e. two loop devices). A quick solution is (which I've been doing actually): edit /usr/lib/kde/bin/startkde, comment out the mount line. Then mount manually and run startx as usual.
-
Zdevil's stuff:
http://mail.pdaxrom.org/contrib/zdevil/kde..._3.5.0.squashfs (http://mail.pdaxrom.org/contrib/zdevil/kde_lite_3.5.0.squashfs)
http://mail.pdaxrom.org/contrib/zdevil/kde....0_armv5tel.ipk (http://mail.pdaxrom.org/contrib/zdevil/kde_lite_symlinks_3.5.0_armv5tel.ipk)
-
BTW, has anyone got any solution to the apm and suspend/resume problem?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110616\"][{POST_SNAPBACK}][/a][/div]
I revert to the Light & Power settings for suspend. For the time being I just let the device time-out suspends (say, 1 minute) without using the On/Off button. Works fine. Loading mb-applet-battery doesn't help anything in my case.
Thanks to pgas for putting up my stuff!
-
Hello wowo123,
can you explain how you got rox and kde-apps working?
On my c 1000 all apps are crashing due start or short after coming up!
thanks, Denis
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110598\"][{POST_SNAPBACK}][/a][/div]
Hi Denis,
I installed rox, rox-clib, rox-lib and rox-session from the actual feed. Then I changed the .xinitrc-File in /home/root into the one, which was published in this forum some time ago. After coming up with rox I installed all kde-packages from the feed on sd. They ran out of the box without kde desktop.
But I did it on a C860. I don't know anything about the different behaviour of C1000.
-
Okay, finally work out three simple workarounds to the annoying "suspend by On/Off button" issues.
General rule: Do not use the On/Off button for suspend (until someone finds out what actually is going on and how to fix it)
Solution 1: Use the original Light & Power settings for suspend.
Solution 2: Add the 'Suspend' application icon (the original one from matchbox, will first appear on the list of Lost & Found in K Menu) to the panel. Press it and the device will suspend as expected. Resume works fine. A little glitch is you'll see suspend still working for around 20 seconds upon resume. But it doesn't hurt and you can do other things without waiting for it to finish.
Solution 3: Map a shortcut key to 'Suspend'. For example, I use Ctrl-Alt-Escape (= the Cancel button) to suspend the device. Works exactly the same as 2 above.
Hope this helps!
Perhaps someone has come up with nicer and better ideas. Please do tell us!
-
One issue:
-- startkde cannot be run directly but has to be symlinked to ~/.xinitrc. But executing startx the image will be mounted twice to /usr/lib/kde/kde3.5 (i.e. two loop devices). A quick solution is (which I've been doing actually): edit /usr/lib/kde/bin/startkde, comment out the mount line. Then mount manually and run startx as usual.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110617\"][{POST_SNAPBACK}][/a][/div]
I don't see this happening and I followed your updated 'short' directions after a clean flash. FYI
-
Ok, my recent screenshot:
[ You are not allowed to view attachments ]
Still I have yet to figure out two things: improper portrait rotation and the way to map keys to turn up/down backlight.
The first issue doesn't concern me much as I'm using landscape almost all the time.
Then does anyone know what the command/keybinding for turning up/down backlight is? With this for me the basic KDE setup will be more or less complete. Thanks a lot!
-
commands for backlight:
setfl +
setfl -
-
commands for backlight:
setfl +
setfl -
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110769\"][{POST_SNAPBACK}][/a][/div]
Cool! Thanks, pgas! It's a lifesaver (to KDE)! So the next thing is to create icons/shortcut keys for them...
-
Any hope to see kde_lite working on SL-6000?
-
Here is my quick way of adding backlight adjustment to KDE (in Menu Editor). The pictures just speak for themselves:
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
Oops. A little glitch? But that doen't really hurt!
[ You are not allowed to view attachments ]
-
Any hope to see kde_lite working on SL-6000?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=110779\")
Probably there are at least two issues to resolve:
1. Capability to mount squashfs in 6000 (dunno if pgas' [a href=\"https://www.oesf.org/forums/index.php?showtopic=16946]Squashfs Modules And Utils For 1000/3100[/url] will do here)
2. Screen rotation problem: as Putherguy reports in #83, xrandr has strange output: 320 x 240 for orientation 1 (portrait). Have taken a briet look at xrandr, rotate and the related scripts but cannot figure out how to change that. Hope some experts here can enlighten us.
[Edited: In Screen Resize & Rotate (KRandRTray), there are also only options for 640 x 480 and 320 x 240. ]
-
Problem solved!
If you don't wanna see the busy sandglasses both in Suspend (Post #97) and Backlight Up/Down (Post #103), just uncheck the "Enable Launch Feedback" box on the right. Out of sight, out of mind.
-
Probably there are at least two issues to resolve:
1. Capability to mount squashfs in 6000 (dunno if pgas' Squashfs Modules And Utils For 1000/3100 (https://www.oesf.org/forums/index.php?showtopic=16946) will do here)
2. Screen rotation problem: as Putherguy reports in #83, xrandr has strange output: 320 x 240 for orientation 1 (portrait). Have taken a briet look at xrandr, rotate and the related scripts but cannot figure out how to change that. Hope some experts here can enlighten us.
[Edited: In Screen Resize & Rotate (KRandRTray), there are also only options for 640 x 480 and 320 x 240. ]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110782\"][{POST_SNAPBACK}][/a][/div]
uhm... and what about memory request? 6000's 64 MB flash memory???
-
uhm... and what about memory request? 6000's 64 MB flash memory???
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110788\"][{POST_SNAPBACK}][/a][/div]
Oh, I was just thinking 6000 has got 128MB flash. Then probably the only way to do this is to mount the squashfs on card and make symlinks to the paths there, or just use Laze's packages of kdebase and kdelibs. Not sure about the difference in performance between these two setups.
Also I don't know if 6000 runs a 2.4.18 or 2.4.20 kernel. If it's 2.4.18 then use the squashfs module mentioned by ShioriKuma on the first page of this post; if it's 2.4.20 then pgas' may do.
-
uhm... and what about memory request? 6000's 64 MB flash memory???
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110788\"][{POST_SNAPBACK}][/a][/div]
Oh, I was just thinking 6000 has got 128MB flash. Then probably the only way to do this is to mount the squashfs on card and make symlinks to the paths there, or just use Laze's packages of kdebase and kdelibs. Not sure about the difference in performance between these two setups.
Also I don't know if 6000 runs a 2.4.18 or 2.4.20 kernel. If it's 2.4.18 then use the squashfs module mentioned by ShioriKuma on the first page of this post; if it's 2.4.20 then pgas' may do.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110790\"][{POST_SNAPBACK}][/a][/div]
Here is what I did, which should work fine on a 6000 also asuming there is squashfs support.
KDE lite 3.5.0 Installation procedure for non-flash install
#1 Install the symlinks package to the main memory
#2 Copy kde_lite_3.5.0.squashfs to storage media (SD, CF, HDD)
#3 ln -s /mnt/card/kde_lite_3.5.0.squashfs /usr/lib/kde/ (asuming file on SD card)
#4 ln -s /usr/lib/kde/bin/startkde ~/.xinitrc (Use mv ~./.xinitrc ~./.xinitrc.old to restore matchbox if necessary)
#5 startx
Probably doesn't run as fast as from flash, but it works great and seems much faster then the standard IPK install. Now to start looking into getting a build of Koffice
-
Oops! Disabling the Introduction page in Konqueror (and start with no page loaded) and now get ...
Normal: 15 seconds!
Preloaded: 10 seconds!
Now I begin to get hooked on KDE 3.5 ...
-
Hi All
I think I'm doing something seriously wrong.
I'm copying the squashfs file to /usr/lib/kde but there doesn't seem to be enough room, it seems to copy about 9mb of it and then run out of space.
I've cleanly flashed my C1000 and I'm no linux whiz so I'm probably making a very basic mistake.
Any help would be gratefully received!
After a new flash this is what I get:
#df
filesystem       1k-blocks    Used  Available  Use%  Mounted on
/dev/root          59392   47712    11680   80%  /
none             11288      16    12272    0%  /dev
/dev/mtdblock3 Â Â Â Â Â 64512 Â Â Â 3852 Â Â Â 60660 Â Â Â 6% Â /home
/dev/mtdblock3 Â Â Â Â Â 64512 Â Â Â 3852 Â Â Â 60660 Â Â Â 6% Â /mnt/usr
-
Hi All
I think I'm doing something seriously wrong.
I'm copying the squashfs file to /usr/lib/kde but there doesn't seem to be enough room, it seems to copy about 9mb of it and then run out of space.
I've cleanly flashed my C1000 and I'm no linux whiz so I'm probably making a very basic mistake.
Any help would be gratefully received!
After a new flash this is what I get:
#df
filesystem       1k-blocks    Used  Available  Use%  Mounted on
/dev/root          59392   47712    11680   80%  /
none             11288      16    12272    0%  /dev
/dev/mtdblock3 Â Â Â Â Â Â Â Â 64512 Â Â Â 3852 Â Â Â 60660 Â Â Â 6% Â /home
/dev/mtdblock3 Â Â Â Â Â Â Â 64512 Â Â Â 3852 Â Â Â 60660 Â Â Â 6% Â /mnt/usr[div align=\"right\"][a href=\"index.php?act=findpost&pid=110835\"][{POST_SNAPBACK}][/a][/div]
The instructions asume you are copying the squashfs to root, which requires 43mb free... and you only have 11mb free.
You can either repartition the nand to a bigger root, or copy the squishfs file to /home and link it to /usr/lib/kde. In theory since they both reside in flash shouldn't effect speed at all.
-
Hi All
I think I'm doing something seriously wrong.
I'm copying the squashfs file to /usr/lib/kde but there doesn't seem to be enough room, it seems to copy about 9mb of it and then run out of space.
I've cleanly flashed my C1000 and I'm no linux whiz so I'm probably making a very basic mistake.
Any help would be gratefully received!
After a new flash this is what I get:
#df
filesystem       1k-blocks    Used  Available  Use%  Mounted on
/dev/root          59392   47712    11680   80%  /
none             11288      16    12272    0%  /dev
/dev/mtdblock3 Â Â Â Â Â Â Â Â 64512 Â Â Â 3852 Â Â Â 60660 Â Â Â 6% Â /home
/dev/mtdblock3 Â Â Â Â Â Â Â 64512 Â Â Â 3852 Â Â Â 60660 Â Â Â 6% Â /mnt/usr[div align=\"right\"][a href=\"index.php?act=findpost&pid=110835\"][{POST_SNAPBACK}][/a][/div]
The instructions asume you are copying the squashfs to root, which requires 43mb free... and you only have 11mb free.
You can either repartition the nand to a bigger root, or copy the squishfs file to /home and link it to /usr/lib/kde. In theory since they both reside in flash shouldn't effect speed at all.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110859\"][{POST_SNAPBACK}][/a][/div]
I'm afraid I've no idea how to accomplish either of those :-( Sorry
-
Or you may want to reflash pdaXrom with a bigger root partition. In the installation menu of pdaXrom, before flashing, you can go to the NAND Flash utils and then choose "Fix loader 64MB limit". After that you can set a large enough root partition (I always go for the max. 121MB). Then flash as usual.
-
Or you may want to reflash pdaXrom with a bigger root partition. In the installation menu of pdaXrom, before flashing, you can go to the NAND Flash utils and then choose "Fix loader 64MB limit". After that you can set a large enough root partition (I always go for the max. 121MB). Then flash as usual.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110868\"][{POST_SNAPBACK}][/a][/div]
Ok, I did the nand thing and then choce fix loader
Then it said it would need to reboot and then flash again
I rebooted and started the flash
should I not have said yes to "do you want to flash the user flash" or what ever that message is?
What step did I miss? cause it's still no different in layout. :-(
-
Ok, I did the nand thing and then choce fix loader
Then it said it would need to reboot and then flash again
I rebooted and started the flash
should I not have said yes to "do you want to flash the user flash" or what ever that message is?
What step did I miss? cause it's still no different in layout. :-(
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110873\"][{POST_SNAPBACK}][/a][/div]
After fix loader you need to go back to the Nand Flash Utils again.
This time you choose "Resize root partition".
Then you'll be prompted to fill in the size of the root partition.
Say you go for the max (121MB).
Then reboot again and enter the pdaXrom installation screen once again (the last time).
Finally you can go ahead with real flashing, choose "1 Install new ROM".
Hope this helps.
(Actually what I say all comes from pdaXrom's original documentation)
Good luck and hope things will go well.
-
Ok, I did the nand thing and then choce fix loader
Then it said it would need to reboot and then flash again
I rebooted and started the flash
should I not have said yes to "do you want to flash the user flash" or what ever that message is?
What step did I miss? cause it's still no different in layout. :-(
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110873\"][{POST_SNAPBACK}][/a][/div]
After fix loader you need to go back to the Nand Flash Utils again.
This time you choose "Resize root partition".
Then you'll be prompted to fill in the size of the root partition.
Say you go for the max (121MB).
Then reboot again and enter the pdaXrom installation screen once again (the last time).
Finally you can go ahead with real flashing, choose "1 Install new ROM".
Hope this helps.
(Actually what I say all comes from pdaXrom's original documentation)
Good luck and hope things will go well.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110875\"][{POST_SNAPBACK}][/a][/div]
I really don't remember this documentation, I guess it's somewhere exceedingly obvious, lol
-
ok, some progress
the xinitrc step took me in to a weird xscreen with odd windows open and nothing happened
running startkde direct gave me a lot of kpersonalizer: cannot connect to X server
-
ok, some progress
the xinitrc step took me in to a weird xscreen with odd windows open and nothing happened
running startkde direct gave me a lot of kpersonalizer: cannot connect to X server
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110883\"][{POST_SNAPBACK}][/a][/div]
Do you mean twm (the ancient window manager 'hidden' in pdaXrom)?
Don't use startkde directly. Instead try:
rm -f ~/.xinitrc
ln -s /usr/lib/kde/bin/startkde ~/.xinitrc
startxSee if this helps. Cheers.
-
Surprise again. Using a 64MB swap on SD, I'm very surprised to see about 20MB free RAM in KDE! Amazing ...
Would it be just an illusion??
-
Surprise again. Using a 64MB swap on SD, I'm very surprised to see about 20MB free RAM in KDE! Amazing ...
Would it be just an illusion??
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110897\"][{POST_SNAPBACK}][/a][/div]
Wow, thats a lot of free ram. At the most I have about 6mb and thats with a 128mb swap. Crazy... gonna spend some time this weekend tweaking though, will see what trouble I can get into.
-
using a no swap i got 6MB free but if you go to KinfoCenter you will see that 20MB are used for disk cache so in reality i have 26MB free even running kinfocenter!!!!(i will post here a screenshot)
-
Lol, so KDE 3.5 is definitely usable after all!
By the way, urielka, which KDE "flavor" are you trying?
-
the first "lite" version
it run a bit slow as i see it coz kicker is slow and kdesktop is kinda slow.
so the next target is making it more reponsive.
-
ok, some progress
the xinitrc step took me in to a weird xscreen with odd windows open and nothing happened
running startkde direct gave me a lot of kpersonalizer: cannot connect to X server
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110883\"][{POST_SNAPBACK}][/a][/div]
Do you mean twm (the ancient window manager 'hidden' in pdaXrom)?
Don't use startkde directly. Instead try:
rm -f ~/.xinitrc
ln -s /usr/lib/kde/bin/startkde ~/.xinitrc
startxSee if this helps. Cheers.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110888\"][{POST_SNAPBACK}][/a][/div]
OMG OMG OMG
wow
-
Here is what I did, which should work fine on a 6000 also asuming there is squashfs support.
KDE lite 3.5.0 Installation procedure for non-flash install
#1 Install the symlinks package to the main memory
#2 Copy kde_lite_3.5.0.squashfs to storage media (SD, CF, HDD)
#3 ln -s /mnt/card/kde_lite_3.5.0.squashfs /usr/lib/kde/ (asuming file on SD card)
#4 ln -s /usr/lib/kde/bin/startkde ~/.xinitrc (Use mv ~./.xinitrc ~./.xinitrc.old to restore matchbox if necessary)
#5 startx
Ok... It works and it is fast enough... starting konqueror require 15 sec with google set as homepage and usingo 32MB of SD swapfile.
Rotating doesn't work, Using the pdaxrom menu applet has no effect.
Running xrandr it says
#xrandr
SZ: Pixels Physical Refresh
*0 480 x 640 (163mm x 217 mm)
1 240 x 320 (163mm x 217 mm)
when xrandr -0 1 to landscape
the screen rotate but its width is 480 (as in portrait, it should be 640) and its length is more then 480 and the bottom of the screen is cut....
anyone has suggestions??
and what do u do for right clicking???
-
My friend told me that he got the On/Off button to suspend and resume properly on his C1000 (KDE Lite) without special tweaking. Is it also the case for the other C1000 users? If so then perhaps the On/Off button behaves somewhat differently between C860 and C1000 (kernel difference)?
Also would the pdaXrom dev team make the KDE headers and includes available so that we can start trying to compile some KDE apps ourselves? Thanks!
-
Also would the pdaXrom dev team make the KDE headers and includes available so that we can start trying to compile some KDE apps ourselves?
What are the killer KDE apps?
-
Now I'm thinking of Basket, KPilot and skim.
BTW, omro, can you get KDE to work now?
-
What are the killer KDE apps?
For me the whole thing is a killer app. Most of the KDE apps are nicely integrated and takes advantage of the KDE infrastructure. The powerful file dialog and kio-slaves are just two of the most useful features that all KDE apps can use. Sadly KMail is too large to use effectively on the Z.
-- cheers
-
Now I'm thinking of Basket, KPilot and skim.Â
BTW, omro, can you get KDE to work now?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111244\"][{POST_SNAPBACK}][/a][/div]
yes thank you so much, my "OMG OMG OMG wow" earlier was meant to convey that I'd got it working. I'm beyond happy. I just need to learn how to tweak and configure my Z properly now that my enthusiasm is renewed.
Unfortunately I come to this all from a Mac perspective. You plug it in, you turn it on and it works. Tweaking doesn't come naturally to me.
Is it my imagination, or does having a full scale window manager like KDE (rather than the mini one that came with pdaXrom) make the Z seem more like a mini laptop than an advanced PDA? I'm sure the window manager that comes with pdaXrom is pretty powerful, I just never spent enough time getting to grips with it, I'll be honest. Again that's my lack of natural tweaking inclinations.
-
I'm getting an error. It can't find kstartupconfig. I looked in the dir its supposed to be in but its not there.
Any ideas what I botched?
-
Can you see it in /usr/lib/kde/kde3.5/bin ?
-
Can you see it in /usr/lib/kde/kde3.5/bin ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111347\"][{POST_SNAPBACK}][/a][/div]
That directory is empty. Something obviously didn't take.
-
Can you see it in /usr/lib/kde/kde3.5/bin ?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=111347\")
That directory is empty. Something obviously didn't take.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111348\"][{POST_SNAPBACK}][/a][/div]
Which KDE packages are you using? If you're using the "Lite" squashfs version, make sure that you've installed the latest symlinks package from here: [a href=\"http://mail.pdaxrom.org/contrib/misc/]http://mail.pdaxrom.org/contrib/misc/[/url]
kstartupconfig should be right in /usr/lib/kde/de3.5/bin and symlinked to /usr/lib/kde/bin.
-
Can you see it in /usr/lib/kde/kde3.5/bin ?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=111347\")
That directory is empty. Something obviously didn't take.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111348\"][{POST_SNAPBACK}][/a][/div]
Which KDE packages are you using? If you're using the "Lite" squashfs version, make sure that you've installed the latest symlinks package from here: [a href=\"http://mail.pdaxrom.org/contrib/misc/]http://mail.pdaxrom.org/contrib/misc/[/url]
kstartupconfig should be right in /usr/lib/kde/de3.5/bin and symlinked to /usr/lib/kde/bin.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111362\"][{POST_SNAPBACK}][/a][/div]
i think the problem is that I don't have squashfs support installed, but when I try to install the ipk I get a bunch of errors.
-
There are two squashfs packages, one for 2.4.18 kernel (mainly Cxx0 and SL-xk)) from the regular feed and another one newly complied by pgas for 2.4.20 kernel (Cxk series) whiich can be found earlier in this thread and in the contrib feed. Dunno if this helps.
-
There are two squashfs packages, one for 2.4.18 kernel (mainly Cxx0 and SL-xk)) from the regular feed and another one newly complied by pgas for 2.4.20 kernel (Cxk series) whiich can be found earlier in this thread and in the contrib feed. Dunno if this helps.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111408\"][{POST_SNAPBACK}][/a][/div]
That indeed did the trick. I was trying to install the earlier version of it. Thanks... booting presently
-
That indeed did the trick. I was trying to install the earlier version of it. Thanks... booting presently biggrin.gif
Does this mean that the squashfs modules I compiled for 2.4.20 work?
-
Does this mean that the squashfs modules I compiled for 2.4.20 work?
Yes, it works for me on C3100. Thanks.
-- cheers
-
That indeed did the trick. I was trying to install the earlier version of it. Thanks... booting presently biggrin.gif
Does this mean that the squashfs modules I compiled for 2.4.20 work?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111417\"][{POST_SNAPBACK}][/a][/div]
I installed the "squashfs_2.2r2_armv5tel.ipk" package I found on the other thread. If that is the package you're refering to, then yes, it seems to work. To be honest it's all a bit beyond me so far... I'm just struggling to keep my head above water here.
-
Installed the "squashfs_2.2r2_armv5tel.ipk" package I found on the other thread. If that is the package you're refering to, then yes, it seems to work.
yes, it works for me on C3100. Thanks.
Yes that was what I was refering to, I don't have a machine to test these.
thanks for the feedback
-
Just downloaded and installed KDE 3.5. Works like a charm on my C3100 but I find it rather heavy.
All it needed was a new .xinitrc file with an added xmodmap line pointing to the correct character map (akita.xmodmap).
I'll have to ask this (too lazy to search) How do I run the initial configuration wizard again? I am specifically looking for the performance settings... Thanks
-
Just downloaded and installed KDE 3.5. Works like a charm on my C3100 but I find it rather heavy.
All it needed was a new .xinitrc file with an added xmodmap line pointing to the correct character map (akita.xmodmap).
I'll have to ask this (too lazy to search) How do I run the initial configuration wizard again? I am specifically looking for the performance settings... Thanks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112226\"][{POST_SNAPBACK}][/a][/div]
It seems my kde_lite_symlinks package already contains the lines pointing to the xmodmap. You can simply edit xmodmap or the userdefined to suit your need.
That initial configuration thingy is K-Menu > Settings > Desktop Settings Wizards.
Yes, indeed KDE is a desktop with great depth and the settings just look like a big maze.
-
Rotating doesn't work, Using the pdaxrom menu applet has no effect.
Running xrandr it says
#xrandr
SZ: Pixels Physical Refresh
*0 480 x 640 (163mm x 217 mm)
1 240 x 320 (163mm x 217 mm)
when xrandr -0 1 to landscape
the screen rotate but its width is 480 (as in portrait, it should be 640) and its length is more then 480 and the bottom of the screen is cut....
I have the same problem and I'm not sure if it is a KDE problem or a xrandr problem.
-
all:
kde 3.5 works very nicely, if a bit slowly, thanks to all the previous suggestions.
summarizing a bit for folks just starting out (with a 3100):
make sure that you allocate max memory to rom (128Mb).
[oops... correction, its 121...]
i've loaded kde (not the lite pkg) 2-different times, once in rom, once on the 3100 'hard drive'.
there was a negligible speed difference in loading. i'm probably going to revert to the 'hard drive' installation -- since kde stores a lot of info in the root directory; the extra space is nice.
speaking of which, does everyone run in 'root' mode?
good form is to also remember to rename your original .xinitrc to xinitrc.old (i use xinitrc.mbox), so i can easily revert to the matchbox gui. then symlink startkde to .xinitrc per earlier suggestions. startx makes it happen.
as i began to use it, i wonder if anyone has any further suggestions for including battery and/or memory monitors in the toolbar. also, is there a graphic pkg manager?
i'll be comparing some korganizer vs kopi over the next few days if anyone is interested.
korganizer would be nice, since i would like to access some calendars via internet (and, at last check, kopi did not support this option).
thanks again
-
I was just wondering if someone could tell the speed and performance of the KDE lite squashfs image + symlinks solution work for C3100 and C3000. In both my 860 and 1000, KDE 3.5 seems to run the fastest using this option.
BTW I'm using KDE 3.5 as my primary desktop and window manager, leaving matchbox for auxiliary use now.
-
Could someone please explain why its a good idea to allocate max memory to rom (121MB if I'm not mistaken...)?
From what I understand, the C3100 has 128 MB of memory. If my root partition is 58MB, then the rest is used for RAM? Right?
I'm running KDE from my hdd now and it is rather slow... But I would think that increasing the root partition in size would make things slower, right?
-
128MB is for ROM and also you got 64MB of ram
-
Then that means that increasing the root partition doesn't affect performance, right? Of course, having a bigger root partition would allow for more programs to be installed in main memory and thus run faster...
-
yes bigger root partition doesn`t speed up things.
but... if you install things on the flash it will run faster than installing on some cards
-
Hope someone can advise this pdaXrom noob....just installed pdaXrom on my 3100 yesterday and it works great. However, interested in trying out KDE but feel a bit confused after reading through this long thread a few times.
So would be great if someone could describe:
A) Best way to install KDE on a 3100 and
Where to get the files. Have checked the pdaXrom feeds, but don't see the files there....
Thanks for any and all help!!
-
IMHO there are 2 options... sashz compiled kde and announced it soemwhere around here.
This thread is about a kde 3.5 (same kde) squash image buildt from that.
I've tried sahz's version, and liked it...but I'm not real handy (read lazy and uninformed) with pdaxrom xinitrc config stuff and so have played with it less than it deserves.
the squashfs image sounds really cool.... but you have room to go either way easily on a 3100
-
Thanks for your help, adf!
So anyone else have any input/detail on installing KDE for 3100???
Thanks,
Mark
IMHO there are 2 options... sashz compiled kde and announced it soemwhere around here.
This thread is about a kde 3.5 (same kde) squash image buildt from that.
I've tried sahz's version, and liked it...but I'm not real handy (read lazy and uninformed) with pdaxrom xinitrc config stuff and so have played with it less than it deserves.
the squashfs image sounds really cool.... but you have room to go either way easily on a 3100
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113084\"][{POST_SNAPBACK}][/a][/div]
-
Thanks for your help, adf!
So anyone else have any input/detail on installing KDE for 3100???
Thanks,
Mark
IMHO there are 2 options... sashz compiled kde and announced it soemwhere around here.
This thread is about a kde 3.5 (same kde) squash image buildt from that.
I've tried sahz's version, and liked it...but I'm not real handy (read lazy and uninformed) with pdaxrom xinitrc config stuff and so have played with it less than it deserves.
the squashfs image sounds really cool.... but you have room to go either way easily on a 3100
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113084\"][{POST_SNAPBACK}][/a][/div]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113143\"][{POST_SNAPBACK}][/a][/div]
1. use the instructions in this thread
2. or add "c7x0-860" feed to your feeds (package manager) (http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/)
Then install at least "kdebase" and "kdelibs", make sure to install on Hd or card.
There is a command somewhere in the forum to link ".xinitrc" to "startkde",then you can just type "startx" and kde starts.
I didn't do this, instead I created a "xinitrc.kde" and a "startxkde", now I have a choice (startx=matchbox, startxkde=kde or startxfce4=xfce4).
I can post them tomorrow if you like, left my Z at work.
Chero.
-
PLease do post your xinits
my startx does ice.... (which is ok)
startxfce4 isn't needed, but the kde one would be handy
-
Thanks for your help, Chero!
Meanwhile searched through more posts on this in the pdaXrom section and found an interesting one for dual-booting pdaXrom with KDE and Qtopia on a C3000....
Instructions seemed be clear even to me, so in the process of giving it a shot..... sounded like a nice way to go if it works....
Mark
1. use the instructions in this thread
2. or add "c7x0-860" feed to your feeds (package manager) (http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/)
Then install at least "kdebase" and "kdelibs", make sure to install on Hd or card.
There is a command somewhere in the forum to link ".xinitrc" to "startkde",then you can just type "startx" and kde starts.
I didn't do this, instead I created a "xinitrc.kde" and a "startxkde", now I have a choice (startx=matchbox, startxkde=kde or startxfce4=xfce4).
I can post them tomorrow if you like, left my Z at work.
Chero.
Thanks for your help, adf!
So anyone else have any input/detail on installing KDE for 3100???
Thanks,
Mark
-
PLease do post your xinits
my startx does ice.... (which is ok)
startxfce4 isn't needed, but the kde one would be handy
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113149\"][{POST_SNAPBACK}][/a][/div]
when you extract this archive, you'll find a dir called "home", copy the file that's in it to your home-dir.
You'll also find a dir called "bin", copy the file that's in there to a bin dir (I prefer /usr/local/bin, but /usr/X11R6/bin would perhaps be more logical).
then "startx" will remain unchanged, "startxkde" will launch kde.
Please note, the files are not "polished", they just work.
Chero.
-
OK, got KDE working using someonehoi's post about dual-booting Sharp ROM and pdaXrom/KDE.
Works great except I have a couple questions please....
1) In KDE, how do I get connected to internet using my Ambicom WiFi card
I tried to open up kwifimanager to setup my WiFi card, but it's not installed yet...
2) In KDE, how do I get connected to internet using my Socket Ethernet card.
3) In Package Manager, what feed should I use to get KDE apps?
4) Can I only install KDE apps or ???
Thanks,
Mark
-
Bump.....
Mark
-
1) In KDE, how do I get connected to internet using my Ambicom WiFi card
I tried to open up kwifimanager to setup my WiFi card, but it's not installed yet...
Have you got wifi working at all? If it's not setup yet then use "Lan & Wifi", which is found under "System Tools" in matchbox. Once you've got it working then it'll just work, whether you're using KDE or whatever.
2) In KDE, how do I get connected to internet using my Socket Ethernet card.
Ditto
3) In Package Manager, what feed should I use to get KDE apps?
The "main" feed, ie the one for 7x0-860, ie in the case of 1.1.0beta1:
http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/ (http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/)
All the KDE apps that you can use are found in
kdebase
kdeedu
kdegraphics
kdelibs
kdepim
-- cheers
-
I'm using the squashfs image created by ShiroiKuma and refined by ZDevil. I've also installed kdegraphics from the main feed. Now the problem is that kde apps don't know how to handle jpegs, although pngs are fine. Any idea what I'm missing?
-- cheers
-
THANKS for taking the time to explain this, desertrat!!
Yes, I do have WiFi/Ethernet cards working now in matchbox....
Mark
1) In KDE, how do I get connected to internet using my Ambicom WiFi card
I tried to open up kwifimanager to setup my WiFi card, but it's not installed yet...
Have you got wifi working at all? If it's not setup yet then use "Lan & Wifi", which is found under "System Tools" in matchbox. Once you've got it working then it'll just work, whether you're using KDE or whatever.
2) In KDE, how do I get connected to internet using my Socket Ethernet card.
Ditto
3) In Package Manager, what feed should I use to get KDE apps?
The "main" feed, ie the one for 7x0-860, ie in the case of 1.1.0beta1:
http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/ (http://mail.pdaxrom.org/1.1.0beta1/Zaurus-7x0-860/feed/)
All the KDE apps that you can use are found in
kdebase
kdeedu
kdegraphics
kdelibs
kdepim
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=118692\"][{POST_SNAPBACK}][/a][/div]
-
Hi all.
Could someone post their original xinitrc file (which works with matchbox). I removed it to get kde running and now cant get back into matchbox. KDE looks great though!
Cheers guys
btw im running a C1000 with pdaxrom 1.1.0beta2
-
Wonderful!
But I haven't the desktop....why?
-
Sorry sorry!
At second boot I have now..
However compliments to zdevil and ShiroiKuma.
-
mmm..
I've tried to install:
kdebase
kdeedu
kdegraphics
kdelibs
kdepim
from beta4 feed, but don't work...
-
whow
i've just found this terrible thread!
is it still alive??? (i'm talking about KDE 3.5 on pdaxrom)
has someone tried with pdaxii13 ?
-
It worked with Beta 1, so it ought to work with pdaXii13.
-
whow
i've just found this terrible thread!
is it still alive??? (i'm talking about KDE 3.5 on pdaxrom)
has someone tried with pdaxii13 ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166674\"][{POST_SNAPBACK}][/a][/div]
I install from the kde ipks, rther thahn using the squashfs (I didn't have a copy of the squash til you revived this thread). Kde works great on pdaxii13. just kill whatever desktop you re using and do a startx -e startkde
-
whow
i've just found this terrible thread!
is it still alive??? (i'm talking about KDE 3.5 on pdaxrom)
has someone tried with pdaxii13 ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166674\"][{POST_SNAPBACK}][/a][/div]
I install from the kde ipks, rther thahn using the squashfs (I didn't have a copy of the squash til you revived this thread). Kde works great on pdaxii13. just kill whatever desktop you re using and do a startx -e startkde
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166685\"][{POST_SNAPBACK}][/a][/div]
whow! i've just tried and.... it works !!!
my Z continues to surprise me again and again !
i was afraid about suspend/resume process as some tells about it in this thread but it seems to work (via on/off switch) ! terrrrrrrible ! anyway i've to test some apps further
-
whow
i've just found this terrible thread!
is it still alive??? (i'm talking about KDE 3.5 on pdaxrom)
has someone tried with pdaxii13 ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166674\"][{POST_SNAPBACK}][/a][/div]
I install from the kde ipks, rther thahn using the squashfs (I didn't have a copy of the squash til you revived this thread). Kde works great on pdaxii13. just kill whatever desktop you re using and do a startx -e startkde
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166685\"][{POST_SNAPBACK}][/a][/div]
whow! i've just tried and.... it works !!!
my Z continues to surprise me again and again !
i was afraid about suspend/resume process as some tells about it in this thread but it seems to work (via on/off switch) ! terrrrrrrible ! anyway i've to test some apps further
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166690\"][{POST_SNAPBACK}][/a][/div]
well,
after testing, some apps doesn't want to start, for ex korganiser which want libqui.so.1 .......
moveover i cannot have the blue keys (* for ex !)
any help?
-
i also missed a battery monitor applet...
-
For the Fn keys you probably have to alter the xinitrc file used by KDE to load the appropriate keymap, as done for the Matchbox/Openbox window manager. You can basically steal a large portion of the .xinitrc for Matchbox and use it to replace the keymapping section of KDE's .xinitrc. Note that the xinitrc's are in some system directory and not in your home folder unless you specifically created one. Also, the above procedure only applies for the KDE ipks. I'm not sure how the squashfs is built -- you may be able to mount it, edit an xinitrc hidden somewhere and try starting KDE like that, but I'm not sure.
Also note that I haven't actually tried KDE on my Z for many months now because it is really too slow for everyday use and it didn't really add much to my desktop experience that I don't get from XFCE.
-
Haven't been able to download the squashfs files for KDE, are they still around? Nor have I found the individual kde ipk files. Would be interested in giving it a try. Thus far I have tried, matchbox, xfce, e17 and windowmaker. So far I like xfce.
Seems I found the idividual files, now to find the squashfs.
-
Haven't been able to download the squashfs files for KDE, are they still around? Nor have I found the individual kde ipk files. Would be interested in giving it a try. Thus far I have tried, matchbox, xfce, e17 and windowmaker. So far I like xfce.
Seems I found the idividual files, now to find the squashfs.
I have copies--if you don't find 'em drop a line
-
The ipks are here: http://distro.ibiblio.org/pub/linux/distri...s-7x0-860/feed/ (http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/download/1.1.0beta1/Zaurus-7x0-860/feed/) (You need a few of them -- kdebase, kdelibs, ... I'm not sure how many you need -- It's probably posted earlier in this thread).
All links to the squashfs seem to be broken, so if you want that (which it seems you do) you'll have to beg adf.
-
Got the individual files Got 3.5 running well at the moment, still looking for the squashfs for future cleaner work.
Thanks
-
It needs more memory to be usable. I would say, 128MB ram at least for kde + something else. Otherwise - SLOOOOW
-
It needs more memory to be usable. I would say, 128MB ram at least for kde + something else. Otherwise - SLOOOOW
Agreed, other wms are more responsive, but as i pointed out elsewhere it seems like seek times make a difference as well--it is certainly quicker run from my CF than it was from a microdrive. what I use it for is the ability to put a few kde apps on my desktop (rox) which can then be run (admittedly with long load times) at a click, and every once in a while fire up kde "just 'cause."