Messages

1

Zaurus - pdaXrom / Time Sync Ntp And Rc12

« on: January 08, 2006, 02:30:02 pm »

I can confirm this. For the past couple of weeks I'd been wondering why my 750 kept its time less and less accurately. This weekend it dawned on me that there was a clear pattern: after each suspend it was 89--90 seconds late, regardless of how many suspends or how much time had passed since the last ntpd -q.

It turns out that the sethwclock / sltime -set in the suspend scripts wasn't enough; however, a sethwclock right after the ntpd -q did the trick.

2

Zaurus - pdaXrom / Apmsleep Freeze On Resume

« on: November 17, 2005, 08:24:16 am »

Does anyone else who uses the "wake up in X minutes" feature, like say, with kopi, have any trouble with the system freezing when you wake it up?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99139\"][{POST_SNAPBACK}][/a][/div]

Yes, this seems to have bitten me as well (although it was a bit difficult to debug, as there was another problem with a faulty battery that also resulted in my c750 hanging on resume every once in a while, with different symptoms).

It appears that when I resume the Zaurus immediately (say, less than half a minute or so) after suspending, apmsleep hangs, which results in X freezing as well. This happens with apmsleep but not regular apm(.x) -- that is, for instance with kopi alarm wakeups enabled. As a quick and dirty solution I patched /usr/bin/apm:

Code: [Select]

 if [ "$TIME_LOW" = "0" ];then
    $APM --suspend
  else
    $APMSLEEP +0:$TIME_LOW &
    sleep 2
    kill -HUP %1
  fi
That is, run apmsleep in background, wait for a couple of seconds (during which time the Z is supposed to be suspended) and then kill the hung apmsleep.

3

Zaurus - pdaXrom / Pdaxrom Rc12 For Sl-c7x0/7500/c860/c1000/c3100

« on: November 08, 2005, 09:03:44 am »

It should be in the FAQ really. Like previous post suggested, the hardware clock needs to be kept in UTC.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102580\"][{POST_SNAPBACK}][/a][/div]

Apparently so. However, the FAQ entry really should suggest some other method for doing this than hwclock --utc, now that there is no hwclock easily available. I don't remember exactly how it works, but it might be sufficient to write an /etc/adjtime that says, for example,

Code: [Select]

0.000000 1131415328 0.000000
0
UTC
If this is sufficient, wouldn't it be a good idea to put this in the root file system to start with? If not, wouldn't it be an equally good idea to include hwclock (and put the instructions somewhere)?

4

Zaurus - pdaXrom / Time Sync Ntp And Rc12

« on: November 08, 2005, 04:11:07 am »

I've been having similar problems with my newly-bought C750. Every once in a while, about once a day, it won't wake up: it has suspended apparently normally, but when I try to turn it on the screen stays black. Once I remove and reinsert the battery it reboots, but the time is reset to about the time when it was suspended.

Yesterday I grabbed hwclock from my old SL-5500 and changed the hardware clock to UTC. This seems to have fixed it to the extent that this particular problem hasn't appeared yet. On the other hand, when I changed sethwclock / sltime -set in the suspend scripts to hwclock --systohc the zaurus stopped suspending properly. A quick session with hwclock --debug showed that there seems to be some sort of problem with /dev/rtc.

More often than not, hwclock --debug says that it is "Waiting for clock tick..."; hwclock with other options just hangs. On the other hand, sethwclock and sltime appear to work, but sltime seems to set the clock back to the time of the last sltime -set. In other words, the clock behind /dev/rtc is not running, just like hwclock says.

Now the interesting question is whether this is a feature of this particular c750, all cXX0's, or pdaXrom on a cXX0.

5

General Discussion / Sony Ericcson K750i Usb

« on: October 20, 2005, 08:39:40 am »

I really don't know, but is the K750 seen as a USB Mass Storage Device by the host system?

My Linux laptop recognises a K750 as mass storage all right. Can't really say anything about how a Zaurus would behave, as I'm still trying to manage with a 5500.

However, it's worth noting that the K750's USB implementation has its problems. First of all, the phone won't see the memory card while connected to a computer. This is intentional (it was probably easier to design); after disconnecting the phone is supposed to refresh its view of the memory card. However, at least in some firmware versions this last part has some bugs in it, which can in some circumstances result in thrashed files. Separate card readers aren't that expensive..

6

Deals and Great Z Buys / Socket CF 802.11b WiFi for $49.98 on eBay

« on: September 16, 2004, 04:04:24 pm »

It's also worth noting that my Symbol card, supposedly identical to the Socket except for the stickers, has started having rather severe problems with certain new wlans. The current hypothesis, based on a quick comparison between the networks it works with and those it doesn't, is that the Linux driver doesn't like access points with 802.11g enabled.

7

Accessories / Symbol Spectrum 24 WiFi card problems.

« on: September 14, 2004, 10:26:13 am »

I'm not sure what make our APs are, I can see one from my window but can't read the label on the case, too far.

The antenna sticking down from the ceiling in my hallway says Lucent.

Anyway, reports on the Socket forum (eg. http://www.socketforum.com/topic.asp?TOPIC_ID=2146) support the hypothesis that this is some sort of driver problem.

8

6000 - Tosa / SL-6000 kernel source?

« on: April 21, 2004, 03:43:26 am »

Sharp appears to have released the source in Japan today. Of course, they only have the Japanese version at
http://developer.ezaurus.com/sl_j/source/source_dl.htm
but still this looks promising. Also, there is only one set of files for the SL-6000, instead of different source packages for the N, L and W.