GNU bug report logs -
#37021
GuixSD 1.01-i686 install DVD boot failure on Macbook1,1: failed to resolve partition
Previous Next
Reported by: Calvin Heim <calheim <at> sbcglobal.net>
Date: Tue, 13 Aug 2019 23:05:01 UTC
Severity: normal
Tags: moreinfo
Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37021 in the body.
You can then email your comments to 37021 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Tue, 13 Aug 2019 23:05:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Calvin Heim <calheim <at> sbcglobal.net>:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org.
(Tue, 13 Aug 2019 23:05:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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):
ehci-pci 0000:00:1d.7: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.7 setup!??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.7: init 0000:00:1d.7 fail, -19????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.0 setup!??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -19????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.1: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.1 setup!??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.1: init 0000:00:1d.1 fail, -19????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.2 setup!??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.2: init 0000:00:1d.2 fail, -19????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.3: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.3 setup!??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
ehci-pci 0000:00:1d.3: init 0000:00:1d.3 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"????????????
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.
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Wed, 14 Aug 2019 22:33:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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 0000:00:1d.7: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.7 setup!
ehci-pci 0000:00:1d.7: init 0000:00:1d.7 fail, -19
ehci-pci 0000:00:1d.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.0 setup!
ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -19
ehci-pci 0000:00:1d.1: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.1 setup!
ehci-pci 0000:00:1d.1: init 0000:00:1d.1 fail, -19
ehci-pci 0000:00:1d.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.2 setup!
ehci-pci 0000:00:1d.2: init 0000:00:1d.2 fail, -19
ehci-pci 0000:00:1d.3: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.3 setup!
ehci-pci 0000:00:1d.3: init 0000: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.
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 09:03:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 09:08:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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.
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 09:13:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 37021 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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 <efraim <at> flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 10:44:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 19:17:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 37021 <at> debbugs.gnu.org (full text, mbox):
Calvin Heim <frofroggy <at> gmail.com> 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 0000:00:1d.7: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.7 setup!
> ehci-pci 0000:00:1d.7: init 0000:00:1d.7 fail, -19
> ehci-pci 0000:00:1d.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.0 setup!
> ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -19
> ehci-pci 0000:00:1d.1: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.1 setup!
> ehci-pci 0000:00:1d.1: init 0000:00:1d.1 fail, -19
> ehci-pci 0000:00:1d.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.2 setup!
> ehci-pci 0000:00:1d.2: init 0000:00:1d.2 fail, -19
> ehci-pci 0000:00:1d.3: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.3 setup!
> ehci-pci 0000:00:1d.3: init 0000: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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 22:01:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 37021 <at> debbugs.gnu.org (full text, mbox):
On Thu, 2019-08-15 at 15:15 -0400, Mark H Weaver wrote:
> Calvin Heim <frofroggy <at> gmail.com> 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 0000:00:1d.7: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.7 setup!
> > ehci-pci 0000:00:1d.7: init 0000:00:1d.7 fail, -19
> > ehci-pci 0000:00:1d.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.0 setup!
> > ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -19
> > ehci-pci 0000:00:1d.1: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.1 setup!
> > ehci-pci 0000:00:1d.1: init 0000:00:1d.1 fail, -19
> > ehci-pci 0000:00:1d.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.2 setup!
> > ehci-pci 0000:00:1d.2: init 0000:00:1d.2 fail, -19
> > ehci-pci 0000:00:1d.3: Found HC with no IRQ. Check BIOS/PCI 0000:00:1d.3 setup!
> > ehci-pci 0000:00:1d.3: init 0000: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 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 : 0x8000000 from 0xc1000000 (relocation range: 0xc0000000-0xf7dfdfff)
Kernel rebooting in 30 seconds
>%----------end paste------------------------->%
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 22:05:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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.
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 22:07:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 22:08:01 GMT)
Full text and
rfc822 format available.
Message #35 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 23:12:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 37021 <at> debbugs.gnu.org (full text, mbox):
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.
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 23:39:02 GMT)
Full text and
rfc822 format available.
Message #41 received at 37021 <at> debbugs.gnu.org (full text, mbox):
Hi Calvin,
Calvin Heim <frofroggy <at> gmail.com> 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 : 0x8000000 from 0xc1000000 (relocation range: 0xc0000000-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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 15 Aug 2019 23:54:02 GMT)
Full text and
rfc822 format available.
Message #44 received at 37021 <at> debbugs.gnu.org (full text, mbox):
Mark H Weaver <mhw <at> netris.org> writes:
> Hi Calvin,
>
> Calvin Heim <frofroggy <at> gmail.com> 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 : 0x8000000 from 0xc1000000 (relocation range: 0xc0000000-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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Fri, 16 Aug 2019 03:26:01 GMT)
Full text and
rfc822 format available.
Message #47 received at 37021 <at> debbugs.gnu.org (full text, mbox):
On Thu, 2019-08-15 at 19:37 -0400, Mark H Weaver wrote:
> Hi Calvin,
>
> Calvin Heim <frofroggy <at> gmail.com> 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 : 0x8000000 from 0xc1000000 (relocation range: 0xc0000000-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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Fri, 16 Aug 2019 05:34:02 GMT)
Full text and
rfc822 format available.
Message #50 received at 37021 <at> debbugs.gnu.org (full text, mbox):
Calvin Heim <frofroggy <at> gmail.com> 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
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Fri, 16 Aug 2019 19:52:01 GMT)
Full text and
rfc822 format available.
Message #53 received at 37021 <at> debbugs.gnu.org (full text, mbox):
On +2019-08-15 15:05:57 -0700, Calvin Heim wrote:
> 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]
>
I have found this incantation, and variants, e.g. filtering with grep, useful also:
$ stat -c %N /dev/disk/by-*/*
I have also encountered, IIRC, system versions where /disk/dev/by-* could present info
from stale cache information, so it might not show what e.g. the following might:
$ lsblk
$ lsblk -f
For your purposes, it might be worth trying asking for interesting
specifics (see lsblk -h for more), e.g.
$ lsblk -o mountpoint,name,size,fstype,label,partlabel,partuuid,uuid
Maybe that partuuid '31393730-3031-3031-3139-343934363833' might show up?
BTW, I think some older systems might not know how to look for partuuid,
(especially beyond the intial boot device?) and it could be worth trying
plain uuid instead. I suspected such a stiutation when I got
a not-found in the past, but did not diagnose it unambigously.
--8<--aside
BTW2, I am using refind to multiboot, and consider my shooting myself in the foot
(clobbering my efi partition with unintended grub install) as a kind of usability-bug,
which I am tempted to use as rationale for posting to this list (but not hijacking
this post further ;-) Would that be ok, or should I join guix-help as well? I am getting
more email traffic than I am used to :) ...
(I would like to mount a losetup file partition as a target for grub bootloader install,
and thereby capture initrds etc for manual (at first ;-) transfer into my refind efi vfat
file tree.)
--8<--aside--
> 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
>
Regards,
Bengt Richter
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Fri, 16 Aug 2019 22:19:01 GMT)
Full text and
rfc822 format available.
Message #56 received at 37021 <at> debbugs.gnu.org (full text, mbox):
On Fri, Aug 16, 2019 at 12:51:28PM -0700, Bengt Richter wrote:
> For your purposes, it might be worth trying asking for interesting
> specifics (see lsblk -h for more), e.g.
>
> $ lsblk -o mountpoint,name,size,fstype,label,partlabel,partuuid,uuid
>
> Maybe that partuuid '31393730-3031-3031-3139-343934363833' might show up?
>
I just checked for my working USB image and the
boot/grub/grub.cfg contains that line
bzImage --root=31393730-3031-3031-3139-343934363833 --system=/gnu/store/2j79kbvsxqq7lmzp3isnran1dpcp2z5j-system --load=/gnu/store/2j79kbvsxqq7lmzp3isnran1dpcp2z5j-system/boot quiet
but I cannot find that partition either. It seems to be created by
grub-mkrescue from make-iso9660-image, but I am not sure.
@Calvin: The manual contains this line in section _Building the
Installation Image_ (with Mark’s --system=i686-linux added):
guix system disk-image --file-system-type=iso9660 --system=i686-linux \
gnu/system/install.scm
If you omit --file-system-type=iso9660, a USB image will still work
and I believe no --root=31393730-3031-3031-3139-343934363833 will be
inserted in GRUB.
Regards,
Florian
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 22 Aug 2019 14:32:02 GMT)
Full text and
rfc822 format available.
Message #59 received at 37021 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Calvin,
could you try booting https://drive.google.com/open?id=15YTPS2jt1l3VMyE4LTbMCoy7DnEu7etv from DVD and later from USB Flash drive?
[Message part 2 (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 22 Aug 2019 18:35:02 GMT)
Full text and
rfc822 format available.
Message #62 received at 37021 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi,
On Thu, 22 Aug 2019 16:31:19 +0200
Danny Milosavljevic <dannym <at> scratchpost.org> wrote:
> could you try booting https://drive.google.com/open?id=15YTPS2jt1l3VMyE4LTbMCoy7DnEu7etv from DVD and later from USB Flash drive?
Sorry, I didn't mean that one. Wrong architecture.
https://drive.google.com/open?id=15aGwwzF8IrijSKeUi1OWRbl0aPKGGW4b
(guix master for i686)
[Message part 2 (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 22 Aug 2019 21:28:02 GMT)
Full text and
rfc822 format available.
Message #65 received at 37021 <at> debbugs.gnu.org (full text, mbox):
Hi Danny,
Danny Milosavljevic <dannym <at> scratchpost.org> writes:
> On Thu, 22 Aug 2019 16:31:19 +0200
> Danny Milosavljevic <dannym <at> scratchpost.org> wrote:
>
>> could you try booting https://drive.google.com/open?id=15YTPS2jt1l3VMyE4LTbMCoy7DnEu7etv from DVD and later from USB Flash drive?
>
> Sorry, I didn't mean that one. Wrong architecture.
>
> https://drive.google.com/open?id=15aGwwzF8IrijSKeUi1OWRbl0aPKGGW4b
>
> (guix master for i686)
I appreciate your effort to make life easier for Calvin, but in general
it seems like a bad security practice to post large unsigned disk images
and asking users to try them. A digital signature from you would
improve matters somewhat, but ideally there should also be a description
of how to reproduce this image.
It's also not good to be promoting Google Drive here, which requires
non-free Javascript. I'm aware that IceCat includes an extension to
allow Google Drive to at least partially work with LibreJS, but I was
unable to easily get it to work on my IceCat configuration where I use
NoScript instead.
Thoughts?
Mark
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 22 Aug 2019 22:34:01 GMT)
Full text and
rfc822 format available.
Message #68 received at 37021 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Mark,
Hi Calvin,
On Thu, 22 Aug 2019 17:26:50 -0400
Mark H Weaver <mhw <at> netris.org> wrote:
> I appreciate your effort to make life easier for Calvin, but in general
> it seems like a bad security practice to post large unsigned disk images
> and asking users to try them.
In general I agree. So I would suggest Calvin to try it and then later delete
the target drive.
I think it is unreasonable to expect users to build disk images of distributions
that don't work for them (it's nice if they do--but I don't like the shirking of
responsibility. It's a large time investment that has a big initial learning
curve and no guaranteed payoff).
> A digital signature from you would
> improve matters somewhat, but ideally there should also be a description
> of how to reproduce this image.
In this case, the current Guix release image doesn't have one important fix
that directly affects Macbooks. Therefore, I built a current image of guix
master (without any extra changes--so it does contain the fix):
$ ./pre-inst-env guix system disk-image -t iso9660 -s i686-linux gnu/system/install.scm
As I said in the past, let's please release Guix again soon so the fix is going
to users.
Also, I'm curious whether it improves the situation for Calvin (reading through
the thread, it might not--the failure is too late).
> It's also not good to be promoting Google Drive here, which requires
> non-free Javascript. I'm aware that IceCat includes an extension to
> allow Google Drive to at least partially work with LibreJS, but I was
> unable to easily get it to work on my IceCat configuration where I use
> NoScript instead.
In the end there's a limit to how much time I'm going to spend on this.
Google drive works and is easy enough to use--if there's an alternative that
at least takes less effort than Calvin building the image on his own, I'll
use that.
[Message part 2 (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Thu, 22 Aug 2019 22:35:02 GMT)
Full text and
rfc822 format available.
Message #71 received at 37021 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
> and asking users to try them. A digital signature from you would
> improve matters somewhat
sha256sum:
c09b3d75e15f46cf04605895402fcfeaf2d1ef92eeee2859c7e9fab49352debc guix-master-i686.iso
This mail is signed.
[Message part 2 (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Fri, 10 Jun 2022 01:12:01 GMT)
Full text and
rfc822 format available.
Message #74 received at 37021 <at> debbugs.gnu.org (full text, mbox):
Hi Calvin,
Calvin Heim <frofroggy <at> gmail.com> writes:
> 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.
Did you gave up, or eventually got it working?
Thanks,
Maxim
Added tag(s) moreinfo.
Request was from
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
to
control <at> debbugs.gnu.org.
(Fri, 10 Jun 2022 01:12:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org:
bug#37021; Package
guix.
(Fri, 10 Jun 2022 19:48:01 GMT)
Full text and
rfc822 format available.
Message #79 received at 37021 <at> debbugs.gnu.org (full text, mbox):
On Thu, 2022-06-09 at 21:11 -0400, Maxim Cournoyer wrote:
> Hi Calvin,
>
> Calvin Heim <frofroggy <at> gmail.com> writes:
>
> > 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.
>
> Did you gave up, or eventually got it working?
I gave up because my DVD-drive stopped reading discs and instead makes gentle
tapping sounds and three short low-pitched buzzes for thirty seconds before
ejecting any inserted media. Happens at both the OEM bootloader stage and after
Trisquel is fully booted. It's not a Guix problem -- it's my personal hardware
problem now.
I expect that you may wish to close the issue to tidy up, and I accept that
outcome.
Thanks,
Calvin
resent, forgot to cc the list
>
> Thanks,
>
> Maxim
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
You have taken responsibility.
(Sat, 11 Jun 2022 06:14:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Calvin Heim <calheim <at> sbcglobal.net>:
bug acknowledged by developer.
(Sat, 11 Jun 2022 06:14:02 GMT)
Full text and
rfc822 format available.
Message #84 received at 37021-done <at> debbugs.gnu.org (full text, mbox):
Hi Calvin,
Calvin Heim <frofroggy <at> gmail.com> writes:
> On Thu, 2022-06-09 at 21:11 -0400, Maxim Cournoyer wrote:
>> Hi Calvin,
>>
>> Calvin Heim <frofroggy <at> gmail.com> writes:
>>
>> > 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.
>>
>> Did you gave up, or eventually got it working?
>
> I gave up because my DVD-drive stopped reading discs and instead makes gentle
> tapping sounds and three short low-pitched buzzes for thirty seconds before
> ejecting any inserted media. Happens at both the OEM bootloader stage and after
> Trisquel is fully booted. It's not a Guix problem -- it's my personal hardware
> problem now.
Ah, the joys of vintage hardware :-).
> I expect that you may wish to close the issue to tidy up, and I accept that
> outcome.
OK, thanks for the prompt reply!
I do hope you get to install Guix successfully in another adventure to
have :-).
Thanks,
Maxim
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Sat, 09 Jul 2022 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 290 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.