Sponsored Content
Operating Systems SCO SCO 5.0.7 driver for HP SmartArray P410i Controller on Proliant DL380 G7? Post 303037238 by jgt on Friday 26th of July 2019 02:07:01 PM
Old 07-26-2019
Go to the sco site xinuos.com and check the certified hardware list.


According to the hardware list, only the P400 controller is supported, and i am pretty sure that the P410 was never supported.

Last edited by jgt; 07-26-2019 at 05:55 PM..
This User Gave Thanks to jgt For This Post:
 

10 More Discussions You Might Find Interesting

1. SCO

ultra 320 scsi raid controller driver for sco 5.0.6

I am facing a problem to install sco 5.0.6 in Dell Power Edge SC1420 which raid controller is ultra 320 scsi raid controller . how/from where to download the ultra 320 scsi raid controller driver for sco 5.0.6. Plz help with any idea karzon (1 Reply)
Discussion started by: karzon
1 Replies

2. SCO

driver needed for hp smartarry p200i sas raid controller

recently we have purchased hp proliant ml350 g5 server and configured raid 5 with hp smartarray p200i sas controller.but i could not found any sas raid controller hp smartarry p200i driver for sco unix 5.0.7 :(.i searched on hp support site,but no use.any one can help. (3 Replies)
Discussion started by: prakrithi
3 Replies

3. UNIX for Dummies Questions & Answers

SCO Openserver 6.0 Insall on HP DL380 serverl

Trying to install Openserver 6.0 on this server which has an integrated Smart Array P400. Install halts with the message ....... "Incorrect Disk Partitioning .........................." I havent yet got to the "divvy" and disk partitioning section of the install section so I am... (2 Replies)
Discussion started by: farmacy
2 Replies

4. SCO

SCO 5.0.7 no root disk controller found error during install

I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd. I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies

5. SCO

Loading SCO 507 on HP ProLiant ML350 G6

This is my first load of SCO OpenServer v5.0.7 on a HP ProLiant ML350 G6. When it asks me to identify the source media it can't find it no matter how I respond. The SCO compatible page says it used the on board SATA DVD-ROM on Port 2 of the embedded SATA controller with "Legacy IDE emulation (as... (8 Replies)
Discussion started by: farmboy
8 Replies

6. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 Replies

7. Debian

HP ProLiant DL380 G4 w/ Debian... If your familiar with this machine please help.

Hello, I have a few questions about this server. It has two CPU's 3.20 ghz / 800 mhz / 1MB L2 5120 MB RAM 6 hard disks on HP Smart Array 6i controller (36.4 GB Ultra320 SCSI HD each) RAID set to RAID 5 (5 discs) with one spare (6th disk) USB, 2 Ethernet ports, 1 ILO port, 1 SCSI port ... (2 Replies)
Discussion started by: Marcus Aurelius
2 Replies

8. SCO

Getting error sco unix 507 from cdrom:no controller for device you chosen

Installing SCO UNIX 507 on Dell Poweredge T610. It has no floppy so I downloaded the BTLD onto CD from SCO site to load without floppy drive. BTLD loads ok. when i get to the Media to be used, no matter what option i chose i get the error: No controller for device you have chosen. During bootup you... (9 Replies)
Discussion started by: romanglad112
9 Replies

9. SCO

How to change raid controller driver ? (hardware change)

Hello I'm trying to virtualize an instance of Sco Unix 5.0.5 in VirtualBox (called VM-A) , but sco I have problems set to launch with the new raid controller . The physical machine has a raid controller adaptec (alad driver) but VirtualBox uses buslogic (blc driver) What ... (3 Replies)
Discussion started by: flako
3 Replies

10. SCO

SCO OS 6 Driver for LSIL SAS1064E Raid Controller

Hi all, A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password. Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore. I tried to boot with the CD Rom, then "Tools", then exit to... (7 Replies)
Discussion started by: thm2222
7 Replies
ddi_intr_get_supported_types(9F)										  ddi_intr_get_supported_types(9F)

NAME
ddi_intr_get_supported_types - return information on supported hardware interrupt types SYNOPSIS
#include <sys/types.h> #include <sys/conf.h> #include <sys/ddi.h> #include <sys/sunddi.h> int ddi_intr_get_supported_types(dev_info_t *dip, int *typesp); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI) dip Pointer to dev_info structure typesp Pointer to supported interrupt types The ddi_intr_get_supported_types() function retrieves the interrupt types supported by a particular hardware device and by the system soft- ware. Upon successful return, the supported types are returned as a bit mask in the integer pointed to by the typesp argument. See <sys/ddi_intr.h> for a list of interrupts that can be returned by a hardware device. For PCI devices that support MSI and/or MSI-X based hardware, this interface returns only the interrupt types that are supported by all the hardware in the path to the hardware device. An interrupt type is usable by the hardware device if it is returned by the ddi_intr_get_supported_types() function. The device driver can be programmed to use one of the returned interrupt types to receive hardware interrupts. The ddi_intr_get_supported_types() function returns: DDI_SUCCESS On success. DDI_EINVAL On encountering invalid input parameters. DDI_INTR_NOTFOUND Returned when the hardware device is found not to support any hardware interrupts. CONTEXT
The ddi_intr_get_supported_types() function can be called from user or kernel non-interrupt context. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ pci(4), attributes(5), pcmcia(7D), sysbus(4), ddi_intr_add_handler(9F), ddi_intr_alloc(9F), ddi_intr_enable(9F) The ddi_intr_get_supported_types() function can be called by the device driver even at any time if the driver has added an interrupt han- dler for a given interrupt type. Soft interrupts are always usable and are not returned by this interface. Any consumer of this interface should verify that the return value is not equal to DDI_SUCCESS. Incomplete checking for failure codes could result in inconsistent behavior among platforms. 07 Apr 2005 ddi_intr_get_supported_types(9F)

Featured Tech Videos

All times are GMT -4. The time now is 12:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy