OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: scoutme on July 25, 2005, 05:44:50 am
-
Does anyone know how to obtain it?
-
One way is :
- compile the atd daemon from (http://handhelds.org/cgi-bin/cvsweb.cgi/apps/atd/)
- compile and find out how the qcop for X11/opie works (http://handhelds.org/cgi-bin/cvsweb.cgi/opie/x11/libqpe-x11/qt/)
- hack the qalarm daemon from qtopia so that it works with the above qcop
- rewrite the applet for matchbox and the above
- modify the ko/pi build for the desktop so that it uses the above
Another way would be to write an applet that uses the atd daemon directly, write some custom inter-process communication and modify ko/pi to use this....
And other things like this (like modify the atd daemon so that it communicates directly with kopi, write a custom daemon...)
in short it requires a bit of work.
(Please correct me if I am wrong and if there is a more simple way that I completely missed)
-
Hello,
I thought I read somewhere that kopi alarms now (version 2.x.x) work on linux desktop.
Does pdaX act as a linux desktop ? So maybe with the new version the alarms will work on pdaX.
Chero.
-
I think alarms work on the desktop version in that if you have kopi open it gives you an alert.
On qtopia, the alarm can wake up the Z and start ko/pi.
(maybe while setting up an alarm, it is possible to set an alarm with at to wake the Z up and start ko/pi)
Though I might be wrong
-
I wonder what would happen on the Z, if you have this version (> 2.1.0) of kopi running and the Z suspended.
Chero
-
gonna try if kopi can wake up the Z
I'll let you know
-
gonna try if kopi can wake up the Z
I'll let you know
[div align=\"right\"][a href=\"index.php?act=findpost&pid=89516\"][{POST_SNAPBACK}][/a][/div]
Doesn't work, at least for me.
If anyone knows how to 'wake' the Z then it shouldn't be too difficult to retrieve the next alarm from ko/pi, and I'll be happy to give it a go.
I suspect (though I may be wrong ;-) that under QT it does the following just before it suspends: -
- Check when the next alarm is? (1440 seconds away...)
- Tell apm to wake in 1440-10 seconds
- Tell apm to suspend
...
- apm wakes Z
- alarm applet gets triggered since its open
- Bundabrg
-
Ok, to 'wake' after a sleep you need to apmsleep command. I've seen another thread about this some day. I'm going to apt-get it in my debian chroot and play around.
- Bundabrg
gonna try if kopi can wake up the Z
I'll let you know
[div align=\"right\"][a href=\"index.php?act=findpost&pid=89516\"][{POST_SNAPBACK}][/a][/div]
Doesn't work, at least for me.
If anyone knows how to 'wake' the Z then it shouldn't be too difficult to retrieve the next alarm from ko/pi, and I'll be happy to give it a go.
I suspect (though I may be wrong ;-) that under QT it does the following just before it suspends: -
- Check when the next alarm is? (1440 seconds away...)
- Tell apm to wake in 1440-10 seconds
- Tell apm to suspend
...
- apm wakes Z
- alarm applet gets triggered since its open
- Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=89531\"][{POST_SNAPBACK}][/a][/div]
-
Any update on this? I really want my Z to have an wake-up/alarm function. This is one of the reasons my Z languishes unused for over long periods. I know people say that their Z is like a mini laptop... and it is fantastic, but I also want it to be pda too.
Oooh, dodgy ground here I think... but the alarm function is a big thing for me. If a crappy little £10 data bank can buzz me, why can't my Z?
Please tell me it can and that I am talking utter drivel.
J
-
apmsleep actually works ;-). As mentioned in the other thread, if you use apmsleep from a terminal window (or indeed, directly call 'apm --suspend'), when you resume the pda is very slow and unresponsive till you suspend and resume the normal way.
When you suspend using xset, ie by doing the following: -
xset dpms force off
Then it does something, and calls 'apm --suspend' as its last step. It seems to work fine.
I have already modified /usr/bin/apm to call run-parts on a directory of files when suspending. However if you edit /usr/bin/apm, and instead of getting it to call 'apm.x --suspend' to perform the suspend, you call 'apmsleep +00:01', it will go to sleep, wake up a minute later and it works fine.
SO... what needs to be done is as follows: -
1. Modify /usr/bin/apm to call something else to checks the calender (and perhaps a few other things) for the next event that occurs. Work out how many minutes/seconds away, or work out the absolute time.
2. If no event at all, then call 'apm.x --suspend'.
3. If there is an event, then call 'apmsleep +relative' or 'apmsleep absolute' in /usr/bin/apm
4. The pda will wake up at that time, and the event will trigger the alarm.
5. Probably be good to have some way of when being woken by event (rather than by user) it is re-suspended in a shorter time (say 30 seconds). Havn't worked out a good way of doing that yet since apm doesn't seem to be called on resume.
Anyway, mooch point for me for the moment since for some obscure reason KOPI doesn't actually play audibly any alarms on my C860. If I set the alarm as a procedure alarm that calls a script that calls 'play blah', it plays the sounds, but not otherwise.
- Bundabrg
Any update on this? I really want my Z to have an wake-up/alarm function. This is one of the reasons my Z languishes unused for over long periods. I know people say that their Z is like a mini laptop... and it is fantastic, but I also want it to be pda too.
Oooh, dodgy ground here I think... but the alarm function is a big thing for me. If a crappy little £10 data bank can buzz me, why can't my Z?
Please tell me it can and that I am talking utter drivel.
J
[div align=\"right\"][a href=\"index.php?act=findpost&pid=90437\"][{POST_SNAPBACK}][/a][/div]
-
A bit off-topic - where can I find kopi/kdepim >2.1.0 (precompiled) for pdax..?
leskimo
-
Hmm, I suppose I should attach apmsleep, since its not included in pdaXrom at the moment. I pulled this directly from my debian chroot, and it has no other dependencies that are unmet in a standard pdaXrom install.
Just ungzip it, and copy to /usr/bin.
- Bundabrg
-
Anyway, mooch point for me for the moment since for some obscure reason KOPI doesn't actually play audibly any alarms on my C860. If I set the alarm as a procedure alarm that calls a script that calls 'play blah', it plays the sounds, but not otherwise.
- Bundabrg
I think the bit that plays a wave file is in kalarmd/alarmdialog.cpp, and the command is
QString command = "playwave -r 22050 " + mFileName;
Recently I had a binary, 'play', which would play wav files (seems to have disappeared from my system now), so when I changed the line to call 'play', the alarm worked fine.
Dan
-
I think the bit that plays a wave file is in kalarmd/alarmdialog.cpp, and the command is
QString command = "playwave -r 22050 " + mFileName;[div align=\"right\"][a href=\"index.php?act=findpost&pid=90617\"][{POST_SNAPBACK}][/a][/div]
Ooh good tip. This, of course, means that you can create a file in /usr/local/bin called playwave, containing
play $3Make it executable, and it should allow alarms to play without recompiling ko/pi, should it not?
-
A bit off-topic - where can I find kopi/kdepim >2.1.0 (precompiled) for pdax..?
leskimo
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=90594\")
I have attached the latest version [a href=\"https://www.oesf.org/forums/index.php?showtopic=11164&st=15#]here.[/url]
Dan
-
THANKS danr!
I'll add your tip to my ipk of 'fixes' etc. See end.
I've also got a working (somewhat) of apmsleep with wakeup checking kopi. I can't take all the credit since Chistoph created a script that almost fulfilled my needs and I just modified it a bit. (See discussion at This Thread (https://www.oesf.org/forums/index.php?showtopic=14228)).
I've packaged everything in ipk's and put them on my server. To install, add the following as a feed: -
src updates http://www.worldguard.com.au/projects/zaur...urrent/cookpot/ (http://www.worldguard.com.au/projects/zaurus/pdaxrom/current/cookpot/)
The following ipks are there currently: -
- apmwrapper - More advanced apm script that wraps the real apm executable.
This is compatible with the pdaxrom apm wrapper and should work with
the original apm file as well. It creates /etc/apm/suspend.d and
/etc/apm/resume.d directories and will execute the scripts in there
on a suspend or resume.
Will also wake the device up on events.
- chkhinge-scripts - Enhances the clamshell scripts
Creates closed.d, landscape.d and portrait.d under /etc/sysconfig/clamshell.
Scripts in these dirs will be executed each time the device enters one
of these states.
- mplay - mplayer wrapper for Zaurus.
Will drop the resolution to 320x240 and execute mplayer with commandline
useful for playing video fullscreen.
- pdaxrom-patchlist - A list of fixes/hacks I find useful.
- Creates a cron.hourly job that sets the "hardware" clock to minimize timeloss on a crash
- Adds scripts to /etc/apm directories to unmount all smbfs mounts before a suspend and to set the "hardware" clock on both suspend and resume to minimize time loss on crash
- Wraps xrandr so that when full resolution is selected (IE: xrandr -s 0) and matchbox-panel is running, it will restart matchbox-panel. This restores the applets that were killed due to lack of screen space.
- Patches /etc/profile PS1 to display in colour
- Adds .Xdefaults to root as posted by jerrybme
- Modify esd.conf to terminate and wait longer to start (rgrep)
- Added /usr/bin/playwave. It calls play. Fixes kopi alarm issue (danr, gromituk)
- wakeup-kopi - Provides a wakeup event for kopi. The zaurus will wake up
in time to view the next alarm
To install the alarm wakup, install 'wakeup-kopi'. It will in turn install apmwrapper. Install the pdaxrom-patchlist to include the fix for playwave. The wakeup-kopi stuff is placed in /etc/apm/wakeup.d and /etc/apm/scripts.d
I must stress I've not had much chance to test out the wake-kopi stuff. It seems to work for me, but theres lots I've not tested. Recurring events definately do not yet work, and perhaps events on daylight saving days etc...
- Bundabrg
-
Installed the latest kdepim provided by danrs link above. Very nice.
It calls 'playwave', so it plays the alarm fine now. The older kdepim does NOT call playwave.
I set an event 1 hour from now, with a reminder at 57 minutes before. Hit the suspend button on my C860, stuck it in my belt and waited. 3 Minutes later, it woke up, and started beeping!
- Bundabrg
-
Fantastic work Bundabrg, I've been waiting for this sort of feature for a long time! I want to try it out for myself, but the only problem is a couple of the ipkg files on your web site are not found (apmwrapper_3.2.1_arm.ipk and hotfix-pdaxrom-rc8_1.0.5_arm.ipk). Perhaps there are permission problems on these two files?
Anyway, looking forward to giving it a go when I can.
Cheers,
Dan
-
Wierd. The packages file doesnt even reference them. I've uploaded newer versions.
I'll check that its not sending a cached copy.
[update]
I can definatley see the correct versions. It almost sounds like you are getting an older copy of the Packages file. If you get the file manually ( http://www.worldguard.com.au/projects/zaur...okpot/Packages) (http://www.worldguard.com.au/projects/zaurus/pdaxrom/current/cookpot/Packages)) , does it have a reference to apmwrapper 3.2.3?
I guess the other obvious is to check that you are not accessing my older rc9 and rc8 feeds before the current feed?
- Bundaberg
-
I must stress I've not had much chance to test out the wake-kopi stuff. It seems to work for me, but theres lots I've not tested. Recurring events definately do not yet work, and perhaps events on daylight saving days etc...
- Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91053\"][{POST_SNAPBACK}][/a][/div]
Hmm, it should be no problem to add a small feature to KO/Pi that KO/Pi writes the next alarm (in local time) to a file when it did compute the next alarm.
Then you won't miss any recurring alarm.
If you think that this is useful please let me know what filename / filepath do you need and what format the date/time values should have.
z.
-
Hmm, it should be no problem to add a small feature to KO/Pi that KO/Pi writes the next alarm (in local time) to a file when it did compute the next alarm.
Then you won't miss any recurring alarm.
If you think that this is useful please let me know what filename / filepath do you need and what format the date/time values should have.
z.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91078\"][{POST_SNAPBACK}][/a][/div]
Hi Zautrix,
I've been looking at this too. The way I see it either this or writing a custom AlarmServer is the way to go.
Obviously if you can add this in directly to kopi that would be the coolest option. If possible could you put a time_t value (from toTime_t) in the file? That would allow the logic for "how long to sleep" to be very easy to write.
File wise I'd prefer /home/$USER/.koalarm_next or something similar, as it wouldn't be a problem for non-root z's.
Once again, that would be excellent many thanks for the offer.
cheers,
Chris
PS For all others in the thread, do you know how long the apmsleep can sleep for? is it 99 hours or 24 hours etc? This would affect how often the Z would have to wake to check the time for an alarm when its over this maximum number.
-
No idea how long it can sleep. Still testing ;-). Worst case, it sleeps for the length of time, wakes up, then sleeps again.
Having the next alarm written to a file (or pipe) would be great. It gets around a lot of issues, especially the fact that kopi only saves every few minutes.
- Bundabrg
-
I must stress I've not had much chance to test out the wake-kopi stuff. It seems to work for me, but theres lots I've not tested. Recurring events definately do not yet work, and perhaps events on daylight saving days etc...
- Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91053\"][{POST_SNAPBACK}][/a][/div]
Hmm, it should be no problem to add a small feature to KO/Pi that KO/Pi writes the next alarm (in local time) to a file when it did compute the next alarm.
Then you won't miss any recurring alarm.
If you think that this is useful please let me know what filename / filepath do you need and what format the date/time values should have.
z.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91078\"][{POST_SNAPBACK}][/a][/div]
I think have it call an external file, if its there 'ala' playwave. IE, call '/usr/bin/setkopialarm next_alarm_in_epoch_time "next_alarm_summary"'
That way we can change how it works without a recompile or needing something to 'poll' the alarm file.
PS For all others in the thread, do you know how long the apmsleep can sleep for? is it 99 hours or 24 hours etc? This would affect how often the Z would have to wake to check the time for an alarm when its over this maximum number.
I don't use the hours field in my script, just the minutes field. IE, apmsleep +24:00 is equivalent to apmsleep +0:1440.
I'm thinking that since it supports that, then assuming the hardware supports it, it may be able to sleep up to int:int hours and minutes away (ie: 65535 hours and 65535 minutes?). I'm assuming (havn't looked at its code) that is just converts the time to seconds anyway.
- Bundabrg
-
Don't forget also to have it set the alarm or write to the external file when a uses suspends an alarm.
- Bundabrg
-
I've been struggling for ages to make this work, so today I did some serious debugging of the awk file. It turns out that I didn't have the TIMEZONES package installed, so all my times were out by 1 hour as kopi was taking timezone into account and the 'date' command wasn't.
Hope this helps someone.
Andrew
-
Ohhh nice catch. I'll update the ipk to require the timezones package.
- Bundabrg
-
THANKS danr!
I'll add your tip to my ipk of 'fixes' etc. See end.
I've also got a working (somewhat) of apmsleep with wakeup checking kopi. I can't take all the credit since Chistoph created a script that almost fulfilled my needs and I just modified it a bit. (See discussion at This Thread (https://www.oesf.org/forums/index.php?showtopic=14228)).
I've packaged everything in ipk's and put them on my server. To install, add the following as a feed: -
src updates http://www.worldguard.com.au/projects/zaur...urrent/cookpot/ (http://www.worldguard.com.au/projects/zaurus/pdaxrom/current/cookpot/)
The following ipks are there currently: -
- apmwrapper - More advanced apm script that wraps the real apm executable.
This is compatible with the pdaxrom apm wrapper and should work with
the original apm file as well. It creates /etc/apm/suspend.d and
/etc/apm/resume.d directories and will execute the scripts in there
on a suspend or resume.
Will also wake the device up on events.
- chkhinge-scripts - Enhances the clamshell scripts
Creates closed.d, landscape.d and portrait.d under /etc/sysconfig/clamshell.
Scripts in these dirs will be executed each time the device enters one
of these states.
- mplay - mplayer wrapper for Zaurus.
Will drop the resolution to 320x240 and execute mplayer with commandline
useful for playing video fullscreen.
- pdaxrom-patchlist - A list of fixes/hacks I find useful.
- Creates a cron.hourly job that sets the "hardware" clock to minimize timeloss on a crash
- Adds scripts to /etc/apm directories to unmount all smbfs mounts before a suspend and to set the "hardware" clock on both suspend and resume to minimize time loss on crash
- Wraps xrandr so that when full resolution is selected (IE: xrandr -s 0) and matchbox-panel is running, it will restart matchbox-panel. This restores the applets that were killed due to lack of screen space.
- Patches /etc/profile PS1 to display in colour
- Adds .Xdefaults to root as posted by jerrybme
- Modify esd.conf to terminate and wait longer to start (rgrep)
- Added /usr/bin/playwave. It calls play. Fixes kopi alarm issue (danr, gromituk)
- wakeup-kopi - Provides a wakeup event for kopi. The zaurus will wake up
in time to view the next alarm
To install the alarm wakup, install 'wakeup-kopi'. It will in turn install apmwrapper. Install the pdaxrom-patchlist to include the fix for playwave. The wakeup-kopi stuff is placed in /etc/apm/wakeup.d and /etc/apm/scripts.d
I must stress I've not had much chance to test out the wake-kopi stuff. It seems to work for me, but theres lots I've not tested. Recurring events definately do not yet work, and perhaps events on daylight saving days etc...
- Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91053\"][{POST_SNAPBACK}][/a][/div]
Hello Bundabrg
I was waiting for a long time for alarm waiking up my zaurus
I want to try that; but i can't download the following files from you server
-pdaxrom-patchlist
-wakeup-kopi
- apmwrapper
Please can you help ?
Thanks
Freebird
-
I have been attempting to setup the alarm system. Could someone be so kind as to point out some things to check and tests to run , that will help me see what parts of the alarm system are working and which are not.
I have a C680 running the latest build of pdaXrom.
Getting this to work would be a big step up for pdaXrom in my life.
Charles Puffer
-
Hello Bundabrg
I was waiting for a long time for alarm waiking up my zaurus
I want to try that; but i can't download the following files from you server
-pdaxrom-patchlist
-wakeup-kopi
- apmwrapper
Please can you help ?
Thanks
Freebird
Whoops, forgot about those who don't just do an ipkg update etc...
I've updated my index.php file to catalog the right directory now (was pointing at rc8) and it will show those files now.
I have been attempting to setup the alarm system. Could someone be so kind as to point out some things to check and tests to run , that will help me see what parts of the alarm system are working and which are not.
I have a C680 running the latest build of pdaXrom.
Getting this to work would be a big step up for pdaXrom in my life.
Charles Puffer
What have you done so far Charles? Have you installed the apps etc as per one of my previous posts (and installed timezones)?
Once that is done, you should be able to make an even for 5 minutes from now, with an alarm for 3 minutes before. Then SAVE in kopi, and suspend the Z. 2 minutes later it should come up.
Another test is to see how many minutes there are till the next alarm. SAVE in kope, and execute the following from the terminal
/etc/apm.d/wakeup.d/wakeup_kopi
It will return the number of minutes to sleep (mine returns 1384, so a little under 24 hours away is my next alarm)
It would be nice if someone could compile KOPI with those changes as discussed before (either writing next alarm to a file, or even better, executing an external script). Using a script like this has a few shortcomings, namely: -
- KOPI needs to have saved its data file
- Can't trigger on suspended alarms
- Doesn't yet trigger on recurring alarms (really complicated!)
- Bundabrg
-
Hello Bundabrg
I was waiting for a long time for alarm waiking up my zaurus
I want to try that; but i can't download the following files from you server
-pdaxrom-patchlist
-wakeup-kopi
- apmwrapper
Please can you help ?
Thanks
Freebird
Whoops, forgot about those who don't just do an ipkg update etc...
I've updated my index.php file to catalog the right directory now (was pointing at rc8) and it will show those files now.
I have been attempting to setup the alarm system. Could someone be so kind as to point out some things to check and tests to run , that will help me see what parts of the alarm system are working and which are not.
I have a C680 running the latest build of pdaXrom.
Getting this to work would be a big step up for pdaXrom in my life.
Charles Puffer
What have you done so far Charles? Have you installed the apps etc as per one of my previous posts (and installed timezones)?
Once that is done, you should be able to make an even for 5 minutes from now, with an alarm for 3 minutes before. Then SAVE in kopi, and suspend the Z. 2 minutes later it should come up.
Another test is to see how many minutes there are till the next alarm. SAVE in kope, and execute the following from the terminal
/etc/apm.d/wakeup.d/wakeup_kopi
It will return the number of minutes to sleep (mine returns 1384, so a little under 24 hours away is my next alarm)
It would be nice if someone could compile KOPI with those changes as discussed before (either writing next alarm to a file, or even better, executing an external script). Using a script like this has a few shortcomings, namely: -
- KOPI needs to have saved its data file
- Can't trigger on suspended alarms
- Doesn't yet trigger on recurring alarms (really complicated!)
- Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=93555\"][{POST_SNAPBACK}][/a][/div]
ampsleep works.
/etc/apm/wakeup.d/wakeup_kopi works (but it is apm not apm.d)
The wakup works (but becase of daylight saveings time the time that triggers the wakeup is an hour ahead of the displayed time and the KO/PI time.)
I am not getting any sound this may be do to a config problem or it may be do to the time/daylight saveings time problem noted above.
is there a good way to test the alarm part of the alarm?
$25 US to pdaXrom when I can simply install and use KO/PI and the alarms work (a second $25 for recurrring alarms) I know this is not a big prize, but I think some other users can pile on. Being clear this means a standard install and not haveing to do anything extra.
Charles Puffer
-
Yep its /etc/apm. (And I have my Z on me as well, so no excuse)
I've not tested any daylight savings yet. I'll test later when I get a chance.
To get KOPI to play alarms, you need to either create the playwave file as described earlier in this thread, or install 'pdaxrom-patchlist.ipk' from my feed. I deliberately did not make wakeup_kopi depend on my patchlist since some people may not like my fixes (its fully reversable if you don't like it and uninstall it).
- Bundabrg
-
Oh, and you have to install a later version of KOPI than is currently in the pdaXrom feeds (older version does not call an external script). There was another thread somewhere in this forum that had a link to a precompiled version.
New version of KOPI looks very nice.
- Bundabrg
-
Oh, and I had to change line 180 to date -u. Sorry forgot to add that to earlier post.
-
Ok I have read through this thread and I have followed the instructions and most everything seems to be working. The script to return minutes to the next alarm and the new apm work as expected. But apmsleep has an issue. When used with the new apm etc apmsleep will suspend my 6000 but it will not wake up. If i run it by hand (ampsleep +0:05) it will suspend and when i wake it up it will have an illegal instruction in the aterm window right after the apmsleep command.
Any suggestions?
Running a zaurus sl6000, kopi 2.17 on RC11 (ran through same tests with rc10)
Thanks
-
Ok I have read through this thread and I have followed the instructions and most everything seems to be working. The script to return minutes to the next alarm and the new apm work as expected. But apmsleep has an issue. When used with the new apm etc apmsleep will suspend my 6000 but it will not wake up. If i run it by hand (ampsleep +0:05) it will suspend and when i wake it up it will have an illegal instruction in the aterm window right after the apmsleep command.
Any suggestions?
Running a zaurus sl6000, kopi 2.17 on RC11 (ran through same tests with rc10)
Thanks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=97242\"][{POST_SNAPBACK}][/a][/div]
Yeah, not sure why the illegal instruction, but since it happens behind the scenes when called by dpms sleep I havn't worried about it
I havn't tested my scripts with RC11, so if you're running that there may be incompatibilities. It sounds like apmsleep is not being called when suspended.
- Bundabrg
-
Im fairly sure that apmsleep is being called, but it does not wake up the zaurus when its time. Even if i run apmsleep by hand. Im not sure where to even look for logs on why it might not be waking up. I flashed back to rc10 and I have the same issues. I was wondering if it might have something to do with the kernel?
Thanks
-
Anyone have any idea where to start with trouble shooting apmsleep problems?
Thanks
Todd
-
I can confirm that running apmsleep +0:05 by hand works on a C860 fine (well, it wakes up with pauses but thats 'normal' and fixed by getting dpms to call apm instead).
Anyone else with a sl6000 have positive results?
- Bundabrg
-
Hi
I have an SL6000L and I have the exact same problem on RC10 and RC11 - after a lot of googling this is the first time I have found anyone with the same issue!
The problem lies with the RTC wakeup somewhere - I have used apmsleep, and even written my own test programs using the SDK and info from the Linux kernel rtc documentation. It sets the alarm time correctly, and appears to turn the alarm interrupt on - I have never seen it confirmed via /proc/driver/rtc, but I can confirm that the interrupt fires (via the count in /proc/interrupts) unless the alarm is cancelled before the time arrives.
The Zaurus just never wakes up when the interrupt fires. If this were a PC, this would normally relate to a BIOS setting telling the machine to wake on this interrupt.
Aside from this issue, pdaXrom does absolutely everything I want and I am keen to get it fixed - any ideas that I can try out to get more info (or solve the problem!) would be greatly appreciated.
Regards
Karl
I can confirm that running apmsleep +0:05 by hand works on a C860 fine (well, it wakes up with pauses but thats 'normal' and fixed by getting dpms to call apm instead).
Anyone else with a sl6000 have positive results?
- Bundabrg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98055\"][{POST_SNAPBACK}][/a][/div]
-
Is there anything we can do to help find a fix for this? Testing, logs, etc? Im not much of a coder as of yet but Im willing to help in any way that I can.
Todd
-
I would be keen to help too - just not sure what to do next...
Does anyone know where any detailed specs are? What about source for the apm in the stock Zaurus kernel (which does wake up)?
-
I think I found the problem. Here's a quick and dirty fix that seems to work on my C1K:
http://www.iral.com/~albertr/linux/misc/pxa27x_power.diff (http://www.iral.com/~albertr/linux/misc/pxa27x_power.diff)
I think the right way to fix the problem is to mask the appropriate wakeup events, but that would require reading thru sharp's messy kernel code and understand all dependancies for possible events. I just don't have time for this right now, if anyone wants to give it a shot, please feel free to provide a better fix.
-albertr
-
I think I found the problem. Here's a quick and dirty fix that seems to work on my C1K:
http://www.iral.com/~albertr/linux/misc/pxa27x_power.diff (http://www.iral.com/~albertr/linux/misc/pxa27x_power.diff)
I think the right way to fix the problem is to mask the appropriate wakeup events, but that would require reading thru sharp's messy kernel code and understand all dependancies for possible events. I just don't have time for this right now, if anyone wants to give it a shot, please feel free to provide a better fix.
-albertr
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98485\"][{POST_SNAPBACK}][/a][/div]
Thanks albertr - that makes some sense. I was hunting around these registers yesterday looking for issues (before my head exploded between the processor docs and the Sharp kernel source...).
I was hoping not to have to recompile a kernel, but it looks inevitable. There is a lot of specific stuff for the tosa that seems to be in Sharp's source not referred to in the pdaxrom headers I have. When I get some spare time I will download the pdaxrom kernel source and give it a bash...
-
karlto if you do get around to building a kernel I would be happy to help you test it.
todd
-
Well im have been trying to rebuild the kernel for my 6000 to fix this issue but I think im missing something simple. Im trying to build the kernel just like i do on my normal box. Is there a doc someplace on how to build a kernel with the dev kit for pdaxrom?
Thanks
Todd