On Mon, Jun 1, 2015, at 10:36 PM, Facundo Curti wrote:

Distros/computer, I didn't. But in windows it works fine. :/ El 01/06/2015 22:55, "Christian Demsar" escribió:

...

On Mon, Jun 1, 2015, at 09:50 PM, Facundo Curti wrote:

...

Hi. I hope someone can help me please.

I bought a new keyboard, a noga NKB-710. The problem is that, according to xev, four of the keys have the same keycode...

The keys Ctrl, Alt, Win*** and shift, have the same keycode, 50. Off course, it doesn't work correctly. and this way, It's imposible to me to configure it with xmodmap.

I don't know what data I can share. I hope this to be sufficient:

attached a lsusb -v output

Thx, bye! :P Email had 1 attachment: + lsusb-v2 20k (application/octet-stream)

Have you tested if it works in other distros or other computers? Might narrow down the problem.

-- vixsomnis

(please bottom-post if you can) I installed the xorg-xev package to compare to what you're seeing. I think the X11 keycodes are different from the codes actually sent by the keyboard. Can you post the output of typing the problem keys when running $ sudo showkey I have: left-ctrl = 29 windows = 125 left-alt = 56 right-alt = 57 right-ctrl = 97 left-shift = 24 right-shift = 54 I think these are standard for all US keyboards. That should confirm if the problem is with your keyboard (if the keys show the same code) or in the driver (or somewhere else). There's also the slight possibility that it's a kernel bug, which would show up as repeating codes from showkey, since showkey is as close to the kernel as possible. -- vixsomnis

On Mon, Jun 1, 2015, at 11:26 PM, Facundo Curti wrote:

2015-06-02 0:10 GMT-03:00 Christian Demsar :

...

On Mon, Jun 1, 2015, at 10:36 PM, Facundo Curti wrote:

...

Distros/computer, I didn't. But in windows it works fine. :/ El 01/06/2015 22:55, "Christian Demsar" escribió:

...

On Mon, Jun 1, 2015, at 09:50 PM, Facundo Curti wrote:

...

Hi. I hope someone can help me please.

I bought a new keyboard, a noga NKB-710. The problem is that, according to xev, four of the keys have the same keycode...

The keys Ctrl, Alt, Win*** and shift, have the same keycode, 50. Off course, it doesn't work correctly. and this way, It's imposible to me to configure it with xmodmap.

I don't know what data I can share. I hope this to be sufficient:

attached a lsusb -v output

Thx, bye! :P Email had 1 attachment: + lsusb-v2 20k (application/octet-stream)

Have you tested if it works in other distros or other computers? Might narrow down the problem.

-- vixsomnis

(please bottom-post if you can)

I installed the xorg-xev package to compare to what you're seeing. I think the X11 keycodes are different from the codes actually sent by the keyboard.

Can you post the output of typing the problem keys when running $ sudo showkey

I have:

left-ctrl = 29 windows = 125 left-alt = 56 right-alt = 57 right-ctrl = 97 left-shift = 24 right-shift = 54

I think these are standard for all US keyboards.

That should confirm if the problem is with your keyboard (if the keys show the same code) or in the driver (or somewhere else).

There's also the slight possibility that it's a kernel bug, which would show up as repeating codes from showkey, since showkey is as close to the kernel as possible.

-- vixsomnis

Yes, sorry. My bad. I answered from my phone

With showkey I have the code 42 In alt, ctrl, shift and windows. Again, the same code on the keys :/

I'm from Argentina, So I don't have an english keyboard.

The keyboard works fine on windows :/. ¿Maybe is a Driver thing? :S

I dont know what else I can do :S. Is really a nice keyboard :'( jaja.

Thank you!

What's your keymap set to? I don't know what the Argentina layout or file is. Try temporarily switching to US qwerty (it'll clear on reboot) and see if that differentiates the keys. $ loadkeys us You can see which keymaps you have by checking /usr/share/kbd/keymaps -- vixsomnis

2015-06-02 0:38 GMT-03:00 Christian Demsar :

...

2015-06-02 0:10 GMT-03:00 Christian Demsar :

...

On Mon, Jun 1, 2015, at 10:36 PM, Facundo Curti wrote:

...

Distros/computer, I didn't. But in windows it works fine. :/ El 01/06/2015 22:55, "Christian Demsar" escribió:

...

On Mon, Jun 1, 2015, at 09:50 PM, Facundo Curti wrote:

...

Hi. I hope someone can help me please.

I bought a new keyboard, a noga NKB-710. The problem is that, according to xev, four of the keys have the same keycode...

The keys Ctrl, Alt, Win*** and shift, have the same keycode, 50. Off course, it doesn't work correctly. and this way, It's imposible to me to configure it with xmodmap.

I don't know what data I can share. I hope this to be sufficient:

attached a lsusb -v output

Thx, bye! :P Email had 1 attachment: + lsusb-v2 20k (application/octet-stream)

Have you tested if it works in other distros or other computers? Might narrow down the problem.

-- vixsomnis

(please bottom-post if you can)

I installed the xorg-xev package to compare to what you're seeing. I think the X11 keycodes are different from the codes actually sent by

On Mon, Jun 1, 2015, at 11:26 PM, Facundo Curti wrote: the

...

...

keyboard.

Can you post the output of typing the problem keys when running $ sudo showkey

I have:

left-ctrl = 29 windows = 125 left-alt = 56 right-alt = 57 right-ctrl = 97 left-shift = 24 right-shift = 54

I think these are standard for all US keyboards.

That should confirm if the problem is with your keyboard (if the keys show the same code) or in the driver (or somewhere else).

There's also the slight possibility that it's a kernel bug, which would show up as repeating codes from showkey, since showkey is as close to the kernel as possible.

-- vixsomnis

Yes, sorry. My bad. I answered from my phone

With showkey I have the code 42 In alt, ctrl, shift and windows. Again, the same code on the keys :/

I'm from Argentina, So I don't have an english keyboard.

The keyboard works fine on windows :/. ¿Maybe is a Driver thing? :S

I dont know what else I can do :S. Is really a nice keyboard :'( jaja.

Thank you!

What's your keymap set to? I don't know what the Argentina layout or file is.

Try temporarily switching to US qwerty (it'll clear on reboot) and see if that differentiates the keys.

$ loadkeys us

You can see which keymaps you have by checking /usr/share/kbd/keymaps

-- vixsomnis

Switching to us keymap makes me the same :/ it doesn't works I was using es layout before

2015-06-02 0:56 GMT-03:00 Christian Demsar :

...

2015-06-02 0:38 GMT-03:00 Christian Demsar :

...

On Mon, Jun 1, 2015, at 11:26 PM, Facundo Curti wrote:

...

2015-06-02 0:10 GMT-03:00 Christian Demsar :

...

On Mon, Jun 1, 2015, at 10:36 PM, Facundo Curti wrote:

...

Distros/computer, I didn't. But in windows it works fine. :/ El 01/06/2015 22:55, "Christian Demsar" escribió:

> On Mon, Jun 1, 2015, at 09:50 PM, Facundo Curti wrote: > > Hi. I hope someone can help me please. > > > > I bought a new keyboard, a noga NKB-710. The problem is that, according > > to > > xev, four of the keys have the same keycode... > > > > The keys Ctrl, Alt, Win*** and shift, have the same keycode,

On Mon, Jun 1, 2015, at 11:47 PM, Facundo Curti wrote: 50.

...

...

...

...

...

> > course, it doesn't work correctly. and this way, It's imposible to me to > > configure it with xmodmap. > > > > I don't know what data I can share. I hope this to be sufficient: > > > > attached a lsusb -v output > > > > Thx, bye! :P > > Email had 1 attachment: > > + lsusb-v2 > > 20k (application/octet-stream) > > Have you tested if it works in other distros or other computers? Might > narrow down the problem. > > -- > vixsomnis >

(please bottom-post if you can)

I installed the xorg-xev package to compare to what you're seeing. I think the X11 keycodes are different from the codes actually sent by

Off the

...

...

keyboard.

Can you post the output of typing the problem keys when running $ sudo showkey

I have:

left-ctrl = 29 windows = 125 left-alt = 56 right-alt = 57 right-ctrl = 97 left-shift = 24 right-shift = 54

I think these are standard for all US keyboards.

That should confirm if the problem is with your keyboard (if the keys show the same code) or in the driver (or somewhere else).

There's also the slight possibility that it's a kernel bug, which would show up as repeating codes from showkey, since showkey is as close to the kernel as possible.

-- vixsomnis

Yes, sorry. My bad. I answered from my phone

With showkey I have the code 42 In alt, ctrl, shift and windows. Again, the same code on the keys :/

I'm from Argentina, So I don't have an english keyboard.

The keyboard works fine on windows :/. ¿Maybe is a Driver thing? :S

I dont know what else I can do :S. Is really a nice keyboard :'( jaja.

Thank you!

What's your keymap set to? I don't know what the Argentina layout or file is.

Try temporarily switching to US qwerty (it'll clear on reboot) and see if that differentiates the keys.

$ loadkeys us

You can see which keymaps you have by checking /usr/share/kbd/keymaps

-- vixsomnis

Switching to us keymap makes me the same :/ it doesn't works

I was using es layout before

I may have been mistaken about scancodes vs keycodes (see https://wiki.archlinux.org/index.php/Extra_keyboard_keys#Scancodes).

Try this in a virtual terminal (ttyX, not xterm, gnome-terminal, etc):

$ sudo showkeys --scancodes

-- vixsomnis

Nope. :S Again have the same code. 0x2a when pressing, 0xaa when release.

2015-06-02 1:07 GMT-03:00 Christian Demsar :

...

2015-06-02 0:56 GMT-03:00 Christian Demsar :

...

On Mon, Jun 1, 2015, at 11:47 PM, Facundo Curti wrote:

...

2015-06-02 0:38 GMT-03:00 Christian Demsar :

...

On Mon, Jun 1, 2015, at 11:26 PM, Facundo Curti wrote:

...

2015-06-02 0:10 GMT-03:00 Christian Demsar < vixsomnis@fastmail.com>:

> On Mon, Jun 1, 2015, at 10:36 PM, Facundo Curti wrote: > > Distros/computer, I didn't. But in windows it works fine. :/ > > El 01/06/2015 22:55, "Christian Demsar" < vixsomnis@fastmail.com> > > escribió: > > > > > On Mon, Jun 1, 2015, at 09:50 PM, Facundo Curti wrote: > > > > Hi. I hope someone can help me please. > > > > > > > > I bought a new keyboard, a noga NKB-710. The problem is

...

...

...

...

...

> according > > > > to > > > > xev, four of the keys have the same keycode... > > > > > > > > The keys Ctrl, Alt, Win*** and shift, have the same keycode,

...

...

...

> > > > course, it doesn't work correctly. and this way, It's imposible to > me to > > > > configure it with xmodmap. > > > > > > > > I don't know what data I can share. I hope this to be sufficient: > > > > > > > > attached a lsusb -v output > > > > > > > > Thx, bye! :P > > > > Email had 1 attachment: > > > > + lsusb-v2 > > > > 20k (application/octet-stream) > > > > > > Have you tested if it works in other distros or other computers? Might > > > narrow down the problem. > > > > > > -- > > > vixsomnis > > > > > (please bottom-post if you can) > > I installed the xorg-xev package to compare to what you're seeing. I > think the X11 keycodes are different from the codes actually sent by

Off the

...

> keyboard. > > Can you post the output of typing the problem keys when running > $ sudo showkey > > I have: > > left-ctrl = 29 > windows = 125 > left-alt = 56 > right-alt = 57 > right-ctrl = 97 > left-shift = 24 > right-shift = 54 > > I think these are standard for all US keyboards. > > That should confirm if the problem is with your keyboard (if

On Tue, Jun 2, 2015, at 12:01 AM, Facundo Curti wrote: that, the

...

...

keys

...

...

...

> show the same code) or in the driver (or somewhere else). > > There's also the slight possibility that it's a kernel bug, which would > show up as repeating codes from showkey, since showkey is as close to > the kernel as possible. > > -- > vixsomnis >

Yes, sorry. My bad. I answered from my phone

With showkey I have the code 42 In alt, ctrl, shift and windows. Again, the same code on the keys :/

I'm from Argentina, So I don't have an english keyboard.

The keyboard works fine on windows :/. ¿Maybe is a Driver thing? :S

I dont know what else I can do :S. Is really a nice keyboard :'( jaja.

Thank you!

What's your keymap set to? I don't know what the Argentina layout or file is.

Try temporarily switching to US qwerty (it'll clear on reboot) and see if that differentiates the keys.

$ loadkeys us

You can see which keymaps you have by checking /usr/share/kbd/keymaps

-- vixsomnis

Switching to us keymap makes me the same :/ it doesn't works

I was using es layout before

I may have been mistaken about scancodes vs keycodes (see https://wiki.archlinux.org/index.php/Extra_keyboard_keys#Scancodes).

Try this in a virtual terminal (ttyX, not xterm, gnome-terminal, etc):

$ sudo showkeys --scancodes

-- vixsomnis

Nope. :S Again have the same code.

0x2a when pressing, 0xaa when release.

Ah, sorry. That's the extent of my knowledge. It might be a kernel bug, so you can submit a bug report (or try out the latest kernel in the testing repo).

Another option is trying an operating system with a different kernel, say freebsd. If you still have a problem, it's the fault of the keyboard (although this is unlikely since Windows sees it fine).

-- vixsomnis

No problem men! Thank you for helping me! I will try with a ubuntu livecd, changing the kernel, and if not, I will send a bug report. Thank you men!

On Tue, Jun 2, 2015, at 09:41 PM, Kodephault wrote:

Is your keyboard based on Microdia board? I had the same issue and I fixed it using a custom driver.

Please check the idVendor and idProduct with the lsusb command and maybe I can help you.

Regards.

Replying for OP (he attached the lsusb output -- appears to be Microdia). Some info is missing, probably not run under root. Bus 003 Device 003: ID 0c45:7603 Microdia Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0c45 Microdia idProduct 0x7603 bcdDevice 1.06 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 300mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 169 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 -- vixsomnis

2015-06-02 23:13 GMT-03:00 Kodephault :

Is the same model that has a known problem of keycodes interpretation.

I found a solution thanks to a guy called Colin Svinger that made a very complete post speaking deeply about this problem, you can find it on his blog: http://goo.gl/JcdvxG

That solution works great if you have an 101-key standard layout but mine has an 102-key layout, so many keys differs from his driver and I had to rebuild my own based on it but I haven't made it public by now.

Tell me if you need my version, regards.

Thank you men. I will see it.

2015-06-02 22:49 GMT-03:00 Christian Demsar :

On Tue, Jun 2, 2015, at 09:41 PM, Kodephault wrote:

...

Is your keyboard based on Microdia board? I had the same issue and I fixed it using a custom driver.

Please check the idVendor and idProduct with the lsusb command and maybe I can help you.

Regards.

Replying for OP (he attached the lsusb output -- appears to be Microdia). Some info is missing, probably not run under root.

Bus 003 Device 003: ID 0c45:7603 Microdia Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0c45 Microdia idProduct 0x7603 bcdDevice 1.06 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 300mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 169 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10

-- vixsomnis

Yes, it seems to be a microdia. How do you fixed it? idVendor 0x0c45 Microdia idProduct 0x7603 I attach a new lsusb -v as a root. it seems that there are errors: can't get debug descriptor: Resource temporarily unavailable Thank you for help!