From: "Nikita N." <nikitan@operamail.com>
To: backports@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: 3.13 various backports bugs
Date: Sat, 30 Nov 2013 04:45:30 -0800 [thread overview]
Message-ID: <1385815530.23776.53787977.56B183FC@webmail.messagingengine.com> (raw)
Hi dear maintainers of backports :) I have few bugs to report, Ill try
to be as fast as I can.
- Bug #1:
Im running on standard Slitaz4, kernel 2.6.37-slitaz, updating modules,
the following script:
./backports-3.13-rc1-1/scripts/compress_modules.sh
the "if" is not able to detect the present compression, as result the
new modules are not compressed, and get mixed with the old ones
compressed, resulting in lots of errors.
My actual workaround is just to delete the "if" line.
The issue is present systematically in all backports releases, since the
switch from compat-drivers.
The compress_modules script into 3.9 is instead working good.
- 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/
- Bug #3:
New dependance has been added, CRYPTO_CCM, which denies all modules
compilation based on MAC80211.
The dependance is set in ./backports-3.13-rc1-1/net/mac80211/Kconfig
On Slitaz4, such kernel config is not set, hence its needed to edit
manually the kernel .config in order to enable it.
After enabling, modules compilation goes all right.
Hence, or CRYPTO_CCM is useless, or its needed to show a warning to the
user at Kconfig runtime, in order to take the necessary measures.
It took forever (even for me!) to find that bug, which btw was denying
the compilation of my Realtek modules.
- Bug #4:
Repeated back-slashes "//" are present into script-makefile files, you
can see them appear for example running "make alldefconfig & make
install":
[...]
COMPRESS /lib/modules/2.6.37-slitaz//updates/compat/compat.ko
gzip: can't open
'/lib/modules/2.6.37-slitaz//updates/compat/compat.ko.gz': File exists
[...]
- Bug #5:
Cosmetic bug, in file ./backports-3.13-rc1-1/Makefile, the following
line is duplicated:
@echo " allyesconfig - New config where all options are accepted
with yes"
Hope all is clear, now I have to leave you because my baby sh*t the
diapers so much all is getting out and my wife is shouting at me!
aaargh! :D
Thanks for your attention :)
--
http://www.fastmail.fm - The professional email service
next reply other threads:[~2013-11-30 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 12:45 Nikita N. [this message]
2013-11-30 13:00 ` 3.13 various backports bugs 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.
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=1385815530.23776.53787977.56B183FC@webmail.messagingengine.com \
--to=nikitan@operamail.com \
--cc=backports@vger.kernel.org \
--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