Messages

1

General Discussion / Sl-c1000 Portability

« on: July 28, 2007, 11:50:22 pm »

Repeating an edit to my 12-2006 post here:  after several months of inexplicable lockups of my C1000, I have traced the source of the problem to...my beloved belt case! I now no longer use the D-Pods 40 case, which I believe was causing my lid to shift just enough to change the state of one or both of the lid switches while still on my belt. I haven't tracked down the exact mechanism--I've contented myself with the complete disappearance of the lockup problem when I leave my C1000 out of the case. The problem is no fault of LowePro, of course, since they don't sell this product as a PDA case. But a word to the wise: your case shouldn't cause or allow your screen/lid to move at all when your Zaurus is stored in it.

2

Zaurus - pdaXrom / Old Kopi Wakeup Pbm Back?

« on: April 03, 2007, 09:09:15 pm »

Well, it's been a wild ride since that last post.  What began as an apparent fix collapsed each time I tried the last thing to finish the fixes.  I used Meanie's very latest datentyme.py, applied the time fix routine at https://www.oesf.org/forums/index.php?showt...5618&hl=hwclock, including stopping and starting both atd and ntpd, ensured that apm was installed and running, checked for script functionality by logging to a file on resume and suspend, and did other things I've forgotten by now, but still found irregular execution of the scripts.d scripts, repeatedly incorrect time & date, system lockup after some suspends but not others, and still no Z wakeup by kopi.

Finally I have given up and reflashed to pdaXrom 1.1.0beta1 and applied the apmsleep fix, and everything is working just fine with kopi, kopi wakeup, clock and suspend again.  I've learned a few things in other areas that will enable me to live with beta1 for the moment.  Not a rant or a complaint about anybody's work--just a narrative.  Sometimes the excellent deeds others perform just aren't intended for you, eh?

CktRider

3

Zaurus - pdaXrom / Old Kopi Wakeup Pbm Back?

« on: March 29, 2007, 10:55:42 am »

Is the kopi-apm script linked into the resume.d directory? If so, it must be executed on resume...
Did you modify the kopi-apm script in any way, so that the resume portion of it may not be triggered on resume via the parameter $1?

daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157495\"][{POST_SNAPBACK}][/a][/div]

Yes to the first question, and no to the second.  The great news is, that I just had success.  My Z came out of suspend and rang the alarm.  I'll document things for future reference.

Daniel, thanks very much for the help.  I'm glad to understand more about the suspend and resume process, and I'm sure others are also.

Best regards,

CktRider

4

Zaurus - pdaXrom / Old Kopi Wakeup Pbm Back?

« on: March 28, 2007, 11:44:26 pm »

No, sorry to say, the name is only vaguely familiar.  Probably from when they used to page people over the building public address system about fifteen years ago or more.

I have tried writing log files on scripts' suspend and resume functions.  The files are written on suspend, but not a thing is written to the log files when I resume.  After a ton of frustration, I'm going to reflash.  I don't know how many times I can get away with that, but I'll give it one more go.  That way I can see what the state of the system is at the outset.

Thanks for the help, Daniel!

CR

5

Zaurus - pdaXrom / Old Kopi Wakeup Pbm Back?

« on: March 27, 2007, 09:04:45 pm »

please make sure that atd is running.

daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157275\"][{POST_SNAPBACK}][/a][/div]

Yes, atd has been running, per ps.  I restarted it and still have the problem.

I have a C1000 running the latest apm package, and I've eliminated the clock problems per other threads.  I'm using your controllable clock, Daniel--thank you for that good work, as well as all the work for many years among the HPLX community.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157290\"][{POST_SNAPBACK}][/a][/div]

so do I know you from the HPLX community?  

This forum is quite different, as here people don't usually post using their real names. That helped to make the HPLX mailing list such a familiar and cordial place, knowing some more about the people you talked to.

Well, if atd is running, you may follow the single steps of the kopi-apm init script and try to find out if one of the steps is broken...
THe script is in /etc/apm/scripts.d and must be linked into the suspend directory, so it is really executed on suspend. It does some calculations, using KO/PI's "next alarm" file and makes sure a resume is triggered shortly before the alarm comes up.
(I tell this all from memory, I don't have the exact script and file names handy now).

Somewhere in that chain may be an error.
Maybe only a missing link to the script?

daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157321\"][{POST_SNAPBACK}][/a][/div]

No, Daniel, I was a diehard 200LX owner, but pretty much just a lurker among the web community.  I'm a longtime HP Corvallis employee, but I was on the IC side, not the handheld side.  Like you, with the passing of the LX products I've moved to the best replacement.  I still type on my Z!  I'll send you an email at your hermocom address for an offline contact.

Lo and behold, kopi-apm wasn't installed.  I've installed it, restarted X, rebooted/restarted X, run ipkg-link, and no luck!  I'll start investigating the scripts per your suggestion.

Thanks,

CktRider

6

Zaurus - pdaXrom / Old Kopi Wakeup Pbm Back?

« on: March 27, 2007, 10:42:46 am »

please make sure that atd is running.

daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157275\"][{POST_SNAPBACK}][/a][/div]

Yes, atd has been running, per ps.  I restarted it and still have the problem.

I have a C1000 running the latest apm package, and I've eliminated the clock problems per other threads.  I'm using your controllable clock, Daniel--thank you for that good work, as well as all the work for many years among the HPLX community.

7

Zaurus - pdaXrom / Old Kopi Wakeup Pbm Back?

« on: March 27, 2007, 02:17:46 am »

Last time kopi failed to wake the Z before an alarm, the modified apmsleep binary fixed the problem.  I'm trying pdaxii13 now, and my Z again doesn't wake.  I put in the fixed apmsleep binary with no success.  I tried apmsleep from the command line, but I was informed summarily that my kernel doesn't support rtc and I need to recompile.  I hope that's not the case!  I've searched the threads, but don't find anything else past Jan '06.  Is there a pdaXii13-specific fix, or am I just missing something?  TIA.

8

Zaurus - pdaXrom / Pdaxii13 B5

« on: March 14, 2007, 11:30:24 pm »

This workaround has always gotten me past the suspend problem.  Perhaps it's posted elsewhere, but I haven't found it.  When the screen flashes I wait until the Z has timed out and powers off.  (Catch the reflection of the room light to determine when the LCD images disappear after the backlight goes off.)  I then simply hit the 'on' switch again.  If the screen flashes, I repeat the steps.  After two or at most three of these cycles the screen stays on.

9

Zaurus - pdaXrom / Disappearing Libraries Fix

« on: March 14, 2007, 01:56:01 am »

Just a note to make a common tip in this forum more accessible to a search.  I've fought a frequent problem of nonfunctional software due to disappearing libraries after a system crash or unexpected reboot--or sometimes, for no apparent reason at all.  The fix is simply ipkg-link mount /mnt/user or whatever your install mount point is.  Voila, links are restored to software installed at that point, libraries are suddenly found, and software functions again!

10

Security and Networking / Ambicom Wl54-cf

« on: January 09, 2007, 11:43:31 pm »

Well, Ambicom got back to me, with a doubtless business-wise but somewhat disappointing reply.  They indicate that the WL54-CF uses the Marvell 8385, and that's all they can provide in the way of help.

I've also searched the forum and googled quite a bit, without hitting on the 2.4 driver.

At this point, unless there's a path forward along the lines of a) finding the 2.4 driver,  locating help to create the driver, or c) potentially contactin Marvell for help, I'll need to return my card and look for another solution.

11

C1000/3x00 Hardware / A Few Doubts Wi-fi Cf

« on: January 05, 2007, 12:45:03 am »

I will try to port the driver over the weekend! The card would really rock! Worth the effort....

Edit: Could not make it this week, will try my best during the week...
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Globolus, there's renewed interest in the Ambicom WL54-CF.  Did you ever get a chance to work with the driver?

See [a href=\"https://www.oesf.org/forums/index.php?showtopic=15034&hl=wl54-cf]https://www.oesf.org/forums/index.php?showt...5034&hl=wl54-cf[/url]

12

Security and Networking / Ambicom Wl54-cf

« on: December 30, 2006, 06:22:30 pm »

This sounds hopeful.  I did get a reply from Ambicom, but only to say their engineers are on vacation and that they'll get back to me later.  I understand vendor support is a second-tier component, but perhaps they have some leads as well as support.

Sounds like a significant first objective is to find that 2.4 driver.

13

General Discussion / Sl-c1000 Portability

« on: December 29, 2006, 07:30:11 pm »

Evidently I'm the only one around who upholds the best of geek tradition and carries my Z on my belt.  It fits snugly in a low-profile and stretchable LowePro D-Pods 40 case, which also includes two pockets for my CF cards.  The flap is velcro, and is configured to latch even with my (still non-working) WiFi CF card in place.

http://www.lowepro.com/Products/Camera_Pou.../D-Pods_40.aspx

7-28-2007 After several months of inexplicable lockups of my C1000, I have traced the source of the problem to...my beloved belt case!  I now no longer use the D-Pods 40 case, which I believe was causing my lid to shift just enough to change the state of one or both of the lid switches while still on my belt.  I haven't tracked down the exact mechanism--I've contented myself with the complete disappearance of the lockup problem when I leave my C1000 out of the case.  The problem is no fault of LowePro, of course, since they don't sell this product as a PDA case.  But a word to the wise:  your case shouldn't cause or allow your screen/lid to move at all when your Zaurus is stored in it.

14

Security and Networking / Ambicom Wl54-cf

« on: December 29, 2006, 01:29:35 am »

Thanks for the good answers.  What do you think, Da_Blitz (and others)--can a newbie like me champion this task and help make it succeed?  If so, what's your advice on how to do so?

I appreciate the help.

15

Security and Networking / Ambicom Wl54-cf

« on: December 28, 2006, 04:38:00 pm »

Thanks, speculatrix.  Let's see how things unfold.  As a newbie, I don't know what I'm doing. It seems like the components of a solution, however, are a) vendor support, b) an understanding of any existing development work on this or related drivers, c) a hw/sw target (I'd personally need pdaXrom compatibility, if that level of software is even an issue), d) a developer or team to write the driver, and e) testing.  Have I missed anything, anyone?