04-05-2010 11:37 PM
Windows 7 Ultimate 64
Northbridge NVIDIA nForce4 rev. A3
Southbridge NVIDIA nForce4 MCP rev. A3
2x 1GB DDR1
XFX HD 4850 1GB
DMI BIOS Phoenix Technologies, LTD version 6.00 PG
AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
* G-keys are non-responsive
* Backlighting now does not come on
* screen usually always shows distortion, like whole columns of pixels are the wrong color and flicker between different shades of what they should be
* Sceen flash randomly
* unplug and leave overnight - no effect
* reinstall driver - no effect
* soft rebot after cold boot
04-06-2010 10:14 PM
I have now disabled sideshow and that did not fix the issue. I am wondering if I buy a USB Y cable if that would fix the problem or am I just going to waste my time
04-07-2010 03:19 PM
As it turns out the G19 is not the only keyboard with a buit in USB hub.
The Microsoft/Razer Reclusa has a similiar design.
I have been chasing this x58/ICH10 bug since May of last year when I received the Asus Rampage II Gene.
This problem is definitely more widespread than I think is discussed. Here's just one example of many threads that exist on the Asus forums about this problem:
It has spread to other tech forums as well:
This is really the kind of problem that leads people to look in the wrong direction. Couple in the apparent details that 32bit operating systems and systems without USB hubs - which I presume are a larger percentage of the market - are not impacted and this is an issue ripe for never being adequately addressed.
As I understand what was written here the G19 actually stops working as the system works up to the crash. The Reclusa meanwhile has exhibited a different set of behaviors. The behavior of this problem has also changed on the Rampage II Gene over the course of the BIOS releases.
The original and early BIOS releases had the problem manifest by crackling of audio, the onboard NIC fully disconnecting, and the CPU usage climbing up to 100% on a single core before finally hardlocking or ending in a BSOD that did not leave a crash dump. The later BIOS firmware - including the most recent 1202 - no longer disconnects the NIC or has the CPU usage of the first core climb to 100%, but it still has the crackling audio along with the eventual hardlock or BSOD.
LIke many others my self discovered solution was using the warm boot method. Discovering this method implied to me that this was some sort of firmware bug in the BIOS, but I wasn't sure which component was at fault. I believed - incorrectly - that it must have been the CPU power management or the motherboard poorly managing the voltage. The discovery of this thread has more clearly defined that the issue is with the bus and more specifically the USB bus.
I am still in the process of testing, but at this time it appears that disabling the EHCI Hand Off has been the silver bullet for my issues on the Asus Rampage II Gene. This certainly makes me leary to attach any further USB hubs to my system; i.e. monitor. It also made me feel a bit dumb to be honest. Leaving the EHCI Hand Off at the default of Enabled when the text description to the right said to cut it off? Not the finest hour for me or my reading skills.
Now with the information Logitech has provided I believe this has the potential to be a true hardware errata with the ICH10 or an issues with the Microsoft 64bit USB drivers. Logitech, as a vendor my expectation is that you have the ability to make the connections to these large corporations. A discussion with Intel might be a fruitful direction. Intel is in a position to track down the precise elements of this issue and determine what is or isn't at fault. If it is a hardware errata in their design they can release a specification update and push out a firmware fix to all the vendors. Once a firmware fix from Intel is released Logitech would be in a great position to push the motherboard makers to roll out that firmware fix to their customers.
If this is actually the fault of the 64bit USB drivers in Microsoft products then that fix needs to be spread to more than just Windows 7, which is a problem with the currently i790 patch listed in this thread; sort of hard to test it on Vista64 and determine its worth.
I really feel like this problem needs more attention. A good news article that details the situation in a concise and simple way I believe would generate a wellspring of people with the issue who were pulling their hair, confused as to the problem, or doing strange work arounds - like the warm boot method - just to use their machine. I also believe such an article would considerably assist Logitech in finally squashing this and removing this support headache. The G19 strikes me as the kind of profitable botique products that ends up in the hands of a vocal, loyal, and lucrative market. Getting slammed for something that isn't your fault is always frustrating.
04-08-2010 04:10 PM
04-14-2010 05:02 AM
I post the following on the thread about G110 issue that causing loop reboot
"I just put together my new pc with the Gigabyte X58A-UD3R motherboard and my brand new G19.
I'm having the same problems, (keeps rebooting on Gigabyte logo screen, until I pull the plug) while all software and firmware are up to date with latest known versions.
I tried using different usb's, even the usb 3.0 slots, and still.... it's a bit annoying.
Expept that, when I'm turning off my pc, the backlight on keys isn't turning off and the LCD turns gray. Is that normal?"
My systems specs are:
MB: Gigabyte X58A-UD3R
CPU: Intel i7 930
RAM: Corsair XMS 3x 2Gb DDR3 @ 1333
Gfx: Albatron 9800 GX2
HDD: 2x WD Black CAviar 160GB, 1x WD 640GB
Monitor: LG W2361 on DVI
Card Reader on internal usb slot
KB: Logi G19
Mouse: Logi MX600 (from my old kb/mouse combo MX3200)
OS: Win 7 Ultimate -64bit
As I said, to turn on my pc, I have to pull the USB plug of my KB....
04-14-2010 10:56 AM
Please do NOT crosspost into different threads. This is your warning.
The problem you are experiencing is a BIOS one. Gigabyte has provided us some beta BIOSes for their motherboards with the G110/G19, and they resolve the boot issue. Please await for Gigabyte to release a new BIOS for your motherboard.
04-15-2010 07:58 AM
I plugged my mouse's (MX600) wireless bundle into one of the keyboard's USB socket, and problem gone!
Weird, but it works.
"Please do NOT crosspost into different threads. This is your warning."
Sorry about that, didn't know where to post. Wont happen again