<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ad160 driver in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512689#M5408</link>
    <description>Clive - I guess one of the "variables that I haven't sorted out" is the fresh &lt;BR /&gt;installation of 5.0.6 over 5.0.6 .  Thanks.  I can get the manual install to &lt;BR /&gt;work, and run 5.0.6 sucessfully. When I install EFS5.38b ( from single user &lt;BR /&gt;mode), relink and reboot, the reboot hangs at " H iinit ". Going back to the &lt;BR /&gt;old kernel, removing EFS5.38b fixes the problem.  Can you run EFS5.38b ?</description>
    <pubDate>Wed, 11 Apr 2001 23:00:00 GMT</pubDate>
    <dc:creator>Ayman Altounji</dc:creator>
    <dc:date>2001-04-11T23:00:00Z</dc:date>
    <item>
      <title>ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512683#M5402</link>
      <description>When installing 5.06 the system hangs after entering License number and key for sco - at the stage 'Checking system state and loading installation files'. There is an occasional led flash on all of the 4 15k 9.1 Gb drives (at the same time)  in the hot swap bay and on the sdt-10000 tape drive. The defbootstr is link="ad160" hd=Sdsk Srom=wd(0,0,0) with the ad160 driver from the Compaq efs V5.38. &lt;BR /&gt;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. &lt;BR /&gt;Has anyone else tried this? &lt;BR /&gt;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) &lt;BR /&gt;Comments would be appreciated. &lt;BR /&gt; &lt;BR /&gt;Clive Rhodes &lt;BR /&gt;Jobmaster Plc (UK)</description>
      <pubDate>Mon, 02 Apr 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512683#M5402</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-02T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512684#M5403</link>
      <description>This seems to be normal.  Check the controller boot order in the bios, make &lt;BR /&gt;sure the controller/channel with the drives on it is controller order one. &lt;BR /&gt;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. &lt;BR /&gt;We normally set the tape drive on a different controller from the hard drives.</description>
      <pubDate>Mon, 02 Apr 2001 23:00:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512684#M5403</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-02T23:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512685#M5404</link>
      <description>Solution! Thanks to scoace - the reason for discs and tape on the same controller is that I need an IRQ for - dare I say a 8port pci card and irq 15 is now used for the Compaq Management facility. BUT the solution to the hang problem is that I downloaded EFS 5.38 whereas 5.38b is the latest. A bit confused about the EFS dates. EFS 5.28 sp10586 sept 9 1999, EFS  sp14378 5.38b nov 1 2000, efs5.38a sp14378(again) 11 oct 2000. Thanks for your reply and to a fast response from Compaq.  &lt;BR /&gt;Clive Rhodes</description>
      <pubDate>Wed, 04 Apr 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512685#M5404</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-04T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512686#M5405</link>
      <description>Clive - I have attempted installs on a pair of ML350's, with no success.  There &lt;BR /&gt;seems to be a variable I have not sorted out, because I was able to complete &lt;BR /&gt;an install a few weks ago. The assisted install fails ( I think ) because 5.38a &lt;BR /&gt;is on the 4.90 CD, which is autoloaded at the end of a SCO install. This causes &lt;BR /&gt;the first reboot after the install to hang at " H iinit ", which I think is &lt;BR /&gt;a first step in accessing the hard drive.  The 5.38a BTLD causes a hang at the &lt;BR /&gt;same point that you observed.  Only stepping through a manual installation, then &lt;BR /&gt;loading EFS 5.38b seemed to work.  Is there various releases of SS 4.90 ? &lt;BR /&gt; &lt;BR /&gt;Your PCI interrupt table differs from what I expect. My controllers share the &lt;BR /&gt;interrupts, as follows &lt;BR /&gt; &lt;BR /&gt;FPU 13, serial 4 &amp;amp; 3, parallel 7, floppy 6, IDE 14, network 15, kbmouse 12, &lt;BR /&gt; &lt;BR /&gt;BUT both ad160 controllers are on 11.  Should leave 10  &amp;amp; 5 for the 8 port. &lt;BR /&gt; &lt;BR /&gt;Update this when you can.</description>
      <pubDate>Fri, 06 Apr 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512686#M5405</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-06T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512687#M5406</link>
      <description>Scoace - ad160 driver. I may have misled myself on this. I dowloaded efs 5.38b and created the BTLD floppy then installed OS5 successfully with this disk. The bad news is I installed V5.05 accidentally!! So then I tried V5.06 and it hung as usual. Using the default ad160 on the SCO cd worked ok so it looks like a problem specific to 5.06 &lt;BR /&gt; &lt;BR /&gt;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.</description>
      <pubDate>Sun, 08 Apr 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512687#M5406</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-08T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512688#M5407</link>
      <description>Finally, manual install of sco5.06 with ad160 from floppy works IF at boot: &lt;BR /&gt; &lt;BR /&gt;defbootstr link="ad160" hd=Sdsk Srom=wd(0,0,0) scsi.noscan &lt;BR /&gt; &lt;BR /&gt;is entered. Used this after reading on &lt;A href="http://www.sco.com" target="_blank"&gt;www.sco.com&lt;/A&gt; 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. &lt;BR /&gt; &lt;BR /&gt;Clive Rhodes</description>
      <pubDate>Sun, 08 Apr 2001 23:00:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512688#M5407</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-08T23:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512689#M5408</link>
      <description>Clive - I guess one of the "variables that I haven't sorted out" is the fresh &lt;BR /&gt;installation of 5.0.6 over 5.0.6 .  Thanks.  I can get the manual install to &lt;BR /&gt;work, and run 5.0.6 sucessfully. When I install EFS5.38b ( from single user &lt;BR /&gt;mode), relink and reboot, the reboot hangs at " H iinit ". Going back to the &lt;BR /&gt;old kernel, removing EFS5.38b fixes the problem.  Can you run EFS5.38b ?</description>
      <pubDate>Wed, 11 Apr 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512689#M5408</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-11T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512690#M5409</link>
      <description>Scoace- no problems implementing efs5.38b(sp14378.exe on Compaq site). The file /usr/adm/messages verifies its 5.38b on the Compaq SCSI-2, Compaq Proliant Storage system, Compaq Wellness Driver and Compaq rom driver lines. Machine bios is Do4/F04 11/13/2000. Irqs used are: &lt;BR /&gt;13   fpu &lt;BR /&gt; 4    serial &lt;BR /&gt; 3    serial &lt;BR /&gt; 6    floppy &lt;BR /&gt;12   kbmouse &lt;BR /&gt; 5    cpqw compaq wellness &lt;BR /&gt;10   compaq onboard nic &lt;BR /&gt;11    ultra 3 port 1 &lt;BR /&gt;11    ultra 3 port 2 &lt;BR /&gt;14    ide controller &lt;BR /&gt;15    specialix serial card &lt;BR /&gt;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?</description>
      <pubDate>Mon, 16 Apr 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512690#M5409</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-16T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512691#M5410</link>
      <description>Clive, still not much luck with efs5.38x, but the SS 5.00 and CMA 5.00, &lt;BR /&gt;which has EFS 5.40, seems to work.  I am having a problem with some of the &lt;BR /&gt;ML530's in the field, they seem to ASR after 13-14 days if they are heavily &lt;BR /&gt;loaded.  Removing the CMA seems to correct the problem, but then you lose &lt;BR /&gt;all that functionality. I am retesting the new CMA version to see what happens.</description>
      <pubDate>Mon, 30 Apr 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512691#M5410</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-04-30T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512692#M5411</link>
      <description>Clive, &lt;BR /&gt; &lt;BR /&gt;Hope you still are in the loop.  After more problems on a total of 5 ML350, &lt;BR /&gt;and a lot of effort from Canadian tech support, I have conformation that there &lt;BR /&gt;IS a problem with the Adaptec chip set and the AD160 driver.  No solution as &lt;BR /&gt;of yet, but some machine will hang at H iinit at boot time.  &lt;BR /&gt; &lt;BR /&gt;scoace</description>
      <pubDate>Wed, 25 Jul 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512692#M5411</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-07-25T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512693#M5412</link>
      <description>scoace - thanks for the information. I know it doesn't help your position but the only ml350 using the ad driver with discs attached (the one which caused all this in the first place) has been in use at one of our customers since April with no problems - and this reboots itself nightly!. But I am still monitoring the machine and this forum. &lt;BR /&gt;Cliver</description>
      <pubDate>Thu, 26 Jul 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512693#M5412</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-07-26T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512694#M5413</link>
      <description>Hi Clive,  are you going to Caldera Forum? &lt;BR /&gt;Do NOT upgrade the BIOS on your ML350, it may stop working.  I had been &lt;BR /&gt;upgrading the machines to 03/13/01 before installing, and not having any luck. &lt;BR /&gt;I loaded and tested a machine with the 10/13/00 BIOS, and started having the &lt;BR /&gt;boot hang after the bios upgrade.</description>
      <pubDate>Sat, 04 Aug 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512694#M5413</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-08-04T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512695#M5414</link>
      <description>Hi, I encounter the familiar "H iinit" problem during installation,  its normally will hangs after loading the entire efs V5.42.  and this only happened if I have two partition on a single drive.  but if I omit the Compaq Proliant Storage System Support Driver, the system seems to work.  What this driver suppose to do?</description>
      <pubDate>Thu, 16 Aug 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512695#M5414</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-08-16T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: ad160 driver</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512696#M5415</link>
      <description>Interesting...  The Storage System Driver should talk to a hot swap backplane, &lt;BR /&gt;such as an external storage cabinet, that may report temperature or other &lt;BR /&gt;metrics back to the host server.  Could it be that by not having two partitions &lt;BR /&gt;on the hard drive you are not going through SS, and not loading the Compaq &lt;BR /&gt;drives?</description>
      <pubDate>Wed, 22 Aug 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ad160-driver/m-p/2512696#M5415</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-08-22T23:00:00Z</dc:date>
    </item>
  </channel>
</rss>

