| View previous topic :: View next topic |
| Author |
Message |
_tebra_
Guru
Joined: 12 Nov 2004
Posts: 304
Location: Brussels - Belgium
|
 Posted: Sun Jan 04, 2009 10:42 am Post subject: [network manager] wlan0 reconnue comme cablée (résolu) |
 |
|
Bonjour et bonne année à tous,
j'ai un problème avec mon wifi... Je suis passé d'un kernel 2.6.24 à un flambant neuf 2.6.27. Depuis "network manager" reconnaît mon interface wifi wlan0 comme une interface cablée et donc ne se connecte pas à mon réseau wifi.
Je sais me connecter en root à mon réseau wifi avec la commande "wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf" ce n'est donc pas un problème de modules manquant dans le kernel.
Petite bizaries: dans le cas d'une connection au wifi en root (via une console), seul cette console a acces à internet, le user pas.
PS: j'utilise network-manager v0.6.6 et mon interface wifi est une Broadcom 4311
Last edited by _tebra_ on Sun Jan 04, 2009 7:14 pm; edited 1 time in total |
|
| Back to top |
|
 |
_tebra_
Guru
Joined: 12 Nov 2004
Posts: 304
Location: Brussels - Belgium
|
| Posted: Sun Jan 04, 2009 1:30 pm Post subject: |
|
|
Pour plus d'info voici les infos du kernel au sujet de la Broadcom 4311
| Code: | [ 11.854970] b43-phy0: Broadcom 4311 WLAN found
[ 11.876503] phy0: Selected rate control algorithm 'pid'
[ 11.879037] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
[ 12.161132] nvidia: module license 'NVIDIA' taints kernel.
[ 12.423469] ACPI: PCI Interrupt Link [LK3E] enabled at IRQ 17
[ 12.423485] nvidia 0000:00:05.0: PCI INT A -> Link[LK3E] -> GSI 17 (level, high) -> IRQ 17
[ 12.423494] nvidia 0000:00:05.0: setting latency timer to 64
[ 12.423767] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 177.82 Tue Nov 4 16:50:05 PST 2008
[ 13.198410] EXT3 FS on sda6, internal journal
[ 14.015377] Adding 506036k swap on /dev/sda2. Priority:-1 extents:1 across:506036k
[ 27.088037] Clocksource tsc unstable (delta = 4398045693255 ns)
[ 27.425048] evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html
[ 37.282949] NET: Registered protocol family 10
[ 40.313724] eth0: no link during initialization.
[ 40.314712] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 40.345066] firmware: requesting b43/ucode5.fw
[ 40.426374] firmware: requesting b43/pcm5.fw
[ 40.449667] firmware: requesting b43/b0g0initvals5.fw
[ 40.457618] firmware: requesting b43/b0g0bsinitvals5.fw
[ 40.579059] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 40.687551] Registered led device: b43-phy0::tx
[ 40.689170] Registered led device: b43-phy0::rx
[ 40.707652] ADDRCONF(NETDEV_UP): wlan0: link is not ready |
Et voici ce que me donne iwconfig
| Code: | lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management: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 |
|
|
| Back to top |
|
|
_tebra_
Guru
Joined: 12 Nov 2004
Posts: 304
Location: Brussels - Belgium
|
| Posted: Sun Jan 04, 2009 6:31 pm Post subject: |
|
|
Je pense être sur une piste. Voici ce qu'il y a dans le /var/log/messages concernant NetworkManager
| Code: | Jan 4 17:37:38 Tebra-Laptop NetworkManager: <info> starting...
Jan 4 17:37:38 Tebra-Laptop NetworkManager: <debug> [1231087058.678155] GentooReadConfig(): Enabling DHCP for device eth0.
Jan 4 17:37:38 Tebra-Laptop NetworkManager: <debug> [1231087058.678265] GentooReadConfig(): Found hostname.
Jan 4 17:37:38 Tebra-Laptop NetworkManager: nm_ip4_config_set_hostname: assertion `config != NULL' failed
Jan 4 17:37:38 Tebra-Laptop NetworkManager: <info> eth0: Device is fully-supported using driver '(null)'.
Jan 4 17:37:38 Tebra-Laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Jan 4 17:37:38 Tebra-Laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Jan 4 17:37:38 Tebra-Laptop NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
Jan 4 17:37:38 Tebra-Laptop NetworkManager: <info> Deactivating device eth0.
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <debug> [1231087059.082096] GentooReadConfig(): Enabling DHCP for device wlan0.
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <debug> [1231087059.082391] GentooReadConfig(): Found hostname.
Jan 4 17:37:39 Tebra-Laptop NetworkManager: nm_ip4_config_set_hostname: assertion `config != NULL' failed
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <info> wlan0: Driver '(null)' does not support carrier detection. You must switch to it manually.
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <info> Now managing wired Ethernet (802.3) device 'wlan0'.
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <info> Deactivating device wlan0.
Jan 4 17:37:39 Tebra-Laptop NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link.
Jan 4 17:37:59 Tebra-Laptop NetworkManager: <info> Updating allowed wireless network lists. |
Le message "wlan0: Driver '(null)' does not support carrier detection. You must switch to it manually" a sûrement son importance mais je ne comprends vraiment son sens. |
|
| Back to top |
|
|
_tebra_
Guru
Joined: 12 Nov 2004
Posts: 304
Location: Brussels - Belgium
|
| Posted: Sun Jan 04, 2009 7:05 pm Post subject: |
|
|
| OK le Bug 246026 concerne mon problème il y a un patch mais il est pas encore dans l'arbre du portage. |
|
| Back to top |
|
|
|
French
