Annotation of wikisrc/ports/sun3.mdwn, revision 1.2
1.1 mspo 1: [[!template id=port
2: port="sun3"
3: cur_rel="6.0"
4: future_rel="7.0"
5: changes_cur="6.0"
6: changes_future="7.0"
7: thumbnail="http://www.netbsd.org/images/ports/sun3/110.gif"
8: about="""
9: NetBSD/sun3 is the port of NetBSD to the Sun Microsystems sun3, and sun3x series of computers, which are based on the Motorola [68020](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68020) and [68030](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68030) CPUs respectively, with a Sun-designed custom MMU. Sun sold these computers as both servers and desktop workstations from the mid to late 1980's. They were superseded by the sun4 SPARC RISC systems, which are supported by NetBSD as [NetBSD/sparc](/ports/sparc).
10:
11: Nathan Williams and Jeremy Cooper are the maintainers of NetBSD/sun3.
12: """
13: supported_hardware="""
14: ###Supported System Models
15:
1.2 ! mspo 16: NetBSD/sun3 runs on these <span class="bold"><strong>sun3</strong></span> and
! 17: <span class="bold"><strong>sun3x</strong></span> architecture
! 18: machines:
! 19:
! 20: <table border="2" cellpadding="4" cellspacing="0" id="sun3-supported">
! 21: <tr>
! 22: <th>Model</th>
! 23: <th>MHz</th>
! 24: <th>RAM</th>
! 25: <th>RAM Expansion</th>
! 26: <th>Bus</th>
! 27: <th>Slots</th>
! 28: <th>Type</th>
! 29: </tr>
! 30: <tr>
! 31: <td>Sun 3/50</td>
! 32: <td align="right">15.7</td>
! 33: <td align="right">4</td>
! 34: <td>3rd party</td>
! 35: <td>n/a</td>
! 36: <td align="right">n/a</td>
! 37: <td>sun3</td>
! 38: </tr>
! 39: <tr>
! 40: <td>Sun 3/60</td>
! 41: <td align="right">20</td>
! 42: <td align="right">24</td>
! 43: <td>24 30-pin SIMM: 1x9 100ns</td>
! 44: <td>P4 (video)</td>
! 45: <td align="right">1</td>
! 46: <td>sun3</td>
! 47: </tr>
! 48: <tr>
! 49: <td>Sun 3/75</td>
! 50: <td align="right">16.67</td>
! 51: <td align="right">16</td>
! 52: <td>VME bus memory cards</td>
! 53: <td>VME bus</td>
! 54: <td align="right">2</td>
! 55: <td>sun3</td>
! 56: </tr>
! 57: <tr>
! 58: <td>Sun 3/80</td>
! 59: <td align="right">20</td>
! 60: <td align="right">40/64</td>
! 61: <td>16 30-pin SIMM: 1x9 or 4x9 100ns</td>
! 62: <td>P4 (video)</td>
! 63: <td align="right">1</td>
! 64: <td>sun3x</td>
! 65: </tr>
! 66: <tr>
! 67: <td>Sun 3/100 series</td>
! 68: <td align="right">16.67</td>
! 69: <td align="right">16</td>
! 70: <td>VME bus memory cards</td>
! 71: <td>VME bus</td>
! 72: <td align="right">3</td>
! 73: <td>sun3</td>
! 74: </tr>
! 75: <tr>
! 76: <td>Sun 3/200 series</td>
! 77: <td align="right">25</td>
! 78: <td align="right">64</td>
! 79: <td>VME bus memory cards</td>
! 80: <td>VME bus</td>
! 81: <td align="right">12</td>
! 82: <td>sun3</td>
! 83: </tr>
! 84: <tr>
! 85: <td>Sun 3/400 series</td>
! 86: <td align="right">33</td>
! 87: <td align="right">128</td>
! 88: <td>VME bus memory cards</td>
! 89: <td>VME bus</td>
! 90: <td align="right">12</td>
! 91: <td>sun3x</td>
! 92: </tr>
! 93: <tr>
! 94: <td>Sun 3/E</td>
! 95: <td align="right">20</td>
! 96: <td align="right">4(?)</td>
! 97: <td>VME bus memory cards</td>
! 98: <td>VME bus</td>
! 99: <td align="right">n/a(?)</td>
! 100: <td>sun3</td>
! 101: </tr>
! 102: </table>
! 103:
! 104: The RAM column is maximum supported RAM in megabytes.
1.1 mspo 105:
106: Sun made a variety of VME bus cabinets with different numbers of bus slots; ultimate RAM and I/O expansion is more a matter of how many bus slots there, rather than the particular CPU you have.
107:
108: The Sun3/80 RAM capacity varies with the boot ROM revision - 3.0.2 allows 40MB, 3.0.3 allows 64MB.
109:
110: The Sun 3/50 has 4MB soldered on the motherboard; all RAM expansions for that workstation were provided by third-party solutions (read "hacks") of one kind or another.
111:
112: The Sun 3/E is a 6U VME single-board computer intended as an embedded system component.
113:
114: The Sun 3/80 workstation and Sun 3/400 series servers are sun3x architecture machines based on the [Motorola 68030 CPU](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68030). They were Sun's last design using Motorola microprocessors, and were somewhat complicated by the fact that the mc68030 has an integrated MMU in the CPU chip.
115:
116: Sun Microsystems stopped designing systems with Motorola microprocessors when their own SPARC CPU design became a commercial success.
117:
118: ###Disk and RAM Requirements
119:
120: Minimum
121:
122: 4MB RAM, ~80MB disk
123:
124: Normal
125:
126: 8MB RAM, 200MB disk
127:
128: Normal + X11
129:
130: 16MB RAM, 300MB disk
131:
132: The complete NetBSD sources without objects require 200MB of disk.
133:
134: To run the X Window System or compile the NetBSD system sources (i.e. development), more RAM and disk are recommended. Good performance requires 8MB of RAM, or 16MB of RAM when running the X Window System.
135:
136: ###Supported Hardware
137:
138: The following Sun3 devices are currently supported:
139:
140: * RS-232c Serial ports:
141: * built-in z8530 SCC as ttya, ttyb (zs)
142: * Sun Video adapters:
143: * 1 bpp framebuffer, (bwtwo)
144: * 8 bpp framebuffer (cgtwo)
145: * 8 bpp (+overlay) framebuffer (cgfour)
146: * Network interfaces:
147: * On-board AMD LANCE Ethernet (le)
148: * On-board Intel Ethernet (ie)
149: * VME Intel Ethernet board (ie)
150: * SCSI bus host adapters:
151: * On-board NCR 5380 SCSI Bus Controller (si)
152: * On-board Emulex SCSI controller on sun3x (esp)
153: * Sun-3 VME SCSI (also NCR 5380 SBC, Sun part # 501-1236) (si)
154: * SMD Disks: (the big, heavy ones)
155: * Xylogics 450/451 (xy)
156: * Xylogics 753/7053 (xd)
157: * Floppy drive:
158: * Sun 3/80 built-in floppy drive (fdc)
159: * Input devices:
160: * Sun keyboard (kbd) and mouse (ms)
161: * Miscellaneous:
162: * Battery-backed real-time clock.
163:
164: If you have a device that's not listed, it might be compatible with something else, or we might have simply forgotten it. If all else fails, maybe you could write a driver!
165:
166: Note: The Sun VME sc SCSI card is not yet supported.
167:
168:
169: """
170: additional="""
171: Features of NetBSD/sun3
172:
173: * Native boot programs for disk, network, and tape
174: * Automated installation tools (using a "miniroot")
175: * SCSI drivers supporting DMA, interrupts, and (optional) disconnect/reselect
176: * Frame buffer drivers compatible with SunOS and X11R6
177: * Support for the Virtually Addressed Cache (VAC) on Sun3/2XX models
178: * Storage Module Device (SMD) disk drivers
179: * Supports most SCSI devices (CD-ROM, disk, etc)
180: * Diskless (network) boot capability
181: * Built-in kernel debugger
182: * [SunOS 4.1 Compatibility](http://www.netbsd.org/ports/sun3/faq.html#sunos_compat)
183:
184: ###links
185: * [ILVSUN3](http://www.ilvsun3.com/) page by arthur also has various useful information about TME and Sun3 stuff.
186: * [The Machine Emulator (tme)](http://people.csail.mit.edu/fredette/tme/) can emulate a Sun 3/150 running NetBSD.
187:
188: <div id="content"><div class="fullWidth"><div class="rowOfBoxes">
189: <h1>NetBSD/sun3 Frequently Asked Questions</h1>
190: <h2 class="title">NetBSD/sun3 Frequently Asked Questions</h2>
191: <h3 class="title"><a name="general">General Questions</a></h3>
192: <ul>
193: <li><a href="#le0-not-multicast-capable">No multicast or IPv6 - "le0: not multicast capable" </a></li>
194: <li><a href="#3-80-esp-endless-reset">Running diskless 3/80 with ESP driver - "esp: SCSI bus reset." </a></li>
195: <li><a href="#sunos_compat">SunOS 4.1 Compatibility</a></li>
196: <li><a href="#boot-devices">Booting SCSI devices at different targets</a></li>
197: <li><a href="#sun3x-history">History of NetBSD/sun3x</a></li>
198: </ul>
199: <h3 class="title"><a name="info_sources">Other sources of information</a></h3>
200: <ul>
201: <li><a href="#sunhelp">SunHELP</a></li>
202: <li><a href="#hwreffaq">Sun Hardware Reference FAQ</a></li>
203: <li><a href="#hostidfaq">Sun NVRAM/Hostid FAQ</a></li>
204: <li><a href="#cdromfaq">Sun CD-ROM FAQ</a></li>
205: <li><a href="#installnotes">NetBSD 6.0 install notes</a></li>
206: <li><a href="#mailinglist">port-sun3 mailing list</a></li>
207: <li><a href="#disklesshowto">Diskless NetBSD HOW-TO</a></li>
208: <li><a href="#sun3arc">Sun3 Archive</a></li>
209: <li><a href="#techrat">Techrat's Sun 3/160 pages</a></li>
210: <li><a href="#netbsddocs">General NetBSD Documentation</a></li>
211: </ul>
212: <hr>
213: <h3 class="title">General Questions</h3>
214: <h4 class="title">
215: <a name="le0-not-multicast-capable"></a>No multicast or IPv6 - "<code class="code">le0: not multicast capable</code>" (<a href="#general">top</a>)
216: </h4>
217: <p> The LANCE revision C chips used in
218: some sun3s (not the sun3x) have a bug which sometimes results in garbage
219: inserted where the first bits should be, with the correct bits shifted later. So
220: instead of the destination MAC address at the beginning, you get something
221: random looking. </p>
222: <p> The workaround is to examine the beginning of the packet and throw away
223: anything that's not for us (my MAC or broadcast). Unfortunately this prevents
224: the use of multicast. </p>
225: <p> The LANCE Rev. C chip was probably only used in the 3/50, so on other sun3
226: machines you should be able to <a class="ulink" href="../../docs/kernel/#how_to_build_a_kernel" target="_top">build a
227: kernel</a> without the line:</p>
228: <pre class="programlisting">options LANCE_REVC_BUG</pre>
229:
230: <h4 class="title">
231: <a name="3-80-esp-endless-reset"></a>Running diskless 3/80 with ESP driver - <code class="code">"esp: SCSI bus reset."</code> (<a href="#general">top</a>)
232: </h4>
233: <p>
234: This message is a symptom of a bug in the
235: esp driver on diskless systems. The ESP (Emulex SCSI Processor) driver in
236: NetBSD/sun3x has a bug that causes it to enter an endless loop when it probes an
237: empty SCSI bus. To work around this problem, use a kernel which does not have
238: the esp device driver, or plug in at least one powered SCSI device into the bus.</p>
239:
240: <h4 class="title">
241: <a name="sunos_compat"></a>SunOS 4.1 Compatibility (<a href="#general">top</a>)
242: </h4>
243: <p> NetBSD/Sun3 features extensive binary compatibility with SunOS 4.1.x
244: programs. Static SunOS executables will run without any extra setup. </p>
245: <p> To run dynamic executables, you'll need to provide the dynamic libraries that
246: came with your SunOS installation. SunOS programs that will
247: <span class="emphasis"><em>not</em></span> work include those that use the SunOS kvm library,
248: certain (low-level) disk manipulation utilities, and programs making explicit
249: use of Sun's STREAMS subsystem. Check the <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_sunos+8+NetBSD-6.0+i386">compat_sunos(8)</a> manual page
250: for more details. </p>
251:
252: <h4 class="title">
253: <a name="boot-devices"></a>Booting SCSI devices at different targets (<a href="#general">top</a>)
254: </h4>
255: <p> All sun3 and sun3x monitors support booting from SCSI devices. Most users
256: will be familiar with booting from the monitor device <code class="code">sd(0,0,0)</code>,
257: which they know means booting the SCSI disk at target zero. However, determining
258: the monitor device name for booting an arbitrary SCSI device can be confusing. </p>
259: <p> A monitor boot device takes the form
260: <span class="emphasis"><em>dev</em></span><code class="code">(</code><span class="emphasis"><em>cntrl</em></span><code class="code">,</code><span class="emphasis"><em>unit</em></span><code class="code">,</code><span class="emphasis"><em>part</em></span><code class="code">)</code>.
261: <span class="emphasis"><em>dev</em></span> is two letters, and <span class="emphasis"><em>cntrl</em></span>,
262: <span class="emphasis"><em>unit</em></span>, and <span class="emphasis"><em>part</em></span> are hexadecimal
263: numbers. </p>
264: <p> For SCSI disks and CD-ROMs, <span class="emphasis"><em>dev</em></span> is <code class="code">sd</code>. For
265: SCSI tapes, <span class="emphasis"><em>dev</em></span> is <code class="code">st</code>. </p>
266: <p> For all SCSI devices, <span class="emphasis"><em>cntrl</em></span> is the number of the SCSI
267: controller the device is attached to. For a machine with a single SCSI
268: controller, <span class="emphasis"><em>cntrl</em></span> is <code class="code">0</code>. </p>
269: <p> For all SCSI devices, <span class="emphasis"><em>unit</em></span> identifies the SCSI target
270: and logical unit number of the device. Exactly how the SCSI target and logical
271: unit number are combined into the single number <span class="emphasis"><em>unit</em></span>
272: depends on your machine type and ROM revision, and whether or not the device is
273: a disk, CD-ROM, or tape. Use the tables below to figure out how
274: <span class="emphasis"><em>unit</em></span> works on your machine. </p>
275: <p> For SCSI disks and CD-ROMs, <span class="emphasis"><em>part</em></span> selects the partition
276: to boot on that disk or CD-ROM. The first partition is <code class="code">0</code>, the
277: second partition is <code class="code">1</code>, etc. Normally, <span class="emphasis"><em>part</em></span> is
278: <code class="code">0</code>, since the first partition on a disk is usually the bootable
279: one. Common exceptions are booting a miniroot that has been written to the swap
280: partition, in which case <span class="emphasis"><em>part</em></span> is <code class="code">1</code>, or booting
281: a CD-ROM that contains different bootable partitions for different
282: architectures, in which case you have to know which partition boots your
283: architecture. </p>
284: <p> For SCSI tapes, <span class="emphasis"><em>part</em></span> selects the tape segment (also
285: called "tape file") to boot. The first tape segment is <code class="code">0</code>, the
286: second tape segment is <code class="code">1</code>, etc. You will need to know which tape
287: segment is bootable for your architecture in order to give the right
288: <span class="emphasis"><em>part</em></span>. </p>
289: <p> Finally, these are the tables that demonstrate how <span class="emphasis"><em>unit</em></span>
290: works on various machines. They list <code class="code">sd</code> monitor devices for disks
291: and CD-ROMs, and <code class="code">st</code> monitor devices for tapes, all at different
292: SCSI targets. These tables assume that you want the first SCSI controller
293: <code class="code">0</code>, and the first partition or first tape segment
294: <code class="code">0</code>. Also, because many Sun 3 models use the same CPU board, to keep
295: these tables simple Sun's CPU board code names are used wherever possible. </p>
296:
297: <div class="informaltable">
298: <a name="hw_model"></a>
299: <table border="1">
300: <colgroup>
301: <col>
302: <col>
303: <col>
304: <col>
305: </colgroup>
306: <thead><tr>
307: <th>Model</th>
308: <th>CPU</th>
309: <th>Model</th>
310: <th>CPU</th>
311: </tr></thead>
312: <tbody>
313: <tr>
314: <td>3/75</td>
315: <td>
316: <span class="emphasis"><em>Carrera</em></span>
317: </td>
318: <td>3/140</td>
319: <td>
320: <span class="emphasis"><em>Carrera</em></span>
321: </td>
322: </tr>
323: <tr>
324: <td>3/150</td>
325: <td>
326: <span class="emphasis"><em>Carrera</em></span>
327: </td>
328: <td>3/160</td>
329: <td>
330: <span class="emphasis"><em>Carrera</em></span>
331: </td>
332: </tr>
333: <tr>
334: <td>3/180</td>
335: <td>
336: <span class="emphasis"><em>Carrera</em></span>
337: </td>
338: <td> </td>
339: <td> </td>
340: </tr>
341: </tbody>
342: </table>
343: </div>
344: <p> </p>
345:
346: <div class="informaltable">
347: <a name="hw_cpu_rom"></a>
348:
349: <table border="1">
350: <colgroup>
351: <col align="center" class="col1">
352: <col align="center" class="col2">
353: <col align="center" class="col3">
354: <col align="center" class="col4">
355: <col align="center" class="col5">
356: <col align="center" class="col6">
357: <col align="center" class="col7">
358: <col align="center" class="col8">
359: <col align="center" class="col9">
360: </colgroup>
361: <thead>
362: <tr>
363: <th rowspan="2" align="center">CPU/rev ROM</th>
364: <th colspan="8" align="center">Monitor device to
365: boot the disk or CD-ROM at target</th>
366: </tr>
367: <tr>
368: <th align="center">0</th>
369: <th align="center">1</th>
370: <th align="center">2</th>
371: <th align="center">3</th>
372: <th align="center">4</th>
373: <th align="center">5</th>
374: <th align="center">6</th>
375: <th align="center">7</th>
376: </tr>
377: </thead>
378: <tbody>
379: <tr>
380: <td align="center">3/60 rev 1.9 <span class="emphasis"><em>Carrera</em></span> rev 2.7</td>
381: <td align="center">
382: <code class="code">sd(0,0,0)</code>
383: </td>
384: <td align="center">
385: <code class="code">sd(0,4,0)</code>
386: </td>
387: <td align="center">
388: <code class="code">sd(0,8,0)</code>
389: </td>
390: <td align="center">
391: <code class="code">sd(0,C,0)</code>
392: </td>
393: <td align="center">
394: <code class="code">sd(0,10,0)</code>
395: </td>
396: <td align="center">
397: <code class="code">sd(0,14,0)</code>
398: </td>
399: <td align="center">
400: <code class="code">sd(0,18,0)</code>
401: </td>
402: <td align="center">N/A</td>
403: </tr>
404: <tr>
405: <td align="center">3/80 rev 2.9.2</td>
406: <td align="center">
407: <code class="code">sd(0,0,0)</code>
408: </td>
409: <td align="center">
410: <code class="code">sd(0,8,0)</code>
411: </td>
412: <td align="center">
413: <code class="code">sd(0,10,0)</code>
414: </td>
415: <td align="center">
416: <code class="code">sd(0,18,0)</code>
417: </td>
418: <td align="center">
419: <code class="code">sd(0,20,0)</code>
420: </td>
421: <td align="center">
422: <code class="code">sd(0,28,0)</code>
423: </td>
424: <td align="center">
425: <code class="code">sd(0,30,0)</code>
426: </td>
427: <td align="center">N/A</td>
428: </tr>
429: </tbody>
430: </table>
431: </div>
432: <p> </p>
433:
434:
435: <div class="informaltable">
436: <a name="cpu_monitor"></a>
437: <table border="1">
438: <colgroup>
439: <col class="col1">
440: <col class="col2">
441: <col class="col3">
442: <col class="col4">
443: <col class="col5">
444: <col class="col6">
445: <col class="col7">
446: <col class="col8">
447: <col class="col9">
448: </colgroup>
449: <thead>
450: <tr>
451: <th rowspan="2">CPU/rev ROM</th>
452: <th colspan="8" align="center">Monitor device to
453: boot the tape at target</th>
454: </tr>
455: <tr>
456: <th>0</th>
457: <th>1</th>
458: <th>2</th>
459: <th>3</th>
460: <th>4</th>
461: <th>5</th>
462: <th>6</th>
463: <th>7</th>
464: </tr>
465: </thead>
466: <tbody>
467: <tr>
468: <td>3/60 rev 1.9</td>
469: <td>???</td>
470: <td>
471: <code class="code">st(0,8,0)</code>
472: </td>
473: <td>
474: <code class="code">st(0,10,0)</code>
475: </td>
476: <td>
477: <code class="code">st(0,18,0)</code>
478: </td>
479: <td>
480: <code class="code">st(0,0,0)</code>
481: </td>
482: <td>
483: <code class="code">st(0,28,0)</code>
484: </td>
485: <td>
486: <code class="code">st(0,30,0)</code>
487: </td>
488: <td>N/A</td>
489: </tr>
490: <tr>
491: <td>3/80 rev 2.9.2</td>
492: <td>???</td>
493: <td>
494: <code class="code">st(0,8,0)</code>
495: </td>
496: <td>
497: <code class="code">st(0,10,0)</code>
498: </td>
499: <td>
500: <code class="code">st(0,18,0)</code>
501: </td>
502: <td>
503: <code class="code">st(0,0,0)</code>
504: </td>
505: <td>
506: <code class="code">st(0,28,0)</code>
507: </td>
508: <td>
509: <code class="code">st(0,30,0)</code>
510: </td>
511: <td>N/A</td>
512: </tr>
513: </tbody>
514: </table>
515: </div>
516: <p> The above tables also assume that you want SCSI logical unit number zero. The
517: SCSI specification allows one SCSI target to contain different logical units
518: (also called LUNs). Virtually no SCSI devices make use of this feature, and have
519: only a single LUN, zero. However, if you know you have a disk at a LUN other
520: than zero (early Sun SCSI disk setups do), you can add the LUN number to the
521: <span class="emphasis"><em>unit</em></span> value, noting that <span class="emphasis"><em>unit</em></span> is a
522: hexadecimal number. </p>
523:
524: <h4 class="title">
525: <a name="sun3x-history"></a>History of NetBSD/sun3x (<a href="#general">top</a>)
526: </h4>
527: <p> The sun3x port of NetBSD was initiated by two independent groups of
528: developers. The first group, headed by Gordon Ross and Jeremy Cooper, began work
529: in March of 1996 with the (then) current sun3 port and the intent to create a
530: new pmap system that was not based on the hp300 m68k code. Their work is the
531: officially supported version of NetBSD/sun3x. </p>
532: <p> The second group, headed by Tsubai Masanari, also began with the sun3
533: distribution but instead choose to use the traditional hp300 m68k pmap. This
534: approach allowed them to get a fully running system in a matter of weeks. They
535: were the first to successfully integrate the SPARC Enhanced SCSI Processor
536: driver into the kernel, proving that the Sun3x was indeed half SPARC, half Sun3. </p>
537: <p> Although the currently supported NetBSD/sun3x is based on Gordon and Jeremy's
538: work, they are indebted to the second group for their innovation. </p>
539: <p> Between NetBSD 1.3 and 1.4 NetBSD/sun3x was merged into NetBSD/sun3. They
540: build separate kernels, but share the same userland, and kernel build tree.
541: </p>
542: <hr>
543: <h3 class="title">Other sources of information</h3>
544: <h4 class="title">
545: <a name="sunhelp"></a>SunHELP (<a href="#info_sources">top</a>)
546: </h4>
547: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
548: <a class="ulink" href="http://www.sunhelp.com/" target="_top">SunHELP</a> - much
549: sun related information
550: </li></ul></div>
551:
552: <h4 class="title">
553: <a name="hwreffaq"></a>Sun Hardware Reference FAQ (<a href="#info_sources">top</a>)
554: </h4>
555: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
556: <a class="ulink" href="http://www.mso.anu.edu.au/~kim/faq/hardfaq.html" target="_top">Sun
557: Hardware Reference FAQ</a> - overview of Sun hardware
558: over the years
559: </li></ul></div>
560:
561: <h4 class="title">
562: <a name="hostidfaq"></a>Sun NVRAM/Hostid FAQ (<a href="#info_sources">top</a>)
563: </h4>
564: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
565: <a class="ulink" href="http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html" target="_top">Sun NVRAM/Hostid FAQ</a> - if your machine PROM's battery has gone dead
566: </li></ul></div>
567:
568: <h4 class="title">
569: <a name="cdromfaq"></a>Sun CD-ROM FAQ (<a href="#info_sources">top</a>)
570: </h4>
571: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
572: <a class="ulink" href="http://www.pimpworks.org/sun/cdrom.html" target="_top">Sun
573: CD-ROM FAQ</a> - lists which CD-ROM drives can boot a
574: Sun
575: </li></ul></div>
576:
577: <h4 class="title">
578: <a name="installnotes"></a>NetBSD 6.0 install notes (<a href="#info_sources">top</a>)
579: </h4>
580: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
581: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-6.0/sun3/INSTALL.html" target="_top">NetBSD 6.0 install notes</a> - supported hardware and how to install.
582: </li></ul></div>
583:
584: <h4 class="title">
585: <a name="mailinglist"></a>port-sun3 mailing list (<a href="#info_sources">top</a>)
586: </h4>
587: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
588: <a class="ulink" href="../../mailinglists/#port-sun3" target="_top"> port-sun3 mailing list</a> -
589: if you have any additional questions please subscribe.
590: </li></ul></div>
591:
592: <h4 class="title">
593: <a name="disklesshowto"></a>Diskless NetBSD HOW-TO (<a href="#info_sources">top</a>)
594: </h4>
595: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
596: <a class="ulink" href="../../docs/network/netboot/" target="_top">Diskless NetBSD
597: HOW-TO</a>.
598: </li></ul></div>
599:
600: <h4 class="title">
601: <a name="sun3arc"></a>Sun3 Archive (<a href="#info_sources">top</a>)
602: </h4>
603: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
604: The <a class="ulink" href="http://www.sun3arc.org/" target="_top">Sun3 Archive</a> has lots of
605: information about Sun3 hardware, PROM images, etc.
606: </li></ul></div>
607:
608: <h4 class="title">
609: <a name="techrat"></a>Techrat's Sun 3/160 pages (<a href="#info_sources">top</a>)
610: </h4>
611: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
612: <a class="ulink" href="http://www.obsolyte.com/sun3/" target="_top">Techrat's Sun 3/160
613: pages</a> contains information on Techrat's 3/160, hardware information,
614: lots of pictures of old Sun hardware, and links to various FAQs and
615: things.
616: </li></ul></div>
617:
618: <h4 class="title">
619: <a name="netbsddocs"></a>General NetBSD Documentation (<a href="#info_sources">top</a>)
620: </h4>
621: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
622: <a class="ulink" href="../../docs/" target="_top">General NetBSD Documentation</a> -
623: for questions not specific to NetBSD/sun3.
624: </li></ul></div>
625: <hr>Back to <em><a href="./">NetBSD/sun3 Port Page</a></em>
626: </div></div></div>
627: """
628:
629: ]]
630: [[!tag tier2port]]
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb
![[BACK]](/icons/back.gif){kind=icon}
Return to sun3.mdwn CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [NetBSD Developer Wiki] / wikisrc / ports