Hi Chris,
Thanks for testing!
> - The fonts were different than I remember. Not sure why it happened,
> but I'm guessing it had to do with the fact that I emptied my default
> profile, and thus got rid of a lot of fonts accidentally. At this
> time, I doubt it's because of your changes.
On Wed, 13 Nov 2019 08:53:29 +0200
Efraim Flashner wrote:
> On my machine with EFI I mounted my vfat partition at /boot/efi
> instead of /boot. Does your /boot partition contain an efi directory?
>
I created one with mkdir, but it's empty.
But I'm going to try with mounting at /boot/efi instead
Tried this, but didn't work, also tried mounting the partition at
"/boot/efi" and installing bootloader at "/boot". I'm installing Guix
form a not-UEFI machine, could this cause the problem?
Jan Wielkiewicz
Hi all! Last reconfigure passed without errors, but no messages about grub
installation. After reboot - grub rescue prompt. For example, some command
output in rescue console:
insmod search
# ok, silent
insmod linux
error: symbol 'some_symbol' not found
cd /mnt/boot/; ls -R
.:
grub
./grub:
fonts
On Wed, Nov 13, 2019 at 08:15:51PM +0100, Jan wrote:
> Tried this, but didn't work, also tried mounting the partition at
> "/boot/efi" and installing bootloader at "/boot". I'm installing Guix
> form a not-UEFI machine, could this cause the problem?
>
I don't remember now if for the initializatio
I am using a Pinebook Pro (aarch64) to build a disk image. However the build
process stops very quickly when it gets to the ...-disk-image.drv...
The guix --version is guix (GNU Guix) d673993...1ce0f20
The command that I am issuing is:
guix system disk-image -e "(@ (gnu system install) rockpr
I had a similar issue building a disk-image. It was on an x86 machine, and the
build would error out right at that point. The fix was to put add my user to
the 'kvm' group.
>From looking at top during the build, it seems that the disk-image derivation
is doing something with qemu. Is there even AR
Thanks for the tip. Unfortunately the gnu/build/vm.scm file explicitly states
that it is buggy on ARM32 boards and should not be used, even if available. I
would assume that would be the case for aarch64 as well.
> On Nov 13, 2019, at 5:19 PM, x...@wilsonb.com wrote:
>
> I had a similar issue
