OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => 5x00 Hardware => Topic started by: fido on April 14, 2004, 03:46:21 pm
-
hi all!
Today I purchased a 256MB Lexar SD card because I read that there are no problems with this card but apparently this is not the case
First I formatted the card with ext2. It lasted a long time but it looked ok. But when i tried to write a file on it (e.g. touch test) it needed a very very long time and there were errors in dmesg.
output with dmesg when inserting the card:
VFS: Disk change detected on device mmcd(60,1)
Partition check:
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
SD read error 00
SD read error : data block
invalidate: busy buffer
VFS: Disk change detected on device mmcd(60,1)
invalidate: busy buffer
VFS: busy inodes on changed media.
mmcda: mmcda1
invalidate: busy buffer
output with dmesg when writing file on card:
SD write error unknown status : 1f
[SD]-W 44400 0400 ERROR!
SD read error 00
SD read error : data block
SD write error unknown status : 1f
[SD]-W 44400 0400 ERROR!
I was able to partition and format the card with an external usb writer on my pc so I think the card is ok.
I have a Zaurus SL-5500 with OZ-3.3.6-pre1.
I hope someone can help me..
Cheers, Hermann
-
Try two things.
First, suspend your zaurus, then put the card in and unsuspend. I had problems with my 256meg lexar at first, and I think that card is a bit more sensitve to which pins hit first (the problem somewhat went away after I cleaned the card contacts with a rubber eraser).
Second, there is an alternate mmcsd driver in the downloads section on this board. See if you have better luck with that one.
--derek
-
thanks for your help but the alternate mmscd driver didn\'t help either.
strange things are going on: if i put the card in the running zaurus fdisk says that there isn\'t a partition table on the sd card.
but when i suspend the zaurus as you said with the card put in fdisk shows me a partition table but with a strange entry:
Disk /dev/mmcda: 255 MB, 255852544 bytes
16 heads, 32 sectors/track, 976 cylinders
Units = cylinders of 512 * 512 = 262144 bytes
Device Boot Start End Blocks Id System
/dev/mmcda1 1 976 249840 6 FAT16
/dev/mmcda2 1 1 0 0 Empty
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 0) logical=(0, 0, 1)
Partition 2 has different physical/logical endings:
phys=(0, 0, 0) logical=(8388607, 15, 32)
Partition 2 does not end on cylinder boundary.
/dev/mmcda2 shouldn\'t be there. i partitioned the card with an external card writer and there should be only mmcda1.
# touch test
touch: test: Input/output error
# dmesg
EXT2-fs error (device mmcd(60,1)): read_inode_bitmap: Cannot read inode bitmap - block_group = 0, inode_bitmap = 4
-
Hi Fido,
I had the same error with my lexar 256 super-duper-speed sd-card.
i wiped the mbr on that card totaly out and recreated the partition.
dd if=/dev/zero of=/dev/mmcda bs=512 count=1
fdisk /dev/mmcda
after fdisking a got again 2 partions, even if i created only one.
but anyway i was able to create the filesystem on the /dev/mmcda1 with mk2fs.
Since then it runs without any error.
Keep in mind to make regular backups of your card!
hope that helps a little bit.
SevenEleven