Daveleh Posted March 7, 2003 Report Share Posted March 7, 2003 Hi, I'm still trying to get my Smartmedia reader working in ML9.0 When I installed ML9 the reader was recognised and the following driver was loaded: disk/scsi|hardware_raid card usb-storage When I use the application USBVIEW I see the following: USB Storage Device Manufacturer: Serial Number: 0AEC501000001A002 Speed: 12Mb/s (full) USB Version: 1.10 Device Class: 00(>ifc ) Device Subclass: 00 Device Protocol: 00 Maximum Default Endpoint Size: 16 Number of Configurations: 1 Vendor Id: 0aec Product Id: 5010 Revision Number: 1.00 Config Number: 1 Number of Interfaces: 1 Attributes: 80 MaxPower Needed: 100mA Interface Number: 0 Name: usb-storage Alternate Number: 0 Class: 08(stor.) Sub Class: 06 Protocol: 50 Number of Endpoints: 2 Endpoint Address: 01 Direction: out Attribute: 2 Type: Bulk Max Packet Size: 64 Interval: 0ms Endpoint Address: 82 Direction: in Attribute: 2 Type: Bulk Max Packet Size: 64 Interval: 0ms When I enter less /proc/bus/usb/devices in a console I see the following: T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 93/900 us (10%), #Int= 1, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=d400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1 P: Vendor=0aec ProdID=5010 Rev= 1.00 S: Manufacturer= S: Product= USB Storage Device S: SerialNumber=0AEC501000001A002 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=05fe ProdID=0011 Rev= 0.00 S: Manufacturer=Cypress Sem. S: Product=PS2/USB Browser Combo Mouse C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usb_mouse E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms and when iI enter less /proc/modules in a console I get: msdos 5364 0 (autoclean) vfat 9588 0 (autoclean) fat 31864 0 (autoclean) [msdos vfat] isofs 25652 0 (autoclean) inflate_fs 17892 0 (autoclean) [isofs] nls_iso8859-15 3356 1 (autoclean) udf 85472 0 (autoclean) ide-floppy 13316 0 (autoclean) sd_mod 11788 0 (autoclean) (unused) lp 6720 0 (unused) parport_pc 21672 1 parport 23936 1 [lp parport_pc] i810 59396 19 agpgart 31840 7 (autoclean) sr_mod 15096 0 (autoclean) floppy 49340 0 (autoclean) i810_audio 21352 2 soundcore 3780 0 [i810_audio] ac97_codec 9928 0 [i810_audio] ppp_async 7456 0 (unused) ppp_generic 20064 0 [ppp_async] slhc 5072 0 [ppp_generic] af_packet 13000 0 (autoclean) keybdev 1920 0 (unused) mousedev 4116 1 hid 18340 0 (unused) usbmouse 2004 0 (unused) input 3456 0 [keybdev mousedev hid usbmouse] supermount 14340 3 (autoclean) ide-cd 28712 1 cdrom 26848 0 [sr_mod ide-cd] ide-scsi 8212 0 usb-storage 51952 0 scsi_mod 90372 4 [sd_mod sr_mod ide-scsi usb-storage] usb-uhci 21676 0 (unused) usbcore 58304 1 [hid usbmouse usb-storage usb-uhci] rtc 6560 0 (autoclean) ext3 74004 11 jbd 38452 11 [ext3] When I used my old camera in ML8.2 I was able to mount sda1 in order to view the contents of the card but in ML9 i get told that sda1 doesn't exist so I can't mount it. My question is, how can i tell what device to mount from the information given above, or is there more info that I need to obtain before I can decide that? Sorry for the long post but this is the only thing now that keeps Win98 installed. :( Thanks in advance Quote Link to comment Share on other sites More sharing options...
mtweidmann Posted March 8, 2003 Report Share Posted March 8, 2003 You need to know which entry in /dev represents your card reader. So boot up Linux, without the card reader attached. Then open up a terminal or Konqueror to /dev. At this point connect your card reader, wait a couple of seconds, then refresh /dev and look for new entries. Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted March 8, 2003 Report Share Posted March 8, 2003 Leave the reader plugged in and reboot. Immediately after run : $ dmesg You should be able to find the device listing in the print out. However, this is really driving me nuts. I know there is a utility which will give you this info when run. Quote Link to comment Share on other sites More sharing options...
Daveleh Posted March 11, 2003 Author Report Share Posted March 11, 2003 Hi pmpatrick Leave the reader plugged in and reboot. Immediately after run : $ dmesg You should be able to find the device listing in the print out. However, this is really driving me nuts. I know there is a utility which will give you this info when run. I think this is the section that is relevant: Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage scsi0 : SCSI emulation for USB Mass Storage devices WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 USB Mass Storage support registered. Do you know how to interpret it to find out the device? If so can you explain it please :) Quote Link to comment Share on other sites More sharing options...
Daveleh Posted March 11, 2003 Author Report Share Posted March 11, 2003 You need to know which entry in /dev represents your card reader. So boot up Linux, without the card reader attached. Then open up a terminal or Konqueror to /dev. At this point connect your card reader, wait a couple of seconds, then refresh /dev and look for new entries. Tried that. 685 items with the reader connected and disconnected :( Quote Link to comment Share on other sites More sharing options...
mtweidmann Posted March 11, 2003 Report Share Posted March 11, 2003 It would appear then that your system simply is picking up the device. Try running (if need be installing) USB view. Its a small app that show you every USB device connected on your machine. I'm pretty sure it comes with MDK 9.0 Quote Link to comment Share on other sites More sharing options...
hea Posted March 11, 2003 Report Share Posted March 11, 2003 If you havent allready,maybe you should take a look at www.linux-usb.org . A visit here solved my problem with digital camera connection! Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted March 11, 2003 Report Share Posted March 11, 2003 I thought it would be in dmesg output somewhere but I guess it's not. In my experience, mass storage devices on usb are designated /dev/sdax. Try mounting it like this: # mount -t vfat /dev/sda0 /mnt/<insert mount point> If that doesn't work, try /dev/sda4. That's what my usb zip drive is on and there is no sda0 thru 3. Go figure. Quote Link to comment Share on other sites More sharing options...
MottS Posted March 11, 2003 Report Share Posted March 11, 2003 USB mass storage devices are emulated as scsi hard drive for the linux kernel. This is why they are in /dev/sdaX. You should be able to mount the device with the pmpatrick command. Good luck MOttS Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted March 12, 2003 Report Share Posted March 12, 2003 Slight revision to my prior post. I'm not sure the first entry for sda is sda0; it might be sda1. You can try going through the number sequence for sdax from 0 to 4 till you find the right device file. My best guess is it will be either sda0 or sda1. Also checked my /dev both with and without my zip drive connected and indeed, /dev/sda4 and /dev/sda only appear after the zip drive is connected. Now that you know exactly where to look in /dev (i.e. for a /dev/sdax file) you may be able to track down your card reader device file directly by looking in /dev. Best of luck. Sorry for any confusion. Quote Link to comment Share on other sites More sharing options...
Daveleh Posted March 12, 2003 Author Report Share Posted March 12, 2003 Slight revision to my prior post. I'm not sure the first entry for sda is sda0; it might be sda1. You can try going through the number sequence for sdax from 0 to 4 till you find the right device file. My best guess is it will be either sda0 or sda1. Also checked my /dev both with and without my zip drive connected and indeed, /dev/sda4 and /dev/sda only appear after the zip drive is connected. Now that you know exactly where to look in /dev (i.e. for a /dev/sdax file) you may be able to track down your card reader device file directly by looking in /dev. Best of luck. Sorry for any confusion. Thanks to everyone for answering however as stated in the first message in this thread the card reader is recognised. I can see it listed in USBView, Harddrake (under unknown/other) and Kmenu/config/kde/info/usb devices (as Vendor: Neodio, Product ID: 0x5010 ND5010 card reader). The problem is that there are no sdxx devices listed in /dev. I have tried the commands mount /mnt/sdax and mount /mnt/sdbx (where x is from 0 - 9) only to be told that special device sdxx does not exist. :( Perhaps I should try another distro (debian for example) or wait for ML9.1 One thing I did notice was one time when I rebooted with the camera (not the reader) connected and turned on the boot sequence got as far as: Finding Module Dependencies (OK) and then the following appeared: Unable to handle kernel paging request at virtual address 01100112 *pde=00000000 Oops: 0000 CPU: 0 EIP: 0010:[<d8829001>] not tainted EFLAGS: 00010282 eax: 00000004 ebx: 01100112 ecx: 00000004 edx: 00000004 esi: c15edebc edi: 01100112 ebp: d71d5f64 esp: d71d5f50 ds: 0018 es: 0018 ss: 0018 Process scsi_eh_0 (pid:379 , stackpage=d71d5000 Stack: 00000000 01100112 d774ece0d74e4200 c15ede00 d71d5f84 d88d22c9 c15ede00 d74e42ac d74e4344 00000282 d74e4400 00000000 d71d5f98 d88bfab1 d74e4400 00000000 d74e4400 d71d5fc4 d88c047c d74e4400 c1452860 d71d5fd8 00000000 Call Trace: [<d88d22c9>] [<d88bfab1>] [<d88c047c>] [<d88c0956>] [<c0107526>] [<d88c0880>] Code: f3 ab 0f 84 cb 00 00 00 53 e8 d1 91 90 e7 8b 5d 08 53 e8 e8 <6>hub.c: USB new device connect on bus 1/1, assigned device number 4 (the italics are my own) Then everything stopped with the cursor flashing in the bottom left of the screen and the only thing I could do was to switch off, turn off the camera and reboot. As I said if only I can determine what to mount in order to access the reader I will be happy. Quote Link to comment Share on other sites More sharing options...
mtweidmann Posted March 12, 2003 Report Share Posted March 12, 2003 It might just have been a typ but the command you were using was wrong. You should be mounting /dev/sda* not /mnt/sda* This is all my system needed: An extra line in /etc/fstb line. /dev/sda1 /mnt/memory_card vfat noauto,umask=007,gid=500,codepage=850 0 0 Then as root: mount /dev/sda1 /mnt/memory_card (/mnt/memory_card has to already exsit) Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted March 13, 2003 Report Share Posted March 13, 2003 Check the syntax on your mount command per the above. However, if you have no sda* in /dev, trying to mount it is an exercise in futility IMHO. I'm beginning to wonder if you have your scsi modules loaded. Do you currently have anything currently running under scsi emulation(e.g. cdwriter)? If you don't have the scsi modules loaded, that would explain your problem since usb mass storage devices must run under scsi emulation. Open up a console and run the following as root: # lsmod The modules scsi_mod and ide-scsi are listed in mine. If they're not listed in your output run the following commands as root: # insmod scsi_mod # insmod ide-scsi After that, check /dev for an sda and sda*. If you find one or both of them there try to mount it per the above. Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted March 13, 2003 Report Share Posted March 13, 2003 Oop!! Just reread your initial post with cat /proc/modules and you do have the scsi modules loaded I'm pretty much stumped. A few things I can think of to try: 1. Try a different usb port. In particular, if you have it connected through a hub, try connecting directly to the port on the box. 2.Remove the scsi moudules with: # rmmod ide-scsi # rmmod scsi_mod and then reactivate with: # insmod scsi_mod # insmod ide-scsi See if you have an sda* in /dev and if so try mounting. 3. Wait for 9.1 to come out next week, download, install and hope it all goes away. Quote Link to comment Share on other sites More sharing options...
Daveleh Posted March 13, 2003 Author Report Share Posted March 13, 2003 Oop!! Just reread your initial post with cat /proc/modules and you do have the scsi modules loaded I'm pretty much stumped. A few things I can think of to try: 1. Try a different usb port. In particular, if you have it connected through a hub, try connecting directly to the port on the box. 2.Remove the scsi moudules with: # rmmod ide-scsi # rmmod scsi_mod and then reactivate with: # insmod scsi_mod # insmod ide-scsi See if you have an sda* in /dev and if so try mounting. 3. Wait for 9.1 to come out next week, download, install and hope it all goes away. Thanks again. I'll try the rmmod idea in the next few days. I'll let you know how I get on Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.