From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Francisco Gómez" <espectalll@kydara.com>
Cc: 35856@debbugs.gnu.org
Subject: bug#35856: Unable to boot on iMac, likely because of UUIDs
Date: Wed, 22 May 2019 16:09:09 +0200 [thread overview]
Message-ID: <20190522140908.oy47v5u5ww3kgkrc@pelzflorian.localdomain> (raw)
In-Reply-To: <1558523401.20880.0@kydara.com>
On Wed, May 22, 2019 at 11:10:00AM +0000, Francisco Gómez wrote:
> When I have inserted a device recorded with a GuixSD image in my Late 2009
> iMac (EFI, not UEFI) during boot, the computer gets stuck in a loop and
> doesn't respond. I believe this is due to a lack of, or duplication, of
> UUIDs (not to be confused with PARTUUIDs) on some partitions, as manually
> assigning them allows my computer to properly detect the attached devices
> and boot from the GuixSD one (although not successfully).
>
> > udisksctl loop-setup -rf guix-system-install-1.0.1.x86_64-linux.iso
> Mapped file guix-system-install-1.0.1.x86_64-linux.iso as /dev/loop0.
>
> > sudo blkid -o list | grep ^/dev/loop0 | cut -d" " -f1 | sort
> /dev/loop0
> /dev/loop0p1
> /dev/loop0p2
> /dev/loop0p3
> /dev/loop0p4
>
> > sudo blkid -s UUID | grep ^/dev/loop0
> /dev/loop0: UUID="1970-01-01-19-49-46-83"
> /dev/loop0p2: UUID="C920-B8AE"
>
>
>
>
>
>
I believe this is <https://issues.guix.info/issue/35428>.
Unfortunately Danny pushed his patch after the 1.0.1 release got
branched off.
Can you try an ISO built from current Guix git master?
Regards,
Florian
next prev parent reply other threads:[~2019-05-22 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 11:10 bug#35856: Unable to boot on iMac, likely because of UUIDs Francisco Gómez
2019-05-22 14:09 ` pelzflorian (Florian Pelz) [this message]
2019-05-22 14:35 ` pelzflorian (Florian Pelz)
[not found] ` <1558617164.2167.0@kydara.com>
2019-05-23 20:18 ` pelzflorian (Florian Pelz)
2019-05-23 20:24 ` pelzflorian (Florian Pelz)
2019-05-22 17:23 ` Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190522140908.oy47v5u5ww3kgkrc@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35856@debbugs.gnu.org \
--cc=espectalll@kydara.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.