EOS 70D - Mode Dial problem...

Hi ... I'm Patricio from Argentina.
One week ago I received from the U.S. a Canon EOS 70D.
It worked ok until yesterday.
Since today, when I want to choose different modes with the dial mode, the camera just sets: P or A+ (auto).
- If I select A+ mode (Auto mode) or "Disabling Flash mode" or "Manual mode" .... the camera sets as A+ (Auto mode).
- If I select modes: CA, SCN, C, B, AV, TV, or P ... the camera sets as "P mode".
I have read some similar cases in other models of EOS cameras ... they recommen do a "hard reset" by removing the main battery and clock battery.
I tried to do that, but this model (EOS 70D) seems to have a battery for the date and clock ... but it is internal, It`s a rechargeable battery.
I guess as a new model, there is no more than the actual firmware, that comes from factory ... so I can`t try to update, since there is no other firmware available.
Anyone have any suggestions before taking it for service?
Thanks!
you can see what's wrong with my 70D here: (the mode selected by the dial, it's not the same on the screen)

Have you tried powering off the camera, removing the battery, waiting a minute, re-inserting the battery, and powering it back on?
The on/off switch is really puts the camera into an extended power-saving sleep mode. The camera still technically has power. When you turn on the camera again, the camera really just wakes up -- it does NOT actually re-start or reload the firmware.
If, however, you remove the batteries from the camera, you (mostly) deprive it of power. When you insert the battery and power it up it actually forces the camera to load the stored firmware again... you are in effect "rebooting" the camera when you do this -- the camera does not "reboot" simply by turning the power swtich off and on again.
I did say "mostly" deprive power when you remove the battery because there is a technicality. Depending on the camera body, most cameras have a 2nd battery used to store settings and also maintiain the date/time clock. That battery is either a removable coin size battery OR it's a built-in rechrageable battery which recharges off the regular battery. If you store the camera without a battery for too long, it will prompt you for the date & time when it powers up -- but this means the internal battery was depleted of power.
I *think* your 70D has an internal rechargeable battery. Simply leaving the batteries out over-night will not be enough. Hopefully just re-started the firmware by ejecting and re-inserting the main battery will be enough to fix the problem.
Tim Campbell
5D II, 5D III, 60Da

Similar Messages

EOS Rebel SL1 Mode Dial Problems

Hi, I don't know much about cameras, but I have always wanted a nice one like this and a friend of mine told me that the SL1 was good for beginners. It arrived in the mail today and I just started to experiment and play around with it. I don't know if it's something I did by mistake or it's just an issue with the camera, but I realized the Mode Dial is not programmed correctly. To elaborate if I were to spin the dial to the A+ symbol (I'm sorry if that's not what it's called), the camera will go to the sports function. I'm sorry, but I really do no understand this and I would love it if someone could help me. Thanks!

Hmmm.
On that camera the Sports mode is directly across from the A+ (Auto) mode position.  There is a little pip as the indicator on the camera on the left side of the dial.
Are you sure you are looking at the white pip and not the power on lever as the indicator?
If so, that is the problem.
If not:
Do ALL the modes register as the one directly across from the correct one, or are they all Sports or are they random or something?
The modes are printed on a thin metal "cap" that is literally glued on top of the knob.  I know because mine fell off once and I had to glue it back on.  I suppose it is possible that they put it on backwards at the factory, but I don't think so because there was a little slot in thge knob and a tab in the cap that have to line up or else you can't set the cap in flush.
If you are reading it right and the knob is wrong you need to return the camera.

Photoshop Elements 12 (PL) & Canon EOS 70D RAW problems

Photoshop Elements 12 (PL) & Canon EOS 70D RAW problems
Pomoc - uakltualnienia - brak dostępnych uaktualnień
wersja camera RAW - 8.0.0.137
not reading raw's from 70D

so, now after following the linked instructions...
1. I'v installed ACR 8.4 and it's opening the RAW files from 70D, but in camera profile I have "matrix"
in case with 60D RAWs ther was portrait, landscape, etc...
2. The step wit installing the DNG converter I download the DNG converter 7.4, 8.1, 8.2, 8.3. - the reason is to add in the system camera profile that I want
every one of them do not install - just nothing happen after doubleclick (!?)
only one that install and run it's 7.1 which dont support 70D RAW files....
it's amazing how to put all this to work propertly
any ideas?

EOS 70D is stuck on live view mode

I've only had my EOS 70D for two days, but I have taken a 5 hour online crash course on the camera. As of today, I can't get completely out of live mode when taking pictures. I can see out of my viewfinder, but for some reason, the live view area never goes away and stays on screen. Yesterday, it worked correctly, but no matter how many times I press the Start/Stop button now, the live view mode stays up on the screen. Help!

This was my question, but I actually figured it out on my own. I had changed my LCD off/on btn accidentally. It's working now.

LCD live viewing & copy work with EOS 70D (W)

Hi,
Can anyone please provide insight, guidance, solutions to accomplish this efficiently?
Goal/operation:
I want to use the camera for copy work: portfolio, flat art, photos, objects etc. I have old family photo albums I want to copy/photograph each image separately without removing/disturbing/damaging the images in the books.
The camera is mounted on a vertical copy stand shooting down (subject is mainly flat art).
I want to be able to view through the LCD in live view (camera is 90º facing down at copy board), have manual control, set up & align the subject and shoot the photos using the flash lighting system in quick efficient production process.
Equipment used:
Camera EOS 70D (W)
Minolta Copy stand
Novatron 240 portable light system, 2 lights with polarized sheet film
synch connections:
wireless - Pocket Wizard Plus 2 Transceiver.
wired - Nikon AS-15 Hot shot cord adapter
PROBLEM
I am having issues being able to view through the LCD, set up & align the subject and shoot the photos - without jumping through hoops.
It seems I have to switch to Av from M after shutter release to view subject in LCD, then switch back to M for the next shot, camera fails to shoot and shows error message: “Press start/stop button to activate movie shooting”. This doesn’t make sense as I’m not movie shooting.
If I change the mode to “Flash off” and back to “M” then it appears to work, however once I switch to Av mode to view the subject again, it starts the process all over.
There must be a better/easier way.
Could this be a potential bug in the camera? or am I missing something? I don’t see solutions in manual.
Will mode setting “C” Custom allow “Live viewing” w/ custom “Manual control” to bypass the need to use “M” manual setting that wont allow LCD viewing?
Camera settings:
Shooting with LCD (live view shooting)
mode setting:
Av - for live viewing and setup of subject
Then switch to M - Manual for manual control and shutter release
Also - I would like to connect to Apple Mac Laptop computer, live view on screen, and if possible have the option to record the photos direct to computer hard disk. Can this be done with this camera? IF so, what is needed?
Best regards,
J

-Canon 70D have built-in Wifi, so you can connect your camera with your computer wirelessly for tethered shooting. I have PC so the instruction may be different, but you need to install Canon EOS Utility.
-You can do everything in M mode even Live View. I think you are doing something wrong here, you may need to re-read your manual regarding this problem.
-C mode is customized M mode, so you can do everything in C mode also. With C mode, you can save all the setting so you can come back later. It's a great use in your case where you can make your C mode has all the settings for your work, then when you take the camera out to shoot something else, use other mode. Later, when you come back, just switch back to C so you don't have to change anything.
Weekend Travelers Blog | Eastern Sierra Fall Color Guide

EOS-70D Announcement and Preview

London, UK, 2 July 2013 – Canon today unveils an outstanding new addition to its world-famous EOS series – the EOS 70D. Designed for aspiring enthusiast photographers, the EOS 70D is the ideal camera for anyone looking to take their photography to the next level. It combines completely new, world-first Canon imaging technology with powerful, creative and wireless sharing features – delivering a responsive, all-purpose camera ideal for capturing the moment with stunning images and Full HD video.
Capture the moment with stills and Full HD movies
The EOS 70D features a new 20.2 MP APS-C CMOS sensor, designed and manufactured by Canon. It’s the first Digital SLR in the world to feature ground-breaking Dual Pixel CMOS AF technology, which delivers smooth and accurate autofocus (AF) when shooting Full HD movies and fast AF acquisition when shooting in Live View mode. Paired with the 14-bit DIGIC 5+ processor and 19-point all cross-type AF System, the EOS 70D captures incredible, full resolution images at up to 7 frames per second, with up to 65 JPEG or 16 RAW images in a single burst*. Additionally, a native ISO range of ISO 100-12800 enables photographers to shoot in lower light conditions and use faster shutter speeds whilst retaining high image quality.
“I was incredibly impressed with how many new technologies the EOS 70D packs into one body, and how versatile it is,” said Brutus Östling, Canon Ambassador. “The EOS 70D is the perfect camera for anyone that wants to develop their photography skills. Not only is it suited to shooting people, landscapes and action easily and in outstanding quality, but also filming subjects in Full HD with focus speeds I never thought would be possible. The camera proved itself in the most challenging of circumstances, and had a range of new-generation technologies to comfortably solve any test I threw at it – especially with the new Dual Pixel CMOS AF technology. It really takes DSLR shooting and filmmaking to a whole new level.”
Canon’s new Dual Pixel CMOS AF provides swift AF performance when shooting in Live View mode and smooth accurate focus for Full HD movies. It makes it easy for users to take their next step with movies, enabling them to keep moving subjects in sharp focus and create professional-looking pull-focus effects. The technology utilises advanced CMOS architecture, allowing two photodiodes to be mounted within each pixel, both of which can be read independently to achieve autofocus, or together for image capture, with maximum image quality at all times.
An advanced AF system for stills includes 19 cross-type AF points spread across the frame, providing high speed, accurate AF – ideal for tracking sports and wildlife subjects as they move within the frame. The AF system is customisable, allowing photographers to adapt to the subject they’re shooting. AF points can be used individually, together in small groups, or as a wide active area for more unpredictable subjects. A dedicated AF area selection button, positioned conveniently next to the shutter release, enables quick switching between modes, without having to take the camera away from the eye.
Expertly designed for professional control
The EOS 70D’s powerful specification is packed into an expertly-engineered body that’s designed for comfort and swift operation. The Intelligent Viewfinder, with 98 per cent frame coverage and 0.95x magnification, allows photographers to comfortably frame their images and visualise settings via the electronic overlay. Conveniently-placed controls provide instant access to the most frequently used settings, such as ISO, AF mode selection and metering, so users can quickly change settings and concentrate on capturing the moment.
A 7.7cm (3.0”) Vari-angle Clear View LCD II Touch screen with a sharp 1,040k dot resolution is ideal for video shooting, or composing images from unusual and creative angles. The screen is a capacitive type, which supports a series of multi-touch gestures including swiping and pinch-zooming – perfect for navigating menus, amending settings or flicking through images.
Clever connectivity for easy control and instant sharing
The EOS 70D is the latest EOS model to feature integrated Wi-Fi, providing the freedom to remotely control the camera, as well as share images. Using Wi-Fi connectivity, users can connect to the EOS Remote app and control a wide range of image settings, including ISO and exposure, as well as focus and release the shutter. Photographers can also remotely use Live View mode, as well as review and rate their images.
Instant creativity unleashed
The EOS 70D features a host of creative modes to make capturing unique images easy. In-camera HDR removes the challenges of shooting in tricky, high contrast situations, merging three exposures into one that captures more detail in both the shadow and highlight areas. With multiple-exposure mode, photographers can shoot and combine up to nine exposures into a single image, or use a range of Creative Filters to instantly change the style and look of their shot.
Experimenting with creative off-camera flash is easy, thanks to the Integrated Speedlite transmitter, which provides in-camera control of multiple Canon Speedlite EX flash units.
Creative Full HD Movies
Alongside beautiful stills, the EOS 70D allows photographers to create high quality movies with ease. Full HD (1920 x 1080p) resolution video can be captured with a choice of selectable frame rates, including 30, 25 or 24fps, and 60 and 50fps at 720p, and a range of compression options for post-editing and sharing. Thanks to new Dual Pixel CMOS AF, Movie Servo AF mode tracks subjects as they move, or even as shots are recomposed, ensuring they’re always in focus. Alternatively, users can select different focus areas over 80 per cent of the frame** simply by tapping the touch-screen, even when recording – ensuring that movies stay sharp and clear if a subject moves or the user changes the composition of a shot.
Videographers can also enjoy stereo sound using the internal microphone, or enhance audio with the in-built external microphone input terminal. Full control over settings such as aperture and ISO is also possible within manual mode, giving users greater freedom as their skills develop.
EOS 70D – key features:
20.2 megapixel APS-C CMOS sensor and DIGIC 5+
19 point cross-type AF System and 7 fps shooting
Dual Pixel CMOS AF
Instant sharing and remote control with Wi-Fi
ISO 12800 (H:25600)
Vari-angle 7.7cm ClearView II LCD touch screen
Intelligent viewfinder
Full-HD movies
UHS-I card required for maximum burst duration
Dual Pixel CMOS AF is possible over 80 per cent of the width and height of the Live View frame
MSRP $1,199 body ; $1,349 with 18-55mm IS STM ; $1,549 with 18-135mm IS STM
Pre-orders available now
Dual Pixel CMOS AF Explained
Short video on EOS-70D camera and its features
EOS-70D camera preview and sample photos
MichaelDanielHo.com

Thanks for your EOS-70D camera info and videos. When is the camera available in North America?

How open raw from canon eos 70D in elements 11

I cannot open raw from canon eos 70D in photoshop elements 11. Help me please.

Your PSE is too old—the camera was released after a newer version of software was available and Adobe only adds new camera support to the newest version of software.
Specifically, the 7D Mark II needs ACR 8.7 and PSE12 can only be updated to ACR 8.5.
Your choices are to:
Use the DNG Converter 8.7 or newer to create DNGs from the CR2s and those DNGs will open in the older version of ACR that comes with PSE12, OR
Buy the newer version of Element 13 that can be updated to a new enough Adobe Camera Raw plugin.
The DNG Converter is available from the Adobe Updates page:
http://www.adobe.com/downloads/updates
And the newer version of Elements is available from the Adobe Products page:
http://www.adobe.com/products/catalog/software.html
Another option would be to use Lightroom 5.7 or newer and use Edit in Photoshop Elements from LR once most of your raw adjustments are done, for any final touches in Elements.
For any of these choices you’d want to download the latest updates and run the software in trial mode to make sure your computer is compatible before paying anything.
BTW, I have the 7D Mark II and like it very much, having upgraded from an older Digital Rebel, but I’m not that thrilled with the in-camera JPG processing so always use Adobe products for raw development.

EOS 70D display screen not working because of humidity - Canon cutomer service totally unhelpful

Hi!
I have purchased an EOS 70D last October. Everything was working perfectly until I took it to the Caribbean, where on the second day the display screen stopped working. I could still take photos, but nothing was shown on the screen. I currently live in Canada. I took the camera to the store, where they told me that I have to send the camera (that still has warranty on it) at my own cost to the official repair centre. After a week, i got a letter from them, saying the following:
"We have received your equipment for evaluation and repair. Upon further examination it was determined that we are unable to repair your equipment therefore
Canon has suggested a replacement product to you in exchange for your original unit at the cost detailed below. Please respond to this estimate promptly to
avoid having your equipment returned.
We will replace your equipment with a EOS 70D. The new serial number is not yet available.
Upon inspection, technician found unit is beyond repair due to moisture damage. Estimate has been adjusted to reflect replacement suggestion."
I am furious. They are offering me to buy a new camera for the same price. I called customer service and asked them to explain the letter. They said they will send me photos of the inside of the camera, where they have found mositure. I asked them to re-check it, as I didn't misuse it, I didn't drop it in the water, or anything of that kind. They said the camera must have been used in a very humid/or very cold place. Can they be serious? Is that really my fault? I mean, I bought the camera to be able to take pictures anywhere I go. I didn't do anything extra to it or with it. I will take this as far as I can, I just don't find this a normal response. Any suggestions??? Anyone had the same problem before?

Every post ought to have a learning opportunity so I am attaching a list compiled by a Canon technical advisor addressing the problem of handling photographic equipment in hot weather.
Hot Weather Photo Equipment Handling Tips
Compiled by Chuck Westfall, Technical Advisor/Canon U.S.A., Inc.
1.) Avoid Condensation:
This is a biggie. If temperature and humidity differentials are high enough, condensation may occur when moving photo equipment from a relatively cool environment such as an air-conditioned vehicle, to a warmer one. When condensation forms inside a lens, for instance, internal elements can fog up, preventing clear images. When condensation gets bad enough inside a camera body, it can cause short circuits resulting in unexpected shutdowns. Worse yet, when equipment temperatures finally equalize to the warmer environment, water droplets on glass surfaces inside a lens may dry out and leave spots, mildew or fungus that can’t be cleaned by the photographer.
Similarly, when condensation dries up inside a camera, fungus, mildew, rust or corrosion may be left behind on printed circuit boards, viewfinder eyepieces, shutter curtains, or other internal components. If any of this happens, the equipment may be permanently damaged.
Incidentally, no matter how good it is, ‘weather sealing’ cannot prevent condensation, nor was it ever intended to do so. Damage caused by condensation is considered a user error, and it will void warranty coverage. One of the best methods to avoid condensation is to allow photo equipment to warm up gradually before exposing it to a hot environment. If this is not practical, consider placing the equipment in an airtight, resealable plastic bag with silica gel packets inside before exposing it to heat. (Don’t forget to squeeze as much air as possible out of the bag before you seal it, otherwise this technique may not work.) Using this method, the condensation will form on the bag instead of the equipment. Once the condensation on the bag has dried out, it should be safe to remove the equipment and start using it.
On a related matter, in hot and humid conditions, perspiration may cause condensation to form on your camera’s viewfinder eyepiece. Some camera manufacturers including Canon offer anti-fog eyepieces to prevent condensation from forming.
2.) What To Do When Condensation Has Occurred:
Use a soft, dry clean cloth to remove moisture from exterior surfaces. If possible, place the equipment in a dry, well-ventilated area to prevent further condensation from occurring.
3.) Cover Equipment When Not In Use:
If you must leave your camera equipment exposed to high heat and/or humidity conditions for long periods of time, consider covering it with a dry white towel when it’s not in use. Even when condensation is not an issue, heat absorption is another big concern for professional cameras and lenses, and especially digital SLRs. Cameras are designed to operate within a specific range of temperature and humidity conditions. For instance, the EOS-1D Mark IV professional camera has a high-end temperature rating of 45C/113F and a humidity rating of 85% or less. Since most camera bodies are black, internal temperatures can exceed this limit even when the ambient temperature is below it.
4.) Avoid or Limit the Use of Camera Settings that Generate Heat:
Heat build-up caused by ambient temperatures is one problem, but the other side of the coin is heat build-up caused by the camera itself. This has become more of an issue recently with professional digital SLRs due to the incorporation of new features such as Live View and HD video recording. These features generate heat from several camera components including battery packs, image sensors and LCD screens. If you plan on using Live View or recording video outdoors in high-temperature environments with your digital SLR, there are a couple of things you can do to minimize heat build-up inside the camera:
Limit the use of Live View for still shots. This will minimize heat build-up from the image sensor and LCD screen.
Use an external monitor when recording video. This will shut off the camera’s LCD screen.
Use an AC Adapter Kit. This will reduce heat build-up by eliminating battery packs.
Set the camera’s Auto Power Off setting to a reasonably short interval. Let the camera help to minimize heat build-up by allowing it to shut down automatically after a minute or two of inactivity. This will also conserve battery power.
5.) Storing Equipment in Hot Weather:
In high temperature environments with ambient humidity over 80%, use silica gel packets in your gadget bag or equipment case to absorb excessive moisture and protect your camera gear. Silica gel packets can be purchased in quantity from professional camera dealers and chemical supply houses, and are available in clear or moisture-indicating varieties. For long-term storage, consider storing camera equipment in Tupperware or similar sealable plastic containers with silica gel packets to absorb moisture and prevent fungus and mildew. In severely humid environments, even silica gel packets may be insufficient; so-called “camera dry cabinets” from manufacturers such as Toyo Living are available for such conditions. No matter what kind of storage container you use, ideally the humidity level should be less than 60% for maximum protection. Relatively inexpensive hygrometers of the type used for cigar thermidors are available to monitor humidity levels inside the containers. Remember to test hygrometers at least once a year, and recalibrate them if necessary.
6.) Store Battery Packs Separately and Keep Equipment Clean:
To prevent corrosion of your camera’s electrical contacts, remove battery packs prior to long-term storage. Also, as a matter of good housekeeping, clean cameras and lenses regularly and thoroughly. This is especially important in hot and humid weather, or after your camera equipment has been exposed to rain or condensation, to prevent mildew and fungus from forming.
© August, 2010 by Chuck Westfall
http://blog.photoshelter.com/2010/08/keeping-your-camera-gear-safe-in-the-heat/

Canon Battery Grip BG-E14 with the EOS 70D

Recently purchased the Canon BG-E14 battery grip to replace a third party battery grip for my new EOS 70D. The reason for replacing the third party grip with the more expensive Canon grip was a problem with using AA batteries with the third party product. At the time, I thought the reason the AA batteries were not working was because the grip was not a Canon product.
Turns out the Canon BG-E14 battery grip also does not work with AA batteries, but I not sure now if it's the grip or the camera causing the issue. I need to use AA batteries because of camping for long periods of time (no access to electricity) in remote areas. The battery indicator will show “Full” for about five minutes, then quickly go down to empty. The camera will shut down after about 6 minutes and if you keep turning the camera back on then you can continue shooting a few more pictures. I have use other Canon battery grips in the past with AA batteries with no issues, so again maybe the issue is with the new EOS 70D.
Does anyone have any knowledge on what could cause this issue of the AA batteries not working with the EOS 70D battery grip BG-E14? AND how is Canon fixing this issue (since this is an expensive Canon product that is not working as designed)?
Thanks,

Canon's rechargeables are Lithium Ion batteries. If you were to plot a graph of the power output from the battery as it is drained, you'd find that it provides a fairly steady voltage and then only drops at the very end when the battery is basically dead.
Non-rechargeable alkaline batteries don't behave like this. The voltage slowly drops as the battery drains and this may be fooling the camera into thinking it's got a dead battery (because the voltage doesn't normally drop on rechargeables until the very end.)
I use Sanyo Eneloop rechargeables and, if you're planning to take a huge pile of AA batteries camping, then I'd highly suggest that you specifically get the Eneloop brand. The Eneloops are "low self discharge". Most rechargeable batteries loose an astonishing amount of their charge within just 24 hours of being charged up -- simply through "self discharge". Eneloops are designed to not self-discharge. Sanyo claims that a charged Eneloops will still hold 90% of it's charge even after sitting on a shelf for 1 year after being charged.
I use Eneloops in all my speedlites. I normally just use the Canon batteries in my 5D III battery grip... but I through 6 Eneloops into the AA battery tray just as a test. I'll let you know how long it lasts (so far I've shot dozens of shots in the last 10 minutes and the battery power indicator still shows full as I would expect).
One other question... is the WiFi enabled on your 70D?
Tim Campbell
5D II, 5D III, 60Da

Canon Flash 430EX 11 to go with my Canon EOS 70D camera with an 18-135mm lens.

I purchased a Canon Flash 430EX 11 to go with my Canon EOS 70D camera with an 18-135mm lens. The flash displays the icon confirming auto zoom only intermittenly and when it doesn't, twisting the camera zoom does not display on the flash screen. All batteries are charged and the flash is locked on to the camera.
Solved!
Go to Solution.

I'm not entirely certain I understand your question. The 430EX II has can be put in a mode where it automatically follows the camera zoom (within limits... 24mm to 105mm) but you can ALSO put it into a mode where you manually control the flash zoom. If it's in the manual control mode then it will not automatically zoom.
It is important that the "wide" panel NOT be in-use (if you pull out and flip down the wide-panel then the flash will go to wide angle and will not zoom EVEN if it was in auto mode.)
Press the Zoom button, then use the - / + buttons to change the zoom.
When under manual control there's a black "M" icon which will appear next the word "Zoom". If the "M" is not present then it's in auto zoom mode.
Lastly... when you change the zoom on the camera lens, typically nothing will happen on the flash UNTIL you wake the system by doing a half-press of the shutter button. When the camera wakes up to meter and focus... that's when it adjusts the zoom on the flash head.
Tim Campbell
5D II, 5D III, 60Da

Photobooth live preview gives No-Signal (Canon EOS 70D)

I have a Canon 70D which is being used as a Photobooth. There is no software used. The Camera is connected to a LCD via HDMI for live view and the photos are clicked using a remote.
The connection is good over HDMI and the photos are being clicked too. The problem is loss of HDMI signal. After clicking 5-6 photos, the LCD signal goes off and comes back only if the photo is clicked again or if we press the live preview switch on the camera. Sometimes, the signal looses after single shot also.
I have checked the quality of the HDMI cable and it is very good. The camera and LCD are connected by Adapters and no battery is being used, so there is no chance of power being turned off.
Please let me know what is the solution for this.
Thanks,
Girish

Thanks for your EOS-70D camera info and videos. When is the camera available in North America?

EOS 70D Shutter Lag

Bought my EOS 70D a couple months ago and it has been working great until recently. Now, my shutter lag is a few seconds long. I've checked the drive mode and it is in single shutter mode, not self-timer (however, I have used the self-timer recently). I manually focus all of my pictures. HELP! The pictures are coming out blurry everytime and it's getting extremely frustrating.
Thanks,
Emily

Most likely it is in 2 sec timer mode or mirror lock up mode. Why are you using manual focus?
"A skill is developed through constant practice with a passion to improve, not bought."

EOS 70D weather sealed?

Does anyone know if the 70D will be weather sealed, I'm thinking of making the switch from Olympus E-3 to Canon but wanted a swing out display like the E-3. I shoot at the beach everyday and never had a problem with the E-3 and mist, wave splash or sand.
Solved!
Go to Solution.

Ok so I found this on DP reviews site.
Canon's spec sheet for the EOS 70D says it has water and dust resistance 'equivalent to the EOS-1N' - Canon's professional 35mm SLR in the mid-1990s. It's debatable how much this information will mean to most buyers, but the implication is that it shouldn't be fazed by a splash of rain. The diagram below gives an idea of how the body is sealed (courtesy of Canon EU).

Laptop mode tools problem with kernel 3.0

today I just updated the system and my laptop runs dramatically hotter after that. I read the archwiki, it does talk about the laptop mode tools problem with kernel 3.0 but when I opened the file /usr/sbin/laptop_mode, the lines which the wiki mentions are not there. Does anyone here have the same problem and can you offer the solution?
Here is my /usr/sbin/laptop_mode
#! /bin/sh
# Script to start or stop laptop_mode, and to control various settings of the
# kernel, hardware etc. that influence power consumption.
# This script is a part of Laptop Mode Tools. If you are running a supported
# power management daemon, this script will be automatically called on power
# state change.
# Configure laptop mode tools in /etc/laptop-mode/laptop-mode.conf, and in
# the broken-out config files in /etc/laptop-mode/conf.d.
# Please consult the manual pages laptop-mode.conf(8) and laptop_mode(8) for
# additional information.
# Maintainer: Ritesh Raj Sarraf ([email protected])
# Original Author: Bart Samwel ([email protected])
# Project home page: http://samwel.tk/laptop_mode
# Contributors to this script: Bart Samwel
# Kiko Piris
# Micha Feigin
# Andrew Morton
# Herve Eychenne
# Dax Kelson
# Jan Polacek
# ... and many others that I've stopped
# keeping track of.
# Based on a script for Linux 2.4 written by Jens Axboe.
set -a
# The laptop mode tools version number. Extracted by the installer makefile
# as well, so don't change the format!
LMTVERSION=1.59
# This script is loaded from multiple scripts to set the config defaults
# and to read the configuration on top of those. Only when the command is
# recognized does this script do anything else.
VERBOSE_OUTPUT=0
ENABLE_LAPTOP_MODE_ON_BATTERY=1
ENABLE_LAPTOP_MODE_ON_AC=0
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0
PARTITIONS="auto /dev/mapper/*"
LM_BATT_MAX_LOST_WORK_SECONDS=600
LM_AC_MAX_LOST_WORK_SECONDS=360
DEF_MAX_AGE=30
LM_READAHEAD=3072
NOLM_READAHEAD=128
CONTROL_READAHEAD=1
CONTROL_NOATIME=0
USE_RELATIME=1
CONTROL_HD_IDLE_TIMEOUT=1
LM_AC_HD_IDLE_TIMEOUT=4 # 20 seconds
LM_BATT_HD_IDLE_TIMEOUT=4 # 20 seconds
NOLM_HD_IDLE_TIMEOUT=244 # 2 hours
DEF_UPDATE=5
DEF_XFS_AGE_BUFFER=15
DEF_XFS_SYNC_INTERVAL=30
DEF_XFS_BUFD_INTERVAL=1
XFS_HZ=100
CONTROL_MOUNT_OPTIONS=1
BATT_HD_POWERMGMT=1
LM_AC_HD_POWERMGMT=254
NOLM_AC_HD_POWERMGMT=254
CONTROL_HD_POWERMGMT=0
CONTROL_HD_WRITECACHE=0
NOLM_AC_HD_WRITECACHE=1
NOLM_BATT_HD_WRITECACHE=0
LM_HD_WRITECACHE=0
LM_DIRTY_RATIO=60
LM_DIRTY_BACKGROUND_RATIO=1
NOLM_DIRTY_BACKGROUND_RATIO=10
NOLM_DIRTY_RATIO=40
LM_SECONDS_BEFORE_SYNC=2
BATT_CPU_MAXFREQ=medium
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=ondemand
NOLM_AC_CPU_IGNORE_NICE_LOAD=0
CONTROL_CPU_FREQUENCY=0
HD="/dev/[hs]d[abcdefgh]"
CONTROL_SYSLOG_CONF=0
LM_AC_SYSLOG_CONF=/etc/syslog-on-ac-with-lm.conf
NOLM_AC_SYSLOG_CONF=/etc/syslog-on-ac-without-lm.conf
BATT_SYSLOG_CONF=/etc/syslog-on-battery.conf
SYSLOG_CONF_SIGNAL_PROGRAM=syslogd
SYSLOG_CONF=/etc/syslog.conf
CONTROL_DPMS_STANDBY=0
BATT_DPMS_STANDBY=300
LM_AC_DPMS_STANDBY=1200
NOLM_AC_DPMS_STANDBY=1200
CONTROL_CPU_THROTTLING=0
BATT_CPU_THROTTLING=medium
LM_AC_CPU_THROTTLING=minimum
NOLM_AC_CPU_THROTTLING=minimum
CONTROL_START_STOP=1
CONTROL_TERMINAL=0
TERMINALS="/dev/vc/1 /dev/vcs1"
BATT_TERMINAL_BLANK_MINUTES=1
BATT_TERMINAL_POWERDOWN_MINUTES=2
LM_AC_TERMINAL_BLANK_MINUTES=10
LM_AC_TERMINAL_POWERDOWN_MINUTES=10
NOLM_AC_TERMINAL_BLANK_MINUTES=10
NOLM_AC_TERMINAL_POWERDOWN_MINUTES=50
ENABLE_AUTO_HIBERNATION=0
HIBERNATE_COMMAND=/usr/sbin/hibernate
AUTO_HIBERNATION_ON_CRITICAL_BATTERY_LEVEL=1
DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
AUTO_HIBERNATION_BATTERY_CHARGE_MAH=0
AUTO_HIBERNATION_BATTERY_CHARGE_MWH=0
MINIMUM_BATTERY_CHARGE_MAH=0
MINIMUM_BATTERY_CHARGE_MWH=0
ASSUME_SCSI_IS_SATA=1
CONTROL_BRIGHTNESS=0
BATT_BRIGHTNESS_COMMAND=false
LM_AC_BRIGHTNESS_COMMAND=false
NOLM_AC_BRIGHTNESS_COMMAND=false
LOG_TO_SYSLOG=1
DEBUG=0
ENABLE_LAPTOP_MODE_TOOLS=1
# Initialize the PATH Variable
export PATH="${PATH}":/bin:/sbin:/usr/bin:/usr/sbin
# This is a 2 phase locking approach. LMT_REQ_LOCK is the outer lock and LMT_INVOC_LOCK is the inner lock
# We take this approach to ensure the scenario that, "At any point when an event occurs (AC/BATT), the
# kernel can generate multiple events spanning over a couple of events. The first event is honored and
# lmt executes. If the last event triggered at the 9th second, there is a fair chance that a good amount
# of state change would have occured in the OS, to honor that state, we keep an outer lock (LMT_REQ_LOCK)
# handy, so that those changes can also be applied and not forgotten.
# Workflow:
# Event-1 is generated and lmt executes (lmt runtime could span 5-10 seconds)
# At seventh second, 4 events generate. But Event-1 is still running.
# We don't want to discard all the remaining 4 events, but at least honor 1 so that we can act to the changes
# that occured in the last 7 seconds.
# So, Event-2 acquire LMT_REQ_LOCK and waits to acquire LMT_INVOC_LOCK (which is acquire by Event-1)
LMT_REQ_LOCK="/var/lock/lmt-req.lock"
LMT_INVOC_LOCK="/var/lock/lmt-invoc.lock"
FLOCK=`which flock`
checkint ()
# $1 arg should be the string/integer
# that you want to check for as an integer.
echo $1 | grep "[^0-9]" > /dev/null 2>&1
return $?;
# Returns 1 if it is an integer
# Function to handle logging
LOGGER=`which logger`;
log ()
# $1 should be msg type
# $2 should be the real msg
if [ x$LOG_TO_SYSLOG = x1 ]; then
# NOTE: Add the check on $2 being empty, once you are confident
# that there aren't any bugs in logging. And no bugs in executing
# modules and logging
if [ -x $LOGGER -a "$1" != "STATUS" ]; then
#if [ -z $2 ]; then
# continue
#elif [ "$1" = "MSG" ]; then
if [ "$1" = "MSG" ]; then
logger -p daemon.info -t laptop-mode "$2";
elif [ "$1" = "ERR" ]; then
logger -p daemon.err -t laptop-mode "$2";
elif [ "$1" = "VERBOSE" ]; then
if [ x$VERBOSE_OUTPUT = x1 ]; then
logger -p daemon.debug -t laptop-mode "$2";
fi
else
logger -p daemon.notice -t laptop-mode "$2";
fi
fi
fi
if [ "$1" = "VERBOSE" ]; then
$LM_VERBOSE && echo "$2" >/dev/fd/2;
elif [ "$1" = "ERR" ]; then
echo "$2" >/dev/fd/2;
else
# Message of type MSG and STATUS can go to stdout.
echo "$2" >/dev/fd/1;
fi
enableDebug ()
# Check if debug is enabled
if [ x$(($(basename $1 | cut -d . -f1 | tr "[:lower:]" "[:upper:]" | sed 's/-/_/g')_DEBUG)) = x1 ]; then
set -vx
fi
disableDebug ()
# Check if debug is enabled
if [ x$(($(basename $1 | cut -d . -f1 | tr "[:lower:]" "[:upper:]" | sed 's/-/_/g')_DEBUG)) = x1 ]; then
set +vx
fi
# No default on these ones -- we need to detect if they have been set, for
# backward compatibility with MINIMUM_BATTERY_MINUTES etc.
AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT=
MINIMUM_BATTERY_CHARGE_PERCENT=
# Backward compatibility variable that is sometimes
# set externally (Debian init system)
unset VERBOSE
lmt_load_config ()
# Source config. Some config settings have been moved from the main config file
# to modular configuration files, and to support existing laptop-mode.conf
# files from earlier versions, we source the modular configuration files FIRST.
if [ -d /etc/laptop-mode/conf.d ] ; then
for CONF in /etc/laptop-mode/conf.d/*.conf ; do
if [ -r "$CONF" ] ; then
. "$CONF"
#Handle individual module debug settings
if [ "$DEBUG" -eq 1 ]; then
export $(basename $CONF | cut -d . -f1 | tr "[:lower:]" "[:upper:]" | sed 's/-/_/g')_DEBUG=1
log "VERBOSE" "Enabling debug mode for module $CONF"
fi
DEBUG=0
else
log "MSG" "Warning: Configuration file $CONF is not readable, skipping."
fi
done
fi
if [ -r /etc/laptop-mode/laptop-mode.conf ] ; then
. /etc/laptop-mode/laptop-mode.conf
else
log "ERR" "$0: Configuration file /etc/laptop-mode/laptop-mode.conf not present or not readable."
exit 1
fi
if [ x$ENABLE_LAPTOP_MODE_TOOLS = x0 ]; then
log "MSG" "laptop-mode-tools is disabled in config file. Exiting"
exit 0;
fi
# Add a simple bash debug mode switch
if [ "$DEBUG" -eq 1 ]; then
set -vx;
fi
# Support for old config settings
if [ "$AC_HD" != "" ] ; then
AC_HD_WITHOUT_LM="$AC_HD"
AC_HD_WITH_LM="$AC_HD"
fi
if [ "$VERBOSE" != "" ] ; then
VERBOSE_OUTPUT="$VERBOSE"
fi
if [ "$CPU_MAXFREQ" != "" ] ; then
BATT_CPU_MAXFREQ="$CPU_MAXFREQ"
fi
if [ "$MAX_AGE" != "" ] ; then
LM_BATT_MAX_LOST_WORK_SECONDS="$MAX_AGE"
LM_AC_MAX_LOST_WORK_SECONDS="$MAX_AGE"
fi
if [ "$DEF_AGE" != "" ] ; then
DEF_MAX_AGE="$DEF_AGE"
fi
if [ "$LAPTOP_MODE_ALWAYS_ON" != "" ] ; then
ENABLE_LAPTOP_MODE_ALWAYS="$LAPTOP_MODE_ALWAYS_ON"
fi
if [ "$LM_WHEN_LID_CLOSED" != "" ] ; then
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED="$LM_WHEN_LID_CLOSED"
fi
if [ "$REMOUNT_PARTITIONS" != "" ] ; then
PARTITIONS="$REMOUNT_PARTITIONS"
fi
if [ "$READAHEAD" != "" ] ; then
LM_READAHEAD="$READAHEAD"
fi
if [ "$DO_REMOUNT_NOATIME" != "" ] ; then
CONTROL_NOATIME="$DO_REMOUNT_NOATIME"
fi
if [ "$DO_HD" != "" ] ; then
CONTROL_HD_IDLE_TIMEOUT="$DO_HD"
fi
if [ "$AC_HD_WITH_LM" != "" ] ; then
LM_AC_HD_IDLE_TIMEOUT="$AC_HD_WITH_LM"
fi
if [ "$AC_HD_WITHOUT_LM" != "" ] ; then
NOLM_HD_IDLE_TIMEOUT="$AC_HD_WITHOUT_LM"
fi
if [ "$BATT_HD" != "" ] ; then
LM_BATT_HD_IDLE_TIMEOUT="$BATT_HD"
fi
if [ "$DO_REMOUNTS" != "" ] ; then
CONTROL_MOUNT_OPTIONS="$DO_REMOUNTS"
fi
if [ "$DO_HD_POWERMGMT" != "" ] ; then
CONTROL_HD_POWERMGMT="$DO_HD_POWERMGMT"
fi
if [ "$AC_HDPARM_POWERMGMT_WITH_LM" != "" ] ; then
LM_AC_HD_POWERMGMT="$AC_HDPARM_POWERMGMT_WITH_LM"
fi
if [ "$AC_HDPARM_POWERMGMT_WITHOUT_LM" != "" ] ; then
NOLM_AC_HD_POWERMGMT="$AC_HDPARM_POWERMGMT_WITHOUT_LM"
fi
if [ "$BATT_HDPARM_POWERMGMT" != "" ] ; then
BATT_HD_POWERMGMT="$BATT_HDPARM_POWERMGMT"
fi
if [ "$DO_WRITECACHE" != "" ] ; then
CONTROL_HD_WRITECACHE="$DO_WRITECACHE"
fi
if [ "$AC_WRITECACHE_WITHOUT_LM" != "" ] ; then
NOLM_AC_HD_WRITECACHE="$AC_WRITECACHE_WITHOUT_LM"
fi
if [ "$BATT_WRITECACHE" != "" ] ; then
LM_HD_WRITECACHE="$BATT_WRITECACHE"
fi
if [ "$DIRTY_RATIO" != "" ]; then
LM_DIRTY_RATIO="$DIRTY_RATIO"
fi
if [ "$DIRTY_BACKGROUND_RATIO" != "" ] ; then
LM_DIRTY_BACKGROUND_RATIO="$DIRTY_BACKGROUND_RATIO"
fi
if [ "$DEF_DIRTY_RATIO" != "" ]; then
NOLM_DIRTY_RATIO="$DEF_DIRTY_RATIO"
fi
if [ "$DEF_DIRTY_BACKGROUND_RATIO" != "" ] ; then
NOLM_DIRTY_BACKGROUND_RATIO="$DEF_DIRTY_BACKGROUND_RATIO"
fi
if [ "$DO_CPU" != "" ] ; then
CONTROL_CPU_FREQUENCY="$DO_CPU"
fi
if [ "$CONTROL_CPU_MAXFREQ" != "" ] ; then
CONTROL_CPU_FREQUENCY="$CONTROL_CPU_MAXFREQ"
fi
if [ "$AC_CPU_MAXFREQ_WITH_LM" != "" ] ; then
LM_AC_CPU_MAXFREQ="$AC_CPU_MAXFREQ_WITH_LM"
fi
if [ "$AC_CPU_MAXFREQ_WITHOUT_LM" != "" ] ; then
NOLM_AC_CPU_MAXFREQ="$AC_CPU_MAXFREQ_WITHOUT_LM"
fi
if [ "$DO_SYSLOG" != "" ] ; then
CONTROL_SYSLOG_CONF="$DO_SYSLOG"
fi
if [ "$SYSLOG_SIGNAL_PROGRAM" != "" ] ;then
SYSLOG_CONF_SIGNAL_PROGRAM="$SYSLOG_SIGNAL_PROGRAM"
fi
if [ "$AC_SYSLOG_WITH_LM" != "" ] ; then
LM_AC_SYSLOG_CONF="$AC_SYSLOG_WITH_LM"
fi
if [ "$AC_SYSLOG_WITHOUT_LM" != "" ] ; then
NOLM_AC_SYSLOG_CONF="$AC_SYSLOG_WITHOUT_LM"
fi
if [ "$BATT_SYSLOG" != "" ] ; then
BATT_SYSLOG_CONF="$BATT_SYSLOG"
fi
if [ "$ENABLE_LAPTOP_MODE_ALWAYS" != "" ] ; then
ENABLE_LAPTOP_MODE_ON_AC="$ENABLE_LAPTOP_MODE_ALWAYS"
fi
if [ "$MINIMUM_BATTERY_MINUTES" != "" -a "$MINIMUM_BATTERY_CHARGE_PERCENT" = "" ] ; then
# Use a very conservative estimate (1% = 1 battery minute, 100 minutes in a battery)
# for backward compatibility.
MINIMUM_BATTERY_CHARGE_PERCENT="$MINIMUM_BATTERY_MINUTES"
fi
if [ -z "$MINIMUM_BATTERY_CHARGE_PERCENT" ] ; then
# Apply the default, now that we've determined that this is the minimum.
MINIMUM_BATTERY_CHARGE_PERCENT=3
fi
if [ "$AUTO_HIBERNATION_BATTERY_MINUTES" != "" -a "$AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT" = "" ] ; then
# Use a very conservative estimate (1% = 1 battery minute, 100 minutes in a battery)
# for backward compatibility.
AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT="$AUTO_HIBERNATION_BATTERY_MINUTES"
fi
if [ -z "$AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT" ] ; then
# Apply the default, now that we've determined that this is the minimum.
AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT=2
fi
# Postprocessing
if [ "$VERBOSE_OUTPUT" -ne 0 ] ; then
OUTPUT="/dev/stdout"
LM_VERBOSE="[ 1 = 1 ]"
else
OUTPUT="/dev/null"
LM_VERBOSE="[ 1 = 0 ]"
fi
if [ "$PARTITIONS" = "" ] ; then
PARTITIONS="auto /dev/mapper/*"
fi
# Expand shell wild cards immediately.
PARTITIONS=$( echo $PARTITIONS )
TERMINALS=$( echo $TERMINALS )
# Convert seconds to hdparm -S format
# Everything over 20 minutes is interpreted as 2 hours.
seconds_to_hdparm_S() {
if [ "$1" -eq 0 ] ; then
# disable.
echo 0
elif [ "$1" -gt 0 -a "$1" -lt 5 ] ; then
# 5 seconds minimum
echo 1
elif [ "$1" -le $((240*5)) ] ; then
# Values between 1 and 240 signify increments of 5 seconds
echo $(($1 / 5))
elif [ "$1" -lt $((30*60)) ] ; then
# Values between 20 and 30 minutes are rounded up to 30 minutes.
echo 241
elif [ "$1" -lt $((12*30*60)) ] ; then
# Values between 30 minutes and 6 hours (exclusive) yield values between
# 241 and 251, in 30-minute increments.
echo $(( 240 + ($1 / (30*60)) ))
else
# Larger values effectively indicate no timeout at all.
echo 0
fi
# Convert configured idle timeouts to hdparm -S format.
if [ "$LM_AC_HD_IDLE_TIMEOUT_SECONDS" != "" ] ; then
LM_AC_HD_IDLE_TIMEOUT=$(seconds_to_hdparm_S $LM_AC_HD_IDLE_TIMEOUT_SECONDS)
fi
if [ "$LM_BATT_HD_IDLE_TIMEOUT_SECONDS" != "" ] ; then
LM_BATT_HD_IDLE_TIMEOUT=$(seconds_to_hdparm_S $LM_BATT_HD_IDLE_TIMEOUT_SECONDS)
fi
if [ "$NOLM_HD_IDLE_TIMEOUT_SECONDS" != "" ] ; then
NOLM_HD_IDLE_TIMEOUT=$(seconds_to_hdparm_S $NOLM_HD_IDLE_TIMEOUT_SECONDS)
fi
# The main workhorse.
lmt_main_function ()
if [ "$1" = "status" ] ; then
# Display a status report.
log "STATUS" "Mounts:"
mount | sed "s/^/ /"
log "STATUS" " "
log "STATUS" "Drive power status:"
for disk in $HD; do
if [ -r $disk ]; then
hdparm -C $disk 2>/dev/null | sed "s/^/ /"
else
log "STATUS" " Cannot read $disk, permission denied - $0 needs to be run as root"
fi
done
log "STATUS" " "
log "STATUS" "(NOTE: drive settings affected by Laptop Mode cannot be retrieved.)"
log "STATUS" " "
log "STATUS" "Readahead states:"
cat /etc/mtab | while read DEV MP FST OPTS DUMP PASS ; do
# skip funny stuff
case "$FST" in
rootfs|unionfs|tmpfs|squashfs|sysfs|usbfs|proc|devpts) continue
esac
if [ -b $DEV ] ; then
if [ -r $DEV ] ; then
log "STATUS" " $DEV: $((`blockdev --getra $DEV` / 2)) kB"
else
log "STATUS" " Cannot read $DEV, permission denied - $0 needs to be run as root"
fi
fi
done
log "STATUS" " "
if [ -e /var/run/laptop-mode-tools/enabled ] ; then
log "STATUS" "Laptop Mode Tools is allowed to run: /var/run/laptop-mode-tools/enabled exists."
else
log "STATUS" "Laptop Mode Tools is NOT allowed to run: /var/run/laptop-mode-tools/enabled does not exist."
fi
log "STATUS" " "
STATFILES="/proc/sys/vm/laptop_mode /proc/apm /proc/pmu/info /proc/sys/vm/bdflush /proc/sys/vm/dirty_ratio /proc/sys/fs/xfs/age_buffer /proc/sys/fs/xfs/sync_interval /proc/sys/fs/xfs/lm_age_buffer /proc/sys/fs/xfs/lm_sync_interval /proc/sys/vm/pagebuf/lm_flush_age /proc/sys/fs/xfs/xfsbufd_centisecs /proc/sys/fs/xfs/xfssyncd_centisecs /proc/sys/vm/dirty_background_ratio /proc/sys/vm/dirty_expire_centisecs /proc/sys/fs/xfs/age_buffer/centisecs /proc/sys/vm/dirty_writeback_centisecs /sys/devices/system/cpu/*/cpufreq/cpuinfo_*_freq /sys/devices/system/cpu/*/cpufreq/scaling_governor /proc/acpi/button/lid/*/state /proc/acpi/ac_adapter/*/state /proc/acpi/battery/*/state /sys/class/power_supply/*/online /sys/class/power_supply/*/state"
for THISFILE in $STATFILES ; do
if [ -e "$THISFILE" ] ; then
log "STATUS" "$THISFILE:"
if [ -r "$THISFILE" ] ; then
cat "$THISFILE" | sed "s/^/ /"
else
log "STATUS" " Not accessible, permission denied - $0 needs to be run as root."
fi
log "STATUS" " "
fi
done
elif [ "$1" != "readconfig" -a "$1" != "defaults" ] ; then
KLEVEL="$(uname -r |
IFS='.-' read a b c
echo $a.$b
KMINOR="$(uname -r |
IFS='.-' read a b c d
# Strip any stuff from the end -- only the initial digits are part of the KMINOR.
echo $c | sed -e 's/$[[:digit:]]*$.*/\1/'
# Stop exporting everything -- what we do from here is private.
set +a
if [ "$1" = "--version" ] ; then
log "MSG" "Laptop Mode Tools $LMTVERSION"
exit 0
fi
if [ ! -e /proc/sys/vm/laptop_mode ] ; then
log "ERR" "Kernel does not have support for laptop mode. Please apply the laptop mode"
log "ERR" "patch or install a newer kernel."
exit 1
fi
if [ ! -w /proc/sys/vm/laptop_mode ] ; then
log "ERR" "You do not have enough privileges to enable laptop_mode."
exit 1
fi
INIT=0 # Display info in init script format?
FORCE=0 # Force reapplying the current state?
while [ "$1" != "" ] ; do
case "$1" in
init) INIT=1 ;;
force) FORCE=1 ;;
# Old options. We always do "auto" for any option now, but
# we still have to accept the options.
start) ;;
stop) ;;
auto) ;;
modules=*)
MODULES=$1
MODULES=${MODULES#"modules="}
devices=*)
DEVICES=$1
DEVICES=${DEVICES#"devices="}
*) log "ERR" "Unrecognized option $1."
exit 1 ;;
esac
shift
done
mkdir -p /var/run/laptop-mode-tools
# Used to display laptop mode state later on. This is the enabled/disabled
# state for laptop mode processing, it tells us nothing about whether laptop
# mode is actually _active_.
STATE=enabled
if [ "$ENABLE_LAPTOP_MODE_ON_BATTERY" -eq 0 -a "$ENABLE_LAPTOP_MODE_ON_AC" -eq 0 -a "$ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED" -eq 0 ] ; then
STATE=disabled
fi
# Determine the power state.
# First try /sys/class/power_supply/*
FOUND_SYS_CLASS_POWER_SUPPLY_AC=0
ON_AC=0
for POWER_SUPPLY in /sys/class/power_supply/* ; do
if [ -f $POWER_SUPPLY/type ] ; then
if [ "$(cat $POWER_SUPPLY/type)" = "Mains" ] ;then
log "VERBOSE" "Determining power state from $POWER_SUPPLY/online."
FOUND_SYS_CLASS_POWER_SUPPLY_AC=1
if [ "$(cat $POWER_SUPPLY/online)" = 1 ] ; then
ON_AC=1
fi
fi
fi
done
if [ $FOUND_SYS_CLASS_POWER_SUPPLY_AC = 1 ] ; then
# Already found it!
log "VERBOSE" "Not trying other options, already found a power supply."
elif [ -d /proc/acpi/ac_adapter ] ; then
log "VERBOSE" "Determining power state from /proc/acpi/ac_adapter."
ADAPTERS_FOUND=0
ON_AC=0
for ADAPTER in /proc/acpi/ac_adapter/* ; do
if [ -f $ADAPTER/state ] ; then
ADAPTERS_FOUND=1
STATUS=`awk '/^state: / { print $2 }' $ADAPTER/state`
if [ "$STATUS" = "on-line" ] ; then
ON_AC=1
fi
fi
done
if [ "$ADAPTERS_FOUND" -eq 0 ] ; then
ON_AC=1
fi
elif [ -f /proc/pmu/info ] ; then
log "VERBOSE" "Determining power state from /proc/pmu/info."
if ( grep -q "^AC Power.*0$" /proc/pmu/info ) ; then
log "VERBOSE" "/proc/pmu/info indicates absence of AC power."
ON_AC=0
else
# It is possible that there is no AC Power = 1 in the file,
# but we always assume AC power when we're not sure.
ON_AC=1
log "VERBOSE" "/proc/pmu/info indicates presence of AC power."
fi
elif [ -f /proc/apm ] ; then
log "VERBOSE" "Determining power state from /proc/apm."
read D1 D2 D3 APM_AC_STATE D0 </proc/apm
if [ "$APM_AC_STATE" = "0x00" ] ; then
ON_AC=0
else
ON_AC=1
fi
else
log "VERBOSE" "No /sys/class/power_supply, ACPI, APM or PMU power management information found -- assuming AC power is present."
ON_AC=1
fi
# Determine whether to activate or deactivate laptop mode.
ACTIVATE=0
if [ "$ON_AC" -eq 1 ] ; then
if [ "$ENABLE_LAPTOP_MODE_ON_AC" -ne 0 ] ; then
log "VERBOSE" "On AC power: Activating, because ENABLE_LAPTOP_MODE_ON_AC is set."
ACTIVATE=1
else
log "VERBOSE" "On AC power: Deactivating, because ENABLE_LAPTOP_MODE_ON_AC is not set."
ACTIVATE=0
fi
else
if [ "$ENABLE_LAPTOP_MODE_ON_BATTERY" -ne 0 ] ; then
log "VERBOSE" "On battery power: Activating, because ENABLE_LAPTOP_MODE_ON_BATTERY is set."
ACTIVATE=1
else
log "VERBOSE" "On battery power: Deactivating, because ENABLE_LAPTOP_MODE_ON_BATTERY is not set."
ACTIVATE=0
fi
fi
if [ "$ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED" -ne 0 -a "$ACTIVATE" -eq 0 ] ; then
if [ -x "`which hal-find-by-property`" ] ; then
HAL_LID_BUTTON=$(hal-find-by-property --key "button.type" --string "lid")
fi
if [ "$HAL_LID_BUTTON" != "" ] ; then
HAL_LID_BUTTON_STATE=$(hal-get-property --udi $(hal-find-by-property --key "button.type" --string "lid") --key "button.state.value")
if [ "$HAL_LID_BUTTON_STATE" = "true" ] ; then
log "VERBOSE" "Setting action to \"start\" because the lid is closed (says HAL)."
ACTIVATE=1
fi
elif [ -f /proc/acpi/button/lid/*/state ] ; then
if ( grep -q "closed" /proc/acpi/button/lid/*/state ) ; then
log "VERBOSE" 'Setting action to "start" because the lid is closed (says /proc/acpi/button/lid/*/state).'
ACTIVATE=1
fi
else
log "MSG" "Warning: ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED is set, but there is no file"
log "MSG" "/proc/acpi/button/lid/.../state, and hal information is not available either!"
fi
fi
# If the init script has not been run or has been run with the "stop"
# argument, then we should never start laptop mode.
if [ ! -f /var/run/laptop-mode-tools/enabled ] ; then
log "VERBOSE" "Laptop mode disabled because /var/run/laptop-mode-tools/enabled is missing."
STATE=disabled
fi
if [ "$ACTIVATE" -eq 1 -a -f /etc/default/laptop-mode ] ; then
. /etc/default/laptop-mode
if ! ( echo "$ENABLE_LAPTOP_MODE" |grep y ) ; then
log "VERBOSE" "Not starting laptop mode because it is disabled in /etc/default/laptop-mode."
STATE=disabled
fi
fi
if [ "$STATE" = "disabled" ] ; then
ACTIVATE=0
fi
# Check whether we are allowed to activate the data-loss-sensitive stuff.
# If the battery charge is too low, we want to disable this, but not the
# other power-saving stuff.
if [ "$ACTIVATE" -eq 0 ] ; then
ACTIVATE_WITH_POSSIBLE_DATA_LOSS=0
elif [ "$ON_AC" = 1 ] ; then
log "VERBOSE" "On AC, not checking minimum battery charge."
ACTIVATE_WITH_POSSIBLE_DATA_LOSS=1
else
ACTIVATE_WITH_POSSIBLE_DATA_LOSS=1
ENOUGH_CHARGE=0
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=0
# Weird way of checking that /sys/class/power_supply is not empty -- but it works.
if [ "$(echo /sys/class/power_supply/*)" != '/sys/class/power_supply/*' ] ; then
log "VERBOSE" "Not on AC and we have battery information in /sys/class/power_supply/BAT* -- checking minimum battery charge."
for BATT in /sys/class/power_supply/* ; do
BATT_TYPE=$(cat $BATT/type)
log "VERBOSE" "$BATT is of type $BATT_TYPE."
if [ "$BATT_TYPE" != "Battery" ] ; then
log "VERBOSE" "Not of type \"Battery\", skipping."
else
PREV_ENOUGH_CHARGE=$ENOUGH_CHARGE
PREV_ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=$ENOUGH_CHARGE_TO_PREVENT_HIBERNATION
log "VERBOSE" "Checking levels for $BATT."
PRESENT=$(cat $BATT/present)
log "VERBOSE" "Present: $PRESENT."
# Only do if the battery is present
if [ "$PRESENT" -eq 1 ] ; then
FOUND_AN_ENABLED_CHECK=0
FOUND_AN_ENABLED_HIBERNATION_CHECK=0
# Get the remaining capacity.
IN_UAH=0
IN_UWH=0
if [ -f $BATT/charge_now ] ; then
REMAINING=$(cat $BATT/charge_now)
IN_UAH=1 # charge_* is in microAmpere-hours
elif [ -f $BATT/energy_now ] ; then
REMAINING=$(cat $BATT/energy_now)
IN_UWH=1 # energy_* is in microWatt-hours
else
REMAINING=0
fi
if [ -z "$REMAINING" -o "$REMAINING" -eq 0 ] ; then
log "VERBOSE" "Battery does not report remaining charge. Perhaps it is not present?"
REMAINING=0
fi
log "VERBOSE" "Remaining charge: $REMAINING"
if [ -f $BATT/charge_full_design ] ; then
CAPACITY=$(cat $BATT/charge_full_design)
elif [ -f $BATT/energy_full_design ] ; then
CAPACITY=$(cat $BATT/energy_full_design)
else
CAPACITY=0
fi
if [ -z "$CAPACITY" -o "$CAPACITY" -eq 0 ] ; then
log "VERBOSE" "Battery does not report design full charge, using non-design full charge."
if [ -f $BATT/charge_full ] ; then
CAPACITY=$(cat $BATT/charge_full)
elif [ -f $BATT/energy_full_design ] ; then
CAPACITY=$(cat $BATT/energy_full)
else
CAPACITY=0
fi
if [ -z "$CAPACITY" -o "$CAPACITY" -eq 0 ] ; then
log "VERBOSE" "Battery does not report non-design full charge."
CAPACITY=0
fi
fi
log "VERBOSE" "Full capacity: $CAPACITY"
# Check the charge percentage
if [ "$MINIMUM_BATTERY_CHARGE_PERCENT" -ne 0 ] ; then
FOUND_AN_ENABLED_CHECK=1
if [ "$CAPACITY" -eq 0 ] ; then
log "MSG" "WARNING: Battery does not report a capacity. Minimum battery"
log "MSG" "charge checking does not work without a design capacity."
ENOUGH_CHARGE=1
elif [ "$(($REMAINING * 100 / $CAPACITY))" -ge "$MINIMUM_BATTERY_CHARGE_PERCENT" ] ; then
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT" -ne 0 ] ; then
FOUND_AN_ENABLED_HIBERNATION_CHECK=1
if [ "$CAPACITY" -eq 0 ] ; then
log "MSG" "WARNING: Battery does not report a design capacity. Auto hibernation"
log "MSG" "does not work without a design capacity."
ENOUGH_CHARGE=1
elif [ "$(($REMAINING * 100 / $CAPACITY))" -ge "$AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT" ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
# $BATT/alarm is the design_capacity_warning of a battery.
ALARM_LEVEL=$(cat $BATT/alarm)
if [ "$ALARM_LEVEL" -ne 0 ] ; then
if [ "$REMAINING" -le "$ALARM_LEVEL" ] ; then
# Restore the state we had before checking this battery, so that
# this battery does not count as having enough charge.
ENOUGH_CHARGE=$PREV_ENOUGH_CHARGE
elif [ "$FOUND_AN_ENABLED_CHECK" -eq 0 ] ; then
# This is the only check that is enabled. In that case a non-critical
# battery level counts as "enough". (If we would count non-critical
# battery levels as enough *always*, then the other settings would
# have no effect; this is only a final fallback.)
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_ON_CRITICAL_BATTERY_LEVEL" -ne 0 ] ; then
if [ "$REMAINING" -le "$ALARM_LEVEL" ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=$PREV_ENOUGH_CHARGE_TO_PREVENT_HIBERNATION
elif [ "$FOUND_AN_ENABLED_HIBERNATION_CHECK" -eq 0 ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
# Fallback: hard values
if [ "$IN_UAH" -ne 0 ] ; then
if [ "$MINIMUM_BATTERY_CHARGE_MAH" -ne 0 ] ; then
FOUND_AN_ENABLED_CHECK=1
if [ "$REMAINING" -ge $((1000*"$MINIMUM_BATTERY_CHARGE_MAH")) ] ; then
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_BATTERY_CHARGE_MAH" -ne 0 ] ; then
FOUND_AN_ENABLED_HIBERNATION_CHECK=1
if [ "$REMAINING" -ge $((1000*"$AUTO_HIBERNATION_BATTERY_CHARGE_MAH")) ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
elif [ "$IN_UWH" -ne 0 ] ; then
if [ "$MINIMUM_BATTERY_CHARGE_MWH" -ne 0 ] ; then
FOUND_AN_ENABLED_CHECK=1
if [ "$REMAINING" -ge $((1000*"$MINIMUM_BATTERY_CHARGE_MWH")) ] ; then
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_BATTERY_CHARGE_MWH" -ne 0 ] ; then
FOUND_AN_ENABLED_HIBERNATION_CHECK=1
if [ "$REMAINING" -ge $((1000*"$AUTO_HIBERNATION_BATTERY_CHARGE_MWH")) ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
else
log "ERR" "Failed to determine battery charge. Battery charge units are not in"
log "ERR" "mWh, uWh, mAh or uAh."
fi
else
log "VERBOSE" "Battery is not present."
fi
fi
done
elif [ "$(echo /proc/acpi/battery/*)" != '/proc/acpi/battery/*' ] ; then
log "VERBOSE" "Not on AC and we have batteries in /proc/acpi/battery -- checking minimum battery charge."
for BATT in /proc/acpi/battery/* ; do
PREV_ENOUGH_CHARGE=$ENOUGH_CHARGE
PREV_ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=$ENOUGH_CHARGE_TO_PREVENT_HIBERNATION
BATT_STATE=$BATT/state
BATT_INFO=$BATT/info
log "VERBOSE" "Checking info and state for $BATT."
# Only do if the battery is present
if ( grep -q 'present:.*yes' $BATT_INFO ) ; then
FOUND_AN_ENABLED_CHECK=0
FOUND_AN_ENABLED_HIBERNATION_CHECK=0
# Get the remaining capacity.
REMAINING=`grep "remaining capacity:" $BATT_STATE | sed "s/.* $[0-9][0-9]* $.*/\1/" `
if [ -z "$REMAINING" ] ; then
log "VERBOSE" "Battery does not report remaining charte. Perhaps it is not present?"
REMAINING=0
fi
log "VERBOSE" "Remaining charge: $REMAINING"
CAPACITY=`grep "design capacity:" $BATT_INFO | sed "s/.* $[0-9][0-9]* $.*/\1/" `
if [ -z "$CAPACITY" ] ; then
log "VERBOSE" "Battery does not report capacity. Perhaps it is not present?"
CAPACITY=0
fi
log "VERBOSE" "Design capacity: $CAPACITY"
# Check the charge percentage
if [ "$MINIMUM_BATTERY_CHARGE_PERCENT" -ne 0 ] ; then
FOUND_AN_ENABLED_CHECK=1
if [ "$CAPACITY" -eq 0 ] ; then
log "MSG" "WARNING: Battery does not report a design capacity. Minimum battery"
log "MSG" "charge checking does not work without a design capacity."
ENOUGH_CHARGE=1
elif [ "$(($REMAINING * 100 / $CAPACITY))" -ge "$MINIMUM_BATTERY_CHARGE_PERCENT" ] ; then
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT" -ne 0 ] ; then
FOUND_AN_ENABLED_HIBERNATION_CHECK=1
if [ "$CAPACITY" -eq 0 ] ; then
log "MSG" "WARNING: Battery does not report a design capacity. Auto hibernation"
log "MSG" "does not work without a design capacity."
ENOUGH_CHARGE=1
elif [ "$(($REMAINING * 100 / $CAPACITY))" -ge "$AUTO_HIBERNATION_BATTERY_CHARGE_PERCENT" ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
# Fallback: hard values.
# Determine the reporting unit.
IN_MAH=0
IN_MWH=0
if ( grep -q mWh $BATT_INFO ) ; then
IN_MWH=1
elif ( grep -q mAh $BATT_INFO ) ; then
IN_MAH=1
fi
if [ "$IN_MAH" -ne 0 ] ; then
if [ "$MINIMUM_BATTERY_CHARGE_MAH" -ne 0 ] ; then
FOUND_AN_ENABLED_CHECK=1
if [ "$REMAINING" -ge "$MINIMUM_BATTERY_CHARGE_MAH" ] ; then
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_BATTERY_CHARGE_MAH" -ne 0 ] ; then
FOUND_AN_ENABLED_HIBERNATION_CHECK=1
if [ "$REMAINING" -ge "$AUTO_HIBERNATION_BATTERY_CHARGE_MAH" ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
elif [ "$IN_MWH" -ne 0 ] ; then
if [ "$MINIMUM_BATTERY_CHARGE_MWH" -ne 0 ] ; then
FOUND_AN_ENABLED_CHECK=1
if [ "$REMAINING" -ge "$MINIMUM_BATTERY_CHARGE_MWH" ] ; then
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_BATTERY_CHARGE_MWH" -ne 0 ] ; then
FOUND_AN_ENABLED_HIBERNATION_CHECK=1
if [ "$REMAINING" -ge "$AUTO_HIBERNATION_BATTERY_CHARGE_MWH" ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
else
log "ERR" "Failed to determine battery charge. Battery charge units are not in"
log "ERR" "mWh or mAh."
fi
CAP_STATE=`sed -r 's/^capacity state:\s*(.*)\s*$/\1/;t;d' "$BATT_STATE"`
if [ "$DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL" -ne 0 ] ; then
if [ "$CAP_STATE" = "critical" ] ; then
# Restore the state we had before checking this battery, so that
# this battery does not count as having enough charge.
ENOUGH_CHARGE=$PREV_ENOUGH_CHARGE
elif [ "$FOUND_AN_ENABLED_CHECK" -eq 0 ] ; then
# This is the only check that is enabled. In that case a non-critical
# battery level counts as "enough". (If we would count non-critical
# battery levels as enough *always*, then the other settings would
# have no effect; this is only a final fallback.)
ENOUGH_CHARGE=1
fi
fi
if [ "$AUTO_HIBERNATION_ON_CRITICAL_BATTERY_LEVEL" -ne 0 ] ; then
if [ "$CAP_STATE" = "critical" ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=$PREV_ENOUGH_CHARGE_TO_PREVENT_HIBERNATION
elif [ "$FOUND_AN_ENABLED_HIBERNATION_CHECK" -eq 0 ] ; then
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
fi
fi
else
log "VERBOSE" "Battery is not present."
fi
done
else
ENOUGH_CHARGE=1
ENOUGH_CHARGE_TO_PREVENT_HIBERNATION=1
log "VERBOSE" "Not on AC and could not check battery state -- data loss sensitive features stay enabled and auto-hibernation will not work."
fi
if [ "$ENABLE_AUTO_HIBERNATION" -ne 0 -a "$ENOUGH_CHARGE_TO_PREVENT_HIBERNATION" -eq 0 ] ; then
log "VERBOSE" "None of the batteries have a charge above the auto-hibernation level."
log "VERBOSE" "Starting hibernation."
if [ -x $HIBERNATE_COMMAND ]; then
$HIBERNATE_COMMAND
elif [ -f /sys/power/state ]; then
grep -q disk /sys/power/state && echo disk > /sys/power/state
fi
# Don't continue -- if things are configured correctly, then we
# will be called on resume.
exit 0
fi
if [ "$ENOUGH_CHARGE" -eq 0 ] ; then
log "VERBOSE" "None of the batteries have a charge above the minimum level."
log "VERBOSE" "Deactivating data loss sensitive features."
ACTIVATE_WITH_POSSIBLE_DATA_LOSS=0
fi
fi
if [ "$INIT" -eq 0 ] ; then
log "MSG" "Laptop mode "
fi
# WAS_ACTIVE is used later on. If there is no /var/run/laptop-mode-tools/state, then
# we know that laptop mode wasn't active before.
WAS_ACTIVE=0
log "VERBOSE" "Checking if desired state is different from current state."
if [ -f /var/run/laptop-mode-tools/state ] ; then
read WAS_ACTIVE WAS_ON_AC WAS_ACTIVATE_WITH_POSSIBLE_DATA_LOSS WAS_STATE < /var/run/laptop-mode-tools/state
if [ "$WAS_STATE" != "" ] ; then
if [ "$WAS_ACTIVE" -eq "$ACTIVATE" -a "$WAS_ON_AC" -eq "$ON_AC" -a "$WAS_ACTIVATE_WITH_POSSIBLE_DATA_LOSS" -eq "$ACTIVATE_WITH_POSSIBLE_DATA_LOSS" -a "$WAS_STATE" = "$STATE" -a "$FORCE" -eq 0 ] ; then
log "MSG" "$STATE, "
if [ "$WAS_ACTIVE" -eq 1 ] ; then
log "MSG" "active [unchanged]"
if [ "$ACTIVATE_WITH_POSSIBLE_DATA_LOSS" -eq 0 ] ; then
log "MSG" " (Data-loss sensitive features disabled.)"
fi
else
log "MSG" "not active [unchanged]"
fi
exit 0
fi
fi
else
log "VERBOSE" "/var/run/laptop-mode-tools/state does not exist, no previous state."
fi
echo "$ACTIVATE $ON_AC $ACTIVATE_WITH_POSSIBLE_DATA_LOSS $STATE" > /var/run/laptop-mode-tools/state
if [ "$ACTIVATE" -eq 1 ] ; then
log "MSG" "$STATE, active"
if [ "$ACTIVATE_WITH_POSSIBLE_DATA_LOSS" -eq 0 ] ; then
log "MSG" " (Data-loss sensitive features disabled.)"
fi
else
log "MSG" "$STATE, not active"
fi
# Finally, call laptop-mode-tools modules. The modules can use the settings
# from the config files, but they may NOT assume the settings actually exist,
# as no defaults have been given for them.
# Note that the /usr/local/lib path is deprecated.
export FORCE STATE ON_AC ACTIVATE ACTIVATE_WITH_POSSIBLE_DATA_LOSS KLEVEL KMINOR WAS_ACTIVE LM_VERBOSE DEVICES
for SCRIPT in /usr/share/laptop-mode-tools/modules/* /usr/local/lib/laptop-mode-tools/modules/* /usr/local/share/laptop-mode-tools/modules/* /etc/laptop-mode/modules/* ; do
if [ -z "$MODULES" ] ; then
# If a module list has not been provided, execute all modules
EXECUTE_SCRIPT=1
else
# If a module list has been provided, execute only the listed
# modules.
EXECUTE_SCRIPT=0
for MODULE in $MODULES; do
# Attempt to remove the module name from the end of the
# full script path. If the module name matches the
# script, the name will be removed from the end of the
# full file path, leaving the path to the script. If
# there was not a match made, the module name would not
# be removed from the path, and $PATH_TO_SCRIPT would
# be the same as $SCRIPT.
PATH_TO_SCRIPT=${SCRIPT%%$MODULE}
# Execute the script if a match was found (module name
# was removed from the script path, making it shorter.
if [ $PATH_TO_SCRIPT != $SCRIPT ] ; then
EXECUTE_SCRIPT=1
fi
done
fi
if [ -x "$SCRIPT" -a $EXECUTE_SCRIPT -eq 1 ] ; then
log "VERBOSE" "Invoking module $SCRIPT."
SCRIPT_DEBUG=$SCRIPT; # We do this because in start-stop-programs module a $SCRIPT variable is used. That
# changes the whole meaning when passed to disableDebug ()
enableDebug $SCRIPT_DEBUG;
. $SCRIPT
disableDebug $SCRIPT_DEBUG;
else
log "VERBOSE" "Module $SCRIPT is not executable or is to be skipped."
fi
done
exit 0
# This fi closes the if for "readconfig". If I would have indented this one
# I would have indented the whole file. :)
fi
lmt_load_config
lock_retry ()
( $FLOCK -n -x -w 1 8 || exit 0;
i=10;
while [ $i -ge 1 ]
do
log "ERR" "Couldn't acquire lock. Retrying.... PID is $$\n"
$FLOCK -x -w 1 9 && lmt_main_function "$@" && break;
i=$(( $i - 1 ))
done
) 8>$LMT_REQ_LOCK
# Check and acquire locks and then exec.
( $FLOCK -n -x -w 1 8; ) 8>$LMT_REQ_LOCK
($FLOCK -n -x -w 1 9 && lmt_main_function "$@";) || lock_retry "$@"
) 9<>$LMT_INVOC_LOCK
# We do a special run of battery polling daemon here so that it does not get
# plagued by the lock. We need the polling daemon to be independent of any locks
if [ x$ENABLE_BATTERY_LEVEL_POLLING = x1 ] && [ x$BLACKLIST_IN_FLOCK = x1 ]; then
log "VERBOSE" "Battery level polling is enabled."
if [ x$ON_AC = x1 ] ; then
log "VERBOSE" "On AC, stopping the polling daemon."
# In AC mode we disable the polling daemon.
killall -q lm-polling-daemon
else
if ! pidof -x lm-polling-daemon ; then
log "VERBOSE" "On battery and there was no polling daemon yet, starting the polling daemon."
# If there is no polling daemon, we start one.
/usr/share/laptop-mode-tools/module-helpers/lm-polling-daemon < /dev/null > /dev/null 2> /dev/null &
fi
fi
else
log "VERBOSE" "Battery level polling is disabled."
fi
exit 0;
and here is the lines which archwiki mentions
case "$KLEVEL" in
"2.4" ) ;;
"2.6" ) ;;
log "ERR" "Unhandled kernel version: $KLEVEL ('uname -r' = '$(uname -r)')" >&2
exit 1
esac

I had the problem but edited the line in /usr/sbin/laptop_mode and it worked. But thoes lines are not there anymore. I guess they changed it at the recent update of laptop-mode-tools.
Regarding your heat problem; is there any other thing you use to cut down power usage (from AUR maybe)? I use acpi_call from AUR had to edit lines there aswell, but it should be updated by now.

Photoshop, Bridge, CS4 Lightroom 4 don't recognize CR2 raw picture from new camera Canon eos 70d -

I just received purchased a new Canon EOS 70D and my Adobe Master Creative Suite CS4 and Photoshop Lightroom 4 do not recognize the image format. Error message I get is "Could not complete your request because Photoshop does not recognize this type of file." Working on a MAC.
Thanks,

http://blogs.adobe.com/crawlspace/2011/03/why-doesnt-my-version-of-photoshop-or-lightroom- support-my-camera.html
http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html

EOS 70D - Mode Dial problem...

Similar Messages

Maybe you are looking for