MIPS/FAQ/ja

このよくある質問集は、Gentoo/MIPS と Linux/MIPS 一般に関わるとりわけよくある質問の一部に回答しています.

はじめに
This FAQ is intended to answer frequently asked questions about Gentoo/MIPS and Linux/MIPS that we receive from various users. It's aimed at both new users and experienced users alike. It has been split into a number of categories to make navigation easier.

If you'd like to contribute to the FAQ or, having read this guide, you still have questions that are left unanswered, feel free to drop us a line.

Gentoo/MIPS とは何ですか?
Gentoo/MIPS is a small project responsible for looking after the MIPS port of Gentoo Linux.

なぜ MIPS に Gentoo Linux をインストールするのでしょうか?
Okay, sure, some MIPS machines aren't the fastest boxes on the block these days. However, despite the age of some of these beasts, they still can make very functional, useful machines. A Cobalt Qube 2 could make a very nice broadband Internet router, capable of hosting websites, email, IRC and numerous other tasks. There are a number of reasons why you'd want to install Linux on this sort of hardware.


 * It teaches you a lot about computer hardware by giving you an alternate frame of reference


 * It allows you to turn what would otherwise be useless junk into a very functional system


 * Status Symbol: Linux on x86 is so common these days it's not funny. However, Linux on MIPS is a lot less common and quite a talking point.

なぜ Gentoo を NetBSD/MIPS や IRIX に移植しないのですか?
Hey, great idea. Unfortunately, a lot of the Gentoo/MIPS team already have their hands full looking after Linux/MIPS as well as other commitments. A project like this would fall under the umbrella of the Gentoo Prefix project. Some work has been done for IRIX, the remnants of which can be found in bugzilla.

MIPS とは何ですか?
MIPS Technologies is a company that produce a number of RISC CPU cores which implement theMIPS Architecture. These processors appear in all sorts of hardware ranging from small embedded devices to large servers.

It also happens to be an acronym; M illions of I nstructions P er S econd.

What sort of hardware uses MIPS processors?
In short... lots. MIPS Processors see use inside all sorts of machines, ranging from small PDAs (such as the early Windows CE powered Casio PDAs), X Terminals (e.g. Tektronix TekXPress XP330 series), through to workstations such as the Silicon Graphics Indy and O2 and even high end servers such as the Silicon Graphics Origin 2000.

A comprehensive list can be found on the Linux/MIPS website

... and that's only scratching the surface. These machines are wide and varied. Many of them do not currently run Linux. Of those that do, we only support a handful, although you're welcome to port Gentoo/MIPS to any MIPS machine if you so wish. Some of these machines are also the focus of the Embedded Gentoo Project such as the Linksys WRT54G.

私のマシンはサポートされていますか?
For the first one an easy way to find out is to have a look at the Gentoo/MIPS requirements page. This will tell you if the system you've got can theoretically run Gentoo/MIPS.

If you don't find your machine listed there, you may wish to have a look on the Linux/MIPS website to find it there. Installation won't be straightforward however, as the actual process of producing a kernel and suitable boot media for your hardware will have to be done largely by yourself. Naturally though, we'll try to help where we can.

Why don't you support machine X
If you've looked at the Gentoo/MIPS Hardware Requirements page, you've probably noticed there are a lot of machines we don't support. In the case of SGI hardware, very little is known about some of them, not enough to successfully port Linux to them.

If you managed to get Linux working on a box currently listed as unsupported however, please tell us. We'd be interested to know.

どの stage tarball を使用すべきですか?
This will depend on the CPU type running in your system. The stage filename is named as follows:

Stage Tarball Naming Scheme

For R4000-class CPUs, use a  or   stage tarball.

For R5000-class or later CPUs, use a  or   stage tarball.

I got an "Illegal Instruction" or "Cannot Execute Binary File" error message when chrooting. What did I do wrong?
This is generally caused by using the wrong stage tarball. If you try to run a  userland on a   CPU, you'll get an illegal instruction error message. Likewise, if you have a Big Endian CPU and you try to run Little Endian code on it, you'll get cannot execute binary file.

The fix is simple: clean out your partition, then unpack the correct tarball.

Why doesn't my SGI machine netboot?
This could be for any number of reasons, ranging from cabling issues, through to issues on the server. The best way to troubleshoot any problem is a step-by-step approach...


 * 1)  Have you got the SGI machine (and server) plugged into the right network ports? Make sure the network is cabled correctly. Also note that some machines have special needs. For instance the Challenge S cannot obtain network connectivity under Linux via its UTP port, you need to use the AUI port via a transceiver.


 * 1)  Are there any firewalls in use? Make sure your firewall is not blocking DHCP/BOOTP requests (ports 67 and 68 on UDP) or TFTP (port 69 on UDP).   should get things rolling.


 * 1)  Have you disabled packet MTU discovery and set the port range? SGI boxes require  = 1 and  = "2048 32767". See the Gentoo/MIPS handbook.


 * 1)  Is the server giving out the correct details via BOOTP? Double check your  . ISC's dhcpd won't dish out addressing information via BOOTP unless the machine has been statically defined with a fixed address.


 * 1)  Which TFTP server are you using?    is known to work.   is a lot more advanced, this can cause problems. If in doubt, try installing   and see if the problem clears up.


 * 1)  Are the daemons running?    should show up when typing   . As for TFTP, it'll largely depend on whether its a standalone server, or if its running from   .   runs as a process called   . Look for that in the   output and start any services not currently running.


 * 1)  Does the kernel exist in  ? Make sure you place the kernel image to be booted in this directory and that it is world-readable.  Also, in your , note that the path to the kernel will be relative to the  directory if you're using.


 * 1)  Have you unset the   and   PROM variables? Try running   and.

The machine downloads the kernel, but then "hangs" (using a monitor and keyboard not serial console)
Unfortunately, not all graphics frame buffers are supported under Linux yet. This doesn't mean you can't use the machine... it just means you'll need a null-modem serial cable to interact with it. It is quite possible that the machine is in fact running, however, the system is outputting to the serial console rather than the screen.

Why won't my Cobalt machine boot?
This could be for a number of reasons. Our easiest bet however is to run through a checklist and make sure everything is correct.


 * 1)  Have you got the Cobalt machine (and server) plugged into the right network ports? Make sure the network is cabled correctly. Please note, the Cobalt firmware will only boot via the Primary network port.


 * 1)  Are there any firewalls in use? Make sure your firewall is not blocking DHCP/BOOTP requests (ports 67 and 68 on UDP) or RPC/Portmap (port 111 on UDP and TCP).         should get things rolling.


 * 1)  Is the server giving out the correct details via BOOTP? Double check your  . ISCs dhcpd won't dish out addressing information via BOOTP unless the machine has been statically defined with a fixed address.


 * 1)  Are you exporting  in your  ? Make sure you are exporting that to the Cobalt machine. It only needs read-only access. Also remember to run   after you edit the file.


 * 1)  Are the daemons running?    should show up when typing   . Likewise with   and the other RPC daemons. The following commands should look after this for you:


 * 1)  Does the kernel exist in  ? Make sure you place the kernel image to be booted in this directory and that it is world-readable.

Why don't you support the Qube 2700?
The Qube 2700 was the first of the Cobalt servers. While they are very nice machines, unfortunately, they lack a serial port. In other words, any interaction with the machine has to be done through a network. At present, our netboot images do not support this.