Opened 5 years ago
Last modified 5 years ago
#15381 new bug
Haiku doesn't like system clock of Coreboot+Seabios systems. — at Version 1
Reported by: | trashHeap | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | - General | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
Every nightly build I've tried the past few weeks results in Haiku unable to read or write to the system clock accurately.
The following steps for me today resulted in Haiku reporting back a current date/time of 4/8/61 2:12 PM.
- Booting the system cold into Haiku.
- Connecting to WiFi and and initiating a network time synch at approximately 1:08 pm.
- Rebooting back into Haiku, via the reboot option in the Deskbar menu.
Reproducible on a Thinkpad X230 and X230T, both running the Coreboot distribution known as Skulls.
https://github.com/merge/skulls/
The X230T is running the latest release of Skulls. Which is based on based on coreboot commit 555419f356 and SeaBIOS 1.12.1
GNU/Linux , FreeBSD, NetBSD and Windows 10 all have never had issues with the system clock on either laptop.