Technical article 112022

Questions or Problems installing SCO OpenServer 5.0.6 on systems with IDE root hard drives.

OpenServer 5.0.6

Written · Last revised

Problem

I am installing SCO OpenServer 5.0.6 on a system where the root drive is on an IDE controller, and I have installation problems, or I have questions about Ultra DMA (UDMA) support and configuration.

Solution

A new wd driver is included with SCO OpenServer 5.0.6 that includes UDMA support.

Motherboard vendors are using several popular chips sets that provide Ultra DMA/PIO support, all of which have a specific PCI vendor and device ID. Each of these chips sets support either UDMA mode 0=16.7, 1=26, 2=33, 3=48, or 4=66.

By looking at the PCI info, the wd driver knows what the motherboard
can support. The wd driver also does an ATA drive identify command
to pull information about the state of the drive to see what UDMA
modes the drive supports and what UDMA mode the drive has been
programmed by the BIOS to use.  The driver looks for the highest
matching speed and checks to see if the drive has been set to this,
and if not, reprograms the drive.

With certain combinations of hard disk and motherboard, the installation might hang when using Ultra Direct Memory Access (UDMA) mode, although the standard Programmed I/O (PIO) mode will work correctly.

To avoid this problem, start the installation by typing this bootstring at the boot prompt:

defbootstr wd.udma=off
NOTES:    The wd(HW) manual page contains other UDMA bootstrings that can
          be used to manually set the UDMA mode or to query the hardware:

There are two bootstrings that can be used to change the default detection and setting of transfer modes for motherboards or controllers not recognized by the driver. The wd.udma bootstring has the following settings:

off              disables UDMA (forces PIO mode)
auto             if settings do not match
                 motherboard, tries to sense and
                 reprogram disk
0, 16, or 16.7   udma 16  MB/sec
1 or 26          udma 26  MB/sec
2 or 33          udma 33  MB/sec
3, 44, or 48     udma 44  MB/sec
4 or 66          udma 66  MB/sec

The wd.debug=udma bootstring displays the current DMA setting and values for motherboard and drives.

wd.debug=udma can be useful in verifying that the wd driver is making the best choice with respect to DMA. If the driver is not selecting the highest speed that both the motherboard and drive can support, you can manually set the speed with the wd.udma bootstring.

NOTES:
          Within some BIOS's, you can specify "Auto" for the IDE hard
          disk configured which OpenServer 5.0.6 will detect when it installs
          as it queries the BIOS.

You can also specify, on some BIOS's, to IDE Detect so that it appears to manually configure the hard disk within the BIOS. For example, it appears as

"User; 80GB; Cylinders 38309; Heads 16; Precomp 0; Landz 38309; Sector 255.

When OpenServer 5.0.6 boots from the CDROM or from the floppies when
installing it will run "hwconfig" to determine the detected
hardware.  This may reveal different values, for example:
W0: Cyl 9729; Heads 255; Sectors 63

Further into the installation the "Customise" option should display the correct amount of hard disk that OpenServer sees.

Should you pick the "Fdisk/Divvy" option then you can run:

1. Display hard disk parameters, 2. Modify hard disk parameters, ...

Should you manually set the hard disk parameters to the values defined in the BIOS it should still be possible to install.

It has been found though that should you abort the installation at
this stage then the MBR has been written to the disk and should you
reboot and try to install again you will see that now the hwconfig
reports the same values as the BIOS.  This implies that the values
are now being read from the hard disk and not the BIOS.

Unfortunately, this can caused a problem going into the menu selecting disk options with the error:

"Function DiAdjustDivisions: Cannot adjust divisions to fit in the usable space: Disk 0"

and the installation fails.  Pressing ALT-F3 you can run "fdisk" at
the prompt and you will see that the disk has a valid partition on
it.  It can only be reset by booting with a DOS disk and
running "fdisk /mbr".

This will put the disk back into it's original state so you will be able to install as some BIOS's no longer supply the low level format option.

See also

Manual page for wd(HW).
SCOhelp documentation -> Release Notes
SCOhelp documentation -> Late News

For use during install, look for "biosgeom" in boot(HW) and in:

http://localhost:457/HANDBOOK/overriding_BIOS.html
on an OSR5 system.
For a secondary hard disk, post-install, you can run `mkdev hd` on it
or use dparam(HW).

http://osr507doc.xinuos.com/en/HANDBOOK/overriding_BIOS.html http://osr507doc.xinuos.com/en/cgi-bin/man/man?boot+HW http://osr507doc.xinuos.com/en/cgi-bin/man/man?mkdev http://osr507doc.xinuos.com/en/cgi-bin/man/man?dparam http://osr507doc.xinuos.com/en/cgi-bin/man/man?hd+HW http://osr507doc.xinuos.com/en/HANDBOOK/hard_disk_installing.html http://osr507doc.xinuos.com/en/HANDBOOK/hdi_dkinit.html http://osr507doc.xinuos.com/en/HANDBOOK/hard_disk_adding_secondary.html http://osr507doc.xinuos.com/en/HANDBOOK/replacing_disk.html

From the Xinuos technical article database, record 112022. Reproduced with permission. The original is at www.sco.com/ta/112022, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.