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

Contents of /xml/htdocs/doc/en/gentoo-alpha-faq.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.4 - (show annotations) (download) (as text)
Fri Jul 13 18:39:46 2007 UTC (7 years, 3 months ago) by yoswink
Branch: MAIN
Changes since 1.3: +41 -22 lines
File MIME type: application/xml
Added a troubleshooting section with the AS800 xorg lock and removed/fixed sections mentioning old compaq java. Thanks to Brian Evans

1 <?xml version="1.0" encoding="UTF-8"?>
2 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-alpha-faq.xml,v 1.3 2006/06/22 20:01:26 nightmorph Exp $ -->
3
4 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 <guide link="/doc/en/gentoo-alpha-faq.xml">
6
7 <title>Gentoo Linux/Alpha Frequently Asked Questions</title>
8 <author title="Author">
9 <mail link="tcort@gentoo.org">Thomas Cort</mail>
10 </author>
11 <author title="Author">
12 <mail link="grknight2k@bluebottle.com">Brian Evans</mail>
13 </author>
14
15 <abstract>
16 This FAQ is intended to answer some of the most frequently asked questions
17 relating to Gentoo/Alpha and Linux/Alpha in general.
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.5 -->
22 <license/>
23
24 <version>1.3</version>
25 <date>2007-07-13</date>
26
27 <chapter>
28 <title>About this Document</title>
29
30 <section>
31 <title>Introduction</title>
32 <body>
33
34 <p>
35 This document contains answers to the most commonly asked questions about
36 Gentoo/Alpha and Alpha/Linux. It's aimed at both new users and experienced
37 users alike.
38 </p>
39
40
41 </body>
42 </section>
43
44 <section>
45 <title>Content</title>
46 <body>
47
48 <p>
49 <b>About the Gentoo/Alpha Project</b>
50 </p>
51
52 <ul>
53 <li><uri link="#what">What is Gentoo/Alpha?</uri></li>
54 <li>
55 <uri link="#status">
56 What is the current status of the Gentoo/Alpha Project?
57 </uri>
58 </li>
59 </ul>
60
61 <p>
62 <b>The Alpha Architecture</b>
63 </p>
64
65 <ul>
66 <li><uri link="#dead">Isn't the Alpha architecture dead?</uri></li>
67 <li><uri link="#bitapps">Can I run 32-bit applications?</uri></li>
68 <li><uri link="#endian">Is Alpha big endian or little endian?</uri></li>
69 <li><uri link="#i386">Can I run Linux/x86 applications on Alpha?</uri></li>
70 <li><uri link="#why">Why install Gentoo on Alpha?</uri></li>
71 <li><uri link="#where">Where can I buy Alpha hardware?</uri></li>
72 </ul>
73
74 <p>
75 <b>Hardware</b>
76 </p>
77
78 <ul>
79 <li>
80 <uri link="#ascase">I opened up the case on an AlphaServer and now it won't
81 power on, what do I do?</uri>
82 </li>
83 </ul>
84
85 <p>
86 <b>Alpha Specific Compiler Flags</b>
87 </p>
88
89 <ul>
90 <li>
91 <uri link="#CFLAGS">
92 Is the use of Alpha specific compiler flags recommended?
93 </uri>
94 </li>
95 <li>
96 <uri link="#MCPU">
97 How do I optimize for a specific instruction set and scheduling model?
98 </uri>
99 </li>
100 <li>
101 <uri link="#MTUNE">
102 How do I specify the scheduling model without changing the instruction
103 set?
104 </uri>
105 </li>
106 <li>
107 <uri link="#mieee">
108 How do I enable software assisted floating point numbers?
109 </uri>
110 </li>
111 <li>
112 <uri link="#MEMLAT">How do I specify the memory latency of my system?</uri>
113 </li>
114 <li>
115 <uri link="#SMALLDATA">
116 How do I specify that static data should be placed in the small data area?
117 </uri>
118 </li>
119 <li>
120 <uri link="#SMALLTEXT">
121 How do I specify that object code should be placed in the small text area?
122 </uri>
123 </li>
124 <li>
125 <uri link="#CFLAGSERR">
126 What do I do if any of these compiler flags cause a compile, linker, or
127 runtime error?
128 </uri>
129 </li>
130 </ul>
131
132 <p>
133 <b>Alpha Booting and Bootloaders</b>
134 </p>
135
136 <ul>
137 <li><uri link="#SRM">What is SRM?</uri></li>
138 <li><uri link="#ARC">What is ARC?</uri></li>
139 <li>
140 <uri link="#ARCvsSRM">
141 How can I tell if which firmware my Alpha has, ARC or SRM?
142 </uri>
143 </li>
144 <li><uri link="#whichbootloader">Which bootloader do I use?</uri></li>
145 <li>
146 <uri link="#abootfs">
147 Can aboot boot kernels from xfs, reiserfs, or jfs partitions?
148 </uri>
149 </li>
150 </ul>
151
152 <p>
153 <b>Software</b>
154 </p>
155
156 <ul>
157 <li><uri link="#javasupport">How is Java support in Gentoo/Alpha?</uri></li>
158 <li>
159 <uri link="#currentjava">Will there ever be working Java support?</uri>
160 </li>
161 <li><uri link="#dotnetsupport">How is .NET support in Gentoo/Alpha?</uri></li>
162 <li>
163 <uri link="#dotnetneeded">What is needed for .NET support?</uri>
164 </li>
165 </ul>
166
167 <p>
168 <b>Alpha Linux Kernel</b>
169 </p>
170
171 <ul>
172 <li><uri link="#whichkernel">Which kernel sources should I use?</uri></li>
173 <li><uri link="#selinux">Are hardened-sources supported?</uri></li>
174 <li><uri link="#smpkernel">Does the 2.6 kernel support Alpha SMP?</uri></li>
175 </ul>
176
177 <p>
178 <b>Helping out the Gentoo/Alpha Project</b>
179 </p>
180
181 <ul>
182 <li><uri link="#bugs">How do I report bugs?</uri></li>
183 <li><uri link="#project">How can I help the Gentoo/Alpha Project?</uri></li>
184 <li><uri link="#archtest">Is there an Alpha Arch Testers Project?</uri></li>
185 </ul>
186
187 <p>
188 <b>Troubleshooting</b>
189 </p>
190
191 <ul>
192 <li><uri link="#tshoot-xorg">Why is my Xorg locking up my Alpha?</uri></li>
193 </ul>
194
195 <p>
196 <b>Other Resources</b>
197 </p>
198
199 <ul>
200 <li><uri link="#noforum">Why is there no Gentoo on Alpha forum?</uri></li>
201 <li>
202 <uri link="#othergentoo">
203 Where can I get more help or information about Gentoo/Alpha?
204 </uri>
205 </li>
206 <li>
207 <uri link="#other">
208 Where can I get more help or information about Alpha/Linux?
209 </uri>
210 </li>
211 </ul>
212
213 </body>
214 </section>
215 </chapter>
216
217 <chapter>
218 <title>About the Gentoo/Alpha Project</title>
219 <section id="what">
220 <title>What is Gentoo/Alpha?</title>
221 <body>
222
223 <p>
224 The Gentoo/Alpha project is responsible for keeping the Gentoo distribution
225 updated and current for the Alpha platform. This primarily includes keywording
226 packages, porting software, and making new releases. The Gentoo/Alpha project
227 aims to provide a usable environment for both desktops and servers.
228 </p>
229
230 </body>
231 </section>
232 <section id="status">
233 <title>What is the current status of the Gentoo/Alpha Project?</title>
234 <body>
235
236 <p>
237 You can find out about the current status of the Gentoo/Alpha project via
238 status reports. These reports inform the public about what we've been up to.
239 New status reports will be posted about once every 6 months. Current and past
240 status report can be found on the <uri
241 link="/proj/en/base/alpha/status/index.xml">Status Reports Project page</uri>.
242 </p>
243
244 </body>
245 </section>
246 </chapter>
247
248 <chapter>
249 <title>The Alpha Architecture</title>
250 <section id="dead">
251 <title>Isn't the Alpha architecture dead?</title>
252 <body>
253
254 <p>
255 Not yet! HP will be taking orders for new Alpha systems until October 27, 2006
256 and Alpha options and upgrades until November 2, 2007. See their <uri
257 link="http://h18002.www1.hp.com/alphaserver/planning2005.html">planning
258 page</uri> for more details.
259 </p>
260
261 </body>
262 </section>
263 <section id="bitapps">
264 <title>Can I run 32-bit applications?</title>
265 <body>
266
267 <p>
268 No, all Alpha systems use a pure 64 bit kernel and a pure 64 bit userland. You
269 cannot even force gcc to output 32 bit code using the <c>-m32</c> compiler
270 flag.
271 </p>
272
273 </body>
274 </section>
275 <section id="endian">
276 <title>Is Alpha big endian or little endian?</title>
277 <body>
278
279 <p>
280 All Alpha systems support both little and big endian. However, Linux only uses
281 little endian.
282 </p>
283
284 </body>
285 </section>
286 <section id="i386">
287 <title>Can I run Linux/x86 applications on Alpha?</title>
288 <body>
289
290 <p>
291 No, not without a full x86 system emulator like <uri
292 link="http://bochs.sourceforge.net/">bochs</uri>. In the past DEC/Compaq/HP
293 maintained a program called <c>em86</c> which allowed Linux/x86 applications to
294 be run on Linux/Alpha systems. However, the program is closed source and no
295 longer maintained upstream. There are no <c>em86</c> binaries available that
296 are compatible with gcc3's ABI.
297 </p>
298
299 </body>
300 </section>
301 <section id="why">
302 <title>Why install Gentoo on Alpha?</title>
303 <body>
304
305 <p>
306 Admittedly, you can find faster 64-bit systems out there, like amd64. However,
307 that doesn't mean that Alpha systems are useless. The following are a few good
308 reasons why you'd want to install Linux on this sort of hardware:
309 </p>
310
311 <ul>
312 <li>
313 You can turn an old computer into something useful. Older Alphas make great
314 routers and servers. Their desktop performance isn't that bad either.
315 </li>
316 <li>You will learn about unusual computer hardware.</li>
317 <li>
318 It's cool. How many people can say they've got Linux running on an Alpha?
319 </li>
320 </ul>
321
322 </body>
323 </section>
324 <section id="where">
325 <title>Where can I buy Alpha hardware?</title>
326 <body>
327
328 <p>
329 Alpha hardware generally isn't available at your local computer store. If you
330 want a new Alpha you're going to have to contact <uri
331 link="http://h18002.www1.hp.com/alphaserver/">HP</uri>. If you want a used
332 Alpha (more economical), <uri link="http://ebay.com">eBay</uri> is usually a
333 good option, assuming that the shipping doesn't cost you too much. There are
334 several used equipment dealers that can be found via google, however most of
335 them charge too much.
336 </p>
337
338 </body>
339 </section>
340 </chapter>
341
342 <chapter>
343 <title>Hardware</title>
344 <section id="ascase">
345 <title>I opened up the case on an AlphaServer and now it won't power
346 on, what do I do?</title>
347 <body>
348
349 <p>
350 Make sure the top panel of the case is on and properly in place. The middle of
351 the top panel of the case has a small piece of metal oriented downwards. When
352 the top panel is put back in place properly, the small piece of metal will
353 press down on a switch. When the switch isn't pressed down, the system will
354 refuse to power on.
355 </p>
356
357 </body>
358 </section>
359 </chapter>
360
361 <chapter>
362 <title>Alpha Specific Compiler Flags</title>
363 <section id="CFLAGS">
364 <title>Is the use of Alpha specific compiler flags recommended?</title>
365 <body>
366
367 <p>
368 As with all compiler optimizations, don't over do it. Use these flags with care
369 and they will give you a stable, speedy system; use them too aggressively and
370 you could seriously break your system. When in doubt, leave it out. If you need
371 further clarification, check the <c>gcc</c> man page.
372 </p>
373
374 </body>
375 </section>
376 <section id="MCPU">
377 <title>
378 How do I optimize for a specific instruction set and scheduling model?
379 </title>
380 <body>
381
382 <p>
383 You can optimize for a specific instruction set and scheduling model with
384 <c>-mcpu=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>,
385 <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>.
386 If you do not use the <c>-mcpu=XXX</c> flag, then <c>gcc</c> will default to
387 the cpu type of the machine it was compiled on. <c>-mcpu=</c> is equivalent to
388 the <c>-march=</c> flag on x86.
389 </p>
390
391 <note>
392 AlphaServer 800 users should set <c>ev5</c>. There are known issues setting
393 <c>ev56</c> particularly with Xorg causing a full system lock up.
394 </note>
395
396 </body>
397 </section>
398 <section id="MTUNE">
399 <title>
400 How do I specify the scheduling model without changing the instruction set?
401 </title>
402 <body>
403
404 <p>
405 You can specify the scheduling model without changing the instruction set with
406 <c>-mtune=XXX</c>, where XXX is your cpu type. Valid cpu types are <c>ev4</c>,
407 <c>ev45</c>, <c>ev5</c>, <c>ev56</c>, <c>pca56</c>, <c>ev6</c> and <c>ev67</c>.
408 <c>-mtune=</c> is implied by <c>-mcpu=</c>, so you don't need to specify this
409 with if you set <c>-mcpu=</c>. <c>-mtune=</c> is equivalent to the
410 <c>-mcpu=</c> flag on x86.
411 </p>
412
413 </body>
414 </section>
415 <section id="mieee">
416 <title>How do I enable software assisted floating point numbers?</title>
417 <body>
418
419 <p>
420 You can enable software assisted floating point numbers with <c>-mieee</c>.
421 This will enable software assistance to correctly support denormalized numbers
422 and exceptional IEEE values such as not-a-number and plus/minus infinity.
423 </p>
424
425 <p>
426 This should be in your global <c>CFLAGS</c> unless you really know what you are
427 doing.
428 </p>
429
430 </body>
431 </section>
432 <section id="MEMLAT">
433 <title>How do I specify the memory latency of my system?</title>
434 <body>
435
436 <p>
437 You can specify the memory latency of your system with
438 <c>-mmemory-latency=XXX</c>, where XXX is the number of clock cycles. This sets
439 the latency time that the scheduler should assume for memory references.
440 <c>gcc</c> has some predefined "typical" values that are also accepted by
441 <c>-mmemory-latency=XXX</c>. Those values are <c>L1</c> for Dcache, <c>L2</c>
442 for Scache, <c>L3</c> for Bcache, and <c>main</c> for main memory.
443 </p>
444
445 <p>
446 This flag should probably not be use in your global <c>CFLAGS</c> as the value
447 you choose is highly dependent on the memory access pattern of the application
448 you are compiling.
449 </p>
450
451 </body>
452 </section>
453 <section id="SMALLDATA">
454 <title>
455 How do I specify that static data should be placed in the small data area?
456 </title>
457 <body>
458
459 <p>
460 You can specify that static data should be placed in the small data area with
461 <c>-msmall-data</c>. This will cause <c>gcc</c> to take advantage of some
462 features of the Alpha architecture by storing heavily used pieces of data in
463 specific sections called the small memory sections. The sections are limited to
464 64kb which means accessing anything stored in them will only take one
465 instruction.
466 </p>
467
468 <p>
469 <c>-fPIC</c> will override <c>-msmall-data</c>, so you should use the
470 <c>-fpic</c> flag instead if you do not want <c>-msmall-data</c> to be
471 overridden.
472 </p>
473
474 <p>
475 This flag should probably not be used in your global <c>CFLAGS</c> as some
476 objects require more than 64kb to be stored, and this will cause a gp_overflow
477 ld error.
478 </p>
479
480 </body>
481 </section>
482 <section id="SMALLTEXT">
483 <title>
484 How do I specify that object code should be placed in the small text area?
485 </title>
486 <body>
487
488 <p>
489 You can specify that object code should be placed in the small text area with
490 <c>-msmall-text</c>. This will cause <c>gcc</c> to assume that the entire
491 program (or library) fits in 4MB, and is thus reachable with a branch
492 instruction. This reduces the number of instructions required for a function
493 call from 4 to 1.
494 </p>
495
496 <p>
497 This flag should probably not be used in your global <c>CFLAGS</c> as some
498 programs (or libraries) are larger than 4MB, and this will cause an ld error.
499 </p>
500
501 </body>
502 </section>
503 <section id="CFLAGSERR">
504 <title>
505 What do I do if any of these compiler flags cause a compile, linker, or
506 runtime error?
507 </title>
508 <body>
509
510 <p>
511 As <uri link="#CFLAGS">already mentioned</uri>, please use these <c>CFLAGS</c>
512 cautiously. They may break your system. If you experience problems, try using
513 less aggressive <c>CFLAGS</c> before <uri link="#bugs">filing a bug
514 report</uri>.
515 </p>
516
517 </body>
518 </section>
519 </chapter>
520
521 <chapter>
522 <title>Alpha Booting and Bootloaders</title>
523 <section id="SRM">
524 <title>What is SRM?</title>
525 <body>
526
527 <p>
528 SRM is based on the Alpha Console Subsystem specification, which provides an
529 operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. See
530 the <uri link="http://www.alphalinux.org/faq/SRM-HOWTO/"> SRM Howto</uri> for
531 more information about SRM.
532 </p>
533
534 </body>
535 </section>
536 <section id="ARC">
537 <title>What is ARC?</title>
538 <body>
539
540 <p>
541 ARC is based on the Advanced RISC Computing (ARC) specification, which provides
542 an operating environment for Windows NT.
543 </p>
544
545 </body>
546 </section>
547 <section id="ARCvsSRM">
548 <title>How can I tell if which firmware my Alpha has, ARC or SRM?</title>
549 <body>
550
551 <p>
552 When you power your system on you will see a screen with a blue background and
553 white text if it is using SRM. You will see a graphical boot system if it is
554 using ARC.
555 </p>
556
557 </body>
558 </section>
559 <section id="whichbootloader">
560 <title>Which bootloader do I use?</title>
561 <body>
562
563 <p>
564 If your Alpha system supports SRM, then you should use aboot. If your system
565 supports both SRM and ARCs (ARC, AlphaBIOS, ARCSBIOS), then you should follow
566 <uri link="http://www.alphalinux.org/faq/x31.html">the SRM Firmware Howto</uri>
567 for switching to SRM and use aboot. If your system can only use ARCs (Ruffian,
568 nautilus, xl, etc.) then you will need to choose milo.
569 </p>
570
571 </body>
572 </section>
573 <section id="abootfs">
574 <title>Can aboot boot kernels from xfs, reiserfs, or jfs partitions?</title>
575 <body>
576
577 <p>
578 No, <c>aboot</c> only supports booting kernels from <c>ext2</c> and <c>ext3</c>
579 partitions. You may still use other files systems for your root partition, you
580 just need to create a <path>/boot</path> partition with either <c>ext2</c> or
581 <c>ext3</c> on it.
582 </p>
583
584 <p>
585 Support for reiserfs and xfs is planned. In fact, there are patches floating
586 around that add support for those two file systems. However, the use of those
587 patches is unsupported.
588 </p>
589
590 </body>
591 </section>
592 </chapter>
593 <chapter>
594 <title>Software</title>
595
596 <section id="javasupport">
597 <title>How is Java support in Gentoo/Alpha?</title>
598 <body>
599
600 <p>
601 There was only one option for Java VM and Java SDK on Gentoo/Alpha.
602 The packages are called <c>compaq-jre</c> and <c>compaq-jdk</c>.
603 Sadly, Compaq/HP stopped all support and was removed from Gentoo on
604 October 11, 2006.
605 </p>
606
607 </body>
608 </section>
609
610 <section id="currentjava">
611 <title>Will there ever be working Java support?</title>
612 <body>
613
614 <p>
615 We really hope so. We are following the development of the jdk from <uri
616 link="http://sablevm.org">SableVM</uri>. It isn't ready yet, but we hope with
617 time that it will be a full drop in replacement jdk.
618 </p>
619
620 </body>
621 </section>
622 <section id="dotnetsupport">
623 <title>How is .NET support in Gentoo/Alpha?</title>
624 <body>
625
626 <p>
627 Neither of the two main open source efforts, <uri
628 link="http://www.mono-project.com/Main_Page">mono</uri> nor <uri
629 link="http://www.dotgnu.org/">DotGNU</uri>, support the alpha architecture.
630 </p>
631
632 </body>
633 </section>
634 <section id="dotnetneeded">
635 <title>What is needed for .NET support?</title>
636 <body>
637
638 <p>
639 Bringing .NET to alpha isn't a simple task. It requires coding all of the
640 assembly language code generation macros for the JIT (just in time) compiler
641 and coding architecture specific functions (register allocators, etc).
642 </p>
643
644 </body>
645 </section>
646 </chapter>
647
648 <chapter>
649 <title>Alpha Linux Kernel</title>
650 <section id="whichkernel">
651 <title>Which kernel sources should I use?</title>
652 <body>
653
654 <p>
655 <c>gentoo-sources</c> and <c>vanilla-sources</c> are both supported. You
656 should read the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>
657 to determine which one is right for your needs.
658 </p>
659
660 </body>
661 </section>
662 <section id="selinux">
663 <title>Are hardened-sources supported?</title>
664 <body>
665
666 <p>
667 <c>hardened-sources</c> and SELinux support is being worked on by Stephen
668 Bennett (<mail link="spb@gentoo.org">spb</mail>). <c>hardened-sources</c> is
669 currently keyworded for alpha. We hope to see an SELinux profile for Alpha in
670 the tree as soon as we feel confident about it.
671 </p>
672
673 </body>
674 </section>
675 <section id="smpkernel">
676 <title>Does the 2.6 kernel support Alpha SMP?</title>
677 <body>
678
679 <p>
680 There were some times in the past when it was broken. However, <c>2.6.15.1</c>
681 and <c>2.6.16.19</c> are both known to work well. If you find that SMP is
682 broken and want SMP support you will need revert to the one of the versions
683 mentioned above or use a 2.4 kernel. If you really need to run the latest 2.6
684 kernel on an SMP box and you don't care that only one of your processors is
685 getting used, then you could configure the 2.6 kernel without SMP support.
686 </p>
687
688 </body>
689 </section>
690 </chapter>
691
692 <chapter>
693 <title>Helping out the Gentoo/Alpha Project</title>
694 <section id="bugs">
695 <title>How do I report bugs?</title>
696 <body>
697
698 <p>
699 If you find a bug or you want to send us patches, then you need to file a bug
700 report. It only takes you a little bit of your time, and your help is really
701 appreciated. Please follow the <uri link="/doc/en/bugzilla-howto.xml">Gentoo
702 Bug Reporting Guide</uri>.
703 </p>
704
705 </body>
706 </section>
707 <section id="project">
708 <title>How can I help the Gentoo/Alpha Project?</title>
709 <body>
710
711 <p>
712 Users can help us by:
713 </p>
714
715 <ul>
716 <li>Filing clear and concise <uri link="#bugs">bug reports</uri>.</li>
717 <li>Testing software that does not yet have the <c>~alpha</c> keyword.</li>
718 <li>
719 Answering questions on the <uri link="/main/en/lists.xml">mailing
720 lists</uri>, <uri link="http://forums.gentoo.org/viewforum-f-32.html">
721 forum</uri> and IRC channel.
722 </li>
723 <li>Sending patches</li>
724 <li>Becoming an <uri
725 link="http://www.gentoo.org/proj/en/base/alpha/AT/index.xml">AT</uri>
726 </li>
727 </ul>
728
729 </body>
730 </section>
731 <section id="archtest">
732 <title>Is there an Alpha Arch Testers Project?</title>
733 <body>
734
735 <p>
736 Yes, see the <uri link="http://www.gentoo.org/proj/en/base/alpha/AT/index.xml">
737 Gentoo Linux Alpha Arch Testers Project</uri> page for details.
738 </p>
739
740 </body>
741 </section>
742 </chapter>
743
744 <chapter>
745 <title>Troubleshooting</title>
746 <section id="tshoot-xorg">
747 <title>Why is my Xorg locking up my Alpha?</title>
748 <body>
749
750 <p>
751 This is usually caused by a bad -mcpu setting. For example, the AlphaServer
752 800 needs to be compiled with the <c>ev5</c> flag for xorg <b>and</b> glibc.
753 Failing to do so will cause undesired results.
754 </p>
755
756 </body>
757 </section>
758 </chapter>
759
760 <chapter>
761 <title>Other Resources</title>
762 <section id="noforum">
763 <title>Why is there no Gentoo on Alpha forum?</title>
764 <body>
765
766 <p>
767 On the <uri link="http://forums.gentoo.org">Gentoo Forums</uri> there are
768 several arch specific categories like <uri
769 link="http://forums.gentoo.org/viewforum-f-24.html">Gentoo on PPC</uri> and
770 <uri link="http://forums.gentoo.org/viewforum-f-24.html">Gentoo on
771 Sparc</uri>. There is no Gentoo on Alpha category because there simply isn't
772 enough Gentoo/Alpha activity on the forums to warrant one. All Alpha related
773 posts should go in the <uri
774 link="http://forums.gentoo.org/viewforum-f-32.html"> Gentoo on Alternative
775 Architectures</uri> category.
776 </p>
777
778 </body>
779 </section>
780 <section id="othergentoo">
781 <title>Where can I get more help or information about Gentoo/Alpha?</title>
782 <body>
783
784 <p>
785 If any of your questions weren't answered here, you can try other resources
786 like the <uri link="/doc/en/handbook/handbook-alpha.xml">Alpha Handbook</uri>
787 or <uri link="/proj/en/base/alpha/">our project homepage</uri>. You can also
788 ask us at <c>#gentoo-alpha</c> on <c>irc.freenode.net</c>, <uri
789 link="http://forums.gentoo.org/viewforum-f-32.html">Gentoo on Alternative
790 Architectures Forum</uri>, or on the <mail>gentoo-alpha@lists.gentoo.org</mail>
791 mailing list.
792 </p>
793
794 </body>
795 </section>
796 <section id="other">
797 <title>Where can I get more help or information about Alpha/Linux?</title>
798 <body>
799
800 <p>
801 <uri link="http://alphalinux.org/">AlphaLinux.org</uri> is a central repository
802 for all things Alpha/Linux.
803 </p>
804
805 </body>
806 </section>
807 </chapter>
808 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20