News Group Posts

ide cd-writer

From belal@sco.com Sun Mar  7 09:58:43 2004
Newsgroups: comp.unix.sco.programmer
From: Bela Lubkin <belal@sco.com>
Subject: Re: Hardware config question with a CD-Writer Issue
  by mail.ut.sco.com with SMTP; 6 Mar 2004 02:20:43 -0000
Date: Sat, 6 Mar 2004 02:24:33 GMT
Message-ID: <20040306022432.GD24746@sco.com>
X-Nntp-Posting-Host: enigma.xenitec.on.ca
References: <VA.00000f0c.00b95808@thesoftwaresource.com>
Resent-By: mmdf@xenitec.on.ca

Brian Keener wrote:

> Newsgroups: comp.unix.sco.programmer

this really belongs on .misc...

> I have a customer currently in the process of upgrading their system (actually 
> a full replacement) from a SCO Openserver 5.0.5 to Openserver 5.0.7.  I do 
> their application software but have been assisting in system configuration and 
> testing and we are currently having problems getting the CD Writer to install.  
> To my knowledge - no patches are installed as reading the update on the wd 
> driver and newsgroup posting I do not believe I need that to make the CD Writer 
> work for 5.0.7. But thought I would point out about no updates - just in case.
> 
> It appears the machine was ordered and configured to their specs from Compaq 
> and then another person actually installed the OSR5.0.7.  The system was 
> configured for RAID and Tape Backup and then will eventually have a zip drive 
> but also has a CD Reader and a CDWriter.  The disk and tape and CD Reader have 
> been working without a hitch but attempts to get the CD Writer to work have 
> been frustrating. They kept trying to install the CD Writer on the Primary IDE 
> as the Slave device but that would hang the system (lock it down) when we would 
> attempt to mount the device.  I told them they would need to pull the cover or 
> get the hardware guy to and determine exactly where the drive was cabled and 
> also if the devices have jumpers for master or slave or cable select make sure 
> they are set for master or slave and not cable select (remove the guess work).  
> 
> They pulled the cable and asked the hardware fellow if the CdWriter was on the 
> primary or secondary and he advised secondary.  We then removed the second CD 
> from the system configuration and reconfigured it as the master on the 
> secondary controller.  It does not hang the system now but does hang the 
> process that tried to mount it.  Any attempts to kill the process doing the 
> mount will blindly fail (process will continue to exist after a kill).
> 
> Further digging has revealed the Disk and tape are both SCSI and I would say 
> there appears to be an Adaptec Controller involved (ad160) or that might be 
> some form of a Compaq controller and the Compaq Intelligent Storage Subsystem 
> (ciss) driver also involved.
> 
> I have posted the output for hwconfig below - because my review of it makes me 
> believe that there is no second IDE controller and it also appears to show two 
> tapes configured (we have only one) - one on the ad160 and one on the ciss.  
> Based on the output below - I am questioning whether there CDWriter is 
> secondary IDE or could it be a SCSI Writer and if there are other config errors 
> like a second tape that should not be there.  I have asked them to get the 
> Hardware guys to give us a full accounting of devices in the system and their 
> controllers.
> 
> Any info anyone could supply on getting the CDWriter to work and/or if the 
> hardware on this thing looks believable based on the below would be greatly 
> appreciated.

I converted the `hwconfig` output you supplied to `hwconfig -h` output:

device          address    vec  dma  comment

Regarding the IDE subsystem and CD-ROMs, these lines:

adapter       0x1f0-0x1f7   14   -   type=IDE ctlr=primary dvr=wd
cd-rom             -         -   -   type=IDE unit=0 ctlr=pri cfg=mst dvr=Srom->wd
cd-rom             -         -   -   type=IDE unit=1 ctlr=sec cfg=mst dvr=Srom->wd

show that the link kit is configured for two IDE CD-ROMs, but only one
is physically being detected.  The "wd" driver only announces an
"adapter" when it sees at least one ATAPI device on the controller.  So
there's an ATAPI device on master, slave, or both positions of the
primary controller; no ATAPI devices on the secondary controller.  The
"cd-rom" lines only tell us what the link kit is configured for.

You can get more information if you install the "Wd Driver Supplement",
then add "wd.debug=ui" to the bootstring.

Because there are no IDE hard disks, the CD-ROMs should be configured
as primary/master and either primary/slave or (preferably, if there are
two IDE controllers) secondary/master.  Since the link kit is already
configured for primary/master & secondary/master, the best thing is to
jumper the drives to match.

Regarding the tape(s):

adapter      0x2400-0x24ff   3   -   type=ad160 ha=0 slot=0 bus=0 id=7 fts=sto
adapter      0x2800-0x28ff   3   -   type=ad160 ha=1 slot=0 bus=0 id=7 fts=sto
adapter      0x3000-0x3100  15   -   type=ciss ha=0 PCI slot=2 (rev 5.62a)
tape               -         -   -   type=S ha=0 id=3 lun=0 bus=2 ht=ciss unit=0
tape               -         -   -   type=S ha=1 id=3 lun=0 bus=0 ht=ad160 unit=1
Stp-1              -         -   -   Vnd=HP Prd=Ultrium 1-SCSI Rev=N26D

We see two "ad160" adapters, both in slot 0 -- probably a single board
with two buses, the driver has chosen to present this as two adapters
rather than a single dual-bus adapter.  That's up to the driver.

We see two "tape" lines, one on "ciss" and one on "ad160" second adapter
(ha=1).  Again, this shows how the link kit is configured (i.e.
corresponds to the contents of /etc/conf/cf.d/mscsi).  Then we see
"Stp-1": this shows the hardware vendor/product/revision attached to the
"tape... unit=1" line.  So your tape drive is definitely on the "ad160".

Don't edit mscsi directly.  You can use `mkdev tape` to remove the tape
drive on "ciss".  Note that the device nodes will shuffle down -- the
drive is currently accessible as /dev/rStp1, it would become rStp0.

The mscsi configuration for the CD-ROMs is already sensible.  You just
need to get the hardware lined up with it.

>Bela<

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.