@fhvyhjriur stays over reboot? Problem was that it was not staying (cold boot/war boot/reboot), same reported on some x230 since then as well.

Coreboot devels contacted, even issues opened upstream... Still considered not working and would require ps2 code modified under coreboot to force proper keyboard (AT2 translated), bypassing automatic flawed detection, or having linux kernel module switch to be forced for all x230. Behavior being fixated by first ps2 keyboard initializer.

Both solutions not yet implemented. Basically you are lucky here and real cause of issue still not fixed in code AFAIK.

For some traceability.

2254 is 27d09d4 so 24.04.02 coreboot based with ps2 init still on.

If someone can invest time to see if ps2 code was rewritten or replicate this RAW/TRANSLATED AT2 keyboard detection and can confirm that the problem vanished once and for all and pinpoint why and where this was fixed, then @fhvyhjriur x230 and x230t should be exactly the same board from coreboot perspective last time I checked. There would not be any need of creating/maintaining yet another board variant, and past e-ink across everything searchable x230t should answer your questions in this repo.

Assigned to myself because /i have a x230t somewhere, so if I can have behavior stable across reboots/cold boot/reboots, then x230 could be advertised as also working on x230t and this issue could be closed as resolved when actual code fix si traced back to why the problem is fixed now. Maybe TOP_DOWN allocator?! unsure really, this being fixed without reason is just weird as of now.

Backspace works on cold boot after first flash. Testing #1541 derivate on undusted x230t real hardware.

Will reply here after reboot/warm boot/reset->q4.2 after total re-ownership (btrfs partitions reencryption from custom 4.2 install on disk for #1541 with proper Argon2 sturdier key addition from TPM DUK and proper reencryption speeds and reusing OS install LUKS containers)

Weird, I confirm this works on x230t now.

Time to understand why now. Anybody sees what changed under coreboot?

Hmmm will need to do this local, cannot just do files changes from web GUIs to sshare process with community, too many changes.

coreboot/coreboot@4.22_branch...24.02_branch

Nothing directly linked to PC80 not PS/2 from what I see....

Well, could be linux kernel version bump as well, good news is that its fixed :/

Note that I only tested coreboot 24.02.01 with linux 5.10.214 per https://github.com/linuxboot/heads/pull/1541/files#diff-2b51dc9d1602ab31c054d57804a441059a68dcfdf7f3c407f83a85148bcecfc6R31

@fhvyhjriur: what would fix this issue? As of today, x230t was considered not supported by Heads x230 board flavors. Today it would. A note added under board configs?

@fhvyhjriur ping

@fhvyhjriur reping

Some GPIO's was strange(my expectation) on my test but the keyboard was now fine.

Could you confirm following issues on your hardware?

• The Powerbutton for example does not work as a powerbutton any more. Even the default ATX-Shutdown that have to always work does not work. You can turn the x230t on with the powerbutton, but then even pressing and holding it for a long time does not turn the x230t off.
• Soudcard is not working

Because this is been asked often on coreboot development: Yes, S3 is working fine

Some GPIO's was strange(my expectation) on my test but the keyboard was now fine.

Could you confirm following issues on your hardware?

• The Powerbutton for example does not work as a powerbutton any more. Even the default ATX-Shutdown that have to always work does not work. You can turn the x230t on with the powerbutton, but then even pressing and holding it for a long time does not turn the x230t off.
• Soudcard is not working

Because this is been asked often on coreboot development: Yes, S3 is working fine

That answers the question then. No I haven't tested extensively x230t but keyboard. This means x230t cannot be supported through x230 board flavor and x230t coreboot config should be brought in: hotp and non-hotp variants just like the x230.

PR welcome, @fhvyhjriur. Use helpers of modules/coreboot end file to modify and save config after haviong copied boar configs, renamed x230t coreboot config to a distinct file and make something that works for you. If you create a PR. I will test and merge.

Renamed issue

Some GPIO's was strange(my expectation) on my test but the keyboard was now fine.
Could you confirm following issues on your hardware?

• The Powerbutton for example does not work as a powerbutton any more. Even the default ATX-Shutdown that have to always work does not work. You can turn the x230t on with the powerbutton, but then even pressing and holding it for a long time does not turn the x230t off.
• Soudcard is not working

Because this is been asked often on coreboot development: Yes, S3 is working fine

That answers the question then. No I haven't tested extensively x230t but keyboard. This means x230t cannot be supported through x230 board flavor and x230t coreboot config should be brought in: hotp and non-hotp variants just like the x230.

PR welcome, @fhvyhjriur. Use helpers of modules/coreboot end file to modify and save config after haviong copied boar configs, renamed x230t coreboot config to a distinct file and make something that works for you. If you create a PR. I will test and merge.

@fhvyhjriur I created x230t PR at #1791. Just like I did x200 which lead nowhere. I'm doing my best but this is unfortunately of low interest for me and the community, i'm sorry: this is reality.

Trail of commands there showing you not needing to be a developer, just somewhat really interested into making this go forward for yourself if you really wanted: learning is possible for all curious enough. Asking others to do that for oneself for whatever personal interests not matched by community won't be sustainable, that is a fact. Selfish contributionnism is a thing as already discussed elsewhere. This is my last attempt to fulfill user needs that don't match my priorities or bugfixes for what already works and have Pareto outcome. Consider this said multiple times. If #1791 doesn't work, then this is upstream issue. No I won't create x220t board flavors nor add other boards not brought back by users interested enough into participating to this project and making things work for others. Once again Heads is a community FOSS project, and contributionnism is expected in form of code/donations/testing: testing doesn't just mean saying works/ot works, it means making it work or being able to troubleshoot leading for things to work for othrs. Otherwise this is me giving infinite supplies of fish where what I try to do is give fishing lines. Last unsustainable attempt of pleasing testers that will only say: works/doesn't work. Boards should be brought to master by people technical enough to learn how things work and move the ecosystem forward. Sorry, but time and resources are limited.

I'm grateful for your testing and support to Heads, but again, I wish you were bringing people who can help fix things that doesn't work, not just say things doesn't work. Boards expected to work having a "works" tag is good, but as also previously said: when things won't work, what am I supposed to do next? How much time you expect me to put in things/boards nobody else uses? I get you want blobless hardware, this is my fight too. But gains are limited unless technical enough to make things work for others, not just say it doesn't work. Know others that have that board from coreboot? Bring those people in. Open issues at coreboot. Don't expect me to fix everything for everyone on boards not yet supported under Heads. Hope you understand this. I cannot explain priorities in each issues/PR. Technical people should port boards they care about to Heads and collaborate upstream for things that don't work. Heads is a coreboot user, and therefore, things not working under coreboot needs to be worked upstream, where downstream (Heads) can at best be used to build and stitch roms to be tested upstream for specific configurations: that requires upstream participation. If you think you are not technical enough to take that task, there is not much I can do here to support your adventure. You need to connect to more technical board owners of yours that can help work problems out into solutions; don't expect me to be that person for all boards you are interested in. I unfortunately do not/will not have the time to support your interests alone.