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

Contents of /xml/htdocs/doc/en/mips-requirements.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.4 - (show annotations) (download) (as text)
Mon Jan 31 17:16:08 2005 UTC (9 years, 5 months ago) by swift
Branch: MAIN
Changes since 1.3: +426 -178 lines
File MIME type: application/xml
Kumba has passed on a huge update on the MIPS hardware requirements page.

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3
4 <!-- $Header$ -->
5
6 <guide link="/doc/en/mips-requirements.xml">
7
8 <title>Gentoo/MIPS Linux Hardware Requirements</title>
9
10 <author title="Author">
11 <mail link="kumba@gentoo.org">Joshua Kinard</mail>
12 </author>
13
14 <abstract>
15 This document provides an overview of the status of various MIPS-based systems
16 for installing Gentoo Linux. If you find errors or ommissions please email the
17 maintainer or an editor.
18 </abstract>
19
20 <!-- The content of this document is licensed under the CC-BY-SA license -->
21 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
22 <license />
23
24 <version>0.2</version>
25 <date>2005-01-31</date>
26
27 <chapter>
28 <title>Supported/Unsupported Hardware</title>
29 <section>
30 <body>
31
32 <note>
33 Items in <brite>Red</brite> are currently <e>Unsupported</e> in
34 Gentoo/MIPS at this time. This means Linux does not run on this
35 system/CPU at the current time, or the specific piece of hardware
36 is unsupported in the kernel.
37 </note>
38
39 <note>
40 Items in <c>Blue</c> are considered <e>Highly Experimental</e> at this time.
41 This means the system can boot Linux, but either is unstable, or Gentoo/MIPS
42 has not been tested on it yet. In regards to hardware, it means the specific
43 piece of hardware either works to some extent, or is untested.
44 </note>
45
46 <note>
47 If a particular system is not listed, then it's status is unknown.
48 </note>
49
50 <p>&#160;</p>
51
52 </body>
53 </section>
54 <section>
55 <title>SGI Systems</title>
56 <body>
57
58 <table>
59 <tr>
60 <th>Systems</th>
61 <th>SGI IP #</th>
62 <th>CPUs</th>
63 <th>Kernel Arch</th>
64 <th>Kernel Ver</th>
65 <th>Userland</th>
66 <th>Notes</th>
67 </tr>
68 <tr>
69 <ti>Indy</ti>
70 <ti>IP22</ti>
71 <ti>R4000, R4400, R4600, R5000</ti>
72 <ti>mips, <c>mips64</c></ti>
73 <ti>2.4, <c>2.6</c></ti>
74 <ti>o32, <brite>n32</brite>, <brite>n64</brite></ti>
75 <ti>(1), (4), (8)</ti>
76 </tr>
77 <tr>
78 <ti>Challenge S</ti>
79 <ti>IP22</ti>
80 <ti>R4000, R4400, R4600, R5000</ti>
81 <ti>mips, <c>mips64</c></ti>
82 <ti>2.4, <c>2.6</c></ti>
83 <ti>o32, <brite>n32</brite>, <brite>n64</brite></ti>
84 <ti>(1), (2), (4), (8)</ti>
85 </tr>
86 <tr>
87 <ti>Indigo2</ti>
88 <ti>IP22</ti>
89 <ti>R4000, R4400, R4600</ti>
90 <ti>mips, <c>mips64</c></ti>
91 <ti>2.4, <c>2.6</c></ti>
92 <ti>o32, <brite>n32</brite>, <brite>n64</brite></ti>
93 <ti>(1), (3), (4), (8)</ti>
94 </tr>
95 <tr>
96 <ti><brite>Indigo2 Power</brite></ti>
97 <ti><brite>IP26</brite></ti>
98 <ti><brite>R8000</brite></ti>
99 <ti><brite>mips</brite>, <brite>mips64</brite></ti>
100 <ti><brite>2.4</brite>, <brite>2.6</brite></ti>
101 <ti><brite>o32</brite>, <brite>n32</brite>, <brite>n64</brite></ti>
102 <ti></ti>
103 </tr>
104 <tr>
105 <ti><c>Indigo2 Impact</c></ti>
106 <ti><c>IP28</c></ti>
107 <ti><c>R10000</c></ti>
108 <ti><brite>mips</brite>, <c>mips64</c></ti>
109 <ti><c>2.4</c>, <c>2.6</c></ti>
110 <ti><c>o32</c>, <brite>n32</brite>, <brite>n64</brite></ti>
111 <ti>(1), (3), (4), (5)</ti>
112 </tr>
113 <tr>
114 <ti>O2</ti>
115 <ti>IP32</ti>
116 <ti>R5000, RM5200, <c>RM7000</c>, <brite>R10000</brite>, <brite>R12000</brite></ti>
117 <ti><brite>mips</brite>, mips64</ti>
118 <ti><brite>2.4</brite>, 2.6</ti>
119 <ti>o32, <c>n32</c>, <brite>n64</brite></ti>
120 <ti>(5), (6), (8)</ti>
121 </tr>
122 <tr>
123 <ti><c>Origin 200/2000</c></ti>
124 <ti><c>IP27</c></ti>
125 <ti><c>R10000</c>, <c>R12000</c></ti>
126 <ti><brite>mips</brite>, <c>mips64</c></ti>
127 <ti><brite>2.4</brite>, 2.6</ti>
128 <ti>o32, <c>n32</c>, <brite>n64</brite></ti>
129 <ti></ti>
130 </tr>
131 <tr>
132 <ti><c>Octane</c></ti>
133 <ti><c>IP30</c></ti>
134 <ti><c>R10000</c>, <c>R12000</c>, <c>R14000A</c></ti>
135 <ti><brite>mips</brite>, <c>mips64</c></ti>
136 <ti><brite>2.4</brite>, <c>2.6</c></ti>
137 <ti><c>o32</c>, <c>n32</c>, <brite>n64</brite></ti>
138 <ti>(7)</ti>
139 </tr>
140 <tr>
141 <ti><brite>Indigo</brite></ti>
142 <ti><brite>IP20</brite></ti>
143 <ti><brite>R3000</brite>, <brite>R4000</brite></ti>
144 <ti><brite>mips</brite>, <brite>mips64</brite></ti>
145 <ti><brite>2.4</brite>, <brite>2.6</brite></ti>
146 <ti><brite>o32</brite>, <brite>n32</brite>, <brite>n64</brite></ti>
147 <ti></ti>
148 </tr>
149 <tr>
150 <ti><brite>Fuel</brite></ti>
151 <ti><brite>IP34</brite></ti>
152 <ti><brite>R14000A</brite>, <brite>R16000</brite></ti>
153 <ti><brite>mips</brite>, <brite>mips64</brite></ti>
154 <ti><brite>2.4</brite>, <brite>2.6</brite></ti>
155 <ti><brite>o32</brite>, <brite>n32</brite>, <brite>n64</brite></ti>
156 <ti></ti>
157 </tr>
158 <tr>
159 <ti><brite>Origin 300</brite></ti>
160 <ti><brite>IP45</brite></ti>
161 <ti><brite>R14000</brite></ti>
162 <ti><brite>mips</brite>, <brite>mips64</brite></ti>
163 <ti><brite>2.4</brite>, <brite>2.6</brite></ti>
164 <ti><brite>o32</brite>, <brite>n32</brite>, <brite>n64</brite></ti>
165 <ti></ti>
166 </tr>
167 <tr>
168 <ti><brite>Origin 3000</brite></ti>
169 <ti><brite>IP35</brite></ti>
170 <ti><brite>R14000, R14000A</brite></ti>
171 <ti><brite>mips</brite>, <brite>mips64</brite></ti>
172 <ti><brite>2.4</brite>, <brite>2.6</brite></ti>
173 <ti><brite>o32</brite>, <brite>n32</brite>, <brite>n64</brite></ti>
174 <ti></ti>
175 </tr>
176 <tr>
177 <ti><brite>Origin 350, Tezro</brite></ti>
178 <ti><brite>IP53</brite></ti>
179 <ti><brite>R16000</brite></ti>
180 <ti><brite>mips</brite>, <brite>mips64</brite></ti>
181 <ti><brite>2.4</brite>, <brite>2.6</brite></ti>
182 <ti><brite>o32</brite>, <brite>n32</brite>, <brite>n64</brite></ti>
183 <ti></ti>
184 </tr>
185 </table>
186
187 <p>&#160;</p>
188
189 </body>
190 </section>
191 <section>
192 <title>SGI Accessories</title>
193 <body>
194
195 <table>
196 <tr>
197 <th>Miscellaneous (Supported)</th>
198 </tr>
199 <tr>
200 <ti>Indy/Indigo2: XL Graphics Card (Newport)</ti>
201 </tr>
202 <tr>
203 <ti>Indy/Indigo2: SGI Seeq Ethernet 10Mbps</ti>
204 </tr>
205 <tr>
206 <ti>Indy/Indigo2: WD33C93 SCSI</ti>
207 </tr>
208 <tr>
209 <ti>Indy/Indigo2: HAL2 Sound/Audio</ti>
210 </tr>
211 <tr>
212 <ti>Indy/Indigo2: Parallel Port</ti>
213 </tr>
214 <tr>
215 <ti>Indy/Indigo2: Serial Port</ti>
216 </tr>
217 <tr>
218 <ti>O2: SGI MACE Ethernet 10/100Mbps</ti>
219 </tr>
220 <tr>
221 <ti>O2: Adaptec AIC7880 SCSI</ti>
222 </tr>
223 <tr>
224 <ti>O2: Serial Port</ti>
225 </tr>
226 <tr>
227 <ti>Indigo2 ISA: Parallel Port Card (PC-Style)</ti>
228 </tr>
229 <tr>
230 <ti>Indigo2 ISA: NE2000 Compatible 10Mbps NIC (RTL8019)</ti>
231 </tr>
232 <tr>
233 <th>Miscellaneous (Experimental)</th>
234 </tr>
235 <tr>
236 <ti><c>Indy: I2C/VINO subsystem &amp; IndyCam</c></ti>
237 </tr>
238 <tr>
239 <ti><c>O2: GBE Framebuffer</c></ti>
240 </tr>
241 <tr>
242 <ti><c>O2: PCI Slot</c></ti>
243 </tr>
244 <tr>
245 <ti><c>Octane: Keyboard</c></ti>
246 </tr>
247 <tr>
248 <ti><c>Octane: Mardi Gras (MGRAS) Graphics</c></ti>
249 </tr>
250 <tr>
251 <ti><c>Octane: QLogic ISP1040B SCSI</c></ti>
252 </tr>
253 <tr>
254 <ti><c>Octane: RAD1 Audio</c></ti>
255 </tr>
256 <tr>
257 <ti><c>Origin: IOC3 Ethernet 10/100Mbps</c></ti>
258 </tr>
259 <tr>
260 <ti><c>Origin: QLogic ISP1020 SCSI</c></ti>
261 </tr>
262 <tr>
263 <ti><c>Indigo2 EISA: 3COM 3c597 10/100Mbps</c></ti>
264 </tr>
265 <tr>
266 <ti><c>O2 PCI: ALi 5273 USB 2.0 (Req. Kernel >=2.6.8.1)</c></ti>
267 </tr>
268 <tr>
269 <th>Miscellaneous (Unsupported)</th>
270 </tr>
271 <tr>
272 <ti><brite>Indy/Indigo2: Impact &amp; Extreme/XZ graphics chipsets</brite></ti>
273 </tr>
274 <tr>
275 <ti><brite>Indy: Phobos G130 10/100Mbps NIC</brite></ti>
276 </tr>
277 <tr>
278 <ti><brite>Indigo2: GIO64 Slots</brite></ti>
279 </tr>
280 <tr>
281 <ti><brite>Indigo2: Phobos G160 10/100Mbps NIC</brite></ti>
282 </tr>
283 <tr>
284 <ti><brite>Challenge S: WD33C95A SCSI Adapter/RJ-45 Daughter Card</brite></ti>
285 </tr>
286 <tr>
287 <ti><brite>O2: VICE Subsystem</brite></ti>
288 </tr>
289 <tr>
290 <ti><brite>Octane: SMP Support</brite></ti>
291 </tr>
292 <tr>
293 <ti><brite>Octane: V6/V8/V10/V12 Graphics (Odyssey)</brite></ti>
294 </tr>
295 </table>
296
297 <p>&#160;</p>
298
299 </body>
300 </section>
301
302
303 <section>
304 <title>Notes on SGI Machines</title>
305 <body>
306
307 <impo>
308 <b><c>(1)</c></b> If you lack an appropriate Framebuffer, you will be required
309 to use serial console. Serial console programs for linux include <c>minicom</c>
310 and <c>xc</c>, and for Windows, <c>HyperTerminal</c> and <c>Tera Term Pro</c>.
311 If you are running Windows, and intend to use HyperTerminal, it is advised that
312 you seek out an updated client from the program's website instead of the one
313 installed by default. An upgraded client provides much better serial support
314 than the default one installed by Windows.
315 </impo>
316
317 <impo>
318 <b><c>(2)</c></b> The Challenge S has its RJ-45 connector on a daughter board
319 (Mezz) linked with an unsupported SCSI adapter, a <c>WD33C95A</c>. In order
320 for this network connector to function, this SCSI bus needs to be activated,
321 however it is not yet supported by Linux. As a result of this, the Challenge
322 S can only get network connectivity via its AUI connector.
323 </impo>
324
325 <impo>
326 <b><c>(3)</c></b> Indigo2 EISA Support is <e>highly</e> experimental. It isn't
327 very well tested and may not work with all hardware. Hardware that it is known
328 to function with is listed, and as more compatible hardware is discovered, it
329 will be added. Please note that hardware requiring DMA support is currently
330 not functional. This includes EISA/ISA-based soundcards. EISA Video cards
331 requiring an x86-compatible BIOS are also not functional.
332 </impo>
333
334 <impo>
335 <b><c>(4)</c></b> The IP22 Serial Driver is non-functional in the 2.6 kernel,
336 so while the 2.6 kernel will boot on IP22 systems, if you lack an appropriate
337 framebuffer, then you will be unable to see any output on the main console.
338 Hopefully this driver will be fixed soon.
339 </impo>
340
341 <impo>
342 <b><c>(5)</c></b> IP28 Indigo2 Impact support (classified as an Indigo2 system
343 w/ an R10000 Processor) is <e><c>very experimental</c></e>. Most of the work
344 is currently being done by Peter Fuerst, and he maintains patches on his
345 website at <uri>http://home.alphastar.de/fuerst/download.html</uri>. This
346 kernel is <e><brite>NOT</brite></e> intended for stable, day-to-day use.
347 The Indigo2 IP28 system suffers from an issue known as <e>Speculative
348 Execution</e>, a feature of the R10000 Processor that is problematic on
349 machines that are <e>Non Cache Coherent</e>, such as the IP28 Indigo2
350 and on R10000/R12000-based IP32 O2 systems. Details on the nature of
351 Speculative Execution, and the issues it poses to the Indigo2 can be found
352 at the following URLs:
353 <br/>
354 1. MIPS R10000 Microprocessor User's Manual (See <c>PDF Pages 51-55</c>) -
355 <uri>http://techpubs.sgi.com/library/manuals/2000/007-2490-001/pdf/007-2490-001.pdf</uri>
356 <br/>
357 2.
358 Post to NetBSD sgimips Mailing List on 29 Jun 2000 -
359 <uri>http://mail-index.netbsd.org/port-sgimips/2000/06/29/0006.html</uri>
360 </impo>
361
362 <impo>
363 <b><c>(6)</c></b> The O2 RM7000 Processor support is limited in Linux currently,
364 as it requires a fairly recent kernel version (>2.6.7), and has several notable
365 issues. The first issue is a problem with scsi at the moment, making the
366 internal disks unusable at the current time. The Level 3 (Tertiary) Cache is
367 also disabled due to there being no support for this cache in the linux kernel.
368 <br /><br />
369 Please be aware that this note only applies to the official SGI RM7000 running
370 at 350MHz, not the 600MHz RM7000 that can be assembed using an RM5200 board.
371 These "modded" CPU modules for O2 systems are not supported/tested, although,
372 in theory, they should be functional, but may suffer from the same problems
373 listed above.
374 </impo>
375
376 <impo>
377 <b><c>(7)</c></b> Octane support in Linux shoul be regarded as
378 <e><c>experimental</c></e>. Support for this particular machine from SGI has
379 been progressing quite well, and the Linux kernel functions reasonably well.
380 The current status for this system may be found here:
381 <uri>http://helios.et.put.poznan.pl/~sskowron/ip30/</uri>. Wider
382 support in Gentoo for this system will be available in the future, so watch
383 this space closely for more details.
384 </impo>
385
386 <impo>
387 <b><c>(8)</c></b> The maximum amount of RAM supported in the Indy, Challenge S,
388 Indigo2 (not Power or Impact), and O2 systems is 256MB, due to no HIGHMEM
389 support the Linux kernel. Only a 64-bit kernel w/ HIGHMEM support can properly
390 detect RAM amounts greater than 256MB on these systems. However, do note that
391 using HIGHMEM does incur a performance hit, so it should only be used when
392 necessary.
393 </impo>
394
395 <p>&#160;</p>
396
397 </body>
398 </section>
399 <section>
400 <title>Cobalt Microserver Systems</title>
401 <body>
402
403 <table>
404 <tr>
405 <th>Systems</th>
406 <th>CPU</th>
407 <th>Kernel Arch</th>
408 <th>Kernel Ver</th>
409 <th>Userland</th>
410 </tr>
411 <tr>
412 <ti><c>RaQ 1</c></ti>
413 <ti><c>RM5230/150MHz</c></ti>
414 <ti><c>mipsel</c>, <brite>mips64el</brite></ti>
415 <ti><c>2.4</c>, <brite>2.6</brite></ti>
416 <ti><c>o32</c>, <brite>n32</brite>, <brite>n64</brite></ti>
417 </tr>
418 <tr>
419 <ti>RaQ 2</ti>
420 <ti>RM5231/250MHz</ti>
421 <ti>mipsel, <brite>mips64el</brite></ti>
422 <ti>2.4, 2.6</ti>
423 <ti>o32, <brite>n32</brite>, <brite>n64</brite></ti>
424 </tr>
425 <tr>
426 <ti><brite>Qube 2700 (a.k.a. Qube 1)</brite></ti>
427 <ti><brite>RM5230/150MHz</brite></ti>
428 <ti><brite>mipsel</brite>, <brite>mips64el</brite></ti>
429 <ti><brite>2.4</brite>, <brite>2.6</brite></ti>
430 <ti><brite>o32</brite>, <brite>n32</brite>, <brite>n64</brite></ti>
431 </tr>
432 <tr>
433 <ti>Qube 2800 (a.k.a. Qube 2)</ti>
434 <ti>RM5231/250MHz</ti>
435 <ti>mipsel, <brite>mips64el</brite></ti>
436 <ti>2.4, <c>2.6</c></ti>
437 <ti>o32, <brite>n32</brite>, <brite>n64</brite></ti>
438 </tr>
439 <tr>
440 <ti><c>Seagate NASRaQ</c></ti>
441 <ti><c>RM5231/???</c></ti>
442 <ti><c>mipsel</c>, <brite>mips64el</brite></ti>
443 <ti><c>2.4</c>, <brite>2.6</brite></ti>
444 <ti><c>o32</c>, <brite>n32</brite>, <brite>n64</brite></ti>
445 </tr>
446 <tr>
447 <ti><c>Gateway Microserver</c></ti>
448 <ti><c>RM5231/???</c></ti>
449 <ti><c>mipsel</c>, <brite>mips64el</brite></ti>
450 <ti><c>2.4</c>, <brite>2.6</brite></ti>
451 <ti><c>o32</c>, <brite>n32</brite>, <brite>n64</brite></ti>
452 </tr>
453 </table>
454
455 <impo>
456 Cobalt support is still in testing phases, and the documentation is incomplete
457 and has not yet been fully integrated into this guide, nor into the Gentoo
458 Handbook. Gentoo does run on these systems, and installation stages may be
459 found in the <c>experimental/mips</c> folder on your nearest mirror. Expect
460 many neat things for Cobalt machines in the coming months.
461 </impo>
462
463 <note>
464 2.6 has been tested to boot on the Cobalt RaQ2 and Qube2 systems, however
465 booting this kernel requires the use of a new bootloader (called <c>colo</c>)
466 that can either replace the original Cobalt bootloader in the system's flash
467 chip, or the new boot loader can be <e>chain loaded</e>, or booted by the old
468 bootloader. Those interested in learning more about this new bootloader may
469 visit the webpage of its author, who also maintains several 2.4/2.6 patchsets
470 for these machines. The webpage can be found here:
471 <uri>http://www.colonel-panic.org/cobalt-mips/</uri>. This new bootloader is
472 available in the portage tree as <c>sys-boot/colo</c>.
473 </note>
474
475 <p>&#160;</p>
476
477 </body>
478 </section>
479 <section>
480 <title>Other Notes</title>
481 <body>
482
483 <note>
484 The Playstation 2 is a specialized MIPS system, using an R5900 MIPS processor
485 (EmotionEngine) manufactured by Toshiba. The support for this processor is
486 extremely limited, and only found in the development toolchains available in
487 the PS2 Linux Kit and via some patches available on the PS2 Linux Homepage.
488 There was a limited amount of work done on porting Gentoo to the PS2 Linux
489 Kit, however it is incomplete as of this writing. Those interested may visit
490 <uri>http://playstation2-linux.com/projects/gentoo-ps2/</uri> if they are
491 interested in assisting or completing the port. Additional information on
492 PS2 Compiler Toolchains can be found at <uri>http://www.ps2dev.org/</uri>.
493 </note>
494
495 <note>
496 Gentoo/MIPS has also been installed on a SiByte BCM1250 Machine, a Big-endian,
497 dual-processor MIPS machine. Currently, only one person to date has done this,
498 but more people willing to test Gentoo on such hardware are welcomed to try
499 and report results.
500 </note>
501
502 <p>&#160;</p>
503
504 </body>
505 </section>
506 <section>
507 <title>Minimum Recommended Requirements</title>
508 <body>
509
510 <ul>
511 <li>
512 128MB RAM - More ram is better, as Gentoo currently uses the gcc-3.2.x and
513 greater versions of gcc. These versions of gcc tend to consume more memory
514 than their older 2.95.x counterparts, and on the merging of large packages,
515 anything less than 128MB of ram could make gcc fail to compile the package,
516 or mysteriously stop in the middle of compiliation. A recommended amount
517 of ram is 160MB.
518 </li>
519 <li>
520 9GB Hard Drive Space - 9GB is more or less the recommended minimum. It is
521 enough space to install Gentoo on and leaves extra space for daily
522 activities on the machine. Gentoo has been installed on smaller drives,
523 the smallest being a 3.2GB drive, but it does not leave alot of room for
524 much else.
525 </li>
526 </ul>
527
528 <p>&#160;</p>
529
530 </body>
531 </section>
532 </chapter>
533 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20