GNU bug report logs - #34978
Enable support for veyron chrombooks

Previous Next

Package: guix-patches;

Reported by: Vagrant Cascadian <vagrant <at> debian.org>

Date: Sun, 24 Mar 2019 18:04:02 UTC

Severity: normal

Tags: fixed

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Vagrant Cascadian <vagrant <at> debian.org>
To: 34978 <at> debbugs.gnu.org
Subject: [bug#34978] Enable support for veyron chrombooks
Date: Tue, 26 Mar 2019 15:50:24 -0700
On 2019-03-24, Vagrant Cascadian <vagrant <at> debian.org> wrote:
> On 2019-03-24, Vagrant Cascadian wrote:
>> Attached is a patch series that adds a linux-libre kernel variant for
>> "veyron" type chromebooks, tested on an Asus-C201
>> (a.k.a. veyron-speedy), and corresponding support for installing the
>> kernel so that the "depthcharge" bootloader can boot it, and an example
>> system config used on the veyron-speedy. It may also work on other
>> veyron models; they are untested.
>
> A bonus caveat:
>
> * currently u-boot-tools and tdb fail tests on armhf; but those should
>   probably be their own bugs...

"guix system reconfigure" works just fine when done from a checkout
(e.g. ./pre-inst-env guix system reconfigure ...), but unfortunately, if
I guix pull the very same commit:

  $ guix system reconfigure /home/vagrant/src/config/asus-c201-spdygx.scm
  guix system: error: failed to load '/home/vagrant/src/config/asus-c201-spdygx.scm':
  ice-9/boot-9.scm:2803:6: In procedure resolve-interface:
  no code for module (gnu bootloader depthcharge)

How could that happen?


live well,
  vagrant




This bug report was last modified 6 years and 128 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.