On 2019-05-11, John Paul Adrian Glaubitz wrote:
>>> If you find some time, I think it would be interesting if we had a
>>> grub-boot test image where BootX is using:
>>>
>>>
>>> boot &device;:,\System\Library\CoreServices\grub.elf
>>>
>>>
>>> I suspect Apple users would then be able to "properly
On 5/11/19 8:07 AM, John Paul Adrian Glaubitz wrote:
>> If you find some time, I think it would be interesting if we had a
>> grub-boot test image where BootX is using:
>>
>>
>> boot &device;:,\System\Library\CoreServices\grub.elf
>>
>>
>> I suspect Apple users would then be able to "properly" bo
CC-ing GRUB upstream.
The context are the new Debian installation ISOs which are now using GRUB
instead of Yaboot for booting the installer.
The debian-cd script which generates the ISO image with xorriso can be found
here:
> https://salsa.debian.org/images-team/debian-cd/blob/master/tools/boot/
On 2019-05-05, John Paul Adrian Glaubitz wrote:
> If just removing the extra colon fixes the problem *and* also does not
> break the boot using a CD-ROM (which currently works so it should be
> tested it still does with the change), we should fix the bug upstream.
I would like to point out that p
On 06/05/2019 10:35, John Paul Adrian Glaubitz wrote:
> On 5/5/19 4:24 PM, Mark Cave-Ayland wrote:
>> Right, these graft points are unnecessary - if you look at the BootX file on
>> the ISO
>> then it's simply a pointer to /boot/grub/powerpc-ieee1275/grub.chrp which is
>> a
>> bootinfo file cont
On 06/05/2019 10:25, John Paul Adrian Glaubitz wrote:
> On 5/5/19 2:47 PM, Mark Cave-Ayland wrote:
>> Ah no, that's not correct - BootX is an enhanced bootloader written by Apple
>> to
>> enable multi-booting with MacOS X and grub-mkrescue is assuming that it is
>> being
>> installed on a HD con
Hi,
i wrote:
> > If a file CD1/System/Library/CoreServices/BootX had existed on hard disk,
> > the pathspec "CD1" would have overwritten the previously inserted IsoNode
> > object which held the instruction to copy from "grub.chrp".
John Paul Adrian Glaubitz wrote:
> But there is no file CD1/Syst
On 5/4/19 9:19 PM, John Paul Adrian Glaubitz wrote:
> I just created the first test image for debian-installer which boots
> with GRUB instead of Yaboot. The image is available from the usual
> location for GRUB tests:
>
>> https://cdimage.debian.org/cdimage/ports/grub-test/
>
> Feel free to test
On 5/5/19 5:19 PM, Thomas Schmitt wrote:
>> BootX is an enhanced bootloader written by Apple [...]
>> in real life BootX is a COFF executable and not a bootinfo file.
>
> This seems to be not mutually exclusive.
>
> https://opensource.apple.com/source/bless/bless-11/README.BOOTING
> states
>
On 5/5/19 4:24 PM, Mark Cave-Ayland wrote:
> Right, these graft points are unnecessary - if you look at the BootX file on
> the ISO
> then it's simply a pointer to /boot/grub/powerpc-ieee1275/grub.chrp which is a
> bootinfo file containing this:
>
>
> boot &device;:&partition;,\System\Library\Co
On 5/5/19 3:59 PM, Thomas Schmitt wrote:
> It's name on hard disk was "grub.chrp".
> (Its purpose and format is beyond my knowledge.)
It's a CHRP bootscript for PowerMacs.
> If a file CD1/System/Library/CoreServices/BootX had existed on hard disk,
> the pathspec "CD1" would have overwritten the p
On 5/5/19 2:47 PM, Mark Cave-Ayland wrote:
> Ah no, that's not correct - BootX is an enhanced bootloader written by Apple
> to
> enable multi-booting with MacOS X and grub-mkrescue is assuming that it is
> being
> installed on a HD containing MacOS X with BootX in the default location.
> Whilst
On 5/5/19 16:35, Mark Cave-Ayland wrote:
On 05/05/2019 15:02, Frank Scheiner wrote:
On 5/5/19 14:47, Mark Cave-Ayland wrote:
On 05/05/2019 13:24, John Paul Adrian Glaubitz wrote:
I think the bootinfo.txt is for IBM CHRP machines while the BootX is for Macs.
Ah no, that's not correct - Bo
Hi,
Mark Cave-Ayland wrote:
> Right, these graft points are unnecessary - if you look at the BootX file on
> the ISO then it's simply a pointer to /boot/grub/powerpc-ieee1275/grub.chrp
They are copy siblings. libisofs knew that they came from the same hard
disk inode and thus decided to store the
On 05/05/2019 15:02, Frank Scheiner wrote:
> On 5/5/19 14:47, Mark Cave-Ayland wrote:
>> On 05/05/2019 13:24, John Paul Adrian Glaubitz wrote:
>>
On May 5, 2019, at 2:16 PM, Mark Cave-Ayland
wrote:
Presumably for the test ISO image you were manually copying
/System/Libra
On 05/05/2019 14:59, Thomas Schmitt wrote:
> Hi,
>
> Mark Cave-Ayland wrote:
>> Hi Adrian, [...]
>> In the last thread you listed the options as:
>
> The actually used options can be seen in a debian-cd specific data file
> of the ISO:
>
> mount debian-10.0-powerpc-grub-NETINST-1.iso /mnt/iso
On 5/5/19 14:47, Mark Cave-Ayland wrote:
On 05/05/2019 13:24, John Paul Adrian Glaubitz wrote:
On May 5, 2019, at 2:16 PM, Mark Cave-Ayland
wrote:
Presumably for the test ISO image you were manually copying
/System/Library/CoreServices/* into the image yourself? Hopefully with the above
chan
Hi,
Mark Cave-Ayland wrote:
> Hi Adrian, [...]
> In the last thread you listed the options as:
The actually used options can be seen in a debian-cd specific data file
of the ISO:
mount debian-10.0-powerpc-grub-NETINST-1.iso /mnt/iso
cat /mnt/iso/.disk/mkisofs
yields in a single line which
On 05/05/2019 13:24, John Paul Adrian Glaubitz wrote:
>> On May 5, 2019, at 2:16 PM, Mark Cave-Ayland
>> wrote:
>>
>> Presumably for the test ISO image you were manually copying
>> /System/Library/CoreServices/* into the image yourself? Hopefully with the
>> above
>> changes then you should no
> On May 5, 2019, at 2:16 PM, Mark Cave-Ayland
> wrote:
>
> Presumably for the test ISO image you were manually copying
> /System/Library/CoreServices/* into the image yourself? Hopefully with the
> above
> changes then you should no longer have to do this.
No, I used pathspecs and I create
On 04/05/2019 20:19, John Paul Adrian Glaubitz wrote:
> Hello!
>
> I just created the first test image for debian-installer which boots
> with GRUB instead of Yaboot. The image is available from the usual
> location for GRUB tests:
>
>> https://cdimage.debian.org/cdimage/ports/grub-test/
>
> Fe
> On May 5, 2019, at 8:46 AM, Frank Scheiner wrote:
>
> @Adrian:
> The `hfsprogs` package was also not included in the older ISO from
> 2019-04-20 (I only checked the ppc64 one). Should we include it, so
> off-line installations work?
Yes. I will include hfsprogs to the package list for d-i.
On 5/5/19 08:46, Frank Scheiner wrote:
@Adrian:
The `hfsprogs` package was also not included in the older ISO from
2019-04-20 (I only checked the ppc64 one). Should we include it, so
off-line installations work?
OTOH should this even work? I.e. to install a base OS from just the
netinstall ISOS?
On 5/5/19 00:27, Karl wrote:
Hope this helps
https://ibb.co/hmHrvfT
The installer can't find the `hfsprogs` package. I just checked the
Debian Ports FTP service and it's there, both for powerpc and ppc64. So
either your Internet connection was down or - if packages were installed
from the insta
On 5/5/19 6:28 AM, Rick Thomas wrote:
> The log says "grub-installer: grub-install: error: ofpathname: not found.”
Ah, right. Since the debian-installer GRUB test image doesn't contain Yaboot
anymore, Frank cannot steal of the "ofpath" utility from Yaboot and repurpose
it for GRUB.
So, we need to
On 5/5/19 12:21 AM, John Ogness wrote:
>> If the GRUB rescue image does not show this problem, then we probably know
>> why.
>
> The behavior is exactly the same for both ISOs. When I do:
>
> boot usb0/disk:,\\BootX
>
> It gives the error:
>
> DISK-LABEL: invalid partition #
>
> And I
Don’t know, if mail mail reached you …
Here is the log:
https://ibb.co/hmHrvfT
> Am 04.05.2019 um 23:43 schrieb John Paul Adrian Glaubitz
> :
>
> On 5/4/19 11:31 PM, Carlos wrote:
>> Booting with this path worked for me:
>> boot usb1/disk:,\\grub.elf
>>
>> How could I provide a log? Because I
Hope this helps
https://ibb.co/hmHrvfT
> Am 04.05.2019 um 23:43 schrieb John Paul Adrian Glaubitz
> :
>
> On 5/4/19 11:31 PM, Carlos wrote:
>> Booting with this path worked for me:
>> boot usb1/disk:,\\grub.elf
>>
>> How could I provide a log? Because I have no working OS right now.
> Switch t
On 2019-05-04, John Paul Adrian Glaubitz wrote:
>> Then I would be able to do the expected:
>>
>> boot usb0/disk:,\\BootX
>>
>> This is all probably special case iBook G4 issues. But I wanted to
>> mention it since it is pretty obvious a lot of people are tripping over
>> it.
>
> Did you see
On 5/4/19 11:31 PM, Carlos wrote:
> Booting with this path worked for me:
> boot usb1/disk:,\\grub.elf
>
> How could I provide a log? Because I have no working OS right now.
Switch to a second console with Alt+Cursor, the log file is located
in /var/log/syslog.
Adrian
--
.''`. John Paul Adria
On 5/4/19 11:16 PM, John Ogness wrote:> Then I would be able to do the expected:
>
> boot usb0/disk:,\\BootX
>
> This is all probably special case iBook G4 issues. But I wanted to
> mention it since it is pretty obvious a lot of people are tripping over
> it.
Did you see this behavior with t
Booting with this path worked for me:
boot usb1/disk:,\\grub.elf
How could I provide a log? Because I have no working OS right now.
> Am 04.05.2019 um 23:13 schrieb John Paul Adrian Glaubitz
> :
>
>> On 5/4/19 11:08 PM, Carlos wrote:
>> So, I tried to install, but failed:
>>
>> A few errors oc
On 2019-05-04, John Paul Adrian Glaubitz wrote:
> The boot script has:
>
>
> boot &device;:&partition;,\System\Library\CoreServices\grub.elf
>
I believe this boot script is causing a problem when trying to boot from
USB. Normally I would do:
boot usb0/disk:,\\BootX
Note that no partition
On 5/4/19 11:08 PM, Carlos wrote:
> So, I tried to install, but failed:
>
> A few errors occurred while installation:
> - couldn't load firmware b43, I think because that isn't on the image?
Yes, the images currently don't contain any firmware. I will work on the
firmware issues once I have commi
So, I tried to install, but failed:
A few errors occurred while installation:
- couldn't load firmware b43, I think because that isn't on the image?
- The archive security.debian.org could not be accessed
- GRUB bootloader couldn't be installed
Language was English
Keyboard was German
Installat
On 5/4/19 10:06 PM, Carlos wrote:
> Tried the GRUB image with the following path:
> boot usb1/disk@1:2,\install\vmlinux
This is the kernel image, not the GRUB image.
The boot script has:
boot &device;:&partition;,\System\Library\CoreServices\grub.elf
So, try booting \\System\Library\CoreServic
On 2019-05-04, Carlos wrote:
> Tried the GRUB image with the following path:
> boot usb1/disk@1:2,\install\vmlinux
On my iBook G4, I can boot the installer from USB with:
boot usb0/disk:,\\grub.elf
(Note that you do not specify a partition.)
John Ogness
Tried the GRUB image with the following path:
boot usb1/disk@1:2,\install\vmlinux
I guess this is wrong, because I got the message:
MAC-PARTS: specific partition is not valid can't open -> path
> Am 04.05.2019 um 21:55 schrieb John Paul Adrian Glaubitz
> :
>
>> On 5/4/19 9:52 PM, Carlos wrote:
On 5/4/19 9:52 PM, Carlos wrote:
> I will try. The last image 2019-04-20 doesn't work. Because I couldn't
> install GRUB while installation
There is a known bug when running the installer in a language other
than English. Please run the installer in English.
Adrian
--
.''`. John Paul Adrian
I will try. The last image 2019-04-20 doesn't work. Because I couldn't install
GRUB while installation
> Am 04.05.2019 um 21:19 schrieb John Paul Adrian Glaubitz
> :
>
> Hello!
>
> I just created the first test image for debian-installer which boots
> with GRUB instead of Yaboot. The image is
Hello!
I just created the first test image for debian-installer which boots
with GRUB instead of Yaboot. The image is available from the usual
location for GRUB tests:
> https://cdimage.debian.org/cdimage/ports/grub-test/
Feel free to test and report back. It boots fine on my iBook G4.
Adrian
41 matches
Mail list logo
