weird DAS 3

[ins]

My DAS 3 (the 'eth' version) arrived today! I've plugged it in and to my surprise it's not working correctly besides the known flaw:

hitting shift 5 oder shift 6 gives me %T and ^Y. It's present on linux/windows (even in grub) and I've checked it on my notebook with the same result.

Did somebody encounter the same problem? Is there a fix (trying different setxkbmap options didn't resolve the issue)?

xev reveals faulty keystrokes too:

KeyPress event, serial 34, synthetic NO, window 0x3400001,
    root 0x13c, subw 0x0, time 3677908, (95,94), root:(100,119),
    state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes:                                    
    XmbLookupString gives 0 bytes:                                  
    XFilterEvent returns: False                                      

KeyPress event, serial 34, synthetic NO, window 0x3400001,
    root 0x13c, subw 0x0, time 3680693, (95,94), root:(100,119),
    state 0x11, keycode 15 (keysym 0x5e, asciicircum), same_screen YES,
    XLookupString gives 1 bytes: (5e) "^"                              
    XmbLookupString gives 1 bytes: (5e) "^"                            
    XFilterEvent returns: False                                        

KeyPress event, serial 34, synthetic NO, window 0x3400001,
    root 0x13c, subw 0x0, time 3680693, (95,94), root:(100,119),
    state 0x11, keycode 29 (keysym 0x59, Y), same_screen YES,  
    XLookupString gives 1 bytes: (59) "Y"                      
    XmbLookupString gives 1 bytes: (59) "Y"                    
    XFilterEvent returns: False                                

KeyRelease event, serial 34, synthetic NO, window 0x3400001,
    root 0x13c, subw 0x0, time 3680805, (95,94), root:(100,119),
    state 0x11, keycode 15 (keysym 0x5e, asciicircum), same_screen YES,
    XLookupString gives 1 bytes: (5e) "^"                              
    XFilterEvent returns: False                                        

KeyRelease event, serial 34, synthetic NO, window 0x3400001,
    root 0x13c, subw 0x0, time 3680805, (95,94), root:(100,119),
    state 0x11, keycode 29 (keysym 0x59, Y), same_screen YES,  
    XLookupString gives 1 bytes: (59) "Y"                      
    XFilterEvent returns: False                                

KeyRelease event, serial 34, synthetic NO, window 0x3400001,
    root 0x13c, subw 0x0, time 3684789, (95,94), root:(100,119),
    state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes:                                    
    XFilterEvent returns: False

I like the feel of the keys and I could live with the glitch but not being able to use ^ and % in ONE key stroke is not acceptable.

trigging shift_right 5 or 6 produces '%F' and '^J'. shift - = has problems too.

considering to swtich to the Filco Majestouch Tactile Click "Otaku" NKRO if there is no fix.

This keyboard does not deserve a german article!

[ch_123]

Welcome to Geekhack.

The controller of the Das is notorious around here for doing just about everything except working. Fortunately Metadot have a good returns policy. To be honest, even if there is a user-serviceable solution for your particular problem, I'd just return it and get the Filco which is a much better keyboard in just about everyway except for lack of USB hub.

[alexlzl]

My colleague had the exact same problems 5 months ago and exchanged the DAS twice (the second one has some other issues). Eventually he returned it and got a Realforce.