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

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

  ViewVC Help
Powered by ViewVC 1.1.20