--- Begin Message ---
|
Subject: |
GuixSD resets hardware clock (on Lenovo x200 with libreboot) |
|
Date: |
Wed, 30 Dec 2015 09:24:49 -0600 |
Hello,
I recently installed GuixSD on the laptop I got fresh from Minifree. I
was happy to see how much worked, but I've noticed a bug that occurs in
GuixSD but not in Debian.
In Debian I can set the hardware clock (with `hwclock -w`) and if I
reboot back into Debian again, I still have the same hardware clock.
If I reboot into GuixSD, at some point in the boot process it resets my
hardware clock to 1970! If I reboot into Debian again after that, it's
1970 there also.
This is fairly serious, because this could greatly mess up committing to
git, running makefiles, or simply knowing when I wrote that file to
disk. Also, ssl certs no longer validate, etc.
Any idea what could be causing this? I noticed that if I rebooted it
at the time that it asked me for a passphrase to decrypt /home/ that it
didn't reset the clock, though maybe I should test that again.
My system config file is attached.
;; This is an operating system configuration template
;; for a "desktop" setup with X11.
(use-modules (gnu) (gnu system nss))
(use-service-modules desktop)
(use-package-modules xfce ratpoison certs)
(operating-system
(host-name "oolong")
(timezone "America/Chicago")
(locale "en_US.UTF-8")
;; Assuming /dev/sdX is the target hard disk, and "root" is
;; the label of the target root file system.
(bootloader (grub-configuration
(device "/dev/sda")))
(mapped-devices (list (mapped-device
(source "/dev/sda8")
(target "home-luks")
(type luks-device-mapping))))
(file-systems `(,(file-system
(device "guix")
(title 'label)
(mount-point "/")
(type "ext4"))
,(file-system
(device "/dev/mapper/home-luks")
(mount-point "/home")
(type "ext4"))
,@%base-file-systems))
(users (cons (user-account
(name "cwebber")
(uid 1000)
(comment "Christopher Allan Webber")
(group "cwebber")
(supplementary-groups '("users"
"wheel" "netdev"
"audio" "video"))
(home-directory "/home/cwebber"))
%base-user-accounts))
(groups (cons (user-group
(name "cwebber")
(id 1000))
%base-groups))
;; Add Xfce and Ratpoison; that allows us to choose
;; sessions using either of these at the log-in screen.
(packages (cons* xfce ratpoison ;desktop environments
nss-certs ;for HTTPS access
%base-packages))
;; Use the "desktop" services, which include the X11
;; log-in service, networking with Wicd, and more.
(services %desktop-services)
;; Allow resolution of '.local' host names with mDNS.
(name-service-switch %mdns-host-lookup-nss))
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot) |
|
Date: |
Fri, 05 Feb 2016 10:23:01 -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:
>>
>>> 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.
>>>
>>> Fine by me, assuming it works. I can test it works fine probably tomorrow.
>>
>> I just added a 'linux-libre-4.1' variable. Can you test to make sure it
>> works for you? I'd like to remove linux-libre-4.2.5 ASAP because 4.2.x
>> is no longer supported upstream and contains security flaws.
Chris reported on IRC that linux-libre-4.1 works for him, so I removed
linux-libre-4.2.5.
> Regardless, it seems that this bug can be closed on the Guix side; WDYT?
Agreed. I've closed the bug.
Thanks,
Mark
--- End Message ---