htdocs/Ports/sparc/faq.html - view

File: [cvs.NetBSD.org] / htdocs / Ports / sparc / Attic / faq.html
Revision 1.116: download - view: text, annotated - select for diffs
Mon Jan 17 05:42:11 2005 UTC (20 years, 4 months ago) by jschauma
Branches: MAIN
CVS tags: HEAD

regen

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html xmlns:html="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta name="generator" content="Website XSL Stylesheet V2.3"> <link rel="home" href="../../." title="Welcome to The NetBSD Project: Of course it runs NetBSD."> <link rel="up" href="../../Ports/." title="Hardware Supported by NetBSD"> <link rel="previous" href="../../Ports/sgimips/." title="NetBSD/sgimips"> <link rel="next" href="../../Ports/sun3/." title="NetBSD/sun3"> <link rel="first" href="../../Ports/acorn26/." title="NetBSD/acorn26"> <link rel="last" href="../../Ports/xen/." title="NetBSD/xen"> <link rel="stylesheet" href="/NetBSD.css" type="text/css"> <title>NetBSD/sparc Frequently Asked Questions</title> </head> <body class="website" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="webpage"> <a name="sparc-faq"></a><h1>NetBSD/sparc Frequently Asked Questions</h1> <h3 class="title"> <a name="general"></a>General Questions</h3> <ul> <li><a href="#mpg123-nosupportedrate">I'm getting a No supported rate found! error from mpg123</a></li> <li><a href="#serial-console-garbage">Serial console displays garbage</a></li> <li><a href="#consoleopt">How do I change console options such as colour or font size?</a></li> <li><a href="#voyager-mouse">The mouse on SPARCstation Voyager acts weird in X (ms0: input error (0xc47))</a></li> <li><a href="#cgsix-framebuffer-garbage">Framebuffer displays garbage on scrollback</a></li> <li><a href="#sparclinux-sun4c">Why is NetBSD so much faster than SparcLinux on sun4c</a></li> <li><a href="#illegal-reloc">I get a ld: /usr/lib/c++rt0.o: illegal reloc type mix when compiling</a></li> <li><a href="#boot-floppy">Making install boot floppies</a></li> <li><a href="#bootcd">Making a bootable CD-ROM</a></li> <li><a href="#nell">Using the nell sbus-to-PCMCIA bridge</a></li> </ul> <h3 class="title"> <a name="hardware"></a>Hardware Questions</h3> <ul> <li><a href="#smp-cpus">What CPU modules are capable of running multiprocessor</a></li> <li><a href="#video-cables">How do I hook up a VGA monitor to my Sun</a></li> <li><a href="#pmap-failure">What does a message similar to "*** U0209 ***" "PMAP 000d5000, Exp = 00000000, Obs = 04000000" from the PROM mean</a></li> <li><a href="#ross-mbus">Are hyperSPARC mbus modules supported?</a></li> <li><a href="#ross-memory">What is the memory configuration in a Ross sparc 20 clone?</a></li> <li><a href="#oldscsi">How do I hook up this strange SCSI connector to a normal device</a></li> </ul> <h3 class="title"> <a name="booting"></a>PROM/Booting Questions</h3> <ul> <li><a href="#abort-to-prom">How to abort to the prom</a></li> <li><a href="#prom-troubleshooting">Troubleshooting PROM problems</a></li> <li><a href="#non-sun-cdrom">Why won't my non-Sun SCSI CD-ROM drive boot the NetBSD/sparc CD-ROM?</a></li> <li><a href="#sun4c-sw-cache">sw flush: cache enabled</a></li> <li><a href="#no-kernel-1-6-install">open netbsd: no such file or directory</a></li> <li><a href="#sun4c-framebuffer-speedup">How to speed up the framebuffer on sun4c hosts</a></li> <li><a href="#cylinders">Do I really have to have my partitions start and end on cylinder boundaries</a></li> <li><a href="#prom-passwd">The PROM wants a password when I abort booting</a></li> <li><a href="#cachechipbug">What does the cache chip bug; trap page uncached kernel message mean?</a></li> <li><a href="#floppy-memory-boundary">When booting from 1.4.2 floppies, you get "Data Access Exception"</a></li> <li><a href="#powerlite85-floppy">How do I boot an RDI PowerLite 85 from a floppy disk?</a></li> </ul> <h3 class="title"> <a name="serial"></a>Serial Port Questions</h3> <ul> <li><a href="#sparc2-serial-console">Problems running a serial console on a SPARCstation 2 prior to NetBSD 1.4.2</a></li> <li><a href="#serial-unplug">Whenever I unplug the serial console, my machine reboots!</a></li> <li><a href="#serial-port-minidin8">Can I use a Macintosh serial cable on machines that have a MiniDin8 connector?</a></li> <li><a href="#serial-port-splitter">Splitting the serial port on a SPARCstation 20 and SPARC classic</a></li> <li><a href="#fastserial">Can I run my built-in serial port faster than 38400 bps?</a></li> </ul> <h3 class="title"> <a name="ethernet"></a>Ethernet Questions</h3> <ul> <li><a href="#ether-address">All my ethernet interfaces have the same hardware address</a></li> <li><a href="#dead-nvram">Ethernet address or hostid are all ones</a></li> <li><a href="#tadpole-3gx-transceiver">Tadpole 3GX transceiver does not work if not \</a></li> </ul> <h3 class="title"> <a name="javastation"></a>JavaStation Questions</h3> <ul> <li><a href="#javastation-supported">Which JavaStations are supported?</a></li> <li><a href="#javastation-info">Hardware information</a></li> <li><a href="#fox">What was the Fox?</a></li> </ul> <h3 class="title"> <a name="emulation"></a>SunOS and Solaris Emulation Questions</h3> <ul> <li><a href="#solaris-filesystem">Does NetBSD support the Solaris filesystem?</a></li> <li><a href="#emulation-setup">How do I set up SunOS/Solaris emulation?</a></li> <li><a href="#netscape">Can NetBSD/sparc run Netscape</a></li> <li><a href="#sunos-netscape-socket">Under SunOS emulation, Netscape fails with `Error: Can't open display: :0.0'</a></li> </ul> <h3 class="title"> <a name="other-sources"></a>Other sources of information</h3> <ul> <li><a href="#sun-system-handbook">Sun System Handbook</a></li> <li><a href="#memory-modules">Memory Modules</a></li> <li><a href="#SunHelp">SunHELP</a></li> <li><a href="#sun-hardware-reference">Sun Hardware Reference FAQ</a></li> <li><a href="#openboot-collection">OpenBoot Collection</a></li> <li><a href="#sun-hostid-faq">Sun NVRAM/Hostid FAQ</a></li> <li><a href="#sun-erial-port">Sun Serial Port & Cable Pinouts</a></li> <li><a href="#frame-buffer-faq">Frame Buffer FAQ</a></li> <li><a href="#sunchack-data">The SunShack Data Archive</a></li> <li><a href="#sparc-cpu-resources">Technical SPARC CPU resources</a></li> <li><a href="#mixing-mbus">Information about mixing MBus modules</a></li> </ul> <h3 class="title"> <a name="other-onsite"></a>Other sources of information from NetBSD.org</h3> <ul> <li><a href="#install-notes">NetBSD 2.0 install notes</a></li> <li><a href="#port-sparc-ml">port-sparc mail list</a></li> <li><a href="#diskless-howto">Diskless NetBSD HOW-TO.</a></li> <li><a href="#serial-primer">NetBSD Serial Port Primer</a></li> <li><a href="#general-docs">General NetBSD Documentation</a></li> </ul> <hr> <h3 class="title">General Questions</h3> <h4 class="title"> <a name="mpg123-nosupportedrate"></a>I'm getting a <code class="code"><span class="bold"><strong>No supported rate found!</strong></span></code> error from mpg123 (<a href="#general">top</a>) </h4> <p> If you've gotten this error you'll have to pass arguments to mpg123 for your number of channels and rate of stream. Older systems (such as the sun4c machines and the SPARC Classic) only support an 8 bit 8 kHz mono sampling rate. For these systems, you would specify: </p> <table class="programlisting"><tr><td><pre> mpg123 -m -r 8000 <code class="filename">filename</code> </pre></td></tr></table> <p> The -m option is for mixing both channels for mono output, and the -r specifies the rate that the audio card supports. </p> <h4 class="title"> <a name="serial-console-garbage"></a>Serial console displays garbage (<a href="#general">top</a>) </h4> <p> Typically this is because the default terminal type for console is <code class="code">sun</code> and most serial terminals are <code class="code">vt100</code> (or similar), and they use different escape codes. The temporary fix is to change your terminal type: </p> <table class="programlisting"><tr><td><pre># <span class="bold"><strong>setenv TERM vt100</strong></span></pre></td></tr></table> <p>> The permanent solution is to edit <code class="code">/etc/ttys</code> and change the <code class="code">console</code> line to read: </p> <table class="programlisting"><tr><td><pre>console "/usr/libexec/getty suncons" vt100 on secure</pre></td></tr></table> <p> Then you need to <code class="code">kill -HUP 1</code> or reboot. </p> <h4 class="title"> <a name="consoleopt"></a>How do I change console options such as colour or font size? (<a href="#general">top</a>) </h4> <p> You have to recompile a kernel for this. For example, for a white on black console, add the following to your kernel config file: </p> <table class="programlisting"><tr><td><pre> options RASTERCONSOLE_FGCOL=WSCOL_WHITE options RASTERCONSOLE_BGCOL=WSCOL_BLACK </pre></td></tr></table> <p> </p> <p> For a smaller font, add the following: </p> <table class="programlisting"><tr><td><pre> options FONT_BOLD8x16 </pre></td></tr></table> <p> </p> <p> Another useful option is </p> <table class="programlisting"><tr><td><pre> options RASTERCONS_FULLSCREEN </pre></td></tr></table> <p> </p> <h4 class="title"> <a name="voyager-mouse"></a>The mouse on SPARCstation Voyager acts weird in X (<code class="code">ms0: input error (0xc47)</code>) (<a href="#general">top</a>) </h4> <p> Apparently the original mouse that came with the Voyager (the Compact1 370-1865-01 mouse, but not the 370-1865-03) runs at a faster serial speed than every other Sun mouse (4800 bps instead of 1200 bps). You have two options: </p> <div class="itemizedlist"><ul type="disc"> <li>Use another mouse</li> <li>Add <code class="code">options SUN_MS_BPS=4800</code> to your kernel configuration and recompile</li> </ul></div> <p> See <a href="http://netbsd.gw.com/cgi-bin/man-cgi?ms+4+NetBSD-current">ms(4)</a> for more information. </p> <h4 class="title"> <a name="cgsix-framebuffer-garbage"></a>Framebuffer displays garbage on scrollback (<a href="#general">top</a>) </h4> <p> When exiting vi, and sometimes when scrolling back, the display scrolls back for a few seconds displaying a lot of garbage. There is usually garbage in the non-text portion of the screen as well. This is purported to be caused by a firmware bug on Sbus cgsix boards, and has to date been noticed on all machines in which a cgsix board is installed. </p> <p> Some options: </p> <p> </p> <div class="itemizedlist"><ul type="disc"> <li>Set your terminal type to <code class="code">sun-cgsix</code>.</li> <li>Edit your termcap so that the default '<code class="code">sun</code>' entry has <code class="code">:tc=sun-cgsix:</code> instead of <code class="code">:tc=sun-il:</code> </li> <li>Edit <code class="code">/etc/ttys</code> and change <table class="programlisting"><tr><td><pre>console "/usr/libexec/getty suncons" sun on secure</pre></td></tr></table> to <table class="programlisting"><tr><td><pre>>console "/usr/libexec/getty suncons" sun-cgsix on secure</pre></td></tr></table> </li> </ul></div> <p> </p> <h4 class="title"> <a name="sparclinux-sun4c"></a>Why is NetBSD so much faster than SparcLinux on sun4c (<a href="#general">top</a>) </h4> <p> The memory management hardware on sun4c machines (SPARCstation 1, 1+, 2, IPC, IPX, SLC, ELC and clones) is not handled particularly well by Linux. Until Linux reworks their MMU code NetBSD will be significantly faster on this hardware. There was a longstanding bug prior to NetBSD 1.6.2 on SPARCstation/server 1, SPARCstation/server 1+, and Sun IPC models. We recommend updating these models to the latest version of NetBSD to for improved stability and speed. See <a href="#sun4c-sw-cache" target="_top"><code class="code">sw flush: cache enabled</code></a>. </p> <h4 class="title"> <a name="illegal-reloc"></a>I get a <code class="code"><span class="bold"><strong>ld: /usr/lib/c++rt0.o: illegal reloc type mix</strong></span></code> when compiling (<a href="#general">top</a>) </h4> <p> For versions older than 1.4.3, the default NetBSD/sparc /usr/lib/c++rt0.o is compiled -fpic. This means it can only handle offsets up to a certain size, and can fail to work in large programs. Compiling -fPIC allows larger offsets and should permit large programs to function. </p> <p> If you're using a NetBSD release before 1.4.3, replacing /usr/lib/c++rt0.o with a -fPIC version, located at <a href="ftp://ftp.NetBSD.org/pub/NetBSD/arch/sparc/c++rt0/" target="_top">ftp://ftp.NetBSD.org/pub/NetBSD/arch/sparc/c++rt0/</a>, will solve this problem. </p> <h4 class="title"> <a name="boot-floppy"></a>Making install boot floppies (<a href="#general">top</a>) </h4> <p> To create install floppies for NetBSD/sparc, you first need to have the release source. You also need to have the release files installed; you'll find them under the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-release-1-6/tar_files/src/distrib.tar.gz" target="_top"> NetBSD-release</a> section. Note that the release source extracts to the <code class="code">src</code> directory, so be sure to extract the archive under <code class="code">/usr</code>. Next, create the INSTALL kernel: </p> <table class="programlisting"><tr><td><pre> # cd /sys/arch/sparc/INSTALL; make</pre></td></tr></table> <p> After the kernel has build, you can create the installation floppies: </p> <table class="programlisting"><tr><td><pre># cd /usr/src/distrib/sparc/sysinst.ramdisk; make # cd /usr/src/distrib/sparc/sysinst.bootfs; make</pre></td></tr></table> <p> </p> <h4 class="title"> <a name="bootcd"></a>Making a bootable CD-ROM (<a href="#general">top</a>) </h4> <p> See the <a href="../../Documentation/bootcd.html#sparcimage" target="_top">NetBSD Bootable CD ROM HOWTO</a>. </p> <h4 class="title"> <a name="nell"></a>Using the <span class="emphasis"><em>nell</em></span> sbus-to-PCMCIA bridge (<a href="#general">top</a>) </h4> <p> NetBSD 1.6 and later support cardbus and PCMCIA cards with the SPARCstation Voyager's on-board interface and with the nell sbus-to-PCMCIA bridge card. Support was dramatically improved in NetBSD 2.0, fixing many longstanding bugs. All PCMCIA devices listed on the <a href="../../Hardware/pcmcia.html" target="_top">Machine-independent PCMCIA drivers</a> page should work in NetBSD 2.0. Some have been tested. The GENERIC kernel has the nell interface disabled by default. You'll need to build a kernel with the nell and various pcmcia interfaces uncommented. </p> <p>In NetBSD 1.6.x, there is a byte endian issue which currently prevents 16 bit devices from working. See the <a href="http://mail-index.NetBSD.org/port-sparc/2002/03/10/0002.html" target="_top">post</a> by Martin Husemann on nell support. This problem is fixed in NetBSD 2.0 and later. </p> <p>In NetBSD 1.6.x, There is a conflict between the <span class="emphasis"><em>audioamd</em></span> device in sun4c and some sun4m models and the (nell) device. This problem is fixed in NetBSD 2.0 and later. </p> <p>If your 1.6.x system has the audioamd device on-board and you want to use it and the nell interface, you need to build a new kernel with the following option: </p> <table class="programlisting"><tr><td><pre> options AUDIO_C_HANDLER </pre></td></tr></table> <p> This problem is fixed in NetBSD 2.0 and later. </p> <p>If you wish to use the Lucent WaveLAN card on 1.6.x, you will need to add the following hack to your kernel configuration: </p> <table class="programlisting"><tr><td><pre> options WI_AT_BIGENDIAN_BUS_HACK wi* at pcmcia? function ? # Lucent WaveLan IEEE (802.11) </pre></td></tr></table> <p> </p> <hr> <h3 class="title">Hardware Questions</h3> <h4 class="title"> <a name="smp-cpus"></a>What CPU modules are capable of running multiprocessor (<a href="#hardware">top</a>) </h4> <p> <span class="emphasis"><em>Note: This capability was added in NetBSD 2.0. NetBSD 1.6.x and earlier will only use one CPU if more than one is present.</em></span> </p> <p>The only NetBSD/sparc models capable of SMP are the Sun 4/600, SPARCstation/server 10, SPARCstation/server 20, and clones of these models. Most SuperSPARC-I, SuperSPARC-II, and hyperSPARC MBus CPU modules can be used in an SMP system. Briefly, two modules with the same speed and (non-zero) cache size will have no problems. Modules with different cache sizes and speeds have been reported to work, but you run into trouble when using older (i.e. slower) modules and modules without caches. Check the following references: </p> <div class="itemizedlist"><ul type="disc"> <li><a href="http://www.sunshack.org/data/suncpum.html" target="_top">Sun CPU and Memory Tables</a></li> <li><a href="http://mbus.sunhelp.org/" target="_top">The Rough Guide to MBus Modules</a></li> </ul></div> <p> </p> <p>You will need to use the GENERIC.MP kernel, or a kernel with the following options enabled: </p> <table class="programlisting"><tr><td><pre>options MULTIPROCESSOR # include multiprocessor support cpu* at mainbus0 # declare additional CPUs</pre></td></tr></table> <p> </p> <p>To boot from a different CPU, run the following commands at the PROM prompt: </p> <table class="programlisting"><tr><td><pre><#0> ok <span class="bold"><strong>N switch-cpu</strong></span></pre></td></tr></table> <p> Where <code class="code"><span class="bold"><strong>N</strong></span></code> is the cpu number you want to switch to. 0 is the primary CPU on the first mbus module. 1 is the second CPU on the first module. 2 is the first CPU on the second module. 3 is the second CPU on the second module. Switching to a non-existent CPU may cause your system to hang. You must have already booted NetBSD once to load the CPU code into the PROM. See Paul Kranenburg's <a href="http://mail-index.NetBSD.org/port-sparc/2003/01/20/0016.html" target="_top">post</a>. </p> <h4 class="title"> <a name="video-cables"></a>How do I hook up a VGA monitor to my Sun (<a href="#hardware">top</a>) </h4> <p> Well, there are two ways, build your own cable, or purchase an adapter. The adapters can be found for around US$30 and the framebuffer will typically "just work" at its default resolution. </p> <p> To build your own cable, can follow the <a href="http://mail-index.NetBSD.org/port-sparc/2000/04/22/0001.html" target="_top">instructions </a>provided by Izumi Tsutsui. </p> <p> Don't forget to take a look at the <a href="http://www.sunhelp.org/faq/FrameBuffer.html" target="_top">Frame Buffer FAQ</a> for information on your framebuffer, what resolutions it supports, and how to set the default resolution in the prom. </p> <h4 class="title"> <a name="pmap-failure"></a>What does a message similar to <code class="code">"*** U0209 ***</code>" "<code class="code">PMAP 000d5000, Exp = 00000000, Obs = 04000000</code>" from the PROM mean (<a href="#hardware">top</a>) </h4> <p> If the page map ram on a sparc2 fails the PROM will not initialise the frambuffer, but will output a message similar to </p> <table class="programlisting"><tr><td><pre> *** U0209 *** PMAP = 000d5000, Exp = 00000000, Obs = 04000000 </pre></td></tr></table> <p> to the serial console. (the U0209 can also be U0208). The only options are to replace the chip, which requires exceptionally delicate soldering work, or the entire motherboard. </p> <h4 class="title"> <a name="ross-mbus"></a>Are hyperSPARC mbus modules supported? (<a href="#hardware">top</a>) </h4> <p> Yes. All Ross hyperSPARC modules should work. See also <a href="#smp-cpus" target="_top">What CPU modules are capable of running multiprocessor</a>. </p> <h4 class="title"> <a name="ross-memory"></a>What is the memory configuration in a Ross sparc 20 clone? (<a href="#hardware">top</a>) </h4> <p> Ben Cottrell reports that: “<span class="quote">For anyone else who's curious about this, the slots in a Ross sparc 20 clone go like: 0 4 1 5 2 6 3 7, going top to bottom, looking down on the case in its conventional orientation. </span>” </p> <h4 class="title"> <a name="oldscsi"></a>How do I hook up this strange SCSI connector to a normal device (<a href="#hardware">top</a>) </h4> <p> Older sun4 machines might have an old style SCSI connector with three rows of pins. The pins are listed on <a href="oldscsipins.html" target="_top">this page</a>. </p> <hr> <h3 class="title">PROM/Booting Questions</h3> <h4 class="title"> <a name="abort-to-prom"></a>How to abort to the prom (<a href="#booting">top</a>) </h4> <p> There are three ways to abort to the prom: </p> <p> </p> <div class="itemizedlist"><ul type="disc"> <li>If using a Sun keyboard, Press <code class="code">[L1]</code>+<code class="code">[A]</code>, (or <code class="code">[STOP]</code>+<code class="code">[A]</code>)</li> <li>If using a Tadpole SPARCbook keyboard, press <code class="code">[Pause]</code>+<code class="code">[A]</code> </li> <li>If using a serial console, send a BREAK signal (the method may very from terminal to terminal).</li> </ul></div> <p> </p> <p> Once at the prom you can continue with '<code class="code">go</code>' ('ok' prompt), or '<code class="code">c</code>' (> prompt). </p> <h4 class="title"> <a name="prom-troubleshooting"></a>Troubleshooting PROM problems (<a href="#booting">top</a>) </h4> <p> See the troubleshooing guide at <a href="http://docs.sun.com/db?p=/doc/806-2906-10/6jc3f0abd&a=view" target="_top">docs.sun.com</a>. Additionally, if your ethernet address is <code class="code">FF:FF:FF:FF:FF:FF</code>, then your NVRAM is dead and you may have trouble booting. See <a href="#dead-nvram" target="_top">Ethernet address or hostid are all ones</a>. </p> <h4 class="title"> <a name="non-sun-cdrom"></a>Why won't my non-Sun SCSI CD-ROM drive boot the NetBSD/sparc CD-ROM? (<a href="#booting">top</a>) </h4> <p> Most UNIX workstations, including Sun's OpenBoot PROM, have a PROM that requires the CD-ROM to support a 512 byte block size. Most OEM Sun CD-ROM drives are set to 512 byte block size by default. Most newer 3rd party drives automatically support both 512 and 2048 byte block sizes. Older 3rd party drives may have a jumper to change the value from 2048 bytes to 512 bytes. Check with your hardware vendor -- those drives that do not support 512 byte sectors will be unusable for booting, but will be useable once the kernel is loaded for normal operations. </p> <p>See the <a href="http://www.ebsinc.com/solaris/suncdrom.html" target="_top">Sun CD-ROM FAQ</a>. </p> <h4 class="title"> <a name="sun4c-sw-cache"></a><code class="code">sw flush: cache enabled</code> (<a href="#booting">top</a>) </h4> <p> Prior to NetBSD 1.6.2, there was a longstanding MMU bug in the sun4c architecture. NetBSD 1.6 and 1.6.1 attempted to work around this bug by using a slower caching mechanism on the SPARCstation/server 1, SPARCstation/server 1+, and Sun IPC. All known problems are fixed in 1.6.2 and later. Read Paul Kranenburg's <a href="http://mail-index.NetBSD.org/port-sparc/2003/07/18/0002.html" target="_top">post</a> for more information. </p> <h4 class="title"> <a name="no-kernel-1-6-install"></a><code class="code">open netbsd: no such file or directory</code> (<a href="#booting">top</a>) </h4> <p> D'oh. The NetBSD 1.6 installer does not install a kernel if you select the default install. This is, of course, corrected in NetBSD 1.6.1 and later. </p> <p>The easy fix is to run the installer again and select <code class="code">Re-install sets or install additional sets</code> and chose the <code class="code">kern-GENERIC.tgz</code> package to install. </p> <h4 class="title"> <a name="sun4c-framebuffer-speedup"></a>How to speed up the framebuffer on sun4c hosts (<a href="#booting">top</a>) </h4> <p> Here is a shellscript provided by greywolf@starwolf.com which speeds up PROM access to the framebuffer on sun4c hosts running OBP version 2 and greater (such as the IPX). </p> <table class="programlisting"><tr><td><pre> #! /bin/sh - eeprom 'nvramrc=probe-all install-console ramforth : cache-page dup pgmap@ cacheable swap pgmap! ; up@ cache-page here origin do i cache-page pagesize +loop banner' eeprom 'use-nvramrc?=true' exit 0 </pre></td></tr></table> <p> </p> <h4 class="title"> <a name="cylinders"></a>Do I really have to have my partitions start and end on cylinder boundaries (<a href="#booting">top</a>) </h4> <p> Yes and no. The prom only knows how to load a bootloader from the beginning of a cylinder. This means that your bootable partitions need to start on cylinder boundaries. The cylinder size in your disklabel does not have to bear any relation to the actual physical cylinder size of the disk. You can't just set your cylinder size to 1 (i.e. the number of cylinders = the number of sectors), since the number of cylinders is stored as a 16 bit number (i.e. your disk could only be about 32 MB). </p> <p> The partitions apparently do not need to end on cylinder boundaries, and there are no bad side-effects of doing so. </p> <h4 class="title"> <a name="prom-passwd"></a>The PROM wants a password when I abort booting (<a href="#booting">top</a>) </h4> <p> You need physical access to the machine to erase the password. Power off, power on, hold <code class="code">[L1]</code>+<code class="code">[N]</code>, (or <code class="code">[STOP]</code>+<code class="code">[N]</code>) until the PROM prompt. This will reset your PROM to the factory defaults. </p> <p> Alternatively (this is not for the faint of heart), power on, abort, wait for the password prompt, carefully remove the PROM chip, hit return, carefully replace the PROM, enter a new password. </p> <h4 class="title"> <a name="cachechipbug"></a>What does the <code class="code"><span class="bold"><strong>cache chip bug; trap page uncached</strong></span></code> kernel message mean? (<a href="#booting">top</a>) </h4> <p> If you get this kernel message, nothing has gone wrong. Machines with "buserr-type" 1 have a bug in the cache chip that affects traps. The <code class="code"><span class="bold"><strong>cache chip bug; trap page uncached</strong></span></code> message is the kernel activating a workaround for this bug. </p> <p> Without this workaround, the cache simply delivers wrong data. Often this turns into an illegal instruction, so that you get a trap during a trap, which causes a reset. This condition can only be caught by the ROM, and by then it is too late to do anything about it. This message, if you happen to get it, just means you'll avoid that problem. </p> <h4 class="title"> <a name="floppy-memory-boundary"></a>When booting from 1.4.2 floppies, you get "Data Access Exception" (<a href="#booting">top</a>) </h4> <p> Unfortunately, the NetBSD 1.4.2 floppies, have a problem with the bootloader on some machines (in particular, sun4c machines with non-contiguous memory banks, such as the IPX). If you encounter this error, then you will need to download the repaired <a href="ftp://ftp.NetBSD.org/pub/NetBSD/arch/sparc/1.4.2-bootfs/" target="_top">floppy images</a> or install a 16 MB SIMM in the first bank of your machine (4 MB isn't large enough to hold the broken bootloader and the kernel). </p> <p> This problem is only present on 1.4.2 boot floppies. It has been fixed in -current and will not be present in future releases of NetBSD/sparc. </p> <h4 class="title"> <a name="powerlite85-floppy"></a>How do I boot an RDI PowerLite 85 from a floppy disk? (<a href="#booting">top</a>) </h4> <p> The PowerLite 85 seems to have an OpenBoot PROM bug in the floppy driver. Cliff Wright has determined the nvramrc patch to fix this: </p> <table class="programlisting"><tr><td><pre>: trk0_delay 50 ms 4 ; ['] trk0_delay false ['] 4 false ffd34e90 (patch) 4 true ['] 2 false ffd34f28 (patch)</pre></td></tr></table> <p> See his <a href="http://mail-index.NetBSD.org/port-sparc/2001/05/14/0001.html" target="_top">post</a> for more information. </p> <hr> <h3 class="title">Serial Port Questions</h3> <h4 class="title"> <a name="sparc2-serial-console"></a>Problems running a serial console on a SPARCstation 2 prior to NetBSD 1.4.2 (<a href="#serial">top</a>) </h4> <p> When booting a 1.4 or 1.4.1 kernel from a serial console, the following messages may appear: </p> <table class="programlisting"><tr><td><pre>Warning: unparseable stdin-path property Warning: unparseable stdout-path property cninit: invalid inSource 0xffffffff</pre></td></tr></table> <p> This is a know problem when booting with a serial console on a SPARCstation 2 with a PROM revision prior to 2.4. The full details can be found under <a href="http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=7409" target="_top"> PR/7409</a>. The problem has been solved in NetBSD 1.4.2. If you need a patched 1.4.1 GENERIC kernel, try <a href="ftp://ftp.yubyub.net/pub/NetBSD/NetBSD-1.4.1/sparc/netbsd.GENERIC_SS2_CONSOLE.gz" target="_top"> this one</a>. A patch which alters <code class="code">src/arch/sparc/dev/zs.c</code> to force <code class="code">/dev/ttya</code> as the only serial console can be found as <a href="ftp://ftp.yubyub.net/pub/NetBSD/NetBSD-1.4.1/sparc/zs.diff" target="_top"> zs.diff</a>. Note that this patch does not prevent a standard keyboard and monitor from being the console; it forces <code class="code">/dev/ttya</code> to be the console should a serial console be selected. </p> <h4 class="title"> <a name="serial-unplug"></a>Whenever I unplug the serial console, my machine reboots! (<a href="#serial">top</a>) </h4> <p> A continuous stream of zeros is equivalent to a "BREAK" command which will enter the prom. This might happen, since the serial lines are floating when you unplug your cable. If you build a special switchbox that uses a pullup resistor, then you can avoid this problem. </p> <p> Put a 4.7 KOhm resistor between pins 3 and 25. </p> <h4 class="title"> <a name="serial-port-minidin8"></a>Can I use a Macintosh serial cable on machines that have a MiniDin8 connector? (<a href="#serial">top</a>) </h4> <p> Yes and no. Yes, you can use it, but it doesn't support the same hardware handshaking lines so you won't get hardware handshaking. </p> <p> See the <a href="../../Documentation/Hardware/Misc/serial.html" target="_top">NetBSD Serial Port Primer</a> for more information. </p> <h4 class="title"> <a name="serial-port-splitter"></a>Splitting the serial port on a SPARCstation 20 and SPARC classic (<a href="#serial">top</a>) </h4> <p> Some sparc machines, such as the SPARCstation 20 and SPARC Classic, have 2 serial ports but use a single DB-25 connector. Serial port A is wired using the standard pin out so that it may be used with a "normal" (whatever that means with serial ports) serial cable. To use serial port B, an adapter cable is required. Dan McMahill has traced the pin out on a Sun P/N 530-1677-01 cable. </p> <p> </p> <div class="itemizedlist"><ul type="disc"> <li><a href="faq/sun_530-1677-01-rev50.txt" target="_top">Cable Diagram (ascii 4k)</a></li> <li><a href="faq/sun_530-1677-01-rev50.jpg" target="_top">Cable Diagram (jpeg 76k)</a></li> <li><a href="faq/sun_530-1677-01-rev50.ps" target="_top">Cable Diagram (postscript 18k)</a></li> </ul></div> <p> </p> <h4 class="title"> <a name="fastserial"></a>Can I run my built-in serial port faster than 38400 bps? (<a href="#serial">top</a>) </h4> <p> The short answer: No. </p> <p> The long answer is that you can possibly run it at non-standard speeds (such as 76800 bps and 51200 bps). der Mouse has patched things in the attempt to run the serial chip in an even <a href="http://mail-index.NetBSD.org/port-sparc/2000/04/25/0005.html" target="_top">faster mode</a>, but it is very unreliable (i.e. very error-prone). </p> <p> Note that some of the <a href="../sparc64/" target="_top">sparc64</a> machines can run their serial ports faster, but they use a different serial chipset. </p> <hr> <h3 class="title">Ethernet Questions</h3> <h4 class="title"> <a name="ether-address"></a>All my ethernet interfaces have the same hardware address (<a href="#ethernet">top</a>) </h4> <p> Yes, that's correct. In general, each machine only has one ethernet hardware address (a.k.a. MAC) for <span class="emphasis"><em>all</em></span> ethernet interfaces attached to it, since the MAC address is stored in the NVRAM on the motherboard instead of on the ethernet interface. </p> <p> This means that if you have a sparc box with more than one ethernet interface, no two interfaces can be on the same subnet. In most practical situations, this should not be a problem. For example: </p> <table class="programlisting"><tr><td><pre>smaug% ifconfig -a le0: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu 1500 address: 08:00:20:20:e2:54 media: Ethernet autoselect be0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 08:00:20:20:e2:54 media: Ethernet autoselect (10baseT half-duplex) </pre></td></tr></table> <p> </p> <h4 class="title"> <a name="dead-nvram"></a>Ethernet address or hostid are all ones (<a href="#ethernet">top</a>) </h4> <p> If a machine boots up with with an all-ones ethernet address (i.e. ff:ff:ff:ff:ff:ff) or hostid, it is most likely because the NVRAM has reached the end of its life cycle. This is especially common on sun4c class machines because the NVRAM used in those systems have relatively short life spans many of which are currently ending now. </p> <p> See the <a href="http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html" target="_top"> Sun NVRAM/Hostid FAQ</a> for information on how to replace and reinitialize the chip and possible workarounds if you cannot find a new NVRAM chip. </p> <p>If you don't know your system's original hostid and ethernet address, it may be possible to reconstruct them using the information on the nvram chip's barcode. See this <a href="http://mail-index.NetBSD.org/port-sparc/2001/09/04/0002.html" target="_top">post</a> and this <a href="http://mail-index.NetBSD.org/port-sparc/2001/09/04/0003.html" target="_top">post</a> for more information. </p> <h4 class="title"> <a name="tadpole-3gx-transceiver"></a>Tadpole 3GX transceiver does not work if not \ (<a href="#ethernet">top</a>) </h4> <p> plugged in at boot The interface may be autosensing to 10BaseT, even though there's no physical 10Base-T port. </p> <p> Check the media type in the output of "<code class="code"><span class="bold"><strong>ifconfig le0</strong></span></code>". it should read <code class="code">10Base5</code> to use the external transceiver, if not issue a "<code class="code"><span class="bold"><strong>ifconfig le0 media 10base5</strong></span></code>" command. </p> <hr> <h3 class="title">JavaStation Questions</h3> <h4 class="title"> <a name="javastation-supported"></a>Which JavaStations are supported? (<a href="#javastation">top</a>) </h4> <p>Read the <a href="javastation.html" target="_top"> JavaStation Status</a> page to determine what JavaStation you have, and which hardware is supported. </p> <h4 class="title"> <a name="javastation-info"></a>Hardware information (<a href="#javastation">top</a>) </h4> <p> The Linux on the Sun JavaStation NC HOWTO contains gobs of good info. <a href="http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/JavaStation-HOWTO.html#WHATISCHAPTER" target="_top"> Section 2</a> covers the various models and what sorts of guts they've got. <a href="http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/JavaStation-HOWTO.html#BACKGROUNDREQUIREMENTSCHAPTER" target="_top"> Section 3</a> describes the netboot environment (also see the NetBSD <a href="../../Documentation/network/netboot/" target="_top">Diskless HOW-TO</a> on how to set up netbooting for these puppies). And <a href="http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/JavaStation-HOWTO.html#APPENDIXCHAPTER" target="_top"> Section 10</a> lists the jumper settings for JavaStations. </p> <h4 class="title"> <a name="fox"></a>What was the Fox? (<a href="#javastation">top</a>) </h4> <p> The Fox is probably best described as a brick sized SS4. Among it's features: </p> <p> </p> <div class="itemizedlist"><ul type="disc"> <li> one SBus and one AFX slot side by side so you can only use one</li> <li> Crystal Semiconductor 4231 audio <span class="emphasis"><em>(audiocs)</em></span> </li> <li> stp4020 (PCMCIA) <span class="emphasis"><em>(nell)</em></span> </li> <li> the usual onboard serial a/b, SCSI, 10BaseT</li> </ul></div> <p> </p> <p> This was used in the early versions of the Java car, which later moved to a faster machine. </p> <hr> <h3 class="title">SunOS and Solaris Emulation Questions</h3> <h4 class="title"> <a name="solaris-filesystem"></a>Does NetBSD support the Solaris filesystem? (<a href="#emulation">top</a>) </h4> <p> Kinda. If Solaris 5 or later created a filesystem with access control lists (ACL), NetBSD's <a href="http://netbsd.gw.com/cgi-bin/man-cgi?fsck+8+NetBSD-current">fsck(8)</a> will render the superblock unusable to Solaris (i.e. Solaris can't mount the filesystem again). </p> <p>You should either mount your Solaris filesystem read-only or have created it without ACLs. See this <a href="http://mail-index.NetBSD.org/port-sparc/2001/03/10/0001.html" target="_top">post</a> by Christos Zoulas on this topic. </p> <h4 class="title"> <a name="emulation-setup"></a>How do I set up SunOS/Solaris emulation? (<a href="#emulation">top</a>) </h4> <p> <span class="bold"><strong>Note:</strong></span> Remember, despite Sun's marketing and the misleading output of uname on Solaris, SunOS and Solaris are not the same OS! SunOS 4.x (Solaris 1.x) is BSD, Solaris 2.x is SysV. SunOS uname says `SunOS 4.x', Solaris uname says `SunOS 5.x'. </p> <p> To setup Solaris emulation, you'll need to compile a kernel with COMPAT_SVR4, and copy the appropriate files from a Solaris system. For more information, please consult <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_svr4+8+NetBSD-current">compat_svr4(8)</a>. </p> <p> To setup SunOS emulation, you'll need to compile a kernel with COMPAT_SUNOS, and some of SunOS's libraries. They can be found at Sun's support site. You'll need the following libraries: </p> <p> </p> <div class="itemizedlist"><ul type="disc"> <li> <code class="code"><a href="ftp://sunsolve.sun.com/pub/patches/102545.readme" target="_top"> ftp://sunsolve.sun.com/pub/patches/102545-13.tar.Z</a></code> - This archive contains <code class="code">102545-13/lib/libc.so19</code> and <code class="code">102545-13/5lib/libc.so29</code>, which should be renamed to <code class="code">/emul/sunos/usr/lib/libc.so.1.9</code> and <code class="code">/emul/sunos/usr/5lib/libc.so.2.9</code> respectively.</li> <li> <code class="code"><a href="ftp://sunsolve.sun.com/pub/patches/100257-06.tar.Z" target="_top"> ftp://sunsolve.sun.com/pub/patches/100257-06.tar.Z</a></code> - This archive contains <code class="code">100257-06/4.1.3c/sun4/ld.so</code>, which should be renamed to <code class="code">/emul/sunos/usr/lib/ld.so</code> </li> <li>Lastly, you'll need to get <code class="code">libdl.so.1.0</code> from any SunOS machine, and place this file in <code class="code">/emul/sunos/usr/lib</code>. Please note that the <code class="code">libdl.so.1.0</code> from Solaris will not work for SunOS emulation. <p> For more information see <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_sunos+8+NetBSD-current">compat_sunos(8)</a>. </p> </li> </ul></div> <p> </p> <h4 class="title"> <a name="netscape"></a>Can NetBSD/sparc run Netscape (<a href="#emulation">top</a>) </h4> <p> There are three 'Netscape' browsers in the <a href="../../Documentation/software/packages.html" target="_top">NetBSD packages collection</a>: </p> <p> </p> <div class="itemizedlist"><ul type="disc"> <li> <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/communicator/README.html" class="pkgname">www/communicator</a> - complete Netscape communicator install including email. (requires SunOS or Solaris libraries)</li> <li> <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/navigator/README.html" class="pkgname">www/navigator</a> - Standalone Navigator browser (requires SunOS or Solaris libraries)</li> <li> <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/mozilla/README.html" class="pkgname">www/mozilla</a> - Free version of the Netscape browser.</li> </ul></div> <p> </p> <p> Both the communicator and navigator packages will run faster and provide more features than mozilla, but they require either Solaris libraries in /emul/svr4 (see <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_svr4+8+NetBSD-current">compat_svr4(8)</a>) or SunOS-4.1 libraries in /emul/sunos (see <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_sunos+8+NetBSD-current">compat_sunos(8)</a>). All of the SunOS-4.1 libraries except libdl.so are available from Sun's <a href="ftp://sunsolve.sun.com/pub/patches/" target="_top">ftp site</a>. If anyone is interested in putting together a libdl it would be greatly appreciated :) The Solaris-2.5.1 versions of communicator and navigator are the defaults as current netscape versions are available for Solaris. It appears that netscape-4.61 was the last SunOS-4.1 version available. If you wish to use the SunOS-4.1 version of netscape, set the NS_USE_SUNOS variable in /etc/mk.conf. </p> <h4 class="title"> <a name="sunos-netscape-socket"></a>Under SunOS emulation, Netscape fails with `Error: Can't open display: :0.0' (<a href="#emulation">top</a>) </h4> <p> Solaris Netscape (at least, version 4.51 attempts to use a pipe rather than a Unix domain socket to connect to the X server. Put <span class="bold"><strong>DISPLAY=unix:0.0</strong></span> into netscape's environment before starting it and it will work ok. The easiest way to do this, as well as the other variables you need to set up for it, is to have a shell script that does this before executing netscape: </p> <p> </p> <table class="programlisting"><tr><td><pre>#!/bin/sh export XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB export MOZILLA_HOME=/usr/local/netscape.svr4 export XNLSPATH=$MOZILLA_HOME/nls exec $MOZILLA_HOME/netscape $* </pre></td></tr></table> <p> </p> <hr> <h3 class="title">Other sources of information</h3> <h4 class="title"> <a name="sun-system-handbook"></a>Sun System Handbook (<a href="#other-sources">top</a>) </h4> <a href="http://sunsolve.sun.com/handbook_pub/" target="_top">Sun System Handbook</a> - Sun's online system docs <h4 class="title"> <a name="memory-modules"></a>Memory Modules (<a href="#other-sources">top</a>) </h4> <a href="http://sunsolve.sun.com/handbook_pub/Devices/Memory/MEM_Modules.html" target="_top">Memory Modules</a> - memory module compatability <h4 class="title"> <a name="SunHelp"></a>SunHELP (<a href="#other-sources">top</a>) </h4> <a href="http://www.sunhelp.org/" target="_top">SunHELP</a> - much sun related information <h4 class="title"> <a name="sun-hardware-reference"></a>Sun Hardware Reference FAQ (<a href="#other-sources">top</a>) </h4> <a href="http://www.sunhelp.org/faq/sunref1.html" target="_top">Sun Hardware Reference FAQ</a> - overview of Sun hardware over the years <h4 class="title"> <a name="openboot-collection"></a>OpenBoot Collection (<a href="#other-sources">top</a>) </h4> <a href="http://docs.sun.com/?p=/coll/216.2" target="_top">OpenBoot Collection</a> reference on PROM commands and variables <h4 class="title"> <a name="sun-hostid-faq"></a>Sun NVRAM/Hostid FAQ (<a href="#other-sources">top</a>) </h4> <a 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 <h4 class="title"> <a name="sun-erial-port"></a>Sun Serial Port & Cable Pinouts (<a href="#other-sources">top</a>) </h4> <a href="http://www.stokely.com/unix.serial.port.resources/A-B-Ycablepinout.html" target="_top"> Sun Serial Port & Cable Pinouts</a> - lists serial port pinouts for almost all models <h4 class="title"> <a name="frame-buffer-faq"></a>Frame Buffer FAQ (<a href="#other-sources">top</a>) </h4> <a href="http://www.sunhelp.org/faq/FrameBuffer.html" target="_top">Frame Buffer FAQ</a> by David Tong <h4 class="title"> <a name="sunchack-data"></a>The SunShack Data Archive (<a href="#other-sources">top</a>) </h4> <a href="http://lios.apana.org.au/~cdewick/data/" target="_top">The SunShack Data Archive</a> collected by Craig Dewick (includes BootROM upgrades and the Sun Field Engineer Handbook) <h4 class="title"> <a name="sparc-cpu-resources"></a><a href="http://www.users.qwest.net/~eballen1/sparc.tech.links.html" target="_top">Technical SPARC CPU resources</a> (<a href="#other-sources">top</a>) </h4> <h4 class="title"> <a name="mixing-mbus"></a><a href="http://mbus.sunhelp.org/misc/genconf.htm" target="_top">Information about mixing MBus modules</a> (<a href="#other-sources">top</a>) </h4> <hr> <h3 class="title">Other sources of information from NetBSD.org</h3> <h4 class="title"> <a name="install-notes"></a>NetBSD 2.0 install notes (<a href="#other-onsite">top</a>) </h4> <a href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-2.0/sparc/INSTALL.html" target="_top"> NetBSD 2.0 install notes</a> - supported hardware and how to install. <h4 class="title"> <a name="port-sparc-ml"></a>port-sparc mail list (<a href="#other-onsite">top</a>) </h4> <a href="../../MailingLists/#port-sparc" target="_top"> port-sparc mail list</a> - if you have any additional questions please subscribe. <h4 class="title"> <a name="diskless-howto"></a><a href="../../Documentation/network/netboot/" target="_top">Diskless NetBSD HOW-TO</a>. (<a href="#other-onsite">top</a>) </h4> <h4 class="title"> <a name="serial-primer"></a><a href="../../Documentation/Hardware/Misc/serial.html" target="_top">NetBSD Serial Port Primer</a> (<a href="#other-onsite">top</a>) </h4> <h4 class="title"> <a name="general-docs"></a>General NetBSD Documentation (<a href="#other-onsite">top</a>) </h4> <a href="../../Documentation/" target="_top">General NetBSD Documentation</a> - for questions not specific to NetBSD/sparc. <div class="navfoot"> <hr> <table border="0" summary="Footer navigation"><tr> <td class="foothome"><span class="foothome"><a href="../../."><img src="/images/NetBSD-flag.png" alt="" border="0" width="90" height="90"></a></span></td> <td class="foothome"> <span class="foothome"><a href="../../.">Home page</a></span><br> </td> </tr></table> <hr> </div> <p></p> <span class="footfeed"><a href="http://www.NetBSD.org/cgi-bin/feedback.cgi">(contact us)</a></span> � <span class="foottag">Generated from <em>%NetBSD: faq.xml,v 1.2 2005/01/17 05:40:18 jschauma Exp %</em></span><br><span class="footcopy"><a href="/Misc/disclaimer.html"><span class="copyright">Copyright � 1994-2004 The NetBSD Foundation, Inc. </span>ALL RIGHTS RESERVED.</a></span> </div></body> </html>