LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   digital camera SD card pcmcia adaptor MDK 9.2 (https://www.linuxquestions.org/questions/linux-hardware-18/digital-camera-sd-card-pcmcia-adaptor-mdk-9-2-a-315435/)

dr_skids 04-20-2005 03:54 PM

digital camera SD card pcmcia adaptor MDK 9.2
 
Hello LQ HW Forum readers,
I am trying to use a pcmcia card to access Digital Camera images from
Secure Digital card.

The following is output from dmesg sfter inserting memcard reader
with SD card into pcmcia

cs: memory probe 0xa0000000-0xa0ffffff: clean.
hde: Memory Card Adapter, CFA DISK drive
ide2 at 0x100-0x107,0x10e on irq 3
hde: attached ide-disk driver.
hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hde: task_no_data_intr: error=0x04 { DriveStatusError }
hde: 499712 sectors (256 MB) w/1KiB Cache, CHS=976/16/32
/dev/ide/host2/bus0/target0/lun0: p1
devfs_do_symlink(disc0): could not append to parent, err: -17
ide_cs: hde: Vcc = 3.3, Vpp = 0.0
VFS: Disk change detected on device 21:00
/dev/ide/host2/bus0/target0/lun0: p1
devfs_do_symlink(disc0): could not append to parent, err: -17
VFS: Disk change detected on device 21:00
/dev/ide/host2/bus0/target0/lun0: p1
devfs_do_symlink(disc0): could not append to parent, err: -17

AND WHEN I list hde I get (after a long pause - my CPU is 233MHz 586mmx) flashing symlink
[root@cyclops log]# ls -l /dev/hde
lr-xr-xr-x 1 root root 32 Apr 17 10:09 /dev/hde -> ide/host2/bus0/target0/lun0/disc

WHEN I list /dev/hde without the card
root@cyclops log]# ls -l /dev/hde
brw-r--r-- 1 root root 33, 0 Apr 17 10:15 /dev/hde
[root@cyclops log]# file !$
file /dev/hde
/dev/hde: block special (33/0)


I found the following on the DEVFS home page:
"Strange kernel messages

You may see devfs-related messages in your kernel logs. Below are some messages and what they mean (and what you should do about them, if anything).
devfs_register(fred): could not append to parent, err: -17
You need to check what the error code means, but usually 17 means EEXIST. This means that a driver attempted to create an entry fred in a directory, but there already was an entry with that name. This is often caused by flawed boot scripts which untar a bunch of inodes into /dev, as a way to restore permissions. This message is harmless, as the device nodes will still provide access to the driver (unless you use the devfs=only boot option, which is only for dedicated souls:-). If you want to get rid of these annoying messages, upgrade to devfsd-v1.3.20 and use the recommended RESTORE directive to restore permissions. "

SHould I delte the /dev/hde entry and remove the section on mknod in the
/etc/pcmcia/ide.opts?????

Thanks for reading this far, can you help?

DR. Skids


All times are GMT -5. The time now is 10:24 AM.