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

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

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

Revision 1.11 Revision 1.19
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-sparc-faq.xml,v 1.11 2006/05/26 20:55:10 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-faq.xml,v 1.19 2010/03/03 03:16:37 nightmorph Exp $ -->
3 3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5<guide link="/doc/en/gentoo-sparc-faq.xml"> 5<guide>
6<title>Gentoo Linux/SPARC Frequently Asked Questions</title> 6<title>Gentoo Linux/SPARC Frequently Asked Questions</title>
7 7
8<author title="SPARC Developer"> 8<author title="SPARC Developer">
9 <mail link="weeve@gentoo.org">Jason Wever</mail> 9 <mail link="weeve"/>
10</author>
11<author title="Editor">
12 <mail link="nightmorph"/>
10</author> 13</author>
11 14
12<abstract> 15<abstract>
13This FAQ is designed to help answer the most commonly asked questions about 16This FAQ is designed to help answer the most commonly asked questions about
14Gentoo Linux/SPARC and Linux on SPARC architecture. Feel free to send 17Gentoo/SPARC and Linux on SPARC architecture. Feel free to send revisions and
15revisions and corrections to the sparc team or the doc team. 18corrections to the Gentoo/SPARC team or the doc team.
16</abstract> 19</abstract>
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.7</version> 25<version>1.12</version>
23<date>2006-05-26</date> 26<date>2010-03-02</date>
24 27
25<chapter> 28<faqindex>
29<title>Questions</title>
30<section>
26<title>Documentation Notes</title> 31<title>Documentation Notes</title>
27<section>
28<body> 32<body>
29 33
30<p> 34<p>
31These are some notes to elaborate on acronyms and terms used in this document. 35These are some notes to elaborate on acronyms and terms used in this document.
32</p> 36</p>
33 37
34<p> 38<p>
35When mentioning <c>SPARC</c> and <c>SPARC64</c>, this refers to the type of 39When mentioning <c>SPARC</c>, this refers to the type of <c>sun4x</c> system.
36<c>sun4x</c> system. SPARC represents the 32 bit systems using the
37<c>sun4c</c>, <c>sun4d</c> and <c>sun4m</c> architectures (i.e. SPARCstations).
38SPARC64 represents the <c>sun4u</c> architecture seen in the UltraSPARC series 40SPARC represents the <c>sun4u</c> architecture seen in the UltraSPARC series of
39of systems (Ultras, Blades, SunFires, etc). 41systems (Ultras, Blades, SunFires, etc). Older 32-bit systems are no longer
42supported by the Gentoo/SPARC team.
40</p> 43</p>
41 44
42<p> 45<p>
43Acronyms: <c>OBP</c> = OpenBoot PROM, <c>SS</c> = SPARCstation. 46Acronyms: <c>OBP</c> = OpenBoot PROM, <c>SS</c> = SPARCstation.
44</p> 47</p>
45 48
46</body> 49</body>
47</section> 50</section>
48</chapter> 51</faqindex>
49 52
50<chapter> 53<chapter>
51<title>Installation</title> 54<title>Installation</title>
52<section> 55<section>
53<title>How do I install/use my SPARC over a serial console?</title> 56<title>How do I install/use my SPARC over a serial console?</title>
101</tr> 104</tr>
102</table> 105</table>
103 106
104</body> 107</body>
105</section> 108</section>
106<section>
107<title>How do I network boot my SPARC system for installation?</title>
108<body>
109 109
110<p>
111Currently, Gentoo has experimental network boot/tftpboot images available on a
112local Gentoo mirror in experimental/sparc/tftpboot. Get the appropriate image
113for your SPARC computer and then proceed to the Netboot HOWTO for further
114instructions.
115</p>
116
117</body>
118</section> 110<section>
119<section>
120<title>I have a CRT/LCD monitor attached to my SPARC that selects a resolution 111<title>I have a CRT/LCD monitor attached to my SPARC that selects a resolution
121my monitor can't handle when the kernel boots. How do I get a visible and/or 112my monitor can't handle when the kernel boots. How do I get a visible and/or
122non-distorted display on my monitor?</title> 113non-distorted display on my monitor?</title>
123<body> 114<body>
124 115
125<p> 116<p>
126This problem is a result of the framebuffer support the Linux kernel loads at 117This problem is a result of the framebuffer support the Linux kernel loads at
127boot time, and the modelines available on SPARC systems. Here we will assume 118boot time, and the modelines available on SPARC systems. Here we will assume
128your monitor and video card will agree on a resolution of 1024 by 768 at a 119your monitor and video card will agree on a resolution of 1024 by 768 at a
129refresh rate of 60 Hz. In OBP, you can set the resolution by adjusting the 120refresh rate of 60 Hz. In OBP, you can set the resolution by adjusting the
130setting for <c>output-device</c>. To view the current setting, use the 121setting for <c>output-device</c>. To view the current setting, use the command:
131command:
132</p> 122</p>
133 123
134<pre caption="View current settings"> 124<pre caption="View current settings">
135ok <i>printenv output-device</i> 125ok <i>printenv output-device</i>
136 126
186</pre> 176</pre>
187 177
188</body> 178</body>
189</section> 179</section>
190<section> 180<section>
191<title>I'm new to SPARC and am not sure what kernel options to use, 181<title>I'm new to SPARC and am not sure what kernel options to use,
192HELP!</title> 182HELP!</title>
193<body> 183<body>
194 184
195<p> 185<p>
196Most of the time, the default kernel options will be acceptable for hardware 186Most of the time, the default kernel options will be acceptable for hardware
197support. You will need to make sure that <c>devfs</c> (in case you don't use 187support. You will need to make sure that <c>virtual memory</c> and <c>/proc
198<c>udev</c>) and <c>virtual memory filesystem support</c> is enabled in the 188filesystem</c> support is enabled in the kernel as instructed in the <uri
199kernel as instructed in the <uri
200link="/doc/en/handbook/handbook-sparc.xml">Installation Handbook</uri>. 189link="/doc/en/handbook/handbook-sparc.xml">Installation Handbook</uri>.
201</p> 190</p>
202 191
203</body> 192</body>
204</section> 193</section>
205<section> 194<section>
206<title>How do I dual boot Gentoo Linux/SPARC with Solaris?</title> 195<title>How do I dual boot Gentoo Linux/SPARC with Solaris?</title>
207<body> 196<body>
208 197
209<p> 198<p>
210Dual booting Gentoo Linux/SPARC and Solaris can be done one of two ways. The 199Dual booting Gentoo/SPARC and Solaris can be done one of two ways. The two ways
211two ways are: having both Gentoo Linux/SPARC and Solaris on the same drive, or 200are: having both Gentoo/SPARC and Solaris on the same drive, or having them on
212having them on separate drives. Below are example SILO configurations for each 201separate drives. Below are example SILO configurations for each scenario. In the
213scenario. In the example configs, the following things are assumed: 202example configs, the following things are assumed:
214</p> 203</p>
215 204
216<p> 205<p>
217Single Drive Setup: 206Single Drive Setup:
218</p> 207</p>
238<pre caption="Sample silo.conf for a single drive installation"> 227<pre caption="Sample silo.conf for a single drive installation">
239<comment># Generic config options</comment> 228<comment># Generic config options</comment>
240partition = 1 229partition = 1
241timeout = 50 230timeout = 50
242 231
243<comment># Gentoo Linux/SPARC options</comment> 232<comment># Gentoo/SPARC options</comment>
244image = /boot/vmlinux 233image = /boot/vmlinux
245 label = linux 234 label = linux
246 root=/dev/sda4 235 root=/dev/sda4
247 236
248<comment># Solaris options</comment> 237<comment># Solaris options</comment>
253<pre caption="Sample silo.conf for separate disk installation"> 242<pre caption="Sample silo.conf for separate disk installation">
254<comment># Generic config options</comment> 243<comment># Generic config options</comment>
255parition = 1 244parition = 1
256timeout = 50 245timeout = 50
257 246
258<comment># Gentoo Linux/SPARC options</comment> 247<comment># Gentoo/SPARC options</comment>
259image = /boot/vmlinux 248image = /boot/vmlinux
260 label = linux 249 label = linux
261 root=/dev/sda4 250 root=/dev/sda4
262 251
263<comment># Solaris options</comment> 252<comment># Solaris options</comment>
264other = /sbus/espdma/esp/sd@1,0;1 253other = /sbus/espdma/esp/sd@1,0;1
265 label = solaris 254 label = solaris
266</pre> 255</pre>
267
268</body>
269</section>
270<section>
271<title>I just booted my SPARCstation after installing Gentoo but it won't boot.
272Why isn't it booting?</title>
273<body>
274
275<p>
276One possibility has to do with the way the that the SCSI IDs are assigned.
277Gentoo/SPARC developer Keith Wesolowski provides us with the following:
278</p>
279
280<p>
281Linux, 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>
283allows you to specify devices by SCSI ID, so that adding a new device doesn't
284cause your existing devices to be renamed, unless of course you use the
285compatibility names. There are additional ways to solve this.
286</p>
287
288<p>
289The OBP in most or all sun4c and sun4m systems aliases "disk" to the device
290with SCSI ID 3, and "disk0" through "disk3" to the device with = the
291corresponding SCSI ID, if it happens to be a disk rather than a tape, CDROM,
292etc.
293</p>
294
295<p>
296In the desktop systems of this era that support two SCA disks (the Aurora
297chassis systems), the lower slot is assigned SCSI ID 3, and the upper slot is
298assigned SCSI ID 1.
299</p>
300
301<p>
302If you like, you can change the PROM alias "disk" to match that of "disk1" so
303that the <c>boot disk</c> command causes the system to boot from the same
304device Linux calls <c>sda</c>. This feels more consistent and normal,
305especially for users with a PC background. Alternatively, you can simply place
306the filesystem containing <path>/boot</path> (which could be the root
307filesystem or a separate boot filesystem) on device ID 3 (Linux <c>sdb</c>) and
308boot from it, using a root filesystem on either <c>sda</c> or <c>sdb</c>, or in
309fact any other disk attached to the system.
310</p>
311 256
312</body> 257</body>
313</section> 258</section>
314</chapter> 259</chapter>
315 260
331link="/proj/en/base/sparc/sunhw.xml">hardware compatibility list</uri> for 276link="/proj/en/base/sparc/sunhw.xml">hardware compatibility list</uri> for
332SPARC64 systems. In general, support for SPARC64 systems is good enough to 277SPARC64 systems. In general, support for SPARC64 systems is good enough to
333allow some users to run it successfully in production environments. 278allow some users to run it successfully in production environments.
334</p> 279</p>
335 280
336<p>
33732-bit SPARC systems vary. Systems with the sun4m architecture have been
338reported to work fine (SS4-SS20) including SMP configurations with the later
3392.4 series kernels. sun4m systems using HyperSPARC or Ross processors in a SMP
340configuration will have a lot of kernel related trouble. Additionally the
341author hasn't heard of any user reports in regards to the JavaStations so its
342status is unknown. sun4d based systems currently do not work in the 2.4 kernel
343series, and sun4c has been unstable as well.
344</p>
345
346<p>
347Often, the problems encountered in trying to run Gentoo on a 32-bit SPARC
348system stem from the kernel. Rob Radez (not related to Gentoo) maintains a
349webpage <uri>http://osinvestor.com/sparc/</uri> with the status of SPARC system
350support for various versions of the Linux kernel. This can help indicate how
351usable your SPARC system would be under SPARC/Linux.
352</p>
353
354</body> 281</body>
355</section> 282</section>
356<section> 283<section>
357<title>What additional hardware is supported under Gentoo/SPARC?</title> 284<title>What additional hardware is supported under Gentoo/SPARC?</title>
358<body> 285<body>
359 286
360<p> 287<p>
361For a list of additionally supported Sun hardware, consult the following list 288For a list of additionally supported Sun hardware, consult the following list
362from the UltraLinux homepage - 289from the <uri link="http://www.ultralinux.org/faq.html#q_2_2.">UltraLinux
363<uri>http://www.ultralinux.org/faq.html#q_2_2.</uri> 290homepage</uri>.
364</p> 291</p>
365 292
366<p> 293<p>
367A partial list of Sun devices which do NOT currently have support under 294A partial list of Sun devices which do NOT currently have support under
368Gentoo/SPARC or SPARC/Linux in general are: 295Gentoo/SPARC or SPARC/Linux in general are:
374 <li>Smart card readers on some Sun Blade workstations</li> 301 <li>Smart card readers on some Sun Blade workstations</li>
375 <li>Floppy drive on some Sun Blade workstations</li> 302 <li>Floppy drive on some Sun Blade workstations</li>
376</ul> 303</ul>
377 304
378<p> 305<p>
379Also, Gentoo/SPARC developer Sven Blumenstein keeps a list of PC hardware that 306Also, the Gentoo/SPARC team maintains a <uri
380has been tested with the PCI based SPARC64 systems at 307link="/proj/en/base/sparc/hwlist.xml">list of non-Sun PCI hardware that has
381<uri>http://dev.gentoo.org/~bazik/hw.php</uri>. Feel free to add your results 308been tested on Gentoo/SPARC</uri>. To submit additions to the list, email
382at testing PC or non-Sun hardware to the list by emailing <mail 309<mail>sparc@gentoo.org</mail> with the information on the hardware as displayed
383link="bazik@gentoo.org">bazik@gentoo.org</mail> with the information on the 310in the existing hardware list.
384hardware as displayed in the existing hardware list.
385</p> 311</p>
386 312
387</body> 313</body>
388</section>
389<section> 314</section>
390<title>So you keep talking about sun4c/sun4d/sun4m/sun4u. How do I 315<section>
391know which one I have?</title> 316<title>How do I know which SPARC I have?</title>
317<body>
318
319<p>
320The <uri link="http://www.ultralinux.org/faq.html#q_2_1">UltraLinux FAQ</uri>
321has the answer.
322</p>
323
392<body> 324</body>
325</section>
326<section>
327<title>My box has more than one Sun Ethernet device. Why do they all have the
328same MAC address and how do I fix it?</title>
329<body>
393 330
331<p>
332First, the reason they all they all have the same setting is due to a value in
333OpenBoot PROM (OBP). The story goes that in times past, it was assumed that if a
334host had multiple interfaces, the interfaces would not reside on the same
335Ethernet and therefore having the MAC address unique to a machine rather than to
336a NIC wouldn't be a problem. As time went on and different technologies
337developed, the opposite was proven.
394<p> 338</p>
395The UltraLinux FAQ has the answer at 339
396<uri>http://www.ultralinux.org/faq.html#q_2_1</uri>. 340<p>
341As for fixing the issue, there are two ways to it; from OBP and from Linux. The
342OBP variable <c>local-mac-address?</c> controls this behavior. The following
343commands will help you to determine what <c>local-mac-address?</c> is set to:
344</p>
345
346<pre caption="View local-mac-address? setting from OBP">
347ok <i>printenv local-mac-address?</i>
348local-mac-address? = false
349</pre>
350
351<pre caption="View local-mac-address? setting from Linux">
352# <i>eeprom local-mac-address?</i>
353local-mac-address?=false
354</pre>
355
356<p>
357As you'll notice from the samples above, <c>local-mac-address?</c> is set to
358<b>false</b>. This will cause all interfaces on a SPARC to use the same MAC
359address. To change this behavior, use either of the commands below (depending
360on whether you do it from OBP or Linux):
361</p>
362
363<pre caption="Set local-mac-address? from OBP">
364ok <i>setenv local-mac-address?=true</i>
365local-mac-address? = true
366</pre>
367
368<pre caption="Set local-mac-address? from Linux">
369# <i>eeprom local-mac-address?=true</i>
370</pre>
371
372<p>
373Note that you may need to reboot to see the changes take affect.
374</p>
375
376</body>
377</section>
378<section>
379<title>Is SPARC big-endian or little-endian?</title>
380<body>
381
382<p>
383The version supported by Gentoo/SPARC (v9) is bi-endian. It uses big-endian
384instructions, but can access data in little-endian byte-order, such as PCI
385devices, which are little-endian by nature.
397</p> 386</p>
398 387
399</body> 388</body>
400</section> 389</section>
401</chapter> 390</chapter>
402 391
403<chapter> 392<chapter>
404<title>Applications</title> 393<title>Applications</title>
405<section> 394<section>
406<title> 395<title>
407How do I get XFree86 to find a usable modeline on my Ultra 5/10 or Blade 396How do I get Xorg to find a usable modeline on my Ultra 5/10 or Blade 100/150?
408100/150?
409</title> 397</title>
410<body> 398<body>
411 399
412<p> 400<p>
413The ATI Framebuffer normally expects a PC's BIOS to set the Reference Clock 401The ATI Framebuffer normally expects a PC's BIOS to set the Reference Clock
414speed for the video card. However, on non-x86 architectures, this doesn't 402speed for the video card. However, on non-x86 architectures, this doesn't
415happen. So what needs to be done is to set the Reference Clock speed in the 403happen. So what needs to be done is to set the Reference Clock speed in the
416XF86Config file. 404<path>/etc/X11/xorg.conf</path>.
417</p>
418
419<p> 405</p>
420In the "Device" section of your XF86Config file, you will want to add a line 406
421similar to the following:
422</p> 407<p>
408In the "Device" section of your <path>/etc/X11/xorg.conf</path>, you will
409want to add a line similar to the following:
410</p>
423 411
424<pre caption="Add to XF86Config"> 412<pre caption="Add to xorg.conf">
425Option "reference_clock" "28.636 MHz" 413Option "reference_clock" "28.636 MHz"
426</pre> 414</pre>
427 415
428<p> 416<p>
429The following URLs contain more information on how to set the reference clock: 417Other common speeds are 14.318 MHz and 29.5 MHz. If you have issues you might
430<uri>http://www.xfree86.org/~dawes/4.3.0/ati5.html#26</uri>. If you have issues
431you might want to try without a similar setting first. 418want to try without a similar setting first.
432</p> 419</p>
433 420
434</body> 421</body>
435</section>
436<section> 422</section>
423<section>
437<title>How come package foo is masked on Sparc?</title> 424<title>How come package foo is masked on SPARC?</title>
438<body> 425<body>
439 426
440<p> 427<p>
441Chances are this is due to the fact that none of the Gentoo/SPARC developers 428Chances are this is due to the fact that none of the Gentoo/SPARC developers
442have gotten around to testing this yet, and/or the package is currently marked 429have gotten around to testing this yet, and/or the package is currently marked
443with the <c>~sparc</c> keyword (meaning it's in a testing phase). 430with the <c>~sparc</c> keyword (meaning it's in a testing phase).
444</p> 431</p>
445 432
446<p> 433<p>
447If you still want to install the package, you can follow the instructions from 434If you still want to install the package, you can follow the instructions from
448the at <uri link="http://forums.gentoo.org/viewforum.php?t=33534">Portage 435the <uri link="/doc/en/handbook/handbook-sparc.xml?part=3&amp;chap=3">Portage
449Masked Package FAQ</uri>. 436Handbook</uri>.
450</p> 437</p>
451
452<note>
453The FAQ mentions the sparc64 keyword, which is invalid.
454</note>
455 438
456</body> 439</body>
457</section> 440</section>
458<section> 441<section>
459<title>How can I help get package foo marked stable?</title> 442<title>How can I help get package foo marked stable?</title>
461 444
462<p> 445<p>
463If you want to help ensure a package gets marked stable in a timely fashion, 446If you want to help ensure a package gets marked stable in a timely fashion,
464particularly if it's an application with a small userbase (i.e. 447particularly if it's an application with a small userbase (i.e.
465net-im/bitlbee), install the package and test to make sure it works. If it 448net-im/bitlbee), install the package and test to make sure it works. If it
466appears to be working well, feel free to file a bug at 449appears to be working well, feel free to file a bug via the
467<uri>http://bugs.gentoo.org</uri> and assign it to the Gentoo/SPARC team. 450<uri link="http://bugs.gentoo.org">Gentoo Bugzilla</uri> and assign it to the
451Gentoo/SPARC team.
468</p> 452</p>
469 453
470</body> 454</body>
471</section> 455</section>
472<section> 456<section>
473<title>I tried to emerge a package, but emerge failed complaining that a 457<title>I tried to emerge a package, but emerge failed complaining that a
474dependency is masked. How can I fix this?</title> 458dependency is masked. How can I fix this?</title>
475<body> 459<body>
476 460
477<p> 461<p>
478This is a bug. Please file a bug report at <uri>http://bugs.gentoo.org</uri> 462This is a bug. Please file a bug report via the <uri
479for the Gentoo/SPARC team indicating what package you tried to emerge, the 463link="http://bugs.gentoo.org">Gentoo Bugzilla</uri> for the Gentoo/SPARC team
480error message emerge gave you, and the output of <c>emerge --info</c>. 464indicating what package you tried to emerge, the error message emerge gave you,
465and the output of <c>emerge --info</c>.
466</p>
467
468</body>
469</section>
470<section>
471<title>Why am I getting an error related to 32/64-bit when compiling a
472kernel?</title>
473<body>
474
481</p> 475<p>
476The way SPARC/Linux handles the cross-compiler has changed with 2.6.25 (<uri
477link="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=54cd6ddec77b75e6926d73d263aec72255b24030">commit</uri>),
478thus when building a recent kernel you'd get the following error message:
479</p>
480
481<pre caption="SPARC/Linux compile error message">
482CHK include/linux/version.h
483CHK include/linux/utsrelease.h
484CC arch/sparc64/kernel/asm-offsets.s
485arch/sparc64/kernel/asm-offsets.c:1: error: -m64 is not supported by this configuration
486arch/sparc64/kernel/asm-offsets.c:1: error: -mlong-double-64 not allowed with -m64
487arch/sparc64/kernel/asm-offsets.c:1: error: -mcmodel= is not supported on 32 bit systems
488make[1]: *** [arch/sparc64/kernel/asm-offsets.s] Error 1
489make: *** [prepare0] Error 2
490</pre>
491
492<p>
493Because, for the moment (there's an <b>experimental</b> <uri
494link="/proj/en/base/sparc/multilib.xml">multilib</uri> profile),
495Gentoo/SPARC native compiler can't generate 64-bit code (that's what
496sys-devel/kgcc64 is for).
497</p>
498
499<p>
500What you need to do is to tell the SPARC/Linux Makefile what is your
501cross-compiler's binary, by issuing the following commands:
502</p>
503
504<pre caption="Gentoo/SPARC kernel >=2.6.25 kernel compilation">
505# <i>cd /usr/src/linux</i>
506# <i>make CROSS_COMPILE=sparc64-unknown-linux-gnu-</i>
507# <i>make CROSS_COMPILE=sparc64-unknown-linux-gnu- image modules_install</i>
508</pre>
482 509
483</body> 510</body>
484</section> 511</section>
485</chapter> 512</chapter>
486 513
487<chapter> 514<chapter>
488<title>Miscellaneous</title> 515<title>Miscellaneous</title>
489<section> 516<section>
490<title>I'm interested in becoming more involved with Gentoo/SPARC. How do I go about 517<title>I'm interested in becoming more involved with Gentoo/SPARC. How do I go
491doing that?</title> 518about doing that?</title>
492<body> 519<body>
493 520
494<p>
495The best way is to join the <c>#gentoo-sparc</c> IRC channel on Freenode IRC
496network <c>irc.freenode.net</c>. This is where all of the developers hang out
497and talk SPARC (amongst other things). Short of email, this is the best way to
498get our attention, and blame seemant! :)
499</p> 521<p>
500 522There are various ways to improve the project:
501<p> 523</p>
502Also, many users and developers make use of the <uri 524
525<ul>
526 <li>The best way is to become an <uri
527 link="/proj/en/base/sparc/at/index.xml">Arch Tester</uri>, and aid the
528 developers with package testing.
529 </li>
530 <li>File bug reports such as <uri
531 link="http://dev.gentoo.org/~tcunha/reports/imlate-sparc.txt">stable, and
532 keyword</uri> requests.
533 </li>
534 <li>Join the <uri
535 link="irc://irc.gentoo.org/gentoo-sparc">#gentoo-sparc</uri> IRC channel
536 on the FreeNode IRC network.
537 </li>
538 <li>Make use of the <uri
503link="http://forums.gentoo.org/viewforum.php?f=27">Gentoo/SPARC forum</uri>. 539 link="http://forums.gentoo.org/viewforum.php?f=27">Gentoo/SPARC forum</uri>.
504This is a good place to ask questions and see what problems have come up 540 </li>
505before, as well as talk shop about Gentoo/SPARC. 541 <li>Propose solutions for Gentoo/SPARC related bugs via the <uri
506</p>
507
508<p>
509Additionally, you can view the bugs for Gentoo/SPARC via the <uri
510link="http://bugs.gentoo.org">Gentoo Bugzilla</uri>. The bugs will be assigned 542 link="http://bugs.gentoo.org">Gentoo Bugzilla</uri>. The bugs will be
511or CC'd to sparc@gentoo.org. 543 assigned, or CCed to sparc@gentoo.org.
512</p> 544 </li>
513 545</ul>
514</body>
515</section>
516<section>
517<title>Are there any currently known bugs/issues with software packages on
518Gentoo/SPARC?</title>
519<body>
520
521<p>
522A list of problematic packages can be found at
523<uri>http://dev.gentoo.org/~weeve/problems.html</uri>
524</p>
525 546
526</body> 547</body>
527</section> 548</section>
528</chapter> 549</chapter>
529 550
530<chapter> 551<chapter>
531<title>Additional Resources</title> 552<title>Additional Resources</title>
532<section> 553<section>
554<title>Where can I get more help or information about SPARC/Linux?</title>
533<body> 555<body>
534
535<p>
536Here is some info on the Gentoo/SPARC project itself:
537</p>
538 556
539<ul> 557<ul>
540 <li><uri link="http://sparc.gentoo.org">Gentoo/SPARC Project Page</uri></li>
541 <li>#gentoo-sparc - Official IRC channel on irc.freenode.net</li>
542 <li> 558 <li>
543 <uri link="http://forums.gentoo.org/viewforum.php?f=27">Gentoo/SPARC 559 <uri link="http://docs.sun.com/app/docs/coll/216.2">OBP Reference
544 Forum</uri> 560 Guide</uri> - Sun's guide to the OpenBoot PROM
561 </li>
545 </li> 562 <li>
546 <li><mail>sparc@gentoo.org</mail> - Gentoo/SPARC team email address 563 <uri link="http://www.sunstuff.org">OSIAH</uri> - Online Sun Information
564 Archive
565 </li>
547 </li> 566 <li>
548</ul> 567 <uri link="http://www.obsolyte.com">Obsolyte</uri> - Information on older
549 568 SPARC systems and links to a lot of other great SPARC related sites
550<p> 569 </li>
551Here are links to additional information about SPARC/Linux or SPARCs in general: 570 <li>
552</p> 571 <uri link="http://docs.sun.com">Sun Microsystems Documentation</uri> -
553 572 Additional hardware and software information for SPARC systems, including
554<ul> 573 instructions for flashing OBP
574 </li>
575 <li>
576 <uri link="http://sunsolve.sun.com">Sunsolve</uri> - Great resource for Sun
577 hardware documentation
578 </li>
555 <li> 579 <li>
556 <uri link="http://www.ultralinux.org">UltraLinux Homepage</uri> - Homepage 580 <uri link="http://www.ultralinux.org">UltraLinux Homepage</uri> - Homepage
557 of the SPARC/Linux port 581 of the SPARC/Linux port
558 </li> 582 </li>
559 <li>
560 <uri link="http://sunsolve.sun.com">Sunsolve</uri> - Great resource for Sun
561 hardware documentation
562 </li>
563 <li>
564 <uri>http://docs.sun.com</uri> - Additional hardware and software
565 information for SPARC systems, including instructions for flashing OBP
566 </li>
567 <li>
568 <uri link="http://www.obsolyte.com">Obsolyte</uri> - Information on older
569 SPARC systems and links to a lot of other great SPARC related sites.
570 </li>
571 <li>
572 <uri
573 link="http://040.digital-bless.com/texts/Unofficial_Sun_Blade_100_FAQ.htm">Unofficial
574 Sun Blade 100 FAQ</uri> - Answers a lot of hardware related questions on
575 the Blade 100
576 </li>
577 <li>
578 <uri link="http://docs.sun.com/db/coll/216.2">OBP Reference Guide</uri> -
579 Sun's guide to the OpenBoot PROM.
580 </li>
581</ul> 583</ul>
582 584
583</body> 585</body>
584</section> 586</section>
585</chapter> 587</chapter>

Legend:
Removed from v.1.11  
changed lines
  Added in v.1.19

  ViewVC Help
Powered by ViewVC 1.1.20