Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm attempting to get my new IDE-SCSI hardware RAID to be recognised on my
Red Hat 7.3 box, without much success. The SCSIselect utility quite
happily sees the device, but I don't get the usual device detection (via
the card BIOS) upon boot.
Although the SCSIselect utility tells me the device is not a disk drive.
Some dmesg output for your info :-
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
The HBA was detected just fine. Do I have to tinker with the kernel?
Current kernel is 2.4.18-27.7.x.
Any suggestions anyone? Any advice muchly appreciated!
The RAID device has an IFT-7200 controller . I set it to SCSI device 1
(and I've tried numerous different settings, cables and cards). The device
was pre-configured to RAID-5 at the factory.
I'm using an identical card just fine in another RH 7 box using LILO but not with RAID. The card is definitely detected, according to dmesg. The driver file seems to be present in /proc/scsi/aic7xxx but /proc/scsi/scsi says I have no devices attached.
I couldn't find that particular card in the kernel configs. If you think this may be an Adaptec card see the following snippet.
From the kernel help...
│ This driver supports all of Adaptec's I2O based RAID controllers as
│ well as the DPT SmartRaid V cards. This is an Adaptec maintained
│ driver by Deanna Bonds. See drivers/scsi/README.dpti.
│ This driver is also available as a module ( = code which can be
│ inserted in and removed from the running kernel whenever you want).
│ If you want to compile it as a module, say M here and read
│ Documentation/modules.txt. The module will be called
I get :-
00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] System Controller (rev 25)
Flags: bus master, medium devsel, latency 120
Memory at e8000000 (32-bit, prefetchable)
Memory at efdff000 (32-bit, prefetchable)
I/O ports at da00 [disabled]
Capabilities: [a0] AGP version 1.0
00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-756 [Viper] ISA (rev 01)
Flags: bus master, medium devsel, latency 0
00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-756 [Viper] IDE (rev 07) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at f000
00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-756 [Viper] ACPI (rev 03)
Flags: medium devsel
00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-756 [Viper] USB (rev 06) (prog-if 10 [OHCI])
Flags: bus master, medium devsel, latency 16, IRQ 5
Memory at efffd000 (32-bit, non-prefetchable)
00:08.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 01)
Subsystem: Adaptec AHA-2940UW SCSI Host Adapter
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at de00 [disabled]
Memory at effff000 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 1
00:0a.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Mana
01:05.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage Fury Pro/Xpert 2000 Pro
Flags: bus master, stepping, 66Mhz, medium devsel, latency 64, IRQ 11
Memory at e0000000 (32-bit, prefetchable)
I/O ports at c800
Memory at efefc000 (32-bit, non-prefetchable)
Capabilities:  AGP version 2.0
Capabilities: [5c] Power Management version 2
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at dc00
Memory at efffef80 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 2
OK i've been readaing up on this rig. It appears to be an ATA-to-SCSI RAID box that takes ATA drives and makes them avaiable through some hardware voodoo to the SCSI RAID controller. From there it's supposed to present itself as a SCSI device to the host computer.
After browsing the .pdf documentation the situation you are in is not much clearer to me.
So let's confirm that the following things are working;
1) The device has a SCSI ID and that ID is not being used by any other SCSI device (including your onboard controller).
2) The device is terminated properly; ie: if it is the last SCSI device on the chain it should be terminated.
3) Your controller is terminated properly.
4) You can see your onboard Adaptec controller as a functional SCSI device in Linux. You have a kernel built for SCSI or you have the correct modules loaded for the onboard controller. If you have the proc filesystem running you should see a directory like this '/proc/scsi/aic7xxx'
>From there it's supposed to present itself as a SCSI device to >the host computer.
>So let's confirm that the following things are working;
>1) The device has a SCSI ID and that ID is not being used by >any other SCSI device (including your onboard controller).
Yes, the device is set to SCSI ID1, the card is 7. There are no other SCSI devices attached to my PC.
>2) The device is terminated properly; ie: if it is the last SCSI >device on the chain it should be terminated.
That's correct, it is terminated. I have also tried differing terminators.
>3) Your controller is terminated properly.
I assume it is, at least it should have been at the factory(?)
>4) You can see your onboard Adaptec controller as a >functional SCSI device in Linux. You have a kernel built for >SCSI or you have the correct modules loaded for the onboard >controller. If you have the proc filesystem running you should >see a directory like this '/proc/scsi/aic7xxx'
Yep, its there.
>What does 'fdisk -l' report?
sh-2.05a# /sbin/fdisk -l
Disk /dev/hda: 255 heads, 63 sectors, 2480 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 6 48163+ 83 Linux
/dev/hda2 1411 2480 8594775 83 Linux
/dev/hda3 7 643 5116702+ 83 Linux
/dev/hda4 644 1410 6160927+ f Win95 Ext'd (LBA)
/dev/hda5 644 1280 5116671 83 Linux
/dev/hda6 1281 1410 1044193+ 82 Linux swap