Re: Creating dd (driver disk) for FC5, installer "disagrees about version of symbol struct_module"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


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? 

I tried loading the driver manually during the installer.. by going to VC2,
mounting the dd floppy, extracting the modules.cgz and loading the module
from i586 directory.. and it loads fine!

Any ideas how to debug this further? 

And thanks for your reply!

-- Pasi
                                .     .
                              /    -    \

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux