Wrong filename case when inserting a camera memory card.

In short: the files in 11.2 of the memory card from my camera were lower
case, and in 11.4 they are upper case. Thus, F-spot uploads all the photos
again, and I get two copies of each, one low case (old), another upper case
(new), without the comments or rotations that I had made.

How can I make the system automount it again in lower case?

I knew the proper options to do this manually in fstab, but not via udev or
whatever it uses.



Messages log:

>
> May 19 19:39:10 minas-tirith kernel:  3510.269125] usb 1-1: new high speed USB device using ehci_hcd and address 3
> May 19 19:39:10 minas-tirith kernel:  3510.395733] usb 1-1: New USB device found, idVendor=0bda, idProduct=0159
> May 19 19:39:10 minas-tirith kernel:  3510.395739] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> May 19 19:39:10 minas-tirith kernel:  3510.395743] usb 1-1: Product: USB2.0-CRW
> May 19 19:39:10 minas-tirith kernel:  3510.395746] usb 1-1: Manufacturer: Generic
> May 19 19:39:10 minas-tirith kernel:  3510.395749] usb 1-1: SerialNumber: 20071114173400000
> May 19 19:39:10 minas-tirith kernel:  3510.401165] scsi7 : usb-storage 1-1:1.0
> May 19 19:39:11 minas-tirith mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1"
> May 19 19:39:11 minas-tirith mtp-probe: bus: 1, device: 3 was not an MTP device
> May 19 19:39:11 minas-tirith kernel:  3511.403550] scsi 7:0:0:0: Direct-Access     Generic- Multi-Card       1.00 PQ: 0 ANSI: 0 CCS
> May 19 19:39:11 minas-tirith kernel:  3511.403893] sd 7:0:0:0: Attached scsi generic sg2 type 0
> May 19 19:39:12 minas-tirith kernel:  3511.940120] sd 7:0:0:0: [sdb] 7698432 512-byte logical blocks: (3.94 GB/3.67 GiB)
> May 19 19:39:12 minas-tirith kernel:  3511.940995] sd 7:0:0:0: [sdb] Write Protect is off
> May 19 19:39:12 minas-tirith kernel:  3511.941001] sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
> May 19 19:39:12 minas-tirith kernel:  3511.941027] sd 7:0:0:0: [sdb] Assuming drive cache: write through
> May 19 19:39:12 minas-tirith kernel:  3511.945618] sd 7:0:0:0: [sdb] Assuming drive cache: write through
> May 19 19:39:12 minas-tirith kernel:  3511.947135]  sdb: sdb1
> May 19 19:39:12 minas-tirith kernel:  3511.949612] sd 7:0:0:0: [sdb] Assuming drive cache: write through
> May 19 19:39:12 minas-tirith kernel:  3511.949627] sd 7:0:0:0: [sdb] Attached SCSI removable disk

Mounted as:

> minas-tirith:~ # mount | grep sdb
> /dev/sdb1 on /media/AEA9-05F6 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks)


Can I somehow force it to be mounted lowercase as before, or do I have to
accept this change?


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-05-19 20:03, Carlos E. R. wrote:

Ping!


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I did some googling, this may be an issue with vfat.

Some people suggest mounting with the following options


shortname=lower
posix=1

Good luck,
Hiatt

On 05/20/2011 02:33 PM, Carlos E. R. wrote:
> Ping!

wish i could help, but all i can actually do is guess you need a little
higher level of technical knowledge than you are highly likely to find
here, before you next wanna ping!

so, i’d suggest:

post to alt.os.linux.suse
post to an openSUSE mail list
ask on the IRC channel
etc


dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255

jthiatt08 wrote:
> Some people suggest mounting with the following options
>
> Code:
> --------------------
>
> shortname=lower
> posix=1
>
> --------------------
>
>
I think this is what Carlos already knows and this does not help for udev.
The point is how to tell udev (which is used by gnome and kde for that
desktop environment automount feature or however it is called) to do the
same. I did not find out so far. With fstab it is obviously no problem, with
udev rules I seem also to be completely unable to find out how to do the
same.


PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.3 | GeForce
9600 GT | 4GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
ION | 3GB Ram

On 2011-05-20 15:36, jthiatt08 wrote:
>
> I did some googling, this may be an issue with vfat.

Yes, indeed, vfat mount has options to convert all files to uppercase when
mounting in linux. I know that.

> Some people suggest mounting with the following options
>
> Code:
> --------------------
>
> shortname=lower
> posix=1
>
> --------------------

It is automounted by Gnome, thus the options are beyond my reach.

I may have to indeed, mount it manually always to bypass this bug.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-05-20 15:08, DenverD wrote:
> On 05/20/2011 02:33 PM, Carlos E. R. wrote:
>> Ping!
>
> wish i could help, but all i can actually do is guess you need a little
> higher level of technical knowledge than you are highly likely to find
> here, before you next wanna ping!
>
> so, i’d suggest:
>
> post to alt.os.linux.suse
> post to an openSUSE mail list
> ask on the IRC channel
> etc

No, this is something that the good folks at openSUSE/Gnome have done. They
default to mount vfat with the options that convert all names to upper
case, while on previous version they did not - thus breaking things.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Sorry, I guess I’m not much help here.

It seems it’s hardcoded in DeviceKit and the developers get flamed here:

Rant: Arrogant Developers - Kirsle.net

I’m fortunately I didn’t hit this because I download directly from camera using USB from digikam rather than deal with flash cards.

On 2011-05-20 15:50, Carlos E. R. wrote:

> No, this is something that the good folks at openSUSE/Gnome have done. They
> default to mount vfat with the options that convert all names to upper
> case, while on previous version they did not - thus breaking things.

I’m guessing that it is 11.2 which was wrong and converted to lowercase. I
have to check two things later and I will comment on that.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-05-20 16:36, ken yap wrote:
>
> It seems it’s hardcoded in DeviceKit and the developers get flamed
> here:
>
> ‘Rant: Arrogant Developers - Kirsle.net
> (http://www.kirsle.net/blog/kirsle/rant--arrogant-developers)

Yes, it matches my checks so far.

> I’m fortunately I didn’t hit this because I download directly from
> camera using USB from digikam rather than deal with flash cards.

In 11.2 the camera is detected, but does not work. In 11.4 I haven’t tested
it yet.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-05-20 20:42, Carlos E. R. wrote:
> On 2011-05-20 15:50, Carlos E. R. wrote:
>
>> No, this is something that the good folks at openSUSE/Gnome have done. They
>> default to mount vfat with the options that convert all names to upper
>> case, while on previous version they did not - thus breaking things.
>
> I’m guessing that it is 11.2 which was wrong and converted to lowercase. I
> have to check two things later and I will comment on that.

Yes, 11.2 mounts the card like this:


>
> /dev/sde1 on /media/AEA9-05F6 type vfat (rw,nosuid,nodev,uhelper=devkit,uid=1000,gid=100,shortname=lower,dmask=0077,utf8=1,flush)
>

The trick is the “shortname=lower” option. This happens because of this
setting in gconf:

/system/storage/default_options/vfat/mount_options
shortname=lower,flush,utf8,uid=

And indeed, looking at the hexadecimal dump of the card, the filenames
(short) are stored in uppercase. Thus the correct display is uppercase. The
problem is that it is a different default than in 11.2, and there is no way
to change the default - except mounting manually.

11.4 mounts differently:


>
>
> /dev/sdb1 on /media/AEA9-05F6 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks)
>

And all the /system/storage/ keys in gconf have disappeared, we can not
configure defaults. Now it uses “shortname=mixed”, hardcoded.

So, yes, there has been a change, and the user has been denied control.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-05-20 20:42, Carlos E. R. wrote:
> In 11.2 the camera is detected, but does not work. In 11.4 I haven’t tested
> it yet.

Yes, 11.4 can work with the camera. But the connector is small and very
easy to disconnect, just moving the camera unplugs it in mid-transaction.
Dangerous.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 05/20/2011 10:50 PM, Carlos E. R. wrote:

> Yes, 11.4 can work with the camera. But the connector is small and very
> easy to disconnect, just moving the camera unplugs it in mid-transaction.
> Dangerous.

read the directions, i’m sure it is in your camera user manual:

“Do not move the camera while connected to another device.” :slight_smile:


dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255

On 2011-05-21 14:16, DenverD wrote:
> On 05/20/2011 10:50 PM, Carlos E. R. wrote:
>
>> Yes, 11.4 can work with the camera. But the connector is small and very
>> easy to disconnect, just moving the camera unplugs it in mid-transaction.
>> Dangerous.
>
> read the directions, i’m sure it is in your camera user manual:
>
> “Do not move the camera while connected to another device.” :slight_smile:

Ha, ha. Look how I laugh :-}

I did not move the camera. I just used the laptop’s touchpad, the hand
passed near the cable… that was enough.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 05/21/2011 03:08 PM, Carlos E. R. wrote:
> I did not move the camera. I just used the laptop’s touchpad, the hand
> passed near the cable… that was enough.

that is really kinda strange…is it a proprietary cable on one end and
usb on the other?

i ask because my current camera uses a standard USB cable, and though
the part that plugs into the camera is very small, it is also quite snug
and i’ve never had it just fall out…

maybe put a rubber band around the camera to trap the cord in a place
where it can’t fall out…


dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255

On 2011-05-21 15:22, DenverD wrote:
> On 05/21/2011 03:08 PM, Carlos E. R. wrote:
>> I did not move the camera. I just used the laptop’s touchpad, the hand
>> passed near the cable… that was enough.
>
> that is really kinda strange…is it a proprietary cable on one end and usb
> on the other?

Yep.

The “proprietary end” has an engrossment with some electronics and
red/green LED. The same cable is used for charging. The engrossment in the
cable impedes the plug from fully entering the camera socket.

> i ask because my current camera uses a standard USB cable, and though the
> part that plugs into the camera is very small, it is also quite snug and
> i’ve never had it just fall out…

It doesn’t fall out, it just moves a bit and the usb connection fails. The
battery connection may still work, though.

> maybe put a rubber band around the camera to trap the cord in a place where
> it can’t fall out…

Or not use the cable with the laptop, only with the desktop.

By the way, I think I lost some photos, or I can’t find them again. I don’t
see a missing number in the filenames, but I can’t find two photos I made
of an interesting antena. Weird. Yesterday afternoon I saw them. During the
night they disappeared. With all the testing I deleted the directories
several times in both computers, but never in the camera. But those two or
three photos are somehow lost.

Must be a secret black operations antenna, so “they” wiped the proofs. :-p


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-05-21 16:51, Carlos E. R. wrote:
> By the way, I think I lost some photos, or I can’t find them again. I don’t
> see a missing number in the filenames, but I can’t find two photos I made
> of an interesting antena. Weird. Yesterday afternoon I saw them. During the
> night they disappeared. With all the testing I deleted the directories
> several times in both computers, but never in the camera. But those two or
> three photos are somehow lost.
>
> Must be a secret black operations antenna, so “they” wiped the proofs. :stuck_out_tongue:

Oops! What from the ground, afar, looked to be antennas, when zoomed in
were really power line isolators. So I did not recognize the two photos for
what they were, the power line itself I could not see in the bright sun and
several hundred meters below. Curious!

Mystery solved.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 05/21/2011 04:51 PM, Carlos E. R. wrote:
> The “proprietary end” has an engrossment with some electronics and
> red/green LED. The same cable is used for charging. The engrossment in the
> cable impedes the plug from fully entering the camera socket.

i think would contact the maker of that camera and (nicely) complain
about the design (which is the apparent problem)…i mean either your
cable is not produced to design, or the design is faulty…in either
case the manufacturer should be happy to receive your “bug report” and
either send you a correctly produced cable, or maybe they have already
changed the design and they will send a good one to you…

if they won’t do either you can let’em know which camera manufacturer
you will not be purchasing from in the future…

[am happy you solved the Black Ops Antenna mystery!]


dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255