This appendix explains messages displayed by your Serial Parallel Controller
device driver and configuration script. These messages inform you about the
status of the installation of your device driver. They also help you
troubleshoot problems with your device driver and card.
The term board is used instead of card in this appendix.
There are three types of messages:
-
Advisory messages indicate that the device driver or configuration script has
detected a condition which you might find of interest. They are provided
for your information, and do not require any response from you.
-
Error messages indicate that a condition has been detected which disrupts
the normal operation of your device driver, board, or both. You might lose
data as a result of these messages. They do require a response from you.
-
Fatal messages indicate that the device driver was not configured into your
system correctly and, consequently, the Serial Parallel Controller card is
inaccessible to your system. They also require a response from you.
Messages are organized into one of the following seven groups. Each group
relates to the installation, configuration, or operation of your device driver.
Messages in each group appear in order of severity, from Advisory to Fatal.
-
stc_config: invalid number of boards in configuration file, configuring 3
-
Advisory. The /dev/stc.AUTOLOAD file has a number outside the range of
1 to 3. The maximum number of boards which the configuration script can
support (which is 3) is configured. Make sure the file does not contain any
bogus characters inadvertently written to the file.
-
stc_config: invalid number of boards; between 1 and 3 can be configured
-
Advisory. The maximum number of boards which the configuration script can
support (which is 3) is configured. You cannot configure more than 3 boards
into your system.
-
stc_config: unloaded SPC/S driver, id number
-
Advisory. The device driver, which has an id number, is successfully unloaded
(removed) from your system. You cannot operate any peripheral devices
controlled by Serial Parallel Controller until the Serial Parallel Controller
device driver is installed and configured into your system again.
-
stc_config: SPC/S driver successfully loaded from file
-
Advisory. The device driver was successfully loaded into your system from the
specified file.
-
stc_config: SPC/S driver files created in /dev directory
-
Advisory. The files for your device driver have been created in the /dev
directory.
-
stc_config: removing device nodes for all SPC/S boards
-
Advisory. The device nodes for your device driver are being removed from the
/dev directory. This message appears as a result of booting your system or
using the -c command line option with the configuration script.
-
stc_config: making device nodes for number SPC/S boards
-
Advisory. The configuration script is creating device nodes for your device
driver in the /dev directory for the specified number of boards installed in
your system.
-
stc_config: SPC/S driver will be automatically loaded on the next bootup
-
Advisory. The device driver will be loaded into the system the next time you
boot your system. This message is the result of using the -s (status) command
line option with the configuration script.
-
stc_config: added call to /etc/loadable in /etc/rc.local
-
Advisory. The configuration script added a call to the script that loads your
device driver in the /etc/rc.local file.
-
stc_config: created /etc/loadable where none existed before
-
Advisory. The configuration script created the /etc/loadable file. This file
contains the commands to load the device driver into the system the next time
you boot your system.
-
stc_config: added SPC/S driver autoload commands to /etc/loadable
-
Advisory. The configuration script added the commands to load your device
driver into your system to the /etc/loadable file.
-
stc_config: SPC/S driver configured to autoload on next bootup
-
Advisory. The device driver will be loaded into the system the next time you
boot your system. This message is the result of following the instructions for
running the installation script explained in this book.
-
stc_config: automatic loading of SPC/S device driver on bootup is disabled
-
Advisory. The device driver will not be loaded into the system the next time
you boot your system. This message appears as a result of using the -c (clean)
or -n (disable autoload) command line options with the configuration script.
-
stc_config: can't execute defaults setup program /usr/etc/stc/stc_defs
-
Error. The configuration script could not run the program that applies the
modem control and printer settings in the /usr/etc/stc/stc_defaults
file to the serial and parallel ports. Make sure that these files are installed
correctly. This message also appears if you have installed your software in a
directory other than the /usr directory.
-
stc_config: must have root privileges to run this command
-
Fatal. You must be root or superuser to execute one or more of the command
line options you specified.
-
stc_config: can't find driver object file in: stc.o/dev/stc.o
-
Fatal. The configuration script looks for the device driver in several places.
If it cannot locate the device driver on your system, this message is displayed.
Make sure that the device driver is installed correctly on your system. You
must run the stc_config command from either the /dev directory or the
directory where the stc.o file is located on your system.
-
stc_config: invalid device major number specified
-
Fatal. You cannot specify a major number outside the range of 1 to 255 in the
-M# command line option.
-
stc_config: error unloading SPC/S driver - modunload error number number
-
Fatal. The device driver cannot be removed from your system. See the
modload Man Page for information about the error number. Make sure your
board does not have any open devices. Check your console for any indication
of which device(s) might be open.
-
stc_config: error loading SPC/S driver - modload error number number
-
Fatal. The device driver cannot be configured into your system. See the
modunload Man Page for information about the error number. Make sure that
at least one Serial Parallel Controller board is installed in your system. Also
make sure the vd (virtual device) driver is configured into your system kernel.
-
stc_config: driver must be unloaded before devices can be removed, use -u
-
Fatal. You attempted to remove device nodes from the /dev directory before
unloading your device driver. Unload (remove) your device driver using the
-u command line option. Then use the -r command line option to remove the
device nodes for your device driver from the /dev directory.
-
stc_config: driver must be loaded before devices can be made, use -l
-
Fatal. You attempted to create device nodes for your device driver in the /dev
directory before loading your device driver. Load your device driver using the
-l command line option. Then use the -m command line option to create
device nodes for your device driver in the /dev directory.
-
usage: stc_config [-c|-l|-b#|-u|-m|-M#|-r|-s|-p|-n|-a|-d]
-
Fatal. You attempted to use an incorrect command line option with the
configuration script. If no command line option is used with the stc_config
command, the device driver and configuration script are installed in the /dev
directory, device nodes are created in the /dev directory, and a call to the
configuration script is added to the /etc/loadable file. You can use the
following command line options with the stc_config command.
-c This option (clean) unloads your device driver, removes device nodes
from the /dev directory, and removes the device driver and
configuration script from the /dev directory.
-
-l This option (load) loads your device driver into your system.
-
-b# This option allows you to specify the number # of boards to
configure into your system.
-
-u This option removes (unloads) the device driver from your system.
-
-m This option creates device nodes for the device driver in the /dev
directory.
-
-M# This option allows you to specify the major number # of your device
driver. This is required if device nodes must be created for a driver
which is added to the system kernel as opposed to loaded into the
system.
-
-r This option removes device nodes for your device driver from the
/dev directory.
-
-R This option removes device nodes for your device driver from the
/dev directory, but does not check whether the device driver is
loaded.
-
-s This option (status) displays the status of device drivers which have
been loaded into the system.
-
-p This option (put) copies the configuration script and the executable
object file for the device driver to the /dev directory.
-
-n This option disables automatic loading of the device driver the next
time you boot your system.
-
-a This option enables automatic loading of the device driver the next
time you boot your system. This option also creates the
/etc/loadable file if not present, and adds a call to it to the
/etc/rc.local file.
-
-d This option checks for and runs the /usr/etc/stc/stc_defs set
up program to apply the default settings you specify in the
/usr/etc/stc/stc_defaults file.
-
-BOOT This option is used only if it is called from the /etc/loadable
directory while your system is booting.
-
stc_vdcmd: unit board number cd-180 firmware revision: revision
-
Advisory. This message displays the firmware revision level of the cd-180 chip
when the device driver is first loaded.
-
stc_vdcmd: unit board number line number is open
-
Advisory. The serial line on the enumerated board is open (in use by a process).
-
stc_vdcmd: unit board number ppc is open
-
Advisory. The parallel port on the enumerated board is open (in use by a
process).
-
stc_vdcmd: unit board number control line is open
-
Advisory. The control line on the enumerated board is open (in use by a
process).
-
stc_vdcmd: can't unload stc driver, some device(s) are still open
-
Error. The device driver could not be removed because one or more of the
devices controlled by the driver are open (in use by a process). Type the
/dev/stc_config -s (status) command to determine which device(s) are still
open.
-
stc_vdcmd: unknown command: command
-
Error. The virtual device handler of the device driver attempted to execute an
unrecognized command. Phone your Sun sales representative if you receive
this message.
-
stc_attach: unit board number weird oscillator revision (revision), assuming 10Mhz
-
Advisory. The FCode Programmable Read-Only Memory (PROM) on the board
returned an unexpected baud rate oscillator value. The device driver assumes
that a 10Mhz oscillator is installed. This message appears only if you changed
the FCode Programmable Read-Only Memory (PROM) on the Serial Parallel Controller
board.
-
stc_attach: can't allocate memory for unit structs
-
Fatal. The kmem_zalloc() function did not allocate memory for the data
structures used by the device driver. This message indicates a problem with
your system. Try to reinstall the device driver again.
-
stc_attach: unit board number board revision undeterminable!!
-
Fatal. The device driver could not obtain a hardware revision level from the
FCode Programmable Read-Only Memory (PROM) on the board. Make sure
your board is installed properly in its SBus slot. Otherwise, the problem might
be a faulty FCode PROM on your board or a faulty board. In both cases, you
must replace your board.
-
stc_attach: unit board number board revision revision not supported by driver
-
Fatal. The device driver does not support this revision of the board. You might
be using an older version of the Serial Parallel Controller board or the
Programmable Read-Only Memory (PROM) on the board might be faulty.
-
stc_attach: unit board number oscillator revision undeterminable!!
-
Fatal. The device driver could not obtain an oscillator revision level from the
FCode Programmable Read-Only Memory (PROM) on the board. Make sure
your board is installed properly in its SBus slot. Otherwise, the problem might
be a faulty FCode PROM on your board or a faulty board. In both cases, you
must replace your board.
-
stc_attach: error initializing stc board number
-
Fatal. An error occurred while initializing the board. A memory access could
have failed. This message indicates a faulty component on your Serial Parallel Controller
board. If this message appears frequently, replace your board.
-
stc_attach: unit board number bad number of interrupts: number
-
Fatal. An incorrect number of interrupts was read from the FCode
Programmable Read-Only Memory (PROM) on the board. Make sure your
board is installed properly in its SBus slot. Otherwise, the problem might be a
faulty FCode PROM on your board or a faulty board. In both cases, you must
replace your board.
-
stc_attach: unit board number bad number of register sets: number
-
Fatal. An incorrect number of register sets was read from the FCode
Programmable Read-Only Memory (PROM) on the board. Make sure your
board is installed properly in its SBus slot. Otherwise, the problem might be a
faulty FCode PROM on your board or a faulty board. In both cases, you must
replace your board.
-
stc_init: unit board number GIVR was not 0x0ff, was: hexadecimal number
-
Fatal. The 8-channel UART of the cd-180 chip could not initialize, or a
memory fault occurred in attempting to access the chip. If this message
appears frequently, replace your board.
-
cd180_init: unit board number GIVR was not 0x0ff, was: hexadecimal number
-
Fatal. The 8-channel UART of the cd-180 chip could not initialize, or a memory
fault occurred in attempting to access the chip. If this message appears
frequently, replace your board.
-
stc_modem: unit board number line number interesting modem control: MCR: hex num, MSVR: hex num
-
Advisory. The cd-180 chip posted a modem control line change interrupt to the
device driver, but the driver did not detect a change since its last scan. If this
problem occurs frequently, your data cables are either too long or picking up
noise. Hex num stands for hexadecimal number.
-
SET_CCR: CCR *timeout*
-
Error. The CCR register of the cd-180 chip did not return a non-zero value
within the timeout period after receiving a command. This message indicates
a faulty cd-180 chip or board.
-
PUTSILO: unit board number line number soft silo overflow
-
Error. The internal receive data silo of the device driver overflowed for the
enunciated line, because the system has not yet written the data in the silo. All
data in the silo is flushed as a result of this condition. Make sure you are using
the correct flow control.
-
stc_rcvex: unit board number line number receiver overrun, char: hexadecimal character
-
Error. The device driver could not service the cd-180 receive data interrupt
before the receive data FIFO (queue) of the chip filled up. You might wish to
consider purchasing a faster SBus-based SPARC desktop system.
-
stc_drainsilo: unit board number line number can't allocate streams buffer
-
Error. The device driver could not obtain a STREAMS message buffer from the
bufcall() function. All data in the receive data silo of the device driver is
flushed as a result of this condition.
-
stc_drainsilo: unit board number line number punting put retries
-
Error. The device driver could not send data down the stream to the
application because the path was blocked. All data in the receive data silo of
the device driver is flushed as a result of this condition.
-
stc_restart: unit board number line number BREAK BIT off (*ERROR*)
-
Advisory. The BREAK control bit for the enumerated line was set instead of
clear. Your cd-180 chip might be faulty, or your device driver might be faulty.
-
stc_ioctl: unit board number line number can't allocate streams buffer for ioctl
-
Error. The device driver could not obtain a STREAMS message buffer from the
bufcall() function for the requested ioctl. The ioctl will not execute as a result
of this condition.
-
stc_ioctl: unit board number line number can't allocate STC_DCONTROL block
-
Error. The device driver could not allocate a data block from the allocb()
function for the STC_DCONTROL return value. The ioctl will not execute as a
result of this condition.
-
stc_ioctl: unit board number line number can't allocate STC_GDEFAULTS block
-
Error. The device driver could not allocate a data block from the allocb()
function for the STC_GDEFAULTS return value. The ioctl will not execute as a
result of this condition.
-
stc_ioctl: unit board number line number can't allocate STC_GPPC block
-
Error. The device driver could not allocate a data block from the allocb()
function for the STC_GPPC return value. The ioctl will not execute as a result
of this condition.
-
stc_ioctl: unit board number line number can't allocate TIOCMGET block
-
Error. The device driver could not allocate a data block from the allocb()
function for the TIOCMGET return value. The ioctl will not execute as a result
of this condition.
-
ppc_stat: unit board number PAPER OUT
-
Advisory. The peripheral device connected to the parallel port on your
enumerated board is out of paper. The PAPER OUT line was asserted as a
result.
-
ppc_stat: unit board number PAPER OUT condition cleared
-
Advisory. The peripheral device connected to the parallel port on your
enumerated board has cleared the PAPER OUT condition. The PAPER OUT
line was deasserted as a result.
-
ppc_stat: unit board number OFFLINE
-
Advisory. The peripheral device connected to the parallel port on your
enumerated board is off-line. The SLCT line was deasserted as a result.
-
ppc_stat: unit board number OFFLINE condition cleared
-
Advisory. The peripheral device connected to the parallel port on your
enumerated board has cleared the OFFLINE condition. The SLCT line was
asserted as a result.
-
ppc_stat: unit board number ERROR
-
Advisory. The peripheral device connected to the parallel port on your
enumerated board has detected some error. The ERROR line was asserted as a
result.
-
ppc_stat: unit board number ERROR condition cleared
-
Advisory. The peripheral device connected to the parallel port on your
enumerated board has cleared the ERROR condition. The ERROR line was
deasserted as a result.
-
ppc_xwait: unit board number interrupted sleep
-
Advisory. The device driver received a signal while waiting for the queued
output from the previous STREAMS module to be sent to the parallel port.
The device driver returns from the sleep() call prematurely as a result.
-
ppc_int: unit board number stray interrupt
-
Advisory. The parallel port controller (ppc) chip generated an unexpected
interrupt while the peripheral device was closed. If this problem occurs
frequently, your parallel cable might be picking up noise, causing the ppc to
generate an unwanted interrupt; or the ppc might have an internal problem.
-
ppc_acktimeout: unit board number ACK timeout
-
Error. The ACK line of the peripheral device connected to the parallel port on
your enumerated board did not assert itself within the configurable timeout.
Make sure your peripheral device is connected properly and is powered on.
-
ppc_acktimeout: unit board number BUSY timeout
-
Error. The BUSY line of the peripheral device connected to the parallel port on
your enumerated board did not deassert itself within the configurable timeout.
Make sure your peripheral device is connected properly and is powered on.
-
ppc_acktimeout: unit board number can't get pointer to read q
-
Error. The data structure for the parallel port controller (ppc) of the device
driver is faulty.
-
ppc_acktimeout: unit board number can't send M_ERROR message
-
Error. The device driver cannot send an M_ERROR STREAMS message to the
application.
-
ppc_signal: unit board number can't get pointer to read q
-
Error. The data structure for the parallel port controller (ppc) of the device
driver is faulty.
-
ppc_signal: unit board number can't send M_PCSIG (PP_SIGTYPE hexadecimal number) message
-
Error. The device driver cannot send an M_PCSIG STREAMS message to the
application (which could post a signal).
-
stc_wput: unit board number trying to M_STARTI on ppc or control device
-
Advisory. An M_STARTI STREAMS message was sent to the parallel port or
the board control device. This should occur only if an application sends this
message.
-
stc_wput: unit board number line number unknown message: hexadecimal number
-
Advisory. The device driver received an unknown STREAMS message from the
application. Check your application coding.
-
stc_start: unit board number line number unknown message: hexadecimal number
-
Advisory. The device driver received an unknown STREAMS message from the
application. Check your application coding.
