[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ipw3945/iwlwifi/iwl3945 users, please test latest davej kernels



[08.May.07 09:46 -0700] Tom London:
On 5/8/07, John W. Linville <linville redhat com> wrote:
I see a lot of "eth0" -- did you rename the interface?  By default
iwl3945 should have a name like "wlan0".

Don't know how that happened, but that seems to be the way it is...:

eth0      IEEE 802.11a  ESSID:""
         Mode:Managed  Frequency:5.18 GHz  Access Point: Not-Associated
         Retry min limit:7   RTS thr:off   Fragment thr=2346 B
         Encryption key:off
         Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth1      no wireless extensions.

I was running both iwlwifi and ipw3945 on the same kernel.  Perhaps
that got it 'renamed'.

I’ve also seen this happen after using iwlwifi.

After NM establishes connection this was logged:
| kernel: eth1: duplicate address detected!

And returning back to ipw3945 (due to suspend/shutdown problems) interface was renamed to eth0 once and then to devXXXX.

Also after NetworkManager’s INTERFACE_ADD commands, wpa_supplicant’s logged responses were strange:
| NetworkManager: <info>  SUP: response was '@d�'
| NetworkManager: <info>  SUP: response was '`d�'
| NetworkManager: <info>  SUP: response was '`d�'
| NetworkManager: <info>  SUP: response was '�'
| NetworkManager: <info>  SUP: response was 'Hd�'
| NetworkManager: <info>  SUP: response was 'Hd�'
| NetworkManager: <info>  SUP: response was '�d�'

On the other hand I didn’t have any connection/association problems with 3139 and 3142 kernel.

--
~sertaç


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]