[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #15381: Haiku doesn't like system clock of Coreboot+Seabios systems.
From:       "Haiku" <trac () haiku-os ! org>
Date:       2019-09-27 19:38:45
Message-ID: 060.bc85025681906cb4eb4298e2a667b9c6 () haiku-os ! org
[Download RAW message or body]

--===============0884300307452022274==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#15381: Haiku doesn't like system clock of Coreboot+Seabios systems.
-------------------------+----------------------------
   Reporter:  trashHeap  |      Owner:  nobody
       Type:  bug        |     Status:  new
   Priority:  normal     |  Milestone:  Unscheduled
  Component:  - General  |    Version:  R1/Development
 Resolution:             |   Keywords:
 Blocked By:             |   Blocking:
Has a Patch:  0          |   Platform:  All
-------------------------+----------------------------
Description changed by trashHeap:

Old description:

> 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.
>
> 1. Booting the system cold into Haiku.
> 2. Connecting to WiFi and and initiating a network time synch at
> approximately 1:08 pm.
> 3. 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.

New description:

 Every build (nightly or otherwise) 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.

 1. Booting the system cold into Haiku.
 2. Connecting to WiFi and and initiating a network time synch at
 approximately 1:08 pm.
 3. 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.

--
-- =

Ticket URL: <https://dev.haiku-os.org/ticket/15381#comment:2>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
--===============0884300307452022274==--

[prev in list] [next in list] [prev in thread] [next in thread]