TouchPad

I have a firend that gave me her TouchPad. She has no instructions for me.  I have reset it, but now I get a network error message.  I don't know what to do to take her information off and load new apps and my new accounts on the touchpad.  Any suggestions to get me started?  I feel helpless with this TouchPad.

Hello Kspann,
Are you talking about the old HP Touchpad with HP's WebOS?
If so, that Touchpad is no longer usable as WebOS is no longer available and supported. The servers to make all those functions work has been taken down.
You should be able to install Android instead and use it that way. Go to the link below for further information about it.
http://h30434.www3.hp.com/t5/webOS-Hardware-and-Software/Android-on-Touchpad/m-p/4763996#M53973

Similar Messages

  • Touchpad no longer scrolls up and down on Satellite A

    So my HD crashed and i have to completely install Windows and all the Toshiba stuff with it a new.
    All is well - except for one thing, my touchpad no longer scrolls up and down using the side of it in IE or Chrome, but it still works in SeaMonkey.
    My Computer technician tells me it's an issue with getting some new driver for the touchpad, and i think i had to do that already about a year ago when i still had my original HD running.
    So i went to the Toshiba.ch website and tried to find something.
    I found all their "verfication" stuff and got inside the system and it instantly returned about 45 drivers by the looks of my "un"-driving eyeys they all could have been for whatever, so i searched especially for "touch pad" and yes, there was one for my Synapsis touchpad and XP as well, so i downloaded it - or i should say i opened it in Win Zip and checked first on the "readme file - wow, that was some Portugese in there, and that's when i kind of begun to feel lost.
    I check in at Toshiba.ch, get a ton of drivers in my face i have no clue whether i am supposed to download them all or what, and when i finally pick what i think i need the whole thing seems to be in Portugese, what the crickey in the afternoon is this???
    Anyway, before i download and try to install stuff i have no clue about i was hoping someone would actually give me a better hint on what i have to do exactly to get my touchpad to scroll up and down again also in Chrome, IE and where ever else.
    I use Service Pack 3 on Win XP Pro and was told that's maybe why the old original driver for this laptop needs to be updated, but which file, where to get it, and how to properly install it please anyone???

    Thanks for that, you confirm what i actually found out myself in the meantime.
    The way i got this issue solved was that i first tried to download and install the Synaptics driver from the Toshiba site - that simply failed miserably, glad with no negative side effects at least.
    Nesxt i used what unfortunately is way easier that sites like the Toshiba overload, i used Google to simply find the Synaptics website and instantly got the link to their driver download - eh voila, that actually gave me a .exe file, not an endless array of zipped files like the stuff on the Toshiba site in endless language versions!!!
    This worked, tested everything out alread since a while.
    - Which now leaves me with the question about the second driver you mentioned,
    Alps Electric
    what is that one needed for??
    I have not seen this name on my lappy before, so totally unsure about whether it still needs this dispite things are working everywhere, i did not even have to go into the Device Settings of the Mouse / touchpad to change or rearrange anything in there after the direct download from Synapsis, but well informed is always best, so if you could let me know about that
    Alps thing would appreciate...

  • Unable to see file system on touchpad over USB from Windows 7

    When I plug in my HP touchpad running 3.0.4 via USB to my PC running Windows 7 the device appears in device manager, but I don't see a new drive appear with a given drive letter under my computer.
    If I look at device manager in windows, I see two webos devices.  One is under disks.  The other is an unknown device with a question mark next to it.
    If I look at the disk from the disk management interface, the disk appears, but doesn't seem to have a drive letter nor a filesystem on it.
    If I plug the touchpad into an XP box, it wants to format the drive... which loses my apps.
    What did I break?  Any way of fixing this?
    Thanks!
    -- gyre ---
    Post relates to: HP TouchPad (WiFi)

    Before you disconnect the cord from the PC, are you correctly choosing "Eject", or the incorrect "Safely Remove Hardware" from the tool tray?
    I've heard the latter can cause confusion on a PC...
    Wyrenut
    I am a Volunteer here, not employed by HP.
    You too can become an HP Expert! Details HERE!
    If my post has helped you, click the Kudos Thumbs up!
    If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

  • Touchpad Adobe Reader stuck at opening screen

    Hi,
    I downloaded the update for adobe reader version 10.3.351 and now the reader is stuck at the opening screen. I have tried opening my pdf files through quickoffice, restarted the touchpad and nothing seems to work. WebOS doctor is not giving me any solutions as well. Does anyone have any other suggestions.
    Post relates to: HP TouchPad (WiFi)

    What have you tried so far? You mentioned webOS doctor; have you run this app yet to bring you device back to its defaults? After using webOS doctor you would have logged back into your webOS account and reloaded you apps to your device, this would have reloaded Adobe 10.3.351 which is the latest version of the app.
    Adobe 10.3.351 is the latest version available and is working fine on other Touchpad devices including my own. I am not sure why it would be hanging on your device. Have you installed Preware? If so did you install this back to your device after webOS doctor?

  • ConfigMgr 2012 R2 Client Failes to Install on HP EliteBook laptops with Synaptics Touchpad drivers

    I've come across a fairly frustrating issue that has been taking up way too much of my time that past week or so. The issue started a little after some of our larger sites were migrated from SCCM 2007 to SCCM 2012. I started getting complaints that one of
    our technical workstations (HP 8770w) was not deploying properly. I started investigating the issue and the problem involved the removal of the old ConfigMgr 2007 client and install of the new SCCM 2012 R2 client.
    The Windows 7 x64 OS WIM that I am using is one that was migrated from the 07 to 2012 environment and it has been working fine. During the Setup Windows and ConfigMgr step the old client is removed and the new one for the 2012 environment installs. There
    has not been any issues with this, but I feel something has changed now that we are deploying the 2012 R2 client.
    Back to the issue, what happens is that the ConfigMgr client fails to uninstall the old client. Looking in the client.msi_uninstall file you will see that it is unable to locate a couple of SCCM 2007 configmgr client patches that were installed so it can
    uninstall it. I get the "Couldn't find local patch ''. Looking for it at its source." line in the uninstall file. When I look for that under HKEY_CLASSES_ROOT\Installer\Patches the ENTIRE directory structure is empty. There is not a single item
    listed under patches.
    Since the only thing that happens in between the pushing down of the WIM and installing the configmgr client is the drivers that is where I started to look. I started over with the basics (disk and network driver) and it was able to complete the OSD process
    (like the other 30+ models we currently support). I added drivers one by one having the system re-image each time. When I got to the Synaptics TouchPad drivers the issue would return. I've tried around 5 different drivers offered from the vendor and they
    all result in the same behavior.
    I'm still actively troubleshooting how to FIX this issue, but I have no idea why this is going on. I thought I would share with the community on this issue and see if anyone else has observed this VERY odd behavior.
    Here is a snippet from the client.msi_uninstall log:
    === Verbose logging started: 1/15/2014  22:59:34  Build type: SHIP UNICODE 5.00.7601.00  Calling process: D:\_SMSTaskSequence\OSD\GAS000EF\ccmsetup.exe ===
    MSI (c) (6C:BC) [22:59:34:264]: Resetting cached policy values
    MSI (c) (6C:BC) [22:59:34:264]: Machine policy value 'Debug' is 0
    MSI (c) (6C:BC) [22:59:34:264]: ******* RunEngine:
               ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (6C:BC) [22:59:34:264]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (6C:BC) [22:59:34:264]: Grabbed execution mutex.
    MSI (c) (6C:BC) [22:59:34:264]: Cloaking enabled.
    MSI (c) (6C:BC) [22:59:34:264]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (6C:BC) [22:59:34:264]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (00:80) [22:59:34:264]: Running installation inside multi-package transaction {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
    MSI (s) (00:80) [22:59:34:264]: Grabbed execution mutex.
    MSI (s) (00:D4) [22:59:34:264]: Resetting cached policy values
    MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'Debug' is 0
    MSI (s) (00:D4) [22:59:34:264]: ******* RunEngine:
               ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (00:D4) [22:59:34:405]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (00:D4) [22:59:34:405]: End dialog not enabled
    MSI (s) (00:D4) [22:59:34:405]: Original package ==> C:\Windows\Installer\b8ba.msi
    MSI (s) (00:D4) [22:59:34:405]: Package we're running from ==> C:\Windows\Installer\b8ba.msi
    MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall Flags override found.
    MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: looking for appcompat database entry with ProductCode '{2609EDF1-34C4-4B03-B634-55F3B3BC4931}'.
    MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (00:D4) [22:59:34:420]: MSCOREE not loaded loading copy from system32
    MSI (s) (00:D4) [22:59:34:420]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
    MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
    MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
    MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (00:D4) [22:59:34:420]: User policy value 'DisableMedia' is 0
    MSI (s) (00:D4) [22:59:34:420]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
    MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {D478B8EE-EE0A-4004-980B-4D55533EE3C2} 3: 
    MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
    MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
    MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {D478B8EE-EE0A-4004-980B-4D55533EE3C2} -- orphaning this patch
    MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
    MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
    MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
    MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} 3: 
    MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
    MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
    MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} -- orphaning this patch
    MSI (s) (00:D4) [22:59:34:420]: SequencePatches starts. Product code: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}, Product version: 4.00.6487.2000, Upgrade code: {252DA259-82CA-4177-B8D0-49C78937BA3E}, Product language 1033
    MSI (s) (00:D4) [22:59:34:420]: SequencePatches returns success.
    MSI (s) (00:D4) [22:59:34:420]: Final Patch Application Order:
    MSI (s) (00:D4) [22:59:34:420]: Other Patches:
    MSI (s) (00:D4) [22:59:34:420]: Internal Exception during install operation: 0xc0000005 at 0x000007FEFDBF35E1.
    MSI (s) (00:D4) [22:59:34:420]: WER report disabled for silent install.
    MSI (s) (00:D4) [22:59:34:420]: Internal MSI error. Installer terminated prematurely.
    MSI (s) (00:D4) [22:59:34:420]: MainEngineThread is returning 1603
    MSI (s) (00:80) [22:59:34:420]: No System Restore sequence number for this installation.
    Unexpected Termination
    MSI (s) (00:80) [22:59:34:420]: User policy value 'DisableRollback' is 0
    MSI (s) (00:80) [22:59:34:420]: Machine policy value 'DisableRollback' is 0
    MSI (s) (00:80) [22:59:34:420]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (00:80) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (00:80) [22:59:34:420]: Restoring environment variables
    MSI (c) (6C:BC) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (6C:BC) [22:59:34:420]: MainEngineThread is returning 1603
    === Verbose logging stopped: 1/15/2014  22:59:34 ===

    @Narcoticoo
    I've not used the tool. This issue has also expanded since the original title as I'm getting the same behavior with the driver package that does not include the Touchpad driver anymore. I'm currently going back to just the network and storage driver to see
    if it works or not.
    However, this is the bigger issue I have:
    I have an older build called Build 5.7 internally. Using that WIM and the same driver package (original one that has the Touchpad driver included) it works without issue. Never had a problem.
    The new build is called Build 6.0 internally. This WIM and the same driver package has not been working at all.
    We support about 35 models with our current Windows 7 x64 image and I am having the same failure issue on four different HP models. They are the 8770w, ZBook 17, Z600 and Z820. The majority of the other systems are Dell devices. Just for transparency sakes,
    nothing Dell specific is in the core WIM that is captured.
    So, Build 5.7 can deploy just fine on all pieces of hardware with their old driver packages. The new Build 6.0 intalls on almost every platform fine with their old driver packages. These four HP systems are nothing but trouble though. I've opened a case
    with HP to see if they have noticed anything internally. I'm not too hopeful, but at least it is something. Maybe there is some odd conflict with a newer Windows patch or some odd dependency on older HP drivers. The new image has .NET 4.5.1, IE 10 and so forth.

  • HP Envy 15-q004tx Touchpad Issues

    Alright so I've been having some issues with my HP Envy 15-Q004TX and the touchpad.
    I recently purchased the laptop, and it was going fine.
    I decided to speed up the laptop and bought a 500GB SSD to put inside, and install windows. Altough this laptop did not come with a CD, through my University I was able to get an install of Windows 8.1 Professional free, and so I installed that.
    So what's my problem?
    Well every so often the touchpad begins to spazz out. The cursor begins to jump all over the place, sometimes it will automatically open windows 8's charm bar. Sometimes it just stops working for several seconds. But worst of all, sometimes the two finger scroll will just stop working, and instead of scrolling, the cursor just moves up.
    THe only way to fix it, is to go to the mouse settings in the control panel and select 'Reset Devices' and then it just works as normal. Sometimes the mouse will be find for half an hour to an hour, sometimes I will need to reset it after 5 minutes.
    What I have done.
    Reistalled Windows
    Completely uninstalled and deleted drivers
    Installed new drivers from the official HP page
    Tried other versions of drivers
    No matter what I do, it eventually stops working properly. This is incredibly annoying.
    If I cannot fix it, I'll take it back and get another.
    Thanks very much!

    I'm having the exact same issue! Nothing seems to work, HP Suggested a driver down grade, that worked for about 30 minutes.. And also to take my battery out and hold the power button to drain the laptop of static or something, niether worked for longer than an hour!

  • HP Envy 17334 Touchpad issues

    I wanted to let you know these are the things my touchpad has been doing: 
    -Very sluggish when first logging in to the computer.
    -Randomly opens up windows that the arrow hovers over but I don't click on.
    -Jumps around.
    -Makes the window half screen.
    -And just now when I logged on the slight tap on the left side doesn't work anymore and I have to click it all the way for it to take action.  Last week the right click didn't work.
    I have noticed that when you right click on the button on the lower right bar that looks like a index finger (says HP Control Zone when hovering over it) that if I go to Pointing Device Properties, then HP Control Zone Settings and click on Reset Devices, then click OK, that it worked just fine, but I have to do it EVERY time I log in to the computer, and then this last time when logging on, everything worked fine EXCEPT the left side light tap doesn't work: I have to click once hard instead of soft tap to get it to work when wanting to open up something.  
    I Googled problems people are having that are just like the ones I am having with the touchpad on the Envy and I have to say that this is quite frustrating and I'm scared I'll have the same results they have had, which with all of the things they tried -- only a few people seemed to have success with what troubleshooting techinques that were suggested to them.  Some have actually even exchanged and gotten brand new computers and then had the SAME PROBLEM!??  Is this because the touchpad is a relatively new design and not perfected?  I just bought this computer and like everything about it except obviously this problem -- A regular mouse works just fine, but I can't use a mouse most of the time because this computer will be used while travelling which I will be doing a lot of.  HELP!  If I send it in do be worked on will it even help as some of the people I've seen online are saying they are still experiencing problems.

    Hi @ray-and-kitty ,
    Thank you for visiting the HP Support Forums and Welcome. Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link to get the support number for your region. They will be happy to assist you immediately.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • HP ENVY 15-q014tx Issues with touchpad and mouse

    Dear HP,
    I recently bought this laptop and it have been giving me problems ever since.
    Let me start with the touchpad issue. It started out with my touchpad having issues but I shrugged it off as I thought it would've disappeared. It did. But it comes back ever so often I find it hard to ignore anymore. It works as and when it feels like working. The touchpad jumps around the page and clicks when I try to move it around. I can't even scroll up and down with my 2 fingers. I searched and there is no updates available for all my drivers.
    Another issue is when I plug in my mouse, the computer suddenly becomes extremely jumpy. For example, when I watch a video on youtube or any other website (I've tried on all browsers), the video will suddenly stop and it will emit a buzzing noise as though it has been hung and shortly after continues where it has left off. I realise if I change the power option from power saving to high performance this will occur less often. But recently, I feel that it happens too often even when it is plugged in and at high performance. I've called in about this issue and have been waiting for a return phone call ever since. I have yet to receive a return call. (I have since taken a video of what happened so you can better relate to what I meant)
    Another problem that I have made a temporary fix for is that my computer is unable to shutdown when I do a proper shutdown. I have since made a shortcut key that does a shutdown command to turn off the computer.
    I really hope I can get this fixed asap. I await your favourable reply.
    Best Regards,
    Edward
    Edit. I forgot to add that I ran a full hardware scan by restarting the computer, pressing F2 and then running a Extensive System Test. Everything passed

    I have just sent you a private message. If you are not sure how to check your forum messages, this post
    has instructions.
    Malygris1
    I work on behalf of HP
    Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
    Click Kudos Thumbs Up on the right to say “Thanks” for helping!

  • HP Envy 17 Touchpad Issues

    Product name: HP Envy m6 Notebook PC
    Product number: G5N44UA # ABA
    Hello, 
    For the past couple of weeks my touchpad has the pointer moving erratically on the screen. It sometimes responds to my commands to click or to scroll, but most of the time it moves very slow, highlights the text on the screen when I don't want it to, clicks on things I don't click on, and this morning the pointer was moving on its own without me even touching it. I've tried downloading the latest synaptics pointing device that I've read on other posts from the HP discussion boards, but to no avail. What should I do to fix this?  

    Please click on the below shown like to download and re-install the touchpad drivers:
    http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-129864-1&cc=us&dlc=en&lc=en...
    Hope this helps, for any further queries reply to the post and feel free to join us again
    "I work for Hewlett-Packard"
    * * * * * Click the "Purple Thumbs Up Icon in the lower right corner of a post" to say thanks * * * * *
    * * * * * Please mark Accept As Solution if it solves your problem * * * * *
    Regards,
    K N R K

  • HP Touchpad Issues - HP ENVY 15t-q100 - Needs Reflashed to Function Properly -

    I have the HP Slim Quad 100 Notebook with the HP Synaptics Touchpad.
    The touchpad intermittently stops working correctly.  Sometimes it's so bad that it's unusable. 
    I have done a little research and I found that the driver is causing the Touchpad to detect clicks and touch when there is none.  I've confirmed this by looking at the real-time Pressure graph tool that measures Touch Pressure.
    According to the Synaptics Pressure Graph tool (in the Synaptics folder, the red "Z" Icon [SynZMetr] is the name), the Touchpad is detecting pressure even when my hand is off the Touchpad altogether.  I suggest that anyone with this same issue confirm this themselves as well, during your time of random malfunction and sporadic movements.  You will see pressure in the pressure graph even when there is no contact with the touchpad.
    My temporary solution:
    Double click on the 'Reflash' folder in the Synaptics folder:
    C:\Program Files\Synaptics\SynTP\SynReflash
    After I reflash using this method, the issue is fixed immediately.  However, sometimes I have to do this on a daily basis!!!  What is the root issue and how can I fix it???
    Other Troubleshooting:
    I've reinstalled the newest driver a few times:
    Current Version:
    Synaptics Touchpad Driver -18.1.7.8 , Size: 187.8 MB  --  Oct 11, 2014
    File name: sp66500.exe
    ^ This did nothing to solve the problem from re-occurring. 

    Hi @Emmaus7 ,
    Thank you for visiting the HP Support Forums and Welcome. Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link to get the support number for your region. They will be happy to assist you immediately.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • Hp Envy X2 issues with the touchpad gestures

    I am experiencing some issues with the touchpad gestures after every time it wakes up. I am already update the drives posted in the hp web site, is anybody out there with the same issues?

    I couldn't find any graphic drivers for that notebook, but here is an updated chipset that is available for your notebook: http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-114872-1&cc=us&dlc=en&lc=en...
    It was released 6 days ago, so it might enable that option for you. It can't hurt to try it out. If not, you might just have to hold out a little bit until they update the driver. 
    -------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

  • Touchpad doesn't work - HP Pavilion DV4 - 2120ca

    Re: Pavilion DV4-2120ca
    Touchpad doesn't work after cleaning out the dust collection in the fan, heat sink area.  New Therma paste was applied.  
    Both the keyboard & touchpad were the 2 things that didn't work following reassembly.  The keyboard didn't work but able to use USB wireless mouse.  Couple days ago the replacement battery finally arrived, installed and charged for 12 hours.  After restart, the keyboard works as it should. 
    Unfortunately, touchpad still doesn't work. The light switch above the touchpad works, clicking on it turns white & amber but any movement scrolling doesn't work.
    We tried the following, but unsuccessful
    double tapping top left corner
    Hard Reset 
    Uninstalled ALPS & Synaptics -- reinstalled , restarted
    Updated Windows, HP, BIOS, Drivers
    Don't recall during reassembly if touchpad has a cable or connector.  If so, perhaps worth try to disconnect & reconnect to ensure correct connection.
    What do u advise to try next?
    Thank u
    ~ Gayle ~

    Did you connect the ribbon cable for the Touchpad. Often times there is one for the keyboard and one for the touchpad separately. Hopefully you have not damaged the ribbon cable. Just make sure you push it all the way in and seat it properly.
    **Click the KUDOS star on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
    **Click the KUDOS star on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • How do I disable the Symantics TouchPad on my HP Envy 14t notebook?

    I have tried to modify the sensitivity of the touchpad on my laptop, but it's still so touchy it's driving me crazy. The other issues I looked at here in the Community forum don't pertain to the machine or utilities I have.
    I want to COMPLETELY DISABLE it and use a plug-in mouse.  Where is the option to disable the touchpad?
    I have uninstalled the Symantic TouchPad driver, but the touchpad still shows up as a device as "PS/2 Compatible Mouse." When I open its Mouse Properties dialog, on the Driver tab, the Disable button is grayed out.
    How do I COMPELTELY DISABLE the touchpad and just use a plug-in mouse on the HP Envy 14t notebook?
    This question was solved.
    View Solution.

    @kiltinshire, 
    Thanks for posting back.  As you may be aware there are multiple versions of HP notebooks, most control functions are found in the user guide.  If you can not find it there then you would have to go to how to disable hard ware in windows.  That is a microsoft topic.
    You normally have 2 choices to physically shut it off.  First the touchpad has a little button in a corner depending on model.  Use a function key it will have a diagram of a square and a finger.  These methods have been used for years for turning your touchpad off. 
    Next is just google how to turn off touchpad in windows 8.  Here is a couple links that you may find useful that I found using that search.
    TouchPad and Keyboard
    How to Enable and Disable Touch Pad on HP ENVY
    Disable Laptop Touchpad in Windows 8 / 7
    How to disable laptop touch pad in windows 8
    Now if you are actually trying to find a way of permanently shutting off the touchpad so that it does not come on again you will have to dig into Windows help for that.  If Windows sees the hardware at start up it will by default try and load the base driver for it and most likely turn it on when you reboot.
    The only other way is to open up your notebook and disconnect the cable that goes from the touch pad to the motherboard so that does not happen.
    I am hoping that helps.
    Thank you again for posting and have a great day.
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    D5GR
    I work on behalf of HP

  • Lenovo e330 touchpad problem on ubuntu 12.04 LTS (32 bit)

    dear all,
    i've installed ubuntu 12.04 LTS 32 bit on my lenovo e330. everything almost fine, but my touchpad.
    everytime i tap to click on th touchpad, the pointer shifted a little bit to the other direction. that's not what i want...
    the pointer is ok if i click using mouse, or trackpad.
    i've adjust the sensitivity of the touchpad in setting > mouse and touchpad setting but no luck.
    i just thinking maybe i have to update the driver of the touchpad, but i can't find it using google...
    somebody can give me advice? thanks before.
    jojo

    Hi!
    https://bugs.launchpad.net/ubuntu/+source/xserver-​xorg-input-synaptics/+bug/1042069/comments/5
    this xorg.conf addition helped me, but i set VelocityScale 64.

  • XPS 13 9343 touchpad firmware

    I have one of the new XPS 13 laptops that's plagued with poor touchpad performance.  It looks like a new firmware was released to address this problem but it's only supported for installation on Windows 8.1.  I have already removed 8.1 and clean-installed Windows 7 and when I attempt flashing it crashes.  What are my options for installing this update?  Only thing I can think of is temporarily installing 8.1 just to install the update then switching back to Win7 as the firmware should be independent of the OS, but that would be a huge pain.
    Here's a thread (one of many) that outlines the poor performance and provides a link to the update: http://en.community.dell.com/support-forums/laptop/f/3518/t/19616659
    Any suggestions?
    Thanks,
    Todd

    Hi I'm the original poster.  I originally used an old work login of "RustonPaving" for ease but as this is turning into a bigger situation than I anticipated I'd like to transition this conversation over to this personal login I've just created.  I'll send you the friend request from this profile in a moment.
    Thanks for the help so far on this, although I've got to disagree with you on the firmware issue.  Firmware is generally installed onto an EEPROM on the hardware device and has nothing to do with the hard drive and would therefore persist through OS changes, hard drive replacements, formatting, etc.  Anyway, don't want to belabor the point.  Let me know what you're able to make happen on your end.
    To clarify the problems I'm having as there seem to be several different symptoms floating around, here's a list of the issues I'm having:
    - 2 finger scrolling is difficult, it generally doesn't register and instead just moves the cursor up and down.
    - Finger tapping can be overly sensitive and cause unwanted clicks.  The only sensitivity setting in the Dell touchpad utility effects overall sensitivity, not just tapping.  So if I decrease sensitivity it makes it almost impossible to even move the cursor around.
    Thanks,
    Todd

  • [Solved]Synaptics Touchpad not working at all on Fujitsu Siemens UH552

    Hi,
    I have just installed Arch on my Fujitsu Siemens UH552 laptop. Everything works except for the touchpad which seems to get loaded by Xorg, but when in X it doesn't work. I have tried both using /dev/input/event* and /dev/input/mouse0 as device paths, neither works.
    xf86-input-evdev and xf86-input-synaptics are installed.
    I have tried running both with the default 10-evdev.conf, with 10-synaptics.conf, with both, and without both.
    TLDR SOLUTION: https://bbs.archlinux.org/viewtopic.php … 3#p1189603
    My current 10-synaptics.conf:
    Section "InputClass"
    Identifier "Touchpad Catchall"
    MatchIsTouchpad "on"
    MatchDevicePath "/dev/input/event*"
    Driver "synaptics"
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    EndSection
    Xorg.0.log
    [ 2275.127]
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    [ 2275.130] X Protocol Version 11, Revision 0
    [ 2275.131] Build Operating System: Linux 3.4.8-1-ARCH x86_64
    [ 2275.132] Current Operating System: Linux corvo 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64
    [ 2275.132] Kernel command line: root=/dev/sda2 rootflags=subvol=__active ro initrd=/boot/initramfs-linux.img BOOT_IMAGE=/boot/vmlinuz-linux
    [ 2275.134] Build Date: 27 August 2012 08:04:39AM
    [ 2275.135]
    [ 2275.136] Current version of pixman: 0.26.2
    [ 2275.138] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2275.138] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2275.142] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 1 13:16:01 2012
    [ 2275.143] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2275.144] (==) No Layout section. Using the first Screen section.
    [ 2275.144] (==) No screen section available. Using defaults.
    [ 2275.144] (**) |-->Screen "Default Screen Section" (0)
    [ 2275.144] (**) | |-->Monitor "<default monitor>"
    [ 2275.144] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 2275.144] (**) | |-->Device "Intel Graphics"
    [ 2275.144] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 2275.144] (==) Automatically adding devices
    [ 2275.144] (==) Automatically enabling devices
    [ 2275.144] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 2275.144] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 2275.144] Entry deleted from font path.
    [ 2275.144] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 2275.144] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 2275.144] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2275.144] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2275.144] (II) Loader magic: 0x7c8b00
    [ 2275.144] (II) Module ABI versions:
    [ 2275.144] X.Org ANSI C Emulation: 0.4
    [ 2275.144] X.Org Video Driver: 12.1
    [ 2275.144] X.Org XInput driver : 16.0
    [ 2275.144] X.Org Server Extension : 6.0
    [ 2275.144] (--) PCI:*(0:0:2:0) 8086:0166:10cf:16c2 rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00002000/64
    [ 2275.144] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 2275.144] (II) LoadModule: "extmod"
    [ 2275.144] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 2275.145] (II) Module extmod: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] Module class: X.Org Server Extension
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension MIT-SCREEN-SAVER
    [ 2275.145] (II) Loading extension XFree86-VidModeExtension
    [ 2275.145] (II) Loading extension XFree86-DGA
    [ 2275.145] (II) Loading extension DPMS
    [ 2275.145] (II) Loading extension XVideo
    [ 2275.145] (II) Loading extension XVideo-MotionCompensation
    [ 2275.145] (II) Loading extension X-Resource
    [ 2275.145] (II) LoadModule: "dbe"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 2275.145] (II) Module dbe: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] Module class: X.Org Server Extension
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension DOUBLE-BUFFER
    [ 2275.145] (II) LoadModule: "glx"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2275.145] (II) Module glx: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (==) AIGLX enabled
    [ 2275.145] (II) Loading extension GLX
    [ 2275.145] (II) LoadModule: "record"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 2275.145] (II) Module record: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.13.0
    [ 2275.145] Module class: X.Org Server Extension
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension RECORD
    [ 2275.145] (II) LoadModule: "dri"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 2275.145] (II) Module dri: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.0.0
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension XFree86-DRI
    [ 2275.145] (II) LoadModule: "dri2"
    [ 2275.145] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2275.145] (II) Module dri2: vendor="X.Org Foundation"
    [ 2275.145] compiled for 1.12.4, module version = 1.2.0
    [ 2275.145] ABI class: X.Org Server Extension, version 6.0
    [ 2275.145] (II) Loading extension DRI2
    [ 2275.145] (II) LoadModule: "intel"
    [ 2275.146] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 2275.146] (II) Module intel: vendor="X.Org Foundation"
    [ 2275.146] compiled for 1.12.3.901, module version = 2.20.5
    [ 2275.146] Module class: X.Org Video Driver
    [ 2275.146] ABI class: X.Org Video Driver, version 12.1
    [ 2275.146] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
    Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
    Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
    Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
    Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
    Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
    Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
    Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
    Haswell Server (GT2+), Haswell SDV Desktop (GT1),
    Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
    Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
    Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
    Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
    Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
    Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
    Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
    Haswell ULT Server (GT1), Haswell ULT Server (GT2),
    Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
    Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
    Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
    Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
    Haswell CRW Server (GT2), Haswell CRW Server (GT2+)
    [ 2275.146] (--) using VT number 7
    [ 2275.149] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.149] drmOpenDevice: open result is 7, (OK)
    [ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 2275.150] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.150] drmOpenDevice: open result is 7, (OK)
    [ 2275.150] drmOpenByBusid: drmOpenMinor returns 7
    [ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 2275.150] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.150] drmOpenDevice: open result is 8, (OK)
    [ 2275.150] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 2275.150] drmOpenDevice: node name is /dev/dri/card0
    [ 2275.150] drmOpenDevice: open result is 8, (OK)
    [ 2275.150] drmOpenByBusid: drmOpenMinor returns 8
    [ 2275.150] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 2275.150] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 2275.150] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 2275.150] (==) intel(0): RGB weight 888
    [ 2275.150] (==) intel(0): Default visual is TrueColor
    [ 2275.150] (**) intel(0): Option "AccelMethod" "sna"
    [ 2275.150] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
    [ 2275.151] (**) intel(0): Framebuffer tiled
    [ 2275.151] (**) intel(0): Pixmaps tiled
    [ 2275.151] (**) intel(0): 3D buffers tiled
    [ 2275.151] (**) intel(0): Throttling enabled
    [ 2275.151] (**) intel(0): Delayed flush enabled
    [ 2275.151] (**) intel(0): "Tear free" disabled
    [ 2275.151] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 2275.151] (II) intel(0): Output LVDS1 has no monitor section
    [ 2275.152] (II) intel(0): found backlight control interface acpi_video0 (type 'firmware')
    [ 2275.152] (II) intel(0): Output VGA1 has no monitor section
    [ 2275.153] (II) intel(0): Output HDMI1 has no monitor section
    [ 2275.193] (II) intel(0): Output DP1 has no monitor section
    [ 2275.193] (II) intel(0): EDID for output LVDS1
    [ 2275.193] (II) intel(0): Manufacturer: LGD Model: 371 Serial#: 0
    [ 2275.193] (II) intel(0): Year: 2012 Week: 0
    [ 2275.193] (II) intel(0): EDID Version: 1.3
    [ 2275.193] (II) intel(0): Digital Display Input
    [ 2275.193] (II) intel(0): Max Image Size [cm]: horiz.: 29 vert.: 16
    [ 2275.193] (II) intel(0): Gamma: 2.20
    [ 2275.193] (II) intel(0): No DPMS capabilities specified
    [ 2275.193] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 2275.193] (II) intel(0): First detailed timing is preferred mode
    [ 2275.193] (II) intel(0): redX: 0.589 redY: 0.347 greenX: 0.343 greenY: 0.555
    [ 2275.193] (II) intel(0): blueX: 0.160 blueY: 0.124 whiteX: 0.313 whiteY: 0.329
    [ 2275.193] (II) intel(0): Manufacturer's mask: 0
    [ 2275.193] (II) intel(0): Supported detailed timing:
    [ 2275.193] (II) intel(0): clock: 70.0 MHz Image Size: 293 x 165 mm
    [ 2275.193] (II) intel(0): h_active: 1366 h_sync: 1402 h_sync_end 1438 h_blank_end 1476 h_border: 0
    [ 2275.193] (II) intel(0): v_active: 768 v_sync: 772 v_sync_end 780 v_blanking: 790 v_border: 0
    [ 2275.193] (II) intel(0): LG Display
    [ 2275.193] (II) intel(0): LP133WH2-TLF1
    [ 2275.193] (II) intel(0): EDID (in hex):
    [ 2275.193] (II) intel(0): 00ffffffffffff0030e4710300000000
    [ 2275.193] (II) intel(0): 00160103801d10780afc359658578e29
    [ 2275.193] (II) intel(0): 1f505400000001010101010101010101
    [ 2275.193] (II) intel(0): 010101010101581b566e500016302424
    [ 2275.194] (II) intel(0): 480025a5100000190000000000000000
    [ 2275.194] (II) intel(0): 00000000000000000000000000fe004c
    [ 2275.194] (II) intel(0): 4720446973706c61790a2020000000fe
    [ 2275.194] (II) intel(0): 004c503133335748322d544c463100ce
    [ 2275.194] (II) intel(0): EDID vendor "LGD", prod id 881
    [ 2275.194] (II) intel(0): Printing DDC gathered Modelines:
    [ 2275.194] (II) intel(0): Modeline "1366x768"x0.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
    [ 2275.194] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
    [ 2275.194] (II) intel(0): Printing probed modes for output LVDS1
    [ 2275.194] (II) intel(0): Modeline "1366x768"x60.0 70.00 1366 1402 1438 1476 768 772 780 790 -hsync -vsync (47.4 kHz eP)
    [ 2275.194] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
    [ 2275.194] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
    [ 2275.194] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
    [ 2275.194] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
    [ 2275.194] (II) intel(0): EDID for output VGA1
    [ 2275.195] (II) intel(0): EDID for output HDMI1
    [ 2275.236] (II) intel(0): EDID for output DP1
    [ 2275.236] (II) intel(0): Output LVDS1 connected
    [ 2275.236] (II) intel(0): Output VGA1 disconnected
    [ 2275.236] (II) intel(0): Output HDMI1 disconnected
    [ 2275.236] (II) intel(0): Output DP1 disconnected
    [ 2275.236] (II) intel(0): Using exact sizes for initial modes
    [ 2275.236] (II) intel(0): Output LVDS1 using initial mode 1366x768
    [ 2275.236] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 2275.236] (**) intel(0): Display dimensions: (290, 160) mm
    [ 2275.236] (**) intel(0): DPI set to (119, 121)
    [ 2275.236] (II) Loading sub module "dri2"
    [ 2275.236] (II) LoadModule: "dri2"
    [ 2275.237] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2275.237] (II) Module dri2: vendor="X.Org Foundation"
    [ 2275.237] compiled for 1.12.4, module version = 1.2.0
    [ 2275.237] ABI class: X.Org Server Extension, version 6.0
    [ 2275.237] (==) Depth 24 pixmap format is 32 bpp
    [ 2275.237] (II) intel(0): SNA initialized with IvyBridge backend
    [ 2275.237] (==) intel(0): Backing store disabled
    [ 2275.237] (==) intel(0): Silken mouse enabled
    [ 2275.237] (II) intel(0): HW Cursor enabled
    [ 2275.237] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 2275.238] (==) intel(0): DPMS enabled
    [ 2275.239] (II) intel(0): [DRI2] Setup complete
    [ 2275.239] (II) intel(0): [DRI2] DRI driver: i965
    [ 2275.239] (II) intel(0): direct rendering: DRI2 Enabled
    [ 2275.239] (==) intel(0): hotplug detection: "enabled"
    [ 2275.239] (--) RandR disabled
    [ 2275.239] (II) Initializing built-in extension Generic Event Extension
    [ 2275.239] (II) Initializing built-in extension SHAPE
    [ 2275.239] (II) Initializing built-in extension MIT-SHM
    [ 2275.239] (II) Initializing built-in extension XInputExtension
    [ 2275.239] (II) Initializing built-in extension XTEST
    [ 2275.239] (II) Initializing built-in extension BIG-REQUESTS
    [ 2275.239] (II) Initializing built-in extension SYNC
    [ 2275.239] (II) Initializing built-in extension XKEYBOARD
    [ 2275.239] (II) Initializing built-in extension XC-MISC
    [ 2275.239] (II) Initializing built-in extension SECURITY
    [ 2275.239] (II) Initializing built-in extension XINERAMA
    [ 2275.239] (II) Initializing built-in extension XFIXES
    [ 2275.239] (II) Initializing built-in extension RENDER
    [ 2275.239] (II) Initializing built-in extension RANDR
    [ 2275.239] (II) Initializing built-in extension COMPOSITE
    [ 2275.239] (II) Initializing built-in extension DAMAGE
    [ 2275.250] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 2275.250] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 2275.250] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 2275.250] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 2275.250] (II) AIGLX: Loaded and initialized i965
    [ 2275.250] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 2275.251] (II) intel(0): switch to mode 1366x768 on crtc 3 (pipe 0)
    [ 2275.276] (II) intel(0): Setting screen physical size to 361 x 203
    [ 2275.319] (II) config/udev: Adding input device Power Button (/dev/input/event6)
    [ 2275.319] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2275.319] (II) LoadModule: "evdev"
    [ 2275.319] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 2275.320] (II) Module evdev: vendor="X.Org Foundation"
    [ 2275.320] compiled for 1.12.3.901, module version = 2.7.3
    [ 2275.320] Module class: X.Org XInput Driver
    [ 2275.320] ABI class: X.Org XInput driver, version 16.0
    [ 2275.320] (II) Using input driver 'evdev' for 'Power Button'
    [ 2275.320] (**) Power Button: always reports core events
    [ 2275.320] (**) evdev: Power Button: Device: "/dev/input/event6"
    [ 2275.320] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2275.320] (--) evdev: Power Button: Found keys
    [ 2275.320] (II) evdev: Power Button: Configuring as keyboard
    [ 2275.320] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6"
    [ 2275.320] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 2275.320] (**) Option "xkb_rules" "evdev"
    [ 2275.320] (**) Option "xkb_model" "evdev"
    [ 2275.320] (**) Option "xkb_layout" "se"
    [ 2275.355] (II) config/udev: Adding input device Fujitsu FUJ02E3 (/dev/input/event3)
    [ 2275.356] (**) Fujitsu FUJ02E3: Applying InputClass "evdev keyboard catchall"
    [ 2275.356] (II) Using input driver 'evdev' for 'Fujitsu FUJ02E3'
    [ 2275.356] (**) Fujitsu FUJ02E3: always reports core events
    [ 2275.356] (**) evdev: Fujitsu FUJ02E3: Device: "/dev/input/event3"
    [ 2275.356] (--) evdev: Fujitsu FUJ02E3: Vendor 0 Product 0x6
    [ 2275.356] (--) evdev: Fujitsu FUJ02E3: Found keys
    [ 2275.356] (II) evdev: Fujitsu FUJ02E3: Configuring as keyboard
    [ 2275.356] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/FUJ02E3:00/input/input3/event3"
    [ 2275.356] (II) XINPUT: Adding extended input device "Fujitsu FUJ02E3" (type: KEYBOARD, id 7)
    [ 2275.356] (**) Option "xkb_rules" "evdev"
    [ 2275.356] (**) Option "xkb_model" "evdev"
    [ 2275.356] (**) Option "xkb_layout" "se"
    [ 2275.357] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
    [ 2275.357] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 2275.357] (II) Using input driver 'evdev' for 'Video Bus'
    [ 2275.357] (**) Video Bus: always reports core events
    [ 2275.357] (**) evdev: Video Bus: Device: "/dev/input/event9"
    [ 2275.357] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 2275.357] (--) evdev: Video Bus: Found keys
    [ 2275.357] (II) evdev: Video Bus: Configuring as keyboard
    [ 2275.357] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input9/event9"
    [ 2275.357] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 2275.358] (**) Option "xkb_rules" "evdev"
    [ 2275.358] (**) Option "xkb_model" "evdev"
    [ 2275.358] (**) Option "xkb_layout" "se"
    [ 2275.359] (II) config/udev: Adding input device Fujitsu FUJ02B1 (/dev/input/event2)
    [ 2275.359] (**) Fujitsu FUJ02B1: Applying InputClass "evdev keyboard catchall"
    [ 2275.359] (II) Using input driver 'evdev' for 'Fujitsu FUJ02B1'
    [ 2275.359] (**) Fujitsu FUJ02B1: always reports core events
    [ 2275.359] (**) evdev: Fujitsu FUJ02B1: Device: "/dev/input/event2"
    [ 2275.359] (--) evdev: Fujitsu FUJ02B1: Vendor 0 Product 0x6
    [ 2275.359] (--) evdev: Fujitsu FUJ02B1: Found keys
    [ 2275.359] (II) evdev: Fujitsu FUJ02B1: Configuring as keyboard
    [ 2275.359] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/FUJ02B1:00/input/input2/event2"
    [ 2275.359] (II) XINPUT: Adding extended input device "Fujitsu FUJ02B1" (type: KEYBOARD, id 9)
    [ 2275.359] (**) Option "xkb_rules" "evdev"
    [ 2275.359] (**) Option "xkb_model" "evdev"
    [ 2275.359] (**) Option "xkb_layout" "se"
    [ 2275.360] (II) config/udev: Adding input device Power Button (/dev/input/event5)
    [ 2275.360] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2275.360] (II) Using input driver 'evdev' for 'Power Button'
    [ 2275.360] (**) Power Button: always reports core events
    [ 2275.360] (**) evdev: Power Button: Device: "/dev/input/event5"
    [ 2275.360] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2275.360] (--) evdev: Power Button: Found keys
    [ 2275.360] (II) evdev: Power Button: Configuring as keyboard
    [ 2275.361] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5/event5"
    [ 2275.361] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 10)
    [ 2275.361] (**) Option "xkb_rules" "evdev"
    [ 2275.361] (**) Option "xkb_model" "evdev"
    [ 2275.361] (**) Option "xkb_layout" "se"
    [ 2275.362] (II) config/udev: Adding input device Lid Switch (/dev/input/event4)
    [ 2275.362] (II) No input driver specified, ignoring this device.
    [ 2275.362] (II) This device may have been added with another device file.
    [ 2275.362] (II) config/udev: Adding input device FJ Camera (/dev/input/event7)
    [ 2275.362] (**) FJ Camera: Applying InputClass "evdev keyboard catchall"
    [ 2275.362] (II) Using input driver 'evdev' for 'FJ Camera'
    [ 2275.362] (**) FJ Camera: always reports core events
    [ 2275.362] (**) evdev: FJ Camera: Device: "/dev/input/event7"
    [ 2275.363] (--) evdev: FJ Camera: Vendor 0x10f1 Product 0x1a44
    [ 2275.363] (--) evdev: FJ Camera: Found keys
    [ 2275.363] (II) evdev: FJ Camera: Configuring as keyboard
    [ 2275.363] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input7/event7"
    [ 2275.363] (II) XINPUT: Adding extended input device "FJ Camera" (type: KEYBOARD, id 11)
    [ 2275.363] (**) Option "xkb_rules" "evdev"
    [ 2275.363] (**) Option "xkb_model" "evdev"
    [ 2275.363] (**) Option "xkb_layout" "se"
    [ 2275.364] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
    [ 2275.364] (II) No input driver specified, ignoring this device.
    [ 2275.364] (II) This device may have been added with another device file.
    [ 2275.364] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11)
    [ 2275.364] (II) No input driver specified, ignoring this device.
    [ 2275.364] (II) This device may have been added with another device file.
    [ 2275.365] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
    [ 2275.365] (II) No input driver specified, ignoring this device.
    [ 2275.365] (II) This device may have been added with another device file.
    [ 2275.365] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 2275.365] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 2275.365] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 2275.366] (**) AT Translated Set 2 keyboard: always reports core events
    [ 2275.366] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 2275.366] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 2275.366] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 2275.366] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 2275.366] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
    [ 2275.366] (**) Option "xkb_rules" "evdev"
    [ 2275.366] (**) Option "xkb_model" "evdev"
    [ 2275.366] (**) Option "xkb_layout" "se"
    [ 2275.366] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8)
    [ 2275.366] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Touchpad Catchall"
    [ 2275.366] (II) LoadModule: "synaptics"
    [ 2275.366] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 2275.367] (II) Module synaptics: vendor="X.Org Foundation"
    [ 2275.367] compiled for 1.12.2, module version = 1.6.2
    [ 2275.367] Module class: X.Org XInput Driver
    [ 2275.367] ABI class: X.Org XInput driver, version 16.0
    [ 2275.367] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 2275.367] (**) Option "Device" "/dev/input/event8"
    [ 2275.367] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 2275.367] (**) Option "TapButton1" "1"
    [ 2275.367] (**) Option "TapButton2" "2"
    [ 2275.367] (**) Option "TapButton3" "3"
    [ 2275.367] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 2275.367] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 2275.367] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input8/event8"
    [ 2275.368] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
    [ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
    [ 2275.368] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.040
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 2275.368] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 2275.368] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 2275.368] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 2275.368] (II) No input driver specified, ignoring this device.
    [ 2275.368] (II) This device may have been added with another device file.
    [ 2275.368] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
    [ 2275.368] (II) No input driver specified, ignoring this device.
    [ 2275.368] (II) This device may have been added with another device file.
    xinput
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Fujitsu FUJ02E3 id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Fujitsu FUJ02B1 id=9 [slave keyboard (3)]
    ↳ Power Button id=10 [slave keyboard (3)]
    ↳ FJ Camera id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    running
    dmesg | grep -i synaptics
    doesn't show anything. However running
    dmesg | grep -i psmouse
    returns a lot of
    psmouse serio1: bad data from KBC - timeout
    Last edited by flako (2012-11-08 09:44:59)

    I have tried doing that with both linux mint, and now fedora live usb. Neither one loads the touchpad correctly.  So yeah, our problems weren't really related
    Anyway, I tried looking into the
    psmouse serio1: bad data from KBC - timeout
    messages, and tried running psmouse proto (defined in /etc/modprobe.conf/psmouse.conf) as both raw and imps as per https://answers.launchpad.net/ubuntu/+s … ion/206950 Unfortunately, that didn't solve anything. Using the raw setting meant that the touchpad wasn't loaded at all (as in not appearing in the Xorg.log at all).
    The laptop is quite new, but at the same time what i figured from the touchpad vendor & product ID, the touchpad itself isn't. So it should technically work. Before installing arch i booted into windows to see if everything worked, and found no issues with the touchpad. So I have ruled out any hardware errors. Maybe its just the Fn-key that doesn't work yet in Linux? But that doesn't explain the "psmouse serio1: bad data from KBC - timeout" Any pointers to where I should look/ what commands I should run to delve deeper into this issue?
    Last edited by flako (2012-09-09 12:10:51)

Maybe you are looking for