Power managament / Graphical Login Manager / ...

Hi all,
I'm new to arch, coming from ubuntu (which is a noob distro compared to this ).
I have several questions:
I'm running arch (with fluxbox)  on a laptop and I wanted to place a wmpower  thingy in my slit.
Install was succesfull but when I ran the program, I got a message:
Cpu frequency scaling is not available
No power management subsystem detected
wmpower: No power management support...
I searched forums, installed acpi (pacman -s acpi ), put acpid in my daemon list but when I ran wmpower again cpu frequency is available but I still get this error.
No power management subsystem detected
wmpower: No power management support...
What else should I install?
Other question:
How can I install a graphical login manager, and when I'm logged in,  fluxbox must start ( startx has to be executed automatically).
Last question: Which file manager should I use, I find rox a bit simple imo, and konqueror is to much for me
Thx in advance
Greetz Daan

Hi Daan,
Please see the wiki page regarding SpeedStep: http://wiki.archlinux.org/index.php/SpeedStep
There are links for AMD based systems on this page as well, but only the necessary modules differ from this explanation.
Briefly: Load the correct modules (add them to the modules array in /etc/rc.conf) for your CPU and install (and add it to the daemon section in /etc/rc.conf) cpufreq/another daemon to administer frequency scaling.
nice regards

Similar Messages

  • Windows 7 RTM x64 Power Manager and switchable graphics not working

    Installed Windows 7 RTM x64 on my T400. After windows update and installing Lenovo's drivers, everything is accounted for. ATI graphics works fine, and I can see the Intel graphics on the shortcut menu. I just cannot manually switch to the built-in graphics, nor did I see the Power Manager. What do I need to do? I have installed the drivers for the power management, even though on the list of driver on lenovo's webpage it says it's only for SL models.
    Help would be appreciated.
    Specs:
    T400
    LED
    ATI/Intel switchable graphics
    4Gb

    Have you installed the Power manager http://www-307.ibm.com/pc/support/site.wss/WIN7-BE​TA.html#powm ?
    And after that, make sure you have installed the right driver (the one for switchable graphics): http://www-307.ibm.com/pc/support/site.wss/WIN7-BE​TA.html#m8xswitch
    Hope that helps.
    I also have Windows 7 Professional x64 on my T400 and everything works fine (i only uses programs and driver from here: http://www-307.ibm.com/pc/support/site.wss/WIN7-BE​TA.html
    T400 2767-AG8
    Windows 7 Professional 64bit

  • W500: using the switchable graphics with vista ultimate without the power manager software?

    seriously, invest in a new hitachi travelstar 320gb for 49 bucks from that tiger place online and a usb hard drive caddy, pop in your free clonezilla cd and your rescue and recovery problems will be over!
    after reading all the problems with that software i figured my data was too valuble to get caught in that mess so for under 75 bucks problem solved and i rid my w500 of that bloatware. even cheaper then ordering the recovery disks from lenovo.
    working on getting rid of the rest of the useless software now.
    hey question, how do you use the switchable graphics on the w500 with vista ultimate without the power manager software? if you can thats next!!
    Moderator note: Question added to subject line for clarity.
    Message Edited by Agotthelf on 28-04-2009 08:45 AM

    That's because you are asking a T500/W500 question in the Thinkvantage forum. Anyway, the answer to your question is in this thread.
    ATI recently started packaging their switchable graphics driver together with their regular Catalyst. So downloading their latest driver Catalyst 9.4 from the ATI/AMD site and then modifying it with the Mobility Modder will allow you to use switchable graphics without the power manager. The little problem is just that the released version of the Mobility Modder stopped working with Catalyst 9.2 and you are on your own getting a modified Modder  working on 9.4, see here.
    So I decided not to make more work for myself staying on a modded Catalyst 9.1 and for the time being living without switchable graphics.
    T500: Vista 32, 2.8GHz, 4GB RAM, 15.4" 1680x1050, 500GB 7200rpm, ATI Radeon HD3650 + Intel 4500MHD. T42: XP, 1.7GHz, 2GB RAM, 14.1" 1024x768, 250GB PATA, ATI Radeon 7500.

  • Power Manager 3.48 no longer has switchable graphics option

    I ran Active Update yesterday and the Power Manager is now upgraded to version 3.48.  It appears that there is no longer an option to switch between high performance and energy saving graphics.  How is the graphics mode supposed to be switched now that this menu option has been removed from the right mouse button menu on the Power manager?  Do I need to downgrade to a previous version?
    In case it matters, I'm running a W500 with Windows 7 Professional 64-bit.
    Thanks,
    Danny

    @ersiles,
    I have the T400 with switchable, I just updated it to PM 3.64 and it does swtich. What I notice earlier when I wasn't able to switch the graphic was due to BIOS settings.
    Check BIOS settings if you have it on switchable graphic mode and check if BIOS detect is enabled.
    Once that is done, boot into Windows, uninstall all the video drivers, reboot. then install the drivers again.
    Windows would try to install their version of the driver, click "Reboot later" when Windows prompt a reboot. Reboot only when ATi manager prompt the reboot.
    I was having issue too on the T400 not being able to switch. It definitely helped me ..
    Let me know.
    //JameZ
    Check out the Community Knowledge Base for hints and tips.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    X240 | 8GB RAM | 512GB Samsung SSD

  • X301 graphics scramble and can't launch power manager

    some times at boot after I get to the logon page I use the finger print reader the graphics scrabbles and I have to hard boot the x301 to get it to work again.  I have a feeling that this has to do something with the finger printer reader.   Anyone else having this problem.
    Also with the newest update of the power manger I can not get into it anymore as "Power manager has stopped working" is the error message I recieved.  Otherwise as far as power management goes it seems to work correctly.  Anyone else with this problem? 

    Here are the video's
     sorry they are kind of long.
    Video1 shows a cold boot then is reboots on it's own then goes to the Bios screen then boots again.  Ofcourse I have to press continue to tell vista that the computer rebooted without a normal shutdown. I do this pretty much every morning.
    http://www.youtube.com/watch?v=nMLeUkfmuQ8 
    Video2 starts with the scramble you have to hard boot by holding down the power button.
    http://www.youtube.com/watch?v=Tsps3q_pXkk 
    Video3 starts with a bad graphics scramble, that happened right after I turned the camera off on video2.
    http://www.youtube.com/watch?v=lvUiIK9_PBM 

  • Power Manager 2.37 crash on Login (with callstack)

    I recently installed Power Manager 2.37 on my Thinkoad T400 (running Vista x64) and am now seeing the following crash whenever someone logs into Windows. Anyone else seeing this?
    System.Windows.Markup.XamlParseException was unhandled
      Message=" Unable to cast object of type 'System.Windows.Controls.StackPanel' to type 'System.Windows.Controls.Image'.  Error at object 'System.Windows.Controls.StackPanel' in markup file 'PWMUIAux;component/sliderpanel.xaml'."
      Source="PresentationFramework"
      LineNumber=0
      LinePosition=0
      NameContext="Header"
      UidContext="MenuItem_3"
      StackTrace:
           at System.Windows.Markup.XamlParseException.ThrowException(String message, Exception innerException, Int32 lineNumber, Int32 linePosition, Uri baseUri, XamlObjectIds currentXamlObjectIds, XamlObjectIds contextXamlObjectIds, Type objectType)
           at System.Windows.Markup.XamlParseException.ThrowException(ParserContext parserContext, Int32 lineNumber, Int32 linePosition, String message, Exception innerException)
           at System.Windows.Markup.BamlRecordReader.ThrowExceptionWithLine(String message, Exception innerException)
           at System.Windows.Markup.BamlRecordReader.CreateInstanceFromType(Type type, Int16 typeId, Boolean throwOnFail)
           at System.Windows.Markup.BamlRecordReader.GetElementAndFlags(BamlElementStartRecord bamlElementStartRecord, Object& element, ReaderFlags& flags, Type& delayCreatedType, Int16& delayCreatedTypeId)
           at System.Windows.Markup.BamlRecordReader.BaseReadElementStartRecord(BamlElementStartRecord bamlElementRecord)
           at System.Windows.Markup.BamlRecordReader.ReadElementStartRecord(BamlElementStartRecord bamlElementRecord)
           at System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord)
           at System.Windows.Markup.BamlRecordReader.Read(Boolean singleRecord)
           at System.Windows.Markup.TreeBuilderBamlTranslator.ParseFragment()
           at System.Windows.Markup.TreeBuilder.Parse()
           at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
           at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
           at PWMUIAux.TaskTrayMenu.InitializeComponent()
           at PWMUIAux.TaskTrayMenu..ctor()
           at PWMUIAux.MainWindow..ctor()
           at PWMUIAux.App.GetMainWindowHandle()
           at PWMUIAux.App.App_Startup(Object sender, StartupEventArgs e)
           at System.Windows.Application.OnStartup(StartupEventArgs e)
           at System.Windows.Application.<.ctor>b__0(Object unused)
           at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
           at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.DispatcherOperation.InvokeImpl()
           at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
           at System.Threading.ExecutionContext.runTryCode(Object userData)
           at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
           at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
           at System.Windows.Threading.DispatcherOperation.Invoke()
           at System.Windows.Threading.Dispatcher.ProcessQueue()
           at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
           at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
           at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
           at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
           at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
           at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
           at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
           at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
           at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
           at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
           at System.Windows.Threading.Dispatcher.Run()
           at System.Windows.Application.RunDispatcher(Object ignore)
           at System.Windows.Application.RunInternal(Window window)
           at System.Windows.Application.Run(Window window)
           at System.Windows.Application.Run()
           at PWMUIAux.App.Main()
      InnerException: System.InvalidCastException
           Message="Unable to cast object of type 'System.Windows.Controls.StackPanel' to type 'System.Windows.Controls.Image'."
           Source="PWMUIAux"
           StackTrace:
                at PWMUIAux.SliderPanel.System.Windows.Markup.IComponentConnector.Connect(Int32 connectionId, Object target)
                at System.Windows.Markup.BamlRecordReader.ReadConnectionId(BamlConnectionIdRecord bamlConnectionIdRecord)
                at System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord)
           InnerException:
    Solved!
    Go to Solution.

    There are newer Power Manager versions available, the latest I think is 2.50. You should try installing a new one, to see if that solves the problem.

  • Power Manager - big graphical footprint in taskbar + quick profile selection

    Is there any way to make the green battery and charger icons in the taskbar smaller?
    I run Win 7 Pro and have changed to the old classic desktop scheme.
    The taskbar should then be quite slim, but the height of the Lenovo Power Manager tool is made for the new Win 7 desktop theme with a slightly taller taskbar.
    To get a slim taskbar, I have to disable the Lenovo Power Manager tool all together. :-(
    Is there any way to configure the PM to use old WinXP style icons?
    Another change to the worse, compared to the Power Manager in WinXP, is that a single mouseclick on the green batterly in the taskbar no longer popup a quick selection meny with the different power schemas. Instead the entire lenovo Power manager application is started.
    Is there any way to get the quiick selection back?

    welcome to the community.
    which version of Power Manager are you running?
    the machine i've got in front of me right now, running the aero interface, is still on v6.07 and the PM "toolbar" icon doesn't change the taskbar size at all. my taskbar is set to use small icons, by default. also, on this machine, PM advanced options are set to open its power scheme selector with Fn+F3.
    i'll check another machine later today which is running PM v6.32 to see if it's different in some way.
    regards.
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество
    Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
    PM requests for individual support are not answered. If a post solves your issue, please mark it so.
    X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
    I am not a Lenovo employee.

  • Any tips on getting power management/sleep working on an Ideapad y460 (0633)?

    Hi All,
    I've decied to try and put Windows 8 on a new SSD and try using it in my Idepad y460 (0633). 
    I've actually gotten most all of the drivers to work, including the AMD switchable graphics (by running that installer in Win7 compatibility mode).
    However, I cannot get sleep to work properly. If not a crash, I experience random messages about services not running when I wake from sleep (i.e. audio service isn't running, network card is listed as 'unavailable', etc.) that require a restart to fix. I've tried running the power management driver listed for my model (http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS007793) in Win7 compatibility mode, but all it does is slow down my login, and make windows complain about known compatibility issues. Doesn't fix sleep. I've tried the Lenovo Power Managment for Windows 8 (http://support.lenovo.com/en_GR/downloads/detail.page?DocID=DS030850), even though my device wasn't listed. It installs okay, but doesn't fix sleep issues, and the touch buttons still don't work.
    For now, I've decided that "Do nothing" on lid close, while "Hibernate" for power button is fast enough and convenient, as those options work just fine. However, I would like sleep to be able to work.
    I understand Windows 8 is not actually released yet, but I was wondering if anyone had tried this and found success, as this is the only problem I have left preventing me from using Windows 8 comfortably.
    Thanks for any tips,
    - Chase

    maybe some hints..  elevated cmd prompt
    powerCfg /Energy

  • Where can I find XP x64 drivers for Portege R500 - hotkey / power management?

    Where can I find downloads that will enable power management or hotkey support for my Portege R500?
    I have already installed drivers for everything except fingerprint reader (don't want), tpm (really don't want), and hdd motion sensor (tos620a) (not bothered about right now). Most drivers are latest from original vendor websites, or, failing those, from Toshiba's Vista 64-bit download areas.
    Everything else generally works: wifi, graphics & chipset, sound, lan, bluetooth stack, cardbus, card reader, etc.
    However, having done this, the following issues remain:
    FN hotkeys don't work for suspend to ram, suspend to disk, *screen* *brightness* - essential to extending lifetime; FN hotkeys for numeric/direction pad, external monitor toggle *do* work
    Dedicated backlight toggle button doesn't do anything
    However, in order to get battery lifetime beyond ~2.5 hours and closer to the rated 7.1 hours, I'll need to turn some things down / off occasionally. What software can help and where can I get it, such that it works on Windows XP x64 edition?
    Note:
    I have tried the xp 32-bit packages that Toshiba supplies, they don't appear to work on x64. The 'ctrls' package requires 'cmod', but 'cmod' gives this error:
    TOSHIBA Common Modules Setup
    Not an ACPI machine. Cannot install TOSHIBA ACPI Logical Device.
    OK
    I have tried the xp 32-bit package called 'pwrsav'; it installs a bad help link to my start menu, and adds a couple of exes, tpsmain and tpsoddctl, to my auto-runs. These 32-bit executables quit immediately after execution.
    I would have tried to install Toshiba's Vista 64-bit packages for hotkeys / common modules / power management, but the only one of the three I can find via toshiba.co.uk are common modules, and unfortunately that zip file only contains .inf, .cat and .sys files, no installer.
    Motivation:
    I'm using a fresh install both because the default Vista install is unusable (900MB memory used on a fresh boot desktop, drive split into multiple partitions, trial, adware and broken software installed left and right)
    I'm using x64 because I'm a software engineer whose next product needs to work on x64, and this new laptop was a likely first candidate

    You didn't link to the tool you found. If you meant this tool then, you should be aware it doesn't work on x64 on R500:
    Display Tuner
    Cannot detect monitor!
    Your monitor does not support DDC control or your videocard is not supported by Display Tuner.
    You cannot use Display Tuner in this configuration.
    OK
    It would be unlikely to work in any case, as display driver brightness isn't normally the same as the screen's brightness (hence power usage).
    Maybe it's a communication issue, but I *have* found +original+ drivers for all essential components, just not for things like screen brightness - something that, to be honest, I more expect to be handled in firmware / bios, as that's been my experience on previous laptops, and is more reliable in any case, considering I could be running an oddball Linux or a completely different OS, or a CPU-intensive high-priority task.
    The R500 series seem to be scrimping on the firmware and expecting OS utilities and dedicate yet another system tray icon to take over that job.
    It does look like x64 is a no-go for mobile use on this machine, due to lack of firmware power management, which is a great pity as the point of such a light machine is mobility. I'll wipe it and install XP 32-bit and see how that goes.

  • I need a new power management board for MacBook Pro.   The AC 7000 chip is blown from power serge.  Where can I get one in Fiji?

    Where can I get my power management board repaired ...replace the AC7000 chip ( that now has a little hole in it from a power serge ) or replaced in Fiji?

    Actually, this is how I do my projects   . . .  I pull together all the assets  (video clips, stills, graphics) and tag them in a database.  Then, I can pull them into various segments.   I learned the ctrl+m five years ago when it was suggested on the old forum by some guy named named Steve Grisetti.
    Example  - - -  I've done multiple soccer videos.  There are maybe 16 players on a team...  each is a tag.   There are great headers  . . . that's  a tag . . . don't forget awesome defensive plays  . . .  tag.   A tag for screwups / funny.    A tag for regular season play, a tag for post-season playoffs, etc.   
    This allows you to build it as you go.   So, as you start to compile a season end video, it's relatively simple to pull content.    Oops, you review the segments and see that one kid's hardly included... select the tag with their name and you can pull in a few more clips.   If you're documenting a season, you can see how the database is coming along and determine you need more footage of certain situations and then adjust the shooting priorities at the next couple games, etc.
    As you build the collection, possible themes come...  perhaps a song or two that might add an element or tie things together.
    SO...  goal is to assemble a collection of decent and tight clips  (leaving room for handles on each).  Tossing out all the superferlous stuff.    In shooting a 90 minute soccer game, there can be times when I end up with only  ten minutes of visually interesting stuff.
    I'm also compiling content to be used in a video for a cool company here in Seattle.   Different thing altogether, but will take a similar apporach (fewer digital assets, however).
    I don't usually take assets from one project and put onto another  . . .  especially when doing youth sports, this could create issues.

  • Power Manager does not save my custom settings

    I'm running Win7 Pro 64bit SP1 (Swedish) and Power Manager v6.36 on my W530.
    When I create a new power profile, I go through all the 5 steps, but afterward no new profile exist. I only see the default 5 ones from Lenovo PM.
    Same thing if I change the setting in any of the 5 profiles, the changes aren't saved.
    This is reproduceable every time.
    The only changes that DO get saved are the settings on the Global tab like if I choose to do nothing when the lid is closed.
    Is there any way to get the Power Manager to work as it should?
    PS: I really miss the possibility to swiftly change power profile via a left click on the green power gauge next to the systray. Nowdays a single click load and start up the entire Power Manager application. This is SO tiresome when I just want to do a quick change of the profile.
    PPS: I had the same problem in v6.32 and just installed 6.36, but still the problem persists.

    It sounds to me that the two power managers are conflicting with each other. Try to make your custom power settings inside of the Lenovo Power Manager. 
    You can do this by opening the Lenovo Power manager and selecting the power plan tab, directly under the tab is a button that says New. When you select this a new window should open to allow you customize your own power schemes. You will be able to customize the System settings such as: Maximum CPU speed, Display Brightness, Graphics Power plan, also desired Idle timers, events, alarms an other advanced settings. Once created you will see your new power plan listed under the default power plans.
    If this does not work, I would then suggest uninstalling the Lenovo Power Manager and utilize Microsoft Power Manager.
    Good luck! Let me know if you have any questions
    Thank you for being a part of the Lenovo Family,
    Catie
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Donate KUDOS and Click "Accepted Solution"

  • Gnome-power-manager update causes backlight to power off frequently

    After the upgrade to gnome-power-manager 2.26.1-1 today, my laptop screen backlight is being powered off constantly, after only about 1 minute. It's not the screen blanking, but the backlight going off. It comes right back up if I do anything on the keyboard.
    My power management preferences haven't changed though. They're all set (as before the upgrade) to never dim the display and never put the display to sleep. So why is the backlight going off anyway?
    Also, this pretty distinctly seems to have to do with Gnome and not X. If I leave the laptop for an extended period at the GDM login screen, the backlight is never powered off. The problem only develops after I have logged into Gnome.
    Thanks for any help.
    Last edited by cb474 (2009-04-23 07:14:55)

    Thanks, I looked for bugs on this, but didn't find that one on the backlight for some reason. I was about to issue my own bug report. Anyway, so I added my comments to the bug report, but it has been marked "fixed" already (because it was really addressing a slightly different issue with DPMS), so I don't know if I need to start a new bug report or not. I'll wait and see what kind of reply I get. (In fact, it seems like the fix to the problem in the backlight bug report may have caused the problem addressed in this thread.)
    That said, I found a work around, if you want to completely disable the backlight ever going off. You can issue the command:
    xset -dpms
    This disables entirely the display power management system (which I'm guessing gnome-power-manager operates as a frontend for). Of course, if you want your screen to be put to sleep after some set point of time this won't work. But you may be able to configure this directly with other xset commands or in xorg.conf (see links below).
    To disable dpms at startup. I found oddly that it didn't work to add it to my .xinitrc. So instead I went to System > Preferences > Startup Applications. Added an a program in the "Startup Programs" tab, named it "DPMS (disable)" and for the command put:
    xset -dpms
    This is working.
    You can also configue DPMS in xorg.conf, but I'm not using xorg.conf so I didn't fiddle with it. See: http://wiki.archlinux.org/index.php/DPMS and http://www.shallowsky.com/linux/x-screen-blanking.html.
    Hope that helps.
    Last edited by cb474 (2009-04-24 08:26:23)

  • X61 power manager on Win 7 64bit

    I have installed Windows 7 64 bit Ultimate edition on my X61 with 4Gb RAM. 
    Fully charged, the power manager shows over 2 hours available time, but the problem I have is that the machine will, without any warning, perform a "critical power level" shutdown when the power available is still showing in excess of 1 hour.
    After reconnecting the charger and restarting the machine, the power manager now shows almost empty - just over 5%.
    All drivers and utilities are the latest available, based on the System Update tool.  The battery also does not come up as being on the recall list, and in all other respects is in good condition - the cycle count is only 56. The power manager reports version 3.31
    Has anyone else observed similar behaviour for the power manager on an X61 ??

    Hello mate,
    Try to calibrate the battery and see if it's getting better.
    Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it.
    ThinkPad T510 4313-CTO Windows 8 x64 - Intel Core i7-620M - NVIDIA NVS 3100M - 8GB RAM - 240GB SSD- Intel Centrino Ultimate-N 6300 - Gobi 2000.
    ThinkPad Helix 3697-CTO Windows 8.1 x64 - Intel Core i7-3667U - Intel HD Graphics 4000 - 8GB RAM- 256GB SSD - Intel Centrino Advanced-N 6205 - Ericsson C5621gw

  • Gnome 3.2 power management

    Hi everyone!
    I installed gnome 3.2 from unstable, and I notice that now my power management is worst than ever.
    The problem is that my graphics card, nvidia nvs 3100m, has some problems with DPMS. I can set the screen off with dpms, It works, but mouse or key activities won't bring the lights back up.
    With this last gnome version, closing the laptop lid probably issues dpms commands, so to power the screen again I have to kill X11...
    Closing the lid used to work as I wanted, before, letting the laptop (elitebook 8440p) itself handle the screen power.
    I have tried settings "NODPMS" on xorg.conf, but had no luck. I also tried to find something in dconf-editor, but I found no specific option for really doing nothing when the laptop lid is closed.
    It might be worth noting that my power settings don't show like this post advertised, I just have options on actions after determined time, not lid closing: http://justinstories.wordpress.com/2011 … lid-close/
    This is *very* bad for me, gnome is completely unusable this way! Any helps?
    Edit: oh, and the options in gnome tweak tool don't work anymore...
    Last edited by nDray (2011-09-28 10:15:51)

    you shouldn't trust that website. that is ubuntu patching the hell out gnome.
    for me, i setup the monitor to shutdown after 10 minutes from System Settings->Screen, it wakes up fine every time.
    to configure what action to do when lid is closed, you have to use gsettings or dconf-edit.
    gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action
    'blank'

  • Xfce4-power-manager does not start, but after relogin - works

    Hi all.
    When I login after system start, xfce4-power-manager does not start and systemtray icon doesn't appear. But after relogin (not restart), the systemtray icon of xfce4-power-manager appears and power manager itself works correctly (if I don't relogin, notebook will shutdown after 10 minutes of downtime - that rule doesn't exist in xfce4-power-manager settings).
    Diff between two logs (before relogin and after, xfce4-power-manager --debug command)
    diff log_1 log_2
    35c35,36
    < TRACE[xfpm-battery.c:286] xfpm_battery_refresh_icon(): Battery state 0
    > TRACE[xfpm-battery.c:150] xfpm_battery_refresh_visible(): visible=TRUE: ((XfpmShowIcon) SHOW_ICON_WHEN_BATTERY_PRESENT)
    > TRACE[xfpm-battery.c:286] xfpm_battery_refresh_icon(): Battery state 4
    51d51
    < TRACE[xfpm-polkit.c:238] xfpm_polkit_free_data(): Destroying Polkit data
    System
    Linux gready 3.14.1-1-ARCH #1 SMP PREEMPT Mon Apr 14 20:40:47 CEST 2014 x86_64 GNU/Linux
    systemd 212-3
    xfce4-power-manager 1.2.0-6
    That bug start happening after one of last week updates. I don't have a package cache.
    Can anyone help me?
    p.s. sorry for a bad English.

    Yes, i'm actually running xfce4 (all other things from xfce4 group are installed).
    It starts from a login manager named LightDM.
    AcpiD installed as a dependency.
    logind.conf
    # This file is part of systemd.
    # systemd is free software; you can redistribute it and/or modify it
    # under the terms of the GNU Lesser General Public License as published by
    # the Free Software Foundation; either version 2.1 of the License, or
    # (at your option) any later version.
    # See logind.conf(5) for details
    [Login]
    #NAutoVTs=6
    #ReserveVT=6
    #KillUserProcesses=no
    #KillOnlyUsers=
    #KillExcludeUsers=root
    #InhibitDelayMaxSec=5
    HandlePowerKey=ignore
    HandleSuspendKey=ignore
    HandleHibernateKey=ignore
    HandleLidSwitch=ignore
    #PowerKeyIgnoreInhibited=no
    #SuspendKeyIgnoreInhibited=no
    #HibernateKeyIgnoreInhibited=no
    #LidSwitchIgnoreInhibited=yes
    #IdleAction=ignore
    #IdleActionSec=30min
    I turned off key handlers because I truly HATE when I press power button and a notebook doing shutdown after that.
    Last edited by theperfectblance (2014-04-17 06:57:32)

Maybe you are looking for