no, it corrects the VRAM allocation from the previous release, which was inadvertently set to 2GB. Trackpoint is still disabled
Okay, thanks again.
Hey 
I appreciate the time/effort put into getting this working. I just got a C13 Yoga and tested in a couple of distros. Although Fedora was hit-or-miss, Endeavour just worked.
I’ve read a couple of weeks back that the trackpoint was causing CPU problems. Is this still ongoing? If not, would you possibly be able to generate a new version with the trackpoint enabled?
I understand that this might require some time - and it is done as a best-effort - so if that’s not possible, I’m OK too.
Thanks, man! Have a great day 
1 Like
I didn’t have any issues on Fedora personally. I’ll see about reinstalling that on mine- if you have any major issues with Fedora 39 Gnome or KDE, ping me in a new post.
Yeah I also didn’t had issues - just preferred the usability @ Endeavour. Youtube is less choppy and I didn’t felt like dealing with vaapi and the alike, for which Endeavour just worked. The main point really is/was regarding the coreboot version with trackpoint and buttons. That really would make this 100% for me!
1 Like
this issue is resolved with the 4.22 update – there is also an option to enable the trackpoint for linux users.
After updating the firmware, I rebooted my computer, but the screen is black. Only the CPU fan is running, with no other response. What should I do? 
There might have been an unexpected shutdown, but I’m not sure.
I’ve had no shutdowns during flash, but it also broke on me. Got a “a start job is running for /efi”, with a 30s timeout.
I can get to recover, so I might be able to reflash a version. Will try.
EDIT: pic with the error
Uhhh. Weird. Plugged it in the charger once, it worked. It now boots fine, with or without the charger. I don’t really understand, but I’m happy. Will download the stuff needed for manual flash in case of further issues.
I was already pulling my USB drive to download flashrom-libpci38, but that wasn’t needed.
Thanks all, merry Christmas!
Too soon, I guess. Same error after waking up from sleep.
Also the “plugged in” stuff was a fluke - it still breaks when the charger is connected.
Update: the non-trackpoint enabled firmware also fails, with the error “cannot identify the EC”. During rescue, if I do a systemctl enable NetworkManager --now and reboot, next boot will work, sometimes. Might also be a fluke.
Update 2: Dmesg attached
Update 3: While still diagnosing, I can go to the desktop by:
- Executing any systemctl command (i.e, starting network manager)
- Then, doing a systemctl start efi.mount
- Efi is mounted, you can proceed with Ctrl+D
Update 4: It booted after a couple of tries again. I’ve changed sources as a previous comment here and could put in a stable version. I’m fine now, as before the update.
TL;DR: the update broke my boot, resulting in messages like Cannot identify the EC during boot, which happened 5 out of 6 boot tires. I could go to the desktop, but couldn’t do much (no network, no drivers loaded, etc).
This happened with and without the trackpoint-enabled firmware, so likely another change was the culpirit.
I have a firmware backup of both ChromeOS and MrChromeBox locally, in case I need to flash out after failures - as such, I’m available to troubleshoot any new versions once they’re made.
Thanks, all! Sorry for the flood
Also note that the NVMe versions of the C13 Yoga are easier to install distros on. For the eMMC versions, you can install to the eMMC if you want, but you’ll likely have to use a MicroSD card for your home folder.
I have resolved the issue of the screen going black and being unable to boot due to a failed firmware update. Disassembling the machine to find the BIOS chip and then using a WSON8 probe to flash the BIOS is a viable solution. I used CH341A to flash the backup ROM I had, and it was successful. Also, the model of the BIOS chip is W25Q128FW, and the voltage is 1.8V. I hope this information can be of some help to others. 
4.22-2 has fixed suspend/wake issue
Hey, is this the problem I’ve reported, where I can’t boot 5 out of 6 times? I assume not, but 
best to ask =)
Just in case: my device uses NVMe
Thanks!