You are not logged in.

Pages: 1

#1 2013-09-23 01:32:13

keepitsimpleengineer
Member
From: San Joaquin Valley, CA
Registered: 2012-06-25
Posts: 380

Broadcom/b43 suddenly cannot hold wireless connection

The last week or so my wireless connection on my Lenovo S-12 (Intel Atom) i686 laptop will connect but will disconnect after a period of time or a small amount of data having been transferred.  Since b43-fwcutter   was updated 13.09.12, I suspect it may be responsible.

I use wicd as it was the only wireless controller that worked when I installed archlinux for 32 bit..  It has worked very well for many months.

For example, when updating the rate of transfer drops to practically nothing after only a little way through updating from repositories, and the update will fail.

The hardware works fine with the Windows XP, and the wired connection works fine.

Has anybody else run up against this..?

Ref:  System Info for archlinux on the Lenovo S12

Edit: Corrected link to Sysinfo

b43 modules loaded...

[ljohnson@KISE-007 ~]$ lsmod | grep b43
b43                   341637  0
bcma                   30352  1 b43
mac80211              389724  1 b43
cfg80211              336964  2 b43,mac80211
ssb                    48159  1 b43
mmc_core               86479  2 b43,ssb
pcmcia                 40213  2 b43,ssb
Thw6g/]System Information[/url] for archlinux on the Lenovo s12

pacman query for b43   and wicd ...

root@KISE-007 ~]# pacman -Qii b43-fwcutter b43-firmware wicd wicd-gtk
Name           : b43-fwcutter
Version        : 018-1
Description    : firmware extractor for the b43 kernel module
Architecture   : i686
URL            : http://wireless.kernel.org/en/users/Drivers/b43
Licenses       : GPL
Groups         : None
Provides       : None
Depends On     : glibc
Optional Deps  : None
Required By    : None
Optional For   : None
Conflicts With : None
Replaces       : None
Installed Size :  59.00 KiB
Packager       : Tobias Powalowski <tpowa@archlinux.org>
Build Date     : Sun 01 Sep 2013 01:08:21 AM PDT
Install Date   : Thu 12 Sep 2013 09:04:36 PM PDT
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By   : Signature
Backup Files:
(none)

Name           : b43-firmware
Version        : 5.100.138-2
Description    : Firmware for Broadcom B43 wireless networking chips
Architecture   : any
URL            : http://linuxwireless.org/en/users/Drivers/b43
Licenses       : GPL
Groups         : None
Provides       : None
Depends On     : linux>=3.2
Optional Deps  : None
Required By    : None
Optional For   : None
Conflicts With : None
Replaces       : None
Installed Size : 1072.00 KiB
Packager       : Unknown Packager
Build Date     : Fri 07 Dec 2012 11:11:28 AM PST
Install Date   : Fri 07 Dec 2012 11:12:19 AM PST
Install Reason : Explicitly installed
Install Script : No
Validated By   : Unknown
Backup Files:
(none)

Name           : wicd
Version        : 1.7.2.4-9
Description    : Wired and wireless network manager for Linux
Architecture   : any
URL            : http://wicd.sourceforge.net/
Licenses       : GPL2
Groups         : None
Provides       : None
Depends On     : python2  python2-dbus  dhcpcd  wpa_supplicant  wireless_tools  inetutils  net-tools  ethtool
                 shared-mime-info  python2-urwid  python2-gobject2  dbus-glib  rfkill
Optional Deps  : wicd-gtk: needed if you want the GTK interface [installed]
Required By    : wicd-gtk
Optional For   : None
Conflicts With : wicd-svn
Replaces       : None
Installed Size : 2373.00 KiB
Packager       : Angel Velasquez <angvp@archlinux.org>
Build Date     : Tue 20 Aug 2013 12:10:07 PM PDT
Install Date   : Wed 21 Aug 2013 07:59:56 AM PDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By   : Signature
Backup Files:
UNMODIFIED	/etc/wicd/encryption/templates/active

Name           : wicd-gtk
Version        : 1.7.2.4-9
Description    : Wired and wireless network manager for Linux - GTK client
Architecture   : any
URL            : http://wicd.sourceforge.net/
Licenses       : GPL2
Groups         : None
Provides       : None
Depends On     : wicd  pygtk  hicolor-icon-theme
Optional Deps  : gksu: needed to access some preferences in gtk interface
                 notification-daemon: needed if you want notifications [installed]
                 python2-notify: needed if you want notifications [installed]
Required By    : None
Optional For   : wicd
Conflicts With : wicd-svn
Replaces       : None
Installed Size : 535.00 KiB
Packager       : Angel Velasquez <angvp@archlinux.org>
Build Date     : Tue 20 Aug 2013 12:10:08 PM PDT
Install Date   : Wed 21 Aug 2013 07:59:56 AM PDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By   : Signature
Backup Files:
(none)

Last edited by keepitsimpleengineer (2013-09-24 14:55:21)

Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius

Offline

#2 2013-09-23 01:43:02

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: Broadcom/b43 suddenly cannot hold wireless connection

Your Sysinfo link reports "This paste has been removed!"

On this system, wicd with wicd-gtk drives my Broadcom flawlessly.

ewaller$@$odin ~ 1001 %pacman -Qi linux
Name           : linux
Version        : 3.11.1-1
Description    : The Linux kernel and modules
Architecture   : x86_64
URL            : http://www.kernel.org/
Licenses       : GPL2
Groups         : base
Provides       : kernel26=3.11.1
Depends On     : coreutils  linux-firmware  kmod  mkinitcpio>=0.7
Optional Deps  : crda: to set the correct wireless channels of your country
                 [installed]
Required By    : b43-firmware  virtualbox-host-modules
Optional For   : None
Conflicts With : kernel26
Replaces       : kernel26
Installed Size : 67172.00 KiB
Packager       : Tobias Powalowski <tpowa@archlinux.org>
Build Date     : Sat Sep 14 10:35:05 2013
Install Date   : Mon Sep 16 09:51:58 2013
Install Reason : Explicitly installed
Install Script : Yes
Validated By   : Signature

ewaller$@$odin ~ 1002 %pacman -Qs wicd
local/wicd 1.7.2.4-9
    Wired and wireless network manager for Linux
local/wicd-gtk 1.7.2.4-9
    Wired and wireless network manager for Linux - GTK client
ewaller$@$odin ~ 1003 %pacman -Qs broadcom
local/b43-firmware 5.100.138-2
    Firmware for Broadcom B43 wireless networking chips
ewaller$@$odin ~ 1004 %lspci -nn | grep Broad 
02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
ewaller$@$odin ~ 1005 %

Are you sure there is nothing else trying to control the interface?

edit:

ewaller$@$odin ~ [1]1002 %lsmod | grep b43 
b43                   364869  0 
bcma                   35004  1 b43
mac80211              453808  1 b43
cfg80211              402729  2 b43,mac80211
ssb                    55467  1 b43
pcmcia                 45356  2 b43,ssb
mmc_core               95506  5 b43,ssb,mmc_block,sdhci,sdhci_pci
ewaller$@$odin ~ 1003 %

Last edited by ewaller (2013-09-23 01:44:37)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2013-09-23 10:30:49

keepitsimpleengineer
Member
From: San Joaquin Valley, CA
Registered: 2012-06-25
Posts: 380

Re: Broadcom/b43 suddenly cannot hold wireless connection

ewaller wrote:

Your Sysinfo link reports "This paste has been removed!"

Fixed, thanks for the heads up. smile

Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius

Offline

#4 2013-09-23 14:42:52

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: Broadcom/b43 suddenly cannot hold wireless connection

Well, it seems we have the same hardware, the same firmware, Same wicd.  Likely the same kernel.

This is the part where I suggest looking at the journal for anything interesting.  Also, take a look at the output of iwconfig (while you have a connection)
Perhaps if you could post the output of ps -ef

What make and model is your router?  Is it Open, WEP, or WPA 1/2 ?
If it is WPA, what is your version of wpa_supplicant ?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2013-09-23 17:23:53

keepitsimpleengineer
Member
From: San Joaquin Valley, CA
Registered: 2012-06-25
Posts: 380

Re: Broadcom/b43 suddenly cannot hold wireless connection

ewaller wrote:

Well, it seems we have the same hardware, the same firmware, Same wicd.  Likely the same kernel.

[ljohnson@KISE-007 ~]$ uname -a
Linux KISE-007 3.11.1-1-ARCH #1 SMP PREEMPT Sat Sep 14 20:31:35 CEST 2013 i686 GNU/Linux

[root@KISE-007 ~]# lspci | grep Broadcom
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

Note: i686 vice x86_64

This is the part where I suggest looking at the journal for anything interesting.  Also, take a look at the output of iwconfig (while you have a connection)
Perhaps if you could post the output of ps -ef

No wireless connection this a.m. Journctl at bottom of post...

  [ljohnson@KISE-007 ~]$ ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 16:29 ?        00:00:01 /sbin/init verbose
root         2     0  0 16:29 ?        00:00:00 [kthreadd]
root         3     2  0 16:29 ?        00:00:02 [ksoftirqd/0]
root         4     2  0 16:29 ?        00:00:03 [kworker/0:0]
root         5     2  0 16:29 ?        00:00:00 [kworker/0:0H]
root         7     2  0 16:29 ?        00:00:00 [migration/0]
root         8     2  0 16:29 ?        00:00:03 [rcu_preempt]
root         9     2  0 16:29 ?        00:00:00 [rcu_bh]
root        10     2  0 16:29 ?        00:00:00 [rcu_sched]
root        11     2  0 16:29 ?        00:00:00 [watchdog/0]
root        12     2  0 16:29 ?        00:00:00 [watchdog/1]
root        13     2  0 16:29 ?        00:00:00 [migration/1]
root        14     2  0 16:29 ?        00:00:04 [ksoftirqd/1]
root        16     2  0 16:29 ?        00:00:00 [kworker/1:0H]
root        17     2  0 16:29 ?        00:00:00 [khelper]
root        18     2  0 16:29 ?        00:00:00 [kdevtmpfs]
root        19     2  0 16:29 ?        00:00:00 [netns]
root        20     2  0 16:29 ?        00:00:00 [writeback]
root        21     2  0 16:29 ?        00:00:00 [bioset]
root        22     2  0 16:29 ?        00:00:00 [kworker/u5:0]
root        23     2  0 16:29 ?        00:00:00 [kblockd]
root        25     2  0 16:29 ?        00:00:00 [kworker/1:1]
root        26     2  0 16:29 ?        00:00:00 [khungtaskd]
root        27     2  0 16:29 ?        00:00:00 [kswapd0]
root        28     2  0 16:29 ?        00:00:00 [ksmd]
root        29     2  0 16:29 ?        00:00:00 [khugepaged]
root        30     2  0 16:29 ?        00:00:00 [fsnotify_mark]
root        31     2  0 16:29 ?        00:00:00 [crypto]
root        35     2  0 16:29 ?        00:00:00 [kthrotld]
root        38     2  0 16:29 ?        00:00:00 [deferwq]
root        63     2  0 16:29 ?        00:00:00 [khubd]
root        64     2  0 16:29 ?        00:00:00 [ata_sff]
root        65     2  0 16:29 ?        00:00:00 [scsi_eh_0]
root        66     2  0 16:29 ?        00:00:00 [scsi_eh_1]
root        69     2  0 16:29 ?        00:00:00 [scsi_eh_2]
root        70     2  0 16:29 ?        00:00:00 [scsi_eh_3]
root        71     2  0 16:29 ?        00:00:00 [scsi_eh_4]
root        72     2  0 16:29 ?        00:00:00 [scsi_eh_5]
root        78     2  0 16:29 ?        00:00:00 [kworker/u5:1]
root        86     2  0 16:29 ?        00:00:00 [jbd2/sda5-8]
root        87     2  0 16:29 ?        00:00:00 [ext4-rsv-conver]
root        88     2  0 16:29 ?        00:00:00 [ext4-unrsv-conv]
root       107     1  0 16:29 ?        00:00:01 /usr/lib/systemd/systemd-journald
root       128     2  0 16:29 ?        00:00:00 [cfg80211]
root       145     1  0 16:29 ?        00:00:01 /usr/lib/systemd/systemd-udevd
root       179     2  0 16:29 ?        00:00:00 [hd-audio0]
root       236     2  0 16:29 ?        00:00:00 [kpsmoused]
root       297     1  1 16:29 ?        00:00:25 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-
root       300     1  0 16:29 ?        00:00:00 /usr/bin/syslog-ng -F
root       308     1  0 16:29 ?        00:00:00 /usr/bin/acpid -f
dbus       323     1  0 16:29 ?        00:00:15 /usr/bin/dbus-daemon --system --address=systemd:
root       328     1  0 16:29 ?        00:00:00 /usr/lib/systemd/systemd-logind
root       341     1  0 16:29 ?        00:00:00 login -- ljohnson
ljohnson  1515     1  0 16:29 ?        00:00:00 /usr/lib/systemd/systemd --user
ljohnson  1520  1515  0 16:29 ?        00:00:00 (sd-pam)
ljohnson  1524   341  0 16:29 tty1     00:00:00 xinit /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/x
root      1605   297  0 16:29 ?        00:00:14 /usr/bin/python2 -O /usr/share/wicd/daemon/monit
root      1618  1524  3 16:29 ?        00:00:53 /usr/bin/X -nolisten tcp :0 vt1
ljohnson  1739  1524  0 16:29 tty1     00:00:00 sh /etc/xdg/xfce4/xinitrc
ljohnson  1744  1739  0 16:29 tty1     00:00:00 xfce4-session
ljohnson  1747     1  0 16:30 tty1     00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-ses
ljohnson  1748     1  0 16:30 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 4 --prin
polkitd   1752     1  0 16:30 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
ljohnson  1760     1  0 16:30 ?        00:00:00 /usr/lib/xfce4/xfconf/xfconfd
ljohnson  1767     1  0 16:30 ?        00:00:00 /usr/bin/gpg-agent --sh --daemon --enable-ssh-su
ljohnson  1768  1744  0 16:30 tty1     00:00:00 xfwm4 --replace --display :0.0 --sm-client-id 24
ljohnson  1770  1744  0 16:30 tty1     00:00:00 Thunar --sm-client-id 2b52a40f5-f057-4b03-8f5a-4
ljohnson  1776  1744  0 16:30 tty1     00:00:01 xfce4-panel --display :0.0 --sm-client-id 2d6285
ljohnson  1778  1744  0 16:30 tty1     00:00:01 xfdesktop --display :0.0 --sm-client-id 245fd5b7
ljohnson  1779     1  0 16:30 ?        00:00:00 xfsettingsd --display :0.0 --sm-client-id 2d25be
ljohnson  1781  1744  0 16:30 tty1     00:00:00 xfce4-terminal --geometry=126x36 --display :0.0
ljohnson  1784     1  0 16:30 ?        00:00:00 /usr/lib/gvfs/gvfsd
ljohnson  1798     1  0 16:30 ?        00:00:00 /usr/lib/gvfs//gvfsd-fuse -f /run/user/1000/gvfs
ljohnson  1801     1  0 16:30 ?        00:00:00 xfce4-power-manager --restart --sm-client-id 275
root      1812     1  0 16:30 ?        00:00:00 /usr/lib/upower/upowerd
ljohnson  1815     1  0 16:30 ?        00:00:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
ljohnson  1816  1776  0 16:30 tty1     00:00:08 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/pane
ljohnson  1818  1776  1 16:30 tty1     00:00:21 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/pane
ljohnson  1819  1776  0 16:30 tty1     00:00:02 /usr/lib/xfce4/panel-plugins/xfce4-netload-plugi
ljohnson  1820  1776  0 16:30 tty1     00:00:08 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/pane
ljohnson  1821  1776  0 16:30 tty1     00:00:00 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/pane
ljohnson  1822  1776  0 16:30 tty1     00:00:00 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/pane
ljohnson  1823  1776  0 16:30 tty1     00:00:00 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/pane
ljohnson  1824  1776  0 16:30 tty1     00:00:00 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/pane
root      1826     1  0 16:30 ?        00:00:01 /usr/lib/udisks2/udisksd --no-debug
ljohnson  1846  1781  0 16:30 tty1     00:00:00 gnome-pty-helper
ljohnson  1848     1  0 16:30 ?        00:00:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.9 /org/gt
ljohnson  1857  1781  0 16:30 pts/0    00:00:00 bash
root      1903     1  0 16:30 ?        00:00:00 /usr/lib/udisks/udisks-daemon
root      1905  1903  0 16:30 ?        00:00:00 udisks-daemon: not polling any devices
ljohnson  1912     1  4 16:30 tty1     00:01:14 /usr/lib/skype/skype %U
ljohnson  1926     1  0 16:30 tty1     00:00:07 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-cli
ljohnson  1935     1  0 16:30 ?        00:00:00 /usr/bin/pulseaudio --start
ljohnson  1941     1  0 16:30 tty1     00:00:00 /usr/bin/gnome-keyring-daemon --start --componen
rtkit     1946     1  0 16:30 ?        00:00:00 /usr/lib/rtkit/rtkit-daemon
ljohnson  1952     1  0 16:30 tty1     00:00:00 /usr/bin/gnome-keyring-daemon --start --componen
ljohnson  1953     1  0 16:30 tty1     00:00:00 /usr/bin/gnome-keyring-daemon --start --componen
ljohnson  1955     1  0 16:30 tty1     00:00:00 /usr/bin/gnome-keyring-daemon --start --componen
ljohnson  1972     1  0 16:30 ?        00:00:00 /usr/lib/GConf/gconfd-2
ljohnson  2069  1935  0 16:30 ?        00:00:00 /usr/lib/pulse/gconf-helper
root      2651     2  0 16:35 ?        00:00:00 [kworker/u4:0]
root      3184     2  0 16:48 ?        00:00:00 [kworker/0:1]
root      3186     2  0 16:48 ?        00:00:01 [kworker/1:3]
root      3193     2  0 16:48 ?        00:00:00 [kworker/u4:2]
root      3580     2  0 16:51 ?        00:00:00 [irq/17-b43]
root      3695     1  0 16:51 ?        00:00:00 /usr/sbin/dhcpcd -h KISE-007 --noipv4ll eth0
root      3798     1  0 16:54 ?        00:00:00 sshd: ljohnson [priv]
ljohnson  3809  3798  0 16:54 ?        00:00:00 sshd: ljohnson@pts/1
ljohnson  3810  3809  0 16:54 pts/1    00:00:00 -bash
ljohnson  3902  3810  0 16:57 pts/1    00:00:00 ps -ef

What make and model is your router?  Is it Open, WEP, or WPA 1/2 ?

Router is UntangleBuild: 9.4.2~svn20130830r35759release9.4-1lenny
Kernel: 2.6.26-2-untangle-686 as a bastion firewall.

Access Point is Linksys WRT54GL V1.1 running Firmware: DD-WRT v24-sp2 (07/22/09) voip. Security is WPA2 AES

If it is WPA, what is your version of wpa_supplicant ?

 [root@KISE-007 ~]# pacman -Qi wpa_supplicant
Name           : wpa_supplicant
Version        : 2.0-4
Description    : A utility providing key negotiation for WPA wireless networks
Architecture   : i686
URL            : http://hostap.epitest.fi/wpa_supplicant
Licenses       : GPL
Groups         : None
Provides       : None
Depends On     : openssl  dbus-core  readline  libnl
Optional Deps  : wpa_supplicant_gui: wpa_gui program
Required By    : wicd  wpa_actiond
Optional For   : netctl
Conflicts With : None
Replaces       : None
Installed Size : 1377.00 KiB
Packager       : Tom Gundersen <teg@jklm.no>
Build Date     : Thu 30 May 2013 10:40:54 AM PDT
Install Date   : Tue 04 Jun 2013 09:22:06 AM PDT
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By   : Signature

From this morning boot... (I can post entire log on paste.bin)

[root@KISE-007 ~]# journalctl -b | grep network
Sep 22 16:29:38 KISE-007 kernel: drop_monitor: Initializing network drop monitor service
Sep 22 16:29:49 KISE-007 systemd[1]: Starting A wireless connection using a custom network block configuration...
Sep 22 16:29:49 KISE-007 systemd[1]: Starting Wicd a wireless and wired network manager for Linux...
Sep 22 16:29:50 KISE-007 network[315]: Starting network profile 'ethernet-dhcp-eth0'...
Sep 22 16:29:51 KISE-007 network[282]: Starting network profile 'wireless-dhcp-wlan0-wpa-kise'...
Sep 22 16:29:51 KISE-007 network[282]: Successfully initialized wpa_supplicant
Sep 22 16:29:51 KISE-007 network[282]: Line 5: unknown network field 'Key'.
Sep 22 16:29:51 KISE-007 network[282]: Line 6: failed to parse network block.
Sep 22 16:29:51 KISE-007 network[282]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlan0.conf'.
Sep 22 16:29:53 KISE-007 network[282]: The WPA supplicant did not start for interface 'wlan0'
Sep 22 16:29:54 KISE-007 network[282]: Failed to bring the network up for profile 'wireless-dhcp-wlan0-wpa-kise'
Sep 22 16:29:54 KISE-007 systemd[1]: Failed to start A wireless connection using a custom network block configuration.
Sep 22 16:29:56 KISE-007 systemd[1]: Started Wicd a wireless and wired network manager for Linux.
Sep 22 16:29:59 KISE-007 network[315]: No connection on interface 'eth0'
Sep 22 16:29:59 KISE-007 network[315]: Failed to bring the network up for profile 'ethernet-dhcp-eth0'

Add'l notes:  The S12 when running WinXP has no problem connecting to the AP and maintaining an excellent connection.  No problem with wireless with other devices.  I switched channels from 6 to 11 with no improvement.  This is an inexpensive laptop configured plain-jane as it never leaves the home.  Nothing has changed on this system for over 6 months except for regular updates.

I'm a little leery of the Broadcom wireless hardware, when I bought this the first one the wireless was DOA, so Lenovo replaced it. 

Thanks for your assistance!  smile

Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius

Offline

#6 2013-09-24 14:42:33

keepitsimpleengineer
Member
From: San Joaquin Valley, CA
Registered: 2012-06-25
Posts: 380

Re: Broadcom/b43 suddenly cannot hold wireless connection

Okay, so this morning the laptop booted with wireless up, and I got this:

[ljohnson@KISE-007 ~]$ sudo iwconfig
wlan0     IEEE 802.11bg  ESSID:"kise"  
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:18:F8:F9:63:74   
          Bit Rate=18 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-18 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:1   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

[ljohnson@KISE-007 ~]$ sudo iwconfig
wlan0     IEEE 802.11bg  ESSID:"kise"  
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:18:F8:F9:63:74   
          Bit Rate=18 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=13 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:3  Invalid misc:1   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

[ljohnson@KISE-007 ~]$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1.54 ms
^C
--- 192.168.0.1 ping statistics ---
15 packets transmitted, 1 received, 93% packet loss, time 14018ms
rtt min/avg/max/mdev = 1.541/1.541/1.541/0.000 ms
[ljohnson@KISE-007 ~]$ sudo iwconfig
wlan0     IEEE 802.11bg  ESSID:"kise"  
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:18:F8:F9:63:74   
          Bit Rate=18 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=2 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:5  Invalid misc:1   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

[ljohnson@KISE-007 ~]$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.71 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=4.72 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=1.50 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=1.51 ms
64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=1.58 ms
^C
--- 192.168.0.1 ping statistics ---
58 packets transmitted, 5 received, 91% packet loss, time 57049ms
rtt min/avg/max/mdev = 1.508/2.210/4.728/1.261 ms
[ljohnson@KISE-007 ~]$ sudo iwconfig
wlan0     IEEE 802.11bg  ESSID:"kise"  
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:18:F8:F9:63:74   
          Bit Rate=18 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=7 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:7  Invalid misc:1   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

I also got this:

[ljohnson@KISE-007 ~]$ sudo -i
[root@KISE-007 ~]# journalctl -b | grep network
Sep 23 15:13:36 KISE-007 kernel: drop_monitor: Initializing network drop monitor service
Sep 23 15:13:48 KISE-007 systemd[1]: Starting A wireless connection using a custom network block configuration...
Sep 23 15:13:48 KISE-007 systemd[1]: Starting Wicd a wireless and wired network manager for Linux...
Sep 23 15:13:49 KISE-007 network[439]: Starting network profile 'ethernet-dhcp-eth0'...
Sep 23 15:13:49 KISE-007 network[439]: The interface of network profile 'ethernet-dhcp-eth0' is already up
Sep 23 15:13:49 KISE-007 network[407]: Starting network profile 'wireless-dhcp-wlan0-wpa-kise'...
Sep 23 15:13:51 KISE-007 network[407]: Successfully initialized wpa_supplicant
Sep 23 15:13:51 KISE-007 network[407]: Line 5: unknown network field 'Key'.
Sep 23 15:13:51 KISE-007 network[407]: Line 6: failed to parse network block.
Sep 23 15:13:51 KISE-007 network[407]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlan0.conf'.
Sep 23 15:13:52 KISE-007 network[407]: The WPA supplicant did not start for interface 'wlan0'
Sep 23 15:13:53 KISE-007 network[407]: Failed to bring the network up for profile 'wireless-dhcp-wlan0-wpa-kise'
Sep 23 15:13:53 KISE-007 systemd[1]: Failed to start A wireless connection using a custom network block configuration.
Sep 23 15:13:54 KISE-007 systemd[1]: Started Wicd a wireless and wired network manager for Linux.
Sep 23 15:14:16 KISE-007 gnome-keyring-daemon[1851]: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Sep 23 15:14:17 KISE-007 gnome-keyring-daemon[1876]: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Sep 23 15:14:18 KISE-007 gnome-keyring-daemon[1878]: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[root@KISE-007 ~]#

Last edited by keepitsimpleengineer (2013-09-24 14:47:55)

Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius

Offline

#7 2013-09-24 17:10:36

keepitsimpleengineer
Member
From: San Joaquin Valley, CA
Registered: 2012-06-25
Posts: 380

Re: Broadcom/b43 suddenly cannot hold wireless connection

Post withdrawn sad

Last edited by keepitsimpleengineer (2013-09-24 21:32:32)

Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius

Offline

Pages: 1

Board footer

Powered by FluxBB