Description of problem:
Installer cannot detect disks connected to Promise SuperTrak EX
series adapter (EX4350, EX8350, etc.) driven by stex.ko.
- modules.cgz and pci.ids in initrd.img of the installer don't contain
stex.ko and entries for the stex adapters, respectively.
On the other hand, kernel package contains the driver and
hwdata package contains proper pci.ids file.
- anaconda/loader2/module-info doesn't have an entry for "stex".
So it looks this is a problem of anaconda or installer image.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to install to the disks connected to Promise EX4350 or EX8350
Installation fails due to the absense of installable disk drive
Disks should be detected
# grep 8350 /usr/share/hwdata/pci.ids
8350 80333 [SuperTrak EX8350/EX16350], 80331 [SuperTrak EX8300/EX16300]
# grep 8350 /lib/modules/2.6.9-48.EL/modules.pcimap
stex 0x0000105a 0x00008350 0xffffffff 0xffffffff 0x00000000
# ls -l /lib/modules/2.6.9-48.EL/kernel/drivers/scsi/stex.ko
-rwxr--r-- 1 root root 28072 Feb 13 12:39
# modinfo /lib/modules/2.6.9-48.EL/kernel/drivers/scsi/stex.ko
version: 126.96.36.199 338F79082A7D490A2B57033
description: Promise Technology SuperTrak EX Controllers
author: Ed Lin
vermagic: 2.6.9-48.EL gcc-3.4
# zcat isolinux/initrd.img > initrd
# mount initrd /mnt/0
# zcat /mnt/0/modules/modules.cgz |cpio -t|grep stex
# grep 8350 /mnt/0/modules/pci.ids
RHEL5 anaconda contains the following entry in module-info:
"Promise SuperTrak EX"
and the installer can detect the device.
*** Bug 234229 has been marked as a duplicate of this bug. ***
The decision in the RHEL meeting was to commit the patch to CVS and include it
in 4.5 *ONLY* if we have to respin anaconda prior to 4.5 GA. Using driver disks
would be the workaround until it would come out in 4.6
anaconda has not been respun. moving to 4.6 so this is not closed.
Requesting SEG to create driver disk based off 5.1 kernel and for Engineering to
commit to including anaconda support in 4.6.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.