bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot)


From: Mark H Weaver
Subject: bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot)
Date: Tue, 19 Jan 2016 12:11:51 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

address@hidden (Ludovic Courtès) writes:

> Mark H Weaver <address@hidden> skribis:
>
>> Christopher Allan Webber <address@hidden> writes:
>>
>>> From e60db83ffff23c57ec5c44de7c99cee8e4e353ff Mon Sep 17 00:00:00 2001
>>> From: Christopher Allan Webber <address@hidden>
>>> Date: Sun, 17 Jan 2016 20:34:25 -0800
>>> Subject: [PATCH] gnu: Add linux-libre-4.2.5
>>>
>>> This older version of linux-libre is being added because it was found
>>> that newer versions (or at least 4.3.3) of linux-libre were not reading
>>> the hardware clock on (at least Libreboot-enabled) Thinkpad x200
>>> machines.
>>>
>>> * gnu/linux.scm (linux-libre-4.2.5): New variable.
>>
>> I would say that the variable should be named 'linux-libre-4.2', which
>> would always be bound to the latest 4.2.x.  However, there's another
>> problem: the 4.2 branch is no longer supported upstream, so it will no
>> longer receive security updates and other important fixes.
>>
>> I suggest that we instead add linux-libre-4.1, which is still supported
>> upstream and is designated as an LTS branch.  Would that be okay?
>
> If it works for Christopher, that’s a good idea.
>
>> Another issue is that the kernel config for 4.3 is being used here.  I
>> guess maybe that's working well enough in this case, but really our
>> kernel packages should be refactored somewhat to make this nicer.
>
> Yeah, though that’s probably beyond the scope of this particular issue.

Agreed.

>> One more thing: Francis Rowe told me that the coreboot developers have
>> determined that this is a bug on their side, and libreboot will
>> cherry-pick the fix soon, if it hasn't already.

"determined" may have been too strong a word.  Maybe better to say that
they "think" it's a coreboot bug, exposed by a change in the kernel.

> Interesting.  Any links to the bug report or commit?

https://review.coreboot.org/#/c/11853/

     Mark





reply via email to

[Prev in Thread] Current Thread [Next in Thread]