Spectre x360 (13-4101dx) Synaptics Touchpad Issue
Hello, I just bought a new Spectre x360 (13-4101dx, pre-loaded with Windows 10) and I'm having issues with the Synaptics touchpad. After a Windows update, the driver was updated to version 19.0.12.95. I have reverse scrolling disabled but for some applications, the two finger scrolling is still reversed. Applications like Google Chrome and Device Manager work fine, the reverse scrolling is disabled. However, for applications like Windows settings, Microsoft Edge, and pretty much everything Windows-related, it seems to be permanently reversed. Also, every time I restart my laptop, all of the settings are reverted back to default. Now, on my HP Envy 15-j000, I have the same driver (19.0.12.95) and I don't face the same issues with reverse scrolling being "permanent" on Windows-related applications. However, the settings do still reset itself after every reboot. How can I fix this? Will Synaptics be releasing a fixed driver for this or am I just missing something? I absolutely hate reverse scrolling and only a small handful of my applications actually run with it disabled...
I have this same issue with my HP OMEN using driver 19.0.12.95, windows update says this is the latest driver. Scrolling remains inverted in some apps/settings. I fixed this issue by reverting to an older driver (18.1.30.2), scrolling is now uniform. Kinda annoying that I had to fix it this way, but I had to go the HP Omen driver/support page and download the driver for the synaptics touchpad (even though HP's website insists you use Windows update for Windows 10). I then had to install the old driver, go into device manager and roll back the driver to 18.1.30.2 - you have to do this otherwise Win 10 will just use the latest driver. After that you can change the setting in the synaptics clickpad settings and it will be uniform. This was what worked for me.
Similar Messages
-
I just wanted to chime in here on the Synaptics Touchpad issues...
I have a Toshiba L305D-S5934 Laptop with an AMD Turion X2 Dual Core Processor, it has a Synaptics touchpad as do most laptops these days and I have run into the following problems: I am running Windows 7 RC Build 7100 (an official download not a torrent download) and my Synaptics Touchpad shows up as a PS2 compatable mouse in device manager. If I download the drivers that come through Windows Update they seem to work fine untill I reboot my system, at reboot just after the Windows 7 splash screen, she blue screens with a memory dump going to somewhere and then does an automatic restart, if I attempt to start windows normally after the restart she bluescreens again with the same results, and this will go on time and time again until I either go into safe mode and remove the Synaptics driver or let startup repair do its thing or do a system restore, all of which leaves me with a Synaptics Touchpad with erattic behavior, that loses its scrolling functionality, and is hypersensitive almost to the point that I can't type much of anything without the cursor jumping around all over the place and relocating like it has a mind of its own. Now Toshiba has something called Toshiba's Value Added Package (not much value there for 64 bit systems it seems this thing was a pain in Vista x64 and it is more of a pain in Windows 7 x64) I will not install the Value added Package until I am convinced t hat Toshiba or whoever makes it gives a rat's rear-end about 64 bit systems and Windows 7 the last time I tried to install it gave all kinds of problems and produced some blue screens of its own I believe. The Value Added Package however includes Toshiba's Flash Cards Utility that makes the Fn key work and gives access to disabling the Synaptics touchpad (you can do this in the driver as well, but when the driver is installed well she bluescreens except in safe mode) The Synaptics driver seems to do okay in safe mode so that could mean that another driver is causing the conflict but something is not wanting to lay nice with the Synaptics driver. I must note however that the Synaptics driver worked just fine in Windows Vista x64. Also I have downloaded the driver from Toshiba's site, the 64 bit Synaptics driver from the Synaptic's site and a couple of others, the one that came closeest to working the best was a version 12.something for HP laptops but the option to disable the touchpad wasn't in the driver. I usually use a mouse with my laptop but I use the touchpad when I take it places with me sometimes, it would be nice to have full functionality of both mouse and touchpad and to be able to disable the touchpad when an external pointing device is attached the way I could in Vista but right now I would settle to just be able to disable the touchpad until this is resolved so I can use the laptop without the cursor jumping all over the place and seemingly having a mind of it's own. As a side note I am very careful about allowing Windows Update to install any updates that it wants at this poing, more than once it has installed things that gave me bluescreens at reboot most notably the Toshiba Value Added Package and the Synaptics driver and maybe an Atheros Wireless driver but it does not yet seem to have the best interests of my PC at heart. On the other hand I have the 32 bit version installed on a Desktop PC with an old Athlon XP 2000+ and 2 GB of Ram it runs wonderfully nearly as well as Windows XP but there is no Synaptics touchpad on the desktop of course, and no Toshiba Value Added Package.
CharlesI have had a similar problem, windows update does NOT update the synaptics touchpad. I have a Toshiba Windows 7 and I did everything that was told by man and beast.
Finally, I went to control panel again, uninstalled synaptics and had to use the a program called Driver Update. This program installed my Realtek Audio even though this was working apparently the two work together. It SUCKS that you have to pay
to install security programs that run your programs but this was the only thing that worked for me and I went through months of not having a touchpad.
I hope this helps others solve their touchpad problems. Good Luck
Sandia -
Satellite Pro P100 - Synaptics touchpad issue using Win 7
Satellite Pro P100 with Synaptics touch pad, was running Vista, now Win 7 64 bit.
The original driver had an option "disable when external pointing device connected".
I have installed a driver from Synaptics Synaptics_v14_0_3_C_XP64_Vista64_Win7-64_Signed_default.exe which does not have this check box.
It works fine except that sometimes the Microsoft Mouse turns off and on every few seconds as it or the touchpad fight each. I have to disable the touchpad.
Then next time I turn on. If I do so without a mouse, I cannot use the touchpad, until i plug in the mouse, reactivate, then unplug the mouse.
ThanksSorry, but this problem is reccurring more frequently (like every 2 or 3 days). The driver you recommend does not have the "disable touchpad when external mouse connected", nor does the Fn+F9 button work. Both touchpad and mouse are active at the same time with the result that the mouse becomes active, inactive, active, inactive every few seconds, and is that happens the secondary monitor goes blank (which is normal when new drivers are being installed, such as for an unrecognised flash drive). Thanks.
-
Spectre x360 keyboard issue after recent bios update
Hi Folks, I have a spectre X360 and I am really happy with it. Great product. I recently updated the bios and it was really nice to be rid of the glowing keyboard light LED. There is an issue that has popped up though which is incredibly frustrating, like incredibly annoying, and I was wondering if anyone else has noticed this. The keyboard response to typing a double letter (such as the t in letter) has gone down. In other words my typing speed is now limited because the keyboard isn't as sensitive as it was prior to the bios update. Does anyone know of a setting somewhere where I can increase the sensitivity of the keyboard so I'm not constantly going back to correct a missing double letter? Please! argh it sucks so bad. It has ruined my experience with this machine. -Sam
Hello ,
Thank you for visiting the HP Forums! A great place where you can find solutions for your issues, with help from the community!
I came across your post about the Notebook, and wanted to assist you! I have looked into your issue about your HP Spectre x360 and TouchPad sensitivities not working correctly. Here is a document on how to troubleshoot the Touchpad sensitivities.
If you will go to the section on Adjusting TouchPad pointing sensitivities it should help resolve the issue. It also shows you how to restore the default setting that could help as well.
Hope this fixes your issue.
Thanks. -
Spectre x360 with Windows 10 issues
I just got the Spectre x360 today (8/6/15). It has Windows 10 preinstalled, yet the option to rotate the screen in all of its positions is greyed out - I've seen the post about altering the registry and that kind of works. I have to say I am a bit taken back by how much work I've had to put into configuring this computer! I guess maybe its Windows 10, but I can't even seem to get Windows Live Mail (which I had to install because the new mail program doesn't let you leave copies of messages on the server?) to work. Apparently there is a conflict with Live Mail and the Intel Graphics drivers? All I know is I've spent close to 10 hours trying to get this thing to a point I can hand it to my techno-challenged boss, and from what I can see I have a long way to go... Seriously thinking that for the top dollar we paid for this, it should perform as advertised (rotate screen when closed and be able to use the touch keyboard in tablet mode). Mine sure doesn't. So if anyone has suggestions for the following, I would be very grateful...
Greyed out option for screen rotation and it is in the screen locked position.
Touch keyboard icon in lower right on the taskbar disappears when you enter tablet mode, making it impossible to type in any programs/windows. Even if you have the touch keyboard open and you enter laptop mode, it disappears.
Settings that I have applied revert back to default settings after restart. Example: I have configured my touchpad so that tapping is deactivated, but when my computer restarts, tapping is active.
I am really frustrated.Hello , Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums, I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More. I understand that you are having an issue with your Keyboard, and wanted to assist you! Have you tried using the Windows Update, to check for drivers that will work with Windows 10? You can check this site as well: HP Products - Where Do I Find Windows 10 Drivers and Software for My Model? If you are having trouble installing the drivers, you can use the tool at the following site: Open the Windows Update troubleshooter I did check your product driver page, and I did not see any Keyboard drivers, for Windows 10. It is possible that drivers may not be available for your product. If you are still having trouble, try using the Go back to an earlier build option, in your System Settings: HP Notebook PCs - Upgrading to Windows 10 Once you are back to your original Operating System, check to see if you are experiencing the same issue. If not, then you may consider holding off on the Windows 10 upgrade for a few weeks, until drivers can be updated. Please let me know if this information was helpful by clicking the thumbs up below. Regards!
-
Issues with Fn-keys and Synaptics touchpad on Asus X51RL laptop
Hello,
Since I installed Arch on my laptop, it's been working great. But I still have a few issues:
1) Fn-keys do not work. The brightness Fn-keys work, but I think that's done internally by the laptop, since it works even in the BIOS. The sound Fn-keys don't work, which is the ones I really need. How can I fix this? And I read somewhere that I have to switch from the kbd drivers to the evdev driver, is that true?
2) Since the latest update to the synaptics package in testing, the touchpad lost one-touch tapping, along with some other stuff. I know the solution is to disable hotplugging, but I sometimes need to plug in a keyboard or mouse, so I can't. How can I retain the scrolling and one-touch tapping settings from Xorg.conf AND hotplugging while using the latest synaptics?
3) The pre-configured options for the synaptics touchpad in the archwiki are good, but not that accurate. The size of the scrolling section of the touchpad is a bit too large, among other things. It's a minor problem compared to the others, but it'd be nice to fix it. In Windows, I definitely remember the settings being more accurate. Is there a way to have the Synaptics driver autodetect like the Windows one, or am I missing something here?
Thanks a lot in advance!I have the S62J (Intel verified whatnot version) with this Asus, the brightness keys work. I think they are hard wired though as they work in the BIOS.
I tried the acpi-support, but I haven't had any luck with it yet. I'll have to mess with it some more to see if I'm missing something.
I'm also wondering if there isn't a different keyboard layout I should use. I notice that there is a 30-something-asus-something.fdi (I'm not on the notebook at the moment) on the system, but I don't know if it's being used by anything.
The other observation is that using the Fn button is throwing ACPI calls into my dmesg.log file. I need to research to find out how to use them. -
HP Spectre x360 13-4002dx active pen and other issues
Hi, I'm havng issues with my active pen, but wasn't sure if it's an issue with my laptop or stylus (or if it's a software/driver issue). Is there an easy way to tell?Also, I've been using my laptop for a month now, and recently have had other issues, listed below. I wrote them down below in case that could provide some information, and/or if those issues are something I should be concerned about and should try to fix. To begin with, after doing some research, I bought a Synaptic active stylus (the Dell one), which worked very well for the first two weeks until last week. All of a sudden, it started to respond very awkward and randomly, sometimes it's too sensitive and draw lines even when the pen was off the screen, and sometimes it didn't draw anything at all even though I see the small circle following my pen tip. I initially thought it was due to low battery, but it's the same issue after I replaced the battery. Right now, the laptop doesn't respond to pen touching the screen (no clicks, no writings), although the pointer follows the pen. Any ideas on how to resolve this issue? How do I know if it's the pen that is faulty or if it's the laptop? Other issues I had or am having:1. Today, I had a BAD_POOL_HEADER error and blue screen of death. After reboot, everything seems to still work, but the login is now much slower. It's very fast to reach to the login screen, but it takes 2-3 minutes to bring up the desktop and other startup applications after I enter my password (I think it used to take less than 10 seconds). I tried rebooting 2-3 times, and it was always the same. 2. The laptop seems to gain heat very easily. With moderate workload (example, some websites with flash advertisements or videos), it can easily go above 70 degrees Celsius on either core (according to CPUID HWMonitor). One time, the system actually failed and forced hibernated due to overheating. (To me, the screen went blank all of a sudden. I turn the laptop back on, and the screen printed a message for a while saying it forced shutdown due to overheating. I realized it was hibernation after I logged in since I see all my windows) 3. On the second day of use of this laptop, the laptop just shutdown for no good reason, and then couldn't boot, saying it cannot find boot image or something like that. I looked up the web and found that it could be a BIOS issue. It said to try reseting the BIOS setting, and then it worked. I also upgraded the BIOS image to the latest after this incident. 4. This is probably more a router issue, but I initially had problems connecting wireless to my router. It was solved after changing my router. For those who are interested, the details is as the following: my old router supported up to 802.11n , but not 802.11ac, That shouldn't matter, but all wireless connections get disconnected once in every several hours if my HP Spectre x360 is trying to use the wireless. However the wired connections stayed ok when this happens, so the router is only "partially" killed. The fact that all wireless connections are getting killed seemed to me that the router didn't like something from my HP laptop. To be fair, I didn't try not using my HP laptop to see if the issue goes away, so it could be a coincidence that the router started to go faulty at the same time I bought and used my HP laptop. Anyways, it seemed it's a router issue, so after replacing the router. the issue went away. Thanks.
Will investigate and let you know what I can find out.
Although I am an HP employee, I am speaking for myself and not for HP.
Please click the little thumbs-up dealybopper to the lower right if my reply was helpful to you. Please mark Accept As Solution if it solves your problem. This will help others, too! -
A few questions before buying a spectre x360
Hi I'm considering buying a 13" Spextre x360 once Win10 arrives in final version - but have a few questions before going ahead. Mostly looking into the 4041no (i'm from Denmark) - or similar configuration. I need a configuration with at least 500 GB of hard drive and 8 GBs of RAM. 1. Will the spectre support all the new windows 10 touchpad gestures (similar to OS X/Mac gestures)? I have read something about the touch pad on the not being a "precision touchpad" but instead being run by synoptic drivers or something. Don't know exactly what it means. I come from a Mocbook Pro - and these gestures are so good. 2. One of the things some talk about in reviews is heat - that the x360 gets very hot to hold. Even just browsing the web. And also fan noise being loud. Any experience here - is it just a few unfortunate buyers, or are any of these issues generic. 3. Browsing the web there are so many different model numbers, that i can't keep up - and some of them seem to be identical configurations. Is there any overview of what is what. For instance 4041no and 4040no seem identical - but there is a difference in price, at the stores i have seen online. Similarly there is a 4030no and a 4032no. What are all these models. different numbers for every store/country/????. Any help here.. 4. The 4041no model i'm looking into has this QHD screen. Very high resolution. How is that in everyday life for surfing the web (mostly Chrome), Photoshop, watching movies local/streaming and more. It seems that everything will be very small, or is there scaling options or other stuff that makes this high resolution usable in real life. Or maybe lower the resoltion in settings. Any experience? I will soon try to find one in a real store to try out if possible. Think i'll start with those questions :-) And maybe also some generel feedback on the spectre x360. Thanks /Jonas
Hi Jonas,
I have the 4014 model (core i7, 256gb ssd, 8gb ram and FHD screen) so I can answer some but not all of your questions.
1. Touchpad is responsive and easy to use for me. Just upgraded to windows 10 and multi touch gestures are working fine. Three finger tap to open search, four finger tap to open the quick settings panel. Three finger flicks do app switching and minimising. The pad is controlled by the synaptic driver, but it has quite a few options and seems to work well for me.
2. Heat is not an issue for me. Sure, it gets warm when running intensive tasks, but as long as you are not pushing the cpu for long periods of time, it will be fine on your lap. Browsing the web, the fan will come on briefly when I load 10 or more tabs at a time, otherwise the fan will remain off.
Being an aluminium chassis, it has the ability to transfer heat out of the shell more easily than a plastic laptop, so you might notice it getting warm quicker, but it also cools down fast.
The fan is no louder than any other laptop I have used.
3. Can't help you with model numbers, sorry.
4. I'm finding that a lot of applications do not scale correctly on my FHD screen, so I can imagine that the QHD would be the same or worse. Most of the time, you can get the applications to look better by turning off display scaling in the compatibility settings. Sometimes this means that the application then looks smaller on screen, though text, images and icons are sharp, they are harder to read. The QHD would make these apps even smaller. I do not think QHD is worth it on a small screen for this reason.
In general the laptop works well. I use it in my job as a teacher, and being able to convert from laptop to tablet is a huge benefit. It is super fast to start up and easily gets me through a school day (quite often getting home with more than half a charge). I will just close the lid between uses and it sleeps, drawing very little power. It is capable of running Photoshop and office apps, while browsing the web and doing some light duty CAD modeling on the side.
One small issue that I and a few others have had is a crackling, buzzing noise due to the processor power regulation. Only audible in really quiet rooms or when putting an ear close to the device, when the computer is idling. Not an issue for everyday use, but something to be aware of if you have sensitive hearing or are annoyed by slight imperfections.
Hope that answers a few of your questions. -
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 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! -
[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) -
Synaptics Touchpad No Longer Working Properly
Hello Internet!
Hear my plight and tremble: I just recently updated my Synaptics touchpad drivers from the official manufacturer's website. Prior to the update, I could double tap the top left of the touchpad to enable and disable the touchpad. This was a convenient feature that I have grown quite fond of. However, after the update this feature no longer works! I am so devastated... I really enjoyed watching the pretty light outline of my touchpad turn to an evil red when it was disabled. I suppose that I could revert the drivers back to their old form, but I wanted to check if anybody knew a separate fix so that I could have both the new drivers and the old functions that I so cherished.
My model number is: A6Y49UA#ABA
My operating system: Windows 7
Thanks for your help, I'll remember you when I'm the dictator of the world.
This question was solved.
View Solution.Hi @El-Nacho ,
Welcome to the HP Forums!
It is a terrific place to find answers.
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I see that you upgraded your driver from the manufacturer's site. HP only recommends the drivers listed on the HP driver page. These drivers have all been tested and known to function correctly.When you install drivers from manuacturer's site, they may or may not function correctly with your notebook. OEM can and do sometimes alter a driver so that it functions correctly with your exact notebook.
Downloading or Updating Software and Drivers for HP Computers
If you did not have an issue with the old driver, I suggest you do a driver roll back.
Version 15.3.11.0 is the recommended version for your notebook and Windows 7.
Here is a link to the driver download page should you require it. HP Pavilion dv6-6c10us Entertainment Notebook PC Drivers
Best of Luck!
Sparkles1
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 the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping! -
Synaptics TouchPad V7.5 not working
I have the HP Pavilion dv6t-6b00 CTO Entertainment Notebook PC with the Synaptice TouchPad V7.5 on PS/2 Port. I am running Windows 7. Recently the touchpad had stopped working. It will recognize the pointer, but I cannot tap to click or right click. The only thing working is Left click. I have uninstalled and reinstalled updated drivers and updated my BIOS. I have also opened the bottom cover and the hardware seems ok.
hi johnyjj2,
Welcome to the Lenovo Forums.
Can you try the following:
1. Uninstall the Synaptics Driver from Control Panel > Programs and Features and reboot
2. Download and install this driver directly from the Synaptics website and reboot.
Synaptics Driver v17.0.19
Windows 8/7/XP/Vista 64/32-bit Edition
Let me know how it goes.
Regards
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter! -
Synaptics touchpad on HP Mini 110 Windows 7 32 Bit - not working for one user - working for another
Hi,
I recently have an issue with Synaptics touchpad on HP Mini 110 Windows 7 32 Bit - NOT working for one user - working for another.
Windows 7 updates recently installed ???
By checking the device properties on the user that works - "Synaptics PS/2 Port Touchpad 13/10/2011 Version 15.3.29.0"
When the other user logs on, the touchpad works for a few seconds, then a displays a black square with a red diagonal line through it, then the touchpad won't respond. Trying to use the keypad to navigate to system diagnosics or anything to find further info is useless....Hey eagle_no11,
Thank you for joining the HP Support Community!
I will do my best in assisting to hopefully get the TouchPad to work on the second user profile.
What I would like to start off with, is to restore the original Synaptics drivers onto the profile that is not working correctly. I have included the document Using Recovery Manager to Restore Software and Drivers (Windows 7).
Once you have installed the original drivers, you will need to complete all updates from both HP, as well as Windows. For these updates, if you open the HP Support Assistant, and select Maintain, you should see an option for updating.
Please let me know how these steps do work out for you.
Have a great day!
I worked on behalf of HP -
Synaptics touchpad on 4540s works for one person but not another
The Synaptics touchpad on my ProBook 4540s (Win 7) works normally when I use it but when my wife tries to use it, the touchpad is unresponsive after a very slight initial cursor movement. (Anticipating replies - Yes, she casts a shadow, pictures of her come out normally, and she has a visible reflection in a mirror.) The touchpad sensitivity setting is maxed on light touch and cursor speed is maxed.
She has relatively small hands, and long nails, but she had no difficulty using the touchpad on our old HP dv9910us and has no problem with an iPad touchscreen. This week she tried the touchpad on a Sony VAIO that was so worn most of the original surface coating is gone, and had no problem moving the cursor on that machine either. She even tried the awkward solution of using her knuckle instead of her fingertip on the HP in case her nails were getting in the way, but that didn't work either.
Not having used a 4540s before, and not having access to another one to compare, I have no way to tell whether this is a bad individual touchpad unit or a design issue. If a design issue, what's the workaround? For instance, is there a skin I can put on the touchpad to increase its conductivity?A friend of mine bought a ProBook 4540s yesterday. At Microcenter we noticed that the touch pad often would stop working for her, and sometimes for me, but it usually worked for me. She bought the laptop, and we she got it home we noticed the same problem. I played with the touchpad a little and noticed this pad has a very narrow window of operation. With the 14.1" HP's like the nc6220 or nc6400, you can use one finger, two fingers, even three fingers, and the mouse responds nicely. However if too much surface area is in contact with the touchpad of the 4540s it doesn't work. Too much surface area is the pad of your finger. Because my friend has long nails, she was laying her finger pretty flat on the touch pad, and it wouldn't work. When I used the pad like this it wouldn't work for me either. Because I have short finger nails I have always used the lower end of my tip. This works pretty well with the 4540s. Pressure seems to have little affect. It is a matter of surface area, and the acceptable area has a small range!
Maybe you are looking for
-
GENERIC ERROR COMING RUNNING A PACKAGE
Hi friends, I have a package and under that many procedures has written. When i am trying to add a new procedure and compiling it, it is compiling correct but when i am trying to run it, it is throwing error as ORA-04063: package body "DEV.NEW" has e
-
Best practices for deploying common object services
Hi, Our team has broken out from our main application around 10 services that largely are used to return objects from 10 common tables in the database. We are thinking that these services should be reusable amongst the 5 or so applications that we ar
-
Program GFW_PROG_TIME_AXIS convert to "true" line chart example.
Please disregard...took two days but I have succesful GFW line chart... I found a single customizing method call in error...now wiping egg from face.... )
-
Dear All, I have following queries which needs to be clarified. 1. In the results recording level after recording we give valuation as Accepted or Rejected. But what ever the valuation (Accepted/ Rejected) we give in results recording, in the usage d
-
have Mac OS X 10.6.8; Put a few iPhoto-photos to 'burn folder'; press 'burn' symbol. This window appears: 'Burn - The disc can't be burned, bcause the device failed to calibrate the laser power level for this media'; what to do next to address this?