All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince Radice <vhradice@cfl.rr.com>
To: b43-dev@lists.infradead.org
Subject: Wireless Problem
Date: Thu, 09 Feb 2012 14:00:06 -0500	[thread overview]
Message-ID: <4F3417B6.4060005@cfl.rr.com> (raw)

Hi,

     I am having a problem trying to get a Netgear WNA3100 adapter 
working.  I have probably been through 100+ posts and threads trying to 
figure out what is happening.  I have attached two files.  One contains 
the output from dmesg.  The other has the output from several commands 
as requested in the doc.

     I have the latest of all of the commonly used software - 
ndiswrapper, Broadcom STA, Fedora FC16 with all updates, b43-fwcutter, 
and a lot more that I can't remember.

     The pc I am using has an ethernet connection.  I am trying to get 
the wireless working there.  I am not able to successfully connect to my 
home wireless network.  I can somewhat connect by manually assigning the 
IP address.  It will connect and assign an IP address but I can't do 
anything.  If I try ping, I get host unreachable.

     My question stems from a lack of what to do.  Looking at your 
documentation, I see references to b43-fwcutter.  Do I have to do 
something with that program? I have read what it does, but no where have 
I read anything about me having to do something to get the firmware.

     Another question is which drivers should I be using - Broadcom STA, 
b43, or ndiswrapper with windows drivers for xp?  I have tried to get 
all of these working at some point.  I may have tried running several at 
the same time as I don't know how to check what is being used.  I can 
list what is installed.

     Should I open a thread some place?  If so, I was thinking the 
Networking forum at Fedora.  I found your site listed in one recent post 
there.  I could add to it.

     Thanks in advance for any help and advice you give.

Vince Radice
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: networkfails.txt
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20120209/01c5f2c2/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: WirelessFailure.txt
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20120209/01c5f2c2/attachment-0003.txt>

             reply	other threads:[~2012-02-09 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 19:00 Vince Radice [this message]
2012-02-09 19:17 ` Wireless Problem Rafał Miłecki
2012-02-09 19:38   ` Arend van Spriel
2012-02-09 20:55     ` Vince Radice
2012-02-10  6:13       ` Rafał Miłecki
  -- strict thread matches above, loose matches on Subject: below --
2010-09-12 12:32 wireless problem Simon Baker
2010-09-12 17:37 ` Gábor Stefanik

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=4F3417B6.4060005@cfl.rr.com \
    --to=vhradice@cfl.rr.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.