hello,

first to say that rc11 is awesome (special with xfce!) but anyway i had some troubles with my c3100.

1. battery doesnt last that long like it lasts on sharp rom (its much less). it is possible that it is because the next problem:

SOLVED: 2. i always have cpu load of 30 to 40% though the applications run smooth and fast. but as i said it is a bit annoying to have cpu load if nothing really happens.

3. the zaurus tries to mount hda1 (mostly after a suspend). on hda1 there are just files which are important for sharp rom like hda2. but this thing leads to the next problem:

4. if the hdd is mounted and the zaurus suspends it is nearly impossible to turn the zaurus on. if you click the "on/off" button the screen appears for a very short time and then gets black again (i think it gets again in suspend). then you can see the hdd-led blinking and hear some hdd-sounds but nothing happens. if you click again on the "on/off" button the same happens again. i managed 2 times to get the zaurus again out of the suspend (i think i clicked the adresses button and some more buttons... and then it started again). else i had to reboot the zaurus everytime. it is clear that this suspend-problem is because of the mounted hdd, so i have to unmount it every time i want to suspend... and as you can think this is not making one really happy.

5. i am not able to connect the zaurus via usb to my pc running windows xp. it appears as an drive but when i want to open it, it says that it is not formated and asks if i want to format the drive. but for example if i take the sd or cf card out of the zaurus and put it in my cardreader, windows xp has no problems to read the cards. everytime before connecting to the pc i used the usb application.
another thing is that there is no hdd in the usb utility... so it is also not possible to connect the zaurus internal hdd to my pc.

ok i think thats all until know (cant remember of anymore bugs... but if i do than i'll edit the thread). i will also add more if i can find anything and will also add them to the buglist. but i also wanted to know if someone has the same problems and if/ or how you could solve it.

run "top". what applications are using 30-40% of the cpu?

oh yeah... top it was. i just knew the ps command but this one doesnt show the cpu load.
it is kapm-idled which takes 30% and the rest is unimportant (1% X; 2% xfce).

thanks for answer... i'll google for kapm and look what it is.

EDIT: ok... it should'nt be a problem... its not really takin this 30% but idling the cpu to do nothing. so this is no problem anymore.

i am still trying to resolve the bugs ive found with my c3100 but nothing really worked.

you know the problem with the internal hdd: everytime after a suspend the zaurus mounts hda1 (first partition of the internal hdd). This would not be a problem... i would also like hda3 to auto mount (the large partition on the zaurus for Documents) BUT: if i forget to unmount the hdd before a suspend i have no chance getting out of suspend again. the screen appears for a very short time and gets dark again and the led of the hdd blinks a few times. nothing than a reboot helps here.

so i think that the problem with the suspend gets a bit deeper into the system and is nearly impossible for me to find the bug... but it would be a very nice if someone could tell me how to turn off this auto mount of hda1... so it doesnt mount everytime after a suspend and i dont have to unmount again everytime before a suspend. this would solve a big part of my problem.

Same problem... But not only reboot works... (but it is faster) - you can just try to press on/off key for a few times (usualy on ~10-th press it'll start normaly). But delay between you can press the key again is around 10 sec....

ok i think i managed to find some more about the error:

first i found the config file which automounts the internal hdd. take a look at /etc/pcmcia/ide.opts

in there you have to look for the devices which have the following mount points (here it is called MOUNTPT:
MOUNTPT="/mnt/ide"
MOUNTPT="/mnt/ide2"
MOUNTPT="/mnt/ide3"

for this devices change:
DO_MOUNT="y"
to
DO_MOUNT="n"

as i said before you should make this just for ide to ide3 else you also have to mount the cf card manually.

ok now... if you did turn of this DO_MOUNT than the hdd doesnt mount itself after a suspend. so if you turn on your device you can turn it off again without unmounting it again (else this damn bug appears).



what i also found out:

if you get into suspend the screen first gets black (nearly!) and after about 2 seconds it really turns off.
now how did i found this out: yesterday evening i wanted to load the battery again so i plugged in the connector. then i suspended and suddenly on one corner of the display i saw something which looked like the icon of aterm (but the screen was black and it looked like the picture of the screen burnt in the display... like it was on older monitors). you can see here a screenshot of my desktop.
Click to view attachment
i couldnt belive myself and thought that it might be a fingerprint of myself... so i cleaned the screen fast to see if it really was just a fingerprint... but it wasnt... it really looked like this aterm icon on my desktop. suddenly it disappeared and the orange led shortly interrupted the light... then i wasnt able to see the icon anymore. so i got out of suspend again and turned it off again... and again it was here. looking more concentrated on the screen i was able to see also the icons on the left and the panel... and again it dissapeared after a short time.

you can test it yourself. take a lamp and light on the screen (but dont take to strong light). then get into suspend and slightly twist the zaurus around (so that the light of the lamp doesnt dazzle you)... for some seconds you will be able to see icons of the screen etc (but it is very dark and hard to see... like if you make your console transparency very dark). suddenly everthing will dissappear.

now ive tested around and came to the following conclusion: if you get into suspend and right afterwards (1sec later) you turn the device on again you will have this bug again that the screen will appear just for a very short time and than dissappears again. i think this is because if you turn off the device (suspend) the screen darkens but the suspend happens just after some seconds... so you turn on the device which IS ALREADY/STILL TURNED ON but with darkened screen... and then this bug appears.
if you turn off your device and wait about 3 sec until you turn it on again you should have no problems again about the suspend (considering that you turned off this automount of the hdd before). you can try this also. turn the device off and after some seconds on again... try this as often you want... you will get no problems. and now try to turn off the device and shortly afterwards on again... and there it is again, this bug.

and as you said that after about 10 tries to turn on the device it should work again:
it sometimes worked on my device also... but not always. but the last to times i managed to turn on the device by clicking the "home" button... this worked for me better. but after turning off this automount and waiting some seconds after a suspend to turn it on i never had this problems again.

cool, btw what feeds do you update with? i did an update and crashed mine, gotta reflash and resetup my pdax/xfce install. Also how did you get kopi to work mine wont launch.

i would also like to know the feeds to update with. had a similar experience (reflash) on my SL6000L.

regarding kopi - have you tried using 2.2.3, it works well on SL6000L + rc11 + xfce. although compared to the shar rom version, kdepim is still very slow on pdaxrom and syncing takes a long long time (at least with kapi on my linux desktop)

/bazmi.