/[gentoo]/xml/htdocs/doc/en/gentoo-mips-faq.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-mips-faq.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.4 Revision 1.5
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml,v 1.4 2008/05/21 19:47:28 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml,v 1.5 2011/08/15 20:13:16 swift Exp $ -->
3 3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5<guide link="/doc/en/gentoo-mips-faq.xml"> 5<guide link="/doc/en/gentoo-mips-faq.xml">
6 6
7<title>Gentoo Linux/MIPS Frequently Asked Questions</title> 7<title>Gentoo Linux/MIPS Frequently Asked Questions</title>
8 8
9<author title="Author"> 9<author title="Author">
10 <mail link="redhatter@gentoo.org">Stuart Longland</mail> 10 <mail link="redhatter@gentoo.org">Stuart Longland</mail>
11</author>
12<author title="Editor">
13 <mail link="mattst88">Matt Turner</mail>
11</author> 14</author>
12 15
13<abstract> 16<abstract>
14This FAQ is intended to answer some of the most frequently asked questions 17This FAQ is intended to answer some of the most frequently asked questions
15relating to Gentoo/MIPS and Linux/MIPS in general. 18relating to Gentoo/MIPS and Linux/MIPS in general.
17 20
18<!-- The content of this document is licensed under the CC-BY-SA license --> 21<!-- The content of this document is licensed under the CC-BY-SA license -->
19<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 22<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
20<license/> 23<license/>
21 24
22<version>1.1</version> 25<version>2</version>
23<date>2005-09-08</date> 26<date>2011-08-14</date>
24 27
25<faqindex> 28<faqindex>
26<title>About this document</title> 29<title>About this Document</title>
27<section> 30<section>
28<title>Introduction</title> 31<title>Introduction</title>
29<body> 32<body>
30 33
31<p> 34<p>
34and experienced users alike. It has been split into a number of categories 37and experienced users alike. It has been split into a number of categories
35to make navigation easier. 38to make navigation easier.
36</p> 39</p>
37 40
38<p> 41<p>
39If you have anything to contribute to the FAQ or, having read this guide, you 42If you'd like to contribute to the FAQ or, having read this guide, you
40still have questions that are left unanswered, feel free to 43still have questions that are left unanswered, feel free to
41<uri link="http://mips.gentoo.org">drop us a line</uri>. 44<uri link="http://www.gentoo.org/proj/en/base/mips/">drop us a line</uri>.
42</p> 45</p>
43 46
44</body> 47</body>
45</section> 48</section>
46</faqindex> 49</faqindex>
50<section id="what"> 53<section id="what">
51<title>What is Gentoo/MIPS?</title> 54<title>What is Gentoo/MIPS?</title>
52<body> 55<body>
53 56
54<p> 57<p>
55Gentoo/MIPS is a small project within the Gentoo Foundation, responsible for 58Gentoo/MIPS is a small project responsible for looking after the MIPS port of
56looking after the MIPS port of Gentoo Linux. We currently look after two main 59Gentoo Linux.
57sub architectures of the MIPS family specifically: Silicon Graphics systems and
58MIPS-based Cobalt servers.
59</p> 60</p>
60 61
61</body> 62</body>
62</section> 63</section>
63<section id="why"> 64<section id="why">
94<title>Why don't you port Gentoo to NetBSD/MIPS or IRIX?</title> 95<title>Why don't you port Gentoo to NetBSD/MIPS or IRIX?</title>
95<body> 96<body>
96 97
97<p> 98<p>
98Hey, great idea. Unfortunately, a lot of the Gentoo/MIPS team already have 99Hey, great idea. Unfortunately, a lot of the Gentoo/MIPS team already have
99their hands full looking after Linux/MIPS as well as other commitments. 100their hands full looking after Linux/MIPS as well as other commitments. A
100However, you're welcome to give it a try. May I suggest raising this on the 101project like this would fall under the umbrella of the
101<uri link="http://forums.gentoo.org/viewforum-f-32.html">Gentoo Forums</uri> and 102<uri link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/">Gentoo Prefix
102see what the interest is first. Also, have a look at some of the other threads 103project</uri>. Some work has been done for IRIX, the remnants of which can be
103on porting Gentoo to other architectures such as <uri 104found in <uri
104link="http://forums.gentoo.org/viewtopic-t-113387.html">Solaris/SPARC</uri>, 105link="https://bugs.gentoo.org/buglist.cgi?quicksearch=irix">bugzilla</uri>.
105<uri link="http://forums.gentoo.org/viewtopic-t-319607.html">IBM OS/2</uri> and
106<uri link="http://forums.gentoo.org/viewtopic-t-319691.html">Microsoft Services
107For Unix</uri> for hints on how to proceed. If after some hacking you get
108something useful out of it... chances are a few developers will pick up on this
109and help you get it to the next stage.
110</p> 106</p>
111 107
112</body> 108</body>
113</section> 109</section>
114</chapter> 110</chapter>
119<title>What is MIPS?</title> 115<title>What is MIPS?</title>
120<body> 116<body>
121 117
122<p> 118<p>
123<uri link="http://www.mips.com">MIPS Technologies</uri> is a company that 119<uri link="http://www.mips.com">MIPS Technologies</uri> is a company that
124produce a number of RISC CPU cores which implement the MIPS Instruction Set 120produce a number of RISC CPU cores which implement the <uri
121link="http://en.wikipedia.org/wiki/MIPS_architecture">MIPS Architecture</uri>.
125Architecture. These processors appear in all sorts of hardware ranging from 122These processors appear in all sorts of hardware ranging from small embedded
126small embedded devices to large servers. 123devices to large servers.
127</p> 124</p>
128 125
129<p> 126<p>
130It also happens to be an acronym; <b>M</b>illions of <b>I</b>nstructions 127It also happens to be an acronym; <b>M</b>illions of <b>I</b>nstructions
131<b>P</b>er <b>S</b>econd. 128<b>P</b>er <b>S</b>econd.
136<section id="hardware"> 133<section id="hardware">
137<title>What sort of hardware uses MIPS processors?</title> 134<title>What sort of hardware uses MIPS processors?</title>
138<body> 135<body>
139 136
140<p> 137<p>
141Good question. In short... Heaps. MIPS Processors see use inside all sorts 138In short... lots. MIPS Processors see use inside all sorts
142of machines, ranging from small PDAs (such as the early Windows CE powered Casio 139of machines, ranging from small PDAs (such as the early Windows CE powered Casio
143PDAs), X Terminals (e.g. Tektronix TekXPress XP330 series), through to 140PDAs), X Terminals (e.g. Tektronix TekXPress XP330 series), through to
144workstations such as the Silicon Graphics Indy and O2 and even high end servers 141workstations such as the Silicon Graphics Indy and O2 and even high end servers
145such as the Silicon Graphics Origin 2000. 142such as the Silicon Graphics Origin 2000.
146</p> 143</p>
147 144
148<p> 145<p>
149Here is a list of some of the more famous MIPS-based systems in use. A more
150comprehensive list can be found on the <uri 146A comprehensive list can be found on the <uri
151link="http://www.linux-mips.org/wiki/index.php/Systems">Linux/MIPS website</uri> 147link="http://www.linux-mips.org/wiki/index.php/Systems">Linux/MIPS website</uri>
152</p> 148</p>
153 149
154<table>
155<tr>
156 <th>Sony Game Consoles</th>
157 <ti>
158 <uri link="http://www.linux-mips.org/wiki/index.php/PS1">
159 PlayStation</uri><br />
160 <uri link="http://www.linux-mips.org/wiki/index.php/PS2">
161 PlayStation 2</uri><br />
162 <uri link="http://www.linux-mips.org/wiki/index.php/PSP">
163 PlayStation Pocket</uri>
164 </ti>
165</tr>
166<tr>
167 <th>Nintendo Game Consoles</th>
168 <ti>
169 <uri link="http://www.linux-mips.org/wiki/index.php/Nintendo_64">
170 Nintendo 64
171 </uri>
172 </ti>
173</tr>
174<tr>
175 <th>Silicon Graphics Machines</th>
176 <ti>
177 <uri link="http://www.linux-mips.org/wiki/index.php/IP12">
178 Iris Indigo</uri><br />
179 <uri link="http://www.linux-mips.org/wiki/index.php/IP19">
180 Challenge</uri><br />
181 <uri link="http://www.linux-mips.org/wiki/index.php/IP19">
182 Onyx</uri><br />
183 <uri link="http://www.linux-mips.org/wiki/index.php/IP22">
184 Indy</uri><br />
185 <uri link="http://www.linux-mips.org/wiki/index.php/IP22">
186 Indigo 2</uri><br />
187 <uri link="http://www.linux-mips.org/wiki/index.php/IP22">
188 Challenge S</uri><br />
189 <uri link="http://www.linux-mips.org/wiki/index.php/IP27">
190 Origin 200</uri><br />
191 <uri link="http://www.linux-mips.org/wiki/index.php/IP27">
192 Origin 2000</uri><br />
193 <uri link="http://www.linux-mips.org/wiki/index.php/IP27">
194 Onyx 2</uri><br />
195 <uri link="http://www.linux-mips.org/wiki/index.php/IP30">
196 Octane</uri><br />
197 <uri link="http://www.linux-mips.org/wiki/index.php/IP30">
198 Octane 2</uri><br />
199 <uri link="http://www.linux-mips.org/wiki/index.php/IP32">
200 O2</uri><br />
201 <uri link="http://www.linux-mips.org/wiki/index.php/IP34">
202 Fuel</uri><br />
203 <uri link="http://www.linux-mips.org/wiki/index.php/IP35">
204 Origin 3000</uri><br />
205 <uri link="http://www.linux-mips.org/wiki/index.php/IP45">
206 Origin 300</uri><br />
207 <uri link="http://www.linux-mips.org/wiki/index.php/IP53">
208 Origin 350</uri><br />
209 <uri link="http://www.linux-mips.org/wiki/index.php/IP53">
210 Tezro</uri>
211 </ti>
212</tr>
213<tr>
214 <th>DECStations</th>
215 <ti>
216 <uri link="http://www.linux-mips.org/wiki/index.php/Deskstation_rPC44">
217 rPC44</uri><br />
218 <uri link="http://www.linux-mips.org/wiki/index.php/Deskstation_Tyne">
219 Tyne</uri>
220 </ti>
221</tr>
222<tr>
223 <th>Cobalt Microservers</th>
224 <ti>
225 <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
226 Qube 2700</uri><br />
227 <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
228 Qube 2800</uri><br />
229 <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
230 RaQ</uri><br />
231 <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
232 RaQ 2</uri>
233 </ti>
234</tr>
235<tr>
236 <th>
237 Broadcom-based 802.11g<br />
238 Broadband Internet Routers
239 </th>
240 <ti>
241 <uri link="http://openwrt.org/">Linksys WRT54G</uri>
242 </ti>
243</tr>
244</table>
245
246<p> 150<p>
247... and that's only just scratching the surface. These machines are wide and 151... and that's only scratching the surface. These machines are wide and
248varied. Many of them do not currently run Linux. Of those that do, we only 152varied. Many of them do not currently run Linux. Of those that do, we only
249support a handful, although you're welcome to port Gentoo/MIPS to any MIPS 153support a handful, although you're welcome to port Gentoo/MIPS to any MIPS
250machine if you so wish. Some of these machines are also the focus of the <uri 154machine if you so wish. Some of these machines are also the focus of the <uri
251link="http://embedded.gentoo.org">Embedded Gentoo Project</uri> such as the 155link="http://embedded.gentoo.org">Embedded Gentoo Project</uri> such as the
252Linksys WRT54G. 156Linksys WRT54G.
257<section id="supported"> 161<section id="supported">
258<title>Is my machine supported?</title> 162<title>Is my machine supported?</title>
259<body> 163<body>
260 164
261<p> 165<p>
262This question is difficult to answer. Your machine could fall into one of three
263different baskets:
264</p>
265
266<ul>
267 <li>Your machine is supported by Gentoo/MIPS</li>
268 <li>Your machine is supported by Linux/MIPS, but not by Gentoo/MIPS (yet)</li>
269 <li>Your machine is not supported by Linux/MIPS</li>
270</ul>
271
272<p>
273For the first one an easy way to find out is to have a look at the 166For the first one an easy way to find out is to have a look at the
274<uri link="/doc/en/mips-requirements.xml">Gentoo/MIPS 167<uri link="/doc/en/mips-requirements.xml">Gentoo/MIPS
275requirements page</uri>. This will tell you if the system you've got can 168requirements page</uri>. This will tell you if the system you've got can
276theoretically run Gentoo/MIPS. Stuart has also written a 169theoretically run Gentoo/MIPS.
277<uri link="http://stuartl.longlandclan.hopto.org/gentoo/mips/">hardware support
278database</uri> in which users may contribute their experiences. This can help
279measure how well Gentoo/MIPS runs on a particular machine.
280</p> 170</p>
281 171
282<p> 172<p>
283If you don't find your machine listed there, you may wish to have a look on the 173If you don't find your machine listed there, you may wish to have a look on the
284<uri link="http://www.linux-mips.org/wiki/index.php/Systems">Linux/MIPS 174<uri link="http://www.linux-mips.org/wiki/index.php/Systems">Linux/MIPS
294<title>Why don't you support machine X</title> 184<title>Why don't you support machine X</title>
295<body> 185<body>
296 186
297<p> 187<p>
298If you've looked at the Gentoo/MIPS Hardware Requirements page, you've probably 188If you've looked at the Gentoo/MIPS Hardware Requirements page, you've probably
299noticed there are a LOT of machines we don't support. In the case of SGI 189noticed there are a lot of machines we don't support. In the case of SGI
300hardware, very little is known about some of them, not enough 190hardware, very little is known about some of them, not enough
301to successfully port Linux to them. 191to successfully port Linux to them.
302</p> 192</p>
303 193
304<p> 194<p>
305If you managed to get Linux working on a box currently listed as 195If you managed to get Linux working on a box currently listed as
306<e>unsupported</e> however, feel free to tell us. We'd be interested to know. 196<e>unsupported</e> however, please tell us. We'd be interested to know.
307</p> 197</p>
308 198
309</body> 199</body>
310</section> 200</section>
311</chapter> 201</chapter>
320This will depend on the CPU type running in your system. The stage filename is 210This will depend on the CPU type running in your system. The stage filename is
321named as follows: 211named as follows:
322</p> 212</p>
323 213
324<pre caption="Stage Tarball Naming Scheme"> 214<pre caption="Stage Tarball Naming Scheme">
325 stage3-mipsel4-2005.0.tar.bz2 215 stage3-mipsel4_multilib-20110627.tar.bz2
326 \____/ \_____/ \____/ 216 \____/ \_____/ \_____/ \______/
217 | | | |
218 | | | `-- Gentoo Release (date of creation)
327 | | | 219 | | |
328 | | `--- Gentoo Release (e.g. 1.4, 2004.3, 2005.0) 220 | | `--- ABI: multilib, n32, n64 (nothing for o32)
329 | | 221 | |
330 | `----------- Endianness and ISA Level 222 | `----------- Endianness and ISA Level
331 | mips ==> Big Endian 223 | mips ==> Big Endian
332 | mipsel ==> Little Endian 224 | mipsel ==> Little Endian
333 | 225 |
334 | R3xxx and earlier: ISA Level 1
335 | R4xxx series: ISA Level 3
336 | R5000 and above: ISA Level 4
337 |
338 `------------------ Stage Tarball type: 1, 2 or 3. 226 `------------------ Stage Tarball type: 1, 2 or 3.
339</pre> 227</pre>
340 228
341<p> 229<p>
342So for those of you who are running R4000-class CPUs, try a <c>mips3</c> or 230For R4000-class CPUs, use a <c>mips3</c> or <c>mipsel3</c> stage tarball.
343<c>mipsel3</c> stage tarball.
344</p>
345
346<p> 231</p>
347For those running R5000-class or later CPUs, try a <c>mips4</c> or 232
348<c>mipsel4</c> stage tarball.
349</p> 233<p>
350 234For R5000-class or later CPUs, use a <c>mips4</c> or <c>mipsel4</c> stage
351<p> 235tarball.
352Sometimes the filename will have <c>n32</c> or <c>n64</c> in the filename as
353well. These refer to 64-bit userland images. At the moment, support for 64-bit
354userlands is still quite flaky and a lot of packages are broken. I'd suggest
355leaving these alone unless you're particularly brave and don't mind a rather
356bumpy ride.
357</p> 236</p>
358 237
359</body> 238</body>
360</section> 239</section>
361<section id="chroot"> 240<section id="chroot">
362<title>I got told "Illegal Instruction" or "Cannot Execute Binary 241<title>I got an "Illegal Instruction" or "Cannot Execute Binary
363File" when chrooting. What did I do wrong?</title> 242File" error message when chrooting. What did I do wrong?</title>
364<body> 243<body>
365 244
366<p> 245<p>
367This is generally caused by using the wrong stage tarball. If you try to run a 246This is generally caused by using the wrong stage tarball. If you try to run a
368<c>mips4</c> userland on a <c>mips3</c> CPU, you'll get an <e>illegal 247<c>mips4</c> userland on a <c>mips3</c> CPU, you'll get an <e>illegal
369instruction</e> error message. Likewise, if you have a Big Endian CPU and you 248instruction</e> error message. Likewise, if you have a Big Endian CPU and you
370try running Little Endian code on it, you'll get told <e>cannot execute binary 249try to run Little Endian code on it, you'll get <e>cannot execute binary
371file</e>. 250file</e>.
372</p> 251</p>
373 252
374<p> 253<p>
375The fix is simple... clean out your partition, then unpack the correct tarball. 254The fix is simple: clean out your partition, then unpack the correct tarball.
376Which one is that I hear you ask? Have a read of the previous FAQ entry.
377</p> 255</p>
378 256
379</body> 257</body>
380</section> 258</section>
381</chapter> 259</chapter>
453 331
454</body> 332</body>
455</section> 333</section>
456<section id="serial"> 334<section id="serial">
457<title>The machine downloads the kernel, but then "hangs" (using a monitor and 335<title>The machine downloads the kernel, but then "hangs" (using a monitor and
458keyboard -- not serial console)</title> 336keyboard &ndash; not serial console)</title>
459<body> 337<body>
460 338
461<p> 339<p>
462Unfortunately, not all graphics frame buffers are supported under Linux yet. 340Unfortunately, not all graphics frame buffers are supported under Linux yet.
463This doesn't mean you can't use the machine... it just means you'll need a 341This doesn't mean you can't use the machine... it just means you'll need a
533 411
534<p> 412<p>
535The Qube 2700 was the first of the Cobalt servers. While they are very nice 413The Qube 2700 was the first of the Cobalt servers. While they are very nice
536machines, unfortunately, they lack a serial port. In other words, any 414machines, unfortunately, they lack a serial port. In other words, any
537interaction with the machine has to be done through a network. At present, our 415interaction with the machine has to be done through a network. At present, our
538netboot images do not support this, although plans are in the works that may 416netboot images do not support this.
539enable support for this machine.
540</p> 417</p>
541 418
542</body> 419</body>
543</section> 420</section>
544 421

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20