Handbook:MIPS/Blocks/HWReqs/pt-br

Também cheque os Requirimentos de Hardware do MIPS

Notas de instalação
Em muitas arquiteturas, o processador passou por várias gerações, cada geração baseada nos fundamentos da anterior. O MIPS não é exceção. Há várias gerações de CPU sob a arquitetura MIPS. De modo a escolher o arquivo tar de stage com a imagem de netboot apropriada é necessário conhecer a qual família a CPU do sistema pertence. Essas famílias são chamadas de Conjunto de Instruções da Arquitetura ("Instruction Set Architecture" -- ISA).

Também, outro conceito importante a ser digerido é o conceito de "endian". Endian refere-se ao modo em que a CPU lê palavras da memória principal. Uma palavra pode ser lida como ou "big endian" (byte mais significativo primeiro), ou "little endian" (byte menos significativo primeiro). Máquinas Intel x86 são geralmente little endian, enquanto máquinas Apple e Sparc são big endian. No MIPS, podem ser ambos. Para separá-las, acrescentamos "el" ao nome da arquitetura para denotar little endian.

Aqueles que quiserem aprender mais sobre ISAs, os sites abaixo podem ser úteis:


 * Linux/MIPS Website: MIPS ISA
 * Linux/MIPS Website: Endianness
 * Linux/MIPS Website: Processors
 * Wikipedia: Instruction Set

Visão geral de boot pela rede
Neste seção mostraremos o que é necessário para fazer boot pela rede de uma estação de trabalho Silicon Graphics ou de um dispositivo Cobalt Server. Este é apenas um guia rápido, não sendo feito para ser extensivo. Para mais informação, é recomendada a leitura do artigo Nós sem disco.

Dependendo da máquina, há uma certa quantidade de hardware necessária para fazer boot pela rede e instalar o Linux nela com sucesso.


 * Em geral:
 * DHCP/BOAMD Série Alchemy, 4kc, 4km, várias outras... Há algumas revisões na ISA MIPS32. Servidor OTP (recomendado o ISC DHCPd)
 * Paciência -- muita
 * Para estações de trabalho Silicon Graphics:
 * Servidor TFTP (recomendado o tftp-hpa)
 * Se for necessário usar o console serial:
 * Cabo serial MiniDIN8 --> RS-232 (necessário apenas para sistemas IP22 e IP28)
 * Cabo Null-modem
 * Terminal compatível VT100 ou ANSI capaz de operar a 9600 bauds
 * Para Cobalt Servers (NÃO o Qube original):
 * Servidor NFS
 * Cabo Null-modem
 * Terminal compatível VT100 ou ANSI capaz de operar a 115200 bauds

Configurando TFTP e DHCP
Como mencionado anteriormente, este não é um guia completo, mas apenas uma configuração básica para que as coisas funcionem. Use este guia quando estiver instalando do zero ou use como sugestões adicionais a uma configuração que suporte boot pela rede.

Vale a pena notar que os servidores usados não precisam estar rodando o Gentoo Linux, eles podem muito bem estar usando FreeBSD ou qualquer outra plataforma do tipo Unix. Entretanto, este guia assume que está sendo usado o Gentoo Linux. Se desejado, é também possível usar TFTP/NFS em uma máquina separada do servidor DHCP.

Primeiro Passo -- configurar o DHCP. De modo ao servidor ISC DHCP responder às solicitações de requisição BOOTP (necessário pela SGI & Cobalt BOOTROM) primeiro habilite o BOOTP dinâmico na faixa de endereços em uso; depois configure uma entrada para cada cliente apontando para a imagem de boot.

Uma vez instalado, crie o arquivo. Aqui está uma configuração básica para servir de início.

With that setup, one can then add any number of clients within the subnet clause. We will cover what to put in later in this guide.

Next step - Setting up TFTP server. It is recommended to use tftp-hpa as it is the only TFTP daemon known to work correctly. Proceed by installing it as shown below:

This will create to store the netboot images. Move this elsewhere if necessary. For the purposes of this guide, it is assumed that it is kept in the default location.

Downloading a netboot image
Depending on the system the installation is meant for, there are several possible images available for download. These are all labelled according to the system type and CPU they are compiled for. The machine types are as follows:

Also in the filename, r4k refers to R4000-series processors, r5k for R5000, rm5k for the RM5200 and r10k for R10000. The images are available on the Gentoo mirrors.

DHCP configuration for an SGI client
After downloading the file, place the decompressed image file in the directory. (Use bzip2 -d to decompress) Then edit the file and add the appropriate entry for the SGI client.

Kernel options
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.

Starting the daemons
At this point, start the daemons.

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 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:

Netbooting the SGI station
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.

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.

Troubleshooting
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. 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.

Overview of the netboot procedure
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  (depending on the model) which it assumes to be a standard ELF binary.

Downloading a Cobalt netboot image
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 server configuration
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.

DHCP configuration for a Cobalt machine
Now, the DHCP side of things is relatively straightforward. Add the following to the file.

Starting daemons
Now start the daemons. Enter the following:

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 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.

Netbooting the Cobalt machine
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 and 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.

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

Troubleshooting
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. 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.