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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.14 - (show annotations) (download) (as text)
Sun Jul 1 03:03:39 2007 UTC (7 years, 2 months ago) by nightmorph
Branch: MAIN
Changes since 1.13: +44 -46 lines
File MIME type: application/xml
a few updates from the patch on bug 183783, and lots of other updates that i made as i went along reading the doc. it was pretty outdated. should be shiny now.

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-faq.xml,v 1.13 2006/12/04 21:17:14 jkt Exp $ -->
3
4 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 <guide link="/doc/en/gentoo-sparc-faq.xml">
6 <title>Gentoo Linux/SPARC Frequently Asked Questions</title>
7
8 <author title="SPARC Developer">
9 <mail link="weeve@gentoo.org">Jason Wever</mail>
10 </author>
11
12 <abstract>
13 This FAQ is designed to help answer the most commonly asked questions about
14 Gentoo Linux/SPARC and Linux on SPARC architecture. Feel free to send
15 revisions and corrections to the sparc team or the doc team.
16 </abstract>
17
18 <!-- The content of this document is licensed under the CC-BY-SA license -->
19 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
20 <license/>
21
22 <version>1.9</version>
23 <date>2007-06-30</date>
24
25 <chapter>
26 <title>Documentation Notes</title>
27 <section>
28 <body>
29
30 <p>
31 These are some notes to elaborate on acronyms and terms used in this document.
32 </p>
33
34 <p>
35 When mentioning <c>SPARC</c>, this refers to the type of <c>sun4x</c> system.
36 SPARC represents the <c>sun4u</c> architecture seen in the UltraSPARC series of
37 systems (Ultras, Blades, SunFires, etc). Older 32-bit systems are no longer
38 supported by the Gentoo/SPARC team.
39 </p>
40
41 <p>
42 Acronyms: <c>OBP</c> = OpenBoot PROM, <c>SS</c> = SPARCstation.
43 </p>
44
45 </body>
46 </section>
47 </chapter>
48
49 <chapter>
50 <title>Installation</title>
51 <section>
52 <title>How do I install/use my SPARC over a serial console?</title>
53 <body>
54
55 <p>
56 First, make sure you do not have a keyboard and monitor plugged in. OBP will
57 use the monitor for output by default if either are plugged in. You will need a
58 null modem cable or a regular serial cable with a null modem adapter to be able
59 to view output.
60 </p>
61
62 <p>
63 Standard serial port settings:
64 </p>
65
66 <ul>
67 <li>9600 baud</li>
68 <li>8 data bits</li>
69 <li>None for parity</li>
70 <li>1 stop bits</li>
71 </ul>
72
73 <p>
74 Below is a list of commonly used programs for viewing a serial console. Check
75 to see if your serial console application has the ability to send a break, as
76 it can be very useful on a SPARC. The break signal on a serial console is the
77 equivalent to issuing the Stop+A command on the keyboard.
78 </p>
79
80 <table>
81 <tr>
82 <th>Linux</th>
83 <th>Windows</th>
84 </tr>
85 <tr>
86 <ti>Minicom</ti>
87 <ti>Hyperterm</ti>
88 </tr>
89 <tr>
90 <ti>Kermit</ti>
91 <ti>TeraTerm Pro</ti>
92 </tr>
93 <tr>
94 <ti>Console</ti>
95 <ti></ti>
96 </tr>
97 <tr>
98 <ti>Seyon</ti>
99 <ti></ti>
100 </tr>
101 </table>
102
103 </body>
104 </section>
105 <!-- sparc32 is no longer supported
106 <section>
107 <title>How do I network boot my SPARC system for installation?</title>
108 <body>
109
110 <p>
111 Currently, Gentoo has experimental network boot/tftpboot images available on a
112 local Gentoo mirror in experimental/sparc/tftpboot. Get the appropriate image
113 for your SPARC computer and then proceed to the Netboot HOWTO for further
114 instructions.
115 </p>
116
117 </body>
118 </section>
119 -->
120 <section>
121 <title>I have a CRT/LCD monitor attached to my SPARC that selects a resolution
122 my monitor can't handle when the kernel boots. How do I get a visible and/or
123 non-distorted display on my monitor?</title>
124 <body>
125
126 <p>
127 This problem is a result of the framebuffer support the Linux kernel loads at
128 boot time, and the modelines available on SPARC systems. Here we will assume
129 your monitor and video card will agree on a resolution of 1024 by 768 at a
130 refresh rate of 60 Hz. In OBP, you can set the resolution by adjusting the
131 setting for <c>output-device</c>. To view the current setting, use the command:
132 </p>
133
134 <pre caption="View current settings">
135 ok <i>printenv output-device</i>
136
137 <comment>&lt;output-device&gt; &lt;screen&gt; &lt;screen&gt;</comment>
138 </pre>
139
140 <p>
141 Now, to set this so it will start the display using the above mentioned
142 resolution, we will use the <c>setenv</c> command as follows:
143 </p>
144
145 <pre caption="Setting display">
146 ok <i>setenv output-device screen:r1024x768x60</i>
147
148 output-device = screen:r1024x768x60
149 </pre>
150
151 <p>
152 In order for this to take effect, you will need to reset the machine:
153 </p>
154
155 <pre caption="Resetting the machine">
156 ok <i>reset</i>
157 </pre>
158
159 <p>
160 Additionally, for users using the onboard video card based on the ATI Mach64
161 chipset (Ultra 5/10 and Blade 100/150), you will want to append the following
162 to your kernel boot options:
163 </p>
164
165 <pre caption="Appending a kernel boot option">
166 video=atyfb:1024x768@60
167 </pre>
168
169 <p>
170 If you are booting from SILO, you can append the above string onto the end of a
171 given boot image. The following example would be if you were booting from the
172 LiveCD.
173 </p>
174
175 <pre caption="Booting a Gentoo LiveCD">
176 boot: <i>gentoo video=atyfb:1024x768@60</i>
177 </pre>
178
179 <p>
180 If you were booting from the network, you would append the string onto the end
181 of the boot net command in OBP as illustrated below:
182 </p>
183
184 <pre caption="Booting from the net">
185 ok <i>boot net video=atyfb:1024x768@60</i>
186 </pre>
187
188 </body>
189 </section>
190 <section>
191 <title>I'm new to SPARC and am not sure what kernel options to use,
192 HELP!</title>
193 <body>
194
195 <p>
196 Most of the time, the default kernel options will be acceptable for hardware
197 support. You will need to make sure that <c>virtual memory</c> and <c>/proc
198 filesystem</c> support is enabled in the kernel as instructed in the <uri
199 link="/doc/en/handbook/handbook-sparc.xml">Installation Handbook</uri>.
200 </p>
201
202 </body>
203 </section>
204 <section>
205 <title>How do I dual boot Gentoo Linux/SPARC with Solaris?</title>
206 <body>
207
208 <p>
209 Dual booting Gentoo Linux/SPARC and Solaris can be done one of two ways. The
210 two ways are: having both Gentoo Linux/SPARC and Solaris on the same drive, or
211 having them on separate drives. Below are example SILO configurations for each
212 scenario. In the example configs, the following things are assumed:
213 </p>
214
215 <p>
216 Single Drive Setup:
217 </p>
218
219 <ul>
220 <li>Boot drive is SCSI ID 0</li>
221 <li>Gentoo boots from partition 1</li>
222 <li>Solaris boots from partition 5</li>
223 </ul>
224
225 <p>
226 Separate Drive Setup:
227 </p>
228
229 <ul>
230 <li>Second drive is SCSI ID 1</li>
231 <li>Gentoo is on SCSI ID 0</li>
232 <li>Solaris is on SCSI ID 1</li>
233 <li>boot-device in OBP is SCSI ID 0</li>
234 </ul>
235
236
237 <pre caption="Sample silo.conf for a single drive installation">
238 <comment># Generic config options</comment>
239 partition = 1
240 timeout = 50
241
242 <comment># Gentoo Linux/SPARC options</comment>
243 image = /boot/vmlinux
244 label = linux
245 root=/dev/sda4
246
247 <comment># Solaris options</comment>
248 other=5
249 label = Solaris
250 </pre>
251
252 <pre caption="Sample silo.conf for separate disk installation">
253 <comment># Generic config options</comment>
254 parition = 1
255 timeout = 50
256
257 <comment># Gentoo Linux/SPARC options</comment>
258 image = /boot/vmlinux
259 label = linux
260 root=/dev/sda4
261
262 <comment># Solaris options</comment>
263 other = /sbus/espdma/esp/sd@1,0;1
264 label = solaris
265 </pre>
266
267 </body>
268 </section>
269 <!-- sparc32 is no longer supported
270 <section>
271 <title>I just booted my SPARCstation after installing Gentoo but it won't boot.
272 Why isn't it booting?</title>
273 <body>
274
275 <p>
276 One possibility has to do with the way the that the SCSI IDs are assigned.
277 Gentoo/SPARC developer Keith Wesolowski provides us with the following:
278 </p>
279
280 <p>
281 Linux, normally, orders devices by SCSI ID. The lowest-numbered disk is
282 <c>sda</c>, the next-lowest is <c>sdb</c>, and so on. Note that <c>devfs</c>
283 allows you to specify devices by SCSI ID, so that adding a new device doesn't
284 cause your existing devices to be renamed, unless of course you use the
285 compatibility names. There are additional ways to solve this.
286 </p>
287
288 <p>
289 The OBP in most or all sun4c and sun4m systems aliases "disk" to the device with
290 SCSI ID 3, and "disk0" through "disk3" to the device with the corresponding SCSI
291 ID, if it happens to be a disk rather than a tape, CDROM, etc.
292 </p>
293
294 <p>
295 In the desktop systems of this era that support two SCA disks (the Aurora
296 chassis systems), the lower slot is assigned SCSI ID 3, and the upper slot is
297 assigned SCSI ID 1.
298 </p>
299
300 <p>
301 If you like, you can change the PROM alias "disk" to match that of "disk1" so
302 that the <c>boot disk</c> command causes the system to boot from the same
303 device Linux calls <c>sda</c>. This feels more consistent and normal,
304 especially for users with a PC background. Alternatively, you can simply place
305 the filesystem containing <path>/boot</path> (which could be the root
306 filesystem or a separate boot filesystem) on device ID 3 (Linux <c>sdb</c>) and
307 boot from it, using a root filesystem on either <c>sda</c> or <c>sdb</c>, or in
308 fact any other disk attached to the system.
309 </p>
310
311 </body>
312 </section>
313 -->
314 </chapter>
315
316 <chapter>
317 <title>Hardware</title>
318 <section>
319 <title>Will Gentoo run on my SPARC?</title>
320 <body>
321
322 <p>
323 It depends on the type of SPARC, but chances are yes. One exception seems to be
324 the SPARC based laptops from Tadpole, particularly the newer models. If you
325 have a working Tadpole on Gentoo/SPARC, please contact us and let us know the
326 details on the model and anything special needed to get it to work.
327 </p>
328
329 <p>
330 The Gentoo/SPARC team maintains a <uri
331 link="/proj/en/base/sparc/sunhw.xml">hardware compatibility list</uri> for
332 SPARC64 systems. In general, support for SPARC64 systems is good enough to
333 allow some users to run it successfully in production environments.
334 </p>
335
336 <p>
337 32-bit SPARC systems are no longer supported by the Gentoo/SPARC team.
338 </p>
339
340 <!-- 32bit is no longer supported
341 <p>
342 32-bit SPARC systems vary. Systems with the sun4m architecture have been
343 reported to work fine (SS4-SS20) including SMP configurations with the later
344 2.4 series kernels. sun4m systems using HyperSPARC or Ross processors in a SMP
345 configuration will have a lot of kernel related trouble. Additionally the
346 author hasn't heard of any user reports in regards to the JavaStations so its
347 status is unknown. sun4d based systems currently do not work in the 2.4 kernel
348 series, and sun4c has been unstable as well.
349 </p>
350
351 <p>
352 Often, the problems encountered in trying to run Gentoo on a 32-bit SPARC
353 system stem from the kernel. Rob Radez (not related to Gentoo) maintains a
354 webpage <uri>http://osinvestor.com/sparc/</uri> with the status of SPARC system
355 support for various versions of the Linux kernel. This can help indicate how
356 usable your SPARC system would be under SPARC/Linux.
357 </p>
358 -->
359
360 </body>
361 </section>
362 <section>
363 <title>What additional hardware is supported under Gentoo/SPARC?</title>
364 <body>
365
366 <p>
367 For a list of additionally supported Sun hardware, consult the following list
368 from the UltraLinux homepage -
369 <uri>http://www.ultralinux.org/faq.html#q_2_2.</uri>
370 </p>
371
372 <p>
373 A partial list of Sun devices which do NOT currently have support under
374 Gentoo/SPARC or SPARC/Linux in general are:
375 </p>
376
377 <ul>
378 <li>SunPCI cards</li>
379 <li>SBUS or PCI PCMCIA controllers</li>
380 <li>Smart card readers on some Sun Blade workstations</li>
381 <li>Floppy drive on some Sun Blade workstations</li>
382 </ul>
383
384 <p>
385 Also, the Gentoo/SPARC team maintains a <uri
386 link="/proj/en/base/sparc/hwlist.xml">list of non-Sun PCI hardware that has
387 been tested on Gentoo/SPARC</uri>. To submit additions to the list, email
388 <mail>sparc@gentoo.org</mail> with the information on the hardware as displayed
389 in the existing hardware list.
390 </p>
391
392 </body>
393 </section>
394 <section>
395 <title>How do I know which Sparc I have?</title>
396 <body>
397
398 <p>
399 The <uri link="http://www.ultralinux.org/faq.html#q_2_1">UltraLinux FAQ</uri>
400 has the answer.
401 </p>
402
403 </body>
404 </section>
405 <section>
406 <title>My box has more than one Sun Ethernet device. Why do they all have the
407 same MAC address and how do I fix it?</title>
408 <body>
409
410 <p>
411 First, the reason they all they all have the same setting is due to a value in
412 OpenBoot PROM (OBP). The story goes that in times past, it was assumed that if a
413 host had multiple interfaces, the interfaces would not reside on the same
414 Ethernet and therefore having the MAC address unique to a machine rather than to
415 a NIC wouldn't be a problem. As time went on and different technologies
416 developed, the opposite was proven.
417 </p>
418
419 <p>
420 As for fixing the issue, there are two ways to it; from OBP and from Linux. The
421 OBP variable <c>local-mac-address?</c> controls this behavior. The following
422 commands will help you to determine what <c>local-mac-address?</c> is set to:
423 </p>
424
425 <pre caption="View local-mac-address? setting from OBP">
426 ok <i>printenv local-mac-address?</i>
427 local-mac-address? = false
428 </pre>
429
430 <pre caption="View local-mac-address? setting from Linux">
431 # <i>eeprom local-mac-address?</i>
432 local-mac-address?=false
433 </pre>
434
435 <p>
436 As you'll notice from the samples above, <c>local-mac-address?</c> is set to
437 <b>false</b>. This will cause all interfaces on a SPARC to use the same MAC
438 address. To change this behavior, use either of the commands below (depending
439 on whether you do it from OBP or Linux):
440 </p>
441
442 <pre caption="Set local-mac-address? from OBP">
443 ok <i>setenv local-mac-address?=true</i>
444 local-mac-address? = true
445 </pre>
446
447 <pre caption="Set local-mac-address? from Linux">
448 # <i>eeprom local-mac-address?=true</i>
449 </pre>
450
451 <p>
452 Note that you may need to reboot to see the changes take affect.
453 </p>
454
455 </body>
456 </section>
457 </chapter>
458
459 <chapter>
460 <title>Applications</title>
461 <section>
462 <title>
463 How do I get Xorg to find a usable modeline on my Ultra 5/10 or Blade 100/150?
464 </title>
465 <body>
466
467 <p>
468 The ATI Framebuffer normally expects a PC's BIOS to set the Reference Clock
469 speed for the video card. However, on non-x86 architectures, this doesn't
470 happen. So what needs to be done is to set the Reference Clock speed in the
471 <path>/etc/X11/xorg.conf</path>.
472 </p>
473
474 <p>
475 In the "Device" section of your <path>/etc/X11/xorg.conf</path>, you will
476 want to add a line similar to the following:
477 </p>
478
479 <pre caption="Add to xorg.conf">
480 Option "reference_clock" "28.636 MHz"
481 </pre>
482
483 <p>
484 Other common speeds are 14.318 MHz and 29.5 MHz. If you have issues you might
485 want to try without a similar setting first.
486 </p>
487
488 </body>
489 </section>
490 <section>
491 <title>How come package foo is masked on Sparc?</title>
492 <body>
493
494 <p>
495 Chances are this is due to the fact that none of the Gentoo/SPARC developers
496 have gotten around to testing this yet, and/or the package is currently marked
497 with the <c>~sparc</c> keyword (meaning it's in a testing phase).
498 </p>
499
500 <p>
501 If you still want to install the package, you can follow the instructions from
502 the <uri link="/doc/en/handbook/handbook-sparc.xml?part=3&amp;chap=3">Portage
503 Handbook</uri>.
504 </p>
505
506 </body>
507 </section>
508 <section>
509 <title>How can I help get package foo marked stable?</title>
510 <body>
511
512 <p>
513 If you want to help ensure a package gets marked stable in a timely fashion,
514 particularly if it's an application with a small userbase (i.e.
515 net-im/bitlbee), install the package and test to make sure it works. If it
516 appears to be working well, feel free to file a bug at
517 <uri>http://bugs.gentoo.org</uri> and assign it to the Gentoo/SPARC team.
518 </p>
519
520 </body>
521 </section>
522 <section>
523 <title>I tried to emerge a package, but emerge failed complaining that a
524 dependency is masked. How can I fix this?</title>
525 <body>
526
527 <p>
528 This is a bug. Please file a bug report at <uri>http://bugs.gentoo.org</uri>
529 for the Gentoo/SPARC team indicating what package you tried to emerge, the
530 error message emerge gave you, and the output of <c>emerge --info</c>.
531 </p>
532
533 </body>
534 </section>
535 </chapter>
536
537 <chapter>
538 <title>Miscellaneous</title>
539 <section>
540 <title>I'm interested in becoming more involved with Gentoo/SPARC. How do I go about
541 doing that?</title>
542 <body>
543
544 <p>
545 The best way is to join the <c>#gentoo-sparc</c> IRC channel on Freenode IRC
546 network <c>irc.freenode.net</c>. This is where all of the developers hang out
547 and talk SPARC (amongst other things). Short of email, this is the best way to
548 get our attention.
549 </p>
550
551 <p>
552 Also, many users and developers make use of the <uri
553 link="http://forums.gentoo.org/viewforum.php?f=27">Gentoo/SPARC forum</uri>.
554 This is a good place to ask questions and see what problems have come up
555 before, as well as talk shop about Gentoo/SPARC.
556 </p>
557
558 <p>
559 Additionally, you can view the bugs for Gentoo/SPARC via the <uri
560 link="http://bugs.gentoo.org">Gentoo Bugzilla</uri>. The bugs will be assigned
561 or CCed to sparc@gentoo.org.
562 </p>
563
564 </body>
565 </section>
566 <section>
567 <title>Are there any currently known bugs/issues with software packages on
568 Gentoo/SPARC?</title>
569 <body>
570
571 <p>
572 A list of problematic packages can be found at
573 <uri>http://dev.gentoo.org/~weeve/problems.html</uri>.
574 </p>
575
576 </body>
577 </section>
578 </chapter>
579
580 <chapter>
581 <title>Additional Resources</title>
582 <section>
583 <body>
584
585 <p>
586 Here is some info on the Gentoo/SPARC project itself:
587 </p>
588
589 <ul>
590 <li><uri link="http://sparc.gentoo.org">Gentoo/SPARC Project Page</uri></li>
591 <li>#gentoo-sparc - Official IRC channel on irc.freenode.net</li>
592 <li>
593 <uri link="http://forums.gentoo.org/viewforum.php?f=27">Gentoo/SPARC
594 Forum</uri>
595 </li>
596 <li><mail>sparc@gentoo.org</mail> - Gentoo/SPARC team email address</li>
597 </ul>
598
599 <p>
600 Here are links to additional information about SPARC/Linux or SPARCs in general:
601 </p>
602
603 <ul>
604 <li>
605 <uri link="http://www.ultralinux.org">UltraLinux Homepage</uri> - Homepage
606 of the SPARC/Linux port
607 </li>
608 <li>
609 <uri link="http://sunsolve.sun.com">Sunsolve</uri> - Great resource for Sun
610 hardware documentation
611 </li>
612 <li>
613 <uri>http://docs.sun.com</uri> - Additional hardware and software
614 information for SPARC systems, including instructions for flashing OBP
615 </li>
616 <li>
617 <uri link="http://www.obsolyte.com">Obsolyte</uri> - Information on older
618 SPARC systems and links to a lot of other great SPARC related sites
619 </li>
620 <li>
621 <uri
622 link="http://040.digital-bless.com/texts/Unofficial_Sun_Blade_100_FAQ.htm">Unofficial
623 Sun Blade 100 FAQ</uri> - Answers a lot of hardware related questions on
624 the Blade 100
625 </li>
626 <li>
627 <uri link="http://docs.sun.com/app/docs/coll/216.2">OBP Reference Guide</uri> -
628 Sun's guide to the OpenBoot PROM
629 </li>
630 </ul>
631
632 </body>
633 </section>
634 </chapter>
635 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20