[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: howto netboot powerpc



On Fri, Jan 14, 2005 at 01:58:05PM -0500, Joey Hess wrote:
> Sven Luther wrote:
> > On which kind of powerpc ? It is different on each one, but i will try to
> > contribute some stuff for the pegasos case which is of interest to you i
> > think.
> 
> I'm specifically trying to get pegasos to work, but generally interested
> in making sure that most or all powerpc users have the info in the
> manual or a pointer to a place that it is documented.

I just broke my NewWorld mac laptop and had to netboot it to get it to
work again. So it's still fresh in my memory ;-)

What you need is indeed yaboot in a tftp area. I ran 

dpkg -x yaboot_1.3.13-3_powerpc.deb .

and copied usr/lib/yaboot/yaboot to /tftpboot, together with the vmlinux
and the initrd.gz that I copied from an archive mirror. Then, I created
a /tftpboot/yaboot.conf that looks like this (information extracted from
the list archives, but slightly modified to make it work in my case): 

timeout=100
device=enet:
partition=0
init-message="Debian GNU/Linux Network boot for Debian-Installer (Sarge)"
default=vmlinux
label=vmlinux
image=vmlinux
initrd=initrd.gz
append="devfs=mount,dall init=/linuxrc --"
initrd-size=10240

Now, you need to set up a DHCP server. Nothing special there; making
sure next-server is set as usual and that filename contains "yaboot"
should do it. If it doesn't, it's still possible to boot in a more
explicit way (see below)

Next, boot the Mac and make sure you get an OpenFirmware prompt (hold
Command+Option+O+F during boot). At the OpenFirmware prompt, enter

boot enet:

or, if that doesn't work, the more explicit way:

boot enet:<server's IP>,yaboot

e.g.,

boot enet:192.168.0.1,yaboot

Now, all one needs to do is sit back and relax while the system boots
:-)

-- 
         EARTH
     smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
         WATER
 -- with thanks to fortune

Attachment: signature.asc
Description: Digital signature


Reply to: