At Wed, 22 Aug 2007 11:15:12 +0200 Christian <[EMAIL PROTECTED]> wrote:

> I have the same wireless lan card and I have no problems with
> my installation.

Your soln does not work for me, but we do have differences (see below)

What does work is when I BOTH autoload ipw3945 and have ip23945d in
the boot runlevel (the first fails, but seems necessary for the second
to succeed).

> I am using gentoo-sources-2.6.22-r2 and activated the following
> option in the kernel:

I am behind here using 2.6.20-gentoo-r7.  Perhaps this is the difficulty.

> Networking  --->
>    [*] Networking support
>         Wireless  ---> 
>             <M> Improved wireless configuration API
>             --- Wireless extensions
>             < > Generic IEEE 802.11 Networking Stack (mac80211)

The above 4 do not seem to exist

>             <M> Generic IEEE 802.11 Networking Stack
>             [ ]   Enable full debugging output
>             <M>   IEEE 802.11 WEP encryption (802.1x)
>             <M>   IEEE 802.11i CCMP support
>             <M>   IEEE 802.11i TKIP encryption
>             < >   Software MAC add-on to the IEEE 802.11 networking stack

The same four that you have as modules, I have built in to the kernel.

> The following package I have installed:

I have the same versions as you of these three ipw3945 packages.

>
> Few days ago, I had some problems while booting my system caused by udev. 
> After updating udev to version 114 the problems are gone.

I also run version 114

> So, I don't load the kernel module explizit and I do not start the daemon 
> automatically in one runlevel.

I just now tried this and the following error occurs.

Aug 22 09:18:12 ajglap dhcpcd[5247]: eth1: received SIGTERM, stopping
Aug 22 09:18:12 ajglap dhcpcd[5247]: eth1: removing default route via 
192.168.1.1 metric 2000
Aug 22 09:18:12 ajglap dhcpcd[5247]: eth1: deleting IP address 192.168.1.100/24
Aug 22 09:18:12 ajglap dhcpcd[5247]: eth1: exiting
Aug 22 09:51:53 ajglap rc-scripts: network interface eth1 does not exist

> In my case, it seems to be done by udev.
>
> I also have written a script to start/stop wireless lan manually.

I read your message as saying that without the script, the wireless
lan would start automatically.  This does not happen for me.

> I hope these information may help you.

Indeed, quite helpful.  When I upgrade the kernel, which you may have
inspired me to do right now, I will remove both the autoload and
daemon start in the boot runlevel.

Thanks,
allan
-- 
[EMAIL PROTECTED] mailing list

Reply via email to