geekhack
geekhack Community => Keyboards => Topic started by: Krabpeople on Wed, 14 December 2011, 05:52:45
-
Alright so about a month ago I posted a thread here on Geekhack about a question regarding my non-responsive keyboard. When I got the keyboard working that time I unplugged every USB device except for my mouse. Now today, I unplug it to move it somewhere and go to plug it back in about 30 minutes later and I get something about a USB device has malfunctioned from Windows and my keyboard has all three LEDS lit up and isn't responding again. I restart my computer multiple times, unplugging and replugging the keyboard in; the keyboard is still being unresponsive. I finally through some luck I guess, managed to get it to cooperate after about 10 restarts.
My question is: Is this normal with mechanical keyboards or should I start contacting EliteKeyboards again?
-
About 10 minutes after typing this, all 3 of the LEDS went out for about a second, then came back on. This happened for about 20 minutes after the first initial occurrence every 1-3 minutes. Now the keyboard is back in it's unresponsive state.
-
Have you tried to connect the keyboard to different computers? It could be your keyboard's problem, it could also be your one computer's USB ports problem.
-
Have you tried to connect the keyboard to different computers? It could be your keyboard's problem, it could also be your one computer's USB ports problem.
+1
-
+1
+2
-
+3 since this would make sense. The way these boards are built it's more likely you're having USB interface problems on your motherboard.
-
Have you tried to connect the keyboard to different computers? It could be your keyboard's problem, it could also be your one computer's USB ports problem.
So far I've tried my computer, my dads computers (two different machines running Windows XP and 7), my other older desktop, and a laptop. All of them give me an unknown device with Code 43 error when looking through the device manager. I've flashed and updated my bios, reset my CMOS multiple times and nothing yet. I feel that if it were my motherboard that it would have worked on another computer so far. I'm going to test it at a buddies this coming weekend to see if it's not just my house being wonky.
I've found through some reviews of the DAS keyboard on Amazon, that other people are having this same issue as well and that it's most likely related to the keyboard not receiving enough power through one USB. Apparently some people have found that using a USB Y-splitter would allow the device to have as much energy as it needed, so that's also on the to try list.
-
Since you have tried on different computers with the same result, the last thing you could try is use a powered USB hub. Other than that, I think the keyboard has really gone south.
-
Same thing happened to me, also with a leopold. LEDs kept flashing and it would disconnect randomly. But it only does it under USB, has been fine under ps/2.
Mine also has red switches. Seeing as this is a problem with others, I think I'll be shooting an email to EK to see what's up with an exchange.
-
Alright, so I just got done trying the PS/2 adapter and the keyboard LEDs do not light up, yet I am still unable to get into the bios and it does not respond to key strokes on my desktop. Weird thing though, I go and try it in my sisters computer, and it doesn't work with the PS/2 adapter so I try the USB and it works. So I get up and unplug and take it back to mine, plug it in, it registers keystrokes and the leds are responding correctly. I go to unplug the current keyboard I'm using and go to reroute the Leopold. I come back and find the Leopold has gone back to it's 3 lit up LED unresponsive state. So I'm thinking it's my sister's computer that it works with, I go to plug it into the same exact scenario (same USB plugged in, all the other devices plugged in when it worked the first time) and it was back in the 3 LED lit up unresponsive state.
Edit: On my motherboard I have 8 USB slots, 4 clusters of 2. I have tried each single slot with no other things plugged in to any other USB slot. I am unsure of how to determine a USB slot is powered or not.
-
mine works perfectly fine (well, for the couple of minutes i had it connected) with my mac. like you, i tried numerous usb ports on my computer with the same problem. yet no other keyboard (filco, poker and another leopolds) had that problem im having with my leo with reds.
-
Does he have an account on this website that I could contact him at or would it be possible to reach him through email? I tried to google him and not much came up.
-
carl matsu is the designer of leopold (and i believe ex designer of filco).
so, no, he does not have an account. and most likely wont be able to help you out (or me) with the problem.
our best bet is to get in contact with EK
-
PM Carl Matsu.
lol @ ripster, stop telling noobs to PM CM. =P
Does he have an account on this website that I could contact him at or would it be possible to reach him through email? I tried to google him and not much came up.
Sometimes you have to take ripster's words with a grain of salt. Do like demik said and contact EK. Better yet, try it on another computer first.
-
I figured just as much, will contact them, thanks.
-
Does he have an account on this website that I could contact him at or would it be possible to reach him through email? I tried to google him and not much came up.
lol...
-
ripster
#1 Keybo Expert On Terra
I'm quite new here to the Geekhack community and with a title like that, how could one not believe what he says.
-
I'm quite new here to the Geekhack community and with a title like that, how could one not believe what he says.
welcome to geekhack lol. You will get used to his sarcasms/jokes and hopefully you won't end up hating him like some others did/do.
-
I'm having a similar problem with my brand new Leopold Otaku Brown. Using PS/2, the LEDs just flash on and off like a christmas tree,
using USB they just flash once. No response in either case, and this has been confirmed using multiple cables and seven different
computers running Windows, Linux, OSX. So I'm guessing this is, in fact, a hardware problem. I'll contact EK as soon as I can, but I'd be happy
to hear about the experiences of everyone else, aswell.