The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    NP8130 Keyboard Chaos

    Discussion in 'Sager and Clevo' started by ganzonomy, Nov 20, 2011.

  1. ganzonomy

    ganzonomy Notebook Deity

    Reputations:
    1,169
    Messages:
    919
    Likes Received:
    50
    Trophy Points:
    41
    I have a NP8130 (specs in sig) and although it mostly behaves, occasionally while typing on it, the computer will decide that "Ctrl" is permanently pressed and it results in no longer being able to type. This happens at random and then the only solution is for me to log off and log back in to reset (at some level) windows. What should I do, Logging off and back on is quick, but it is a hassle when my Sager goes into "big baby" mode.

    Jason
     
  2. giggidy

    giggidy Notebook Geek

    Reputations:
    0
    Messages:
    85
    Likes Received:
    1
    Trophy Points:
    16
    Have you installed all of the updated drivers?
     
  3. Anthony@MALIBAL

    Anthony@MALIBAL Company Representative

    Reputations:
    616
    Messages:
    2,771
    Likes Received:
    3
    Trophy Points:
    56
    Has this just started randomly and all of a sudden? If you're comfortable checking, your keyboard ribbon cable may have been knocked loose. Or you could potentially have some software issue, but I can't think of what software would do that. Here's a link to the service manual for this machine, courtesy of NBR member Theriko:

    P15xHM_ESM.zip

    Be careful if you check the ribbon cable, as it's very delicate.
     
  4. ganzonomy

    ganzonomy Notebook Deity

    Reputations:
    1,169
    Messages:
    919
    Likes Received:
    50
    Trophy Points:
    41
    It seems it was a chipset driver issue. I put back in the sager-spec one and so far it seems to be working fine.
     
  5. giggidy

    giggidy Notebook Geek

    Reputations:
    0
    Messages:
    85
    Likes Received:
    1
    Trophy Points:
    16
    glad to hear