Escolar Documentos
Profissional Documentos
Cultura Documentos
[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index] Report as spam
This HOWTO explains how to perform a network install of Debian 3.0 (Woody)
on an IBM RS/6000 44P-170 workstation.
It should definitely also work for other low-end systems such as the 260,
270 and B80. However, I have not yet tested that. I would also expect it to
work on the mid- and high-end POWER3 systems.
You would use the same approach for 604 based CHRP systems like the 43P-150
and B50; however, you would use a different kernel.
I will work on this document some more and find a URL for it.
Rolf
--
Rolf Brudeseth
rolfb@us.ibm.com
pSeries System Engineering & Integration, IBM Enterprise Systems Group
Austin, TX
I would have saved a few key strokes during the install if I had modified
the config file to enable serial port console.
It appears that it is enabled in the config file:
~snip
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
~snip
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
Then, some issues that I noticed later, that we may as well take care of
now.
First, note that the 'bf' flag only equals the image. It turn out that
unlike other BOOTP servers I have used, the one SuSE offers assumes that
the path is with respect to /tftpboot, and not /.
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
We are now done with the server. The remainder of tasks are performed on
the target.
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:
The boot-loader 'yaboot' will later be loaded into 'sda1'. Make sure this
partition is not larger than 8-10M. Due to a bug (I am not sure where) the
boot-loader will not function well if the partition gets much larger than
this.
This is where you normally would select the following option in the
installer:
- Install Kernel and Driver Modules
However, since I know that the FTP/HTTP method will fail, I am going to the
shell instead.
In boot-floppies, I select:
- Execute a Shell
If you issue the 'df' command, you will see that '/dev/sda3' is mounted
under '/target'. If not, simply issue the command:
# cd /target
# wget
http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/drivers.tgz
# tar -zxvf drivers.tgz
# ./install.sh
Install Base
============
# wget
http://ftp.debian.org/debian/dists/woody/main/disks-powerpc/base-images-current/basedebs.tar
# exit
https://lists.debian.org/debian-powerpc/2002/07/msg00858.html 3/5
7/24/2017 Debian network installation on IBM RS/6000 44P-170 (POWER3) - HOWTO
Install kernel
==============
I get the uncompressed kernel from the system where I compiled the kernel:
/usr/src/linux/vmlinux
In boot-floppies, I select:
- Execute a Shell
# cd /target/boot
# wget ftp://user:password@host/usr/src/linux/vmlinux
Well, I can boot from the network again. However, this time I boot the
image with the 'noinitrd' and 'root' kernel parameters specified.
When the system comes up to the SMS menu I again hit 8 or F8, but issue the
following command at the Open Firmware prompt:
Now the system boots up and indicates that the installation is done, and
starts running through the configuration menu.
The reason for this is that the screen emulation is not working correctly
with these menus (at least not for me and my vt102 terminal). Make sure to
press the backspace/delete button a few times in each field. Otherwise, you
will get to the login prompt but not be able to log in, because the root
password will not be what you typed in.
For the same reason I would wait with running 'apt-sel' and 'dselect'.
https://lists.debian.org/debian-powerpc/2002/07/msg00858.html 4/5
7/24/2017 Debian network installation on IBM RS/6000 44P-170 (POWER3) - HOWTO
For the same reason I would wait with running 'apt-sel' and 'dselect'.
However, if this happens, you can still recover. Power the system down by
pressing the power button. Boot up the initrd image, mount '/target' and
edit the '/target/etc/passwd' or '/target/etc/shadow' files with the
'nano-tiny' editor, depending upon whether you enabled shadow passwords or
not. Remove the password field. Then reboot and boot up again with the
'noinitrd' and 'root' kernel parameters specified.
You should now be able to log into the system and run dpkg, apt or dselect,
whichever is your preference.
You may also want to reboot the system and press 1 or F1 at the SMS menu,
and ensure that the hard drive where you just installed Debian is on the
list of boot devices.
Good luck!
Reply to:
debian-powerpc@lists.debian.org
Rolf Brudeseth (on-list)
Rolf Brudeseth (off-list)
Follow-Ups:
Re: Debian network installation on IBM RS/6000 44P-170 (POWER3) - HOWTO
From: Steve Gore <sgore@debian.org>
https://lists.debian.org/debian-powerpc/2002/07/msg00858.html 5/5