Greetings! Here be a tale or two. Red Hat 9, by the way, on a Compaq Armada 1750 laptop with USB port.
To begin at the beginning. For some time I've had a Disgo 256MB USB memory stick. I have had no trouble using this, able to remove it and re-insert it at any time, mount it, and access the files. I set up an entry in /etc/fstab for it which says:
/dev/sda1 /flash auto noauto,suid,dev,exec,user 0 0
so, once I've inserted it and something-or-other goes through a detection process, I can 'mount /flash' and all is well.
Or was.
Yesterday, I spotted a Fujifilm FinePix F440 digital camera on sale at a very interesting price. After checking out reviews (all pretty favourable for general usage) I went back and bought it. A bit speculatively from the Linux point of view, but I reckoned that a similar approach to the USB stick would work.
Since it has been some time since the USB stick was last used, the laptop has been rebooted a time of two since then.
Having taken a few test photos, I then connected the camera to the USB port, switched it on, waited for the "detect", and then as usual ran 'mount /flash'. Again, all went well, I could download the picture files (JPG) and they were good. Then ran 'umount /flash' and disconnected the camera.
Then I tried its "video" function: you can take up to 60 secs of video (with sound) with this camera, which gives you a 4MB AVI file. Again, no problem re-connecting the camera and down- loading the AVI file. (And, by the way, 'xanim' plays these files well).
So far so good, and I repeated the above tests a few time (again, disconnecting and reconnecting the camera to the USB port, with 'mount /flash' and 'umount /flash' each time). It looked as though this arrangement would work just the same as for the USB memory stick.
But then, to try to explore the reason for something unexpected (see "FINAL INDEPENDENT QUESTION" at end), I inserted the USB memory stick. Unusual and unpromising messages on "autodetect", and 'mount /flash' gave message "mount: No medium found". FAILURE!!
So I then explored with happens if I reboot. It's a long story, but this is the summary:
A. Repeated connection disconnection of same device following a reboot.
1. Reboot. Insert USB memory stick. It works fine first time, as above. Remove USB stick, reinsert. FAILURE. And it fails every time I re-try unless I reboot.
2. Reboot. Connect camera. Works fine, as above. Switch off camera, disconnect. Re-connect, switch on, and it works fine. Ad infinitum without reboot.
B. Alternating connection of the two devices following a reboot.
3. Reboot. Insert USB memory stick. Works fine as at (1). remove USB stick, connect camera. Camera fails (message "no medium found" on 'mount /flash'). Disconnect camera, insert USB memory stick, stick fails (message "/dev/sda1 is not a valid block device" on 'mount /flash'). Exactly the same failure for Camera as previous camera failure. Exactly the same failure for Stick as previous stick failure. Ditto ad infinitum with Camera/Stick/Camera/...
4. Reboot. Connect camera. Works fine as at (2). Disconnect camera, insert Stick. Stick fails with "no medium found". Remove stick, connect camera. Camera OK as at (2). Disconnect camera, insert stick. Stick fails again in exctaly the same way. Camera OK. Stick fails. Camera OK. And so on.
SO: Whichever device is first in following a reboot works fine first time.
If Stick is first in, it only works first time, and fails subsequently, and Camera always fails.
If Camera is first in, it works first time and every time, whether Stick has been used or not; but Stick always fails.
So that's the situation. If I only use the Camera, there would be no problem. But I would have to reboot each time I want to use the Stick, whether I have used the Camera or not!
Any ideas? (I suspect I may have tickled Red Hat's "kudzu" in some way it didn't like, but I've never managed to disentangle what goes on with kudzu).
FINAL INDEPENDENT QUESTION: This is what got the above saga rolling (though I'd have hit it some time anyway). I wanted to transfer the Camera files directly to a different machine networked to the laptop (since I usually keep stuff like photos on the other). Rather than download from Camera to laptop and then ftp them across, I thought I'd try downloading to Machine 2 direct from the camera via NFS.
So, with the Camera connected to the laptop and mounted on /flash, from machine 2, I (as root) NFS-mounted the laptop's root directory machine 2. The directory of the Camera memory chip was visible on the laptop, type VFAT, and 'ls .flash' etc. showed all the files on the Camera. However, while the laptop's file system (including the presence of /flash, and files in other directories) was visible from Machine 2, 'ls laptop/flash' showed an empty directory on machine 2.
This was unexpected, so I wondered if it had something to do with the fact that what was mounted on the laptop's /flash directory was a USN storage device, was a peculiarity of the camera, or whatever..
Hence I thought I would experiment by trying to NFS-mount the laptop with the Stick in instead. So I plugged in the stick, did 'mount /flash', and then found myself in the above Saga!
Therefore, is anyone can answer this independent question as well (or instead of) the business about Stick/Camera conflict, I'd be interested!
Thanks, and best wishes to all, Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 26-Jun-05 Time: 14:50:31 ------------------------------ XFMail ------------------------------
On 6/26/05, Ted Harding Ted.Harding@nessie.mcc.ac.uk wrote:
Greetings! Here be a tale or two. Red Hat 9, by the way, on a Compaq Armada 1750 laptop with USB port.
Debian and co. use hotplug which manages the insert events and can automatically mount partitions.
Which kernel are you using?
Regards, Tim.
On 26-Jun-05 Tim Green wrote:
On 6/26/05, Ted Harding Ted.Harding@nessie.mcc.ac.uk wrote:
Greetings! Here be a tale or two. Red Hat 9, by the way, on a Compaq Armada 1750 laptop with USB port.
Debian and co. use hotplug which manages the insert events and can automatically mount partitions.
Which kernel are you using?
Regards, Tim.
Well, I's rather not go installing a different version of Linux! Too much hassle given what's on this machine already.
Anyway, I have
/usr/src/linux-2.4.20-8
so I guess it's kernel 2.4.20-8!
What's peculiar is that before I ever connected the Camera to the USB socket, I could plug and unplug the MemStick any number of times and it would work every time. So up till yesterday that kernel has worked fine with the USB stick.
Now, if I plug the stick in as the first USB item after a reboot, the Stick works first time and, once unplugged, thereafter not at all until the next reboot, and the Camera won't work at all.
But if I plug the Camera in as the first USB item after a reboot, the Camera works every time it's plugged in, but the stick never works.
So for some reason, using the Camera for the first time has screwed up something in the Stick usage which was not screwed up before, even if I don't use the Camera at all!
It rather lookas as though it may be the module configuration for the USB/SCSI setup when a USB storage device is plugged in which has got into a twist.
But I'm actually beginning to wonder if plugging in the USB plug on the Camera cable bent something in the USB socket which affects the contact with the USB plug on the Stick, so that unplugging doesn't get properly registered, and plugging doesn't get properly registered to over-ride a previous Camera plugin.
If so, then it could be bad news --nothing nastier to get fixed than a broken USB socket on a laptop!
An alternative is that the Stick plug may be dodgy -- can only test that by trying another stick, I suppose.
Thanks for the suggestion, anyway!
Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 26-Jun-05 Time: 23:14:38 ------------------------------ XFMail ------------------------------
SO: Whichever device is first in following a reboot works fine first time.
Although both devices will count as usb-storage, I suspect they require different drivers so on inserting device A, hotplug (or whatever it is that does the autodetecting goodness) loads up device driver A. When you unplug it, the driver is probably still loaded and so device B cannot work because driver A still "controls" the usb-storage. Maybe. I'm guessing.
Try booting, plugging in the memory stick, removing it and then doing an lsmod.
So, with the Camera connected to the laptop and mounted on /flash, from machine 2, I (as root) NFS-mounted the laptop's root directory machine 2. The directory of the Camera memory chip was visible on the laptop, type VFAT, and 'ls .flash' etc. showed all the files on the Camera. However, while the laptop's file system (including the presence of /flash, and files in other directories) was visible from Machine 2, 'ls laptop/flash' showed an empty directory on machine 2.
I could be wrong about this because I've never used nfs meself but I'm guessing that, because you've mounted the root partition over nfs to machine 2, you see just what is _stored_ on the root partition itself. Just because you've mounted /flash locally to the laptop doesn't mean the files are _on_ the root partition, they're just superimposed for users of the laptop.
I don't think I explained that very well but I hope you see what I mean.
I'm gussing you'd need to nfs share /flash
Try putting some other files in /flash while you don't have /flash mounted, then mount the camera or memory stick and see what you see from Machine 2.
Excuse my drivel and excessive round-the-houses going but it's morning and it's Monday and I'm not quite awake yet.
Cheers, Steve
FINAL INDEPENDENT QUESTION: This is what got the above saga rolling (though I'd have hit it some time anyway). I wanted to transfer the Camera files directly to a different machine networked to the laptop (since I usually keep stuff like photos on the other). Rather than download from Camera to laptop and then ftp them across, I thought I'd try downloading to Machine 2 direct from the camera via NFS.
I do not believe that you can NFS export a VFAT filesystem.
Jim
So, with the Camera connected to the laptop and mounted on /flash, from machine 2, I (as root) NFS-mounted the laptop's root directory machine 2. The directory of the Camera memory chip was visible on the laptop, type VFAT, and 'ls .flash' etc. showed all the files on the Camera. However, while the laptop's file system (including the presence of /flash, and files in other directories) was visible from Machine 2, 'ls laptop/flash' showed an empty directory on machine 2.
This was unexpected, so I wondered if it had something to do with the fact that what was mounted on the laptop's /flash directory was a USN storage device, was a peculiarity of the camera, or whatever..
Hence I thought I would experiment by trying to NFS-mount the laptop with the Stick in instead. So I plugged in the stick, did 'mount /flash', and then found myself in the above Saga!
Therefore, is anyone can answer this independent question as well (or instead of) the business about Stick/Camera conflict, I'd be interested!
Thanks, and best wishes to all, Ted.
E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 26-Jun-05 Time: 14:50:31 ------------------------------ XFMail ------------------------------
On Monday 27 Jun 2005 3:58 pm, Jim Jackson wrote:
FINAL INDEPENDENT QUESTION: This is what got the above saga rolling (though I'd have hit it some time anyway). I wanted to transfer the Camera files directly to a different machine networked to the laptop (since I usually keep stuff like photos on the other). Rather than download from Camera to laptop and then ftp them across, I thought I'd try downloading to Machine 2 direct from the camera via NFS.
I do not believe that you can NFS export a VFAT filesystem.
I beg to disgree. You should be able to export any filesystem mounted by any file-system support module. SImply because in order to mount any filesystem the file-system support module (e.g. vfat.o) must present the system with vnodes (the very thing that NFS exports). If you can mount it (& see it as a llinux (UNIX) file-system - then you can export it via NFS).
Just my 10cc
Jim
So, with the Camera connected to the laptop and mounted on /flash, from machine 2, I (as root) NFS-mounted the laptop's root directory machine 2. The directory of the Camera memory chip was visible on the laptop, type VFAT, and 'ls .flash' etc. showed all the files on the Camera. However, while the laptop's file system (including the presence of /flash, and files in other directories) was visible from Machine 2, 'ls laptop/flash' showed an empty directory on machine 2.
This was unexpected, so I wondered if it had something to do with the fact that what was mounted on the laptop's /flash directory was a USN storage device, was a peculiarity of the camera, or whatever..
Hence I thought I would experiment by trying to NFS-mount the laptop with the Stick in instead. So I plugged in the stick, did 'mount /flash', and then found myself in the above Saga!
Therefore, is anyone can answer this independent question as well (or instead of) the business about Stick/Camera conflict, I'd be interested!
Thanks, and best wishes to all, Ted.
E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 26-Jun-05 Time: 14:50:31 ------------------------------ XFMail ------------------------------
I do not believe that you can NFS export a VFAT filesystem.
I beg to disgree. You should be able to export any filesystem mounted by any file-system support module. SImply because in order to mount any filesystem the file-system support module (e.g. vfat.o) must present the system with vnodes (the very thing that NFS exports). If you can mount it (& see it as a llinux (UNIX) file-system - then you can export it via NFS).
Indeed, I recall a very clever friend of mine advising me to export a vfat partition via nfs to work around some permissions(orthelackthereof)-related problem with said vfat partition on a super-short-term basis.