[ATrpms-devel] Re: IPW220 build problem
Fedor Pikus
fpikus at gmail.com
Thu Dec 1 22:17:42 CET 2005
On 12/1/05, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
>
> On Thu, Dec 01, 2005 at 09:05:16AM -0800, Fedor Pikus wrote:
> > On 12/1/05, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
> > >
> > > On Thu, Dec 01, 2005 at 12:04:09AM -0800, Fedor Pikus wrote:
> > > > I've had a hell of a time rebuilding ipw200 kernel modules for a new
> > > kernel:
> > > > the modules built, but would not load, I kept getting this message:
> > > >
> > > > ipw2200 disagrees about version of symbol <some ieee80211 symbol>
> > > >
> > > > In the end I found the problem: ipw2200 needs *.mod files from
> ieee80211
> > > > build and expects to find them in /usr/include/ieee80211.
> > > > If they are not found, an error message is issued but rpmbuild
> continues
> > > and
> > > > builds the package, only it'll use module versions from the kernel.
> > > > After copying *.mod from the build area for ieee80211, I built
> ipw2200
> > > > successfully.
> > > >
> > > > I think *.mod files should be included in some package, may be some
> > > > kmdl-devel to go with kmdl for ieee80211 (we'd need one for every
> > > version of
> > > > the kernel, right?). ipw2200 build should require that RPM and copy
> > > *.mod
> > > > from it instead of the shared location /usr/include/ieee80211. Or
> only
> > > one
> > > > kmdl-devel can be installed at any time and it uses the shared
> location.
> > > >
> > > > At the very least, the build should abort if files are not found,
> that
> > > error
> > > > message scrolls by really fast...
> > >
> > > I don't think that's the error that's hitting you. mod files are nice
> > > to have for every kmdl (not only ipw) since 2.6, but never broke any
> > > builds.
> > >
> > > Have you tried the kmdls at ATrpms.net for this kernel?
> >
> >
> > You mean the binary RPM? I can use it with the kernel it's built for,
> sure.
>
> Yes, please. That way you will know whether the build process is
> broken in general, or whether only that one build you made. This will
> decide what to do next.
I'm not sure what you want me to do: binary ipw2200 RPM from ATrpms works
perfectly as long as I use it with the kernel it's meant for (2.6.14-1637).
It will install into its own kernel tree, so my kernel (
2.6.14-1644-swsuspend2) won't even find that module. I can't manually insmod
it, kernel version is wrong.
As far as the build I made, it's consistent, I tried many times: if I build
ipw2200 with no mod files, it will make a module which seems to want to load
together with the ieee80211 module which comes with the kernel, not the one
I built from ieee80211 RPM (the new module is in
/lib/modules/<kver>/updates, the old one is in /lib/modules/<kver>/kernel,
and its version is in the source tree too).
If I build ipw2200 with mod files, it builds a module to work with ieee80211
which matches those mod files.
> But I was rebuilding all my kmdl's for a swsuspend-enabled kernel. I
> rebuilt
> > alsa amd ieee80211 SRPMs from ATRpms with no problems, but ipw2200 would
> > produce modules which would not load unless I had mod files available.
> >
> > I've found this bug report which may be relevant (symptoms are certainly
> the
> > same):
> >
> > http://lists.debian.org/debian-kernel/2005/11/msg00340.html
> --
> Axel.Thimm at ATrpms.net
>
>
>
--
Fedor G Pikus (fpikus at gmail.com)
http://www.pikus.net
http://wild-light.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20051201/7e10c7c5/attachment.html
More information about the atrpms-devel
mailing list