| 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.6 2011/09/04 17:53:40 swift Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml,v 1.7 2012/07/08 23:09:11 nightmorph Exp $ --> |
| 3 | |
3 | |
| 4 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
4 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 5 | <guide> |
5 | <guide> |
| 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> |
11 | </author> |
| 12 | <author title="Editor"> |
12 | <author title="Editor"> |
| 13 | <mail link="mattst88">Matt Turner</mail> |
13 | <mail link="mattst88">Matt Turner</mail> |
| 14 | </author> |
14 | </author> |
| 15 | |
15 | |
| 16 | <abstract> |
16 | <abstract> |
| 17 | This FAQ is intended to answer some of the most frequently asked questions |
17 | This FAQ is intended to answer some of the most frequently asked questions |
| 18 | relating to Gentoo/MIPS and Linux/MIPS in general. |
18 | relating to Gentoo/MIPS and Linux/MIPS in general. |
| 19 | </abstract> |
19 | </abstract> |
| 20 | |
20 | |
| 21 | <!-- 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 --> |
| 22 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
22 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 23 | <license/> |
23 | <license/> |
| 24 | |
24 | |
| 25 | <version>2</version> |
25 | <version>3</version> |
| 26 | <date>2011-08-14</date> |
26 | <date>2012-07-08</date> |
| 27 | |
27 | |
| 28 | <faqindex> |
28 | <faqindex> |
| 29 | <title>About this Document</title> |
29 | <title>About this Document</title> |
| 30 | <section> |
30 | <section> |
| 31 | <title>Introduction</title> |
31 | <title>Introduction</title> |
| 32 | <body> |
32 | <body> |
| 33 | |
33 | |
| 34 | <p> |
34 | <p> |
| 35 | This FAQ is intended to answer frequently asked questions about Gentoo/MIPS and |
35 | This FAQ is intended to answer frequently asked questions about Gentoo/MIPS and |
| 36 | Linux/MIPS that we receive from various users. It's aimed at both new users |
36 | Linux/MIPS that we receive from various users. It's aimed at both new users |
| 37 | and experienced users alike. It has been split into a number of categories |
37 | and experienced users alike. It has been split into a number of categories |
| 38 | to make navigation easier. |
38 | to make navigation easier. |
| 39 | </p> |
39 | </p> |
| 40 | |
40 | |
| 41 | <p> |
41 | <p> |
| … | |
… | |
| 290 | <b>Have you disabled packet MTU discovery and set the port range?</b><br /> |
290 | <b>Have you disabled packet MTU discovery and set the port range?</b><br /> |
| 291 | SGI boxes require <path>/proc/sys/net/ipv4/ip_no_pmtu_disc</path> = 1 and |
291 | SGI boxes require <path>/proc/sys/net/ipv4/ip_no_pmtu_disc</path> = 1 and |
| 292 | <path>/proc/sys/net/ipv4/ip_local_port_range</path> = "2048 32767". |
292 | <path>/proc/sys/net/ipv4/ip_local_port_range</path> = "2048 32767". |
| 293 | See <uri |
293 | See <uri |
| 294 | link="/doc/en/handbook/handbook-mips.xml?part=1&chap=2#doc_chap4">the |
294 | link="/doc/en/handbook/handbook-mips.xml?part=1&chap=2#doc_chap4">the |
| 295 | Gentoo/MIPS handbook</uri>. |
295 | Gentoo/MIPS handbook</uri>. |
| 296 | </li> |
296 | </li> |
| 297 | <li> |
297 | <li> |
| 298 | <b>Is the server giving out the correct details via BOOTP?</b><br /> |
298 | <b>Is the server giving out the correct details via BOOTP?</b><br /> |
| 299 | Double check your <path>/etc/dhcp/dhcpd.conf</path>. ISC's dhcpd won't dish |
299 | Double check your <path>/etc/dhcp/dhcpd.conf</path>. ISC's dhcpd won't dish |
| 300 | out addressing information via BOOTP unless the machine has been statically |
300 | out addressing information via BOOTP unless the machine has been statically |
| 301 | defined with a fixed address. |
301 | defined with a fixed address. |
| 302 | </li> |
302 | </li> |
| 303 | <li> |
303 | <li> |
| 304 | <b>Which TFTP server are you using?</b><br /> |
304 | <b>Which TFTP server are you using?</b><br /> |
| 305 | <c>tftp-hpa</c> and <c>netkit-tftp</c> are known to work. <c>atftp</c> is a |
305 | <c>tftp-hpa</c> is known to work. <c>atftp</c> is a lot more advanced, this |
| 306 | lot more advanced, this can cause problems. If in doubt, try installing |
306 | can cause problems. If in doubt, try installing <c>tftp-hpa</c> and see if |
| 307 | <c>tftp-hpa</c> and see if the problem clears up. |
307 | the problem clears up. |
| 308 | </li> |
308 | </li> |
| 309 | <li> |
309 | <li> |
| 310 | <b>Are the daemons running?</b><br /> |
310 | <b>Are the daemons running?</b><br /> |
| 311 | <c>dhcpd</c> should show up when typing <c>ps ax</c>. As for TFTP, it'll |
311 | <c>dhcpd</c> should show up when typing <c>ps ax</c>. As for TFTP, it'll |
| 312 | largely depend on whether its a standalone server, or if its running from |
312 | largely depend on whether its a standalone server, or if its running from |
| 313 | <c>(x)inetd</c>. <c>tftp-hpa</c> runs as a process called <c>in.tftpd</c>. |
313 | <c>(x)inetd</c>. <c>tftp-hpa</c> runs as a process called <c>in.tftpd</c>. |
| 314 | Look for that in the <c>ps ax</c> output and start any services not |
314 | Look for that in the <c>ps ax</c> output and start any services not |
| 315 | currently running. |
315 | currently running. |
| 316 | </li> |
316 | </li> |
| 317 | <li> |
317 | <li> |
| 318 | <b>Does the kernel exist in <path>/tftpboot</path>?</b><br /> |
318 | <b>Does the kernel exist in <path>/tftpboot</path>?</b><br /> |
| 319 | Make sure you place the kernel image to be booted in this directory and |
319 | Make sure you place the kernel image to be booted in this directory and |
| 320 | that it is world-readable. (<c>chmod 644 /tftpboot/foo</c>) Also, in your |
320 | that it is world-readable. (<c>chmod 644 /tftpboot/foo</c>) Also, in your |
| 321 | <path>/etc/dhcp/dhcpd.conf</path>, note that the path to the kernel will be |
321 | <path>/etc/dhcp/dhcpd.conf</path>, note that the path to the kernel will be |
| 322 | relative to the <path>/tftpboot</path> directory if you're using |
322 | relative to the <path>/tftpboot</path> directory if you're using |