System Details
- Device: DA0ZHRMB6F0 (CYAN)
- OS: Windows 10 23H2
- Firmware Type: [UEFI Full ROM only]
- Firmware Version: Latest
- Internal storage type: eMMC
Summary of the Issue
After flashing the BIOS with the latest UEFI script last night, I made a boot stick with Windows 10 and Rufus, and installed. All that works fine, but upon launch the drivers do not. Touchpad, audio, touchscreen, keyboard. When installing the coolstar drivers, everything is fixed EXCEPT the keyboard. I have read time and time again on here, reddit and the discord server that the keyboard should “just work” and be fine “out of the box”. I’ve also read that the PS/2 generic keyboard driver should work. Neither of these things are true in my case and the keyboard is completely unusable no matter what I try, except in the BIOS screen of course. I’ve tried two other, different versions of Windows 10 and the issue persists.
The keyboard is obviously physically fine, and with everyone else saying “it just works lol” there’s clearly something going on here at the OS level but I can’t determine what. I’ve wiped the drivers and tried reinstalling the coolstar ones fresh, as well as the generic drivers fresh, and no results.
Here’s a cbmem.log:
Additionally, I have verified that there are no missing/unknown device drivers in device manager. I’ve seen it suggested to just disable/re-enable the keyboard driver which also isn’t possible. I used Snappy Driver Installer Origin, and that also did not fix the keyboard.
what do you mean it’s not possible. You should have a Chromebook Keyboard device in DM
Obviously. The option doesn’t exist on right-click, and is greyed out when viewed in properties, only update or uninstall can be clicked. On this device, the driver doesn’t seem to do anything. The driver details say it’s started, yet not one key works. The same occurs with PS/2 driver.
From what I’ve repeatedly read, the coolstar drivers hardly even matter for functionality if the intent is to just remap the top-row keys; the keyboard should in fact work “out of the box™” with generic drivers, which doesn’t occur (on this machine).
works fine on mine here, so you’re going to need to provide a bit more information for anyone to be able to help
What information would be helpful? The flashing process was completely smooth from start to finish, the now-installed OS works fine in and of itself, and every other driver but the keyboard one has been successful in making things work. Touchpad, touchscreen, audio, webcam, microphone, etc.
I also provided a cbmem.log in the OP, but other than that I don’t know what to give you other than device manager pastes.
For instance, sometimes the PS/2 driver says it has started, other times it doesn’t start. Varies on boot. This is one of the instances of it not starting:
Device ACPI\GOOG000A\0 had a problem starting.
Driver Name: keyboard.inf
Class Guid: {4d36e96b-e325-11ce-bfc1-08002be10318}
Service: i8042prt
Lower Filters:
Upper Filters:
Problem: 0x33
Problem Status: 0x0
But considering the problem remains even when it has started, I don’t know what to make of it. The EC keyboard driver from coolstar also claims to have been started, working fine, and say that the device is receiving power and, again, the keyboard does not function.
EDIT: After another round of driver cleaning and reinstalling the coolstar driver, I have observed the chromebook keyboard driver also having this same error.
Tried an Ubuntu drive to check the flash, clear NVRAM and reflash. All worked fine. And the keyboard worked flawlessly. I’m going to try some older versions of W10 that I’ve not tried already, and if that doesn’t pan out I’m just gonna say fuck it and go Linux.
EDIT:
Tried three other versions of W10, failure after failure. I installed Lubuntu and everything worked from the start. Obviously there’s some niche or rare issue with this model and playing well with Windows. I don’t have the patience nor the time to waste guessing and failing at solving this and it’s blatant that no one else does either, so, I guess that’s that. If anyone else comes across this with the same issue, sorry for your luck. Try Linux!
are you serious? your post has been up for 10 whole hours
A 10 whole hours you occasionally took part in and offered nothing of substance, just “uhh it should work dude!” and “I dunno, works for me lol!”. What impression do you want me to have? In trying to research this particular issue, anything similar from other people received the same apathetic one-sentence dismissals from you, and zero suggestions from others.
Thanks for the flashing utility though! That’s about the only thing that’s gone right here.
everything on the device works under both Windows and Linux, with the lone exception of the keyboard issue you’re having under Windows - which is a Windows issue of some sort.
I’m not a Windows dev or even a Windows user. I boot test Windows to make sure the firmware is working properly; coolstar is the one responsible for the Windows drivers.
Everything is working on CYAN here under Win11 25H2. No idea about Win10, I don’t test that.