Post #323,460
3/25/10 2:50:16 PM
|
Ubuntu stopped automounting camera
I'm pretty sure I fought with this a while back, but can't find a thread discussing it. My digital camera (not video) is no longer automounting. It's recognized, assigned to /dev/sdb1, and mounts manually without any problems.
I rebooted last night for the first time in a while, so it's probably some kernel mod in the last few months that made the difference. All the pointers I can find online are how to turn automount on or off, and that the location of the configuration has moved. But nothing about what to do when everything is configured right and it still doesn't work.
Any suggestions?
--
Drew
|
Post #323,466
3/25/10 5:41:58 PM
|
Kodak? If not, maybe this thread will help anyway.
http://ubuntuforums....hp/t-1163070.html
[...]
trx64
December 29th, 2009, 02:24 PM
I have found a partial solution here from Petr:
https://bugs.launchp...linux/+bug/331681
Quick fix - run script in terminal "sudo killall gvfs-gphoto2-volume-monitor" then connect the camera.
Long-term fix (Prevent the process from starting) - run script in terminal "sudo chmod -x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor"
Then go to System -> Preferences -> Removable drives and media -> Cameras and remove the "f-spot-import" with "gthumb --import-photos" or etc...
The quick fix works for me, have just tried it. However, there is no 'Removable drives and media' menu in Karmic so I don't know how to complete the action. Hopefully someone more knowledgeable can chime in.
Tom
Worked form me (Kodak EasyShare Z915). It's a bug in Ubuntu, Mandriva recognized my camera out of box.
Try to right-click in the system menu, and select "Edit Menus". The "Removable drives and media" is probably there, it's just disabled. Homever, you can execute it with:
$ gnome-volume-properties
However, lots of people reply and say it didn't work for them.
HTH a little.
Cheers,
Scott.
|
Post #323,468
3/25/10 7:56:28 PM
|
Thanks, but no, my problem's earlier
Theirs aren't mounting correctly. Mine isn't even trying to mount. The mount works fine manually, it's just automount that isn't happening. (Yes, I tried their solution anyway.)
--
Drew
|
Post #323,469
3/25/10 8:09:02 PM
|
Did you change the USB mode of your camera?
If you changed from mass storage to that other mode...
That is your problem.
I had the same thing with my Sansa.
|
Post #323,471
3/25/10 8:39:53 PM
|
I didn't touch anything on the camera
The difference was a reboot to apply a new kernel. And whatever changes were associated with that.
--
Drew
|
Post #323,508
3/26/10 10:27:42 AM
|
I still use Debian Sid.
There is a reason for that... and its staring you in the face.
It only took 2.7 years to get a bug fixed dealing with not having a battery in my T61 while being on and not being forced into 800MHz mode.
Now I get 1.6GHz, better but not fixed. Its a Kernel issue. But everything else seems to work... oh except the Debian policy regarding *BLOB FIRMWARE*.
So, right now I am stuck on 2.6.31-rc4.
2.6.32 is where all the stabilization is happening for the squeeze release and I cannot boot that Kernel as no X will be there, as the *BLOB* firmware for the video card is considered non-free. Except its available in full source code, but GCC can't compile it in that form and has to be compiled by the Intel compiler. (its loadable by any loader then).
Grrr.
|
Post #323,512
3/26/10 10:52:58 AM
|
Well that sucks
--
Drew
|
Post #324,224
4/7/10 10:36:05 PM
|
Re: Ubuntu stopped automounting camera
I tried the following for an extra HDD, not sure if it would work for cameras:
In Terminal -
sudo apt-get install pysdm
Now that pysdm is installed, you'll find it under System > Administration > Storage Device Manager
Starting it, you'll see your list of drives on the left pane. Select the drive and partition you want (this assumes you know how to do that already) and click Assistant.
In assistant choose at least The file system is mounted at boot time along with any other options you might want.
Apply and reboot to verify it's working.
|
Post #324,233
4/8/10 8:32:27 AM
|
Found that, one problem
That works for mounting something that's connected at startup. I need to hotplug a USB device.
--
Drew
|
Post #324,353
4/10/10 1:20:31 AM
|
/dev/sdb1 implies USB storage mode
libgphoto is necessary for PTP cameras as those do not create /dev entries. That is probably why the hints higher up didn't help out.
http://www.debian-ad....org/articles/127
The above is a tutorial on how to set udev and autofs up to automount USB storage devices. The last two comments (Jan and Mar 2010) read like they have the same issue you ran into. It looks like a change to autofs may be the cause (although the switch to v5 seems to have been underway for a couple of years). One got things going by adding an autofs line to /etc/nsswitch.conf
Is there anything in /var/log/debug related to autofs?
|
Post #324,384
4/10/10 2:49:33 PM
|
Tried it, but no
I didn't have autofs installed, so I tried following the steps in that article. No joy. But since I didn't have autofs before the last kernel update and it was working, it seems I've got some other problem.
As for /var/log/debug it's showing:
Apr 10 14:40:52 drook-desktop kernel: [1518832.644828] usb-storage: device found at 19
Apr 10 14:40:52 drook-desktop kernel: [1518832.644832] usb-storage: waiting for device to settle before scanning
Apr 10 14:40:57 drook-desktop kernel: [1518837.645929] usb-storage: device scan complete
Apr 10 14:40:57 drook-desktop kernel: [1518837.666881] sd 10:0:0:0: [sdb] Mode Sense: 04 00 00 00
To me that looks like everything is detected properly. And a manual mount works just fine. Guess I'll wait to see if a future kernel update fixes it. --
Drew
|
Post #324,400
4/10/10 6:05:19 PM
|
One last far flung try...
http://michael-peete...blems-of-usb.html
He found ndiswrapper (compatibility layer for MS WiFi drivers) had been registered as the driver for USB mass storage devices. And also that ndiswrapper now seems to be part of the base Ubuntu installation...
Any way, if you get the /dev/sdb link, then the kernel is pretty much done with it. Everything beyond that is userspace, so I think the problem is on that side.
|
Post #324,401
4/10/10 6:13:09 PM
|
Will take a look, but not hopeful
Like I said I can mount it manually and it works fine. It's just the automount that isn't happening. You're right that that's in userspace, but it was after my last reboot -- which only happens for kernel changes -- that it stopped working.
--
Drew
|
