Re: Camera mounts as Unknown Device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anno domini 2022 Sun, 29 May 10:45:13 +0200
 Thierry de Coulon scripsit:
> On Sunday 29 May 2022 10.27:53 Dr. Nikolaus Klepp wrote:
> > Anno domini 2022 Sun, 29 May 09:36:59 +0200
> >
> > What does "mount" say, after it got mounted?
> >
> > Nik
>
> I can't see any difference between what mount says before or after. I can
> paste all this here if you want.

Then it didn't mount :)

Can you post a "cat /proc/partitions" before and after you plugged in the device? IMO your camera is not detected as mass storage (praise to GNOMEs of freedesktop.org). You'll have to explictly tell udev, that your camera is a mass storage device of type "disk". Matching rule would be something like this:

ENV{ID_MODEL_ID}=="32f5", ENV{ID_VENDOR_ID}=="04a9", ENV{ID_TYPE}="disk", ENV{UDISKS_AUTO}="1", ENV{UDISKS_SYSTEM}="0", ENV{UDISKS_SYSTEM_INTERNAL}="0"

That is, if at the point where udevd invokes the rule ID_VENDOR_* is set at all. I had to go for ENV{ID_SERIAL}=="CASIO_COMPUTER_CASIO_QV_DIGITAL", 'cause ID_VENDOR_* did not exist in the context.

Oh, please note the use of "==" and "=". The magic, why my camera is mounted in the end are the changes forced by "=".

Nik

>
> Thierry
>



--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx



[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux