Re: d-i: 4.3. Preparing Files for USB Memory Stick Booting
On Tue, Apr 19, 2016 at 6:53 PM, Lennart Sorensen
> On Tue, Apr 19, 2016 at 12:16:27PM +0200, Mathieu Malaterre wrote:
>> Does anyone knows what happen to section:
>> 4.3. Preparing Files for USB Memory Stick Booting
>> in the powerpc install guide ?
>> I see it alright from here:
> Well that's x86_64 so totally different thing.
>> but not from here:
>> AFAIK USB booting works from powerpc system (at least some that I tried).
>> Also I see reference to powerpc in the raw XML file:
>> Comments ?
> You could try to follow the older instructions and it might work:
> Section 5.1.3 says newworld mac booting from USB. It has to be done
> manually from openfirmware though, so it is probably the most complicated
> boot method there is.
> It also had a warning that it might not work. Maybe it was removed from
> newer release's documentation for a reason.
That was precisely my point: why did it got removed ? And if so why is
the upstream (raw) XML still referencing the USB boot mechanism for
> The instructions from Ubuntu might work too:
Neat it contains some more extra information I was not aware, thanks !
I did follow:
and it works for me, on a Mac Mini G4 (PPC).
# wget http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.4.0/powerpc/iso-cd/firmware-8.4.0-powerpc-netinst.iso
# wget http://ftp.nl.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/hd-media/boot.img.gz
# zcat boot.img.gz > /dev/sdb
[manually eject + plug USB drive again]
# cp firmware-8.4.0-powerpc-netinst.iso /media/mathieu/bootable
[reboot + press and hold cmd/option/o/f]
> boot usb1/disk@1:2,\\yaboot
[some silly warning that partition cannot be read]
The only tricky part was that the name
'firmware-8.4.0-powerpc-netinst.iso' is a bit too long for HFS (AFAIK)
and the file extension was *.si instead of *.iso which is an issue for
the debian installer (hence the need for a shorter name on the USB
I'll make an installation-reports bug report for stretch and ask for
the documentation clarification from there.