Author Topic: !!! READ THIS !!!! (Read 9510 times)

Laze · « **on:** January 22, 2006, 01:43:00 pm »

Hey everybody...

I (Laze) has finally managed to get a week holliday and I will spend it all on pdaXrom project - so together with Sash we hope to make great progress in this week.

First off I will be spending most of my time on the long overdue new website with better CMS system and developer sections with blogs and IPK upload and more.

But Sash will try and slowdown on new features and instead try to fix bugs :-) So this is where you come in - please take a look at the buglist on pdaXrom.org and tell us if you have any extra info/comments etc. to any of the bugs and post them.... BUT!!!!

We have decided that our current biggest problems is the suspend related problems so lets start out with them in this thread. So please post your Zaurus type, CF/SD card inserted, AC Adapter plugged in etc. and we will try and fix - please also use the IRC on freenode, #cacko (yes its cacko, we know its confusing).

So basically lets get the suspending problem out of the way and look at the next bug then (but if you know a bug is fixed or how to fix a bug on the buglist please post that too ;-)

stuffman · « **Reply #1 on:** January 23, 2006, 01:41:44 am »

I have a C860 that exhibits some weird behavior with my Seagate ST-1 5GB Microdrive (from a Rio Carbon). I use my Z a lot as an MP3 player, so xmms stays open a good deal of the time. Sometimes (I can't seem to pinpoint the conditions) I'll turn off the Z after I stop playback without closing xmms. Most of the time I'll have no problem turning it back on and playing music, but on occasion xmms will crash after powering on, and the microdrive will show up as not mounted, and will not remount through the mount toolbar thingy (BTW, I use xfce as my wm) though it will mount from the console. There were a few rare occasions where I've had to remove the drive entirely and re-insert it to get it to mount- the thing is I don't remember if this has happened yet with beta1 or was just in RC12... I just remember I had to do it a few times.

Sash and Laze, you guys are awesome and I wish there was more I can do to help. College is too expensive for me to donate at the moment, but if there's anything you can think of that I can do to help, let me know. pdaXrom has taken my Zaurus to places I have never imagined it'd go... and now that work is coming along well on the Playstation emulator, things keep getting better. I don't know of many other 2-and-a-half year old electronics device that actually gets more powerful with age. Thanks again!

clofland · « **Reply #2 on:** January 23, 2006, 02:41:23 pm »

Ok, on the bug list I posted this:
Submitted:   2005-10-13
Submitted by:   clofland
Type:   Bug
Category:   Matchbox related
ROM Version:   RC11
Priority:   3
Short description:   Using ntpdate to update time causes problems

For me the problem is fixed, and this is how:
1.
Always run sltime -set AND sethwclock after I set the time
2.
Add "sethwclock" just above "sltime -set" in the /etc/apm/scripts.d/sltime script

This seems to fix my time problems. Basically, the default ROM just uses the "sltime -set" command but adding the "sethwclock" in addition fixes suspend problems for me.

I don't know how to close bugs, but for me, that bug is fixed if the above changes are made.

stuffman · « **Reply #3 on:** January 24, 2006, 02:24:09 am »

Not really a bug or anything like that, it's just I'd like to see the power light working again. I have too often left my Zaurus on with the lid closed (I use it a lot as an mp3 player, so the lid is closed often) and ran the batteries down. Just a small thing, but it'd be nice to have.

gromituk · « **Reply #4 on:** January 24, 2006, 04:45:13 am »

Power light? Which Z do you have? There isn't one on the 860.

Laze · « **Reply #5 on:** January 24, 2006, 06:14:09 am »

Yes as i wrote in the first post - post all your details about your zaurus/cards etc.

stuffman · « **Reply #6 on:** January 25, 2006, 02:56:53 am »

My first post on this thread had all that info. I guess what I meant is the battery light (and there's the mail light). It usually lights up green when the power is on, and yellow when the battery is charging (unless I'm totally mistaken... it's been awhile since I used something other than pdaXrom). Right now, I only get the yellow charging light when the AC is plugged in.

gab74 · « **Reply #7 on:** January 26, 2006, 06:18:30 am »

On my C3100 i've tested RC12.... the big problem was the wrong clock time....

I try to follow some infos on the forum as using local file for time....
in this way all works well but if i suspend for a long time when i resume the graphics interface was always frozen....and the only way to reboot was put out the battery....

PdaXrom is a best rom, i hope this bug will be solved so i can flash again to it

Another little bug was PPP manager, when i set up a connection to my local ISP the log tells always an auth error....
I put my login and password in the peers files and so it work... I think this bug will be solved too....

maxg · « **Reply #8 on:** January 28, 2006, 02:41:38 pm »

I've got some more infos about bug #332. This bug deserves attention, since it results in important keys being unusable outside X.
I foud after a log of testing and reflashing, on two different devices, that the keys stop working after X has been killed with CTRL+ALT+BACKSPACE.
I did a lot of research and testing but I could not find a solution, not even a clue how this problem occurs.

I strongly advise that you avoid killing your poor X server too harshly, or you'll lose either the dot or period key, something you probably don't want.
If you have any idea of the origin of the bug, or if you think killing X is not the cause of the problem, please let me know.

Meanie · « **Reply #9 on:** January 28, 2006, 06:09:03 pm »

Quote

I've got some more infos about bug #332. This bug deserves attention, since it results in important keys being unusable outside X.
I foud after a log of testing and reflashing, on two different devices, that the keys stop working after X has been killed with CTRL+ALT+BACKSPACE.
I did a lot of research and testing but I could not find a solution, not even a clue how this problem occurs.

I strongly advise that you avoid killing your poor X server too harshly, or you'll lose either the dot or period key, something you probably don't want.
If you have any idea of the origin of the bug, or if you think killing X is not the cause of the problem, please let me know.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112772\"][{POST_SNAPBACK}][/a][/div]

Actually, I don't think it is an X related problem. If I bootup my C3K without going into X, my . key and a few others don't work. In fact, the keyboard seems like its mapped like a C7x0. When X starts xmodmap is called with a keyboard mapfile and the keys are correctly mapped once X is started. When you kill X, that mapping is lost, but if you gracefully exit X, it remains. In case you killed X, you can just run xmodmap and the appropriate keymap file to remap your keyboard. I wonder why the default keymap on the Cxx0 series models isn't their own native keymap.

Antikx · « **Reply #10 on:** January 29, 2006, 01:13:16 am »

Quote

Actually, I don't think it is an X related problem. If I bootup my C3K without going into X, my . key and a few others don't work. In fact, the keyboard seems like its mapped like a C7x0. When X starts xmodmap is called with a keyboard mapfile and the keys are correctly mapped once X is started. When you kill X, that mapping is lost, but if you gracefully exit X, it remains. In case you killed X, you can just run xmodmap and the appropriate keymap file to remap your keyboard. I wonder why the default keymap on the Cxx0 series models isn't their own native keymap.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

This Thread helped me get past the problem:
[a href=\"https://www.oesf.org/forums/index.php?showtopic=17050&hl=period]https://www.oesf.org/forums/index.php?showt...17050&hl=period[/url]

plcg · « **Reply #11 on:** January 29, 2006, 01:51:11 pm »

About suspend/resume issues :
- launch some stuff (aterm, package manager and xvkbd for example)
- suspend Z for more than 10 minutes
- On resume, nothing appears in "Active Tasks" => use ALT+TAB to make them reappear.
- On resume, impossible to switch to xvkbd => you must use a "kill -9" and then launch it again

Thanks
plcg

dtruchan · « **Reply #12 on:** January 29, 2006, 04:13:30 pm »

After booting the zaurus, besides scrolling being borked by the boot logo, suspend and resume work fast and flawless from the command line. If I launch X into matchbox, suspend and resume work flawlessly, but are slow. Then dropping to command line, suspend from button doesn't work anymore.

After booting if I launch X into Fvwm, or other window managers, suspend works fine and fast, but on resume the zaurus is unresponsive and suspends again. When I resume again, zaurus is again unresponsive and application text dissapears, then it suspends again. On the third resume, zaurus is OK.

This happens on RC11, RC12 and Beta1

chiark · « **Reply #13 on:** February 02, 2006, 01:15:45 pm »

Sorry if this is a known fault, but I can't find info about it:

Occasionally refuses to power on (resume) after a period of time despite the fact the battery is good. Screen flicks on showing proper contents and then disappears milliseconds later.

512MB Peak SD and 1GB CF card inserted, SL-C1000 running beta 1. Tried first without AC adaptor, then tried with AC adaptor.

stbrock · « **Reply #14 on:** February 02, 2006, 04:38:05 pm »

I've experienced the same thing and had the sense that the pushbutton switch was not exactly military spec and occasionally behaved erratically. But perhaps it is a softward issue as suggested above.

News:

Author Topic: !!! READ THIS !!!! (Read 9510 times)