06-08-2012 11:13 AM
I just had the issue with my Laptop which isn't X58, Will try your idea akagity since I'm well out of warranty anyway. Thanks for the tip I'll let you know if it works!
06-08-2012 11:42 AM - edited 06-08-2012 12:08 PM
@akagity I assume these are the two screws your talking about, https://dl.dropbox.com/u/3832397/Photos/2012/June/
I don't have any glue handy but I tightened them up, the one on the right seemed a little loose. My keyboard also seems to boot loop almost every time I move my keyboard which would reenforce your theory. Maybe a bit of solder would be appropriate? for now hopefully tightening it up will solve my issue
Edit: Nope didn't work, still boot looping
@CharlesB, Tried on my laptop (not X58) and I also swapped my 8800Gt for a 9500GT and it's still happening, so that rules pretty much everything out. Only possibilities now are what akagity is saying and that it may be a Linux issue.
06-22-2012 12:35 PM - edited 06-22-2012 11:06 PM
Yesterday I got a G110 keyboard, which seems to have the same problems as the G19 keyboards, I will post a solution that worked for me which I have not found anywhere. Maybe because it's completely insane :-)
Gigabyte EX58-UD4P Motherboard (14b bios, mailed to me by Gigabyte, who I have to say responded very fast.)
Core i7 920 Processor
GTX295 (which is 2 GFX cards connected through SLI)
Windows 7-64 Bit
- At first the keyboard wouldn't give any sign of life except during the booting (I could setup my bios fine) and also during the OS Selection screen. However once Windows started up it went blank, never to go on again.
Note: To have the keyboard working in OS Selection screen I had to enable Keyboard USB Legacy support in the BIOS.
Now for my solution:
Keyboard plugged in USB 2.0 Port
USB2 Enabled (EHCI)
Keyboard USB Legacy Support Enabled.
For this I used a 2nd keyboard on my PS2 port:
1. Boot up into windows, the keyboard isn't working.
2. Go to device manager, and for me there was a USB2.0 Hub which had the yellow exclamation mark
3. Find out to which USB the keyboard is connected
- I did this by disabling the universal host controllers one by one to see when the USB2.0 hub would dissappear, there's probably a better and faster method.
4. Uninstall this Universal Host Controller
5 .Uninstall the USB2.0 Hub
7.Now when booting my keyboard worked in the login screen, and only fails working after windows decides to find some better drivers for it.
8.Go to the task manager (ctrl-alt-del)
9.Keep killing all drvinst.exe (or a similar name) processes that keep popping up, I'm guessing with this board you're a game so this shouldn't be a challenge ;-)
10. Go to device manager
11. Here you will find the following devices under "Universal Serial Bus Controllers":
- G110 G-Keys
- Gaming Keyboard G110
- Universal Serial Bus (USB) Controller (the one without "- XXXX"!)
- Uknown device
- USB2.0 Hub
12. Run gpedit.msc
13. In the left part of the window navigate as follows: Local Computer Policy->Administrative Templates->System->Device Installation->Device Installation Restrictions
14. You'll see a list of settings on the right, open the one called "Prevent installation of devices that match any of these IDs"
15.Change it to enabled
16. Press the button called "Show..."
17.Now you need to fill in the following values in these fields 1 by one, there's 1 value for each of the devices mention in step 11, here's how you get it:"
- Go back to Device Manager
- Click properties for the device you want the value for
- Go to the "Details" tab
- Select Hardware Ids
- Copy one of the vallues (I took the ones without REV in them)
- Paste this value in the field mentioned in step 17
- Do this for all 5 devices mentioned in step 11.
- Click Ok and Apply
FYI I ended up with these 5 values, they may differ for you, but so you get an idea:
18. Now when you reboot you will still get the USB Device Installtion dialog, but most of them should fail due to a policy, and your keyboard should keep working.
I also tested it with the Logitech software and it sees my keyboard, I can change lights, and use the G-keys. As mentioned this is for a G110 keyboard, but I hope G19 users can profit from it aswell.
- Sound plugs tested and work aswell
- USB Connection on keyboard works also, tested with a USB-stick
Good luck! And I would like to know if this method helps any others, and I'm sure other people who come into this thread would like to know as well.
06-28-2012 11:45 AM - edited 06-28-2012 11:48 AM
I completely dismantled and re-assembled my G19, unplugged everything, made sure everything was securely seated and bolted down properly. It's been a few days now without a boot loop. I think I fixed it
Edit: of course don't try this at home unless you know what your doing, if your keyboard is still within the warranty period you should probably RMA it, and if you break your keyboard while trying to do what I did don't blame me
07-23-2012 01:09 PM - edited 07-31-2012 12:10 PM
I have a G19 AND G13 with an X58 based MB (ASUS Rampage III Black). I used to get the rare reset, but it happens quite often now that I have the G13 installed. I had also recently put a second GTX580 running in SLI. Reading these posts, logic dictates this should work....
X58 and 790i are "enthusiast architecture" so they need a little massaging to get stable. A recent post hear mentions USB issues are due to low ICH voltages. Probably true. SLI systems should run an ICH voltage of 1.2 and Tri-SLI at 1.3 or higher. My ICH was still set at 1.1. Also, these boards have an "ez-plug" 4 pin molex power connector which the manual says is not necessary to connect. However I've found other sites that say it should be connected for SLI. I had not connected mine to the MB.
So there are 2 issues related to power, USB, and SLI which all the evidence of the G19 problem points to.
I have made the changes to my system, going up to 1.2 on ICH, 1.15 on IOH, and plugging in the ez-plug to the PSU before posting this and no issues so far. Going to try some BF3 and iRacing and see what happens.
Edit 24 hours later:
Haven't had a single issue since I made these changes
Edit 8 days later:
Still no more problems. This is solved for my system.
10-17-2012 11:48 AM
Ok I dont even know where to start, I have been a big fan and consumer of Logitech products and never had any trouble with them at all from my televion remote to mice, keyboards, speakers, etc. I recently purchased a G19 to replace my worn G15. The G19 worked grand for a few days, no problems save for a need to re-boot every now and then. Lately I have been playing Guild Wars 2 with my daughters and the board is now really acting up. Even when we send emails it type liiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiike ttttthhhhhhhhhhhhhhhhhhhhhhhhiiiiiiiiiisssssssssss
Gateway FX6840 Desktop, Windows 7 Home Premium 64bit (6.1, Build 7601), Model Gateway FX6840, Intel i7 email@example.comGHz
8192MB Ram, Intel H57 Express Chipset
Any help would be greatly apppppppppprrreeeciattttttttttttttttttttttttttttte
10-17-2012 04:23 PM
I used to have those problems, however after making the changes I had posted it's been 9 months since I've had any problems with my G19. I also have a G13 installed an no more problems there either. One additional thing.... If you are using a USB extension cable don't use anything longer than 6 feet.
11-16-2012 09:17 PM
Got a weird issue with my G19 not working as well:
I've tried all the methods that's in the Logitech forum in regards to installing the drivers for G19 but it doesn't work.
The OS still uses the HID Keyboard on Device Manager instead of recognising it as G19s. When i try to update driver, online or forcing it to search the LGS folder, it still recognises the HID Keyboard driver as the latest
The keyboard works but no backlight and LCD screen does not work
LGS is not picking up on the G19 as well
I've done a clean boot install of the LGS 835 version and as well as the LGS 816, both isnt working, even trying the LGS 3.01 that came with the keyboard!
Running E8500 with P5Q-SE/R mobo with Windows 7 32 bit
LGS was running before i reformatted the OS on the same USB port but have tried other USB ports and it's not working