OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

Profile
Personal Photo
Options
Options
Personal Statement
wirawan0 doesn't have a personal statement currently.
Personal Info
wirawan0
Age Unknown
Gender Not Set
VA, USA
Birthday Unknown
Interests
Physics, scientific computing
Statistics
Joined: 8-March 04
Profile Views: 354*
Last Seen: 8th August 2009 - 11:41 AM
Local Time: Nov 22 2014, 08:59 PM
21 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
Contact Private
* Profile views updated each hour

wirawan0

Validating


Topics
Posts
Comments
Friends
My Content
27 Jul 2009
I have an old SL-5600 which has been functioning fine for years---one day it decided to not wake up from a sleep (suspend) state. Then I tried to remove the battery, do "Reset", put in the external power cord---nothing avails. I then tested the battery with a multimeter, and to my surprise the battery won't show nonzero voltage between any two contacts. Now I want to diagnose further:

* Will this PDA run on external power only? If somebody is kind enough, could you do this kind of experimentation: close all programs (to avoid losing data), then remove the battery. Close the cover without battery inside, then try running the PDA on external power only. Would it power up? If so, then my problem is not simply the battery.

* Does anyone have a method to fetch the data from the internal flash? I don't want to lose my address book, at least.

Wirawan
15 Jun 2004
Important corrections for the poll!!!

Sorry folks, I was wrong when writing in the poll question:

* ZUG polling allows each of us to vote only once. For your vote, give the answer for the card that you use the most often.

* The question should have read: [b]If you use SD card(s) with ext2 partition, have you ever encountered any problem (filesystem corruption, card damage, ...)? If there's an ZUG admin that could change the poll question, I'd appreciate it *very much*.

---- [ original message below ] -----

Hi,

I start this new thread for a single purpose: trying to centralize the experiences of Zaurus users who employ their SD cards with ext2 filesystem. Could you share your experiences, whether good or bad? This may help others too, to judge whether it is worth trying using SD + ext2.

My experience has been a bad one. (Only 1 experience, so it's unfair to conclude right away.) I used to own a Lexar SD 256MB 32x which I re-format to ext2 right after I received it. After 2 months it broke down, and reformatting it would result in a completely unusable card.

I have checked around and seems like people suggest to NOT mess up with filesystem on an SD card. See e.g.

http://docs.zaurus.com/index.php?id=managi...ing_sd_cf_howto

Now, MMC card seems to be okay to use for ext2. But MMC is slow, and NOT necessarily cheaper than SD anymore (note that, folks!).

So, please contribute your experience, and we'll see if this law applies:

SD + ext2 = corruption


Thanks,
Wirawan
8 Jun 2004
I was looking around if there's some discussion about the use of JFFS (JFFS2) on an external SD card. I couldn't find that easily (if I overlooked one, let me know).

But here's the question: with the stock Z system, I could only make 2 kinds of filesystems on my sd card: either VFAT or EXT2. The former is not desirable because of its many limitations (no links, no casesensitive filenames...). The latter was one that I used. But lately I ended up with a filesystem with quite a bit of errors. I wonder if anybody ever encountered errors with SD+EXT2 card. The error is like this:

[quote]
<snip>
sd flush : ERROR adr = 220856832 (0xd2a0200) , len = 15360 (0x3c00)
[SD]-R 0c00 0400 ERROR!
pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
sd_write_multiple(217741) : select error
sd flush : ERROR adr = 220856832 (0xd2a0200) , len = 15360 (0x3c00)
[SD]-R 0000 0400 ERROR!
pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
sd_write_multiple(217741) : select error
sd flush : ERROR adr = 220856832 (0xd2a0200) , len = 15360 (0x3c00)
[SD]-R 0400 0400 ERROR!
pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
sd_write_multiple(217741) : select error
sd flush : ERROR adr = 220856832 (0xd2a0200) , len = 15360 (0x3c00)
[SD]-R 0800 0400 ERROR!
pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
sd_write_multiple(217741) : select error
sd flush : ERROR adr = 220856832 (0xd2a0200) , len = 15360 (0x3c00)
[SD]-R 0c00 0400 ERROR!
unable to read partition table
pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
sd_write_multiple(217741) : select error
sd flush : ERROR adr = 220856832 (0xd2a0200) , len = 15360 (0x3c00)
VFS: Disk change detected on device mmcd(60,1)
mmcda:pxa_sd_wait_response: responce time out (cmd=07 MMC_STAT=0x2142)
sd_write_multiple(217741) : select error
sd flush : ERROR adr = 220856832 (0xd2a0200) , len = 15360 (0x3c00)
[SD]-R 0000 0400 ERROR!
<snip>
[/quote]

So depressing. I noticed this for the first time when I tried to untar an archive to this partition. Here's the typical e2fsck output:

[quote]
z:/home/zaurus # more fsck-1.txt
z:/home/zaurus # e2fsck /dev/mmcda1
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
/dev/mmcda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 40432, block 0, offset 0: directory corrupted
Salvage<y>? yes

Missing '.' in directory inode 40432.
Fix<y>? yes

Setting filetype for entry '.' in ??? (40432) to 2.
Missing '..' in directory inode 40432.
Fix<y>? yes

Setting filetype for entry '..' in ??? (40432) to 2.
Entry 'ComputeParams.cpp' in /???/??? (52523) has deleted/unused inode 52530. C
lear<y>? yes

Pass 3: Checking directory connectivity
'..' in /Documents/hack-k2-kinetic (40432) is <The NULL inode> (0), should be /D
ocuments (4033).
Fix<y>? yes

Unconnected directory inode 52522 (/Documents/hack-k2-kinetic/???)
Connect to /lost+found<y>? yes

Unconnected directory inode 52523 (/Documents/hack-k2-kinetic/???)
Connect to /lost+found<y>? yes

Pass 4: Checking reference counts
Inode 2 ref count is 10, should be 11. Fix<y>? yes

Inode 4033 ref count is 14, should be 13. Fix<y>? yes

Unattached zero-length inode 40433. Clear<y>? yes

Unattached zero-length inode 40434. Clear<y>? yes

Inode 52522 ref count is 3, should be 2. Fix<y>? yes

Inode 52523 ref count is 3, should be 2. Fix<y>? yes

Pass 5: Checking group summary information
Block bitmap differences: -215628 -215629 -215630 -215631 -215632 -215633 -215634 -215635 -215636 -215637 -215638 -2154Fix<y>? yes

Free blocks count wrong for group #26 (5462, counted=5559).
Fix<y>? yes

Free blocks count wrong (66848, counted=66945).
Fix<y>? yes

Inode bitmap differences: -52530
Fix<y>? yes

Free inodes count wrong for group #20 (1902, counted=1904).
Fix<y>? yes

Free inodes count wrong for group #26 (1902, counted=1903).
Fix<y>? yes

Free inodes count wrong (59063, counted=59066).
Fix<y>? yes


/dev/mmcda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mmcda1: 3430/62496 files (2.0% non-contiguous), 182860/249805 blocks
[/quote]

I wonder if it's merely software fault, that can be solved simply by reformatting, or if it's a hardware fault (i.e. bad sector).

Could anyone give some thought?

Also, this leads me to wonder if JFFS2 is actually better than EXT2 for use on a flash card. Its utilities (mkfs.jffs, etc.) don't come with the standard Z distro, unfortunately. :-(

Wirawan[/quote]
3 May 2004
My windows 2000 box got rebooted this weekend (maybe power failure), and now the NDIS driver wouldn't get loaded when I put my Zaurus (SL-5600) on the cradle. Why is this? I am really frustrated, since I can't get into it via SSH without NDIS 5 connection.

I tried many times to uninstall then re-install the driver, it wouldn't work. The NDIS driver would not be requested by Windows.
31 Mar 2004
Hi,

I have a z-5600 with pxa250 processor inside (uh...). The question is: has the cache problem been fixed (somehow) for a few later revisions of pxa250?

I've learned that pxa250 has a bug in regard to the cache writeback:

http://www.intel.com/design/pca/applicatio...dt/27853405.pdf

see issue # 100.

In the same paper, however, it is indicated that the problem has been solved. Does anybody know what this means? My understanding is that for SOME revisions of the pxa250 the problem has been fixed. Is this correct? And if it has been fixed, which was the first revision when the problem was fixed?

I have a great interest to using special kernel 1.3, but hesitate because the potency for cache problem is not clearly stated there (in the documentation).
Last Visitors
wirawan0 has no visitors to display.

Comments
Other users have left no comments for wirawan0.

Friends
There are no friends to display.
RSS Lo-Fi Version Time is now: 22nd November 2014 - 04:59 PM