On Sun, Jan 17, 2016 at 09:39:24PM +0100, Ludovic Courtès wrote:
> Jookia <166...@gmail.com> skribis:
> I think getting a working bootloader and kernel are the main blockers
> (the current ‘linux-libre’ package might work already, or it might need
> more tweaks; I don’t think anyone has tried to bo
Ricardo Wurmus skribis:
> Ludovic Courtès writes:
>
>> Ricardo Wurmus skribis:
>>
>>> So, using HIDBP is probably wrong and might very well be the cause.
>>> Looking at the module names again I searched the logs for “usbkbd” and,
>>> yes, the GuixSD logs contain this line:
>>>
>>> usbcore:
Jookia <166...@gmail.com> skribis:
> I'm considering seeing if I can get GuixSD to work on an ARM board of mine.
> I'd
> like to know what the main blockers are that I'll need to pass. From what I've
> read and understood, the reason there's no ARM port now is lack of work and
> reliance on GRUB.
Ludovic Courtès writes:
> Christopher Allan Webber skribis:
>
>> My config is attached. Hackily, I copy-pasta'ed the kernel packages
>> entirely from guix v0.9.0's release. I can confirm that this can read
>> the hardware clock just fine, whereas the other version of the kernel
>> can't... so i
==
GNU Guix 0.9.1: ./test-suite.log
==
# TOTAL: 56
# PASS: 53
# SKIP: 2
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
SKIP: tests/containers
==
SKIP tests/containers.scm (exit
On Sat, 16 Jan 2016 21:27:26 +1100
Jookia <166...@gmail.com> wrote:
> Hey there,
>
> I'm considering seeing if I can get GuixSD to work on an ARM board of mine.
> I'd
> like to know what the main blockers are that I'll need to pass. From what I've
> read and understood, the reason there's no ARM
