On Mon, Mar 24, 2003 at 06:17:03PM +0100, Dominik Brodowski wrote:
> OK, understanding more and more of the problem:
>
> Firstly, though: is all compiled as modules?
Yes indeed.
> If not, it's really strange, as
> I use the same driver locally, but built into the kernel. This is what I'd
> recommend for cs.o, ds.o and pci-socket.o/yenta.o anyways.
[...]
> So, I'd suggest you do one of these two things:
> a) modify the process done by modprobe to load the modules in the following
> order:
> - cs.ko
cs.ko doesn't exist, it is part of pcmcia_core here.
> - pci-socket.ko/yenta.ko
> - ds.ko
> - pcnet_cs.ko
Actually this is using the RedHat standard way: /etc/init.d/pcmcia
loads, in order pcmcia_core, yenta.
pcnet_cs get loaded by hotplug, triggered by one of the above modules.
So it seems that what you want is that I disable hotplugging and
loading pcnet_cs by hand later... Hmmm.
> _or_ b) compile cs.ko / pci-socket.ko/yenta.ko into the kernel
>
> until I get a proper fix for this problem.
Sure, I'll try that.
> The requirement of having to load
> the socket drivers before ds.ko will be removed soon... that patch is
> already in my queue somewhere (and will remove the issue you're seeing
> almost surely), but depends on some other stuff. But maybe I can split the
> decisive things out sooner, let's see...
Stelian.
-- Stelian Pop <stelian.pop@fr.alcove.com> Alcove - http://www.alcove.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:16 EST