From: Dennis Nezic <dennisn@dennisn.dyndns.org>
To: b43-dev@lists.infradead.org
Subject: BCM4318 trouble connecting to ad-hoc network
Date: Sun, 24 Oct 2010 19:18:35 -0400 [thread overview]
Message-ID: <20101024191835.7a8fb4e5.dennisn@dennisn.dyndns.org> (raw)
Sometimes, most of the time, when I try to reload/restart my wifi
interface, I get a "No active IBSS STAs" message in my syslog, and my
subsequent dhcpcd call fails "waiting for carrier". However, it does
seem to sortof still work -- if I manually run dhcpcd a few seconds
later, it works.
iw event -t:
1287961348.312835: wlan0 (phy #0): IBSS ... joined
1287961348.599939: wlan0: unknown event 19
1287961350.033722: wlan0: unknown event 1
syslog:
/etc/init.d/net.wlan0[11116]: WARNING: net.wlan0 has started, but is
inactive
kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26
kernel: wlan0: Selected IBSS BSSID ... based on configured SSID
wpa_cli: interface wlan0 CONNECTED
dhcpcd: version 5.1.3 starting
kernel: wlan0: No active IBSS STAs - trying to scan for other IBSS
networks with same SSID (merge)
dhcpcd: wlan0: waiting for carrier
However, on other rare times, when a "Trigger new scan" occurs, it all
works smoothly.
iw event -t:
1287961295.764797: wlan0 (phy #0): IBSS ... joined
1287961295.865132: wlan0: unknown event 19
syslog:
/etc/init.d/net.wlan0[10708]: WARNING: net.wlan0 has started, but is
inactive
kernel: b43-phy0: Loading firmware version 410.2160
kernel: wlan0: Trigger new scan to find an IBSS to join
kernel: wlan0: Selected IBSS BSSID ... based on configured SSID
wpa_cli: interface wlan0 CONNECTED
dhcpcd: version 5.1.3 starting
dhcpcd: wlan0: rebinding lease of 10.0.1.4
dhcpcd: wlan0: acknowledged 10.0.1.4 from 10.0.1.1
Thoughts? What triggers the trigger?
reply other threads:[~2010-10-24 23:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101024191835.7a8fb4e5.dennisn@dennisn.dyndns.org \
--to=dennisn@dennisn.dyndns.org \
--cc=b43-dev@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).