MIPS/FAQ/ko

이 자주 묻는 질문 문서에서는 젠투/MIPS와 일반적인 리눅스/MIPS와 관련한 자주 묻는 대부분의 질문 중 몇가지에 대해 답을 하려 합니다.

도입부
이 자주 묻는 질문 문서에서는 젠투/MIPS와 일반적인 리눅스/MIPS와 관련 여러 사용자가 자주 묻는 질문에 대해 답을 하려 합니다. 새 사용자와 써본 사용자 전부를 대상으로 합니다. 쉽게 찾아볼 수 있도록 몇가지 분류로 나누었습니다.

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.

젠투/MIPS가 뭐죠?
젠투/MIPS는 젠투 리눅스를 MIPS에 포팅하려는 작은 프로젝트입니다.

왜 MIPS에 젠투 리눅스를 설치하죠?
예, 좋아요. 일부 MIPS 머신은 오늘날 추세에 있는 머신에 비하면 빠른 장비가 아닙니다. 그러나 이런 괴물 같은 머신이 존재하는 시대임에도 불구하고, 여전히 쓸모있는 머신이 될 수 있습니다. 코발트 큐브 2는 매우 널리 알려진 광대역 인터넷 라우터이자, 웹사이트, 전자메일, IRC, 등 여러 작업을 처리할 수 있는 머신이 될 수 있습니다. 그러니까 이런 장비에 리눅스를 설치하려는 이유는 여러가지가 있습니다.


 * 판에 박힌 참고를 벗어나 다른 다양한 컴퓨터 하드웨어를 배울 수 있습니다


 * 쓰레기 덩어리를 매우 쓸모있는 시스템으로 바꿔줍니다


 * 상태 심볼: x86 리눅스는 꽤 흔해서 오늘날에 즐기기에는 재미없습니다. 그러나 MIPS 리눅스는 상당히 드물어서 조금 살펴봐야 할 점이 있습니다.

젠투를 NetBSD/MIPS 또는 IRIX로 포팅하면 어떤가요?
올, 괜찮은 생각인데요. 많은 젠투/MIPS 팀 구성원은 다른 기여자들과 마찬가지로 Linux/MIPS를 전반적으로 손보고 있는데요. 이와 같은 프로젝트는 젠투 프리픽스 프로젝트에 들어있습니다. 일부 작업은 IRIX에서 마무리가 됐구요, 나머지는 버그질라에서 찾아볼 수 있습니다.

MIPS가 뭐죠?
MIPS Technologies는 MIPS 아키텍처를 구현한 수많은 RISC CPU 코어를 만드는 회사예요. 이런 모든 종류의 하드웨어에서 나타나는 프로세서는 작은 임베디드 장치로부터 큰 서버에까지 다양한 곳에서 볼 수 있습니다.

이 단어는 다음의 의미를 줄인 말이기도 합니다. M illions of I nstructions P er S econd.

MIPS 프로세서는 어떤 하드웨어가 사용하나요?
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.

Is my machine supported?
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.

Which stage tarball do I use?
This will depend on the CPU type running in your system. The stage filename is named as follows:

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

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. 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. SGI boxes require = 1 and  = "2048 32767". See the Gentoo/MIPS handbook. 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. 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. 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. 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. Try running  and.
 * 1)  Have you got the SGI machine (and server) plugged into the right network ports?
 * 1)  Are there any firewalls in use?
 * 1)  Have you disabled packet MTU discovery and set the port range?
 * 1)  Is the server giving out the correct details via BOOTP?
 * 1)  Which TFTP server are you using?
 * 1)  Are the daemons running?
 * 1)  Does the kernel exist in  ?
 * 1)  Have you unset the   and   PROM variables?

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. Try using a default serial connection of 9600 8N1, with a null modem adapter.

왜 내 코발트 머신이 부팅하지 않죠?
여러가지 이유가 될 수 있는데요. 그 중에 가장 쉬운 해결책을 내보자면 점검 항목을 따라 실행해보고 모든 동작이 올바르게 진행되는지 확인해보세요.

Make sure the network is cabled correctly. Please note, the Cobalt firmware will only boot via the Primary network port. 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). The following firewall rules should get things rolling: Double check your. ISCs dhcpd won't dish out addressing information via BOOTP unless the machine has been statically defined with a fixed address. 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. should show up when typing. Likewise with  and the other RPC daemons. The following commands should look after this for you: Make sure you place the kernel image to be booted in this directory and that it is world-readable.
 * 1)  Have you got the Cobalt machine (and server) plugged into the right network ports?
 * 1)  Are there any firewalls in use?
 * 1)  Is the server giving out the correct details via BOOTP?
 * 1)  Are you exporting  in your  ?
 * 1)  Are the daemons running?
 * 1)  Does the kernel exist in  ?

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.