asked on

Extracting image (.img) file

I have to install a scsi driver during my Redhat linux 7.2 installation
for the onboard Ultra 320 SCSI. I got the driver from adaptec site and extracted the image using " dd " . But in the extracted files . there is a readme file which is no in a readable format so i cant follo the instructions.. when i insert the driver disk during installation its accpting the driver but could not identify scsi.. so i doubt i have to follow the instructions in the README flie..
So my question is whether there is any error in my extraction. iused the command... dd if= name.img of= /dev/fd0.. is it correct... or sholud i mention any more option in order to read the README file.( which looks like a binary file).. please provide me a solution....

Thanks and regards

owensleftfoot

It worked ok for me with the command
dd if=aic79xx-1.1.0-i686-rh72.img of=/dev/fd0 Try downloading the file again. Anyway here is the readme -
===================================================================
= Adaptec Ultra320 Family Manager Set v1.10 =
= =
= README for =
= Redhat Linux 7.3 =
= Redhat Linux 7.2 =
= Redhat Linux Advanced Server 2.1 =
= SuSE Linux 7.3 =
= SuSE Linux 8.0 =
= SuSE Linux Enterprise Server 7 =
====================================================================

The following information is available in this file:

1. Supported Hardware
2. Version History
3. Installation Instructions
4. Command Line Options
5. Additional Notes
6. Diskette Structure
7. Contacting Adaptec

1. Supported Hardware

The following Adaptec SCSI Host Adapters are supported by this
driver set.

Ultra320 Adapters Description
----------------------------------------------------------------
Adaptec SCSI Card 39320 Dual Channel 64-bit PCI-X 133MHz to
Ultra320 SCSI Card (one external
68-pin, two internal 68-pin)
Adaptec SCSI Card 39320D Dual Channel 64-bit PCI-X 133MHz to
Ultra320 SCSI Card (two external VHDC
and one internal 68-pin)
Adaptec SCSI Card 29320 Single Channel 64-bit PCI-X 133MHz to
Ultra320 SCSI Card (one external
68-pin, two internal 68-pin, one
internal 50-pin)
Adaptec SCSI Card 29320LP Single Channel 64-bit Low Profile
PCI-X 133MHz to Ultra320 SCSI Card
(One external VHDC, one internal
68-pin)

AIC-7901A Single Channel 64-bit PCI-X 133MHz to
Ultra320 SCSI ASIC
AIC-7902A4 Dual Channel 64-bit PCI-X 133MHz to
Ultra320 SCSI ASIC

2. Version History

(V1.10, August 2002) Added support for four additional SCSI
products: ASC-39320, ASC-29320, ASC-29320LP, AIC-7901.

(V1.00, May 2002) This is the initial release of the
Ultra320 FMS. The following is a list of supported features:

2.1. Software/Hardware Features
- Support for the SPI-4 "Ultra320" standard:
- 320MB/s transfer rates
- Packetized SCSI Protocol at 160MB/s and 320MB/s
- Quick Arbitration Selection (QAS)
- Initiator Mode (target mode not currently
supported)
- Support for the PCI-x standard up to 133MHz
- Support for the PCI v2.2 standard

2.2. Operating System Support:
- Redhat Linux 7.2, 7.3, Advanced Server 2.1
- SuSE Linux 7.3, 8.0, Enterprise Server 7
- only Intel and AMD x86 supported at this time
- >4GB memory configurations supported.

Refer to the User's Guide for more details on this.

3. Installation Instructions

3.1. Installing Redhat Linux 7.2/7.3/Advanced Server 2.1 with an
Ultra320 SCSI Host Adapter

1) Install the Ultra320 adapter and power on your system.
2) Boot from the Redhat CDROM.
3) At the boot menu, type 'linux dd' and press ENTER.
4) Follow the on-screens prompts to insert the Adaptec
Redhat driver disk.
5) Procede with the normal Redhat installation steps.
6) For RedHat 7.2, additional steps are required:
a) At the Boot Loader Configuration Menu, select 'Use
Grub as the Boot Loader'.
b) At the Boot Disk Configuration Menu, select 'Skip Boot
Disk Creation'.
c) At the Congratulations screen, press CTRL+ALT+F2
d) Type: chroot /mnt/sysimage
e) Type: mount /dev/fd0 /mnt
f) Type: /mnt/fixup.sh
g) Press ALT+F7 and proceed with the installation.

3.2. Installing SuSE 7.3/8.0/Enterprise Server 7 with an Ultra320
SCSI Host Adapter
1) Install the Ultra320 adapter and power on your system.
2) Boot from the SuSE CDROM.
3) At the boot menu, press the ALT key to stop the boot.
4) Press 'Enter' and follow the onscreen prompts to insert
the Adaptec SuSE driver disk.
5) Proceed with the normal SuSE installation steps.

3.3. Installing the Driver when Redhat or SuSE is Already
Installed

1) Fetch the Adaptec driver RPM file appropriate to your version
of RedHat/SuSE.
2) Type: rpm -ivh <RPM file>
3) Make sure to reboot the system by issuing the command
"shutdown -h now". After the system reboots, the
procedure is then done.

3.3. Removing the Driver

Removing the Adaptec U320 driver is not presently supported.

4. Command Line Options

WARNING: ALTERING OR ADDING THESE DRIVER PARAMETERS
INCORRECTLY CAN RENDER YOUR SYSTEM INOPERABLE.
USE THEM WITH CAUTION.

Edit the file "modules.conf" in the directory /etc and add/edit a
line containing 'options aic79xx=[command[,command...]]' where
'command' is one or more of the following:
-----------------------------------------------------------------
Option: verbose
Definition: enable additional informative messages during
driver operation.
Possible Values: This option is a flag
Default Value: disabled
-----------------------------------------------------------------
Option: debug:[value]
Definition: Enables various levels of debugging information
Possible Values: 0x0000 = no debugging, 0xffff = full debugging
Default Value: 0x0000
-----------------------------------------------------------------
Option: no_reset
Definition: Do not reset the bus during the initial probe
phase
Possible Values: This option is a flag
Default Value: disabled
-----------------------------------------------------------------
Option: extended
Definition: Force extended translation on the controller
Possible Values: This option is a flag
Default Value: disabled
-----------------------------------------------------------------
Option: periodic_otag
Definition: Send an ordered tag periodically to prevent
tag starvation. Needed for some older devices
Possible Values: This option is a flag
Default Value: disabled
-----------------------------------------------------------------
Option: reverse_scan
Definition: Probe the scsi bus in reverse oder, starting
with target 15
Possible Values: This option is a flag
Default Value: disabled
-----------------------------------------------------------------
Option: global_tag_depth
Definition: Global tag depth for all targets on all busses.
This option sets the default tag depth which
may be selectively overridden vi the tag_info
option.
Possible Values: 1 - 253
Default Value: 32
-----------------------------------------------------------------
Option: tag_info:{{value[,value...]}[,{value[,value...]}...]}
Definition: Set the per-target tagged queue depth on a
per controller basis. Both controllers and targets
may be ommitted indicating that they should retain
the default tag depth.
Examples: tag_info:{{16,32,32,64,8,8,,32,32,32,32,32,32,32,32,32}
On Controller 0
specifies a tag depth of 16 for target 0
specifies a tag depth of 64 for target 3
specifies a tag depth of 8 for targets 4 and 5
leaves target 6 at the default
specifies a tag depth of 32 for targets 1,2,7-15
All other targets retain the default depth.

tag_info:{{},{32,,32}}
On Controller 1
specifies a tag depth of 32 for targets 0 and 2
All other targets retain the default depth.

Possible Values: 1 - 253
Default Value: 32
-----------------------------------------------------------------
Option: rd_strm: {{rd_strm_bitmask}[,{rd_strm_bitmask}...]}
Definition: Enable read streaming on a per target basis.
The rd_strm_bitmask is a 16 bit hex value in which
each bit represents a target. Setting the target's
bit to '1' enables read streaming for that
target. Controllers may be ommitted indicating that
they should retain the default read streaming setting.
Example: rd_strm:{{0x0041}}
On Controller 0
enables read streaming for targets 0 and 6.
disables read streaming for targets 1-5,7-15.
All other targets retain the default read
streaming setting.
Example: rd_strm:{{0x0023},{},{0xFFFF}}
On Controller 0
enables read streaming for targets 1,2, and 5.
disables read streaming for targets 3,4,6-15.
On Controller 2
enables read streaming for all targets.
All other targets retain the default read
streaming setting.

mshajan

ASKER

Hai owensleftfoot...
Thank you very much for your reply. But i made a mistake it was a driver for SCSi Adaptec SCSI Card 39320 . But the onboard SCSI was

• Adaptec AIC-7902 Controller • Dual-Channel Ultra320 SCSI

I checked in the adaptec site. But in the driver downloads, there are only drivers for SCSI Cards in the Ultra 320 section. we didnt find any drivers for the above said scsi..

So i would be grateful to you if you could provide a link to the driver for the above mentioned driver.

Thanks and Regards

owensleftfoot

Do you have an Adaptec 39320 or an Adaptec 7902?

mshajan

ASKER

It is . Adaptec 7902 ( ONBOARD Adaptec AIC-7902 SCSI Controller )

Alf666

May I suggest you download a more recent RedHat ? This driver is included in recent 2.4 kernels.

ASKER CERTIFIED SOLUTION

owensleftfoot

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mshajan

ASKER

owensleftfoot,
This is the driver i extracted and used while installation, but it didnt help, it showed the error,"unable to find the appropriate device for making the partitions" just after the partition wizard....

Also we cannot go for any other version of Redhat as our softwares are complied for Redhat 7.2...

toh197

either the floppy is bad or you didn't download the image correctly...
you can try mount the image using:

mount name.img some_directory/ -o loop

it will work, but if mount try to ask you to specify the filesystem
try insert fat/vfat modul

you can also use:

file name.img

to identify the filesystem

owensleftfoot

Did you redownload the file? If the readme.txt was corrupt, the chances are the kernel module is as well.