Hardware config question with a CD-Writer Issue - SCO

This is a discussion on Hardware config question with a CD-Writer Issue - SCO ; 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 ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Hardware config question with a CD-Writer Issue

  1. Hardware config question with a CD-Writer Issue

    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.

    --
    Brian Keener
    bkeenerReMoVeAnTiSpAm@thesoftwaresource.com


    name=kernel vec=- dma=- rel=3.2v5.0.7 kid=2003-02-18
    name=cpu vec=- dma=- unit=1 family=15 type=Intel Xeon
    name=cpuid vec=- dma=- unit=1 vend=GenuineIntel tfms=0:15:2:9(11)
    name=fpu vec=13 dma=- unit=1 type=80387-compatible
    name=pci base=0xCF8 offset=0x7 vec=- dma=- am=1 sc=1 buses=6
    name=PnP vec=- dma=- nodes=0
    name=clock vec=- dma=- type=TSC/3.056485078Ghz
    name=serial base=0x3F8 offset=0x7 vec=4 dma=- unit=0 type=Standard nports=1
    base
    =0 16550A/16
    name=console vec=- dma=- unit=vga type=0 num=12 scoansi=1 scroll=50
    name=adapter base=0x2400 offset=0xFF vec=3 dma=- type=ad160 ha=0 slot=0 bus=0
    id
    =7 fts=sto
    name=adapter base=0x2800 offset=0xFF vec=3 dma=- type=ad160 ha=1 slot=0 bus=0
    id
    =7 fts=sto
    name=floppy base=0x3F2 offset=0x5 vec=6 dma=2 unit=0 type=135ds18
    name=kbmouse base=0x60 offset=0x4 vec=12 dma=- type=Keyboard|PS/2 mouse id=0x00
    name=udi vec=- dma=- UDI environment
    name=adapter vec=- dma=- ha=0 type=usb_msto UDI SCSI HBA
    name=adapter base=0x1F0 offset=0x7 vec=14 dma=- type=IDE ctlr=primary dvr=wd
    name=adapter base=0x3000 offset=0x100 vec=15 dma=- type=ciss ha=0 PCI slot=2
    (re
    v 5.62a)
    name=bcme0 vec=5 dma=- chip=BCM5702 mem=F5FE0000 phy=BCM5703
    addr=00:0b:cd:cd:84
    :6e
    name=cd-rom vec=- dma=- type=IDE unit=0 ctlr=pri cfg=mst dvr=Srom->wd
    name=cd-rom vec=- dma=- type=IDE unit=1 ctlr=sec cfg=mst dvr=Srom->wd
    name=tape vec=- dma=- type=S ha=0 id=3 lun=0 bus=2 ht=ciss unit=0
    name=tape vec=- dma=- type=S ha=1 id=3 lun=0 bus=0 ht=ad160 unit=1
    name=disk vec=- dma=- type=S ha=0 id=0 lun=0 bus=0 ht=ciss unit=0
    name=Sdsk vec=- dma=- cyls=17432 hds=255 secs=32 unit=0 fts=stdb
    name=Sdsk-0 vec=- dma=- Vnd=HP Prd=LOGICAL VOLUME Rev=1.30
    name=usb_ohci vec=11 dma=- PCI bus=0 dev=15 func=2
    name=Stp-1 vec=- dma=- Vnd=HP Prd=Ultrium 1-SCSI Rev=N26D



  2. Re: Hardware config question with a CD-Writer Issue

    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
    ====== ======= === === =======
    kernel - - - rel=3.2v5.0.7 kid=2003-02-18
    cpu - - - unit=1 family=15 type=Intel Xeon
    cpuid - - - unit=1 vend=GenuineIntel tfms=0:15:2:9(11)
    fpu - 13 - unit=1 type=80387-compatible
    pci 0xcf8-0xcff - - am=1 sc=1 buses=6
    PnP - - - nodes=0
    clock - - - type=TSC/3.056485078Ghz
    serial 0x3f8-0x3ff 4 - unit=0 type=Standard nports=1 base=0 16550A/16
    console - - - unit=vga type=0 num=12 scoansi=1 scroll=50
    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
    floppy 0x3f2-0x3f7 6 2 unit=0 type=135ds18
    kbmouse 0x60-0x64 12 - type=Keyboard|PS/2 mouse id=0x00
    udi - - - UDI environment
    adapter - - - ha=0 type=usb_msto UDI SCSI HBA
    adapter 0x1f0-0x1f7 14 - type=IDE ctlr=primary dvr=wd
    adapter 0x3000-0x3100 15 - type=ciss ha=0 PCI slot=2 (rev 5.62a)
    bcme0 - 5 - chip=BCM5702 mem=F5FE0000 phy=BCM5703 addr=00:0b:cd:cd:84:6e
    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
    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
    disk - - - type=S ha=0 id=0 lun=0 bus=0 ht=ciss unit=0
    Sdsk - - - cyls=17432 hds=255 secs=32 unit=0 fts=stdb
    Sdsk-0 - - - Vnd=HP Prd=LOGICAL VOLUME Rev=1.30
    usb_ohci - 11 - PCI bus=0 dev=15 func=2
    Stp-1 - - - Vnd=HP Prd=Ultrium 1-SCSI Rev=N26D

    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<


+ Reply to Thread