Pm-suspend only after key press

Hi!
I'm running current Arch with 2.6.27 stock kernel on my Acer Aspire 5520 notebook. If I do "pm-suspend" the screen gets black and only the cursor is blinking at the top line. But the notbook only turns off if i press a key on the keyboard a few times (think about how long I tried to figure this out)!
Also if I "poweroff" the normal poweroff sequence is shown on console until the last line states "Power down". It remains like this until I press a key on the keyboard. Then I can see a line stating "Power down" for a fraction of a second before power finally turns off.
I think this is quite weird! Has someone experienced something similar? Or does someone even have a fix for it? Because it's quite annoying!
Erki
PS: I'm not sure if it might help if I post a log file of some kind. If you know which one might help, please let me know!

Hi,
I have an Aspire 5520 too, running 2.6.28.1 and 2.6.29-rc3 and having the same issue: suspend to ram needs one or more keypress to power down.
Adding "clocksource=jiffies" to the kernel parameter list resolves this issue, but who wants to use jiffies as clocksource.
Tried tsc as clocksource too, but it seemingly doesn't work correctly with cpufreq (sleep 10 waits up to 20+ seconds when the CPU is running at 800MHz).
micsa
Last edited by micsa (2009-02-04 12:27:24)

Similar Messages

  • Get control after key press in listview?

    how to get control after key press in listview ????
    example
    after keyboard key PAGE_DOWN  from listview
    execute my routine ?????
    Thank' s

    PavelSafrata, your solution is right, but in my case it does not work properly, because it has to be "setOnKeyPressed", then he picks up the current line and not after the jump PAGE_DOWN.
    used the routine below, but in this case when pressed SHIFT + PAGE_DOWN, does not bring the line "new" correct.
    this.getSelectionModel().selectedIndexProperty().addListener(new ChangeListener<Number>() {
                @Override
                public void changed(ObservableValue<? extends Number> observableValue, Number old, Number n ) {
                    if( my_last_keyborard_registered == KeyCode.PAGE_DOWN  ) {
                        System.out.println( n.intValue() );    // when pressed SHIFT + PAGE_DOWN
                                       // get -1  << error
    Thank's

  • Retarded reaction after key press

    Hello everybody,
    after I updated from LR 1.0 to 1.1 I encounter strange retardations after pressing a key/menu bar.
    For example:
    In library mode clicking "3" LR takes 15 seconds to react and set the rating of the picture to "3". Clicking "x" to reject a picture also takes 15 seconds.
    Clicking on the menu bar takes 15 seconds for the system to open a menu.
    It is hardly possible to use LR with this flaw.
    Clicking on the navigation buttons (left, right, up, down) the system reacts instantaneously.
    Before I updated to LR 1.1 using LR 1.0 everything was fine (in this respect).
    Has anybody observed this effect too. Does anybody have a solution for this problem?
    Thanks in advance,
    Thorsten
    PS:
    Of course I already uninstalled and reinstalled LR, without improvement.
    My system is:
    Windows XP SP2
    Athlon x2 3800
    2 GB Ram

    Hi Everyone,
    I read Thorsten's post with interest and Michael's reply because I am having a terrible time with LR 1.1.
    I am on a Mac G5 Dual with 2 gigs of RAM and 2-500 gigs of Hard Drive. My LR 1.1 has slowed to an absolute cold molasses crawl. Nothing works anymore without sitting and waiting forever. The files take forever to load and when they do load "working" they are pixelated so bad they can't be read. The metadata never seems to load.. I could go on and on but I would have to list everything that happens in the workflow.
    I have deleted and reloaded my catalogs, I have divided my catalogs so they only hold a small amout of files. One only has about 1700 pictures and most of those are jpegs. I have another catalog that has about 4000 files and about 2/3's of those are RAW.
    I have been on the phone with Adobe Tech Support 3 times (they have been good to work with and have tried to solve the problem). We have changed things, made smaller previews, put the view preference on low, divided catalogs even smaller yet.. etc., etc.
    I have dumped all my 1:1 previews and then reloaded them all over again. I have worked with Adobe on everything that can be changed, but there isn't really much to change. I am very disappointed because I ran version 1.0 on the same machine without a problem.. it ran fast and great.
    I didn't notice this slowdown from the very start of installing 1.1 but it might have started and I just didn't notice. But now it is so slow that working with a folder of just 150 files is almost useless. I have taken screen shots to show that even the navagator picture pixelates to the point of being unreadable. The menus are super slow. The scrolling even takes forever and the power scroll arrows at the end of the filmstrip won't even work with LR sometimes. And then after quitting lightroom it seems my whole computer is sluggish for a while.
    My Photoshop CS3 and Bridge work great at normal speed even when loading a file from LR.
    Now I just noticed Thorsten's post and Michael's reply about unchecking the auto XMP write because of a bug when the Tech at Adobe Lightroom told me just today to leave it checked as on. If there was a problem with that wouldn't they know ??? How utterly frustrating.. I told the tech today that I only have one catalog with 1700 files and another with 4000 and that I was sure there were people with 10's of thousands and if this was how LR bogged down then something was very wrong. Heck my iPhoto has 3 times as many as LR and works great !!
    I just went into preferrences and unchecked the XMP auto write and restarted LR and things seem to work fine and back to normal (fingers crossed).
    I asked the tech today why I always have the 3 dots in my filmstrip that never seem to go away and he didn't know. He just told me to choose the "read or save" metadata from/to file in the Metadata pull down menu to load it.. when I did this it took all day for a 100 picture file to load.
    COULD THIS be my problem finally. Does anyone know any more on this subject.
    Thanks for viewing my question and problem. I hope that is this is the problem then it will help someone else too, this wasa terrible.

  • Show report only after button pressed

    I do have a page with a report in a region , a button and some item's witch are needed for the query of the report. (-> parameters)
    The problem is that the report should only be calculated after pressing the button "Go"
    But the report is calculated instantly when the page is invoked which took very long because when no parameter is selected the result is very large.
    I tried to use the condition in the report but had no success.
    thanks in advance
    Odeedo

    Report condition: request=GO (or the one that you set with the botton)
    Add a BRANCH to page (after processing) to the page itself, and that set the request to GO (or what have you choose ...)
    It should works
    Thanks
    Stefano Corradi
    (be carefully to avoid a redirect in the botton without submit, because in this case you item has not submitted)

  • My MacBook pro retina display 15 inch (2013) doesn't start. After I press the start button there is only a beep sound at regular interval. The screen remains blank and the keys don,t light up. Can anyone help please?

    My MacBook pro retina display 15 inch (2013) doesn't start. After I press the start button there is only a beep sound at regular interval. The screen remains blank and the keys don,t light up. Can anyone help please?

    If your MBP is under warranty, bring it to an Apple store and have the technicians fix it.  If not, try the steps in this support article:
    http://support.apple.com/kb/ts2570
    Ciao.

  • My laptops QWERTY row of keys does not work for long periods at random intervals and only after pushing all the buttons on the row does it eventually turn back on and then will still cut out every now and again, anyone know how to solve this?

    My laptops QWERTY row of keys does not work for long periods at random intervals and only after pushing all the buttons on the row does it eventually turn back on and then will still cut out every now and again, anyone know how to solve this? If not is there any way to actually get a genuis appointment lol to get one of them to have a look at the hardware on the keyboard?

    Apple Support (formerly ExpressLane):
    https://getsupport.apple.com/GetproductgroupList.do
    https://getsupport.apple.com/GetSASO?SG=SG001&locale=en_US

  • Words only show up after I press the SpaceBar?

    On Pages, the that I type only show up after I press the space bar. How can I fix this? Thanks

    Tried changing fonts?
    Does this only happen in Pages?
    What happens in other applications especially TextEdit, Numbers and Keynote?
    Have you tested what happens if you type in another User account?
    Peter

  • Dear all, Since a week ago I observe that when I press the button for my macbook air to start a nap, first the screen turns to black but I can see the arrow (pointer). And only after few seconds the arrow and the screen really shut down.

    Dear all, Since a week ago I observe that when I press the button for my macbook air to start a nap, first the screen turns to black (although I can see it is stil on) and I can see the arrow (pointer). Only after 15 seconds the arrow and the screen really shut down. It did not occur before, as a matter of fact it was instantaneous. What could be the problem?

    Note the time in your Mac's menu bar or some other accurate timepiece. Then, press the button to put the MBA to sleep. Wait until the cursor disappears and for all indications that the Mac appears to be asleep.
    Then, wake the Mac the way you normally wake it.
    Then, find the Console app - it is in your Utilities folder and looks like this
    You can find it by selecting Utilities from the Finder's Go menu.
    Open Console.
    If the log list column on the left is not already displayed, show the log list by selecting Show Log List from Console's View menu.
    Locate system.log in the list and select it. Many date and time-stamped entries will appear, hundreds of them, and you must find the entries relevant to your Mac's sleep problem. To do that type the words sleep cause in the Filter field at the upper left of the Console window:
    That will cause all log entries to be hidden, except for the entries containing those words. The last entry in the list will correspond to the last time you woke the Mac. It will have a time stamp in the form hh:mm:ss later than the time you noted in the Mac's menu bar prior to putting it to sleep.
    Make note of that exact time in hours, minutes, and seconds.
    Next: Clear the filter field by clicking the x in the above screenshot. It should then look like this:
    All previously displayed log entries will reappear.
    Next: Find the log entry that corresponds exactly to the time you noted in hours, minutes, and seconds containing the words "previous sleep cause". You may have to scroll up or down a considerable distance. When you find that line, select it and drag your cursor up and prior to the entry corresponding to the approximate time you noted before putting the Mac to sleep. This will result in a selection of perhaps 50 to 100 lines or so.
    One or more of them, along with their time stamps, may reveal the reason for the fifteen second delay.
    Copy and paste those log entries in a reply.
    Most of the entries will be cryptic but will contain information you might consider personal such as your Mac's name. If you do not want that information to appear, delete or obscure it when posting your reply. Leave enough information so that the entries can be deciphered.

  • How do you register multiple key presses at the same time?

    Hi. I'm trying to write a first person game in OpenGL and I'm having some trouble with key listening. Right now I just use the basic AWT KeyListener. The problem that arises is that whenever I hold down a key, such as a movement key, there is a short pause after it moves me in the appropriate direction, and only after the pause does it start continuously moving me. In addition to that, I can't press multiple keys at once to get diagonal movement (I use WASD for movement). Is there something I can do with AWT to fix both of these problems, or is there something other than AWT that I should use that would be better?

    the pause is the typomatic rate of the keyboard, you can avoid that by using the keyPressed and setting a flag then a sleep(myDelayTime).... if they keyRelease--and clearing of the flag--hasn't happened after the sleep, then you're key is still down so keep firing, moving, or what ever.

  • Multiple key press's with Bluetooth Keyboard

    I'm ready to update my mac to a new G5 imac and fancy getting the wireless bluetooth keyboard and mouse with it.
    I have one question, has anyone experienced problems when holding down multiple keys on the keyboard and moving the mouse all at once (Using illustrator)?
    In my office I have the misfortune of having to use a PC, I have had a number of wireless keyboard and mouse combos, all of them when using Illustrator and photoshop can not handle multiple key press's and mouse movement.
    ie if I'm duplicating an object by dragging a copy of it across the screen, on the PC it will work but it always "releases" after a couple of seconds and drops the copy in the where I don't want it which gets very frustrating (this only happens with wireless).
    As I do a lot of work at home, I hoping this wont be the case with the mac's bluetooth K & M.
    thanks
    Russell

    The shift key works just fine on my Bluetooth keyboard.  So I would imagine this is an issue with your keyboard.

  • Catching Alt Key Press with the Key Down Filter Event

    I am writing an application that requires specific key combinations using ctrl, shift, and alt in addition to a function key (F1, F2, F3, etc).  The application works great except for when I try to catch an alt key press.  The alt key press does not seem to fire an event eventhough it is an option in the PlatMods cluster as well as the VKey enum.  When I press the alt key when my application is running the cursor changes to a normal mouse pointer from the usual finger pointer and prevents any other key presses from going through (in addition to not firing an event itself).
    I have tried completely removing the run-time menu, which doesn't seem to help.  I currently discard all keys after I handle them in my event structure.
    I really hope that the only solution isn't using a Windows DLL.  Any suggestions or ideas at all would be greatly appreciated.
    Thanks,
    Ames

     Hi Ames
    As Kileen has said Khalid has already given you a good solution to detect the ALT key.
    I have another approach that might let you stick to your event-driven approach. I suggest that you have another loop in your app that polls the keyboard using the Input Device utility vi's. When this poll loop sees an ALT + KEY combo it raises a dynamic user event and will be processed in your event structure. This means you can keep your key down filter event to process the CTRL + KEY and SHIFT + KEY events.
    Example attached in 7.1
    cheers
    David
    Attachments:
    Catching Alt Key Press Poll with Events(151551).vi ‏89 KB

  • Key press detection when application is running in the background

    Is it possible to detect any key presses when the application is in the background?

    The key-related, pointer-related, and paint() methods will only be called while the Canvas is actually visible on the output device. These methods will therefore only be called on this Canvas object only after a call to showNotify() and before a call to hideNotify(). After hideNotify() has been called, none of the key, pointer, and paint methods will be called until after a subsequent call to showNotify() has returned. A call to a run() method resulting from callSerially() may occur irrespective of calls to showNotify() and hideNotify().
    The showNotify() method is called prior to the Canvas actually being made visible on the display, and the hideNotify() method is called after the Canvas has been removed from the display. The visibility state of a Canvas (or any other Displayable object) may be queried through the use of the Displayable.isShown() method. The change in visibility state of a Canvas may be caused by the application management software moving MIDlets between foreground and background states, or by the system obscuring the Canvas with system screens. Thus, the calls to showNotify() and hideNotify() are not under the control of the MIDlet and may occur fairly frequently. Application developers are encouraged to perform expensive setup and teardown tasks outside the showNotify() and hideNotify() methods in order to make them as lightweight as possible.
    The above answer you might have found in the JAVADOC, if you would have gone through the description of the Canvas class.
    Don't forget your DUKES as I had to search the JAVADOC for giving you the exact answer, which you should have done that yourself only!!!
    Shan!!!

  • Simultaneous ASDW key press undetected

    Hi guys, I'm currently developing a game that uses ASDW buttons for its movement system
    During one of my testing session, i realized that if i press 2 buttons simultaneously, (ex: A and S), both events would be dispatched one after the other (just like what i assume they would do)
    But if i press 3 buttons simultaneously, (ex: A, S and D), the last keypress (D) will go undetected
    Only after i release one of the keys (either A or S) will the last keypress be detected
    From what i read here ==> http://blog.nobien.net/2008/05/12/more-than-two-simultaneous-key-presses-and-keyboardevent key_down-woes/
    It is said that the problem might had been caused by a hardware issue
    From what i read at wikipedia http://en.wikipedia.org/wiki/Keyboard_%28computing%29
    [quote]
    Some low-quality keyboards suffer problems with rollover (that is, when multiple keys are pressed in  quick succession); some types of keyboard circuitry will register a  maximum number of keys at one time. This is undesirable for games (designed for multiple keypresses, e.g. casting a spell while holding  down keys to run) and undesirable for extremely fast typing (hitting new  keys before the fingers can release previous keys). A common side  effect of this shortcoming is called "phantom key blocking": on some  keyboards, pressing three keys simultaneously sometimes resulted in a  4th keypress being registered.
    Modern keyboards prevent this from happening by blocking the 3rd key  in certain key combinations, but while this prevents phantom input, it  also means that when two keys are depressed simultaneously, many of the  other keys on the keyboard will not respond until one of the two  depressed keys is lifted. With better keyboards designs, this seldom  happens in office programs, but it remains a problem in games even on  expensive keyboards, due to wildly different and/or configurable  key/command layouts in different games.
    [/quote]
    Question
    - What causes this problem is it a hardware issue or a language/flash player problem?
    Because i might be wrong, but i think i've played several non-flash games before that possess the ability to address multiple keypress at the same time
    - Can this problem be fixed?
    Code
    package
            import flash.display.Sprite;
            import flash.events.KeyboardEvent;
            public class Keyboard extends Sprite
                     public function Keyboard()
                            this.stage.addEventListener("keyDown", showKey);
                    public function showKey(event:KeyboardEvent)
                            trace(event.keyCode);
    Any help regarding the matter is greatly appreciated, thank you in advance~

    Quote
    do you think an update of the bios will do the trick?
    No, no, no, it won't, so please don't try it!
    Also, if you read the comments in the link you posted, your answer is there:
    Quote
    By Tony Fendall on May 12, 2008 | Reply
    The problem comes from the way in which the signal for the pressed keys moves from your keyboard to your computer. The signal is only 8-bit, and there are limits to how the signal can be changed to represent more than one key being pressed in combination.
    Long story short, the guys who designed the origional keyboards made a descision to support all two key combinations, and then selected as many three key combinations as they could support with the hardware. This meant that some combinations had to be left out, and they had to make a descision about which ones were more important.
    It just happens to be that they chose not to support three key combinations which involve the up arrow key. I do not think there is any solution to this problem…
    If you're playing games, why not just remap the keys in the game's settings?

  • ActiveX is stealing my key presses?

    Hi all,
    I have a fairly simple front panel with a handful of LabVIEW controls and an ActiveX container. In the ActiveX container is the Adobe Reader plugin.
    My vi works, but exhibits an odd behaviour that I presume is focus related. Once the ActiveX control is programmatically told to open and display a pdf file, it seems to steal the focus - permanently. If I select my LV string control, I can select any text in it, but key presses are all still sent to the Adobe Reader ActiveX control. If I click a few check boxes, then the string control again, it still doesn't accept my keyboard presses. The only way I've found to stop all this is to press tab, as this causes LabVIEW to move the focus away to the next control in the tab sequence. After that, all is ok until the next pdf file is read into the ActiveX control, and then I'm back at square one.
    Now I don't want to be telling my customers, "that's alright mate, just make sure you press the tab key after every pdf you generate and you'll be just fine."
    I've tried programmatically moving the focus away from the ActiveX control, and setting "SkipTabbing" to true, but this doesn't work.
    Anyone know how I can prevent this darned ActiveX control from permanently stealing my focus?
    Thoric (CLA, CLED, CTD and LabVIEW Champion)
    Solved!
    Go to Solution.

    nathand wrote:
    Unfortunately I don't have a good solution, but I can sympathize - I've had the same problem.
    Hi nathand, thanks for the sympathy 
    I've tried a few things, including navigating away from and straight back to the tab panel which houses the control to attempt to change the control focus. I've even tried simulating the keyboard TAB key press, which actually works - but only once for some annoyingly unfathomable reason! A second call to the ActiveX AdobeReader control makes it the focus again, but this time permanently. I've even tried putting the ActiveX control into a subvi that's hosted within a subpanel - no difference.
    Ultimately, like yourself, I've had to settle for a separate window, which I've called a Preview Window. Of course, putting my large ActiveX container in a separate subvi has left a dirty big empty space on my main vi front panel 
    I'm tempted to try to hide all borders around the preview window, and programmatically control its location such that it sits perfectly over the empty space within my main front panel. Of course, this means monitoring main panel window resizes and movements to maintain the correct relative locations, but it's do-able...
    I've got a new problem now - I thought about using Invoke to Get the Front Panel Image, then place this into a picture control. However, it seems the AdobeReaderActiveX control evades the LabVIEW Front Panel Image method, revealing nothing but the blank front panel colour behind the container. I can't seem to find a way around this either!
    Dam dam dam dam dam dam dam dam dam dam dam dam!!!
    Thoric (CLA, CLED, CTD and LabVIEW Champion)

  • Resuming from suspend breaks function key on laptop

    I have an Asus K40IN laptop.  Up until a few days ago, suspending worked perfectly.  However, now when I resume from suspend, my function key no longer works.  I use it for some global shortcuts like play/pause, volume up/down, brightness up/down, etc.  I checked in xev, and it's actually registering no key press at all.  However, if I press it twice quickly, it will start registering infinite presses of the d key (keycode 43).  This also completely incapacitates the keyboard -- many keys do not do what they should.  It stops if I press the actual d key once.
    I'm guessing the most likely cause is a recent update.  Here's my recent /var/log/pacman.log:
    [2010-01-08 14:45] upgraded kernel26-firmware (2.6.32.2-2 -> 2.6.32.3-1)
    [2010-01-08 14:45] >>> Updating module dependencies. Please wait ...
    [2010-01-08 14:45] >>> MKINITCPIO SETUP
    [2010-01-08 14:45] >>> ----------------
    [2010-01-08 14:45] >>> If you use LVM2, Encrypted root or software RAID,
    [2010-01-08 14:45] >>> Ensure you enable support in /etc/mkinitcpio.conf .
    [2010-01-08 14:45] >>> More information about mkinitcpio setup can be found here:
    [2010-01-08 14:45] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
    [2010-01-08 14:45]
    [2010-01-08 14:45] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2010-01-08 14:45] ==> Building image "default"
    [2010-01-08 14:45] ==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    [2010-01-08 14:45] :: Begin build
    [2010-01-08 14:45] :: Parsing hook [base]
    [2010-01-08 14:45] :: Parsing hook [udev]
    [2010-01-08 14:45] :: Parsing hook [autodetect]
    [2010-01-08 14:45] :: Parsing hook [pata]
    [2010-01-08 14:45] :: Parsing hook [scsi]
    [2010-01-08 14:45] :: Parsing hook [sata]
    [2010-01-08 14:45] :: Parsing hook [lvm2]
    [2010-01-08 14:45] :: Parsing hook [filesystems]
    [2010-01-08 14:45] :: Generating module dependencies
    [2010-01-08 14:45] :: Generating image '/boot/kernel26.img'...SUCCESS
    [2010-01-08 14:45] ==> SUCCESS
    [2010-01-08 14:45] ==> Building image "fallback"
    [2010-01-08 14:45] ==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    [2010-01-08 14:45] :: Begin build
    [2010-01-08 14:45] :: Parsing hook [base]
    [2010-01-08 14:45] :: Parsing hook [udev]
    [2010-01-08 14:45] :: Parsing hook [pata]
    [2010-01-08 14:46] :: Parsing hook [scsi]
    [2010-01-08 14:46] :: Parsing hook [sata]
    [2010-01-08 14:46] :: Parsing hook [lvm2]
    [2010-01-08 14:46] :: Parsing hook [filesystems]
    [2010-01-08 14:46] :: Generating module dependencies
    [2010-01-08 14:46] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
    [2010-01-08 14:46] ==> SUCCESS
    [2010-01-08 14:46] upgraded kernel26 (2.6.32.2-2 -> 2.6.32.3-1)
    [2010-01-08 14:46] upgraded zlib (1.2.3.3-3 -> 1.2.3.4-3)
    [2010-01-09 03:18] synchronizing package lists
    [2010-01-09 03:19] starting full system upgrade
    [2010-01-09 03:44] warning: /etc/arno-iptables-firewall/firewall.conf installed as /etc/arno-iptables-firewall/firewall.conf.pacnew
    [2010-01-09 03:44] upgraded arno-iptables-firewall (1.9.2g-1 -> 1.9.2h-1)
    [2010-01-09 20:46] synchronizing package lists
    [2010-01-09 20:47] starting full system upgrade
    [2010-01-09 20:47] starting full system upgrade
    [2010-01-10 03:06] synchronizing package lists
    [2010-01-10 03:06] starting full system upgrade
    [2010-01-10 03:08] In order to use the new nvidia module, exit Xserver and unload it manually.
    [2010-01-10 03:08] upgraded nvidia (190.53-1 -> 190.53-3)
    [2010-01-10 03:32] synchronizing package lists
    [2010-01-10 03:32] starting full system upgrade
    [2010-01-10 03:32] upgraded nvidia (190.53-3 -> 190.53-3)
    [2010-01-10 16:05] synchronizing package lists
    [2010-01-10 16:06] starting full system upgrade
    [2010-01-10 22:50] synchronizing package lists
    [2010-01-10 22:50] starting full system upgrade
    [2010-01-10 22:50] starting full system upgrade
    [2010-01-10 22:50] upgraded freeglut (2.4.0-4 -> 2.6.0-1)
    [2010-01-10 22:51] upgraded kid3 (1.2-1 -> 1.3-1)
    [2010-01-10 23:16] upgraded x264-git (20100107-1 -> 20100110-1)
    [2010-01-10 23:20] upgraded ffmpeg-svn (21082-1 -> 21132-1)
    [2010-01-10 23:27] upgraded mplayer-mt-git (20100107-1 -> 20100110-1)
    [2010-01-10 23:39] upgraded amarok-git (20100107-1 -> 20100110-1)
    [2010-01-10 23:39] upgraded depot_tools-svn (35767-1 -> 35900-1)
    [2010-01-11 00:25] upgraded chromium-svn (35770-1 -> 35902-1)
    [2010-01-11 02:19] installed speedcrunch (0.10.1-1)
    [2010-01-11 06:01] synchronizing package lists
    [2010-01-11 06:01] starting full system upgrade
    [2010-01-11 15:12] synchronizing package lists
    [2010-01-11 15:13] starting full system upgrade
    [2010-01-11 15:14] upgraded x264-git (20100110-1 -> 20100111-1)
    [2010-01-11 15:16] upgraded ffmpeg-svn (21132-1 -> 21152-1)
    [2010-01-11 15:19] upgraded mplayer-mt-git (20100110-1 -> 20100111-1)
    [2010-01-11 17:04] synchronizing package lists
    [2010-01-11 17:04] starting full system upgrade
    [2010-01-11 17:04] starting full system upgrade
    [2010-01-11 17:04] upgraded qtcurve-gtk2 (1.0.0-1 -> 1.0.1-1)
    [2010-01-12 15:32] synchronizing package lists
    [2010-01-12 15:33] starting full system upgrade
    [2010-01-12 15:33] starting full system upgrade
    [2010-01-12 15:34] upgraded dhcpcd (5.1.3-1 -> 5.1.4-1)
    [2010-01-12 15:34] upgraded live-media (2009.09.28-2 -> 2010.01.11-1)
    [2010-01-12 15:34] upgraded strigi (0.7.0-1 -> 0.7.1-1)
    Any ideas?

    Well I still haven't been able to fix it, but here's what I've figured out:
    - Some of the buttons (for example brightness adjust and turn screen off) do not have keycodes.  They seem to work directly through the bios, not through the operating system.  Other buttons (like volume control) do have keycodes, and do work through the OS.
    - If I unload the kernel module asus_laptop, the OS-dependent buttons stop working, but the others continue to work.
    - When I suspend and resume, all the buttons stop working.
    - Putting asus_laptop in SUSPEND_MODULES for pm-utils does not help.
    - Using s2ram from uswsusp does not help.
    - After a suspend and resume (so the buttons are all broken), when I press a button twice and start getting infinite presses of d, I get the following message in dmesg:
    Jan 17 10:45:53 firefly kernel: atkbd.c: Unknown key released (translated set 2, code 0xe1 on isa0060/serio0).
    Jan 17 10:45:53 firefly kernel: atkbd.c: Use 'setkeycodes e061 <keycode>' to make it known.
    I tried running the suggested command using a keycode for a volume button, but it didn't help.  It did stop this message from coming up in dmesg for that particular button, but the other behaviors were the same.
    I can't think of anything else to do to fix it.  Does this mean anything to anyone?

Maybe you are looking for