At Fri, 20 Jul 2007 13:19:55 +0930 Novensiles divi Flamen <[EMAIL PROTECTED]>
wrote:
> I used to have the modules load , which initiated the ipw3945d with an error
> that it can't start until runlevel three, then it worked perfectly once that
> runlevel was reached. Now it loads the module but
On Fri, 20 Jul 2007 12:38:12 Allan Gottlieb wrote:
> Sounds good. I assume you do *not* have ipw3945 in
> /etc/modules.autoload.d/kernel-2.6. If my guess is wrong, do you get
> the boot-time error message I mentioned (Failed to load ipw3945).
>
Your guess is correct, it is not in there.
> > My /
At Fri, 20 Jul 2007 12:05:27 +0930 Novensiles divi Flamen <[EMAIL PROTECTED]>
wrote:
> I have exactly the same laptop, with the wireless assigned to eth1. net.eth1
> is not run in any runlevel, but is launched from udev.
Sounds good. I assume you do *not* have ipw3945 in
/etc/modules.autoload.
On Fri, 20 Jul 2007 10:57:01 Allan Gottlieb wrote:
> What is the clean way to do this? Currently I am using the first
> method above and averting my eyes when the yellow star is to appear.
I have exactly the same laptop, with the wireless assigned to eth1. net.eth1
is not run in any runlevel, b
My laptop (inspiron 6400) has an intel 3945 wireless chip and hence I
use net-wireless/ipw3945{,d,-ucode}.
If I include ipw3945 in /etc/modules.autoload.d/kernel-2.6, I get an
error msg during boot
Failed to load ipw3945
However, everything works fine. Specifically, ifconfig shows that the
5 matches
Mail list logo
