Bug 251823 – net-misc/networkmanager-0.6.6 does not recognize iwl3945 interface as wireless

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Stephen Cavilia 2008-12-21 07:57:56 UTC]

I have an intel 3945 wireless card using the iwl3945 driver (eth1). When I start networkmanager, it thinks this device is a wired network and does not allow wireless configuration for it.

Dec 21 01:10:11 kwyjibo NetworkManager: <info>  starting...
Dec 21 01:10:11 kwyjibo NetworkManager: <info>  Found radio killswitch /org/free
desktop/Hal/devices/ipw_wlan_switch
Dec 21 01:10:11 kwyjibo NetworkManager: <debug> [1229839811.615081] GentooReadCo
nfig(): Enabling DHCP for device eth1.
Dec 21 01:10:11 kwyjibo NetworkManager: <debug> [1229839811.623355] GentooReadCo
nfig(): Found hostname.
Dec 21 01:10:11 kwyjibo NetworkManager: nm_ip4_config_set_hostname: assertion `c
onfig != NULL' failed
Dec 21 01:10:11 kwyjibo NetworkManager: <info>  eth1: Driver '(null)' does not s
upport carrier detection.       You must switch to it manually.
Dec 21 01:10:11 kwyjibo NetworkManager: <info>  nm_device_init(): waiting for de
vice's worker thread to start
Dec 21 01:10:11 kwyjibo NetworkManager: <info>  nm_device_init(): device's worke
r thread started, continuing.
Dec 21 01:10:11 kwyjibo NetworkManager: <info>  Now managing wired Ethernet (802
.3) device 'eth1'.


Also, can networkmanager be configured to use resolvconf for handling dns servers instead of insisting on rewriting resolv.conf itself?

Reproducible: Always

Steps to Reproduce:
1. Have an intel wireless 3945 card
2. install iwl3945 driver
3. /etc/init.d/NetworkManager start
Actual Results:  
networkmanager thinks eth1 is wired

Expected Results:  
networkmanager thinks eth1 is wireless

[Comment 1 Stephen Cavilia 2008-12-21 08:07:10 UTC]

using networkmanager version 0.6.6 by the way

[Comment 2 Jeroen Roovers (RETIRED) 2008-12-23 17:08:43 UTC]

(In reply to comment #1)
> using networkmanager version 0.6.6 by the way

It's net-misc/networkmanager, btw...

[Comment 3 Jeroen Roovers (RETIRED) 2008-12-23 17:10:05 UTC]

Please post your `emerge --info' too.

[Comment 4 Stephen Cavilia 2008-12-23 18:55:24 UTC]

Created attachment 176248 [details]
emerge --info

[Comment 5 Stephen Cavilia 2008-12-23 18:56:20 UTC]

Created attachment 176249 [details]
hal info for network interface, 2.6.27 with cfg80211

[Comment 6 Stephen Cavilia 2008-12-23 18:57:07 UTC]

Created attachment 176250 [details]
hal info on 2.6.25, no cfg80211

[Comment 7 Stephen Cavilia 2008-12-23 19:08:49 UTC]

Someone on freenode #nm suggested hal may not be telling nm the interface is wireless capable, so I think the problem is not in nm but in hal, specifically it's not getting the right information from the kernel when the cfg80211 system is enabled.  I looked at hald/linux/device.c on hal's git server; there's a section about cfg80211 on master that seems to have been added since the last release (0.5.11)

[Comment 8 Wormo (RETIRED) 2008-12-24 17:51:13 UTC]

This looks like a familiar hal issue -- can you try the patch in bug 246026? Let us know if you need instructions on applying it in a local overlay.

[Comment 9 Panagiotis Christopoulos (RETIRED) 2008-12-25 10:58:32 UTC]

(In reply to comment #8)
> This looks like a familiar hal issue -- can you try the patch in bug 246026?
> Let us know if you need instructions on applying it in a local overlay.
> 

I resolve the bug as TEST-REQUEST. Reply here after testing the patch of bug 246026. Please, reopen if there are still issues here.

[Comment 10 Stephen Cavilia 2008-12-26 22:18:41 UTC]

looks like a duplicate of 264026, i'll try that patch when i get a chance