Pasi Kärkkäinen wrote:
On Fri, Jun 16, 2006 at 11:58:19AM +0100, Paul Howarth wrote:
Pasi Kärkkäinen wrote:
On Fri, Jun 16, 2006 at 08:35:03AM +0100, Paul Howarth wrote:
On Fri, 2006-06-16 at 00:00 +0300, Pasi Kärkkäinen wrote:
Hi!
I'm trying to build Qlogic qla4xxx HBA driver (floppy dd image) for FC5,
using
ddiskit 0.9.5.
I've successfully built the dd image for 2.6.15-1.2054_FC5 and
2.6.15-1.2054_FC5smp
kernels. I had to manually add "modules.pcimap" and "pci.ids" files to
the
generated image.. otherwise the FC5 installer complained that those files
are missing from the dd image.
When I boot FC5 CD with "linux dd", and try to load the driver disk, the
installer doesn't load the driver.. If I try to load the driver manually
with insmod (when in the installer) I get:
qla4xxx: disagrees about version of symbol struct_module
modinfo says:
"vermagic: 2.6.15-1.2054_FC5 686 REGPARM 4KSTACKS gcc-4.1"
Is that correct? Looks like correct to me..
Is there something special compilation flags or something that I should
be
using.. ?
Did you build the module for the i586 kernel or the i686 kernel? The
installer uses the i586 kernel.
No, I only built for i686 because "uname -a" says i686 during the
installer.. oh well, my bad.
I added the i586 build of the driver, but for some reason the installer
doesn't like the dd image..
Installer still says "No devices of the appropriate type were found on this
driver disk."
VC 3 (debug) says:
INFO : modules to insert
INFO : load module set done
What does that mean? It doesn't even try to load the module? Something
missing from my dd image.. ?
Same kind of self made dd image works with CentOS 4.2 / 4.3 installers..
Has the format/layout of the dd images changed?
There was a driver disk format change quite a while back back, but I'd
have thought that CentOS 4.x would be using the new format. What's the
directory hierarchy you have?
I used to make driver disks for my old Advnsys SCSI card but that's been
included in the installer kernel for FC5 :-)
What I had for FC1, FC3, and FC4 was:
# ls -l
total 684
-rw-r--r-- 1 paul paul 48 Aug 16 2004 modinfo
-rw-r--r-- 1 paul paul 648561 Jun 20 2005 modules.cgz
-rw-r--r-- 1 paul paul 19 Aug 13 2004 modules.dep
-rw-r--r-- 1 paul paul 392 May 18 2005 modules.pcimap
-rw-r--r-- 1 paul paul 281 Aug 13 2004 pcitable
-rw-r--r-- 1 paul paul 21 Aug 13 2004 rhdd
# cat rhdd
Advansys Driver Disk
# cat modinfo
Version 0
advansys
scsi
"Advansys SCSI Cards"
# cat modules.dep
advansys: scsi_mod
The moduleball was structured like this:
# ls -l 2*/*/*
-rwxr--r-- 1 root root 101164 Sep 24 2004
2.4.22-1.2115.nptl/athlon/advansys.o
-rwxr--r-- 1 root root 94204 Sep 24 2004
2.4.22-1.2115.nptlBOOT/i386/advansys.o
-rwxr--r-- 1 root root 98636 Sep 24 2004
2.4.22-1.2115.nptl/i586/advansys.o
-rwxr--r-- 1 root root 102412 Sep 24 2004
2.4.22-1.2115.nptl/i686/advansys.o
-rwxr--r-- 1 root root 101832 Sep 24 2004
2.4.22-1.2115.nptlsmp/athlon/advansys.o
-rwxr--r-- 1 root root 103176 Sep 24 2004
2.4.22-1.2115.nptlsmp/i686/advansys.o
-rwxr--r-- 1 paul paul 105488 Jun 3 2005
2.6.11-1.1369_FC4/i586/advansys.ko
-rwxr--r-- 1 paul paul 103848 Jun 3 2005
2.6.11-1.1369_FC4/i686/advansys.ko
-rwxr--r-- 1 paul paul 105468 Jun 3 2005
2.6.11-1.1369_FC4smp/i686/advansys.ko
-rwxr--r-- 1 root root 92680 Nov 12 2004 2.6.9-1.667/i586/advansys.ko
-rwxr--r-- 1 root root 93832 Nov 12 2004 2.6.9-1.667/i686/advansys.ko
-rwxr--r-- 1 root root 91720 Nov 12 2004 2.6.9-1.667smp/i586/advansys.ko
-rwxr--r-- 1 root root 96048 Nov 12 2004 2.6.9-1.667smp/i686/advansys.ko
Hmm.. all of my files in the dd image look correct.
In addition to the files above, I also have "pci.ids" file.
FC5 installer will give
"ERROR failed to open /tmp/drivers/pci.ids: No such file or directory"
error if I don't have that file on the dd image.
"pci.ids", "pcitable" and "modules.pcimap" contain correct pci/device ids
(verified with lspci - and those files are taken from "official" qlogic rhel4
qla4xxx dd image)
$ ls -l
total 593
-rwxr-xr-x 1 root root 85 Jun 15 14:22 modinfo
-rwxr-xr-x 1 root root 603405 Jun 16 12:48 modules.cgz
-rwxr-xr-x 1 root root 35 Jun 15 13:25 modules.dep
-rwxr-xr-x 1 root root 273 Jun 15 13:34 modules.pcimap
-rwxr-xr-x 1 root root 106 Jun 19 11:22 pci.ids
-rwxr-xr-x 1 root root 192 Jun 15 13:25 pcitable
-rwxr-xr-x 1 root root 41 Jun 15 13:27 rhdd
$ cat modinfo
Version 0
qla4xxx
scsi
"Updated qla4xxx driver (5.00.04-d5) for 2.6.15-1.2054_FC5"
$ cat modules.dep
qla4xxx: scsi_mod
sd_mod: scsi_mod
$ cat modules.pcimap
qla4xxx 0x00001077 0x00004010 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
qla4xxx 0x00001077 0x00004022 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
qla4xxx 0x00001077 0x00004000 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
$ cat pci.ids
1077 QLogic Corp.
4010 QLA4010 iSCSI Adapter
4022 QLA4022 iSCSI Adapter
4000 QLA4000 iSCSI Adapter
$ cat pcitable
0x1077 0x4000 "qla4xxx" "QLogic Corp.|QLA4000 iSCSI-AL Adapter"
0x1077 0x4010 "qla4xxx" "QLogic Corp.|QLA4010 iSCSI-AL Adapter"
0x1077 0x4022 "qla4xxx" "QLogic Corp.|QLA4022 iSCSI-AL Adapter"
$ cat rhdd
Fedora Core 5 qla4xxx driver update disk
modules.cgz:
$ ls -l 2*/*/*
-rw-r--r-- 1 root root 1325007 Jun 19 11:39 2.6.15-1.2054_FC5/i586/qla4xxx.ko
-rw-r--r-- 1 root root 168288 Jun 19 11:39 2.6.15-1.2054_FC5/i686/qla4xxx.ko
-rw-r--r-- 1 root root 173628 Jun 19 11:39 2.6.15-1.2054_FC5smp/i686/qla4xxx.ko
fs of the dd image is vfat. FC5 installer didn't seem to like ext2.
Hmm.. that i586 module seems to be a lot bigger than the i686 versions..
i586 version is compiled by hand, i686 versions are compiled automatically
by ddiskit.
ddiskit probably strips the module.
Try: strip -g 2.6.15-1.2054_FC5/i586/qla4xxx.ko
But anyway, FC5 installer doesn't like this image. It starts to read the
floppy ("Reading driver disk"), but it won't load the module. No errors in the VC3.
In VC3 I see only this:
"INFO trying to mount sdb"
"INFO modules to insert"
"INFO load module set done"
When I manually extract the i586 qla4xxx.ko from the dd image, I can load it
fine with insmod..
Any ideas? For some reason the installer doesn't even try to load the
qla4xxx module..
Are you sure your actual hardware matches one of the PCI IDs listed?
What's the output of "lspci -n"?
Paul.
