Digital Camera on SuSE 10 Not Recognized

petelogan · 11-11-2005, 05:50 AM

I've done a search, read everything I can and followed the suggestions, but still can't get the camera working under 10.0 Eval, installed from downloaded CDs. Everything else works fine.

I have a Sony DSC-U10 which was previously working fine via USB under 9.1

The USB Monitor in KMenu shows the camera connected.

SuSEPlugger is running (though it does not appear in KMenu as I saw in one thread).

My /etc/fstab file is like this, which I believe provides the necessary scsi device definition to route the camera through.

Quote:

/dev/hda2 / reiserfs acl,user_xattr 1 1
/dev/hda1 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/hdc1 /home auto acl 0 0
/dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
none /subdomain subdomainfs noauto 0 0
/dev/sda1 /media/camera vfat noauto,users 0 0

The folder /media/camera exists.

But the camera does not appear in Konqueror (My Computer icon) under the new Services | Storage Media tab, which replaced the 9.1 Devices tab.

An attempt to issue a mount command through Konsole reports that sda1 does not exist.

Same under root or a user.

I'm stuck

What am I missing ?

Thanks for any help.

Pete

meranto · 11-11-2005, 06:06 AM

check "/dev/disks/by-id" and see if your device is listed there. If it is, look where the symlink points to, maybe it's named sda2 of sdb1 or whatever.

dth1 · 11-11-2005, 06:44 AM

When you plug in your camera go media and see if it is shown there.

petelogan · 11-11-2005, 07:54 AM

/dev/disk/by-id gives

Quote:

file:///dev/disk/by-id/ata-Maxtor_6E040L0_E10E4ADE
file:///dev/disk/by-id/ata-Maxtor_6E040L0_E10E4ADE-part1
file:///dev/disk/by-id/ata-Maxtor_6E040L0_E10E4ADE-part2
file:///dev/disk/by-id/ata-SAMSUNG_SV4002H_0479J1FT706318
file:///dev/disk/by-id/ata-SAMSUNG_SV4002H_0479J1FT706318-part1

which are my two hard drives, so it's not showing up there.

/media shows:

Quote:

file:///media/bmp_audio_cd
file:///media/camera
file:///media/cdrecorder
file:///media/xmms_audio_cd

I created /media/camera as a place to mount the scsi representation of the camera, but /media/camera is empty.

The camera is plugged in as I write, and Kmenu | System | Monitor | USB Devices shows a Sony DSC camera with a Product ID of (DSC-S30/S70/S75/F505V/F505/FD92 Cybershot/Mavica Digital Camera).

KMenu | System | Monitor | SCSI shows no scsi devices.

Looks to me like the system is seeing the camera, but not attaching it to a scsi device and therefore not mounting it.

If I read other threads correctly, I guess SuSEPlugger is supposed to be doing this. It is running according to the KDE System Guard ProcessTable.

Just thinking out loud, is there a SuSEPlugger config setup that tells it what to do or not do on an automatic basis ?

Thanks for the input.

Pete

fragos · 11-11-2005, 07:21 PM

SuSE should be auto mounting your camera. It takes longer than for a memory stick. eventually a konqueror window should pop up with a file view of the camera storage. You can now treat it like any other file device. You can also use digikam to open the camera storage and place pictures in an album. I say this based on experience with a Canon A75 but I'd be surprised if its different for Sony. I didn't have to configure anything for this to work.

Mounting has changed in SuSE 10.0 for the better. You no longer need to interact with SuSEplugger for it to work so the desktop icon isn't there.

petelogan · 11-12-2005, 03:54 PM

Understand and agree, but it isn't happening. The camera's been plugged in for the last 3 days

I understand about the plugger icon. It was just that in another thread someone was insisting that it should be in the KMenu, and it ain't - at least on mine.

I guess I'm stuck, but thanks to everyone for your help.

Pete

Okie · 11-12-2005, 04:46 PM

get these three packages:

libgphoto2

gphoto2

gtkam

1 compile libgphoto2 first

2 compile gphoto2 second

3 compile gtkam last, for a user friendly gui front end

if gtkam is not working open a terminal and type in gphoto2 --auto-detect and
gphoto2 --get-all-files

petelogan · 11-14-2005, 10:14 AM

Thanks. YAST says these 3 are in already.

gphoto2 --auto-detect shows no cameras, even though USB Monitor sees it OK, which I presume means Linux sees it OK but is not mounting it for some reason.

Pete

fragos · 11-14-2005, 01:29 PM

For the sake of completeness there are two things I need to do on my Canon A75 to make things work. The Canon has a switch that goes between picture and menu mode -- select menu mode. 2nd I have to turn the camera on. The Sony may not have a parallel for the mode switch but you still probably need to turn it on.

petelogan · 11-14-2005, 02:24 PM

Quote:

Originally posted by fragos The Sony may not have a parallel for the mode switch but you still probably need to turn it on. [/B]

It has a Play, Still and Movie switch. Never made a difference in the past, and I have tried Play and Still with no result.

The camera is recognised by Linux, I think, but is not mounted as any kind of recognisable drive, so is not available to applications.

I think maybe 10.1

I need to turn it on ? Nice one

Okie · 11-14-2005, 02:27 PM

in order for gphoto2 and gtkam to work you do need hotplug started too...

i should have mentioned that in my first reply...

P.S. Hotplug does slow down boot time by anywhere from 30 seconds up to a minute longer, or if you start hotplug after boot it is slow to launch even on fast computers...

petelogan · 11-14-2005, 02:35 PM

suseplugger is running, loaded automatically.

What can I tell you

To be honest, I think it's prolly best to just wait for 10.1.

The heck with it.

wiresquire · 11-14-2005, 03:14 PM

It's possible that there is a hotplug policy in place that prevents the 'media' from loading correctly. I only learnt about this recently.

Hotplugging is controlled by hal daemon (hald). Is that running? SUSEplugger should start it automagically.

The policies live in the directories under
/usr/share/hal/fdi/
On my SUSE 9.3, there's a policy file
/usr/share/hal/fdi/20freedesktop/sony_dsc.fdi

It may be worth checking that out to see if it matches OK with your camera. Also there could be other policies that modify that.

Best to google around for
hal fdi
to understand what's going on.

Like I said, I'm newbie on this stuff.

hth
ws

petelogan · 11-15-2005, 03:46 AM

Thanks - I hadn't realized that.

hald is running - starts automatically. My file structure appears to be similar to yours but not quite the same, as there are no camera specific files.

Looks like I have some reading and digging to do, which will take me a while due to time constraints, but I'll report back when I can.

Thanks again.

Pete

wiresquire · 11-15-2005, 06:20 AM

If it helps, my file looks like this:
# cat /usr/share/hal/fdi/20freedesktop/sony_dsc.fdi

Code:

<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->

<deviceinfo version="0.2">
  <device>
    <match key="info.bus" string="usb">
      <match key="usb.vendor_id" int="0x054c">
        <match key="usb.product_id" int="0x0010">
          <merge key="info.category" type="string">camera</merge>
          <merge key="info.capabilities" type="string">camera</merge>
          <merge key="camera.access_method" type="string">storage</merge>
        </match>
      </match>
    </match>
  </device>
</deviceinfo>

good luck
ws