[Previous] [Contents] [Next]

disktrap

Autodetect disk controller and start appropriate driver (QNX)

Syntax:

Print command line necessary to start driver:

    disktrap [options] [query]

Start driver:

    disktrap [options] start

Options:

-v
Verbose output to help debugging failed detection.
-x type
Exclude scan for this type of card. Cards are scanned for in the order the valid types are listed, below:

ps2, ncr, aha2, aha7, amd, aha4, ide

Description:

The disktrap utility scans the machine it is run on for disk controller hardware. Depending on the mode it is in (query or start), it will either report the correct driver to use for the hardware as a message to the standard output (query), or will start the appropriate driver (start).

The set of disk controllers disktrap can scan for may change as new controllers are supported by QNX drivers. Check the usage message for a definitive list (use disktrap). The set will include at least the following hardware types:


Note: You can run disktrap only when logged in as root.

For driver: Location:
Fsys.ps2scsi checks addresses 0x96, 0x100 0x101, then 0x94, 0x102
Fsys.ncr8scsi uses PCI BIOS
Fsys.aha2scsi checks addresses 0x140, 0x340
Fsys.aha4scsi checks addresses 0x130, 0x134, 0x230, 0x234, 0x330, 0x334
Fsys.aha7scsi checks PCI BIOS, then addresses 0x1c00, 0x2c00, 0x3c00, 0x4c00, 0x5c00, 0x6c00, 0x7c00, 0x8c00, 0x9c00, 0xac00, 0xbc00, 0xcc00, 0xdc00, 0xec00, 0xfc00
Fsys.ide checks addresses 0x1f0, 0x170
Fsys.ata checks addresses 0x1f0, 0x170
Fsys.amdscsi uses PCI BIOS

Files:

The standard input is unused.

Error messages and -v status messages are written to the standard error.

In start mode, the standard output is unused. In query mode, a message indicating the appropriate driver to run will be written to the standard output.

Exit status:

>0
Failed to detect card and/or start driver.
0
Successfully detected card/started driver.

See also:

Fsys, Fsys.*, inputtrap, mousetrap, nettrap, pcmciatrap, ramtrap


[Previous] [Contents] [Next]