You are not logged in.
Pages: 1
Hi all.
I need a little help, I'm trying to mount a Memorystick.
lspci gives me:
06:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
dmesg gives me:
tifm_core: MemoryStick card detected in socket 0:2
lsmod | grep tifm gives me:
tifm_ms 4582 0
memstick 5108 2 mspro_block,tifm_ms
tifm_7xx1 3450 0
tifm_core 3600 2 tifm_ms,tifm_7xx1
I see no errors, yet it doesnt automount?
Offline
Post the following after you have the stick plugged in:
# fdisk -l
Does your stick show up as /dev/sdb1 (assuming you have a single HDD system)?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Yeah, I checked fdisk earlier to see if I could see what device it was under. But there is only my hd.
willie ~ > sudo fdisk -l
Disk /dev/sda: 40,0 GB, 40007761920 byte
255 huvuden, 63 sektorer/spår, 4864 cylindrar
Enheter = cylindrar av 16065 · 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 512 bytes
Diskidentifierare: 0x7a67b97d
Enhet Start Början Slut Block Id System
/dev/sda1 * 1 26 208844+ 83 Linux
/dev/sda2 27 59 265072+ 82 Linux växling / Solaris
/dev/sda3 60 1589 12289725 83 Linux
/dev/sda4 1590 4864 26306437+ 83 Linux
willie ~ > ls /dev/sd*
brw-rw---- 1 root disk 8, 0 30 jan 01.31 /dev/sda
brw-rw---- 1 root disk 8, 1 30 jan 01.31 /dev/sda1
brw-rw---- 1 root disk 8, 2 30 jan 01.31 /dev/sda2
brw-rw---- 1 root disk 8, 3 30 jan 01.31 /dev/sda3
brw-rw---- 1 root disk 8, 4 30 jan 01.31 /dev/sda4
Offline
Am I missing something? Do I need to do something to make it work?
Offline
What else does dmesg tell you about the device?
Also, check
% find /sys -name \*06:06.0\*
to see if something is created for the device under /sys
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
willie ~ > find /sys -name \*06:06.0\*
/sys/devices/pci0000:00/0000:00:1e.0/0000:06:06.0
/sys/bus/pci/devices/0000:06:06.0
/sys/bus/pci/drivers/yenta_cardbus/0000:06:06.0
Offline
So it seems its creating the devices, just not under /dev. Could it be a policy/rule issue?
Offline
Pages: 1