Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Console not working #8

Open
Nils-TUD opened this issue Oct 30, 2012 · 6 comments
Open

Console not working #8

Nils-TUD opened this issue Oct 30, 2012 · 6 comments
Labels

Comments

@Nils-TUD
Copy link
Member

The console is not working on a system with USB keyboard and legacy USB emulation. The keyboard is delivering scancodes correctly, but the console does not seem to comprehend them. Here's some log output of functions I instrumented:

[2] kb: handle_scancode key=2
[6] kb: input_thread flags=800 scancode=2 keycode=0 character=0
[2] kb: handle_scancode key=82
[6] kb: input_thread flags=800 scancode=82 keycode=0 character=0
[2] kb: handle_scancode key=3
[6] kb: input_thread flags=800 scancode=3 keycode=74 character=0
[2] kb: handle_scancode key=83
[6] kb: input_thread flags=800 scancode=83 keycode=76 character=0
[2] kb: handle_scancode key=4
[6] kb: input_thread flags=800 scancode=4 keycode=72 character=0
[2] kb: handle_scancode key=84
[6] kb: input_thread flags=800 scancode=84 keycode=0 character=0
[2] kb: handle_scancode key=5
[6] kb: input_thread flags=800 scancode=5 keycode=70 character=0
[2] kb: handle_scancode key=85
[6] kb: input_thread flags=800 scancode=85 keycode=0 character=0
[2] kb: handle_scancode key=6
[6] kb: input_thread flags=800 scancode=6 keycode=71 character=0
[2] kb: handle_scancode key=86
[6] kb: input_thread flags=800 scancode=86 keycode=0 character=0
[2] kb: handle_scancode key=7
[6] kb: input_thread flags=800 scancode=7 keycode=7b character=0
[2] kb: handle_scancode key=87
[6] kb: input_thread flags=800 scancode=87 keycode=0 character=0
[2] kb: handle_scancode key=8
[6] kb: input_thread flags=800 scancode=8 keycode=0 character=0
[2] kb: handle_scancode key=88
[6] kb: input_thread flags=800 scancode=88 keycode=0 character=0
[2] kb: handle_scancode key=9
[6] kb: input_thread flags=800 scancode=9 keycode=79 character=0
[2] kb: handle_scancode key=89
[6] kb: input_thread flags=800 scancode=89 keycode=0 character=0
[2] kb: handle_scancode key=a
[6] kb: input_thread flags=800 scancode=a keycode=77 character=0
[2] kb: handle_scancode key=8a
[6] kb: input_thread flags=800 scancode=8a keycode=0 character=0
[2] kb: handle_scancode key=b
[6] kb: input_thread flags=800 scancode=b keycode=75 character=0
[2] kb: handle_scancode key=8b
[6] kb: input_thread flags=800 scancode=8b keycode=0 character=0

@Nils-TUD
Copy link
Member Author

Looks to me as if you have set scancode set 1. Have you specified that in the commandline of the keyboard application via "scset1"? Because the default is 2.

@Nils-TUD
Copy link
Member Author

Specifying scset1 does the trick. Would be nice if the scancode set could be autodetected.

@Nils-TUD
Copy link
Member Author

Of course. If you know a simple and reliable way, please tell me :)

@Nils-TUD
Copy link
Member Author

How about NUL's approach? Try setting the keyboard to scancode set 2 via F0-02. If that fails, you could fall back to scancode set 1.

@Nils-TUD
Copy link
Member Author

This is exactly what NRE does, because the keyboard-stuff has been ported from NUL and just structured a bit differently and wheelmouse-support has been added. As it seems, this detection doesn't always work.

@Nils-TUD
Copy link
Member Author

Oh, I see. So apparently, the scancode set command succeeds, but the actual scancode setting remains the same. Maybe one could check the setting afterwards via F0-00?

@blitz blitz mentioned this issue Nov 2, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant