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: Thu, 25 Oct 2007 16:15:37 +0200 [thread overview]
Message-ID: <4720A509.2070708@sgi.com> (raw)
In-Reply-To: <1193319925.5542.8.camel@localhost.localdomain>
Dan Williams wrote:
> You'll need to update more than just the kernel. There were issues with
> Test 3 for udev and network init scripts that didn't distinguish between
> the wmasterX and wlanX interfaces, and since both have the same MAC
> address things got confused.
>
> Try updating to the latest Rawhide bits rather than using Test 3. The
> make sure you remove the following files:
>
> rm -f /etc/sysconfig/network-scripts/ifcfg-wlan0*
> rm -f /etc/udev/rules.d/70-persistent-net.rules
>
> The initscripts don't care what's after the ifcfg- (because you could
> name it ifcfg-Home or ifcfg-Some-Other-Place, it doesn't have to be the
> device name) and therefore even a ifcfg-wlan0.bak will cause the problem
> too.
Hi Dan,
I think I have the latest updates, provided fedora/core/development is
rawhide? I got udev-116-3.fc8 and initscripts-8.60-1.
That said, I am pretty sure this is a driver issue - even right after
the install, when Fedora hadn't figured out the device and didn't try
to load the module, it didn't find the device either unless I loaded it,
unloaded it and loaded it again.
Cheers,
Jes
next prev parent reply other threads:[~2007-10-25 14:15 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 [this message]
2007-10-25 17:32 ` Dan Williams
2007-10-26 8:05 ` Jes Sorensen
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=4720A509.2070708@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).