All my cameras come up as sdb*. When the cards
are in a reader...they come up as sdb**.
It might be hal or messagebus or other things....
but I have had problems with hal, and it wasn't like
what you described. Let me know if you get it work.
kwhiskers wrote:
On 26/10/05, *Andrew Couture* <relicsrage@xxxxxxxxx
<mailto:relicsrage@xxxxxxxxx>> wrote:
OK, do you have gphoto2 installed?
If you have gthumbs installed, gphoto2 is installed.
I have two digital cameras, one Minolta DV and a Canon G5.
Both have worked flawlessly with FC2/3/4.
I am using FC4 with newest kernel.
Example...i plug in camera, gthumbs opens and asks 'import photos?'
Assuming you have FC4 and the newest kernel, 'yum install gthumbs'
or apt-get or whatever you poison.
Make sure you remove your 'rules' and other changes (put everything
back as original) then plug in your camera.
If you want,envoke gphoto2 from the CLI, or man gphoto2 for more info.
Check out the home page for gphoto2 for more information on your
camera (optional).
I have not had to play with 'fstab' or create 'local.rules' for udev
or screw with any permissions. It works out of the box, first time
every time for me. I have FC4 installed on five systems here at home,
and it just works on every computer.
andy
kwhiskers wrote:
>
>
> On 25/10/05, *Andrew Couture* <relicsrage@xxxxxxxxx
<mailto:relicsrage@xxxxxxxxx>
> <mailto: relicsrage@xxxxxxxxx <mailto:relicsrage@xxxxxxxxx>>> wrote:
>
> First off, what version of FC are you using?,
>
> do you have gphoto or gphoto2 installed?
>
> do you have gThumb installed?
>
> You can mount the thing manually, your almost there...
>
>
> kwhiskers wrote:
> > Problem: I would like to have my camera be mounted
automatically
> when I
> > plug it into its usb cable.
> > NB: Although it is plugged into the usb, it is seen as a
scsi
> device.
> >
> > I have a line in fstab:
> >
>
/dev/sda1 /media/usbdisk auto pamconsole,exec,noauto,managed
> 0 0
> >
> > I have made a dimage.rules file for udev:
> > BUS="scsi", SYSFS{model}="DiMAGE F100", KERNEL="sd?1",
> SYMLINK="camera"
> >
> > I got some of this information by entering the command:
> > udevinfo -a -p 'udevinfo -q path -n /dev/sda1'
> >
> > This is the output I get:
> >
> > device '/sys/block/sda/sda1' has major:minor 8:1
> > looking at class device '/sys/block/sda/sda1':
> > SUBSYSTEM=="block"
> > SYSFS{dev}=="8:1"
> > SYSFS{size}=="493979"
> > SYSFS{start}=="101"
> > SYSFS{stat}==" 163 163 0 0"
> >
> > follow the "device"-link to the physical device:
> > looking at the device chain at '/sys/devices/pci0000:00/0000
> > :00: 1f.2/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0':
> > BUS=="scsi"
> > ID=="2:0:0:0"
> > DRIVER=="sd"
> > SYSFS{device_blocked}=="0"
> > SYSFS{iocounterbits}=="32"
> > SYSFS{iodone_cnt}=="0x2b"
> > SYSFS{ioerr_cnt}=="0x0"
> > SYSFS{iorequest_cnt}=="0x2b"
> > SYSFS{max_sectors}=="240"
> > SYSFS{model}=="DiMAGE F100 "
> > SYSFS{queue_depth}=="1"
> > SYSFS{queue_type}=="none"
> > SYSFS{rev}=="1.00"
> > SYSFS{scsi_level}=="3"
> > SYSFS{state}=="running"
> > SYSFS{timeout}=="30"
> > SYSFS{type}=="0"
> > SYSFS{vendor}=="MINOLTA "
> >
> > couldn't open device directory
> >
> > Perhaps of note is the fact that the number on the line
> SYSFS{stat} is
> > not the same every time
> > Also, the note at the end of the output for this command:
> "couldn't open
> > device directory"
> > Is that normal? Why couldn't directory be opened? When I
manually
> mount,
> > it opens just fine.
> >
> > When I plug in the camera:
> > - the modules are loaded automatically (verified with tail
> messages, etc)
> > - the aforementioned line appears in fstab
> > - /dev/sda1 is created
> > - a link /dev/camera --> /dev/sda1 is created
> > - /media/usbdisk is created
> >
> > However, the camera is not mounted and I have to do so
manually :-(
> >
> > When I turn off the camera:
> > - /media/usbdisk disappears, but only after a very long
time (in
> a few
> > instances it didn't disappear and on next boot, when I
plugged in the
> > camera again, /media/usbdisk1 was created, in addition to the
> > pre-existing /media/usbdisk from the previous session)
> > - the line in fstab also disappears (I would have
preferred to have
> > /media/camera, but usbdisk appears no matter what I write in
> fstab, so
> > instead of fighting it, I decided that it will have to do,
unless
> > someone knows why...)
> >
> > Does anyone know how to get this working? Help would be much
> appreciated
> >
>
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx <mailto:fedora-list@xxxxxxxxxx>
<mailto:fedora-list@xxxxxxxxxx <mailto:fedora-list@xxxxxxxxxx>>
> To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
>
>
> You said I'm almost there, but actually, I'm exactly where I
started, 3
> days ago. I have learned a lot since then, but nothing that makes
any
> difference to the problem at hand.
>
--
fedora-list mailing list
fedora-list@xxxxxxxxxx <mailto:fedora-list@xxxxxxxxxx>
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Thanks, I will try this when I get home in 3 hours.
I suspect, though, that your cameras are not scsi mass storage cameras,
hence are recognized by gphoto out of the box. Nevertheless, I will try.
I have done quite a lot of reading, and I have come to the conclusion
that the real problem is HAL. I have to set up the .fdi file so that the
mass storage device gets automounted.
