I should add that the keyboard works in sys-usb even without the /etc/X11/xorg.conf.d/00-keyboard.conf file I had added as described above, so I removed it. In the equivalent file in dom0 I appended (to no effect as of yet):
If during installation you enabled the creation of a USB-qube, your system should be setup already and none of the mentioned steps here should be necessary. (Unless you want to remove your USB-qube.) If for any reason no USB-qube was created during...
Since I bought this keyboard I have had the problem that my keyboard is not detected at boot. When I put the keyboard in Bios mode it is okay but it still boots kindoff slow. I read a post a while back about the 16.8mil color thing and this problem (wich was kindoff covered up) a while ago but that topic was closed and no information whatsoever about this ever came up again.
Have a ticket at ASUS, but the supportagent claims it's Corsair's fault. Who to believe!? Someone isn't doing proper USB handshake... probably some wakeup/USB timer handshake mismatch... hopefully it'll get fixed by either one!
I boot Komplete Kontrol stand-alone, which recognizes the keyboard. Under Controller it correctly says KK S61 mk2. In Preferences>MIDI, the KK DAW-1 boxes are ticked for Input and Output, along with my other MIDI devices.
I load up a sound from the software, and it appears on the display of the S61. But playing the keyboard produces no sound. I play my other keyboard, and I'm hearing sound, AND, the blue LEDs light up on the S61 ! And also, the knobs on the S61 are changing the sound as expected. But the keys and wheels of the S61 aren't sending anything.
This is repeated when I boot up Cubase. I can use Play/Stop to control Cubase, and the rotary dial to move tracks up/down, mute/solo tracks with those buttons, etc, but there is no MIDI input from the keys.
It's fixed! I downloaded the driver for the fourth time and reinstalled, but this time, I first deleted the previous install from my system. It seems this was the crucial step to "reset" everything, and checking Device Manager also made this easy. So all appears to be working as normal now.
If you check in Device Manager does it show the USB device for the keyboard, is there anything that is showing as an issue? You should be able to see at least the keyboard is connected in the USB device list even if the drivers are not working. That will at least suggest the USB side is fine.
I have looked at many other articles for this exact issue but alas none have worked for me so far. It used to work just fine, but then a few weeks ago it stopped being recognized by all of my libraries (SpitFire, EastWest OPUS, etc.)
Somehow, my MIDI keyboard is not recognized in Ardour.
On the same Linux installation, I can use it in LMMS and Pianoteq, so it is not a problem with the keyboard (Yamaha cp33), nor with the OS.
I also installed Ardour on a Macbook, and there it is also working flawlessly.
Are you using the ALSA audio engine for Ardour? On Linux the other choices would be JACK or PulseAudio.
Assuming you are using the ALSA backend since you did not mention jackd, did you select ALSA Sequencer as the MIDI engine to use, and pick your hardware device?
I type a lot of ( and ) in the code that I write. A long time ago I set up Keyboard Maestro so that if I tap the left shift key without other keys or modifiers, it inserts (, and likewise for the right shift key. I love this, it works beautifully and has become muscle memory. Here's how it's implemented:
I started using a bluetooth keyboard and I can't get this trigger to work for it.
I click the green + button and add another device key trigger, click in the box waiting for a keystroke, and the keystroke is recognized. However, tapping the shift keys does nothing.
The computer does acknowledge the existence of an external keyboard, but some keys are wrong. When I try to change the keyboard type, and am asked to press the button directly to the right of the left shift key (which is ) there is a message saying that I have pressed a key on my Apple keyboard, and please use the keyboard that is not recognized. If I skip it just skips and I'm back to default. If I press OK the settings app hangs. It's like the computer understands that there is an additional keyboard, but thinks it's an Apple keyboard.
The result of this incorrect recognition of my keyboard is that some special characters that I use often are not in the right place and I sometimes have to try several out before finding it, as it's hard to remember.
When I connect my Mac Mini to the same docking station, MacOS recognizes the keyboard correctly and sets the keys right. Having different keysets with the same keyboard for two Mac computers is not optimal.
I have a Yamaha P-115 keyboard with USB MIDI output. I setup Zynthian on a Raspberry PI v4 with no other hardware, so was hoping to get the keyboard recognized through the USB. Unfortunately I cannot seem to get Zynthian to recognize any MIDI input at all coming from the Yamaha. The MIDI log is completely blank.
I have installed Zynthian from the 2021-03-25-zynthianos-stable-2103.img image and configured it per the very helpful instructions provided in Beginners Headless Zynthian Tutorial - ZynthianWiki. I ran the software update after installing and have ran it again for good measure. I also ran sudo apt update and sudo apt upgrade.
I would expect something in dmesg even if the device is not recognised, Zynthian should detect a device being plugged in. Confirm you see something when you plug another USB device, e.g. a mouse or memory stick.
I spent a lot of time wrestling with getting vnc server to work properly on current Zynthian image. Wiki steps said to use raspi-config to enable VNC, and it did a lot of apt stuff, including getting stuck yesterday on not finding an image for one of the libraries, which came back to raspi-config saying it failed to setup vncserver. But today it succeeded, and vnc finally connects to Zynthian.
I was really surprised i had to go through all that. I couldnt think of a good reason the Zynthian image shouldnt be delivered with all that already done. Checking the vnc server in the web.config, and rebooting, definitely was not enough to get vnc server to connect.
Out of the box Zynthian offers VNC server for ancillary views, i.e. engine GUIs, patchage, terminal, etc. Not the main UI. There is a feature request to enable main UI via VNC. You should not have to jump through many hoops to get VNC working.
After installing the IDE Arduino 1.0.6, I've connected the board with a USB cable to my computer.
As expected, my computer was trying to install the driver.
And... It found a driver. The board was recognized as a HID Keyboard.
I didn't get a unrecognized device or a extra COM port.
Neither I can replace the driver with the one I've downloaded with the IDE. (Got a message that the driver is not suitable for this device).
Does anyone knows what I'm doing wrong?
How can I get my board recognized as a COM port so I can program it with the IDE?
I've got the same problem on a Windows 8.1 computer and Windows 7 computer.
You should be able to use Device Manager to update the driver.
Or, use Device Manager to delete the incorrect driver and then follow instructions to install the correct one:
Window Driver Install
I've tried that. But I get a message that the best driver is already installed.
If I lookup the VID/PID on the internet, it's for a Atmel LUFA Keyboard.
And I can't find this VID/PID in the INF file of the driver which i've downloaded with the IDE.
Thanks for all the replies. I found a solution. Proto-pic pointed me to the VID/PID.
The one I have was not the standard for Arduino Uno.
So I guessed there is something wrong with the Firmware.
I've downloaded dfu-programmer-win-0.7.0. And uploaded the firmware from the IDE.
(Following this link)
Do the numlock/capslock leds light up when you hit them? If not it is a physical issue with the keyboard and the connection to the port on the pc. If they do light up, it is an issue with Windows recognizing them.
If it is a windows issue, most likely you will have to reinstall the controller in device manager or see if something is conflicting with it (craziest stuff you can imagine, biometrics, printers, scanners, etc.)
yikes!!! We use the same model here! Same problem! And if it hadnt happened to my own computer, I would tell people they were nuts. But it did happen to mine! I was so pissed after trying to fix it, that I started unplugging everything from the usb ports, with the inention of getting a new computer. But low and behold, when I unplugged all the extra stuff from the front usb ports, my keyboard started to work. I still havent figured it out. Just know, not to leave anything plugged in the front ports. I know that our bios is way out of date on all machines. Maybe that would fix them. But since the others have the same old bios date, I never really went down that road.
Any update? If you unplug and plug the keyboard back in any change? It almost sound though like the OS is ignoring HID input. What are the power setting for USB hubs in device manager on the PCs perhaps they are in power save mode?
After flashing the sd card with armbian and booting it, it asks me to enter the root password, however the keyboard that is plugged in isnt detected and nothing is typed on the screen. Ive already tried bookworm and jammy, both cli and minimal-cli variants.
I understand that the keyboard, track pad and the touchscreen are not working on your HP Spectre x360 - 13-ac023dx. I read that you have reset the Windows operating system and have done a remarkable job in troubleshooting this issue.
d3342ee215