-
Notifications
You must be signed in to change notification settings - Fork 86
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
keyboard and touchpad #8
Comments
I wrote a script for handling keyboard and display when the lid is closed/open. It turned out to be very simple. One has to have the
and
It seems to work. It depends on the usb bus id of the keyboard+touchpad and the lcd brightness control location. Are these likely to change with time? Am I doing this right? |
For some reason, the |
Teres 1 slowly becomes actually usable for me. I plan to share my configs, or the system image, when I am done. I need to figure out how to configure the touchpad. It is way too sensitive to taps, and very hard to scroll with two fingers. Is there any documentation for noobs here? For example, what are the parameters
And how to compile the keyboard files and flash them? |
About compilation: https://github.com/d3v1c3nv11/TERES-KBD-RELEASE.git On how to update: https://github.com/d3v1c3nv11/TERES-KBD-RELEASE/tree/master/upgrade |
Thanks, I will look at it. I only now realized the the battery charge "percent" is reported as Not yet clear how to estimate time to discharge, but this is secondary. Lxde works mostly very well... the only problem I have is the volume regulation with alsa (I didn't install pulseaudio). |
About Sleep button: New firmware released. To upgrade follow instruction in Readme. https://github.com/d3v1c3nv11/TERES-KBD-RELEASE/tree/master/upgrade |
I am not on ubuntu... Is it possible to make the updater static?
I will install the avr toolchain and build the updater in any case, but this takes time. |
The problem with libusb-0.1.so-4 was solved by installation of libusb-compat, the upgrade went through. |
I updated the keyboard firmware and made some test. With
In X, with
It seems, f4-f12 are OK except maybe the |
In our image keycodes reported by xev, evtest, etc., are result of codes generated by keyboard firmware as defined here ...ckickme..., then is transcoded by hidkbd driver ...clickme... then changed by ...hwdb... to be reported to system right as labeled. You are free to change each of those elements to get the right codes for the linux distro you're using Is this really an issue with our image and firmware? Should i consider it solved? |
Thanks for the explanation! I don't know with what the issue is, and I did not look deep. I just checked Fn+f1 on the stock ubuntu, and it is just the same as above. There is no sleep event, and suspend does not happen. I think the issue with the key mapping is not a big one, even though it would be good to do it properly. A bigger problem is the sensitivity of the touchpad. I would appreciate a hint here. I did not find any obvious clues and did not have time to investigate. |
Oooops, sorry. I forgot to change the hwdb, my bad. There is an acpi suspend event on stock ubuntu now! I will investigate. |
Suspend works! I make a mistake in |
Finally! |
Hey, I think it is early to close this issue. It was created for two things: sensitivity of the touchpad and that the lid presses on the keyboard. It is totally great to get the suspend button to work, but it wasn't the focus. |
This is an issue to track a couple of problems with the keyboard and touchpad. I'll attempt to do something about them, but it may take long time before I start, and then I am new to all this.
The text was updated successfully, but these errors were encountered: