Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - mixmax

#1
Other thoughts:

The reason I was somewhat nervously pulling cards in and out was that the camera apparently did not boot up after I changed cards and this (see p.7 in my steps) resonates with msg on ML fb page -
QuoteEric J. Russell
Yesterday at 1:55pm
Two Identical SDXC cards. One boots ML fine, the other puts my 700D in a brickatose state that can only be broken by ejecting the SD card and pulling the battery in and out, and even then the brickatosing SD card can't be in the slot or else the camera stays dead.
#2
Thanks, a1ex! Yes, this shutdown problem thread you're referring to pretty much describes my particular problem. Seems to be unlucky coincidence where card has been accessed and write happened without any visual indication at the very moment it was ejected.. I wish I've read it earlier...well, lesson learned the hard way :(

If there's any slight chance to recover contents of the SD card with camera - I'm in game, let me know here or via PM if other experiments needed.

Here are dmesg outputs for both cards
With normal 4Gb Kingston branded card I'm getting
[  401.948949] mmc0: new SDHC card at address 1234
[  401.968919] Driver 'mmcblk' needs updating - please use bus_type methods
[  401.969048] mmcblk0: mmc0:1234 SA04G 3.70 GiB
[  401.971195]  mmcblk0: p1
[  402.336852] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!


With corrupted 16Gb Transcend card (mixmax - AFAIU first 2 lines stll refer to previous card )

[  546.713246] mmc0: card 1234 removed
[  546.749369] FAT-fs (mmcblk0p1): unable to read boot sector to mark fs as dirty
[  554.570100] mmc0: card never left busy state
[  554.570110] mmc0: error -110 whilst initialising SD card
[  556.216025] mmc0: card never left busy state
[  556.216034] mmc0: error -110 whilst initialising SD card
[  557.861903] mmc0: card never left busy state
[  557.861914] mmc0: error -110 whilst initialising SD card
[  559.507737] mmc0: card never left busy state
[  559.507746] mmc0: error -110 whilst initialising SD card


+ with another healthy 8Gb Samsung card again
[  964.423396] mmc0: new SDHC card at address 0002
[  964.423777] mmcblk0: mmc0:0002 00000 7.41 GiB
[  964.425486]  mmcblk0: p1
[  964.777148] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!


+ with empty microSD-SD adapter, again first 2 lines can be ignored AFAIU
[ 1060.984609] mmc0: card 0002 removed
[ 1061.016661] FAT-fs (mmcblk0p1): unable to read boot sector to mark fs as dirty
[ 1153.950719] mmc0: card never left busy state
[ 1153.950729] mmc0: error -110 whilst initialising SD card
[ 1155.596602] mmc0: card never left busy state
[ 1155.596612] mmc0: error -110 whilst initialising SD card
[ 1157.242471] mmc0: card never left busy state
[ 1157.242483] mmc0: error -110 whilst initialising SD card
[ 1158.888373] mmc0: card never left busy state
[ 1158.888384] mmc0: error -110 whilst initialising SD card

- looks like the card is dead and some trick with low-level access via camera is the only chance...keeping fingers crossed

thanks!
#3
Quote from: Walter Schulz on June 17, 2016, 07:28:24 AM
ML enabled cams will access card *after* opening card slot. It doesn't matter if there is an ML enabled card inserted or a "dumb" one. And it doesn't matter if "Power switch" is in OFF position.
Your incident may be related to this access mimic or not. Always wait some time after opening card door before removing cards from ML cams.
:o
yes, that's most likely what happened. But I'm pretty sure the camera LED in the lower right was off. So if you're familiar with ML source code - is there any way to modify ML to provide a clear indication via LED flashing when there are I/O operations happening?
#4
hi all
I've been a long time ML user, but lately stumbled upon ML mention on the web and decided that I'll try new build with my T3i (aka D600) and ended up with unexpected problem.
Here are my steps:
1) dl-ed latest nightly
magiclantern-Nightly.2016Jun13.600D102.zip
Built on: 2016-06-12 20:59:14 -0400
Changeset: 90fe6de

2) formatted 4Gb card in the camera, made sure that the battery is fully charged
3) copied contents of the archive onto SD card on my laptop
4) put SD card back into camera, run firmware upgrade
5) ML installation screen appeared with green message about successful installation
6) I turned camera off, copied LOGS dir with ROMs onto my laptop, then put card back and turned camera on, it booted up into ML ok, I briefly checked settings once again - didn't change any settings except owner info string and shooting a picture for test
7) turned camera off, replaced SD card with another one (16Gb Transcend) - it is my main one, the card was previously formatted  in the camera and had some pics on it, I removed it and reviewed photos on my laptop just a moment before. Tried to boot the camera...here the problem starts, 'cause
8) NOTHING HAPPENS :( even red LED didn't blink... I pulled out battery and card, waited for a min, put back 1st SD with ML - it booted ok.
9) put back 2nd card - not a single sign of camera booting... battery trick again, 1st card, uninstalled ML via fw upgrade menu, turned camera off.
10) put back 2nd 16 gb card - red led lit up and after a few seconds (it looked like something was happening, took more time than usual) camera turned on, but card was not recognized. "Card cannot be accessed. Reinsert/change the card or format card with camera" message popped up.
I turned camera off, put card into laptop - but it can't recognize the card now too. Even on USB level no new devices appear when I plug it in :(

Now the 16Gb card is totally dead and to me it looks like that ML just killed my card somehow :(

Questions: any chance of reviving the card? Silly me didn't back up photos, never ever before I had an SD card died such out of a sudden ((( so any advice appreciated.
Any clues on what happened? Did the canon/modified bootloader when ML is installed look up parts of firmware on SD card and could it happen that it killed SD flash controller somehow?