Hi Thomas,
"Thomas Schmitt" skribis:
> Ludovic Courtès wrote:
>> I don’t feel like distributing two variants of the ISO per architecture.
>
> Then i guess the most early opportunity for my proposal to get
> into production is after the upcomming Guix release.
Sounds good to me. Thanks again fo
Hi,
Ludovic Courtès wrote:
> I don’t feel like distributing two variants of the ISO per architecture.
Then i guess the most early opportunity for my proposal to get
into production is after the upcomming Guix release.
> It’s also something other distros don’t do: you get only one
> ISO per arch
Hi Thomas,
"Thomas Schmitt" skribis:
> I asked Danny, whether the download servers could offer two partition
> table variations of the ISOs: GPT and MBR (both with APM/HFS+).
> Goal would be to gain experience with MBR and to finally replace GPT
> by that layout.
> He expressed the hope that oth
On Fri, Apr 26, 2019 at 04:41:27PM +0200, Ludovic Courtès wrote:
> So the ISO only “fails” (somehow?) on old Macs, is that correct?
>
> If it’s “just” about old Macs, that’s not a 1.0 blocker for me (though
> it’s something we should fix.)
>
Old Macs are the only machines we know of that otherwis
"pelzflorian (Florian Pelz)" skribis:
> On Thu, Apr 25, 2019 at 06:34:16PM +0200, Ludovic Courtès wrote:
>> I lost track of the discussion. You’re looking at a MacBook-specific
>> issue, right?
>>
>> (The underlying question being: can this wait after 1.0 is out? :-)
>> If it’s MacBook-specifi
Hi,
Ludovic Courtès wrote:
> > I lost track of the discussion. You’re looking at a MacBook-specific
> > issue, right?
Florian Pelz wrote:
> As I understand it, Thomas’ work is about
> - making a correct ISO image and
The grub-mkrescue ISOs are correct but also sometimes inconvenient on
USB stic
On Thu, Apr 25, 2019 at 06:34:16PM +0200, Ludovic Courtès wrote:
> I lost track of the discussion. You’re looking at a MacBook-specific
> issue, right?
>
> (The underlying question being: can this wait after 1.0 is out? :-)
> If it’s MacBook-specific, I would answer “yes.”)
>
As I understand i
> How deep shall this go ? dd, awk, od, head, find, test, mv, rm, ...
Ideally everything. That's why we don't use shell scripts that much: They
are annoying to make behave. Compare with C which will link a library and
with option "-Wl,-rpath" (which we use everywhere) will embed the absolute
pa
Hi,
i wrote:
> > --file-system-type=iso9660[_$variation]
Danny Milosavljevic wrote:
> I'm not sure yet. We have a lot of special-casing for iso9660
> already. If anything, at that point, we could pass an arbitrary list
> of options or something (an "environment" if you will. Hah).
How ever
Hi Thomas,
On Thu, 25 Apr 2019 18:22:11 +0200
"Thomas Schmitt" wrote:
> Then do if you can make use of those two git commits.
> They are the only ones to that file since release 1.5.0.
Okay, I've picked them up.
> > I'm not sure about amending "guix system disk-image" by options that
> > aren'
Hi,
i worte:
> > (My other sport besides ISO 9660 is burning flat round things.)
Florian Pelz wrote:
> :D Burning is not the problem. ;)
We could let xorriso put some read load on it and watch out for error
messages.
> With the USB flash drive booting was not stuck, it just did not appear
> in
Hello,
"pelzflorian (Florian Pelz)" skribis:
> So what’s the plan?
>
> Wait for another responce from the grub-devel mailing list?
>
> Package grub-mkrescue-sed.sh and use
> --xorriso=/path/to/grub-mkrescue-sed.sh when calling grub-mkrescue?
>
> Add an option to “guix system disk-image” to selec
Hi,
Danny Milosavljevic wrote:
> you *are* upstream so
> it's really up to you whether we should patch xorriso or not.
Then do if you can make use of those two git commits.
They are the only ones to that file since release 1.5.0.
> I'm not sure about amending "guix system disk-image" by options
On Thu, Apr 25, 2019 at 05:09:05PM +0200, Thomas Schmitt wrote:
> Hi,
>
> Florian Pelz wrote:
> > I do not know and did not try yet how to configure GRUB to produce
> > both 32-bit and 64-bit EFI.
> […]
> Some digging in the source of grub-mkrescue and util/grub-install-common.c
> reveils that it
Hi,
Florian Pelz wrote:
> I do not know and did not try yet how to configure GRUB to produce
> both 32-bit and 64-bit EFI.
As Debian user i am in the comfortable position to install the
three binary packages for BIOS, x86 EFI 32 bit, and x86 EFI 64 bit.
Then grub-mkrescue knows what to do.
Some
> How comfortable is the Guix patching system ? :))
Very comfortable. But we'd like not to diverge from upstream too much.
We are all in this together, so I'd like upstream to eventually converge on
a solution. I'm fine with carrying a patch if it's coordinated by people with
knowledge about the
Hi,
Florian Pelz wrote:
> So what’s the plan?
> Wait for another responce from the grub-devel mailing list?
They need time to to make up their mind. Maybe other incidents are needed to
push towards some change in grub-mkrescue.
We have a halfways positive response from the old owner and a somewha
On Wed, Apr 24, 2019 at 11:13:23AM +0200, pelzflorian (Florian Pelz) wrote:
> On Wed, Apr 24, 2019 at 08:56:57AM +0200, Thomas Schmitt wrote:
> > Florian Pelz wrote
> > > By the way, someone I know has a most peculiar machine called Lenovo
> > > Ideapad 100S which does not boot Guix, […]
> >
> > I
So what’s the plan?
Wait for another responce from the grub-devel mailing list?
Package grub-mkrescue-sed.sh and use
--xorriso=/path/to/grub-mkrescue-sed.sh when calling grub-mkrescue?
Add an option to “guix system disk-image” to select which
grub-mkrescue-sed.sh environment variables to enable?
Hi,
Danny Milosavljevic wrte:
> If someone is testing this with Guix, make sure to actually try to boot Guix
> with it (until the root is mounted). Back in the day I changed the root
> discovery of Guix to make it also consider using the entire disk (as opposed
> to a partition on it) as a viable
Hi Thomas,
thanks for the investigative work you are doing.
If someone is testing this with Guix, make sure to actually try to boot Guix
with it (until the root is mounted). Back in the day I changed the root
discovery of Guix to make it also consider using the entire disk (as opposed to
a parti
Hi,
Florian Pelz wrote:
> Sorry, I meant to quote this aspect:
I wrote:
> > > One can read trailing garbage not only from USB sticks but also from
> > > most DVD types.
Florian Pelz wrote:
> > So… GPT is wrong for some optical media too?
I wrote:
> Not in this aspect. GPT partitions must not st
On Wed, Apr 24, 2019 at 08:56:57AM +0200, Thomas Schmitt wrote:
> Florian Pelz wrote
> > So… GPT is wrong for some optical media too?
>
> Not in this aspect. GPT partitions must not start at block 0.
> So the overall ISO superblock is not mountable as partition and thus
> free to claim the full im
Hi,
i wrote:
> > > > So programs like /sbin/isosize can tell the image size
> > (The [Debian] layout with nested partitions obsoletes the cleanliness
> > considerations about partition start at LBA 0.)
Florian Pelz wrote
> So… GPT is wrong for some optical media too?
Not in this aspect. GPT pa
On Tue, Apr 23, 2019 at 10:18:10PM +0200, Thomas Schmitt wrote:
> Florian Pelz wrote:
> > florian@florianmacbook ~ [env]$ grub-mkrescue -o output.iso minimal
> > --xorriso=./grub-mkrescue-sed.sh
> > grub-mkrescue: warning: Your xorriso doesn't support `--grub2-boot-info'.
> > Some features are disa
Hi,
Florian Pelz wrote:
> florian@florianmacbook ~ [env]$ grub-mkrescue -o output.iso minimal
> --xorriso=./grub-mkrescue-sed.sh
> grub-mkrescue: warning: Your xorriso doesn't support `--grub2-boot-info'.
> Some features are disabled. Please use xorriso 1.2.9 or later..
>
> and yields no output.is
This sounds nice and clean. Thank you!
On Tue, Apr 23, 2019 at 08:14:48PM +0200, Thomas Schmitt wrote:
> A disadvantage is that for best overall properties, this layout should
> have the ISO partition start at 512-byte block 64. This needs a second
> superblock and directory tree. About 17 MiB wi
Hi,
after the adventure of diagnosing Macbook EFI and mformat, i want to
return to the original topic of this thread:
I deem it worthwhile to offer the opportunity to create the Guix ISO
with MBR partition table rather than with GPT.
If you just want to see my technical proposal, then hop to the
Hi,
Florian pelaz wrote:
> So the options are:
> · Update mtools and then somehow patch mformat to zero out this
> region.
I will hopefully tonight post a proposal for
- Leave grub-mkrescue and mformat as they are. Rather do the partition
entry removal in the course of Guix ISO production.
I
A friend’s “early 2014” MacBookAir6,2 does not have issues with the
old iso image. It seems likely that only old Macbooks are affected.
On Sun, Apr 21, 2019 at 02:27:10PM +0200, Thomas Schmitt wrote:
> > I change it to
> >80 00 02 00 01 01 12 4f 01 00 00 00 3f 0b 00 00
> > I dd
Hi,
Ady Ady gave me a hint about why the EFI partition in Guix 0.16.0 ISO
has 1.4 MB of size, despite grub-mkrescue asks mformat for 2.8 MB.
Obviously Guix uses mtools 4.0.21 (image OEM-ID "MTOO4021") which is one
version before this bug fix:
"Fixed -f flag for mformat (size is KBytes, rather t
Hi,
Florian Pelz wrote:
> it is not
> 80 00 00 04 01 24 4f 00 00 00 00 80 16 00 00 00
> but
> 80 00 01 00 04 01 24 4f 00 00 00 00 80 16 00 00 00
This makes more sense as an MBR partition table entry:
Start C/H/S is 0/0/1.
Start LBA is 0.
Block count is 0x1680 = 5760
On Sun, Apr 21, 2019 at 02:27:10PM +0200, Thomas Schmitt wrote:
> Hi,
>
> i wrote:
> > > ... 3f 0b
> > > ... 40 0b
> > > ... == ==
>
> Florian Pelz wrote:
> > Why is 0b underlined?
>
> Too much enthusiasm on my side.
>
>
> > OK, so I just wrote the Guix git master with ludo’s reproducibilit
Hi,
i wrote:
> > ... 3f 0b
> > ... 40 0b
> > ... == ==
Florian Pelz wrote:
> Why is 0b underlined?
Too much enthusiasm on my side.
> OK, so I just wrote the Guix git master with ludo’s reproducibility
> patches to a USB drive (boot gets stuck again) and then did:
> sudo dd if=/dev/sdc2 of=m
On Sun, Apr 21, 2019 at 01:16:14PM +0200, Thomas Schmitt wrote:
> For that discussion i could also need the exact model name of the Macbook.
> If its EFI has a name, then this too.
>
I booted my ancient version of macOS Yosemite and clicked on the apple
symbol in the top left corner and About thi
Hi,
i plan to ask at gru-devel about mformat, its MBR, and the partition entry,
as soon as the last experiment is made (LBA 1 rather than LBA 0 as start
of the inner partition).
For that discussion i could also need the exact model name of the Macbook.
If its EFI has a name, then this too.
Flor
On Sun, Apr 21, 2019 at 11:35:49AM +0200, Thomas Schmitt wrote:
> Ok, now for the last experiment. Just for curiosity, as i believe it
> is not a good solution (and mformat -k isn't either):
> Does start LBA 1 of partition 1 prevent the endless loop, too ?
>
> So please write to byte 446 (dec) to
Hi,
i wrote:
> > with the Guix EFI partition image in
> > partition 2 of the USB stick and
> >dd if=/dev/zero bs=1 count=16 seek=446 of=/dev/sdc2
Florian Pelz wrote:
> Yes, this fixes the issue.
I really had a good feeling with that theory. :))
--
On Sat, Apr 20, 2019 at 06:32:07PM +0200, Thomas Schmitt wrote:
> We still need to find out whether the partition entry is the culprit.
> So please do the experiment with the Guix EFI partition image in
> partition 2 of the USB stick and
>
>dd if=/dev/zero bs=1 count=16 seek=446 of=/dev/sdc2
>
Hi,
Florian Pelz wrote:
> mkfs.fat fatfs.img
> sudo mount fatfs.img /mnt/img
> sudo cp -r /mnt/efiimg/efi /mnt/img/
> Hooray! It boots!
So it is indeed the filesystem hull, which is to blame.
We still need to find out whether the partition entry is the culprit.
So please do the experiment with
On Sat, Apr 20, 2019 at 04:54:24PM +0200, pelzflorian (Florian Pelz) wrote:
> But… Guix’ gnu/build/vm.scm already uses mkfs.fat. Strange…
>
It uses mkfs.fat for creating FAT partitions, but maybe this
particular EFI partition is created by grub-mkrescue?
Regards,
Florian
On Sat, Apr 20, 2019 at 04:54:24PM +0200, pelzflorian (Florian Pelz) wrote:
> sudo dd if=fatfs.img of=/dev/sdc2
> sync
>
I can copy the same fatfs.img from Guix System 0.16.0 onto a current
Guix git master installer iso and it works too.
It works, see end of this e-mail.
On Sat, Apr 20, 2019 at 12:50:49PM +0200, Thomas Schmitt wrote:
> So after these steps :
>
> > I wrote guixsd-install-0.16.0.x86_64-linux.iso to my USB drive again.
> > Boot gets stuck again.
> >
> > I did `sudo dd if=/dev/zero of=/dev/sdc2` to zero out the EFI
>
Hi,
i wrote:
> To kill table entry 1 after having put the Guix EFI image back into
> partition 2 of the USB stick:
>
> dd if=/dev/zero bs=1 count=16 seek=446 of=/dev/sdc1
Of course i meant of=/dev/sdc2
The 16 bytes written to /dev/sdc1 would deface the GPT's "protective" MBR
and thus make the
Hi,
... and if the erasure of the partition table entry helps, would it then
also help if that entry's partition does not start at LBA 0 ?
Change bytes 446 (dec) to 461 (dec) from (in hex):
80 00 01 00 01 01 12 4f 00 00 00 00 40 0b 00 00
to
80 00 02 00 01 01 12 4f 01
Hi,
i now look at the FAT filesystem images of Debian Live 9 and Guix 0.16.0:
Guix:
- There is an MBR partition table in the image file:
DeviceBoot Start End Sectors Size Id Type
/mnt/iso/efi.img1 *0 28792880 1.4M 1 FAT12
- Program "file" says:
DOS/MBR b
Hi,
Florian Pelz wrote:
> I wonder, what kind of FAT is the EFI partition using? Could it be
> the wrong kind of FAT?
I got a mail from a bystander, Ady Ady whom i know from SYSLINUX/ISOLINUX
mailing list. He proposes the experiment to exchange the whole EFI partition
of the Guix ISO by the one
I wrote guixsd-install-0.16.0.x86_64-linux.iso to my USB drive and
mounted it. I am trying to make the boot not get stuck.
I replaced efi/boot/bootx64.efi by Debian’s bootx64.efi. Still stuck.
I deleted efi/boot/bootx64.efi. Still stuck.
I changed the EFI partition’s GPT type code with gdisk
Hi,
Florian Pelz wrote:
> The DVD works and is bootable. :)
Hrmpf. I hate it when success spoils a theory.
I wrote:
> > The youngest without "Secure" in its bootx64.efi is
> > debian-7.7.0-amd64-netinst.iso
> No, it does not hang, it is bootable.
It is about time for black candles and the t
What is this --hfs-bless option of mkisofs? This is not related by
any chance?
Regards,
Florian
On Fri, Apr 19, 2019 at 12:58:58PM +0200, Thomas Schmitt wrote:
> The youngest without "Secure" in its bootx64.efi is
> debian-7.7.0-amd64-netinst.iso
>
> You could check whether this hangs like Guix.
>
No, it does not hang, it is bootable.
> SHA512:
>
> 5cb6e4fea55fbb5173f90c3a545b843c6c
On Fri, Apr 19, 2019 at 11:01:51AM +0200, Thomas Schmitt wrote:
> Florian Pelz wrote:
> > I could try burning a DVD and attempt to boot from it.
>
> On DVD the El Torito boot equipment should lead EFI to the same partition
> image as the partition table should do on USB stick.
> But a try cannot h
Hi,
Florian Pelz wrote:
> For x86_64 iso images, the Macbook does *not dismiss*. It gets stuck
> in the lightgray startup screen forever without showing a menu with
> the drives to boot from, except for the Debian ISO image, for which a
> menu is shown with an »EFI partition« that runs a bootload
On Fri, Apr 19, 2019 at 11:01:51AM +0200, Thomas Schmitt wrote:
> Hi,
>
> i wrote:
> > > this is the xorriso run for producing a layout like "isohybrid --uefi"
>
> Florian Pelz wrote:
> > No, it still gets stuck. :(
>
> Then it must be something inside the EFI partition which makes the
> Macbook
Hi,
i wrote:
> > this is the xorriso run for producing a layout like "isohybrid --uefi"
Florian Pelz wrote:
> No, it still gets stuck. :(
Then it must be something inside the EFI partition which makes the
Macbook firmware dismiss the partition for booting.
> The GPT partition GUID is different
On Thu, Apr 18, 2019 at 03:50:59PM +0200, Thomas Schmitt wrote:
> > the Guix USB drive
> > merely does not show up (for Debian, it shows up as an EFI partition
> > in the boot menu).
>
> So probably it is not run.
>
Boot gets stuck on x86_64 Guix images only, but the one i686 I tried
did not sho
On Thu, Apr 18, 2019 at 11:28:13PM +0200, Thomas Schmitt wrote:
> Hi,
>
> this is the xorriso run for producing a layout like "isohybrid --uefi"
> with GRUB equipment for BIOS instead of ISOLINUX.
>
No, it still gets stuck. :(
> Expected inspection result:
>
The GPT partition GUID is differe
Hi,
this is the xorriso run for producing a layout like "isohybrid --uefi"
with GRUB equipment for BIOS instead of ISOLINUX.
I prepended command -stdio_sync "off" in order to make use of my generous
amount of RAM for write buffering. The default syncs to disk every 16 MiB.
Good with low RAM or fa
Hi,
Florian Pelz wrote:
> I find a efi/boot/bootx64.efi PE executable inside efi.img on the Guix
> ISO. On Debian the long name is EFI/boot/bootx64.iso in capital letters
(I assume s/bootx64.iso/bootx64.efi/)
It's FAT filesystem. Upper case or lower case does not matter.
Most probably it is a ma
On Thu, Apr 18, 2019 at 10:13:33AM +0200, Thomas Schmitt wrote:
> Florian Pelz wrote:
> > ... > On the 2011 Macbook I am using
>
> The rumors rather talk of the years up to 2010. But well ...
>
>
Next week I can ask others who own newer Macbooks to try out the ISO.
If this only affects old Macb
Hi,
i wrote:
> > From Florian's reports i cannot tell which ISO he used
Florian Pelz wrote:
> The current git master for x86_64.
I begin to remember discussions about 64-bit Macs having 32-bit EFI
firmware.
Googling brought me to
https://everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-
On Thu, Apr 18, 2019 at 09:00:23AM +0200, Thomas Schmitt wrote:
> From Florian's reports i cannot tell which ISO he used as base for
> repacking. Maybe one should distinguish the ISOs by their Volume Id. Like:
> GUIXSD_IMAGE_I686
> GUIXSD_IMAGE_X86_64
The current git master for x86_64. I can
Hi,
meanwhile i learned that "i686" means 32 bit.
So i downloaded
guixsd-install-0.16.0.x86_64-linux.iso
and see indeed the boot program for 64 bit x86 in the EFI partition:
-rwxr-xr-x 1 root root 132608 Dec 5 16:59 /mnt/fat/efi/boot/bootx64.efi
>From Florian's reports i cannot tell which
Hi,
Florian Pelz wrote:
> my Macbook still does not like it.
The content of the EFI partition of guixsd-install-0.15.0.i686-linux.iso
does not look like it is ready for 64-bit x86:
$ mount guixsd-install-0.15.0.i686-linux.iso /mnt/iso
$ mount /mnt/iso/efi.img /mnt/fat
$ find /mnt/fat -exec
On Wed, Apr 17, 2019 at 05:51:41PM +0200, Thomas Schmitt wrote:
> Hi,
>
> here are instructions to repack a Guix ISO with EFI support (via GPT)
> to an ISO with MBR-only partition table.
>
Thank you! However, even though Linux is happy about the repacked
ISO, my Macbook still does not like it.
Hi,
here are instructions to repack a Guix ISO with EFI support (via GPT)
to an ISO with MBR-only partition table.
Tested with guixsd-install-0.15.0.i686-linux.iso, because my copy
of 0.16.0 is one of the victims of bug#33639.
It becomes 130 MiB larger than the original, probably because there
w
On Wed, Apr 17, 2019 at 02:24:12PM +0200, Ludovic Courtès wrote:
> "pelzflorian (Florian Pelz)" skribis:
>
> > On Tue, Apr 16, 2019 at 09:55:10PM +0200, pelzflorian (Florian Pelz) wrote:
> >> On the 2011 Macbook I am using, the boot process gets stuck before I
> >> can select the drive to boot fr
"pelzflorian (Florian Pelz)" skribis:
> On Tue, Apr 16, 2019 at 09:55:10PM +0200, pelzflorian (Florian Pelz) wrote:
>> On the 2011 Macbook I am using, the boot process gets stuck before I
>> can select the drive to boot from, as long as a USB flash drive with
>> this GPT error is in a USB port.
On Wed, Apr 17, 2019 at 12:23:56PM +0200, Thomas Schmitt wrote:
> This operation has killed the MBR partition table with the entry for
> the EFI partition.
> […]
> Did you try booting before or after the gdisk run ?
>
>
Before. I also did not write out. Note that I also called gdisk on
the iso
Hi,
Florian Pelz wrote:
> $ gdisk Downloads/debian-live-9.8.0-amd64-xfce.iso
> ...
> Found valid MBR and GPT. Which do you want to use?
> 1 - MBR
> 2 - GPT
> ...
> Your answer: 2
> Using GPT and creating fresh protective MBR.
> Warning! Main partition table overlaps the first partition by 64 block
The Parabola ISO parabola-systemd-cli-i686-netinstall-2018.06.02.iso
does not inhibit the boot process but also contains no EFI partition
so I cannot boot from it.
Debian 9.8.0 works, see the end of this mail.
On Tue, Apr 16, 2019 at 11:15:56PM +0200, Thomas Schmitt wrote:
> Hi,
>
> i wrot
Hi,
i wrote:
> > A broken backup GPT is not supposed to stop EFI from finding its partition
Florian Pelz wrote:
> On the 2011 Macbook I am using, the boot process gets stuck before I
> can select the drive to boot from, as long as a USB flash drive with
> this GPT error is in a USB port.
Did you
On Tue, Apr 16, 2019 at 09:55:10PM +0200, pelzflorian (Florian Pelz) wrote:
> On the 2011 Macbook I am using, the boot process gets stuck before I
> can select the drive to boot from, as long as a USB flash drive with
> this GPT error is in a USB port. The few other computers I tried have
> no pro
On Tue, Apr 16, 2019 at 07:57:20PM +0200, Thomas Schmitt wrote:
> Hi,
>
> Florian Pelz wrote:
> > I would prefer an image that can be written just with dd,
>
> A broken backup GPT is not supposed to stop EFI from finding its partition
> and running its architecture specific start-up program.
>
Hi,
Florian Pelz wrote:
> I would prefer an image that can be written just with dd,
A broken backup GPT is not supposed to stop EFI from finding its partition
and running its architecture specific start-up program.
But it becomes annoying when another partition shall be created for
a read-write
I would prefer an image that can be written just with dd, because then
it would also be easy to use another tool like gnome-multi-writer or
to use a not UNIX-like OS to create the install USB and give
GNU Guix System a try.
Regards,
Florian
Hi,
Gábor Boskovits wrote:
> I removed the xorriso bug list, as I feel this does not belong there.
As its admin i say that everything xorriso related belongs there. :))
But maybe we should remove 33...@debbugs.gnu.org from the Cc ?
I herby give this a try.
i wrote:
> > The alternative/backup
77 matches
Mail list logo
