Using the Device Configuration Utility (DCU)
The Device Configuration Utility (DCU) lists the hardware controllers
and device drivers configured on your system and allows you to assign
parameter values (IRQ, memory address range, DMA channel and so on) for
the device drivers.
Invoking the DCU
You can invoke the DCU using any one of the following methods:
After invoking the DCU, the DCU main menu is displayed.
During initial system installation,
you are prompted as to whether you want to enter the DCU.
Choose SCOadmin from the SCO menu (above
the SCO logo) on the CDE desktop,
then select Hardware, then select Device
Or you can simply enter scoadmin dev on the command-line.
From the system console or a terminal window,
type su to become root,
and execute the /sbin/dcu command.
Navigating in the DCU
A mouse cannot be used to navigate in the DCU.
To navigate in the DCU, you must use named keys and function keys.
Named keys are the keys that do something other than print an
alphanumeric or special character. Named keys include
<Enter>, <Tab>, <PgUp>, and <PgDn>.
Function keys are those labeled <F1> through <F10>.
Every DCU screen displays a bar at the bottom which lists the
keyboard navigation choices in effect for that screen.
It also displays field-specific information when appropriate.
The following key definitions apply for all DCU screens:
The following key definitions apply when you are in the online help system.
Displays help for the current screen.
Displays valid choices for a field.
Moves the cursor to the next field on a screen.
Moves the cursor up/down/left/right within a field.
Moves to the previous/next page in a multi-page screen.
Enters the selection and continues (on screens with multiple fields, <Enter> moves the cursor to the next field).
On screens with multiple fields, applies selections and continues (on other screens, <F10> is the same as <Enter>).
Gets a menu of related help screens.
<PgUp> or Up Arrow
Goes to previous page of a help screen.
<PgDn> or Down Arrow
Goes to the next page of a help screen.
Exits help system and returns to the current screen.
What to do if your named keys do not work
If you are running the DCU on an ASCII terminal or an
X-terminal, the named keys may not work if they have been remapped.
In these cases, you can use a sequence of alternate
keystrokes that, when typed, are equivalent to pressing that named key.
For example, you can access online help while using
the DCU by pressing <F1>.
If the function keys on your terminal do not work, you can
This sequence is typed by holding down <Ctrl>
while pressing <F>, then pressing <1>.
The sequence of alternate keystrokes for <F10>
Viewing or changing device driver configuration
The system automatically determines the hardware settings for
EISA, MCA and PCI hardware controllers,
but ISA hardware controllers cannot be detected automatically.
You can use the DCU to specify hardware settings that are not detected
We suggest that you run the DCU whenever you add new hardware
controllers to check whether the device drivers are properly configured.
For a current list of device drivers and supported hardware see
``Accessing the SCO Compatible Hardware Web Pages''.
Use the following table to decide which option
to select from the DCU Main Menu:
You want to view the hardware controllers currently configured
on your system and/or change their device driver parameter settings
(IRQ, memory address range, I/O address
range, and DMA channel) for existing devices.
You might also want to delete or disable a controller.
Select Hardware Device Configuration.
Follow the instructions in
``Viewing or updating hardware device configuration''.
You want to view the device drivers on your system and/or add
a new instance of an ISA controller to your current configuration.
Select Software Device Drivers.
Follow the instructions in
``Viewing and activating software device drivers''.
Decide whether to apply your device driver configuration changes.
Configuration changes do not take effect until they are applied.
To apply the configuration changes, select
Apply Changes & Exit DCU from the DCU main menu.
The configuration of your system is then updated to reflect
the changes you specified.
To end the DCU session without
updating your system configuration, select
Exit DCU and Cancel Changes from the DCU main menu.
If you applied new device driver configuration
updates you may be required to reload the driver
or reboot the system before the changes will take effect.
Drivers that are not autoconfigurable, that cannot be unloaded,
or that are static, require that you
reboot for the changes to take effect.
Autoconfigurable drivers must be reloaded for the changes to take effect.
Viewing or updating hardware device configuration
These following procedures are used to view your
current hardware configurations and change them if necessary.
Select Hardware Device Configuration from the DCU main menu.
The resulting screen displays a row for each device configured on your system,
along with its software device driver parameter settings.
If there is more than one page of information, you can press the
<PgDn>and <PgUp>keys to navigate between pages.
A dash (-) character in a field indicates that the entry does not require a
value because it is not required by the device driver.
This screen contains eight fields:
The first field indicates whether the hardware controller
should be configured on your system. Y (Yes)
indicates that the controller should be configured; N
(No) indicates that the controller should not be configured.
The second field, Device Name, provides the name of the device.
If a driver is assigned to an entry, the entry will be either
the device name such as
COM Port, or a driver name
asyc, the driver
for the COM port.
If the device name is
UNKNOWN on an EISA, MCA or PCI system,
this is an entry from NVRAM (Non-Volatile Random Access Memory) indicating
that the DCU cannot assign a driver name.
For example, if you have installed a networking board, but have not
installed the corresponding software for the board,
it will be listed as
If the device name is
unused, this indicates that an
ISA driver is disabled, but the device parameters are retained.
The third field, the IRQ field, lists the interrupt request vector
(IRQ) value for the hardware controller.
The fourth and fifth fields, the IOStart and IOEnd fields,
list the start and end addresses for the hardware controller's I/O
The sixth and seventh fields, the MemStart and MemEnd fields,
list the start and end addresses for the hardware controller's
memory address range.
For an HBA controller, these are the start and end addresses of
the BIOS for the controller.
The eighth field, the DMA field, lists the DMA channel for the controller
if it has one.
To view additional information about any of the entries,
use the arrow keys to move the cursor to the row
with the hardware controller data, and press <F6>.
The name of the controller is repeated along with its board ID,
the device driver for the controller, the hardware bus type,
and (if used by the device driver) the valid values
for the Interrupt Priority Level (IPL), interrupt type (ITYPE),
interrupt request vector (IRQ), I/O address range,
memory address range, DMA channels,
bind CPU and Unit. See the
manual page for more information.
Press <Enter> to return to the "Hardware Device Configuration" screen.
Steps 2 through 5 can be performed in any order and as often as desired.
Change a device driver parameter for
a device according to the following table:
Note that some fields are read only.
The cursor cannot be placed in a read-only field.
The parameter is listed on the "Hardware Device Configuration" screen.
Move the cursor to the field for the parameter you want to change.
Change the parameter by typing over the
existing entry, or press <F2> and follow the instructions for
using a Choices menu that follows this table.
You want to change the Bind CPU, unit number, IPL, or ITYPE
parameter values, or any optional device-specific parameters.
Press <F7> to display the "Advanced Parameter
Move the cursor to the field for the parameter
you want to change.
Change the parameter by typing over the existing entry,
or press <F2> and follow the instructions for using
a Choices menu that follows this table.
You should not change entries for devices like the keyboard.
Doing so may impair the operation of your system.
The following list explains how to use the Choices menu:
Pressing <F2> allows you to make
a choice from the Choices menu.
To keep the current value in the parameter field, be sure the
cursor is positioned on that value, and press <Enter>.
If there are only two valid choices, the current value is replaced
in the field by the alternate choice when you press <F2>.
To toggle back to the original value, press <F2> again.
If there are more than two valid choices, a menu displays all choices.
Move the cursor to your selection and press <Enter>.
If a list of choices is not provided, the field will not change
and a message appears at the bottom of the screen.
Correct any hardware parameter conflicts.
If multiple devices have the same IRQ or DMA values, overlapping
I/O address ranges, or overlapping memory address ranges,
the system may not boot or might be unable to access some hardware.
To prevent this from happening, active devices must have unique
IRQ and DMA values, as well as I/O and memory address ranges
that do not overlap.
(Active devices are all the
controllers listed on the "Hardware Device Configuration" screen
whose first field does not contain the value
(No) and whose second field does not contain the value
The only exceptions are controllers that support shared IRQ values.
When multiple controllers share the same IRQ values, the software
device drivers for these controllers must operate at the same IPL.
For example, two DPT controllers, supported by the same device driver,
will operate at the same IPL.
In addition, software device drivers of the same
class such as HBA drivers will operate at the same IPL.
If you have a PS/2 mouse and you install a controller whose IRQ
conflicts with the mouse, you must change the IRQ for the new controller.
The PS/2 mouse requires IRQ 12.
To temporarily disable a controller (that is, to keep its data in
the system resource database but not
configure the controller for use by the system),
change the Device Name field for this device to
unused by following the instructions in Step 3.
This step is useful if you plan to add the controller to your system
again later, because you will not have to enter its hardware
configuration data again.
It is also useful if you want to temporarily disable all peripherals
attached to a controller.
This is only applicable for non-ISA controllers if the controller
remains physically installed on your system; parameters are automatically
deleted when non-ISA controllers are removed from the system.
To delete an ISA controller from the system resource database,
set the first field of the entry for the hardware device to
Press <F4> to verify the device. (This step is optional,
If the device driver has a verification routine, pressing <F4>
will run the routine and report whether the
parameters you specified are correct.
To return to the DCU main menu, press <F10>.
Select Apply Changes & Exit DCU to save your changes.
Viewing and activating software device drivers
The following procedures allow you to view or activate the
device drivers currently installed on your system.
From the DCU main menu, select
Software Device Drivers.
This menu classifies drivers into several categories:
Network Interface Cards, Host Bus Adapters, Communication Cards,
Video Cards, Sound Boards, and Miscellaneous.
Device drivers created for systems before SCO UnixWare 2.0
or device drivers that do not take full advantage of the SCO UnixWare 2.0 device driver
configuration capabilities, are listed under the Miscellaneous category.
Select a device driver category, or select
All Software Device Drivers to display all the device drivers.
The "Software Device Drivers" screen for the selected class
of device drivers is displayed.
This screen contains three fields:
The ``Active/Inactive'' field indicates whether the device driver is active
on the system.
If there is an asterisk (*) in this field, the driver is available
for use assuming the hardware it supports is installed and enabled.
If there is no asterisk then the device driver is inactive
and supports no devices.
The ``Driver'' field lists the device driver name.
The ``Names of Supported Devices'' field lists the hardware
controllers the device driver supports (if available).
If you are adding a new device after the system has been installed,
the device driver you need might not be listed.
You can add the device driver from the installation media
or, if the device manufacturer has provided a driver, follow their
instructions for adding it.
Many device drivers support multiple controllers.
The "Software Device Drivers" screen lists the controllers supported
by each device driver.
If a device driver is inactive,
the system cannot access any of the controllers
that the device driver supports.
Steps 2 through 4 can be performed in any order and as often as desired.
To obtain additional information about any of the device drivers, press
The device name is repeated along with the driver name;
whether or not it is configured; the unit number;
and valid values for the IPL, ITYPE, IRQ, I/O address range, memory
address range, DMA channel, and Bind CPU.
Press <Enter> to return to the "Software Device Drivers" screen.
To activate a device driver, move the cursor to the device
driver status field for the device driver and press the
<SpaceBar> so that an asterisk appears in the first field.
Do not deactivate a device driver from this screen.
To deactivate a single controller,
use the "Hardware Device Configuration" screen.
``Viewing or updating hardware device configuration''
for further information.)
If you want to add a new controller,
the device driver that supports this controller must be active.
If you are installing
the system, and if there are device drivers on your
boot media that you are sure will not be needed on your system,
you can instruct the installation software not to install
these device drivers.
To do so, remove the asterisk next to each of these device drivers.
To add a controller for a device driver:
To cancel this action at any time before the
<F10> key (apply the changes) is entered,
Move the cursor to the field containing the device driver status.
The "New Hardware Configuration" screen is displayed.
The default values may also be displayed.
This screen contains the fields for
An optional parameter that identifies a subdevice attached to
a particular controller.
In most cases, this value should be set to 0.
The interrupt priority level.
Set this to 0 if interrupt priority handling is disabled for this device,
or specify a value from 1 (lowest priority) to 7 (highest priority).
The interrupt vector sharing type.
Set to 0 if interrupt sharing is not supported or the device
does not use interrupts; 1 if the device uses an
IRQ that cannot be shared; 2 if the device uses
an IRQ that can only be shared with another
instance of the same module; 3 if the IRQ can
be shared with any module; or 4 if the device
uses an EISA level-sensitive IRQ that can be
shared with any module.
The interrupt vector used by this device.
Be sure the IRQ you select matches the setup
(software or jumpers) of your hardware.
I/O address range (I/0 start address and I/O end address):
The lowest and highest I/O addresses through which the device communicates.
These are hexadecimal values from 0 through FFFF.
Memory address range (Memory start address and Memory end address):
The lowest and highest memory addresses through which the
These are hexadecimal values from 10000 through FFFFFFFF.
The direct memory access channel for the device.
If the device has no DMA channel, set it to -1.
The CPU to which this device is bound.
If the device is not CPU-specific, leave this value blank.
Enter the correct configuration parameters for the new controller.
The fields will be initialized with default values.
Optionally, you can press <F4> to verify that
correct values are entered in each field before you apply the changes.
If an error is reported, repeat from Step 5a to update the parameter settings.
If the verify succeeds or the message
Driver does not support the
verify function appears, press<Enter> to continue.
To apply the changes and return to the
"Software Device Drivers" screen, press
<F10>, then press <Enter>.
If you do not want to apply the changes, press
<F8> to cancel.
If a configuration error is reported, repeat Step 5c to
correct the parameter settings.
To see if there are any device-specific parameters,
apply the changes you have made, then navigate back to
the main menu and select "Hardware Device Configuration."
Position the cursor on the line for the new entry.
Press <F7> to display the "Advanced Parameter Selection" screen.
To view or update the device driver information for another category,
go back to Step 1.
If you defined any new controllers, view the
"Hardware Device Configuration" screen and verify that
the new hardware parameters do not conflict with the existing hardware
``Viewing or updating hardware device configuration''.
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 - 02 June 2005