Is hda3 normally a data partition? Have you tried checking dmesg for potential errors? Maybe
pccardctl eject 0;pccardctl insert 0
would help?
The plot thickens . . .pccardctl -v-bash: pccardctl: command not found
with cf card inserted
mount /dev/hda1 /mnt/cfmount: /dev/hda1 is not a valid block device
mount /dev/hdc1 /mnt/cfmount: /dev/hdc1 is not a valid block device
dmesgSTAT=-x2142
of pdxa_sd_wait_id_response: response time out (cmd=01 MMC_STAT=0x2142)
(above line repeated ~110 times)
SD Driver Initialized.
sharp_mmcsd 0.30 12 OCT 2004
pdxa_sd_wait_id_response: response time out (cmd=01 MMC_STAT=0x2142)
pdxa_sd_wait_id_response: response time out (cmd=01 MMC_STAT=0x2142)
[SD]-clustsize = 10000
Partition check:
mmcda: mmcda1
mmcda: mmcda1
mmcda: mmcda1
MSDOS FS: IO charset utf8
mmcda: mmcda1
EXT2-fs: unable to read superblock
mmcda: mmcda1
EXT2-fs: unable to read superblock
VFS: busy inodes on changed media
mmcda: mmcda1
mice: PS/2 mouse device common for all mice
start checkf battery !
pxa+mcmcia_init(0)
Yet I can boot from the cf card (power+OK), go into the flash utils and read the microdrive partitions.
Once booted from the nand, however, it dosen't recognize the microdrive or the cf card, but does see and mount the sd card just fine.