- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ad160 driver
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2001 04:00 PM
тАО04-02-2001 04:00 PM
ad160 driver
As a last resort I just hit return to the boot prompt so using the ad160 on the SCO 5.06 cd and the installation appears to be progressing normally. I think some message was displayed in between the Sco install screens.
Has anyone else tried this?
The disc drive cage and Tape is connected to port 1 only of the onboard 64 bit u3 controller. Its IRQ is 11. Port 2 is terminated but unused also with IRQ 11.(Disabling port 2 causes the install to panic)
Comments would be appreciated.
Clive Rhodes
Jobmaster Plc (UK)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2001 04:00 PM
тАО04-02-2001 04:00 PM
Re: ad160 driver
sure the controller/channel with the drives on it is controller order one.
Sometimes you need to run the Smart Start system erase to reset the works, then follow the assisted install. The erase/assisted install MAY reset the controller order.
We normally set the tape drive on a different controller from the hard drives.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2001 04:00 PM
тАО04-04-2001 04:00 PM
Re: ad160 driver
Clive Rhodes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2001 04:00 PM
тАО04-06-2001 04:00 PM
Re: ad160 driver
seems to be a variable I have not sorted out, because I was able to complete
an install a few weks ago. The assisted install fails ( I think ) because 5.38a
is on the 4.90 CD, which is autoloaded at the end of a SCO install. This causes
the first reboot after the install to hang at " H iinit ", which I think is
a first step in accessing the hard drive. The 5.38a BTLD causes a hang at the
same point that you observed. Only stepping through a manual installation, then
loading EFS 5.38b seemed to work. Is there various releases of SS 4.90 ?
Your PCI interrupt table differs from what I expect. My controllers share the
interrupts, as follows
FPU 13, serial 4 & 3, parallel 7, floppy 6, IDE 14, network 15, kbmouse 12,
BUT both ad160 controllers are on 11. Should leave 10 & 5 for the 8 port.
Update this when you can.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2001 04:00 PM
тАО04-08-2001 04:00 PM
Re: ad160 driver
As for IRQs suggested it all looks ok but I have in addition an IRQ taken up by the Compaq Wellness Driver - installed when the EFS is used to set up the network card and in the F9 setup the ATI Rage Controller uses yet another IRQ although not used by the SCO system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2001 04:00 PM
тАО04-08-2001 04:00 PM
Re: ad160 driver
defbootstr link="ad160" hd=Sdsk Srom=wd(0,0,0) scsi.noscan
is entered. Used this after reading on www.sco.com Technical Article TA111523 about OS 5.05 OR 5.06 hanging if installing on top of 5.05 or 5.06. Not the same conditions but hopefully this appears to work.
Clive Rhodes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2001 04:00 PM
тАО04-11-2001 04:00 PM
Re: ad160 driver
installation of 5.0.6 over 5.0.6 . Thanks. I can get the manual install to
work, and run 5.0.6 sucessfully. When I install EFS5.38b ( from single user
mode), relink and reboot, the reboot hangs at " H iinit ". Going back to the
old kernel, removing EFS5.38b fixes the problem. Can you run EFS5.38b ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2001 04:00 PM
тАО04-16-2001 04:00 PM
Re: ad160 driver
13 fpu
4 serial
3 serial
6 floppy
12 kbmouse
5 cpqw compaq wellness
10 compaq onboard nic
11 ultra 3 port 1
11 ultra 3 port 2
14 ide controller
15 specialix serial card
USB is disabled in f9, ATI rage controller allows disable but keeps coming back!. Not sure about your problem except that its related to what efs 5.38b does - set up the nic and compaq wellness driver - IRQ 's?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2001 04:00 PM
тАО04-30-2001 04:00 PM
Re: ad160 driver
which has EFS 5.40, seems to work. I am having a problem with some of the
ML530's in the field, they seem to ASR after 13-14 days if they are heavily
loaded. Removing the CMA seems to correct the problem, but then you lose
all that functionality. I am retesting the new CMA version to see what happens.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2001 04:00 PM
тАО07-25-2001 04:00 PM
Re: ad160 driver
Hope you still are in the loop. After more problems on a total of 5 ML350,
and a lot of effort from Canadian tech support, I have conformation that there
IS a problem with the Adaptec chip set and the AD160 driver. No solution as
of yet, but some machine will hang at H iinit at boot time.
scoace