Re: Problems with OpenServer 6

On Sun, Jul 30, 2006 at 09:46:49PM -0700, C. Coulter wrote:
Hi all!

Here's the configuration that I'm having problems
with:

Hardware:
Asus P5WD2 Motherboard with Marvell Gigabit onboard
Intel P4 2.8 GHz
Crucial 512 MB memory
Asus 64 MB MX4000 video card
Adaptec 29160 SCSI adapter
Seagate Travan 8 tape drive
Two (2) Seagate Barracuda 7200.10 320 GB SATA II disks
Sony 1.44 MB Floppy
Sony DW-U30 DVD burner
Moxa CP104JU 4 port RJ45 serial port card

Software:
OpenServer 6.0.0
OpenServer 6 Development System
Maintenance Pack 2
Marvell Yukon ethernet driver

Problem No. 1:
I had a functioning OpenServer 6 system when
I checked the SCO web site and saw that there were
a number of patches that SCO was "recommending" over and
above Maintenance Pack 2. So, I downloaded them and
applied them. I had been using my DVD burner to backup
and restore files without any problems prior to this.
However, once I applied the patches, my DVD burner and
IDE driver no longer appeared during the system boot
process and I could no longer use the DVD drive.

I wasn't sure what caused the problem, so I did a
fresh install of OpenServer 6 and then applied the
patches one by one. I was able to determine that
the problem was caused by patch 7.1.4d to the IDE
driver. As soon as that patch was applied, the
driver would disappear from the boot process.
However, it was still shown in "pkginfo". I then
used "pkgrm" to remove the IDE driver and applied
patches 7.1.4c and 7.1.4b (in that order) from the
SCO website. Neither one made the DVD drive and
the IDE interface usable. Unfortunately, 7.1.4a
(which is what comes with the base operating
system was not available on the website). Does
anyone know if this is a defective patch? Could
I have done something wrong to cause this? How
can you retrieve the base driver 7.1.4a when a
patch is installed using "pkgadd" and doesn't
give you a chance to retain the original files as
"custom" often did?

I don't know the answer to this question, but I've looked
at your motherboard specs and manual and the the driver readmes.

In the BIOS, you should set: Configure SATA as to AHCI
The setting for: Onboard IDE operate mode I'm not sure.
You may be able to set it to Enhanced mode, you may have to play
with it.

Try each until everything shows up in the boot list or "sdiconfig -l".

If your drives weren't in AHCI mode originally, you should re-install
so that the AHCI driver gets picked up, then install AHCI 1.2 either
before or after MP2.


Tom
D. Thomas Podnar
Microlite Corporation
2315 Mill Street
Aliquippa PA USA 15001-2228
724-375-6711
888-257-3343 Sales
Developers of Microlite BackupEDGE



Problem No. 2:
We all know that OS6 supports large files. In
addition, the SCO website states that certain
utilities such as "cdrecord" are supported.
However, the problem that I have run into is
as follows: I create a large file and burn it to
DVD using "mkisofs -r -J -o filename.isoimg"
and "cdrecord -gracetime=0 -sao filename.isoimag"
However, when I attempt to extract the file from
the mounted DVD filesystem, I always get an error
near the end of the extraction (where the 2 GB
limit would be) that indicates the "value is too
large." In researching this on the Internet, it
would appear that this is a limitation in
mkisofs (possibly due to the RockRidge/Joiet
format) and/or cdrecord.

Does anyone know of a way to get around this
problem? Why doesn't SCO provide large file
aware versions of "mkisofs", "cdrecord", and,
most importantly, "tar"??? If SCO is going
to force us to change scripts to use the
"/u95/bin" directory, shouldn't there be
versions of all the appropriate utilities in
there?

I know that most of you will respond by
indicating that I should be using a supertar.
I'm quite familiar with these products, but
they have their own problems. As a dealer
and software developer, we don't release our
customer names to anyone. Yet, that is
exactly what the supertar manufacturer's want
you to do. In addition, that media may not
always be compatible with Windows systems.

I know that this is very long, but I've tried
to give you as much information as I have
regarding these 2 problems.

Please respond if you have any input,

C. Coulter
wizard2277@xxxxxxxxxxx (public address)
.

Relevant Pages

  • Problems with OpenServer 6
    ... I checked the SCO web site and saw that there were ... I had been using my DVD burner to backup ... IDE driver no longer appeared during the system boot ... the problem was caused by patch 7.1.4d to the IDE ...
    (comp.unix.sco.misc)
  • Re: Problems with OpenServer 6
    ... You should DEFINITELY turn on AHCI so you can use the AHCI driver. ... Btw, during install, you can see error messages if you switch to the ... If your drives weren't in AHCI mode originally, ...
    (comp.unix.sco.misc)
  • Re: Problems with OpenServer 6
    ... IDE driver no longer appeared during the system boot ... you should set: Configure SATA as to AHCI ... If your drives weren't in AHCI mode originally, ... so that the AHCI driver gets picked up, then install AHCI 1.2 either ...
    (comp.unix.sco.misc)
  • Re: external eSata enclosure drive recognition?
    ... for the port in the BIOS, and driver to go with it, to get support. ... I did some more reading on this last nite, and apparently one needs AHCI to support this "hot plugging" capability. ... And since I only have the older Intel ICH9 controller, it isn't supported, nor are drivers available for AHCI from Intel that will update it (although there is an unsupported patch for AHCI at one of the MSDN sites that *supposedly* will allow the standard ICH9 driver to be patched to get AHCI, instead of just IDE emulation of SATA. ...
    (microsoft.public.windowsxp.hardware)
  • [git patches] libata updates
    ... All bug fixes except for the one-line Promise PCI ID addition to ahci, ... and the amd74xx.c driver by Vojtech Pavlik. ... pata_efar.c - EFAR PIIX clone controller driver ... + * Copyright 2005/2006 Red Hat Inc, ...
    (Linux-Kernel)