From: Maximilian Decker <burbon04@gmx.de>
To: linux-laptop@vger.kernel.org, linux-wlan-user@lists.linux-wlan.com
Subject: linux-wlan-ng and kernel 2.6.10-rc3
Date: Thu, 16 Dec 2004 11:29:49 +0100 [thread overview]
Message-ID: <41C1639D.4040303@gmx.de> (raw)
Hi all,
sorry for posting that again, but my recent mail seemed to get
lost somewhere (at least it is not shown in the archives ....)
... please apologize if some of you get it twice ...
----------
Like many others I also had problems with prism2 based pcmcia cards
and the 2.6.10 kernels - the logs showed messages about unresolved
symbols and the card just refused to work.
It turned out that internal changes in the recent linux kernels
simply broke compatibility to software like linux-wlan-ng.
(well, maybe the next version of linux-wlan-ng will solve that issue,
but I do not know when it will be released .....
.... if someone knows, please let me know - thanks)
If you want to use linux-wlan-ng-0.2.1pre23 with linux 2.6.10-rc3, you
might want to try my patch that brings back the deprecated "dev_get"
and again exports hotplug_path. I know it is kind of ugly to workaround
like that, but I did not want to wait for the next linux-wlan-ng release
;-) Well, it works for me...
if you are interested, you can get it here:
http://burbon04.gmxhome.de/linux/files/2.6.10_old_hotplug.diff.gz
for more information see:
http://burbon04.gmxhome.de/linux/2.6.10_hotplug.html
(use it at your own risk ! absolutely no warranty ;-)
Cheers,
- Maximilian
next reply other threads:[~2004-12-16 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 10:29 Maximilian Decker [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-15 8:12 linux-wlan-ng and kernel 2.6.10-rc3 Maximilian Decker
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=41C1639D.4040303@gmx.de \
--to=burbon04@gmx.de \
--cc=linux-laptop@vger.kernel.org \
--cc=linux-wlan-user@lists.linux-wlan.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 read-only IMAP folder(s) and NNTP newsgroup(s).