The ipw3945d-1.7.22 ebuild fails to copy the necessary modules.d file. This is not strange considering the fact that it does a newins "${FILESDIR}"/${P}-modprobe.conf ${PN}, and the files directory only contains ipw3945d-1.7.18-modprobe.conf.
Fixed in CVS, sorry for the inconvenience.
Even with the modules.d file ipw3945d does not start automatically for me, it never has for the two months or so I am using it now. I have to start it manually.
Actually me too. I've had my dell for about 2 months, and I've got in my /etc/conf.d/local.start file: rmmod ipw3945 modprobe ipw3945 And that makes things work. Otherwise, when udev/coldplug detects the device, it never connects. Perhaps we should file a separate bug though.
(In reply to comment #3) > Actually me too. I've had my dell for about 2 months, and I've got in my > /etc/conf.d/local.start file: > > rmmod ipw3945 > modprobe ipw3945 > > > And that makes things work. Otherwise, when udev/coldplug detects the device, > it never connects. Perhaps we should file a separate bug though. > The problem is that coldplug "comes up" before "modules.conf" is being generated from the modules.d (and other) content. I would consider this as a bug.
ok, people, let's take this discussion to bug #142560 instead. I've added the two of you to cc there.
