I've just bought a device to let me read MMC cards on my linux box. It seems to be recognised by the system, but I don't know how to mount it. Could anyone tell me how to do this? I've tried the obvious 'mount /dev/sda /home/john/MMC', together with '-t vfat' instead to no avail. The messages file shows the following details: Mar 19 11:21:54 linux kernel: hub.c: new USB device 00:07.2-1.4, assigned address 5 Mar 19 11:21:54 linux kernel: usb.c: USB device 5 (vend/prod 0x7c4/0xac01) is not claimed by any active driver. Mar 19 11:21:55 linux kernel: Initializing USB Mass Storage driver... Mar 19 11:21:55 linux kernel: usb.c: registered new driver usb-storage Mar 19 11:21:55 linux kernel: usb-uhci.c: interrupt, status 2, frame# 1113 Mar 19 11:21:56 linux kernel: usb_control/bulk_msg: timeout Mar 19 11:21:56 linux kernel: scsi1 : SCSI emulation for USB Mass Storage devices Mar 19 11:21:56 linux kernel: Vendor: Model: Rev: Mar 19 11:21:56 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Mar 19 11:21:56 linux kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 Mar 19 11:21:56 linux kernel: SCSI device sda: 125440 512-byte hdwr sectors (64 MB) Thanks John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Knossos: escape the ever-changing labyrinth before the Minotaur catches you!
I've just bought a device to let me read MMC cards on my linux box. It seems to be recognised by the system, but I don't know how to mount it. Could anyone tell me how to do this? I've tried the obvious 'mount /dev/sda /home/john/MMC', together with '-t vfat' instead to no avail.
Did the hotplug service add it to the fstab? It did when I tried one out here... If so, what does it put in it? -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 8.1) GNOME updates for SuSE: http://www.usr-local-bin.org
In a previous message, James Ogley wrote:
Did the hotplug service add it to the fstab? It did when I tried one out here...
If so, what does it put in it?
Nothing seems to have changed in my /etc/fstab. John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 March 2003 3:58 am, John Pettigrew wrote:
In a previous message, James Ogley wrote:
Did the hotplug service add it to the fstab? Nothing seems to have changed in my /etc/fstab.
see if you can determine the device "ID" using a program such as "usbview" [X-windows] or poking around /proc/bus/usb. With that, you should be able to search the linux/usb site(s) to see if anyone has broken this ground already - -- Yet another Blog: http://osnut.homelinux.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: http://osnut.homelinux.net/TomEmerson.asc iD8DBQE+eF2cV/YHUqq2SwsRAphfAJwI35dvNzSNNqh9CW/qGB2iq/CNIwCfYDdb lXt6Kx5gjfCJhkgKGR16b8c= =MLc1 -----END PGP SIGNATURE-----
In a previous message, Tom Emerson wrote:
see if you can determine the device "ID" using a program such as "usbview" [X-windows] or poking around /proc/bus/usb
Hmmm. usbview doesn't seem to work (terminal just sits there after issuing the command) and trying to open /proc/bus/usb causes the filer to hang. Perhaps this is telling me that there's a problem in my usb system? Anyhow, did you mean the vendor and device IDs, which were in my original email? They are: vend/prod - 0x7c4/0xac01. Using KDE's control centre, I've had a look at what's happening. With the device unplugged, the "SCSI" information section contains one device (my cd writer): Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: Memorex Model: Twelve MAXX 1032 Rev: LSXA Type: CD-ROM ANSI SCSI revision: 02 When I plug in the card reader, I find that there is a new entry: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: Generic Model: USB SC Reader Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02 This suggests to me that the device is actually being recognised by the system. I have tried mounting /dev/sr1 (assuming that, because the CDRW is scsi0 and mounts from /dev/sr0, the card reader at scsi1 will mount from /dev/sr1) but this says that this is an unknown device. If I try to access the USB information section, it hangs the app, just like usbview or opening /proc/bus/usb. FWIW, here is the relevant line from my fstab: usbdevfs /proc/bus/usb usbdevfs noauto 0 0 The KDE control centre also shows an oddity with my USB controller in the info section - it lists it as "Via Technologies, Inc. (Wrong ID) USB controller". Thanks, John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Knossos: escape the ever-changing labyrinth before the Minotaur catches you!
On Wednesday 19 March 2003 6:33 am, John Pettigrew wrote:
I've just bought a device to let me read MMC cards on my linux box. It seems to be recognised by the system, but I don't know how to mount it. Could anyone tell me how to do this? I've tried the obvious 'mount /dev/sda /home/john/MMC', together with '-t vfat' instead to no avail.
Try: mount -t vfat /dev/sda1 /<path to wherever> and I think you'll get a smile..... :-)
The messages file shows the following details: Mar 19 11:21:54 linux kernel: hub.c: new USB device 00:07.2-1.4, assigned address 5 Mar 19 11:21:54 linux kernel: usb.c: USB device 5 (vend/prod 0x7c4/0xac01) is not claimed by any active driver. Mar 19 11:21:55 linux kernel: Initializing USB Mass Storage driver... Mar 19 11:21:55 linux kernel: usb.c: registered new driver usb-storage Mar 19 11:21:55 linux kernel: usb-uhci.c: interrupt, status 2, frame# 1113 Mar 19 11:21:56 linux kernel: usb_control/bulk_msg: timeout Mar 19 11:21:56 linux kernel: scsi1 : SCSI emulation for USB Mass Storage devices Mar 19 11:21:56 linux kernel: Vendor: Model: Rev: Mar 19 11:21:56 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Mar 19 11:21:56 linux kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 Mar 19 11:21:56 linux kernel: SCSI device sda: 125440 512-byte hdwr sectors (64 MB)
Thanks
John
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 03/19/03 10:56 + +----------------------------------------------------------------------------+ Kauffman's First Law of Airports: "The distance to the gate is inversely proportional to the time available to catch your flight."
In a previous message, Bruce Marshall wrote:
On Wednesday 19 March 2003 6:33 am, John Pettigrew wrote:
I've just bought a device to let me read MMC cards on my linux box. It seems to be recognised by the system, but I don't know how to mount it. Could anyone tell me how to do this? I've tried the obvious 'mount /dev/sda /home/john/MMC', together with '-t vfat' instead to no avail.
Try:
mount -t vfat /dev/sda1 /<path to wherever>
and I think you'll get a smile..... :-)
I'd tried that, too, and trying it again now gives the same results - mount just sits there. top -i gives the following: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND 2675 john 23 0 10432 10M 8372 R 8.5 4.0 0:00 gedit 2569 john 15 0 8940 8936 6804 R 1.7 3.4 0:01 gnome-terminal 2628 john 15 0 976 976 756 R 0.1 0.3 0:00 top 2564 root 24 0 1320 1320 488 D 0.0 0.5 0:00 modprobe 2566 root 15 0 0 0 0 DW 0.0 0.0 0:00 scsi_eh_1 2594 root 15 0 556 556 468 D 0.0 0.2 0:00 mount Which suggests to me that (with a STAT of D) mount has had a serious problem. My USB system is basically OK, because I can sync my Palm device via USB. Admittedly, it sometimes crashes the machine (!) but I'd put this down to something about the new Palm Tungsten, because it had worked for months with no problem with my old Visor. John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards
On Wednesday 19 March 2003 11:45 am, John Pettigrew wrote:
In a previous message, Bruce Marshall wrote:
On Wednesday 19 March 2003 6:33 am, John Pettigrew wrote:
I've just bought a device to let me read MMC cards on my linux box. It seems to be recognised by the system, but I don't know how to mount it. Could anyone tell me how to do this? I've tried the obvious 'mount /dev/sda /home/john/MMC', together with '-t vfat' instead to no avail.
Try:
mount -t vfat /dev/sda1 /<path to wherever>
and I think you'll get a smile..... :-)
Ok.. tell us more about this device.. Does it read other things besides MMC devices? I have a reader here that reads 4 different devices... and because of that, it really has 4 LUN's or 4 addresses on the SCSI bus. And because of that... in order to get it mounted, I run the following script: #!/bin/sh echo "scsi add-single-device 2 0 0 0" > /proc/scsi/scsi echo "scsi add-single-device 2 0 0 1" > /proc/scsi/scsi echo "scsi add-single-device 2 0 0 2" > /proc/scsi/scsi echo "scsi add-single-device 2 0 0 3" > /proc/scsi/scsi cat /proc/scsi/scsi Try that... mine mount automatically after the above is run because I have /etc/fstab set to mount them. NOTE: In the above, since I have a SCSI system with 2 controllers already in use, the first number (2) is for the 3rd controller, the USB device. If you do not have a SCSI system (and IIRC you don't) change that number to (0).
I'd tried that, too, and trying it again now gives the same results - mount just sits there. top -i gives the following: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND 2675 john 23 0 10432 10M 8372 R 8.5 4.0 0:00 gedit 2569 john 15 0 8940 8936 6804 R 1.7 3.4 0:01 gnome-terminal 2628 john 15 0 976 976 756 R 0.1 0.3 0:00 top 2564 root 24 0 1320 1320 488 D 0.0 0.5 0:00 modprobe 2566 root 15 0 0 0 0 DW 0.0 0.0 0:00 scsi_eh_1 2594 root 15 0 556 556 468 D 0.0 0.2 0:00 mount
Which suggests to me that (with a STAT of D) mount has had a serious problem.
My USB system is basically OK, because I can sync my Palm device via USB. Admittedly, it sometimes crashes the machine (!) but I'd put this down to something about the new Palm Tungsten, because it had worked for months with no problem with my old Visor.
John
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 03/19/03 11:49 + +----------------------------------------------------------------------------+ "Murphy's Military Laws:13. The only thing more accurate than incoming enemy fire is incoming friendly fire."
In a previous message, Bruce Marshall wrote:
Ok.. tell us more about this device.. Does it read other things besides MMC devices?
No, it's a single-device reader for MMC and SD cards. It's from TwinMOS and is called a "Gogo Egg" (!). I bought it because it was cheap and is supposed to function under a simple mass-storage driver, so I thought it would be a safe bet.
#!/bin/sh echo "scsi add-single-device 2 0 0 0" > /proc/scsi/scsi
I'll try this. The problem is that each time I try to mount this device, it seems to freeze the USB system so that any subsequent access is impossible. For example, I can run usbview if it's the first thing I do. Plugging the device in causes it to show up in usbview's output, with various details. However, if I try to mount it or look at USB devices in kcontrol (for example), all USB stuff seems to stop and usbview and kcontrol stop updating their windows and have to be killed. Thus, I have to reboot between each thing I try! Thanks! John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Knossos: escape the ever-changing labyrinth before the Minotaur catches you!
On Wednesday 19 March 2003 12:15 pm, John Pettigrew wrote:
No, it's a single-device reader for MMC and SD cards. It's from TwinMOS and is called a "Gogo Egg" (!). I bought it because it was cheap and is supposed to function under a simple mass-storage driver, so I thought it would be a safe bet.
You might also show us: 1) The usb modules that are loaded after you plug the device in. 2) A cat /proc/scsi/scsi after you plug the device in. 3) Then, from one console window, do a: tail -f /var/log/messages then move to another console window and try the mount. See if any messages show up in window (1) before the hang. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 03/19/03 13:14 + +----------------------------------------------------------------------------+ "Cogito cogito ergo cogito sum: I think that I think, therefore I think that I am" - Ambrose Bierce
In a previous message, Bruce Marshall wrote:
You might also show us:
1) The usb modules that are loaded after you plug the device in.
How do I check this?
2) A cat /proc/scsi/scsi after you plug the device in.
john@linux:~> cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: Memorex Model: Twelve MAXX 1032 Rev: LSXA Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: Generic Model: USB SD Reader Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02 This seems to be what kcontrol shows in its 'SCSI' information panel.
3) Then, from one console window, do a: tail -f /var/log/messages
Nothing shows up after the mount - what shows before the mount, I listed in my first email. It is seeming more likely to me that my USB system is not working properly somehow. Admittedly, I am running a Mantel kernel (should probably have mentioned that earlier!). When I get the chance, I'll uninstall this and reinstall the standard SuSE kernel to see whether that makes a difference. Thanks, John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards
In a previous message, John Pettigrew wrote:
It is seeming more likely to me that my USB system is not working properly somehow. Admittedly, I am running a Mantel kernel (should probably have mentioned that earlier!). When I get the chance, I'll uninstall this and reinstall the standard SuSE kernel to see whether that makes a difference.
OK, I've removed the 2.4.20-31 kernel I was running and reinstated the SuSE default k_athlon 2.4.19-4GB. This has made *some* difference - now, when I plug the device in, I get extra messages: Mar 20 12:45:29 linux kernel: hub.c: USB new device connect on bus1/1/4, assigned device number 5 Mar 20 12:45:29 linux kernel: usb.c: USB device 5 (vend/prod 0x7c4/0xac01) is not claimed by any active driver. Mar 20 12:45:30 linux kernel: Initializing USB Mass Storage driver... Mar 20 12:45:30 linux kernel: usb.c: registered new driver usb-storage Mar 20 12:45:30 linux kernel: usb-uhci.c: interrupt, status 2, frame# 1765 Mar 20 12:45:31 linux kernel: usb_control/bulk_msg: timeout Mar 20 12:45:31 linux kernel: scsi1 : SCSI emulation for USB Mass Storage devices Mar 20 12:45:31 linux kernel: Vendor: Model: Rev: Mar 20 12:45:31 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Mar 20 12:45:31 linux kernel: sd_init() Mar 20 12:45:31 linux kernel: sd: allocated major 8 Mar 20 12:45:31 linux kernel: sg: find_free_slot ...<7>sg: ... found 15:01 Mar 20 12:45:31 linux kernel: sg_attach: dev1=(21:1) Mar 20 12:45:31 linux kernel: sd_attach() Mar 20 12:45:31 linux kernel: sd: find_free_slot ...<7>sd: ... found 08:00 Mar 20 12:45:31 linux kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 Mar 20 12:45:31 linux kernel: sd_finish() Mar 20 12:45:31 linux kernel: sd_init_onedisk (0,0), sda 08:00 Mar 20 12:45:31 linux kernel: SCSI device sda: 125440 512-byte hdwr sectors (64 MB) These messages seem to cover some of the suggestions people made (such as the scsi_ commands). However, I still get a console freeze when I try to mount the device at /dev/sda1 (which is what I think it must be - anything else I've tried has given "not a valid device" type errors). The problem with this kernel + drivers is that it won't let me use my Palm Tungsten, so I'll have to recompile myself a visor.o. Is there anything else I could try? I should probably add that this device works fine on the same box under Windows, so it's not a hardware problem. Thanks John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!
John Pettigrew wrote:
In a previous message, John Pettigrew wrote:
It is seeming more likely to me that my USB system is not working properly somehow. Admittedly, I am running a Mantel kernel (should probably have mentioned that earlier!). When I get the chance, I'll uninstall this and reinstall the standard SuSE kernel to see whether that makes a difference.
OK, I've removed the 2.4.20-31 kernel I was running and reinstated the SuSE default k_athlon 2.4.19-4GB. This has made *some* difference - now, when I plug the device in, I get extra messages:
After plugging it in, try fdisk -l to see what exactly you have, use mount with the correct partition and fstype and a viable mount point. HTH -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
In a previous message, Joe Morris (NTM) wrote:
OK, I've removed the 2.4.20-31 kernel I was running and reinstated the SuSE default k_athlon 2.4.19-4GB. This has made *some* difference - now, when I plug the device in, I get extra messages: After plugging it in, try fdisk -l to see what exactly you have, use mount with the correct partition and fstype and a viable mount point. HTH
This was very useful - but not only for the obvious reasons! I connected the device and gave it a few seconds, checked /var/log/messages to see that it had been detected, then tried fdisk -l. No joy - the only drives listed were the IDE ones. However, while I was puzzling about this, i heard the USB-hotplug beep and thought "Aha!". A new fdisk -l showed that I now had a drive at /dev/sda1, and mounting this worked! I've no idea why it seemed to take over a minute to recognise this device the first time, but it's now working as it should (i.e. it's now being recognised almost instantly after being plugged in). Hotplug has inserted the relevant line into my fstab and I can now mount the device as a normal user and use it :-) Thanks to all for the help - it looks like the two things needed were (1) revert to the SuSE-supplied 2.4.19 kernel and (2) wait for a *long* time the first time the device was connected for the system to recognise it. John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!
On Thursday 20 March 2003 3:12 am, John Pettigrew wrote:
In a previous message, Bruce Marshall wrote:
You might also show us:
1) The usb modules that are loaded after you plug the device in.
How do I check this?
lsmod | grep usb or just: lsmod | more
2) A cat /proc/scsi/scsi after you plug the device in.
john@linux:~> cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: Memorex Model: Twelve MAXX 1032 Rev: LSXA Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: Generic Model: USB SD Reader Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02
Note the scsi0 and scsi1 in the above. The system thinks it has two scsi controllers. Therefore, you might try the script lines I mentioned before and use a '1' for the first number. (I said to use '0')
This seems to be what kcontrol shows in its 'SCSI' information panel.
3) Then, from one console window, do a: tail -f /var/log/messages
Nothing shows up after the mount - what shows before the mount, I listed in my first email.
It is seeming more likely to me that my USB system is not working properly somehow. Admittedly, I am running a Mantel kernel (should probably have mentioned that earlier!). When I get the chance, I'll uninstall this and reinstall the standard SuSE kernel to see whether that makes a difference.
Thanks,
John
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 03/20/03 11:05 + +----------------------------------------------------------------------------+ "We're going to turn this team around 360 degrees." -Jason Kidd, upon his drafting to the Dallas Mavericks
participants (5)
-
Bruce Marshall
-
James Ogley
-
Joe Morris (NTM)
-
John Pettigrew
-
Tom Emerson