Handbook:MIPS/Blocks/HWReqs/ko

젠투 위치에 있는 MIPS 하드웨어 요구사항en 도 확인하십시오.

설치 참고
On many architectures, the processor has gone through several generations, each newer generation builds on the foundation of the previous one. MIPS is no exception. There are several generations of CPU covered under the MIPS architecture. In order to choose the right netboot image stage tarball and CFLAGS appropriately, it is necessary to be aware of which family the system's CPU belongs in. These families are referred to as the Instruction Set Architecture.

Also, another important concept to grasp is the concept of endianness. Endianness refers to the way that a CPU reads words from main memory. A word can be read as either big endian (most significant byte first), or little endian (least significant byte first). Intel x86 machines are generally Little endian, whilst Apple and Sparc machines are Big Endian. On MIPS, they can be either. To separate them apart, we append el to the architecture name to denote little endian.

For those willing to learn more about ISAs, the following websites may be of assistance.
 * Linux/MIPS Website: MIPS ISA
 * Linux/MIPS Website: Endianness
 * Linux/MIPS Website: Processors
 * Wikipedia: Instruction Set

Netbooting 간단히 살펴보기
이 절에서는, 실리콘 그래픽스 워크스테이션 또는 코발트 서버 제품에서 성공적으로 네트워크 부팅을 수행하는데 필요한 내용을 다루겠습니다. 간단한 정리 안내서이며 완벽을 의도하지 않았으므로, 더 많은 내용은 무(無)디스크 노드 설명서를 읽어보십시오.

Depending on the machine, there is a certain amount of hardware that is needed in order to successfully netboot and install Linux.


 * In General:
 * DHCP/BOAMD Alchemy series, 4kc, 4km, many others... There are a few revisions in the MIPS32 ISA.OTP server (ISC DHCPd recommended)
 * Patience -- and lots of it
 * For Silicon Graphics workstations:
 * TFTP server (tftp-hpa recommended)
 * When the serial console needs to be used:
 * MiniDIN8 --> RS-232 serial cable (only needed for IP22 and IP28 systems)
 * Null-modem cable
 * VT100 or ANSI compatible terminal capable of 9600 baud
 * For Cobalt Servers (NOT the original Qube):
 * NFS server
 * Null-modem cable
 * VT100 or ANSI compatible terminal capable of 115200 baud

TFTP와 DHCP 설정
As mentioned earlier -- this is not a complete guide, this is a bare-bones config that will just get things rolling. Either use this when starting a setup from scratch, or use the suggestions to amend an existing setup to support netbooting.

It is worth noting that the servers used need not be running Gentoo Linux, they could very well be using FreeBSD or any Unix-like platform. However, this guide will assume to be using Gentoo Linux. If desired, it is also possible to run TFTP/NFS on a separate machine to the DHCP server.

First Step -- configuring DHCP. In order for the ISC DHCP daemon to respond to BOOTP requests (as required by the SGI & Cobalt BOOTROM) first enable dynamic BOOTP on the address range in use; then set up an entry for each client with pointers to the boot image.

설치가 끝나면 를 만드십시오. 시작할 때 기본 구성으로 사용할 설정은 아래와 같습니다.

위 설정을 통해 subnet 절에서 여러대의 클라이언트를 추가할 수 있습니다. 어떤 클라이언트를 설정할지는 이 안내서의 뒷부분에서 다룹니다.

그 다음 단계. TFTP 서버를 설정하십시오. 잘 동작한다고 알려진 tftp-hpa를 TFTP 데몬으로 쓰는것이 좋습니다. 다음과 같이 설치를 계속 진행하십시오.

이 과정을 통해 넷부트 이미지를 저장할 를 만듭니다. 필요한 경우 다른 곳으로 옮기십시오. 이 안내서의 목적에 따르면 기본 위치를 그대로 둡니다.

netboot 이미지 다운로드
설치하려는 시스템에 따라, 다운로드할 수 있는 몇가지 이미지가 있습니다. 컴파일 하려는 시스템 형식과 CPU에 따라 이름이 붙어있습니다. 해당 머신 형식은 아래와 같습니다:

파일이름에서도 r4k는 R4000 프로세서 기종을 참조하며, r5k는 R5000계열 프로세서를, rm5k는 RM5200계열 프로세서를, r10k는 R10000계열 프로세서를 참조합니다. 이미지는 젠투 미러에 있습니다.

SGI 클라이언트 DHCP 설정
파일을 다운로드하고 나면 디렉터리에 압축해제한 이미지 파일을 넣으십시오(bzip2 -d 명령 사용). 그 다음 파일을 편집하여 SGI 클라이언트에 맞게 적당한 항목을 추가하십시오.

커널 옵션
We're almost done, but there's a couple of little tweaks still to be done. Pull up a console with root privileges.

Disable "Path Maximum Transfer Unit", otherwise SGI Prom won't find the kernel:

Set the port range usable by the SGI PROM:

This should be sufficient to allow the Linux server to play nice with SGI's PROM.

데몬 시작
이제 데몬을 시작하십시오.

If nothing went wrong in that last step then everything is all set to power on the workstation and proceed with the guide. If the DHCP server isn't firing up for whatever reason, try running 'dhcpd' on the command line and see what it says -- if all is well, it should just fork into the background, otherwise it will display 'exiting.' just below its complaint.

An easy way to verify if the tftp daemon is running is to type the following command and confirm the output:

SGI 스테이션 넷부팅
Okay, everything is set, DHCP is running as is TFTP. Now it is time to fire up the SGI machine. Power the unit on -- when "Running power-on diagnostics" comes on the screen, either click "Stop For Maintenance" or press. A menu similar to the following will show up.

Diagnostic menu

Type in to enter the command monitor. On the monitor, start the BootP process:

From this point, the machine should start downloading the image, then, roughly 20 seconds later, start booting Linux. If all is well, a busybox ash shell will be started as shown below and the installation of Gentoo Linux can continue.

제대로 진행한다면...

문제 해결
If the machine is being stubborn and refusing to download its image, it can be one of two things,
 * 1) the instructions were not followed correctly, or
 * 2) it needs a little gentle persuasion (No, put that sledge hammer down!)

Here's a list of things to check:
 * dhcpd is giving the SGI Machine an IP Address. There should be some messages about a BOOTP request in the system logs. tcpdump is also useful here.
 * Permissions are set properly in the tftp folder (typically -- should be world readable)
 * Check system logs to see what the tftp server is reporting (errors perhaps)

If everything on the server is checked, and timeouts or other errors occur on the SGI machine, try typing this into the console.

netboot 진행과정 간단히 살펴보기
Unlike the SGI machines, Cobalt servers use NFS to transfer their kernel for booting. Boot the machine by holding down the left & right arrow buttons whilst powering the unit on. The machine will then attempt to obtain an IP number via BOOTP, mount the directory from the server via NFS, then try to download and boot the file vmlinux_raq-2800.gz (depending on the model) which it assumes to be a standard ELF binary.

Cobalt netbook 이미지 다운로드
Inside http://distfiles.gentoo.org/experimental/mips/historical/netboot/cobalt/ the necessary boot images for getting a Cobalt up and running are made available. The files will have the name nfsroot-KERNEL-COLO-DATE-cobalt.tar -- select the most recent one and unpack it to / as shown below:

NFS 서버 설정
Since this machine uses NFS to download its image, it is necessary to export on the server. Install the package:

Once that is done, place the following in the file.

Now, once that is done, start the NFS server:

If the NFS server was already running at the time, tell it to take another look at its exports file using exportfs.

Cobalt 머신 DHCP 설정
Now, the DHCP side of things is relatively straightforward. Add the following to the file.

데몬 시작
이제 데몬을 시작하십시오. 다음 명령을 입력하십시오:

If nothing went wrong in that last step all should be set to power on the workstation and proceed with the guide. If the DHCP server isn't firing up for whatever reason, try running 'dhcpd' on the command line and see what it tells -- if all is well, it should just fork into the background, otherwise it will show 'exiting.' just below its complaint.

Cobalt 머신 넷부팅
Now it is time to fire up the Cobalt machine. Hook up the null modem cable, and set the serial terminal to use 115200 baud, 8 bits, no parity, 1 stop bit, VT100 emulation. Once that is done, hold down the left & right arrow buttons whilst powering the unit on.

The back panel should display "Net Booting", and some network activity should be visible, closely followed by CoLo kicking in. On the rear panel, scroll down the menu until the "Network (NFS)" option then press. Notice that the machine starts booting on the serial console.

Booting the kernel

A busybox ash shell will pop up as shown below, from which the Gentoo Linux installation can continue.

제대로 진행한다면...

문제 해결
If the machine is being stubborn and refusing to download its image, it can be one of two things,
 * 1) the instructions have not been followed correctly, or
 * 2) it needs a little gentle persuasion. (No, put that sledge hammer down!)

Here's a list of things to check:
 * dhcpd is giving the Cobalt Machine an IP Address. Notice messages about a BOOTP request in the system logs. tcpdump is also useful here.
 * Permissions are set properly in the folder. (should be world readable)
 * Make sure the NFS server is running and exporting the directory. Check this using   on the server.