Skip to contentSkip to conversation

Solution - AMI megaraid driver doesn't work with Linux 2.4.x kernels

DISCUSSION Rafael Martinez 2 participants 3 messages May 3, 2001 – May 4, 2001

lore
Share & tools
lore
#0 lore raw

Hei

The Ami megatrends driver (at least for 471, 475, and 493) does not work with 2.4.x kernels.

The solution we got from Ami is to update the firmware of these cards to version FW G158. This update will fix all the problems with ami raid-devices in 2.4.x kernel without changing the driver.

We don't know when AMI will release a fixed firmware (hope soon) but we got it by e-mail. If there is anybody with the same problem I can sent the firmware-update by mail.

Sincerely
Rafael Martinez

#1 lore raw

Can you provide the dmesg output of your system after loading the driver either successfully or unsucessfully.

----- Original Message -----
From: "Rafael Martinez" <[email protected]>
To: <[email protected]>
Sent: Thursday, May 03, 2001 11:37 AM
Subject: Solution - AMI megaraid driver doesn't work with Linux 2.4.x kernels

Quoted 10 lines

Hei

The Ami megatrends driver (at least for 471, 475, and 493) does not work with 2.4.x kernels.

The solution we got from Ami is to update the firmware of these cards to version FW G158. This update will fix all the problems with ami raid-devices in 2.4.x kernel without changing the driver.

We don't know when AMI will release a fixed firmware (hope soon) but we

got it by

Quoted 13 lines

e-mail. If there is anybody with the same problem I can sent the firmware-update by mail.

Sincerely
Rafael Martinez

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw

---Reply to mail from Venkatesh Ramamurthy about Solution - AMI megaraid driver doesn't work with Linux 2.4.x kernels

Quoted 3 lines

Can you provide the dmesg output of your system after loading the driver either successfully or unsucessfully.

Successfully: (Raid 5 4x18GB)
------------------------------------------------------
megaraid: v1.14g (Release Date: Feb 5, 2001; 11:42)
megaraid: found 0x101e:0x1960:idx 0:bus 9:slot 0:func 0 scsi3 : Found a MegaRAID controller at 0xf884e000, IRQ: 17 scsi3 : Enabling 64 bit support
megaraid: [G158:3.11] detected 1 logical drives
scsi3 : AMI MegaRAID G158 254 commands 16 targs 2 chans 40 luns
scsi3: scanning channel 1 for devices.
Vendor: ESG-SHV Model: SCA HSBP M9 Rev: 0.10
Type: Processor ANSI SCSI revision: 02
scsi3: scanning channel 2 for devices.
scsi3: scanning virtual channel for logical drives.
Vendor: MegaRAID Model: LD0 RAID5 52527R Rev: G158
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi disk sdb at scsi3, channel 2, id 0, lun 0 SCSI device sdb: 107575296 512-byte hdwr sectors (55079 MB)
sdb: sdb1
-------------------------------------------------------

When it was unsucessfully, it stoppet in the last line with:
sdb: unknown partition table
(With kernel 2.4.2-2smp from redhat (RH7.1) and "official" 2.4.2, 2.4.3)

The only different between the to instalations is the firmware version C158 --> G158 of the ami card.

The kernel is a 2.4.2-2smp from redhat (RH7.1). I will test the system with an "official" ;-) kernel today.

Rafael Martinez

---End reply