Messages

Hi Irv,

Thank you for the reply and good thought. However, I actually have a grip with battery holder. So yeah, no effect. Plus, that part of the camera isn't running hot.

I've also found that the screen position impacts camera heat. It'll run cooler if you swivel it out away from the camera body.

2. OVERHEATING
I am having issues with overheating. Even just sitting and not filming, the readout went up to:  56c / 131F / 201 raw. I tried moving the LCD away from the body, but no effect. (And neither the LCD or area behind it was warm anyway.)

When I was filming tests for 12 minutes, the temp display went up to 62C and shown in red (at standard 1.0 Bitrate). Though there were no other warnings and the camera did not shut down. I have no idea if this was always a problem or not, as I never knew the temps before ML gave me the readouts just now.  So....how concerned should I be? What temperature (in Celsius since that is the only LCD display) should I be worried about?

I have noticed the SD card was very hot after the filming. Could that be the source?

In my experience, the battery contributes a lot to the heat. Get yourself a battery grip [$25(US) on Amazon] and the cam will run cooler and you can film longer, too.

Old guy who can't figure out how to add a comment. I've been using the 103 version since maybe June. No issues whatsoever. Shot a few thousand clicks and a little video.

I'm running a development version of ML 20180704 Nightly on Canon's v103 firmware. Been testing it for a few months with no issues. Wouldn't do without it.  :-)

Took the 600D to the stock car races last night. Battery consumption seemed very high. Might be be ML, might be my batteries, might be my imagination. Thought I'd report. Will check into it some, but will be slow. Life keeps getting in the way of leisure.

Got it, and thanks. Will see what it does later tonight.

Just returned from vacation. Shot about 1000 frames with 1.0.3. No issues noted.
There's a new build for 1.0.2. Any chance for one for 1.0.3, dfort?

I've shot some more with 1.0.3 with no issues. Specifically checked focus stacking and it works fine.

I've taken the camera on a couple brief outings, and ML seems to work as expected. Specifically, DualISO, ETTR, and focus blinkies are working fine. I'm not a video guy, so don't know enough to play with that. Will continue to experiment and report.

I have 1.0.3 and the test version of ML up and running. I'll walk around with it for a few days. Anything specific I should be looking for?

Mine reads just as yours, except:
Allocated RAM    589KB, peak 1.1MB
SRM job total    4x31MB

Log:
https://www.dropbox.com/s/8sl2qh333fa4yk8/DM-0002.LOG?dl=0

1 - Yes.
2 - I cannot boot to the startup-log ML. Three long and three short flashes. Have to remove battery and card to reset cam. Double-checked that the card is good, that I have the right build, and that I got a good download.

With the power switch off, 60D blinks the LED on any transition on the above variables (card door open/close, battery door open/close, lens mount/unmount), regardless of how you mix them and in what order. For example, removing the lens will produce a blink even if the battery and card doors are open.

600D is between these two; I don't know its exact behavior, but I'd expect it to be like 60D.

I can verify this. LED blinks in all these cases on the 600D.

I asked the same question (about kpartx) and a1ex came up with a good suggestion.

Thanks for the help, I'm trying it now.
Obviously I'm having real trouble with reading comprehension this week. :-(

Successfully complied qemu and discovered "next steps" 1-3 which I was too dull to see yesterday.

In step 3, mount.sh throws an error because it needs kpartx. So install kpartx. Then this:

Code Select Expand

Kernel not configured for semaphores (System V IPC). Not using udev synchronisation code.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper (unknown version) and kernel driver (unknown version).
device mapper prerequisites not met

What am I missing?

i tried also:
https://pastebin.com/YaCiuRFk
what does it look like when you run install and the commands it tells you to run?

I got it sorted. PEBCAK.   

did you run install.sh under magic-lantern/contrib/qemu ?

Yes.

Spoke too soon. Failed with this:

Code Select Expand

hw/arm/. ./eos/dbi/logging.o: In function 'eos_logging_ init':
/home/irv/qemu/qemu-2.5.0/hw/arm/. ./eos/dbi/logging.c:1801: undefined reference to 'memory_set_access_logging_cb'
target-arm/op_helper.o: In function 'helper_log_ldr':
/home/irv/qemu/qemu-2.5.0/tar get-arm/op_helper.c:634: undefined reference to 'log-ldr-cb'
target-arm/op_helper.o: In function 'helper_log_str':
/home/irv/qemu/qemu-2.5.O/tar et-arm/op_helper.c:639: undefined reference to 'log_srt-cb'
collect2: error: ld returned 1 exit status
Makefile:193: recipe for target 'qemu-system-aarch64' failed
make[1] *** [qemu-system-aarch64] Error 1
Makefile:184: recipe for target 'subdir-aarch64-softmu' failed
make: *** [subdir-aarch64-softnunu] Error 2
make: Leaving directory ' /home/irv/qemu/qemu—2.5.O'


As one with some Linux experience, no fear of the command line, and little compiling experience, my observations may be of value?

Starting with a clean Linux install on Win 10, I can get all the way to here with no problem:

Code Select Expand

qemu$ ./run_canon-fw.sh 600D
make: Entering directory '/home/irv/qemu/qemu-2.5.0'
Please call configure before running make!
Makefile:47: recipe for target 'config-host.mak' failed
make: *** [config-host.mak] Error 1
make: Leaving directory '/home/irv/qemu/qemu-2.5.0'


Then a cd qemu-2.5.0 and ./configure seem to sort things.

Did I miss something?

Compiling now.

From today's build:

016a0e5: Removed april fools prank

Thanks, A1ex.

Put it down. It scares newbies to death. I find ML so well done and so helpful that the AFP feels completely out of place.

Done.

I can verify that the experimental build boots successfully. Don't have time to test further tonight. Should the Features page be changed to indicate Lua as unavailable for the 600D until these get pushed?

Can anyone verify that lua loads successfully on the 600D? I get memory errors. Have tried a variety of nightlies back to 2016Apr22, and get the same behavior on all of them. More details later, if there is interest.