[EMAIL PROTECTED] wrote:

> Something went wrong here, I managed to get yaboot loaded as usual,
> but when the kernel was being transfered it just hanged. I tried
> 3 times and it always hanged at the same packet. That's when I sat
> down to write this mail about how I got netbooting working, and
> failed to transfer the kernel sarge uses for netinstall.

Funny... I just worked this week on exactly the same thing.

I did get dhcpd.conf (DHCP v3) configured (w/o patching, just examining the patch and using available docs and the site-option-space, similar to somehting I needed for booting using Intel PXE), but eventually ran into the exact same problem; it just did not want to load the kernel from the TFPTd server.

Until I found this:

http://lists.penguinppc.org/yaboot-users/2003/yaboot-users-200307/msg00017.html

Then it hit me that we do not have to wait for yaboot 2 to be released, but that it might very well be possible to patch yaboot to allow for bigger kernels:

--- yaboot-1.3.11/second/fs_of.c        2002-09-15 05:12:33.000000000 +0200
+++ yaboot-1.3.11.new/second/fs_of.c    2004-04-15 11:41:11.000000000 +0200
@@ -44,7 +44,7 @@
 #include "debug.h"

 #define LOAD_BUFFER_POS                0x600000
-#define LOAD_BUFFER_SIZE       0x400000
+#define LOAD_BUFFER_SIZE       0x600000

 static int of_open(struct boot_file_t* file, const char* dev_name,
                   struct partition_t* part, const char* file_name);

Lo, and behold, this makes the system boot the debian-installer kernel :)

No more in vain CD burning ... now I just boot debian-installer from a secondary (builder) machine, which has the latest nightly available automatically:

device=enet:<secondary ip address>
partition=0
timeout=100
init-message="Debian GNU/Linux Network boot"
default=install

image=vmlinux
    initrd=initrd.gz
    label=install
    initrd-size=8192
    append="init=/linuxrc"
    read-only

Regards,

Pepijn.

P.S.

I also tried starting installation from a USB key, and although it seems (after device investigations through OpenFirmware) that it does start yaboot, the end result is just a black screen and endless activity on the stick. I tried this both with a 'virgin' VFAT system (factory default) and with a HFS partition on the stick. However, no luck.


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to