Tried everything, installed all coolstar ec drivers over again, reset chromebook, everything. Am i missing a driver? What am i doing wrong?
the battery doesn’t require any drivers, it’s handled via ACPI. Sounds like there’s an ACPI error that’s causing Windows to not process the battery section. Boot Linux and run sudo dmesg > dmesg.log
and upload to pastebin/dpaste etc and link here.
@MrChromebox I can confirm a similar issue with Craasneto. The battery is not detected in Windows at all. I have tested multiple versions of Windows, but the issue persists.
Here is the dmesg log: https://pastebin.com/raw/VeXfKWNn
will need an acpi dump which the chrultrabook debugging script should provide
Сhrultrabook debugging script seems to be unavialable… I dumped it using Acpica tools, will this work?: acpi_dump.dat - Google Drive
use acpidump -b
then tar.gz the resulting .dat files, as I need the full set of tables to decompile them
Here it is: full-dump.tar.gz - Google Drive
don’t see anything obvious at first glance, will take a closer look later today
Thanks, that would be great.
Thanks Mrchromebox for the great work, which made windows possible for us.
My craasneto device is also having same problem - battery is not displayed, on initial login screen a battery empty icon is shown. Battery is charging fine after installing coolstar usb c and audio drivers. Also device doesnt seem to enter deep sleep.
my device details -acer chromebook plus - CB514-4H-39T7 - device name chrome recovery screen - craasneto-kyvc . mrchromebox firmware shows acer chromebook 314 in uefi menu.
all devices seems to be recognised in device manager - but there is one device with warning symbol in device manager -Intel(R) Serial IO I2C Host Controller - 54C5 - error shown is “This device cannot start. (Code 10)
STATUS_DEVICE_POWER_FAILURE”
Here is the acpi dump from linux. have also included dmesg.log in the compressed acpidump folder.
acpidump.tar.gz
edit- (corrected link)
thanks a ton again
I’m not seeing any substantial difference between the ACPI for CRAASVIN (which works) and CRAASNETO (which does not). CRAASNETO is an 8-core device (vs 4 for CRAASKVIN) and uses NVMe (vs eMMC), but those differences wouldn’t cause any breakage in Windows’ ACPI parsing.
This is going to have to remain a known/open issue unless someone more familiar with Windows ACPI debugging is able to assist.
Thank you
is this issue related to acpi? hope it is not a hardware issue?
that’s I2C4, which is not used on ADL-N Chromebooks. It’s disabled in coreboot, but apparently Windows thinks the device exists because there is an ACPI stub for it. It’s harmless and can be ignored. I’ll try to clean this up in a future release.
Thank you.