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

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

  ViewVC Help
Powered by ViewVC 1.1.20