Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Wireless disconnecting randomly on 12.1

  1. #1

    Default Wireless disconnecting randomly on 12.1

    I have a laptop with openSUSE 12.1 32-bit and wireless card Broadcom bcm4312. Installed b43 driver from usr/sbin/install_bcm43xx_firmware, and works but it randomly disconnects and connects, very often. Then It stabilizes but only after a while. Tried even b43 driver from Packman, and same issue.

    Then I remembered I had no problems back on 11.4, so I downloaded the rpm for 11.4 repo, which version is 4.174.64.19-3.pm.3.1. Keeps disconnecting, although much less often.

    What's happening? Anyone knows? I wouldn't like to return to 11.4 just because of this.
    And just out of curiosity, how can I check the b43 version the script installs?

    Thanks for your help.

  2. #2
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,379

    Default Re: Wireless disconnecting randomly on 12.1

    On 01/13/2012 05:46 PM, F style wrote:
    >
    > I have a laptop with openSUSE 12.1 32-bit and wireless card Broadcom
    > bcm4312. Installed b43 driver from usr/sbin/install_bcm43xx_firmware,
    > and works but it randomly disconnects and connects, very often. Then It
    > stabilizes but only after a while. Tried even b43 driver from Packman,
    > and same issue.
    >
    > Then I remembered I had no problems back on 11.4, so I downloaded the
    > rpm for 11.4 repo, which version is 4.174.64.19-3.pm.3.1. Keeps
    > disconnecting, although much less often.
    >
    > What's happening? Anyone knows? I wouldn't like to return to 11.4 just
    > because of this.
    > And just out of curiosity, how can I check the b43 version the script
    > installs?


    What script? ALL Linux drivers are kernel modules. Any version info is
    effectively meaningless. You get that information with 'uname -r'. If you mean
    "what version of the firmware" is installed, that information is logged to the
    dmesg output every time the driver is loaded. The list of available firmware
    files is at
    http://wireless.kernel.org/en/users/...e_installation.

    I'm not sure it will make any difference, but you should try the compat-wireless
    package.

    The other thing to do is look at the dmesg log, and report any message that
    happens when the wifi disconnects.

  3. #3

    Default Re: Wireless disconnecting randomly on 12.1

    Quote Originally Posted by lwfinger View Post
    What script?
    The one in usr/sbin/install_bcm43xx_firmware. I just thought there were "driver versions" just like softwae versions because back on 11.4 I installed the b43 wireless driver from Packman, and it got updated just like any other software.

    Back to the central point (the described problems), where do I find that dmesg file?

  4. #4
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,379

    Default Re: Wireless disconnecting randomly on 12.1

    On 01/13/2012 06:16 PM, F style wrote:
    >
    > lwfinger;2430097 Wrote:
    >> What script?

    >
    > The one in usr/sbin/install_bcm43xx_firmware. I just thought there were
    > "driver versions" just like softwae versions because back on 11.4 I
    > installed the b43 wireless driver from Packman, and it got updated just
    > like any other software.


    It got updated because the script got revised. It did not change the driver.

    > Back to the central point (the described problems), where do I find
    > that dmesg file?


    The command is 'dmesg'.


  5. #5
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    37,035
    Blog Entries
    16

    Default Re: Wireless disconnecting randomly on 12.1

    Quote Originally Posted by F_style View Post
    The one in usr/sbin/install_bcm43xx_firmware. I just thought there were "driver versions" just like softwae versions because back on 11.4 I installed the b43 wireless driver from Packman, and it got updated just like any other software.

    Back to the central point (the described problems), where do I find that dmesg file?
    There seems to be some confusion.
    Packman also provides a Broadcom driver referred to as 'wl'
    or are you saying you download the b43 firmware .rpm ?

    In 12.1 many more Broadcom devices work with b43
    b43 firmware can be fetched with the: sudo usr/sbin/install_bcm43xx_firmware
    Assuming you have a wire connection to do so.
    Or yes, you could use the .rpm from Packman
    I keep a copy of the b43 folder it creates/fills at /lib/firmware. So I can run installs and get wireless in a Live cd and/or add the firmware post install.

    If you install the 'wl' Broadcom driver as supplied by packman, it will blacklist b43.

    On my Laptop that uses Broadcom, I can easily switch from 'wl' to b43
    Install 'wl' and it blacklists b43
    Uninstall 'wl' and the blacklist is removed.

    If it is that you have NOT actually used 'wl', it might be worth trying it.
    But you must use the drivers from 12.1 packman repos
    Install Broadcom Drivers from Packman - Blogs - openSUSE Forums

    *Finally: You quoted your device but not accurately:
    /sbin/lspci -nnk
    Will tell us more so
    My openSUSE 13.1 KDE Box
    My Articles
    Was I any help? If yes: Click the star below

  6. #6

    Default Re: Wireless disconnecting randomly on 12.1

    I have the very same problem with the b43 driver from OSuSE 12.1 (the OSuSE 12.1 wl driver does not work for my Dell Broadcom 4312 wireless card). Since the same Dell wireless card/laptop worked perfectly with Suse 11.2, it would seem to point to issues/bugs with OSuSE version of the b43 driver; the random instability I am experiencing came after the upgrade to SuSE 12.1, and I have also used the broadcom drivers from Packman, with no success (yet).

    By "random instability", I mean the following:

    1. My wlan SSID is sometimes but not always revealed by the NetworkManager scan. This applies to some neighbours' wlans that are discovered during the scan, too. However, some SSIDs *do* always seem to appear (sadly not mine)!
    2. When my SSID does appear in the list of discovered SSIDs, clicking it in the NetworkManager application causes it to disappear with the message "[15313.539333] wlan0: direct probe to c0:3f:0e:7a:a0:88 timed out". (See below for dmesg output).
    3. When NetworkManager does manage to discover my SSID, it displays wildly varying Wlan strength (from 0-100%) even with the laptop next to the router.
    4. Connection to my SSID does *very* occasionally succeed. However, after the *first* network request (e.g. an external lookup for ftp/http etc) the connection stalls (no route even to the router) and then drops.
    5. NetworkManager occasionally (but not always) has problems "configuring" the Wlan0 interface
    6. If NetworkManager succeeds in configuring the wlan0 interface, it fails to get an IP address from the router.
    7. NetworkManager does not seem to be able to save/remember details of manually



    NOTE: These problems are reproducable on other wireless networks, not just mine.

    I could not get the wireless card to work either with the old wl driver or by configuring it in YaST with the traditional (ifup) method.

    The card works flawlessly with Windows 7.

    I would be very happy to hear about possible workarounds and/or updates to the drivers.

    Best regards
    Gee

    ----------

    Here is some additional information concerning the card, which as I say worked flawlessly with OSuSE 11.2 and is in the list of supported Broadcom chips on b43 - Linux Wireless.

    Code:
    # tamale:~ # lspci -nnk
    04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
            Subsystem: Dell Wireless 1397 WLAN Mini-Card [1028:000c]
            Kernel driver in use: b43-pci-bridge
    Code:
    #tamale:~ # dmesg | grep cfg802
    [   14.464281] cfg80211: Calling CRDA to update world regulatory domain
    [   14.475720] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
    [   14.485300] cfg80211: World regulatory domain updated:
    [   14.485304] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [   14.485307] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   14.485310] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [   14.485313] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [   14.485316] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   14.485318] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   14.504034] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    [   14.504832] Registered led device: b43-phy0::tx
    [   14.504852] Registered led device: b43-phy0::rx
    [   14.504869] Registered led device: b43-phy0::radio
    [   14.504885] Broadcom 43xx driver loaded [ Features: PMNLS, Firmware-ID: FW13 ]
    Code:
    tamale:~ # lsmod | grep b43
    b43                   363772  0 
    mac80211              332546  1 b43
    cfg80211              210325  2 b43,mac80211
    bcma                   29583  1 b43
    ssb                    67780  1 b43
    mmc_core              108074  2 b43,ssb
    When NetworkManager fails in its attempt to configure the wlan0 interface when trying to connect to the SSID, dmesg displays the following information:

    Code:
    [15292.200725] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 1/3)
    [15292.400174] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 2/3)
    [15292.599820] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 3/3)
    [15292.799458] wlan0: direct probe to c0:3f:0e:7a:a0:88 timed out
    [15299.114965] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 1/3)
    [15299.314512] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 2/3)
    [15299.514074] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 3/3)
    [15299.713687] wlan0: direct probe to c0:3f:0e:7a:a0:88 timed out
    [15306.028346] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 1/3)
    [15306.227817] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 2/3)
    [15306.427414] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 3/3)
    [15306.627027] wlan0: direct probe to c0:3f:0e:7a:a0:88 timed out
    [15312.940603] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 1/3)
    [15313.140162] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 2/3)
    [15313.339693] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 3/3)
    [15313.539333] wlan0: direct probe to c0:3f:0e:7a:a0:88 timed out
    Successfull wlan connection (dmesg):

    Code:
    [  482.838290] r8169 0000:05:00.0: eth0: link up
    [  482.838813] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [  499.679540] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=b8:ac:6f:54:cf:88:c0:3f:0e:7a:a0:88:08:00 SRC=192.168.1.1 DST=192.168.1.10 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=1957 DF PROTO=UDP SPT=1025 DPT=137 LEN=58 
    [ 1080.185725] wlan0: authenticate with c0:3f:0e:7a:a0:88 (try 1)
    [ 1080.187531] wlan0: authenticated
    [ 1080.189436] wlan0: associate with c0:3f:0e:7a:a0:88 (try 1)
    [ 1080.192123] wlan0: RX AssocResp from c0:3f:0e:7a:a0:88 (capab=0x431 status=0 aid=1)
    [ 1080.192127] wlan0: associated
    [ 1080.193959] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1088.193802] martian source 255.255.255.255 from 192.168.1.101, on dev wlan0
    [ 1088.193807] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00

  7. #7
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    37,035
    Blog Entries
    16

    Default Re: Wireless disconnecting randomly on 12.1

    You quote openSUSE 11.2
    I'm certain you would have used 'wl' then.

    Your device is almost identical to mine, except for this line from mine
    Subsystem: Broadcom Corporation Device [14e4:04b5]

    In 12.1 I can use either
    In 11.4 and earlier only 'wl' worked

    Stick with b43 in 12.1 and @lwfinger can assist in any buggy bits
    My openSUSE 13.1 KDE Box
    My Articles
    Was I any help? If yes: Click the star below

  8. #8

    Default Re: Wireless disconnecting randomly on 12.1

    Well, let's hope that @lwfinger can find the problem, because as it stands at the moment, the Broadcom wireless card in my Dell Inspiron 1764 is unusable, which is a real pain given that the card/driver worked so well in 11.2. I really do not want to go through the pain of a roll back...

    On the bright side, I notice that a poster on an adjacent thread mentions that his problem with NetworkManager seemed to be connected with the fact that he had chosen not to use KWallet. Well, me too! I decided not to save the wlan password in Kwallet, so perhaps I will do some experimenting there while @lwfinger gets to work on the b43 driver in 12.1 At least I can find out why NetworkManager is discarding "saved" settings, even if it does not help me with the core problem of network connectivity.

    Long live Linux...

  9. #9
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,379

    Default Re: Wireless disconnecting randomly on 12.1

    On 01/15/2012 11:26 AM, geefn wrote:
    >
    > Well, let's hope that @lwfinger can find the problem, because as it
    > stands at the moment, the Broadcom wireless card in my Dell Inspiron
    > 1764 is unusable, which is a real pain given that the card/driver worked
    > so well in 11.2. I really do not want to go through the pain of a roll
    > back...
    >
    > On the bright side, I notice that a poster on an adjacent thread
    > mentions that his problem with NetworkManager seemed to be connected
    > with the fact that he had chosen not to use KWallet. Well, me too! I
    > decided not to save the wlan password in Kwallet, so perhaps I will do
    > some experimenting there while @lwfinger gets to work on the b43 driver
    > in 12.1 At least I can find out why NetworkManager is discarding
    > "saved" settings, even if it does not help me with the core problem of
    > network connectivity.


    Unless you use the wallet, you cannot expect NM to work correctly!

    The b43 driver works correctly in most cases, and certainly does for the
    14e4:4315 device, which is likely what you have. Note that stating that you have
    a BCM4312 is not sufficient.

    Your other option is to install the compat-wireless package, which will get you
    the latest version of b43.


  10. #10

    Default Re: Wireless disconnecting randomly on 12.1

    Hi again,

    Excuse the delay in replying; just too much work to do, no time for the important things in life ;-).

    Having said that, I am close to giving up with this issue - it is just so random, that I end up going round in circles. I have tried with/without Kwallet active, with YaST/traditional ifup/KDE3 wireless manager. Nothing seems to help. Just to summarize: my SSID is not always discovered by NM, but when it does it will not connect. On the occasional successful connection (when I can see the SSID), the card gets an IP from the router then drops the connection immediately after the first lookup (no route), even though NM says I am still connected...

    Here is a summary of where I am:

    Router: Netgear WNDR3700
    Security: WPA2/Personal

    kernel:
    Code:
    gee@tamale:~> uname -r
    3.1.0-1.2-desktop
    Installed packages:

    • b43-firmware (packman: 4.174.64.19-3.2-noarch)
    • b43-cutter (oSuSE: 012-15.1.2-x86-64)
    • compat-wireless-kmp-desktop (oSuSE: 3.2_k3.1.0_1.2-4.1-x86_64)
    • compat-wireless-kmp-scripts (oSuSE: 3.2-4.1-noarch)



    Drivers:
    Code:
    04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
            Subsystem: Dell Wireless 1397 WLAN Mini-Card [1028:000c]
            Kernel driver in use: b43-pci-bridge
    Code:
    [   15.172527] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
    [   15.200150] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    [   15.200966] Registered led device: b43-phy0::tx
    [   15.200992] Registered led device: b43-phy0::rx
    [   15.201015] Registered led device: b43-phy0::radio
    [   15.201034] Broadcom 43xx driver loaded [ Features: PMNLS ]
    [   15.246181] ifup[808]: Service network not started and mode 'auto' -> skipping
    Code:
    [  993.530963] wlan0: authenticate with c0:3f:0e:7a:a0:88 (try 1)
    [  993.533153] wlan0: authenticated
    [  993.553017] wlan0: associate with c0:3f:0e:7a:a0:88 (try 1)
    [  993.556160] wlan0: RX AssocResp from c0:3f:0e:7a:a0:88 (capab=0x431 status=0 aid=1)
    [  993.556166] wlan0: associated
    [  993.558890] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [  998.609941] martian source 255.255.255.255 from 192.168.1.6, on dev wlan0
    [  998.609946] ll header: ff:ff:ff:ff:ff:ff:00:04:20:22:0b:9a:08:00
    [  998.610410] martian source 255.255.255.255 from 192.168.1.6, on dev wlan0
    [  998.610415] ll header: ff:ff:ff:ff:ff:ff:00:04:20:22:0b:9a:08:00
    [ 1008.475737] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=b8:ac:6f:54:cf:88:c0:3f:0e:7a:a0:88:08:00 SRC=192.168.1.1 DST=192.168.1.10 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=6524 DF PROTO=UDP SPT=1025 DPT=137 LEN=58 
    [ 1010.955004] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1010.955008] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1011.723165] martian source 192.168.1.255 from 192.168.1.1, on dev wlan0
    [ 1011.723170] ll header: ff:ff:ff:ff:ff:ff:c0:3f:0e:7a:a0:88:08:00
    [ 1011.723358] martian source 192.168.1.255 from 192.168.1.1, on dev wlan0
    [ 1011.723361] ll header: ff:ff:ff:ff:ff:ff:c0:3f:0e:7a:a0:88:08:00
    [ 1014.786518] martian source 255.255.255.255 from 192.168.1.101, on dev wlan0
    [ 1014.786522] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1016.943088] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1016.943091] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1041.893640] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1041.893644] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1047.912251] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1047.912255] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1058.530486] martian source 255.255.255.255 from 192.168.1.6, on dev wlan0
    [ 1058.530490] ll header: ff:ff:ff:ff:ff:ff:00:04:20:22:0b:9a:08:00
    [ 1058.531302] martian source 255.255.255.255 from 192.168.1.6, on dev wlan0
    [ 1058.531306] ll header: ff:ff:ff:ff:ff:ff:00:04:20:22:0b:9a:08:00
    [ 1070.901864] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=b8:ac:6f:54:cf:88:c0:3f:0e:7a:a0:88:08:00 SRC=192.168.1.1 DST=192.168.1.10 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=6527 DF PROTO=UDP SPT=1025 DPT=137 LEN=58 
    [ 1072.860212] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1072.860216] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1074.665867] martian source 255.255.255.255 from 192.168.1.101, on dev wlan0
    [ 1074.665873] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1078.848183] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1078.848189] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1103.798781] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1103.798786] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1109.816482] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1109.816487] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1118.435285] martian source 255.255.255.255 from 192.168.1.6, on dev wlan0
    [ 1118.435290] ll header: ff:ff:ff:ff:ff:ff:00:04:20:22:0b:9a:08:00
    [ 1118.435700] martian source 255.255.255.255 from 192.168.1.6, on dev wlan0
    [ 1118.435704] ll header: ff:ff:ff:ff:ff:ff:00:04:20:22:0b:9a:08:00
    [ 1128.119173] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=b8:ac:6f:54:cf:88:c0:3f:0e:7a:a0:88:08:00 SRC=192.168.1.1 DST=192.168.1.10 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=6530 DF PROTO=UDP SPT=1025 DPT=137 LEN=58 
    [ 1134.548414] martian source 255.255.255.255 from 192.168.1.101, on dev wlan0
    [ 1134.548419] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1134.766383] martian source 192.168.1.255 from 192.168.1.101, on dev wlan0
    [ 1134.766387] ll header: ff:ff:ff:ff:ff:ff:00:24:21:dd:19:37:08:00
    [ 1139.112293] ieee80211 phy0: wlan0: No probe response from AP c0:3f:0e:7a:a0:88 after 500ms, disconnecting.
    [ 1139.160347] cfg80211: Calling CRDA to update world regulatory domain
    [ 1139.165282] cfg80211: World regulatory domain updated:
    [ 1139.165287] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 1139.165292] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 1139.165296] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [ 1139.165300] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [ 1139.165304] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 1139.165308] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 1140.645156] wlan0: authenticate with c0:3f:0e:7a:a0:88 (try 1)
    [ 1140.844889] wlan0: authenticate with c0:3f:0e:7a:a0:88 (try 2)
    [ 1141.044460] wlan0: authenticate with c0:3f:0e:7a:a0:88 (try 3)
    [ 1141.244075] wlan0: authentication with c0:3f:0e:7a:a0:88 timed out
    [ 1147.647218] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 1/3)
    [ 1147.846011] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 2/3)
    [ 1148.045606] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 3/3)
    [ 1148.245236] wlan0: direct probe to c0:3f:0e:7a:a0:88 timed out
    [ 1152.003610] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 1/3)
    [ 1152.202390] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 2/3)
    [ 1152.401938] wlan0: direct probe to c0:3f:0e:7a:a0:88 (try 3/3)
    [ 1152.601482] wlan0: direct probe to c0:3f:0e:7a:a0:88 timed out

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •