From: "John W. Linville" <linville@tuxdriver.com>
To: Sean Ongley <seanongley@nofest.net>
Cc: stable@kernel.org, linux-wireless@vger.kernel.org
Subject: Re: 2.6.30 questions of bugs??
Date: Mon, 29 Mar 2010 13:08:19 -0400 [thread overview]
Message-ID: <20100329170818.GD4984@tuxdriver.com> (raw)
In-Reply-To: <C7D61FE6.2FC%seanongley@nofest.net>
On Mon, Mar 29, 2010 at 09:14:14AM -0700, Sean Ongley wrote:
> Bugs, I don't know if its bugs. I'm just very confused about installing
> these drivers. I feel like I'm trying what you say and what the help files
> and forums say, its all very confusing. Isn't there a simple command that
> will work? If not, what is THE ONE command or procedure that works? Please
> help me. This wireless just isn't being read and nobody in the linux
> community seems to put the install procedure simply. I believe if someone
> could very simply and very clearly relate the procedure for installing
> something as simple as a driver, it would help newcomers to the system
> tremendously.
I'm sorry, but I doubt if anyone here is going to be able to help
you either -- at least not without more information. Most likely
you should consult with the support resources for whatever Linux
distribution you are using. At the very least we would have to know
what hardware you are using and whether or not your kernel is built
to include the appropriate driver (if it exists).
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-03-29 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:14 2.6.30 questions of bugs?? Sean Ongley
2010-03-29 16:56 ` [stable] " Greg KH
2010-03-29 17:08 ` John W. Linville [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=20100329170818.GD4984@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=seanongley@nofest.net \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).