On Sun, Dec 24, 2017 at 11:59:11 -0600, Christopher Lemmer Webber wrote:
> It looks the same. Maybe the Libreboot version is responsible... I'm
> not sure.
I just received mine recently from Libiquity and I haven't had a chance
to play around with any of the flashing tools, so I don't know my
ver
Hey,
Sorry to bother you guys, but I'm having trouble leaving this email list...
I've tried logging into the web interface, and that failed.
I tried emailing guix-devel-le...@gnu.org, and that didn't seam to work.
Can someone help me leave this email list?
Thanks,
Joshua
__
Alex Vong writes:
> I get the following error when running ``guix --version | head -n 1''. I
> can get similar after replacing ``--version'' with ``--help''. Also, the
> error is nondeterministic. Any idea?
Attempts to write to a pipe that has already been closed on the other
end results in EPIP
Mark H Weaver writes:
> Danny Milosavljevic writes:
>
>> (Does anyone mind
>>> pasting their equivalent lspci output who's saying "it works for me" on
>>> an x200? I wonder if we can find the soruce of the difference.)
>>
>> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Runing `guix pull` generates the following error message:
Updating from Git repository at
'https://git.savannah.gnu.org/git/guix.git'...
Building from Git commit b982fb1c09573f4638324d7809ec18d0c9956d11...
The following derivation will be built:
/gnu/store/d8gx000cbyihr3x3gggnm9d61adjb0s3-gu
Andreas Enge writes:
> On Sun, Dec 24, 2017 at 04:23:44AM +0800, Alex Vong wrote:
>> ERROR: In procedure display:
>> ERROR: In procedure scm_flush: Broken pipe
>
> Interesting! I get a different error message:
>
> ERROR: In procedure display:
> In procedure fport_write: Broken pipe
>
> Andreas
H
