El mié, 31-07-2002 a las 17:31, Rolf Brudeseth escribió: > This HOWTO explains how to perform a network install of Debian 3.0 (Woody) > on an IBM RS/6000 44P-170 workstation. > [...] > Create initial ramdisk image (zImage.initrd) > ============================================ > > I just happen to have an IBM RS/6000 43P-150 workstation where I already > have SuSE 7.3 installed. I used this system to compile the zImage.initrd > image and used it as an BOOTP/tftp server. > > I got the latest kernel (2.4.18) from: > http://www.kernel.org/pub/linux/kernel/v2.4/ > > I got the ramdisk image from: > http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/root.bin > > Then I compiled the kernel: > $ mv root.bin /usr/src/linux/arch/ppc/boot/images/ramdisk.image.gz > $ cd /usr/src/linux
Well, my previous installation gots broken so I'm following another way because I don't have any machine to build a custom PPC kernel (avoiding cross-compilers). I got the images from: ftp://ftp.suse.com/pub/suse/ppc/update/BETA/kernel/power3/ exactly: zImage.chrp-power3-2.4.16-SMP-3 This image can boot on console without problems. My way on your comments: > Setting up the BOOTP/tftp server > ================================ > > After the fact, this is fairly straight forward. > > I started up the BOOTP/tftp daemons and configured the bootptab file on the > server: > $ cat /etc/bootptab > elas23:\ > ht=ethernet:\ > bf=zImage.initrd.chrp-rs6k On a DHCP server: host power3 { filename "/tftpboot/zImage.chrp-power3-2.4.16-SMP-3"; next-server nfs_server_IP; option root-path "/tftpboot/myIP"; hardware ethernet 00:11:22:33:44:55; fixed-address my.fixed.ip; } > Second, while booting the zImage.initrd image, the target system would > always hang before loading the whole file. It turns out one has to issue > the following command on the server: > $ arp -s target_ip target_hw_addr Necessary. > Booting the initial ramdisk image > ================================= > > Power on the target system. At the SMS menu, press 8 on a ascii terminal or > F8 when using graphics card, monitor, keyboard and mouse. > > You should now get to the Open Firmware prompt. I happened to use a vt102 > terminal, which explains the 'console' statement that you will see in the > remainder of this document: > > Type in the following: > 0> boot net:server_ip,,target_ip console=ttyS0,9600 > - or in my case - > 0> boot net:9.3.52.92,,9.3.52.88 console=ttyS0,9600 In my case, I booted from NFS. So: My /etc/exports looks like: /tftpboot myIP(rw,no_root_squash) The same root.bin were used: http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/root.bin but in a different way, too. $ mv root.bin root.bin.gz $ gunzip root.bin.gz $ mount -t ext2 -o loop root.bin /tftpboot/tmp $ cp -ax /tftpboot/tmp /tftpboot/myIP $ umount /tftpboot/tmp So, now it's ready to boot by network. In OpenFirmware: boot net root=/dev/nfs nfsaddrs=myIP:nfs_server_ip root-path=/tftpboot/myIP nfsroot=nfs_server_ip:/tftpboot/myIP console=ttyS0,9600 [...] IP-Config: Guessing netmask 255.255.0.0 IP-Config: Complete: device=eth0, addr=1.2.3.4, mask=255.255.0.0, gw=255.255.255.255, host=1.2.3.4, domain=, nis-domain=(none), bootserver=2.3.4.5, rootserver=2.3.4.5, rootpath= NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 100003/2 on 146.83.195.84 Looking up port of RPC 100005/1 on 146.83.195.84 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 292k init 40k pmac 8k prep serial console detected. Disabling virtual terminals. init started: BusyBox v0.60.3-pre (2002.01.19-22:40+0000) multi-call binary [...] Debian installer starts... :-) Well, now it's complaining about "root fs", but I'll repartition the disks first ;-) -- German Poo Caaman~o mailto:[EMAIL PROTECTED] http://www.ubiobio.cl/~gpoo/chilelindo.html «Hay 10 tipos de personas: las que entienden binario y las que no.»
