If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Can't wake from sleep.
I have a windows 7 computer with Logitech K520 wireless keyboard
and mouse. Has the unifying USB receiver. I'd been using it for a year without incident. The keyboard or mouse would wake the computer from sleep. Over the last two months, I've been trying to work the wrinkles out of windows 10. I've changed a lot of windows settings, so I restored a win7 backup from two months ago, before I started messing with it. No help; still can't wake from sleep. Pushing the power button on the chassis does to wake it. But, if I plug in a wired USB mouse, that mouse wakes from sleep just fine. I think that proves that the BIOS settings are appropriate. It's set for S3 sleep. I plugged a LED into the USB port to verify that it's still powered on in sleep. I've gone through every entry in device manager and checked the box to allow this device to wake from sleep on all the entries that had the option. Turns out that most of the usb/keyboard/mouse entries don't have that option. Still no wake from sleep. I've gone through the power profile settings and checked everything that looks like it might have anything to do with mouse/keyboard. I've changed the power profile from balanced to high performance...no help. I installed setpoint driver software. Now, I have two new device manager entries for the Logitech HID-complient unifying mouse and keyboard. Neither has the option to wake from sleep. Still can't wake from sleep. I also have a Cirque GP410-U USB touchpad. It won't wake either. Although the device manager entries are hard to decipher, given that there a lot of mouse/keyboard/usb entries, I was able to verify that the Cirque drivers are installed and working and that the box to allow waking from the device is checked in both the mouse entry and the HID entry. I pulled the USB unifying dongle and plugged it into another win7 computer. The same keyboard and mouse can wake that computer just fine. I think I've proved that the computer works and the keyboard works, just not together...although they used to work fine. Previously, I had issues with unwanted wakes from jiggling the mouse. I set device manager to show hidden devices and uninstalled every entry in mouse, keyboard and HID categories. I uninstalled any mouse related software. Still no wake with default MS drivers. Reinstalled vendor drivers. Still no wake. I have no idea what to try next. Ideas? |
Ads |
#2
|
|||
|
|||
Can't wake from sleep.
mike wrote:
I have a windows 7 computer with Logitech K520 wireless keyboard and mouse. Has the unifying USB receiver. I'd been using it for a year without incident. The keyboard or mouse would wake the computer from sleep. Over the last two months, I've been trying to work the wrinkles out of windows 10. I've changed a lot of windows settings, so I restored a win7 backup from two months ago, before I started messing with it. No help; still can't wake from sleep. Pushing the power button on the chassis does to wake it. But, if I plug in a wired USB mouse, that mouse wakes from sleep just fine. I think that proves that the BIOS settings are appropriate. It's set for S3 sleep. I plugged a LED into the USB port to verify that it's still powered on in sleep. I've gone through every entry in device manager and checked the box to allow this device to wake from sleep on all the entries that had the option. Turns out that most of the usb/keyboard/mouse entries don't have that option. Still no wake from sleep. I've gone through the power profile settings and checked everything that looks like it might have anything to do with mouse/keyboard. I've changed the power profile from balanced to high performance...no help. I installed setpoint driver software. Now, I have two new device manager entries for the Logitech HID-complient unifying mouse and keyboard. Neither has the option to wake from sleep. Still can't wake from sleep. I also have a Cirque GP410-U USB touchpad. It won't wake either. Although the device manager entries are hard to decipher, given that there a lot of mouse/keyboard/usb entries, I was able to verify that the Cirque drivers are installed and working and that the box to allow waking from the device is checked in both the mouse entry and the HID entry. I pulled the USB unifying dongle and plugged it into another win7 computer. The same keyboard and mouse can wake that computer just fine. I think I've proved that the computer works and the keyboard works, just not together...although they used to work fine. Previously, I had issues with unwanted wakes from jiggling the mouse. I set device manager to show hidden devices and uninstalled every entry in mouse, keyboard and HID categories. I uninstalled any mouse related software. Still no wake with default MS drivers. Reinstalled vendor drivers. Still no wake. I have no idea what to try next. Ideas? If I was at my wits end, I would 1) Back up the C: partition. 2) Delete the ENUM key with all the hardware detections in it. This will force the OS to redetect all hardware. 3) Now go back and look in Device Manager etc. 4) If the experiment fails, restore from backup in (1). Deleting ENUM still works, even in Win10. Here, I elevate enough so I can hammer it. The hardware will be rediscovered on the reboot. If you get into trouble, try Safe Mode by pressing F8 in Win7. For Safe Mode in Win10, I enable the boot menu so I have that option when Win10 comes up. https://s9.postimg.cc/vwioz43f3/WIN10_delete_ENUM.gif https://winaero.com/blog/enable-the-...in-windows-10/ What removing ENUM can do, is correct situations where more than one declaration is present in ENUM, and you're having trouble getting things to work. (For example, a USB device works in one USB port, but not another USB port, and the situation gets worse and worse as USB ports stop detecting the device.) I don't really think the procedure will solve your problem, and it's really a spin of the roulette wheel. That's why this is a "wits end" thing. Paul |
#3
|
|||
|
|||
Can't wake from sleep.
On 12/2/2018 7:22 AM, Paul wrote:
mike wrote: I have a windows 7 computer with Logitech K520 wireless keyboard and mouse. Has the unifying USB receiver. I'd been using it for a year without incident. The keyboard or mouse would wake the computer from sleep. Over the last two months, I've been trying to work the wrinkles out of windows 10. I've changed a lot of windows settings, so I restored a win7 backup from two months ago, before I started messing with it. No help; still can't wake from sleep. Pushing the power button on the chassis does to wake it. But, if I plug in a wired USB mouse, that mouse wakes from sleep just fine. I think that proves that the BIOS settings are appropriate. It's set for S3 sleep. I plugged a LED into the USB port to verify that it's still powered on in sleep. I've gone through every entry in device manager and checked the box to allow this device to wake from sleep on all the entries that had the option. Turns out that most of the usb/keyboard/mouse entries don't have that option. Still no wake from sleep. I've gone through the power profile settings and checked everything that looks like it might have anything to do with mouse/keyboard. I've changed the power profile from balanced to high performance...no help. I installed setpoint driver software. Now, I have two new device manager entries for the Logitech HID-complient unifying mouse and keyboard. Neither has the option to wake from sleep. Still can't wake from sleep. I also have a Cirque GP410-U USB touchpad. It won't wake either. Although the device manager entries are hard to decipher, given that there a lot of mouse/keyboard/usb entries, I was able to verify that the Cirque drivers are installed and working and that the box to allow waking from the device is checked in both the mouse entry and the HID entry. I pulled the USB unifying dongle and plugged it into another win7 computer. The same keyboard and mouse can wake that computer just fine. I think I've proved that the computer works and the keyboard works, just not together...although they used to work fine. Previously, I had issues with unwanted wakes from jiggling the mouse. I set device manager to show hidden devices and uninstalled every entry in mouse, keyboard and HID categories. I uninstalled any mouse related software. Still no wake with default MS drivers. Reinstalled vendor drivers. Still no wake. I have no idea what to try next. Ideas? If I was at my wits end, I would 1) Back up the C: partition. 2) Delete the ENUM key with all the hardware detections in it. This will force the OS to redetect all hardware. 3) Now go back and look in Device Manager etc. 4) If the experiment fails, restore from backup in (1). Deleting ENUM still works, even in Win10. Here, I elevate enough so I can hammer it. The hardware will be rediscovered on the reboot. If you get into trouble, try Safe Mode by pressing F8 in Win7. For Safe Mode in Win10, I enable the boot menu so I have that option when Win10 comes up. https://s9.postimg.cc/vwioz43f3/WIN10_delete_ENUM.gif https://winaero.com/blog/enable-the-...in-windows-10/ What removing ENUM can do, is correct situations where more than one declaration is present in ENUM, and you're having trouble getting things to work. (For example, a USB device works in one USB port, but not another USB port, and the situation gets worse and worse as USB ports stop detecting the device.) I don't really think the procedure will solve your problem, and it's really a spin of the roulette wheel. That's why this is a "wits end" thing. Paul Thanks for the input. I tried it. I didn't look at the content, but I exported the ENUM key before and after. It went from 4.5MB to less than 1MB. It didn't solve the sleep problem. But it did introduce a network problem. No network connection. No lights on the ethernet connection...dead...dead...dead. Tried searching for drivers using a secondary ethernet. Drivers installed, but the device can't start. Tried restoring drivers using ddbackup. That didn't fix it either. When you look at network and sharing center / change adapter settings there are no entries on that screen. Usually, I'd see both adapters. This time, it's blank. Both show up in device manager. I have a sysprepped win7 that I've been using as an initial starting point for new installs. I restored that. Now, sleep in the start menu is greyed out. I poked around for half an hour and got nowhere. Can't even sleep it, so no reason to work on wake. I'm seeing bizarre random symptoms on this system. I've been adding/deleting stuff since 2009. Probably time for a rebuild, but the sysprep experiment above suggests that won't be easy either. I restored the backup from before this experiment and it's all good again... except the wake from sleep part. There's chatter all over the web about failure to wake from sleep. Looks like I'm not alone. Guess I'll just use the wired mouse buttons to wake from sleep and limp along until I get a fully working win10 system to use. The win10 prototype is progressing. I put 8GB of RAM and a SSD in it. It's faster than this system anyway. I'm attempting to migrate all the incompatible software to a virtual box win7. Still a bunch of niggling issues, like getting the freedns update to work properly. The root cause of many of my earlier attempts was trusting Macrium to fixup whatever it needed when cloning a partition. Turns out that win10 wants a starting sector at 1024K. All my old drives have a starting sector at 63. IF I manually rebuild the hard drive for starting sector at 1024K, then do a macrium restore, it all works fine. Took me weeks to figger out what was happening. I never did get win10-64-bit 1809 to install from a flash drive. Runs along until it decides that it can't find some files it needs and aborts. 32 bit installed fine. I installed win10-64-bit 1803 from a flash drive. The I updated it using the same 64-bit 1809 flash drive that had failed. That updated fine. It's always something... |
Thread Tools | |
Display Modes | Rate This Thread |
|
|