Scheda wifi Broadcom

[psimem]

Ho un problema con la scheda wifi del portatile:

$ lspci | grep WLAN
BroadcomCorporation BCM4311 802.11b/g WLAN (rev 01)

Ho installato Mepis 11 con kernel 2.6.36: tutto funziona senza toccare nulla ed il modulo usato e' b43 (non il broadcom) come confermato da un rapido "$lsmod | grep b43".
Ho provato a connettermi ad un hotspot (il mio cell) e tutto ok.
Il problema sorge quando decido di installare su un'altra partizione debian wheezy con kernel 3.0.0; seguendo il wiki debian installo "firmware-b43-installer" e fino a qui tutto ok.
Il classico "$lsmod | grep b43" mi conferma l'avvenuto caricamento del modulo e un "#iwconfig" mi dice che l'interfaccia e' stata creata.
Tento di riaccedere allo stesso hotspot e nada, l'interfaccia grafica (networ-manager-kde con relativa applet) mi dice "Waiting authentication" fino a che decide di averne abbastanza ed uccide la connessione.
Per inciso l'hotspot viene rilevato correttamente.

Da cosa puo' dipendere? Possibile che sia il kernel? Oppure la versione del pacchetto "firmware-b43-install" (debian 1:015-3 - mepis 4.150.10.5-4)?

PS: perche' non uso mepis? Perche' debian e' debian e mepis (montaggio device, personalizzazione impostazioni, ecc) non la digerisco tanto .

[sacarde]

oppure prova il modulo: b43legacy

oppure : http://www.broadcom.com/support/802.11/linux_sta.php

[Freaxxx]

consulta questo sito http://kmuto.jp/debian/hcl/

[psimem]

Provato con il driver b43legacy che non dovrebbe essere il suo ed infatti non funziona (messo in blacklist b43 b44).
Provato anche con il driver wl (sempre da repository), che da quanto posso capire da questa pagina dovrebbe dare piu' svantaggi che vantaggi ma niente (messo in blacklist b43 b44 ssb).

Non appena ho il portatile sottomano provero' a vedere cosa suggerisce il sito postato da freaxxx.

Magari provo a vedere che versione del modulo b43 usa mepis e la confronto con quella usata da wheezy.

Nel frattempo, qualcuno puo' darmi il link od il nome di una pennetta wifi usb che sia compatibile al 100% con linux? Vorrei montarla su un fisso ed altrettanto evitare di fare la stessa fine del portatile .

[sacarde]

ma! certo che se il device lo crea.....


bo



- controlla il firmware
- quando tenti di connetterti da: dmesg vedi errori?

[psimem]

Esattamente in dmesg cosa dovrei cercare?

-----------------------------------------------------------
Wheezy:
Relativamente al modulo b43 ho trovato solo:

psimem@debian:~$ dmesg | grep b43
[    4.564312] b43-pci-bridge 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.564326] b43-pci-bridge 0000:02:00.0: setting latency timer to 64
[    4.964997] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[    5.062068] Registered led device: b43-phy0::tx
[    5.062092] Registered led device: b43-phy0::rx
[    5.062119] Registered led device: b43-phy0::radio
[  11.256053] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)

Info riguardo al modulo b43:

root@debian:/home/psimem# modinfo b43
filename:       /lib/modules/3.0.0-1-486/kernel/drivers/net/wireless/b43/b43.ko
firmware:       b43/ucode9.fw
firmware:       b43/ucode5.fw
firmware:       b43/ucode16_mimo.fw
firmware:       b43/ucode15.fw
firmware:       b43/ucode14.fw
firmware:       b43/ucode13.fw
firmware:       b43/ucode11.fw
firmware:       FW13
license:        GPL
author:         Gábor Stefanik
author:         Michael Buesch
author:         Stefano Brivio
author:         Martin Langer
description:    Broadcom B43 wireless driver
alias:          pcmcia:m02D0c0476f*fn*pfn*pa*pb*pc*pd*
alias:          pcmcia:m02D0c0448f*fn*pfn*pa*pb*pc*pd*
alias:          ssb:v4243id0812rev10*
alias:          ssb:v4243id0812rev0F*
alias:          ssb:v4243id0812rev0D*
alias:          ssb:v4243id0812rev0C*
alias:          ssb:v4243id0812rev0B*
alias:          ssb:v4243id0812rev0A*
alias:          ssb:v4243id0812rev09*
alias:          ssb:v4243id0812rev07*
alias:          ssb:v4243id0812rev06*
alias:          ssb:v4243id0812rev05*
depends:        ssb,pcmcia,mac80211,mmc_core,cfg80211,rng-core
intree:         Y
vermagic:       3.0.0-1-486 mod_unload modversions 486 
parm:           bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int)
parm:           fwpostfix:Postfix for the .fw files to load. (string)
parm:           hwpctl:Enable hardware-side power control (default off) (int)
parm:           nohwcrypt:Disable hardware encryption. (int)
parm:           hwtkip:Enable hardware tkip. (int)
parm:           qos:Enable QOS support (default on) (int)
parm:           btcoex:Enable Bluetooth coexistence (default on) (int)
parm:           verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug (int)
parm:           pio:Use PIO accesses by default: 0=DMA, 1=PIO (int)

-----------------------------------------------------------
Mepis:

psimem@mepis1:~$ dmesg | grep b43
[    5.366850] b43-pci-bridge 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    5.370782] b43-pci-bridge 0000:02:00.0: setting latency timer to 64
[    6.062427] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[    6.212369] Registered led device: b43-phy0::tx
[    6.212391] Registered led device: b43-phy0::rx
[    6.212412] Registered led device: b43-phy0::radio
[   14.952051] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)

[root@mepis1 psimem]# modinfo b43
filename:       /lib/modules/2.6.36-1-mepis-smp/kernel/drivers/net/wireless/b43/b43.ko
firmware:       b43/ucode9.fw
firmware:       b43/ucode5.fw
firmware:       b43/ucode15.fw
firmware:       b43/ucode14.fw
firmware:       b43/ucode13.fw
firmware:       b43/ucode11.fw
firmware:       FW13
license:        GPL
author:         G�bor Stefanik
author:         Michael Buesch
author:         Stefano Brivio
author:         Martin Langer
description:    Broadcom B43 wireless driver
alias:          pcmcia:m02D0c0476f*fn*pfn*pa*pb*pc*pd*
alias:          pcmcia:m02D0c0448f*fn*pfn*pa*pb*pc*pd*
alias:          ssb:v4243id0812rev10*
alias:          ssb:v4243id0812rev0F*
alias:          ssb:v4243id0812rev0D*
alias:          ssb:v4243id0812rev0C*
alias:          ssb:v4243id0812rev0B*
alias:          ssb:v4243id0812rev0A*
alias:          ssb:v4243id0812rev09*
alias:          ssb:v4243id0812rev07*
alias:          ssb:v4243id0812rev06*
alias:          ssb:v4243id0812rev05*
depends:        ssb,mac80211,led-class,pcmcia,mmc_core,cfg80211,rng-core
vermagic:       2.6.36-1-mepis-smp SMP mod_unload modversions 686 
parm:           bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int)                                                                                               
parm:           fwpostfix:Postfix for the .fw files to load. (string)                                                                                                               
parm:           hwpctl:Enable hardware-side power control (default off) (int)                                                                                                       
parm:           nohwcrypt:Disable hardware encryption. (int)                                                                                                                        
parm:           hwtkip:Enable hardware tkip. (int)                                                                                                                                  
parm:           qos:Enable QOS support (default on) (int)                                                                                                                           
parm:           btcoex:Enable Bluetooth coexistence (default on) (int)
parm:           verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug (int)
parm:           pio:Use PIO accesses by default: 0=DMA, 1=PIO (int)

-----------------------------------------------------------

La differenza che noto e' che in Wheezy viene usato il firmware 508.1084, mentre im mepis 410.2160.

Inoltre cercando qualche traccia nei log ho trovato questo in /var/syslog al momento in cui tento la connessione:

Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0) starting connection 'MB525 6023'
Nov  1 15:11:04 debian NetworkManager[1169]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov  1 15:11:04 debian NetworkManager[1169]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0/wireless): connection 'MB525 6023' requires no security.  No secrets needed.
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Config: added 'ssid' value 'MB525 6023'
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Config: added 'scan_ssid' value '1'
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Config: added 'key_mgmt' value 'NONE'
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov  1 15:11:04 debian NetworkManager[1169]: <info> Config: set interface ap_scan to 1
Nov  1 15:11:04 debian NetworkManager[1169]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Nov  1 15:11:05 debian wpa_supplicant[1248]: Trying to authenticate with f8:7b:7a:99:72:45 (SSID='MB525 6023' freq=2437 MHz)
Nov  1 15:11:05 debian NetworkManager[1169]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov  1 15:11:05 debian kernel: [ 1058.756732] wlan0: direct probe to f8:7b:7a:99:72:45 (try 1/3)
Nov  1 15:11:05 debian kernel: [ 1058.956047] wlan0: direct probe to f8:7b:7a:99:72:45 (try 2/3)
Nov  1 15:11:05 debian kernel: [ 1059.157067] wlan0: direct probe to f8:7b:7a:99:72:45 (try 3/3)
Nov  1 15:11:05 debian kernel: [ 1059.356048] wlan0: direct probe to f8:7b:7a:99:72:45 timed out
Nov  1 15:11:12 debian wpa_supplicant[1248]: Trying to authenticate with f8:7b:7a:99:72:45 (SSID='MB525 6023' freq=2437 MHz)
Nov  1 15:11:12 debian kernel: [ 1065.664115] wlan0: direct probe to f8:7b:7a:99:72:45 (try 1/3)
Nov  1 15:11:12 debian kernel: [ 1065.864063] wlan0: direct probe to f8:7b:7a:99:72:45 (try 2/3)
Nov  1 15:11:12 debian kernel: [ 1066.064043] wlan0: direct probe to f8:7b:7a:99:72:45 (try 3/3)
Nov  1 15:11:12 debian kernel: [ 1066.264059] wlan0: direct probe to f8:7b:7a:99:72:45 timed out
Nov  1 15:11:19 debian wpa_supplicant[1248]: Trying to authenticate with f8:7b:7a:99:72:45 (SSID='MB525 6023' freq=2437 MHz)
Nov  1 15:11:19 debian kernel: [ 1072.576115] wlan0: direct probe to f8:7b:7a:99:72:45 (try 1/3)
Nov  1 15:11:19 debian kernel: [ 1072.776056] wlan0: direct probe to f8:7b:7a:99:72:45 (try 2/3)
Nov  1 15:11:19 debian kernel: [ 1072.976062] wlan0: direct probe to f8:7b:7a:99:72:45 (try 3/3)
Nov  1 15:11:19 debian kernel: [ 1073.176060] wlan0: direct probe to f8:7b:7a:99:72:45 timed out
Nov  1 15:11:26 debian wpa_supplicant[1248]: Trying to authenticate with f8:7b:7a:99:72:45 (SSID='MB525 6023' freq=2437 MHz)
Nov  1 15:11:26 debian kernel: [ 1079.488115] wlan0: direct probe to f8:7b:7a:99:72:45 (try 1/3)
Nov  1 15:11:26 debian kernel: [ 1079.688053] wlan0: direct probe to f8:7b:7a:99:72:45 (try 2/3)
Nov  1 15:11:26 debian kernel: [ 1079.888070] wlan0: direct probe to f8:7b:7a:99:72:45 (try 3/3)
Nov  1 15:11:26 debian kernel: [ 1080.088070] wlan0: direct probe to f8:7b:7a:99:72:45 timed out
Nov  1 15:11:29 debian NetworkManager[1169]: <warn> Activation (wlan0/wireless): association took too long, failing activation.
Nov  1 15:11:29 debian NetworkManager[1169]: <info> (wlan0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Nov  1 15:11:29 debian NetworkManager[1169]: <warn> Activation (wlan0) failed for access point (MB525 6023)
Nov  1 15:11:29 debian NetworkManager[1169]: <warn> Activation (wlan0) failed.
Nov  1 15:11:29 debian NetworkManager[1169]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Nov  1 15:11:29 debian NetworkManager[1169]: <info> (wlan0): deactivating device (reason: 0).
Nov  1 15:11:29 debian NetworkManager[1169]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Nov  1 15:11:29 debian NetworkManager[1169]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.

Da quel che mi sembra di capire non si connette gia' dalla prima fase .

Adesso se volessi fare una prova comparativa come posso sotituire il firmware 510 con il 408?


Ops, ho dimenticato l'output di dmesg:

[ 1593.908937] wlan0: direct probe to f8:7b:7a:99:72:45 (try 1/3)
[ 1594.108043] wlan0: direct probe to f8:7b:7a:99:72:45 (try 2/3)
[ 1594.308067] wlan0: direct probe to f8:7b:7a:99:72:45 (try 3/3)
[ 1594.508061] wlan0: direct probe to f8:7b:7a:99:72:45 timed out
[ 1600.820114] wlan0: direct probe to f8:7b:7a:99:72:45 (try 1/3)
[ 1601.020067] wlan0: direct probe to f8:7b:7a:99:72:45 (try 2/3)
[ 1601.220073] wlan0: direct probe to f8:7b:7a:99:72:45 (try 3/3)
[ 1601.420088] wlan0: direct probe to f8:7b:7a:99:72:45 timed out
[ 1607.728114] wlan0: direct probe to f8:7b:7a:99:72:45 (try 1/3)
[ 1607.928052] wlan0: direct probe to f8:7b:7a:99:72:45 (try 2/3)
[ 1608.128247] wlan0: direct probe to f8:7b:7a:99:72:45 (try 3/3)
[ 1608.328045] wlan0: direct probe to f8:7b:7a:99:72:45 timed out

[sacarde]

il firmware va di pari passo con l'aggiornamento del modulo del kernel




io proverei a configurare a mano:

iwconfig wlan0 ESSID .......

e poi:

dhclient wlan0

[psimem]

Ehm non sono molto pratico di reti, il primo comando assegna l'ESSID (che sarebbe il nome dell'hotspot?) all'interfaccia wireless, giusto?
Ed il secondo tenta di configurare l'interfaccia con il dhc?

[sacarde]

- si.... comunque sono dati (essid + key) che hai, se con mepis funziona

- si se hai il dhcp attivo



p.s.
letto?
http://guide.debianizzati.org/index....configurazione

[psimem]

Rieccomi: allora dando il comando

root@debian:/home/psimem# iwconfig wlan0 essid MB5256023

non ci sono errori.

Invece dando il secondo comando ecco cosa ottengo:

root@debian:/home/psimem# dhclient -v wlan0
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/00:14:a5:db:f5:c5
Sending on   LPF/wlan0/00:14:a5:db:f5:c5
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Il fatto curioso e' che da riga di comando ho lo stesso errore anche in mepis benche' tramite NetworkManager funzioni perfettamente .

[sacarde]

mi confermi che sul router c'e' attivo il dhcp , vero?

mepis riesce a prendere l'IP dal dhcp del router ?

[psimem]

Beh il router e' il mio cellulare e da mepis con la procedura automatica fila tutto liscio, pero' da riga di comando ho lo stesso errore che incontro in debian.

Adesso vedo di recuperare il log di quando in mepis entra in funzione network-manager.

Eccolo:

Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0) starting connection 'MB525 6023'
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0/wireless): connection 'MB525 6023' requires no security.  No secrets needed.
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Config: added 'ssid' value 'MB5256023'
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Config: added 'scan_ssid' value '1'
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Config: added 'key_mgmt' value 'NONE'
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> Config: set interface ap_scan to 1
Nov  5 17:03:49 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  inactive -> scanning
Nov  5 17:03:50 mepis1 wpa_supplicant[1612]: Trying to associate with f8:7b:7a:99:72:45 (SSID='MB5256023' freq=2437 MHz)
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  scanning -> associating
Nov  5 17:03:50 mepis1 kernel: [  175.316469] wlan0: authenticate with f8:7b:7a:99:72:45 (try 1)
Nov  5 17:03:50 mepis1 kernel: [  175.320413] wlan0: authenticated
Nov  5 17:03:50 mepis1 kernel: [  175.320735] wlan0: associate with f8:7b:7a:99:72:45 (try 1)
Nov  5 17:03:50 mepis1 kernel: [  175.350590] wlan0: RX AssocResp from f8:7b:7a:99:72:45 (capab=0x401 status=0 aid=1)
Nov  5 17:03:50 mepis1 kernel: [  175.350596] wlan0: associated
Nov  5 17:03:50 mepis1 kernel: [  175.351924] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov  5 17:03:50 mepis1 wpa_supplicant[1612]: Associated with f8:7b:7a:99:72:45
Nov  5 17:03:50 mepis1 wpa_supplicant[1612]: CTRL-EVENT-CONNECTED - Connection to f8:7b:7a:99:72:45 completed (auth) [id=0 id_str=]
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  associating -> associated
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  associated -> completed
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'MB5256023'.
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov  5 17:03:50 mepis1 wpa_supplicant[1612]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Nov  5 17:03:50 mepis1 kernel: [  175.357422] wlan0: deauthenticated from f8:7b:7a:99:72:45 (Reason: 7)
Nov  5 17:03:50 mepis1 kernel: [  175.357996] cfg80211: Calling CRDA to update world regulatory domain
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> dhclient started with pid 2120
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  completed -> disconnected
Nov  5 17:03:50 mepis1 dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Nov  5 17:03:50 mepis1 dhclient: Copyright 2004-2010 Internet Systems Consortium.
Nov  5 17:03:50 mepis1 dhclient: All rights reserved.
Nov  5 17:03:50 mepis1 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Nov  5 17:03:50 mepis1 dhclient: 
Nov  5 17:03:50 mepis1 dhclient: Listening on LPF/wlan0/00:14:a5:db:f5:c5
Nov  5 17:03:50 mepis1 dhclient: Sending on   LPF/wlan0/00:14:a5:db:f5:c5
Nov  5 17:03:50 mepis1 dhclient: Sending on   Socket/fallback
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Nov  5 17:03:50 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Nov  5 17:03:52 mepis1 wpa_supplicant[1612]: Trying to associate with f8:7b:7a:99:72:45 (SSID='MB5256023' freq=2437 MHz)
Nov  5 17:03:52 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  scanning -> associating
Nov  5 17:03:52 mepis1 kernel: [  176.752435] wlan0: authenticate with f8:7b:7a:99:72:45 (try 1)
Nov  5 17:03:52 mepis1 kernel: [  176.756211] wlan0: authenticated
Nov  5 17:03:52 mepis1 kernel: [  176.756394] wlan0: associate with f8:7b:7a:99:72:45 (try 1)
Nov  5 17:03:52 mepis1 wpa_supplicant[1612]: Associated with f8:7b:7a:99:72:45
Nov  5 17:03:52 mepis1 wpa_supplicant[1612]: CTRL-EVENT-CONNECTED - Connection to f8:7b:7a:99:72:45 completed (reauth) [id=0 id_str=]
Nov  5 17:03:52 mepis1 kernel: [  176.770537] wlan0: RX AssocResp from f8:7b:7a:99:72:45 (capab=0x401 status=0 aid=1)
Nov  5 17:03:52 mepis1 kernel: [  176.770541] wlan0: associated
Nov  5 17:03:52 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  associating -> associated
Nov  5 17:03:52 mepis1 NetworkManager[1577]: <info> (wlan0): supplicant connection state:  associated -> completed
Nov  5 17:03:53 mepis1 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Nov  5 17:03:53 mepis1 dhclient: DHCPACK from 192.168.1.1
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info>   address 192.168.1.30
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info>   prefix 24 (255.255.255.0)
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info>   gateway 192.168.1.1
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info>   nameserver '192.168.1.1'
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Nov  5 17:03:53 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Nov  5 17:03:53 mepis1 avahi-daemon[1370]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.30.
Nov  5 17:03:53 mepis1 avahi-daemon[1370]: New relevant interface wlan0.IPv4 for mDNS.
Nov  5 17:03:53 mepis1 avahi-daemon[1370]: Registering new address record for 192.168.1.30 on wlan0.IPv4.
Nov  5 17:03:53 mepis1 dhclient: bound to 192.168.1.30 -- renewal in 815 seconds.
Nov  5 17:03:54 mepis1 NetworkManager[1577]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Nov  5 17:03:54 mepis1 NetworkManager[1577]: <info> Policy set 'MB525 6023' (wlan0) as default for IPv4 routing and DNS.
Nov  5 17:03:54 mepis1 NetworkManager[1577]: <info> Activation (wlan0) successful, device activated.
Nov  5 17:03:54 mepis1 NetworkManager[1577]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.

[sacarde]

l'errore sembra che non trovi nessun dhcp in rete


p.s.
ma hai soltando l'essid? o anche altre chiavi?

[psimem]

Si' ho soltanto l'essid dato che sto facendo tutte queste prove voglio che sia il piu' semplice possibile.
Quello che mi pare strano e' che da networkmanager funzioni ed invece da linea di comando no.

[sacarde]

non avevo capito che funzionasse..., anche se da networkmanager

[psimem]

Riassumendo:
- da wheezy non funziona 'na mazza sia che provi da riga di comando che da networkmanagerapplet
- da mepis invece funziona solo da networkmanagerapplet
A me servirebbe pero' farlo funzionare da wheezy, in un modo o nell'altro .

[sacarde]

a parita' di moduli caricati e blaklistati ?
a parita' di firmware


p.s.
quindi solo i kernel sono diversi

[psimem]

Precisamente.

[sacarde]

anche a parita' di pacchetti riguardante la connessione?

es: wpasupplicant wireless-tools


parita di file di configurazione: /etc/network/interfaces



p.s.
vedi passaggio di parametri al caricare dei moduli?

[psimem]

I pacchetti installati mi sembrano uguali sia per mepis che wheezy.

Il file di configurazione interfaces e' identico.

Cosa intendi per passaggio di parametri al caricare dei moduli?