public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Volker <evolker@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: b43 driver hang workaround
Date: Tue, 26 Jan 2010 14:23:16 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100126T144339-926@post.gmane.org> (raw)
In-Reply-To: 933379711001260339p6c31f345xde472c6052d4c81f@mail.gmail.com

Giuseppe Fontana <gfontana13@...> writes:

> 
> 2010/1/26 Eric Volker <evolker@...>:
> > Thought I'd post my workaround for the issue I've been experiencing. My
> > setup is as follows: Ubuntu 9.10 x86 and a BCM4318 in AP mode.
> 
> Hi Eric. So, if I'm not wrong, you successfully connected to a wi-fi
> ad-hoc network with BCM4318 and Ubuntu 9.10. I tried with my Acer 5024
> with CM4318 without success (if you want you can take a look at my
> thread "Broadcom BCM4318 AirForceOne issue - Ubuntu 9.10 on Acer
> Aspire 5024wlmi"). Are you using a laptop too? What's your wifi
> adapter model?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Sorry, I think I may have replied to this off-list. I'm using a BCM4318 PCI 
card as an access point. I've got it in mixed wpa/wpa2 mode and have had it up 
for a couple of days so far. It's a Bufflo card, though I'm not sure of the 
exact model. It is in a desktop, a Dell Dimension 4550. Thus far it has vastly 
outperformed my old DLink DIR-655. I'm quite happy, though it took me about a 
wink to iron out several kinks. I also had to use "eapol_version=1" in 
hostapd.conf to get everything working properly. If you need any further 
details, please let me know.

Eric



      reply	other threads:[~2010-01-26 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  2:27 b43 driver hang workaround Eric Volker
2010-01-26 11:39 ` Giuseppe Fontana
2010-01-26 14:23   ` Eric Volker [this message]

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=loom.20100126T144339-926@post.gmane.org \
    --to=evolker@gmail.com \
    --cc=linux-wireless@vger.kernel.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