Re: wicd - wheezy -
El día 19 de junio de 2014, 8:43, Ricardo Delgado
<ricardodelgadoar@gmail.com> escribió:
> Quizas no me explique bien.
>
> La placa inalambrica esta funcionando, a veces se pone "lenta" y en
> esos casos, desconecto y vuelvo a conectar para mejorar la
> conectividad.
>
> Cuando tiro un dmesg me aparece lo que postee.
>
> En definitiva, funcionar funciona, quizas podria optimizar el
> rendimiento, y es lo que pretendo.
>
> Saludos
>
> El día 19 de junio de 2014, 9:07, Debian GMail
> <javier.debian.bb.ar@gmail.com> escribió:
>> El 19/06/14 09:02, Ricardo Delgado escribió:
>>
>>> Me fije y no tenia instalado b43-fwcutter, lo instale. al tirar un dmesg
>>>
>>> [ 76.424734] CPU: 2 PID: 5159 Comm: iwconfig Tainted: P W O
>>> 3.14-1-686-pae #1 Debian 3.14.7-1
>>> [ 76.424738] Hardware name: Acer Aspire V3-571/VA50_HC_CR, BIOS
>>> V1.08 06/21/2012
>>> [ 76.424741] 00000009 c142331d 00000000 c104fd7e c14f4a3c 00000002
>>> 00001427 f909a630
>>> [ 76.424750] 00000397 f907af6e f907af6e f6ab8114 f6a9a600 f6e23000
>>> f6ab8024 c104fe3b
>>> [ 76.424758] 00000009 00000000 f907af6e f6ab8000 f3194800 f6e23000
>>> f6ab8000 f6ab8000
>>> [ 76.424767] Call Trace:
>>> [ 76.424776] [<c142331d>] ? dump_stack+0x3e/0x4e
>>> [ 76.424783] [<c104fd7e>] ? warn_slowpath_common+0x7e/0xa0
>>> [ 76.424799] [<f907af6e>] ? cfg80211_connect+0x3ee/0x430 [cfg80211]
>>> [ 76.424811] [<f907af6e>] ? cfg80211_connect+0x3ee/0x430 [cfg80211]
>>> [ 76.424816] [<c104fe3b>] ? warn_slowpath_null+0x1b/0x20
>>> [ 76.424827] [<f907af6e>] ? cfg80211_connect+0x3ee/0x430 [cfg80211]
>>> [ 76.424843] [<f9094024>] ? cfg80211_mgd_wext_connect+0x114/0x180
>>> [cfg80211]
>>> [ 76.424858] [<f90945b7>] ? cfg80211_mgd_wext_siwap+0xe7/0x170
>>> [cfg80211]
>>> [ 76.424864] [<c1417f4b>] ? ioctl_standard_call+0x4b/0x390
>>> [ 76.424872] [<c1352e39>] ? dev_get_by_name_rcu+0x49/0x70
>>> [ 76.424877] [<c1418485>] ? wext_handle_ioctl+0x1f5/0x230
>>> [ 76.424892] [<f9092b20>] ? cfg80211_wext_siwtxpower+0x190/0x190
>>> [cfg80211]
>>> [ 76.424897] [<c1367c60>] ? dev_ioctl+0x270/0x500
>>> [ 76.424902] [<c133f6e0>] ? sock_fasync+0x80/0x80
>>> [ 76.424907] [<c115cb47>] ? do_vfs_ioctl+0x307/0x500
>>> [ 76.424912] [<c115fbb2>] ? dput+0x12/0xe0
>>> [ 76.424919] [<c114df06>] ? __fput+0x136/0x1e0
>>> [ 76.424923] [<c115cd98>] ? SyS_ioctl+0x58/0x80
>>> [ 76.424929] [<c142e9c6>] ? sysenter_do_call+0x12/0x28
>>> [ 76.424932] ---[ end trace 398f79415b6aa51f ]---
>>>
>>> El día 19 de junio de 2014, 1:59, Manolo Díaz <diaz.manolo@gmail.com>
>>> escribió:
>>>>
>>>> On Wednesday, Jun 18 2014 at 15:40 (UTC+2),
>>>> Ricardo Delgado wrote:
>>>>
>>>>> Buenas Lista,
>>>>>
>>>>> Les consulto por el siguiente mensaje que aparece al realizar un dmesg.
>>>>>
>>>>> De repente empece a notar lentitud al conectarme via wireless y,
>>>>> buscando motivos tire un dmesg que da esa salida.
>>>>>
>>>>> No logro entender que sucede, ya que al abrir WICD y dar desconectar
>>>>> la conexion en curso y volver a conectar, de repente el trafico es
>>>>> "normal" es decir no noto lentitud.
>>>>>
>>>>> el mensaje es este.
>>>>>
>>>>>
>>>>> [ 1818.904961] CPU: 3 PID: 11086 Comm: iwconfig Tainted: P W O
>>>>> 3.14-1-686-pae #1 Debian 3.14.4-1
>>>>> [ 1818.904964] Hardware name: Acer Aspire V3-571/VA50_HC_CR, BIOS
>>>>> V1.08 06/21/2012
>>>>> [ 1818.904966] 00000009 c1422bde 00000000 c104fdee c14f4974 00000003
>>>>> 00002b4e f8fd6630
>>>>> [ 1818.904974] 00000397 f8fb6f2e f8fb6f2e f2cdd114 f27b2200 f2cde000
>>>>> f2cdd024 c104feab
>>>>> [ 1818.904981] 00000009 00000000 f8fb6f2e f2cdd000 f2cd5800 f2cde000
>>>>> f2cdd000 f2cdd000
>>>>> [ 1818.904988] Call Trace:
>>>>> [ 1818.904996] [<c1422bde>] ? dump_stack+0x3e/0x4e
>>>>> [ 1818.905002] [<c104fdee>] ? warn_slowpath_common+0x7e/0xa0
>>>>> [ 1818.905019] [<f8fb6f2e>] ? cfg80211_connect+0x3ee/0x430 [cfg80211]
>>>>> [ 1818.905031] [<f8fb6f2e>] ? cfg80211_connect+0x3ee/0x430 [cfg80211]
>>>>> [ 1818.905036] [<c104feab>] ? warn_slowpath_null+0x1b/0x20
>>>>> [ 1818.905048] [<f8fb6f2e>] ? cfg80211_connect+0x3ee/0x430 [cfg80211]
>>>>> [ 1818.905062] [<f8fd00d4>] ? cfg80211_mgd_wext_connect+0x114/0x180
>>>>> [cfg80211]
>>>>> [ 1818.905077] [<f8fd0667>] ? cfg80211_mgd_wext_siwap+0xe7/0x170
>>>>> [cfg80211]
>>>>> [ 1818.905082] [<c14177db>] ? ioctl_standard_call+0x4b/0x390
>>>>> [ 1818.905088] [<c1352839>] ? dev_get_by_name_rcu+0x49/0x70
>>>>> [ 1818.905092] [<c1417d15>] ? wext_handle_ioctl+0x1f5/0x230
>>>>> [ 1818.905106] [<f8fcebd0>] ? cfg80211_wext_siwtxpower+0x190/0x190
>>>>> [cfg80211]
>>>>> [ 1818.905111] [<c13675a8>] ? dev_ioctl+0x278/0x500
>>>>> [ 1818.905115] [<c133f070>] ? sock_fasync+0x80/0x80
>>>>> [ 1818.905120] [<c115c937>] ? do_vfs_ioctl+0x307/0x500
>>>>> [ 1818.905124] [<c115f9a2>] ? dput+0x12/0xe0
>>>>> [ 1818.905130] [<c114dd26>] ? __fput+0x136/0x1e0
>>>>> [ 1818.905134] [<c115cb88>] ? SyS_ioctl+0x58/0x80
>>>>> [ 1818.905138] [<c142e306>] ? sysenter_do_call+0x12/0x28
>>>>> [ 1818.905142] ---[ end trace 584922b1466961ba ]---
>>>>> [ 1819.089777] INFO @wl_cfg80211_scan : system busy : scan for
>>>>> "wirecasa" canceled
>>>>>
>>>>> Alguna idea del problema, o donde leer al respecto? Gracias
>>>>>
>>>>> el driver Network controller: Broadcom Corporation BCM43228
>>>>> 802.11a/b/g/n
>>>>
>>>>
>>>> No me parece que tenga nada que ver con wicd.
>>>>
>>>> He mirado en la ayuda que aparece al compilar linux desde los fuentes.
>>>> Al parecer hay dos posibles controladores para la serie BCM43xx (b43 y
>>>> b43legacy), y ambos dicen que se debe usar la utilidad b43-fwcutter,
>>>> disponible bajo ese mismo nombre en Debian, sección contrib. ¿La tienes
>>>> instalada?
>>>>
>>>> Este es el texto para b43 al que me refiero:
>>>>
>>>> "This driver uses V4 firmware, which must be installed separately
>>>> using b43-fwcutter."
>>>>
>>>> El de b43legacy habla de la versión V3, pero por lo demás es idéntico.
>>>>
>>>> Saludos.
>>>> --
>>>> Manolo Díaz
>>>>
>>>>
>>>> --
>>>> To UNSUBSCRIBE, email to debian-user-spanish-REQUEST@lists.debian.org
>>>> with a subject of "unsubscribe". Trouble? Contact
>>>> listmaster@lists.debian.org
>>>> Archive: [🔎] 20140619065913.297773cd@gmail.com">https://lists.debian.org/[🔎] 20140619065913.297773cd@gmail.com
>>>>
>>>
>>>
>>>
>>
>>
>> Perdón que me meta.
>> ¿Hiciste TODO lo que dice acá?
>> Yo tengo una netbook HP-mini con una placa BCM4312 y me dio mucho dolores
>> de cabeza.
>> Y la única forma de hacerla funcionar fue siguiendo esta página, sobre todo
>> el tema de los "blacklist".
>>
>> JAP
>>
>> JAP
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-spanish-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>> Archive: [🔎] 53A2D273.2050905@gmail.com">https://lists.debian.org/[🔎] 53A2D273.2050905@gmail.com
>>
>
>
>
> --
> "Windows? Reboot
> Debian? beRoot "
>
>
> --
> To UNSUBSCRIBE, email to debian-user-spanish-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] CA+0kpa0fonRi6WW2-ss4QtiWbweF5Lz_q8VgyV8sxtSFGbCyxw@mail.gmail.com">https://lists.debian.org/[🔎] CA+0kpa0fonRi6WW2-ss4QtiWbweF5Lz_q8VgyV8sxtSFGbCyxw@mail.gmail.com
>
hola , les comento que tengo un dell con una broadcom 4312 y solo hice un
apt-get install firmware-b43-lpphy-installer
y quedo funcionando sin problemas de conexión ni nada de eso
Reply to: