From: Jes Sorensen <jes@sgi.com>
To: Dan Williams <dcbw@redhat.com>
Cc: yi.zhu@intel.com, linux-wireless@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: iwl4965 detection problem
Date: Fri, 26 Oct 2007 10:05:58 +0200 [thread overview]
Message-ID: <47219FE6.70900@sgi.com> (raw)
In-Reply-To: <1193333545.2111.8.camel@localhost.localdomain>
Dan Williams wrote:
> I've had this same problem with one machine and there were problems with
> those two files. I fixed it on that machine (and was fixed on a few
> others using this procedure) by removing those two files and rebooting.
>
> The symptom is that the driver loads and recognizes the card, but no
> wireless devices show up to userspace (via iwconfig, ifconfig, or
> in /sys/class/net) because device renames by udev and/or init scripts
> stomped over them (like trying to rename wmaster0 -> eth1 and then
> renaming wlan0 -> eth1 but failing because it was already taken).
>
> Try killing those two files, making sure you're up to date, then
> restarting.
Hi Dan,
I tried that, but no go :-( Even before the card was detected by Fedora,
when I manually loaded the iwl4965 module, nothing showed up in
ifconfig -a, I had to unload/reload for anything to happen.
Cheers,
Jes
next prev parent reply other threads:[~2007-10-26 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 13:37 iwl4965 detection problem Jes Sorensen
2007-10-25 13:45 ` Dan Williams
2007-10-25 14:15 ` Jes Sorensen
2007-10-25 17:32 ` Dan Williams
2007-10-26 8:05 ` Jes Sorensen [this message]
2007-10-26 12:30 ` John W. Linville
2007-10-26 12:45 ` Jes Sorensen
2007-10-26 14:10 ` Jes Sorensen
2007-10-26 14:41 ` John W. Linville
2007-10-26 14:43 ` Jes Sorensen
2007-10-26 15:17 ` Jes Sorensen
2007-10-26 15:23 ` dragoran
2007-10-26 16:50 ` John W. Linville
2007-10-29 1:14 ` Zhu Yi
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=47219FE6.70900@sgi.com \
--to=jes@sgi.com \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.com \
--cc=yi.zhu@intel.com \
/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).