Ok, re-assemebed for the 10th time (no kidding) and various rows came and went. I read richk on the Lenovo forums:seasonshu wrote:However, the other one is dead in the middle section, everything included:
Did you tape the pins inside the keyboard? Tape must be thin enough to not disrupt near connections.seasonshu wrote:I modded two keyboards, flashed the X230. One of the is working fine.
However, the other one is dead in the middle section, everything included:
4-8
r-i
f-k
v-,
space,=,bkspace,\,enter
does not work. I tried putting the wrong one into the X220, then removed the mod, nothing.
Did I probably tear the cable while modding? Any chance of comeback from this? I ordered the keyboards from the US (to UK) for mainly their layout; the shipping price + Royal Mail "handling fee" was really eye watering...
Thanks.
I'm not sure if the X230's keyboard would fit on an X201T. :OBrothahHeffay wrote:Strange request, but I'd like to do the opposite of what everyone else is doing. I'd like to install a backlit x230 keyboard in my x201 tablet!
I guess it's not really a good idea since there's no much people ready to pay for such thing.evening_hunger wrote:It would be a good idea to do such a mod on, let's use this expression, global scale. So for example, make a small fundraiser (forum people would suffice), buy e.g. a T470, and retrofit it with an old keyboard. By which I mean long n' painfull bios cracking, however I get the feeling the hardest part is finding gear to sacrifice:)
Do you think that eventually it would be possible to achieve these features or some of them? I imagine the Capslock LED may be too proprietary, but maybe the Fn-combinations can be done? I understand there are some concerns, so would it be possible to make a test patch, for the daring? What's the worst thing that can happen if wrong values are used, for example, for Fn+F12 (Hibernate)?hamish wrote:Additionally, the Capslock light doesnt work on the classic keyboard.
- Fn+Space ("zoom" - I never used it, so I dont know that it ever did anything much)
- Fn+Battery (It might be possible to remap this, but I didnt see it as very important, and there were some complications)
- Fn+Hibernate (This should be possible to make go, but the existing data in the firmware concerned me, so - out of cautiousness - I left it unworking)
Ah, updated.RealBlackStuff wrote:It would make sense if you'd enter your location in your profile.
Without looking - I doubt it.. I did look at the x220 tables and they were the same size as on all the x*30 systems.charlotteplusplus wrote: Thanks for the updated documentation - now I see the size problem. 17 slots would be sufficient to cover all the F1-F12 number +4 arrows + space. But maybe the size of the table changed with EC releases.
I wonder if there are also 17 slots on the W520 EC. (I have a W520; I want to add the shortcuts to its native keyboard)
The simplest way I can think of is that I have documented the locations for these tables in the x220 EC firmware version I looked at, so you should look there to see what the table looks like - and then use that to do a binary search in your w520 EC firmwarecharlotteplusplus wrote:
How do you locate the table and check its size?
It is quite possible to do - all the details are known for the tables in the xx20. New patches would be required, also I have not looked at how to build a correct firmware image for the xx20 series - so that could be difficult.Starlight5 wrote:Did anyone make the opposite mod (x30 keyboard in x20 machines) eventually? I'd like to get an x30 keyboard because I like it better, especially the layout, but since I have fully functional machine I'm somewhat lazy to experiment myself, while would adopt tried&tested solution if there is one.
I cannot remember what the Fn+Space issue was - it might actually be working (but as I dont use it, couldnt test it).dr_st wrote:Do you think that eventually it would be possible to achieve these features or some of them? I imagine the Capslock LED may be too proprietary, but maybe the Fn-combinations can be done? I understand there are some concerns, so would it be possible to make a test patch, for the daring? What's the worst thing that can happen if wrong values are used, for example, for Fn+F12 (Hibernate)?hamish wrote:Additionally, the Capslock light doesnt work on the classic keyboard.
- Fn+Space ("zoom" - I never used it, so I dont know that it ever did anything much)
- Fn+Battery (It might be possible to remap this, but I didnt see it as very important, and there were some complications)
- Fn+Hibernate (This should be possible to make go, but the existing data in the firmware concerned me, so - out of cautiousness - I left it unworking)
Of these three I would be using the Hibernate functionality reguarly. Although it's not a firmware solution but at some point (not sure when) I am thinking of checking if the same functionality could be achieved using the 'AutoHotKey' Windows software -- even if the key combination would be something different to Fn-F12. I guess it doesn't really help users running Linux but could be a solution for others, nevertheless.hamish wrote:I cannot remember what the Fn+Space issue was - it might actually be working (but as I dont use it, couldnt test it).
The Fn+Battery combo was similarly hard to test for me - but there was an issue with the swapping of the Fn+Lock that might have made it not work properly.
With the Fn+Hibernate, there was no clear clues to the right code and since the penalty for failure was probably a bricked laptop, I was afraid to try it.
I see. It does not actually have a pointer to a function, but a "magic number" which encodes the function. Without knowing which number encodes what, it would indeed be difficult to guess what value to put there. Is there even a Hibernate function hook in the *30 series EC?hamish wrote:I cannot remember what the Fn+Space issue was - it might actually be working (but as I dont use it, couldnt test it).
The Fn+Battery combo was similarly hard to test for me - but there was an issue with the swapping of the Fn+Lock that might have made it not work properly.
With the Fn+Hibernate, there was no clear clues to the right code and since the penalty for failure was probably a bricked laptop, I was afraid to try it.
Some of this is shown in the documentation at https://raw.githubusercontent.com/hamis ... fnkeys.txt
The primary advantage of Fn+F12 is that it works in all environments, but other than that it's not difficult at all to get a different key combination for hibernation (the Fn key does not generate a scancode, so you will not get it to work via Fn+F12).seasonshu wrote:Of these three I would be using the Hibernate functionality reguarly. Although it's not a firmware solution but at some point (not sure when) I am thinking of checking if the same functionality could be achieved using the 'AutoHotKey' Windows software -- even if the key combination would be something different to Fn-F12. I guess it doesn't really help users running Linux but could be a solution for others, nevertheless.
That won't work! The boards are different, at least for the X220/X220T. The battery connector and display connector are at different positions! See here:CPC464 wrote:Hi,
I managed to adquire a cheap X230 tablet system board (I7 3520m), and my plan is to mount it in my X220 (non tablet)
OK, thank you for your answer and the images! I've assumed that tablet and non-tablet models were sharing the same physical board, like former Thinkpads like X61s and X61T did.StefanKo wrote:That won't work! The boards are different, at least for the X220/X220T. The battery connector and display connector are at different positions! See here:CPC464 wrote:Hi,
I managed to adquire a cheap X230 tablet system board (I7 3520m), and my plan is to mount it in my X220 (non tablet)
http://abload.de/img/dsc_0485axspk.jpg
http://abload.de/img/dsc_0488pas9b.jpg
http://abload.de/img/dsc_0490f4s0s.jpg
The board with fan is a non-tablet X220 board, the other one a X220T board.
There is indeed - you just need to rename the patches to apply the battery patch and not apply the keyboard patches. There is some information in the repo readme for this - have a look and see is that makes sense to you.emeraldgirl08 wrote:Is there a way to use the EC firmware mod to only remove the battery validation check and allow me to keep the chiclet keyboard?
Not too confident about executing this procedure! If anyone could help me I would appreciate it through PM. I rely heavily on my X230 and my battery charge is ~12% TIA.hamish wrote:
There is indeed - you just need to rename the patches to apply the battery patch and not apply the keyboard patches. There is some information in the repo readme for this - have a look and see is that makes sense to you.
That's fair enough. This is not an uncommon question, so I can try and write up some better instructions and add them to the repository. I probably will not get a chance to do that until next week - so try and hang in there!emeraldgirl08 wrote:Not too confident about executing this procedure! If anyone could help me I would appreciate it through PM. I rely heavily on my X230 and my battery charge is ~12% TIA.hamish wrote:
... you just need to rename the patches to apply the battery patch and not apply the keyboard ...
Thanksnitrocaster wrote:Nice performance, hamish! Regarding the further work: did you get any far with the capslock led?
Why unlisted?hamish wrote:Also, the recording of the talk is now online at https://www.youtube.com/watch?v=Fzmm87oVQ6c
Users browsing this forum: No registered users and 2 guests
Homepage
Forum
Drivers
HMM
MTM
Feed
