Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Lennart Sorensen]

On Thu, Oct 25, 2012 at 02:36:48PM -0700, Patrick Fitzmorris wrote:
> Oh!
> 
> That worked perfectly, thank you.
> 
> Is the changelog in question viewable somewhere?
> the one I was referring to, bundled into the tarball for 1.3.17 from
> yaboot.ozlabs.org, doesn't go past 1.3.13. All the info I had on more
> recent versions came from the project homepage, which as you can probably
> see, is pretty sparse.

The one I found mentioned 1.3.14, but nothing since.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121025214807.gu18...@csclub.uwaterloo.ca

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Patrick Fitzmorris]

Oh!

That worked perfectly, thank you.

Is the changelog in question viewable somewhere?
the one I was referring to, bundled into the tarball for 1.3.17 from
yaboot.ozlabs.org, doesn't go past 1.3.13. All the info I had on more
recent versions came from the project homepage, which as you can probably
see, is pretty sparse.

Thanks again. I was really not looking forward to fiddling with it much
more.
On Thu, Oct 25, 2012 at 12:09 PM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:

> On Thu, Oct 25, 2012 at 11:39:22AM -0700, Patrick Fitzmorris wrote:
> > Attempting to boot a Powerbook over the network has been a frustrating
> > endeavor. I did it once in the past with this machine, installing
> > Lenny. It seems little has changed, except that now it doesn't work.
> > Here's a snippet of output:
> >
> > Welcome to yaboot version 1.3.13
> > Enter "help" to get some basic usage information
> > boot: install
> > Please wait, loading kernel...
> >
> > CLIENT: [mac address] [IP]
> > SERVER: [mac address] [IP] [Hostname]
> > Transfer FILE: vmlinux [it pauses here for a little bit] method 'load'
> > failed 0300
> >
> > Can't read Elf e_ident/e_type/e_machine info
> > boot:
> >
> >
> > Looking through the mailing list archives, it looks like the problem
> > is that the kernel image is too large, at 6.7 MB, for yaboot to
> > successfully load it. (does anyone test the functionality of the ppc
> > netboot images anymore?)
> >
> > Is there any way to cut it down to 6 MB or less? Perhaps by using an
> > older kernel, or excluding some of the fancier features? My research
> > indicates that 6 MB's as large as yaboot 1.x.x will go.
> >
> > Additionally, yaboot 1.1.13 is more than eight years old now. 1.1.17
> > is out and has been since last october, and includes, among other
> > things, improved netboot functionality, with IPv6 support and such. (i
> > suspect they'll be releasing 1.1.18 in the near future, since the
> > release schedule looks to be once a year or so) I think it's still
> > limited to 6 MB max kernel size.
>
> That would be sad.
>
> > Until it's been fixed, can you give me some tips? like, can I replace
> > the vmlinux image and initrd image, without having to assemble a
> > custom mini.iso? where should I look for info on the recommended
> > procedure? my google work hasn't been very fruitful so far, so i
> > though I'd ask the experts.
>
> wheezy has a newer yaboot version.  Maybe it would work.  Could try and
> see if it boots or not.  Would be a clue at least.
>
> Changing the kernel would require a custom iso since the modules have
> to match the kernel.
>
> The yaboot in wheezy (1.1.16) has a changelog entry that mentions fixing
> support for kernel+initrd that uncompressed is bigger than 12MB.  That is
> probably the issue you are hitting.  1.3.16 should have at least 20MB
> now for the uncompressed kernel+initrd, and on some systems even more
> than that.
>
> --
> Len Sorensen
>

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Patrick Fitzmorris]

Oh, well.
I used the bootpd and tftpd that ship with OS X10.5 (not the server
edition). If you want to do the same,  then do this:

Tweak /etc/bootpd.plist* to disable all dhcp features, since your home
network probably already has a DHCP server, and Open Firmware only does
bootp, prior to version 3.

Put an entry in  /etc/bootptab* for the target system, giving it the same
IP the DHCP server gives it when it's fully booted into an OS, [and putting
in "yaboot" for the bootfile. (this doesn't actually work)]**

Enable the daemons with launchd, like this:
sudo launchctl load -F /System/Library/LaunchDaemons/tftpd.plist
sudo launchctl load -F /System/Library/LaunchDaemons/bootps.plist
(the -F is to override the "Disabled" string in the plists, which prevents
them from coming up on [re]boot)

Copy all the files from the mirror to /private/tftpboot/

Bring the target system up in Open Firmware, type in: boot enet:0,yaboot
[if the bootfile entry had worked, then you could, theoretically, just hold
the N key down, instead of invoking Open Firmware]

Install! Or do a dry run, i guess.

*The OS X bootpd does not use the same syntax! see:
bootpd(8)
bootptab(5)

**for reasons which I cannot fathom, OS X's bootpd prepends
"/private/tftpboot/" on the bootfile path it sends to the target system,
unless the bootfile path in the bootptab is already an absolute path. For
reasons which I cannot fathom, the tftpd throws an error code 2 if you try
to fetch files by anything other than a path relative to /private/tftpboot,
with NO leading / allowed. This means that using the Netboot hotkey on the
target system won't work, you must use the Open Firmware prompt


OR, you could just install a tftpd and bootpd on your Linux box, configure
more or less the same, copy the files to the correct dir, and bring up the
target in Open Firmware. booting with the same command (you can probably
omit the ",yaboot" in this case)

On Thu, Oct 25, 2012 at 12:41 PM, Rick Thomas  wrote:

>
> On Oct 25, 2012, at 11:39 AM, Patrick Fitzmorris wrote:
>
>  (does anyone test the functionality of the ppc
>> netboot images anymore?)
>>
>
> Well, I try...  I have a number of old PowerPC Macs that I keep just for
> the purpose.  I haven't tried network booting yet.  Can you give me some
> pointers on how it's done?
>
> Thanks!
>
> Rick
>
>

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Rick Thomas]

On Oct 25, 2012, at 11:39 AM, Patrick Fitzmorris wrote:


(does anyone test the functionality of the ppc
netboot images anymore?)


Well, I try...  I have a number of old PowerPC Macs that I keep just  
for the purpose.  I haven't tried network booting yet.  Can you give  
me some pointers on how it's done?


Thanks!

Rick


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/9d3657d5-6abc-4e46-b21c-584acede8...@pobox.com

Re: PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Lennart Sorensen]

On Thu, Oct 25, 2012 at 11:39:22AM -0700, Patrick Fitzmorris wrote:
> Attempting to boot a Powerbook over the network has been a frustrating
> endeavor. I did it once in the past with this machine, installing
> Lenny. It seems little has changed, except that now it doesn't work.
> Here's a snippet of output:
> 
> Welcome to yaboot version 1.3.13
> Enter "help" to get some basic usage information
> boot: install
> Please wait, loading kernel...
> 
> CLIENT: [mac address] [IP]
> SERVER: [mac address] [IP] [Hostname]
> Transfer FILE: vmlinux [it pauses here for a little bit] method 'load'
> failed 0300
> 
> Can't read Elf e_ident/e_type/e_machine info
> boot:
> 
> 
> Looking through the mailing list archives, it looks like the problem
> is that the kernel image is too large, at 6.7 MB, for yaboot to
> successfully load it. (does anyone test the functionality of the ppc
> netboot images anymore?)
> 
> Is there any way to cut it down to 6 MB or less? Perhaps by using an
> older kernel, or excluding some of the fancier features? My research
> indicates that 6 MB's as large as yaboot 1.x.x will go.
> 
> Additionally, yaboot 1.1.13 is more than eight years old now. 1.1.17
> is out and has been since last october, and includes, among other
> things, improved netboot functionality, with IPv6 support and such. (i
> suspect they'll be releasing 1.1.18 in the near future, since the
> release schedule looks to be once a year or so) I think it's still
> limited to 6 MB max kernel size.

That would be sad.

> Until it's been fixed, can you give me some tips? like, can I replace
> the vmlinux image and initrd image, without having to assemble a
> custom mini.iso? where should I look for info on the recommended
> procedure? my google work hasn't been very fruitful so far, so i
> though I'd ask the experts.

wheezy has a newer yaboot version.  Maybe it would work.  Could try and
see if it boots or not.  Would be a clue at least.

Changing the kernel would require a custom iso since the modules have
to match the kernel.

The yaboot in wheezy (1.1.16) has a changelog entry that mentions fixing
support for kernel+initrd that uncompressed is bigger than 12MB.  That is
probably the issue you are hitting.  1.3.16 should have at least 20MB
now for the uncompressed kernel+initrd, and on some systems even more
than that.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121025190949.gt18...@csclub.uwaterloo.ca

PowerPC bootp+tftp Network Boot: "method 'load' failed 00000300, newer yaboot version, alternate kernel images

[Patrick Fitzmorris]

Attempting to boot a Powerbook over the network has been a frustrating
endeavor. I did it once in the past with this machine, installing
Lenny. It seems little has changed, except that now it doesn't work.
Here's a snippet of output:

Welcome to yaboot version 1.3.13
Enter "help" to get some basic usage information
boot: install
Please wait, loading kernel...

CLIENT: [mac address] [IP]
SERVER: [mac address] [IP] [Hostname]
Transfer FILE: vmlinux [it pauses here for a little bit] method 'load'
failed 0300

Can't read Elf e_ident/e_type/e_machine info
boot:


Looking through the mailing list archives, it looks like the problem
is that the kernel image is too large, at 6.7 MB, for yaboot to
successfully load it. (does anyone test the functionality of the ppc
netboot images anymore?)

Is there any way to cut it down to 6 MB or less? Perhaps by using an
older kernel, or excluding some of the fancier features? My research
indicates that 6 MB's as large as yaboot 1.x.x will go.

Additionally, yaboot 1.1.13 is more than eight years old now. 1.1.17
is out and has been since last october, and includes, among other
things, improved netboot functionality, with IPv6 support and such. (i
suspect they'll be releasing 1.1.18 in the near future, since the
release schedule looks to be once a year or so) I think it's still
limited to 6 MB max kernel size.

Until it's been fixed, can you give me some tips? like, can I replace
the vmlinux image and initrd image, without having to assemble a
custom mini.iso? where should I look for info on the recommended
procedure? my google work hasn't been very fruitful so far, so i
though I'd ask the experts.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cafpxt5+amq51bzyeo1oqxn5mdhqgs5fwahkddmnuattvsac...@mail.gmail.com