Did the May 2024 firmware update 2.1.1. solve your M11 freezing problems?

[DadDadDaddyo]

Advertisement (gone after registration)

ACLs: often pronounced "Ackels,"

Means "Access Control Lists," if I'm remembering those meetings correctly...

Excellent info - thanks!

Edited June 5, 2024 by DadDadDaddyo

[marchyman]

21 hours ago, lct said:

You mean switching write protection? Never done that in 20+ years of digital photo with any camera on any Mac so far.

Can't say I've never done it.  Pretty sure I can say I've only done it by accident and probably cussed a bit while I was pulling the card out and flipping the switch back to the writable position so I could use it the way I wanted.

Regarding this latest "bug".  Yeah, the camera should probably ignore supposed image files (ends in DNG) if the name starts with a dot.  It also could have made things less frustrating with a better error message. Something like "._11B05683. DNG is not an image file".  I'd have liked that.  It would be a reminder that my computer is writing stuff in the image folder of my card and maybe I shouldn't be doing whatever it is I'm doing that causes that.

[lct]

5 minutes ago, marchyman said:

Can't say I've never done it.  Pretty sure I can say I've only done it by accident and probably cussed a bit while I was pulling the card out and flipping the switch back to the writable position so I could use it the way I wanted.

Regarding this latest "bug".  Yeah, the camera should probably ignore supposed image files (ends in DNG) if the name starts with a dot.  It also could have made things less frustrating with a better error message. Something like "._11B05683. DNG is not an image file".  I'd have liked that.  It would be a reminder that my computer is writing stuff in the image folder of my card and maybe I shouldn't be doing whatever it is I'm doing that causes that.

I used to teach my students in law to never say never but again i've never seen the "bug" you're referring to so i won't comment on this point.

[Rollei35]

On 6/4/2024 at 5:12 PM, DadDadDaddyo said:

Very very interesting!

You can also see the OS has added a "@" to the left side of the row of each of the files that was previewed:

"-rwx------@"

R, W, and X - are these file attributes? Read, Write, etc?

Does Windows do something similar?

A little lesson on unix command,

rwx is for read, write, execution permission. Granted (a letter) or not granted (a dash -)

you see 3 groups, representing the owner, same group and out of the group permission.

the first dash denotes the file (-) or directory (d)

The last @ symbol represent this file has extended attribution, which I am not going to elaborate.

For above example, -rwx------@, means, this is a file, the owner has read write execution permission, same group users don't have any permission, users out of the group don't have any permission, and this file has extended attribution.

Edited June 6, 2024 by Rollei35

[58rbsj33m]

Great conversation here, thanks much to all of you!   
 

I have a newly purchased M11-P, built in April this year.  It arrived with firmware version 2.0.2, and I used an SD card to update it to v2.1.1.  Zero issues during the FW update, and zero issues afterwards.  The only thing I will note is the same as what others have mentioned:  Via FW update with SD card, it does take maybe 4 -5 minutes for the progress bar to get to the end of the update, and to see the final message that the firmware update was completed successfully (in green letters) — but the camera seems to still be writing something after seeing that message, because you can see that small LED blinking…. So, I just waited and didn’t do anything, but then when the camera stops writing, that blinking LED stops and there is a very brief delay, and the screen goes dark, then the camera automatically restarts.  At that point, I just manually switched the camera off, removed the battery and the SD card, then re-inserted the battery and manually switched the camera back on.  No worries:  Successful update to v2.1.1.  Then, I did a full reset of the camera, and haven’t experienced a single issue.  

Regarding that @ file attribute, it’s called a “sticky bit”.  Since MacOS is a POSIX operating system, or UNIX-like, that sticky bit is an extra file attribute which was set in the file, but it can very often get in the way of things you are trying to accomplish.  In my work, I have encountered those sticky bits, and have had to get rid of them on occasion, because they have prevented me from getting something done.  The following web page will help explain, and show how you can remove any sticky bit placed on your files, if needed,  
 

https://stackoverflow.com/questions/41290761/mac-osx-file-permissions-has-how-to-remove-that

I hope that helps some of you.

[dugby]

8 hours ago, 58rbsj33m said:

Great conversation here, thanks much to all of you!   
 

I have a newly purchased M11-P, built in April this year.  It arrived with firmware version 2.0.2, and I used an SD card to update it to v2.1.1.  Zero issues during the FW update, and zero issues afterwards.  The only thing I will note is the same as what others have mentioned:  Via FW update with SD card, it does take maybe 4 -5 minutes for the progress bar to get to the end of the update, and to see the final message that the firmware update was completed successfully (in green letters) — but the camera seems to still be writing something after seeing that message, because you can see that small LED blinking…. So, I just waited and didn’t do anything, but then when the camera stops writing, that blinking LED stops and there is a very brief delay, and the screen goes dark, then the camera automatically restarts.  At that point, I just manually switched the camera off, removed the battery and the SD card, then re-inserted the battery and manually switched the camera back on.  No worries:  Successful update to v2.1.1.  Then, I did a full reset of the camera, and haven’t experienced a single issue.  

Regarding that @ file attribute, it’s called a “sticky bit”.  Since MacOS is a POSIX operating system, or UNIX-like, that sticky bit is an extra file attribute which was set in the file, but it can very often get in the way of things you are trying to accomplish.  In my work, I have encountered those sticky bits, and have had to get rid of them on occasion, because they have prevented me from getting something done.  The following web page will help explain, and show how you can remove any sticky bit placed on your files, if needed,  
 

https://stackoverflow.com/questions/41290761/mac-osx-file-permissions-has-how-to-remove-that

I hope that helps some of you.

Fond memories-

Green screen / terminal

and chmod 777 *   used to be my old friend

 

I guess now-a-days ....   I'm considered a dino-boomer

[voln]

Advertisement (gone after registration)

I have Leican M11 Monochrome and  attached Visoflex. Today she was frozen when turned on. The firmware is the last 2.1.1.

I have a question - should the camera reset to the factory settings after the firmware process?

Edited June 7, 2024 by voln

[Edax]

31 minutes ago, voln said:

I have Leican M11 Monochrome and  attached Visoflex. Today she was frozen when turned on. The firmware is the last 2.1.1.

I have a question - should the camera reset to the factory settings after the firmware process?

Did you try to wake it up just by half-pressing the shutter button? It is a known issue that sometimes after switching on the camera with the main switch nothing seems to happen, and an additional half-press of the shutter button is needed to wake up the camera. It happens to me at least once a week, sometimes even once a day...

[hmzimelka]

22 hours ago, voln said:

I have Leican M11 Monochrome and  attached Visoflex. Today she was frozen when turned on. The firmware is the last 2.1.1.

I have a question - should the camera reset to the factory settings after the firmware process?

In my experience the contacts of the M11's hot-shoe can be very finicky. Attaching the Visoflex can make the camera act like it's attached, but the visoflex is dead black. I sometimes have months of not using the visoflex and whatever bit of dirt or corrosion happened makes my camera act a bit dead since it assumes the visoflex display is working but it isn't. Could this be the case with yours? Use some alcohol wipe and wipe off some contacts and see if that fixes anything. 

[ChrisFrick]

Freezing observed with v2.1.1 -- slightly different pattern (?)

On 25th of May 2024 I upgraded to v2.1.1 and first observed the freezing pattern again, as I was used to have with earlier versions (see my earlier posts of 25th of May 2024 etc.).  Then, after the hint of LocalHero1953, I formatted an SD card in the M11 with v2.1.1 and didn't experience any freeze any more -- up to today 😞:

Today was the first time I could go for a walk with the M11 again, and I had one freezing occurrence:  The M11 was in stand-by mode, I tried to wake it up by touching the shutter release button, I heard the sound of the opening shutter and saw the frame lines being illuminated, but then the red "Auto", which normally appears after a few moments during the wake-up procedure (when the M11 is set on Auto ISO, as was the case for my M11 today) did not appear, and the M11 didn't react to pressing the shutter button and to switching it off via the power switch.  What was different from earlier freezing experiences with earlier firmware versions:  As far as I remember, when I did observe freezings earlier when trying to wake up the M11 from stand-by, there was no reaction also from all the other buttons, like no reaction when pressing the "Play" button or pressing the "Menu" button.  Today, pressing "Play" looked normal, i.e. the M11 showed the last photo, pressing "Menu" also looked normal.  Only the shutter release button and the power switch were completely ignored by the M11 in this frozen state today.

To unfreeze it, I needed to take out the battery two times -- the freezing was still there after the first removal of the battery (this was the same when it was freezing before with earlier firmware versions).

So maybe the freezing happens much less frequent than with the earlier firmware, and the pattern might be slightly different, i.e., only freezing the shutter release button and the power switch, but not freezing other buttons like "Play" and "Menu"...?  Still, this is not good -- it feels unreliable; I would feed uncomfortable with the M11 if I would want to take photos at an important event (like at a wedding).  Of course I might try to avoid this kind of freezing by not letting the M11 go into stand-by mode at all, but then I would be worried that my two batteries would not be enough to cover the entire event.  (Battery life was never a concern with my M9s).

[_Alex_]

In response to voln's question: I would reset the camera to factory settings after every firmware update. It improved the performance of my M10-P (speed, responsiveness, etc.) which was exhibiting some quirks. I'd also put in a clean, formatted SD card. It just removes so many variables that it's worth it. And M cameras don't have so many options that reconfiguring to your liking takes very long. It's certainly nothing like resetting custom functions on, say, a Sony A7RV or Nikon Z9.

[marchyman]

On 6/7/2024 at 12:38 AM, voln said:

I have a question - should the camera reset to the factory settings after the firmware process?

I believe it depends upon the update.   Some cause a reset, others don't. I don't remember the 2.1.1 updating causing a reset.

[FlashGordonPhotography]

It would be nice if those still having issues would comment on whether they also reset the camera after the update. Seems, anecdotally that a reset seems to also help.

Gordon

[Derbyshire Man]

Without filling the SD card and multiple attachments to the computer to download without a reformat I have had an almost trouble free time other than switch on freeze x1. It's less problematic than a mid session freeze as clearly you've not started and haven't lost a series of shots. It's of course still not good enough however. Events such as this should be as rare as hens teeth. A lost opportunity is only slight less annoying than a lost shot.

[jgeenen]

I never had freezes with FW 1.6.1, 2.0.1 and 2.0.2, but FW 2.1.1 is very sensitive to actions during startup: if I turn on the camera and press any button or shutter release too early during startup sequence, the camera freezes occasionally requiring a battery cycle. 

[harmen]

On 6/1/2024 at 8:28 PM, harmen said:

Anyway, once the photos had downloaded, and while the app was still having a connection, I decided to format the card as I always do.  After a while the app told me it disconnected because the storage had changed.  However the camera never got out of formatting.  Removing the battery brought it back to normal.

I can perfectly repeat my camera freezing over and over.  And I’ve found out which factors help and do not help prevent it.  The camera will freeze when I decide to format the SD card in camera, after downloading photos to my iPad using wifi, while the camera is still connected to Leica Fotos.

• A full write-over format using sdformatter does not prevent the issue.
• A full reset of all camera settings and user profiles (and re-establishing its pairing with my iPad) does not prevent the issue.
• There is no freezing when I only use internal memory and don’t have an SD card in the camera.  I downloaded photos and then formatted the internal memory while still connected.  That also causes Fotos to tell me that the storage has changed, but importantly the camera does not freeze.
• There is also no freezing if I tell Fotos to disconnect before I format the SD card in camera.

I’m not sure if this is any way related to other freezes that other users experience in different circumstances, but at least it is one clearly pinpointed bug.  Would anyone care to try and repeat this?

Edited June 9, 2024 by harmen

[Aperture 2]

Hello, I have an M11P since a few weeks, I have updated to the FW 2.1.1 the day it went out. Today the camera freezed when it was taken out from sleep by pressing the shutter.

It was impossible to restart it with the ON/OFF, cycling the battery or changing the battery - I unblocked the situation only by taking out the SD card.

The files in the SD card are not corrupted and the card worked fine in my Mac, and also again in my M11P (I have reformatted again in the camera)

Card used SanDisk Extreme PRO SDXC 64 GB, after FW upgrade formatted with PC formater then formatted again in M11P, never taken out (transfer of pictures by cable)

Single shot, max resolution, DWG only, SD card only, no live view or EVF, no flash, battery at 80%, Leica Photos active (geolocation) in "performance mode"

As the problem seems to be linked to the SD Card I will shift to internal memory use only, I have also done a full reset and repairing with my iPhone.

I never had this kind of issues with my M9, M9, M9M, M10 nor my SL2, SL2-S or Q2M

I hope that the last bugs will soon be crushed....

PS: just happened again, but this time the camera was off. maybe I pressed the shutter too fast after the ON position ? - the SD card was still inside

Edited June 9, 2024 by Aperture 2

[geoffc60]

Is the card an UHS type 2?

[Aperture 2]

7 minutes ago, geoffc60 said:

Is the card an UHS type 2?

SanDIsk Exterme PRO 300 MB/s SDXC V90 3 C10

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

[Advertisement]

Hallo,

Look here: Interesting Leica gear

[geoffc60]

Looks like a type 2 from the pics