bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
Calvin Heim writes: >> Ubuntu 16.04 uses linux-4.4. We have linux-libre-4.4 (LTS) in Guix, but >> our 1.0.1 installer images are based on linux-libre-5.1. >> >> It might be worth using another machine to build a Guix installer image >> that uses linux-libre-4.4, and trying that. > Is it important that it's another machine, and not this machine (Macbook1,1)? > This machine has Trisquel 8 currently running and functional. > I am confident that I can reinstall the Guix package manager on it > to build the suggested custom installation image. Sure, that should be fine. Note that you'll also need to ensure that the final system you install uses linux-libre-4.4, by adding (kernel linux-libre-4.4) to your OS configuration. I'm not sure off-hand how to do this when using the guided graphical installer, but maybe someone else here knows. I've only ever done manual installations. Mark
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
On Thu, 2019-08-15 at 19:37 -0400, Mark H Weaver wrote: > Hi Calvin, > > Calvin Heim writes: > > > > > On Thu, 2019-08-15 at 15:15 -0400, Mark H Weaver wrote: > > > > > > I did some looking around for any recently updated tutorials on how to > > > install GNU/Linux on a MacBook 1,1, and the only recent success story I > > > found involved installing the rEFInd boot manager and using it to boot > > > to a USB installer. > > > > > > https://www.youtube.com/watch?v=nHRai14ETKU > > > > > > I would suggest something along those lines, since it would eliminate > > > the need to access the DVD drive from the initrd, which seems to be > > > where you're currently getting stuck. > > > > > > Mark > > I have now removed the DVD and made a live USB with the > > guix-system-install-1.0.1.i686-linux.iso image. > > Selecting the live usb at (what I believe to be) the EFI leads to the > > GuixSD LiveUSB image's GRUB, replete with the GUIXSD logo. > > Setting the acpi=off boot option in the GuixSD LiveUSB image's GRUB leads > > to the same log that is > > pasted in my previous email, quoted above. When I saw the identifier for > > the DVD drive again in the log, > > I double-checked to make sure that my previous DVD was not in the drive. > > Nope, it's in a vinyl CD case. > > > > David Stumph (the author of the video) is using lubuntu 16.04 in the video. > > He attempted 18.10 > > but that resulted in a kernel panic. I also see a kernel panic without > > setting acpi=off > > in the grub boot options. In case someone in the future is searching for > > this issue, the kernel panic message is > > > > > > %--begin pasted text->% > > Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast > > exception handler > > Shutting down cpus with NMI > > Kernel Offset : 0x800 from 0xc100 (relocation range: > > 0xc000-0xf7dfdfff) > > Kernel rebooting in 30 seconds > > > > > > %--end paste->% > Ubuntu 16.04 uses linux-4.4. We have linux-libre-4.4 (LTS) in Guix, but > our 1.0.1 installer images are based on linux-libre-5.1. > > It might be worth using another machine to build a Guix installer image > that uses linux-libre-4.4, and trying that. Is it important that it's another machine, and not this machine (Macbook1,1)? This machine has Trisquel 8 currently running and functional. I am confident that I can reinstall the Guix package manager on it to build the suggested custom installation image. > Here's how: Section 3.9 > (Building the Installation Image) describes how to build an installer > image, but instead of passing "gnu/system/install.scm", pass the name of > a modified version of that file, with (kernel linux-libre-4.4) added as > an additional field to 'installation-os'. > > Mark
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
Mark H Weaver writes: > Hi Calvin, > > Calvin Heim writes: > >> On Thu, 2019-08-15 at 15:15 -0400, Mark H Weaver wrote: >>> I did some looking around for any recently updated tutorials on how to >>> install GNU/Linux on a MacBook 1,1, and the only recent success story I >>> found involved installing the rEFInd boot manager and using it to boot >>> to a USB installer. >>> >>> https://www.youtube.com/watch?v=nHRai14ETKU >>> >>> I would suggest something along those lines, since it would eliminate >>> the need to access the DVD drive from the initrd, which seems to be >>> where you're currently getting stuck. >>> >>> Mark >> I have now removed the DVD and made a live USB with the >> guix-system-install-1.0.1.i686-linux.iso image. >> Selecting the live usb at (what I believe to be) the EFI leads to the GuixSD >> LiveUSB image's GRUB, replete with the GUIXSD logo. >> Setting the acpi=off boot option in the GuixSD LiveUSB image's GRUB leads to >> the same log that is >> pasted in my previous email, quoted above. When I saw the identifier for >> the DVD drive again in the log, >> I double-checked to make sure that my previous DVD was not in the drive. >> Nope, it's in a vinyl CD case. >> >> David Stumph (the author of the video) is using lubuntu 16.04 in the video. >> He attempted 18.10 >> but that resulted in a kernel panic. I also see a kernel panic without >> setting acpi=off >> in the grub boot options. In case someone in the future is searching for >> this issue, the kernel panic message is >>>%--begin pasted text->% >> Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast >> exception handler >> Shutting down cpus with NMI >> Kernel Offset : 0x800 from 0xc100 (relocation range: >> 0xc000-0xf7dfdfff) >> Kernel rebooting in 30 seconds >>>%--end paste->% > > Ubuntu 16.04 uses linux-4.4. We have linux-libre-4.4 (LTS) in Guix, but > our 1.0.1 installer images are based on linux-libre-5.1. > > It might be worth using another machine to build a Guix installer image > that uses linux-libre-4.4, and trying that. Here's how: Section 3.9 > (Building the Installation Image) describes how to build an installer > image, but instead of passing "gnu/system/install.scm", pass the name of > a modified version of that file, with (kernel linux-libre-4.4) added as > an additional field to 'installation-os'. I should mention that you'll also need to add "--system=i686-linux" as an option to "guix system disk-image", if the build system is 64-bit. Mark
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
Hi Calvin, Calvin Heim writes: > On Thu, 2019-08-15 at 15:15 -0400, Mark H Weaver wrote: >> I did some looking around for any recently updated tutorials on how to >> install GNU/Linux on a MacBook 1,1, and the only recent success story I >> found involved installing the rEFInd boot manager and using it to boot >> to a USB installer. >> >> https://www.youtube.com/watch?v=nHRai14ETKU >> >> I would suggest something along those lines, since it would eliminate >> the need to access the DVD drive from the initrd, which seems to be >> where you're currently getting stuck. >> >> Mark > I have now removed the DVD and made a live USB with the > guix-system-install-1.0.1.i686-linux.iso image. > Selecting the live usb at (what I believe to be) the EFI leads to the GuixSD > LiveUSB image's GRUB, replete with the GUIXSD logo. > Setting the acpi=off boot option in the GuixSD LiveUSB image's GRUB leads to > the same log that is > pasted in my previous email, quoted above. When I saw the identifier for the > DVD drive again in the log, > I double-checked to make sure that my previous DVD was not in the drive. > Nope, it's in a vinyl CD case. > > David Stumph (the author of the video) is using lubuntu 16.04 in the video. > He attempted 18.10 > but that resulted in a kernel panic. I also see a kernel panic without > setting acpi=off > in the grub boot options. In case someone in the future is searching for this > issue, the kernel panic message is >>%--begin pasted text->% > Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception > handler > Shutting down cpus with NMI > Kernel Offset : 0x800 from 0xc100 (relocation range: > 0xc000-0xf7dfdfff) > Kernel rebooting in 30 seconds >>%--end paste->% Ubuntu 16.04 uses linux-4.4. We have linux-libre-4.4 (LTS) in Guix, but our 1.0.1 installer images are based on linux-libre-5.1. It might be worth using another machine to build a Guix installer image that uses linux-libre-4.4, and trying that. Here's how: Section 3.9 (Building the Installation Image) describes how to build an installer image, but instead of passing "gnu/system/install.scm", pass the name of a modified version of that file, with (kernel linux-libre-4.4) added as an additional field to 'installation-os'. Mark
bug#36747: Official MesCC bootstrap binaries differ from my locally built ones
Marius Bakke writes: > Mark H Weaver writes: > >> I rebased 'wip-binaries' on top of current master (which includes the >> recent 'staging' merge), and excluding the update of mescc-tools to the >> git checkout. >> >> I built the bootstrap-tarballs for i686-linux and got the same hashes >> that we've previously agreed on here. I used "guix download" to load >> the new bootstrap binaries into my store, and am now testing the >> attached draft patch to 'core-updates'. > > Excellent, thank you! The patches LGTM. > > I wonder if we should run these through a 'core-updates-next' branch to > give ourselves a little time to bootstrap the different architectures. > > (also, it would be neat to get SQLite 3.29.0 in..) > > Thoughts? I don't have a strong opinion, so do what you think is best. I think we should continue to treat 'core-updates' as frozen. These slight changes to the bootstrap binaries to make them build deterministically should almost certainly make no difference to anything else in 'core-updates', so the only time we'll lose is the time needed for Berlin to rebuild. If we make any additional changes to 'core-updates', such as updating SQLite or adding more architectures, it will likely cause additional problems that need to be debugged. This 'core-updates' cycle has already taken too long, IMO. Any other opinions? Thanks, Mark
bug#37021: root option during grub boot configuration
When I press e at GRUB to edit the boot configuration I have noticed that the identifier 31393730-3031-3031-3139-343934363833 is the default value of the --root option on the LiveUSB. I will look into other possible values for this --root option.
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
resubmitted to list On Thu, 2019-08-15 at 12:12 +0300, Efraim Flashner wrote: > > > Does this laptop still have the original BIOS/EFI implementation or has > it perchance been replaced with libreboot? > This particular Macbook type (part no. MA472LL/A) is untested with libreboot. https://libreboot.org/docs/hardware/#information-about-the-macbook11
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
resubmitted to list On Thu, 2019-08-15 at 12:43 +0200, pelzflorian (Florian Pelz) wrote: > > Do I understand correctly that this message appears when booting the > DVD, not the installed system? Yes. > > > On Wed, Aug 14, 2019 at 03:32:06PM -0700, Calvin Heim wrote: > > > > > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > I cannot check right now if that is a legitimate partition id for the > i686 installer, but the installer source code in > gnu/system/install.scm should mount a partition with > (file-system-label "Guix_image"). You could check from another OS if > this partition label exists. >From Trisquel 8, $ ls /dev/disk/by-label GUIX_IMAGE $ls /dev/disk/by-uuid 1970-01-01-19-49-46-83 [other stuff that doesn't change when the DVD ejects] The contents of by-id and by-partuuid don't change when the install DVD is inserted, so I assume that the contents of those directories are not related to the DVD. > > You could also type in the recovery > Guile repl that opens: > > (use-modules (ice-9 ftw)) > (scandir "/dev/disk/by-id") > (scandir "/dev/disk/by-uuid") > (scandir "/dev/disk/by-partuuid") > > and maybe: > > ,L bournish > cat /run/booted-system/etc/fstab > The keyboard/usb ports do not function at this point in the boot, despite working earlier in the boot during EFI and GRUB. I can see but not type in the recovery Guile repl. > > Regards, > Florian
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
resent to list On Thu, 2019-08-15 at 12:12 +0300, Efraim Flashner wrote: > > Looks like it is the macbook 1,1. IIRC it has a pre-standardized EFI > implementation in 32-bit, don't remember if the laptop itself is 32- or > 64- bit. 32 bit. > > Personally I would try it with Debian's special mac-installer > image first to see if that happens to boot up. > > Does this laptop still have the original BIOS/EFI implementation or has > it perchance been replaced with libreboot? > Original EFI implementation.
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
On Thu, 2019-08-15 at 15:15 -0400, Mark H Weaver wrote: > Calvin Heim writes: > > > > > Apologies for the formatting errors in the previous email. Hopefully this > > message is cleaner. > > > > GRUB loads. edit: this grub shows the GuixSD logo in the background. > > > > I add acpi=off to the boot options and boot. Otherwise, the screen goes > > black > > with a '-' symbol at the top left corner and freezes. > > > > So, after booting with acpi=off, the display shows the following lines > > (with timestamps on the > > left, but I had to manually transcribe so I left them off): > > > > %<---begin pasted text--- > > ehci-pci :00:1d.7: Found HC with no IRQ. Check BIOS/PCI :00:1d.7 > > setup! > > ehci-pci :00:1d.7: init :00:1d.7 fail, -19 > > ehci-pci :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 > > setup! > > ehci-pci :00:1d.0: init :00:1d.0 fail, -19 > > ehci-pci :00:1d.1: Found HC with no IRQ. Check BIOS/PCI :00:1d.1 > > setup! > > ehci-pci :00:1d.1: init :00:1d.1 fail, -19 > > ehci-pci :00:1d.2: Found HC with no IRQ. Check BIOS/PCI :00:1d.2 > > setup! > > ehci-pci :00:1d.2: init :00:1d.2 fail, -19 > > ehci-pci :00:1d.3: Found HC with no IRQ. Check BIOS/PCI :00:1d.3 > > setup! > > ehci-pci :00:1d.3: init :00:1d.7 fail, -19 > > GC Warning: pthread_getattr_np or pthread_attr_getstack failed for main > > thread > > GC Warning: couldn't read /proc/stat > > Welcome, this is GNU's early boot Guile. > > Use '--repl' for an initrd REPL. > > > > loading kernel modules... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > > ERROR: In procedure scm-error: > > failed to resolve partition "31393730-3031-3031-3139-343934363833" > > %<-end paste- > > > > And then it enters the Guile 2.2.4 prompt, but the keyboard and USB ports > > are disabled at this stage, so I can't use it. > It appears that our initrd lacks the drivers needed to access the DVD > drive. > > I did some looking around for any recently updated tutorials on how to > install GNU/Linux on a MacBook 1,1, and the only recent success story I > found involved installing the rEFInd boot manager and using it to boot > to a USB installer. > > https://www.youtube.com/watch?v=nHRai14ETKU > > I would suggest something along those lines, since it would eliminate > the need to access the DVD drive from the initrd, which seems to be > where you're currently getting stuck. > > Mark I have now removed the DVD and made a live USB with the guix-system-install-1.0.1.i686-linux.iso image. Selecting the live usb at (what I believe to be) the EFI leads to the GuixSD LiveUSB image's GRUB, replete with the GUIXSD logo. Setting the acpi=off boot option in the GuixSD LiveUSB image's GRUB leads to the same log that is pasted in my previous email, quoted above. When I saw the identifier for the DVD drive again in the log, I double-checked to make sure that my previous DVD was not in the drive. Nope, it's in a vinyl CD case. David Stumph (the author of the video) is using lubuntu 16.04 in the video. He attempted 18.10 but that resulted in a kernel panic. I also see a kernel panic without setting acpi=off in the grub boot options. In case someone in the future is searching for
bug#36747: Official MesCC bootstrap binaries differ from my locally built ones
Mark H Weaver writes: > I rebased 'wip-binaries' on top of current master (which includes the > recent 'staging' merge), and excluding the update of mescc-tools to the > git checkout. > > I built the bootstrap-tarballs for i686-linux and got the same hashes > that we've previously agreed on here. I used "guix download" to load > the new bootstrap binaries into my store, and am now testing the > attached draft patch to 'core-updates'. Excellent, thank you! The patches LGTM. I wonder if we should run these through a 'core-updates-next' branch to give ourselves a little time to bootstrap the different architectures. (also, it would be neat to get SQLite 3.29.0 in..) Thoughts? I don't have a strong opinion, so do what you think is best. signature.asc Description: PGP signature
bug#36747: Official MesCC bootstrap binaries differ from my locally built ones
Hi,
Marius Bakke writes:
> I can look into adjusting the bash fix for 5.0, and updating the
> bootstrap binary URLs and hashes.
I've attached preliminary untested patches for these. I'm testing them
now.
Mark
>From e3e477c92af3b62eb8f65a5c4459f02faf60e857 Mon Sep 17 00:00:00 2001
From: Mark H Weaver
Date: Thu, 15 Aug 2019 15:39:57 -0400
Subject: [PATCH 1/2] gnu: bootstrap: Update to the 20190815 bootstrap
binaries.
* gnu/packages/bootstrap.scm (%bootstrap-linux-libre-headers): Update the
download URL.
(%bootstrap-mescc-tools, %bootstrap-mes): Update the download URL and hash.
---
gnu/packages/bootstrap.scm | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/gnu/packages/bootstrap.scm b/gnu/packages/bootstrap.scm
index 8dbe52435e..1982c9706f 100644
--- a/gnu/packages/bootstrap.scm
+++ b/gnu/packages/bootstrap.scm
@@ -1,6 +1,6 @@
;;; GNU Guix --- Functional package management for GNU
;;; Copyright © 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Ludovic Courtès
-;;; Copyright © 2014, 2015, 2018 Mark H Weaver
+;;; Copyright © 2014, 2015, 2018, 2019 Mark H Weaver
;;; Copyright © 2017 Efraim Flashner
;;; Copyright © 2018 Jan (janneke) Nieuwenhuizen
;;;
@@ -490,7 +490,7 @@ $out/bin/guile --version~%"
(origin
(method url-fetch)
(uri (map (cute string-append <>
- "/i686-linux/20181020/"
+ "/i686-linux/20190815/"
"linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz")
%bootstrap-base-urls))
(sha256
@@ -735,12 +735,12 @@ exec ~a/bin/.gcc-wrapped -B~a/lib \
(method url-fetch)
(uri (map
(cute string-append <>
-"/i686-linux/20181020/"
-"mescc-tools-static-0.5.2-0.bb062b0-i686-linux.tar.xz")
+"/i686-linux/20190815/"
+"mescc-tools-static-stripped-0.5.2-i686-linux.tar.xz")
%bootstrap-base-urls))
(sha256
(base32
- "11lniw0vg61kmyhvnwkmcnkci9ym6hbmiksiqggd0hkipbq7hvlz")))
+ "0c3kklgghzh4q2dbpl6asb74cimp7hp6jscdwqwmzxbapgcl6582")))
(synopsis "Bootstrap binaries of MesCC Tools")
(description synopsis)
(home-page #f)
@@ -784,12 +784,12 @@ exec ~a/bin/.gcc-wrapped -B~a/lib \
(method url-fetch)
(uri (map
(cute string-append <>
-"/i686-linux/20181020/"
+"/i686-linux/20190815/"
"mes-minimal-stripped-0.19-i686-linux.tar.xz")
%bootstrap-base-urls))
(sha256
(base32
- "0k7kkl68a6xaadv47ij0nr9jm5ca1ffj38n7f2lg80y72wdkwr9h")))
+ "1q4xjpx6nbn44kxnilpgl12bhpmwy2bblzwszc2ci7xkf400jcpv")))
(supported-systems '("i686-linux" "x86_64-linux"))
(synopsis "Bootstrap binaries of Mes")
(description synopsis)
--
2.22.1
>From 1e609d70cd29af6eed7ceb81b840ac0a4f29fe42 Mon Sep 17 00:00:00 2001
From: Mark H Weaver
Date: Thu, 15 Aug 2019 16:45:03 -0400
Subject: [PATCH 2/2] UNTESTED: bash: Unconditionally configure PGRP_PIPE for
*-linux systems.
* gnu/packages/patches/bash-linux-pgrp-pipe.patch: New file.
* gnu/local.mk (dist_patch_DATA): Add it.
* gnu/packages/bash.scm (bash)[source]: Add the patch.
---
gnu/local.mk | 1 +
gnu/packages/bash.scm | 3 +-
.../patches/bash-linux-pgrp-pipe.patch| 32 +++
3 files changed, 35 insertions(+), 1 deletion(-)
create mode 100644 gnu/packages/patches/bash-linux-pgrp-pipe.patch
diff --git a/gnu/local.mk b/gnu/local.mk
index 08bc205623..2e6d4776b9 100644
--- a/gnu/local.mk
+++ b/gnu/local.mk
@@ -697,6 +697,7 @@ dist_patch_DATA = \
%D%/packages/patches/awesome-reproducible-png.patch \
%D%/packages/patches/azr3.patch\
%D%/packages/patches/bash-completion-directories.patch \
+ %D%/packages/patches/bash-linux-pgrp-pipe.patch \
%D%/packages/patches/bastet-change-source-of-unordered_set.patch \
%D%/packages/patches/bazaar-CVE-2017-14176.patch \
%D%/packages/patches/beets-python-3.7-fix.patch \
diff --git a/gnu/packages/bash.scm b/gnu/packages/bash.scm
index d3abeec6e6..f1ef7047bf 100644
--- a/gnu/packages/bash.scm
+++ b/gnu/packages/bash.scm
@@ -115,7 +115,8 @@ number/base32-hash tuples, directly usable in the 'patch-series' form."
(base32
"0kgvfwqdcd90waczf4gx39xnrxzijhjrzyzv7s8v4w31qqm0za5l"))
(patch-flags '("-p0"))
- (patches %patch-series-5.0)))
+ (patches (cons (search-patch &qu
bug#36747: Official MesCC bootstrap binaries differ from my locally built ones
I rebased 'wip-binaries' on top of current master (which includes the
recent 'staging' merge), and excluding the update of mescc-tools to the
git checkout.
I built the bootstrap-tarballs for i686-linux and got the same hashes
that we've previously agreed on here. I used "guix download" to load
the new bootstrap binaries into my store, and am now testing the
attached draft patch to 'core-updates'.
Thanks,
Mark
>From e3e477c92af3b62eb8f65a5c4459f02faf60e857 Mon Sep 17 00:00:00 2001
From: Mark H Weaver
Date: Thu, 15 Aug 2019 15:39:57 -0400
Subject: [PATCH] gnu: bootstrap: Update to the 20190815 bootstrap binaries.
* gnu/packages/bootstrap.scm (%bootstrap-linux-libre-headers): Update the
download URL.
(%bootstrap-mescc-tools, %bootstrap-mes): Update the download URL and hash.
---
gnu/packages/bootstrap.scm | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/gnu/packages/bootstrap.scm b/gnu/packages/bootstrap.scm
index 8dbe52435e..1982c9706f 100644
--- a/gnu/packages/bootstrap.scm
+++ b/gnu/packages/bootstrap.scm
@@ -1,6 +1,6 @@
;;; GNU Guix --- Functional package management for GNU
;;; Copyright © 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 Ludovic Courtès
-;;; Copyright © 2014, 2015, 2018 Mark H Weaver
+;;; Copyright © 2014, 2015, 2018, 2019 Mark H Weaver
;;; Copyright © 2017 Efraim Flashner
;;; Copyright © 2018 Jan (janneke) Nieuwenhuizen
;;;
@@ -490,7 +490,7 @@ $out/bin/guile --version~%"
(origin
(method url-fetch)
(uri (map (cute string-append <>
- "/i686-linux/20181020/"
+ "/i686-linux/20190815/"
"linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz")
%bootstrap-base-urls))
(sha256
@@ -735,12 +735,12 @@ exec ~a/bin/.gcc-wrapped -B~a/lib \
(method url-fetch)
(uri (map
(cute string-append <>
-"/i686-linux/20181020/"
-"mescc-tools-static-0.5.2-0.bb062b0-i686-linux.tar.xz")
+"/i686-linux/20190815/"
+"mescc-tools-static-stripped-0.5.2-i686-linux.tar.xz")
%bootstrap-base-urls))
(sha256
(base32
- "11lniw0vg61kmyhvnwkmcnkci9ym6hbmiksiqggd0hkipbq7hvlz")))
+ "0c3kklgghzh4q2dbpl6asb74cimp7hp6jscdwqwmzxbapgcl6582")))
(synopsis "Bootstrap binaries of MesCC Tools")
(description synopsis)
(home-page #f)
@@ -784,12 +784,12 @@ exec ~a/bin/.gcc-wrapped -B~a/lib \
(method url-fetch)
(uri (map
(cute string-append <>
-"/i686-linux/20181020/"
+"/i686-linux/20190815/"
"mes-minimal-stripped-0.19-i686-linux.tar.xz")
%bootstrap-base-urls))
(sha256
(base32
- "0k7kkl68a6xaadv47ij0nr9jm5ca1ffj38n7f2lg80y72wdkwr9h")))
+ "1q4xjpx6nbn44kxnilpgl12bhpmwy2bblzwszc2ci7xkf400jcpv")))
(supported-systems '("i686-linux" "x86_64-linux"))
(synopsis "Bootstrap binaries of Mes")
(description synopsis)
--
2.22.1
bug#37035: --with-graft tries to download source files and build them
Hi, writes: > When running `guix build --dry-run --with-graft=mesa=mesa love`, Guix shows > that it will try to download a bunch of source files for quite a few packages: > > ``` > $ guix build --dry-run --with-graft=mesa=mesa love > The following derivations would be built: >/gnu/store/0lfws1b85h6lkv09pp7q0439pd41qirj-love-11.1.drv >/gnu/store/2spqmdn4s13r0z9d9hym25h4nfcl1r5g-sdl2-2.0.9.drv >/gnu/store/aknpb0pgslx9jaidgvh8wrzl7j6nl3nn-fcitx-4.2.9.6.drv >/gnu/store/8pk7gncsr1cfph8km8dhwk67q9d58c0k-libepoxy-1.5.3.drv >/gnu/store/w0wxk5f2a44hksrbvwqxn1d6sx96hdyw-gtk+-3.24.9.drv >/gnu/store/ydx7mg4bni0lfckw0r3x65icmfhr194k-xorg-server-1.20.5.drv >/gnu/store/xnc6a1fjwlwfjpg0lwai3aq51rw5qwrc-extra-cmake-modules-5.55.0.drv >/gnu/store/jp29lhdwhs3znbsbznxq9nd9zp5l8ds0-qtbase-5.11.3.drv >/gnu/store/sblg1v3yxf41b89aaj4r47zcyhxs3az4-ibus-1.5.20.drv >/gnu/store/a4ynsy7ras28jlgmrhfilkc0lnin21mw-libnotify-0.7.7.drv >/gnu/store/d8gvjnrl584wc5pavppa3m3yvm3jaxpk-dconf-0.32.0.drv > 76.4 MB would be downloaded: >/gnu/store/4vl3vkvqv0hhr0rlzciq55l4j8c5lgdz-ibus-1.5.20.tar.gz >/gnu/store/jpxqw86l1gxkfrp66h5mc747xf881hjm-gettext-0.19.8.1 >/gnu/store/9dgbqa3m412prwadpwg0ah7a3kv6fh9p-libnotify-0.7.7.tar.xz >/gnu/store/aaha1wfv58b83fwp0fqg8b5nlpkw1bva-libmng-2.0.3 >/gnu/store/6qy0ni5msmg93a55wi5qmj96729c1fcf-vulkan-headers-1.1.112 > > /gnu/store/3a3j7rnd49fr6papzd2r2i8f96ayxi1v-qtbase-everywhere-src-5.11.3.tar.xz >/gnu/store/3n7yhbfl1gik3n64rmy1574djpc1w6m5-gperf-3.1 >/gnu/store/wkfsm7mv8rjawdkzi8chf7qy8l5dppkm-xorg-server-1.20.5.tar.xz >/gnu/store/7w7fq1iy0jkap5np4q00cw4cllr0lkj5-libdmx-1.1.4 >/gnu/store/cc39n3mx1nswgwx7p8mbx7apy4j1w8yy-xtrans-1.3.5 >/gnu/store/l1nxv1asf958h9ww4iijypyk31mj3d3x-gtk+-3.24.9.tar.xz >/gnu/store/9rzjddyd621n26av5hb6zn55r372fhnv-libepoxy-1.5.3.tar.xz > ``` You asked Guix to build something, so it's not surprising to me that it might need to download some source code to do that. Can you spell out more clearly what you expected to happen differently, and why you think Guix is acting improperly here? Thanks, Mark
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
Calvin Heim writes: > Apologies for the formatting errors in the previous email. Hopefully this > message is cleaner. > > GRUB loads. > I add acpi=off to the boot options and boot. Otherwise, the screen goes black > with a '-' symbol at the top left corner and freezes. > > So, after booting with acpi=off, the display shows the following lines (with > timestamps on the > left, but I had to manually transcribe so I left them off): > > %<---begin pasted text--- > ehci-pci :00:1d.7: Found HC with no IRQ. Check BIOS/PCI :00:1d.7 > setup! > ehci-pci :00:1d.7: init :00:1d.7 fail, -19 > ehci-pci :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 > setup! > ehci-pci :00:1d.0: init :00:1d.0 fail, -19 > ehci-pci :00:1d.1: Found HC with no IRQ. Check BIOS/PCI :00:1d.1 > setup! > ehci-pci :00:1d.1: init :00:1d.1 fail, -19 > ehci-pci :00:1d.2: Found HC with no IRQ. Check BIOS/PCI :00:1d.2 > setup! > ehci-pci :00:1d.2: init :00:1d.2 fail, -19 > ehci-pci :00:1d.3: Found HC with no IRQ. Check BIOS/PCI :00:1d.3 > setup! > ehci-pci :00:1d.3: init :00:1d.7 fail, -19 > GC Warning: pthread_getattr_np or pthread_attr_getstack failed for main > thread > GC Warning: couldn't read /proc/stat > Welcome, this is GNU's early boot Guile. > Use '--repl' for an initrd REPL. > > loading kernel modules... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... > ERROR: In procedure scm-error: > failed to resolve partition "31393730-3031-3031-3139-343934363833" > %<-end paste- > > And then it enters the Guile 2.2.4 prompt, but the keyboard and USB ports > are disabled at this stage, so I can't use it. It appears that our initrd lacks the drivers needed to access the DVD drive. I did some looking around for any recently updated tutorials on how to install GNU/Linux on a MacBook 1,1, and the only recent success story I found involved installing the rEFInd boot manager and using it to boot to a USB installer. https://www.youtube.com/watch?v=nHRai14ETKU I would suggest something along those lines, since it would eliminate the need to access the DVD drive from the initrd, which seems to be where you're currently getting stuck. Mark
bug#37014: Gajim blows me with Pop-Up Errors
Raghav Gururajan writes: >> This sounds like some Gajim state is corrupt. Could you try again >> after >> moving ~/.cache/gajim/cache.db out of the way? > > Thanks for the suggestion. > > I made gajim to work normal but I had to remove ./local/gajim/logs.db. Okay, thanks for letting us know. I’m marking this bug as solved. -- Ricardo
bug#37035: --with-graft tries to download source files and build them
When running `guix build --dry-run --with-graft=mesa=mesa love`, Guix shows that it will try to download a bunch of source files for quite a few packages: ``` $ guix build --dry-run --with-graft=mesa=mesa love The following derivations would be built: /gnu/store/0lfws1b85h6lkv09pp7q0439pd41qirj-love-11.1.drv /gnu/store/2spqmdn4s13r0z9d9hym25h4nfcl1r5g-sdl2-2.0.9.drv /gnu/store/aknpb0pgslx9jaidgvh8wrzl7j6nl3nn-fcitx-4.2.9.6.drv /gnu/store/8pk7gncsr1cfph8km8dhwk67q9d58c0k-libepoxy-1.5.3.drv /gnu/store/w0wxk5f2a44hksrbvwqxn1d6sx96hdyw-gtk+-3.24.9.drv /gnu/store/ydx7mg4bni0lfckw0r3x65icmfhr194k-xorg-server-1.20.5.drv /gnu/store/xnc6a1fjwlwfjpg0lwai3aq51rw5qwrc-extra-cmake-modules-5.55.0.drv /gnu/store/jp29lhdwhs3znbsbznxq9nd9zp5l8ds0-qtbase-5.11.3.drv /gnu/store/sblg1v3yxf41b89aaj4r47zcyhxs3az4-ibus-1.5.20.drv /gnu/store/a4ynsy7ras28jlgmrhfilkc0lnin21mw-libnotify-0.7.7.drv /gnu/store/d8gvjnrl584wc5pavppa3m3yvm3jaxpk-dconf-0.32.0.drv 76.4 MB would be downloaded: /gnu/store/4vl3vkvqv0hhr0rlzciq55l4j8c5lgdz-ibus-1.5.20.tar.gz /gnu/store/jpxqw86l1gxkfrp66h5mc747xf881hjm-gettext-0.19.8.1 /gnu/store/9dgbqa3m412prwadpwg0ah7a3kv6fh9p-libnotify-0.7.7.tar.xz /gnu/store/aaha1wfv58b83fwp0fqg8b5nlpkw1bva-libmng-2.0.3 /gnu/store/6qy0ni5msmg93a55wi5qmj96729c1fcf-vulkan-headers-1.1.112 /gnu/store/3a3j7rnd49fr6papzd2r2i8f96ayxi1v-qtbase-everywhere-src-5.11.3.tar.xz /gnu/store/3n7yhbfl1gik3n64rmy1574djpc1w6m5-gperf-3.1 /gnu/store/wkfsm7mv8rjawdkzi8chf7qy8l5dppkm-xorg-server-1.20.5.tar.xz /gnu/store/7w7fq1iy0jkap5np4q00cw4cllr0lkj5-libdmx-1.1.4 /gnu/store/cc39n3mx1nswgwx7p8mbx7apy4j1w8yy-xtrans-1.3.5 /gnu/store/l1nxv1asf958h9ww4iijypyk31mj3d3x-gtk+-3.24.9.tar.xz /gnu/store/9rzjddyd621n26av5hb6zn55r372fhnv-libepoxy-1.5.3.tar.xz ```
bug#36942: Reconfigure broke GRUB
On Wed, Aug 14, 2019 at 03:50:00PM -0400, Jakob L. Kreuze wrote: > However, I still cannot seem to reproduce this issue with the most > recent master. Everything boots fine. I've extracted the bootloader > installation "script", and everything appears to be normal to me. Sorry it took me so long to reply, I didn't have access to the broken machine until now. As you requested here is the partitions as listed by parted: Number Start End SizeFile system NameFlags 1 1049kB 3046kB 2097kB grubbios_grub 2 3146kB 540MB 537MB fat32 efi boot, esp 3 540MB 2588MB 2048MB linux-swap(v1) swap 4 2588MB 750GB 748GB ext4guixsd /boot/efi looks ok as far as I can tell at least. It's tree is: /boot/efi/ └── EFI ├── grub │ └── grubx64.efi ├── Guix │ └── grubx64.efi └── GuixSD └── grubx64.efi All 3 grubx64.efi files differ from each other and are around 120kb. But considering you can't reproduce the issue would it be a good idea for me to reinstall and see if I can even reproduce it? Although I think this time I would leave off the bios_grub partition I'm willing to keep testing the current bug if it's important or indicative of a more serious problem. But please don't feel obligated to keep working on this just for me, I'm perfectly fine just reinstalling. The issue doesn't seem to affect my desktop anyway, I was able to upgrade it smoothly. It's always possible the issue was caused by some strange combination involving the patched bug, from earlier in the discussion, and my weird partition layout. Might not even be worth investigating unless it happens to someone else (or me again after a fresh install).
bug#37014: Gajim blows me with Pop-Up Errors
> This sounds like some Gajim state is corrupt. Could you try again > after > moving ~/.cache/gajim/cache.db out of the way? Thanks for the suggestion. I made gajim to work normal but I had to remove ./local/gajim/logs.db. Regards, RG. signature.asc Description: This is a digitally signed message part
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
Do I understand correctly that this message appears when booting the DVD, not the installed system? On Wed, Aug 14, 2019 at 03:32:06PM -0700, Calvin Heim wrote: > waiting for partition '31393730-3031-3031-3139-343934363833' to appear... I cannot check right now if that is a legitimate partition id for the i686 installer, but the installer source code in gnu/system/install.scm should mount a partition with (file-system-label "Guix_image"). You could check from another OS if this partition label exists. You could also type in the recovery Guile repl that opens: (use-modules (ice-9 ftw)) (scandir "/dev/disk/by-id") (scandir "/dev/disk/by-uuid") (scandir "/dev/disk/by-partuuid") and maybe: ,L bournish cat /run/booted-system/etc/fstab Regards, Florian
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
On Thu, Aug 15, 2019 at 11:02:29AM +0200, pelzflorian (Florian Pelz) wrote: > Which kind of Macbook is this? At the top of > > https://wiki.archlinux.org/index.php/Macbook > > I see a big fat warning that 2016 and 2017 Macbooks do not yet work > well with Linux (the kernel, I suppose). Some of these issues may > have workarounds, but it would be good to know if they apply to your > Macbook version. > Looks like it is the macbook 1,1. IIRC it has a pre-standardized EFI implementation in 32-bit, don't remember if the laptop itself is 32- or 64- bit. Personally I would try it with Debian's special mac-installer image first to see if that happens to boot up. Does this laptop still have the original BIOS/EFI implementation or has it perchance been replaced with libreboot? -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
On Thu, Aug 15, 2019 at 11:02:29AM +0200, pelzflorian (Florian Pelz) wrote: > Which kind of Macbook is this? At the top of > > https://wiki.archlinux.org/index.php/Macbook > > I see a big fat warning that 2016 and 2017 Macbooks do not yet work > well with Linux (the kernel, I suppose). Some of these issues may > have workarounds, but it would be good to know if they apply to your > Macbook version. > Please ignore this mail; I see you wrote Macbook1,1 in the subject line.
bug#37021: GuixSD 1.01-i686 install DVD boot failure on Macbook1, 1: failed to resolve partition
Which kind of Macbook is this? At the top of https://wiki.archlinux.org/index.php/Macbook I see a big fat warning that 2016 and 2017 Macbooks do not yet work well with Linux (the kernel, I suppose). Some of these issues may have workarounds, but it would be good to know if they apply to your Macbook version. Regards, Florian
