Re: [pcmcia-problem] kernel-image-2.4.20-bf2.4 -5
#include <hallo.h>
* Brian Mays [Thu, Mar 20 2003, 04:13:29PM]:
> Eduard Bloch <edi@gmx.de> wrote:
>
> > Nothing relevant. It is pure 2.4.20 build from Herbert's kernle-source
> > package. But we use Woody's version of pcmcia-source because it is for
> > stable, ...
>
> That's strange, because it doesn't explain the version numbers reported
> in the other email.
Wait, the log messages are from WOLK, but are almost identical with
those I got from 2.4.20-bf2.4
> > ... and because the Sid version refuses to build anything if pcmcia in
> > kernel has been enabled.
>
> You can override this by setting the following environment variable:
>
> FORCE_CONFIG_PCMCIA=y
>
> This is an undocumented feature intended for building Debian packages,
> when it is necessary to override the default behavior and it is assumed
> that the person building the package knows what he is doing. This trick
> is undocumented, because I don't want users doing this. Building two
> sets of modules with the same names leads to problems, like the one
> discussed here.
I see.
> > > One way to fix this would be to use insmod to explicitly load the
> > > correct drivers, or to delete the orinoco and hermes drivers under
> > > the kernel subdirectory and run depmod. The real problem is that
> > > there should not be two modules with the same name.
> >
> > I think I will workaround by removing the kernel versions from the
> > drivers tarball on boot-floppies. Any objections?
>
> I think that will work.
The only thing I do not like is that inocent drivers that share the code
like orinoco_pci driver have to go too.
Gruss/Regards,
Eduard.
--
Zwei Knaben gingen durch das Korn
der eine hinten, der and're vorn
keiner ging in der Mitte
folglich fehlte der dritte.
Reply to: