From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Julien HENRY" <henryju@yahoo.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Re : Not associated with Intel 4965
Date: Sat, 1 Nov 2008 14:31:07 -0700 [thread overview]
Message-ID: <43e72e890811011431j1f286d5ewf8985373e1312657@mail.gmail.com> (raw)
In-Reply-To: <170039.58975.qm@web28509.mail.ukl.yahoo.com>
On Sat, Nov 1, 2008 at 1:48 PM, Julien HENRY <henryju@yahoo.fr> wrote:
>> We no longer have iwl4965, the new name is iwlagn, try that.
>
> Not better (please note that I've upgraded to kernel 2.6.27.4-desktop-0.uc1mnb since my last post):
>
> # modprobe iwlagn
> WARNING: Error inserting iwlcore (/lib/modules/2.6.27.4-desktop-0.uc1mnb/updates/drivers/net/wireless/iwlwifi/iwlcore.ko): Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting iwlagn (/lib/modules/2.6.27.4-desktop-0.uc1mnb/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko.gz): Unknown symbol in module, or unknown parameter (see dmesg)
I see a discrepancy on the directory where the modules are being
picked up on. The ones that should be used are the ones in updates for
compat-wireless, your kernel drivers are under kernel. Lets try this
to be sure:
cd /lib/modules/2.6.27.4-desktop-0.uc1mnb/kernel/drivers/net/wireless/iwlwifi
rename everything there from foo to foo.ignore, for example, then run
sudo depmod -ae
and finally then try unloading all the wireless modules and then try
loading iwlagn.
prev parent reply other threads:[~2008-11-01 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 20:48 Re : Not associated with Intel 4965 Julien HENRY
2008-11-01 21:31 ` Luis R. Rodriguez [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=43e72e890811011431j1f286d5ewf8985373e1312657@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=henryju@yahoo.fr \
--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