From: "Nikita N." <nikitan@operamail.com>
To: Hauke Mehrtens <hauke@hauke-m.de>, backports@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: 3.13 various backports bugs
Date: Sat, 30 Nov 2013 06:21:58 -0800 [thread overview]
Message-ID: <1385821318.11810.53811117.0E0E19AF@webmail.messagingengine.com> (raw)
In-Reply-To: <5299E184.1020302@hauke-m.de>
follow answers
On Sat, Nov 30, 2013, at 05:00 AM, Hauke Mehrtens wrote:
> > - Bug #2:
> > eeprom modules are missing into 3.13.
> > This issue is present systematically in all backports releases, since
> > the switch from compat-drivers.
> > It could be a wireless bug only, or a backports bug only, or both.
> > Anyway, eeprom module is vital for correct interface detection.
> > Into 3.9 the eeprom modules are located in
> > ./compat-drivers-3.9-rc4-2-su/drivers/misc/eeprom/
>
> This should be included in your kernel you are compiling against
> otherwise you wouldn't be able to build rtl8187.
>
> There was a bug in backports regarding EEPROM_93CX6, could you please
> try backports-20131122-2 and report back if the problem is still there.
just did it, same issue.
also in backports-20131122-2 eeprom modules are missing.
At this point I have the suspect that eeprom libraries builtin Slitaz4
are bugged, and the bug is capable of persistent damage.. probably the
bad frames filter in monitor mode im suffering on my two rtl8187, is
caused by that..?
If that would be confirmed, Slitaz4 community has to be warned asap!
If I can help more, please fell free to ask :)
--
http://www.fastmail.fm - Accessible with your email software
or over the web
prev parent reply other threads:[~2013-11-30 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 12:45 3.13 various backports bugs Nikita N.
2013-11-30 13:00 ` Hauke Mehrtens
2013-11-30 13:42 ` Nikita N.
2013-11-30 16:46 ` Hauke Mehrtens
2013-11-30 17:41 ` Nikita N.
2013-11-30 14:21 ` Nikita N. [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=1385821318.11810.53811117.0E0E19AF@webmail.messagingengine.com \
--to=nikitan@operamail.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--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