<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>104100</bug_id>
          
          <creation_ts>2005-08-28 22:49 0000</creation_ts>
          <short_desc>ieee80211 will not emerge due to a requirement for CRYPTO_AES_586</short_desc>
          <delta_ts>2005-09-02 10:33:23 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Unspecified</component>
          <version>2005.0</version>
          <rep_platform>AMD64</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <keywords>InCVS</keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>john.mcclure@tyan.com.tw</reporter>
          <assigned_to>mobile@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>john.mcclure@tyan.com.tw</who>
            <bug_when>2005-08-28 22:49:42 0000</bug_when>
            <thetext>I am using a vanilla 2.6.13-rc3 kernel on a Ferrari 3400 notebook. I have the
wireless working great except that it can&apos;t do WEP or any encryption. I tried
emerging ieee80211 for WEP support and got this message:

* ieee80211-1.0.3 requires support for AES cipher algorithms (i586) (CONFIG_CRY
PTO_AES_586).
 * This option is called CONFIG_CRYPTO_AES in kernels prior to 2.6.8.

Now I know I compiled in AES crypto support. But the issue is that it is this:

less /usr/src/linux/.config |grep CRYPTO

CONFIG_CRYPTO_AES_X86_64=y

ieee80211 does not like x86_64. Should there be an ebuild that supports this
option in the kernel?

Reproducible: Always
Steps to Reproduce:
1. emerge ieee80211
2.
3.

Actual Results:  
* Found sources for kernel version:
 *     2.6.13-rc3
 * ieee80211-1.0.3 requires support for AES cipher algorithms (i586)
(CONFIG_CRYPTO_AES_586).
 * This option is called CONFIG_CRYPTO_AES in kernels prior to 2.6.8.

!!! ERROR: net-wireless/ieee80211-1.0.3 failed.
!!! Function pkg_setup, Line 45, Exitcode 0
!!! CONFIG_CRYPTO_AES_586 support not detected
!!! If you need support, post the topmost build error, NOT this status message.

Expected Results:  
Expected to support x86_64 AES.

Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r1,
2.6.13-rc3 x86_64)
=================================================================
System uname: 2.6.13-rc3 x86_64 Mobile AMD Athlon 64 Processor 3000+
Gentoo Base System version 1.12.0_pre6
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.5-r1, 2.4.1-r1
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS=&quot;amd64&quot;
AUTOCLEAN=&quot;yes&quot;
CBUILD=&quot;x86_64-pc-linux-gnu&quot;
CFLAGS=&quot;-march=k8 -pipe -fomit-frame-pointer -O2&quot;
CHOST=&quot;x86_64-pc-linux-gnu&quot;
CONFIG_PROTECT=&quot;/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/bind
/var/qmail/control&quot;
CONFIG_PROTECT_MASK=&quot;/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d&quot;
CXXFLAGS=&quot;-march=k8 -pipe -fomit-frame-pointer -O2&quot;
DISTDIR=&quot;/usr/portage/distfiles&quot;
FEATURES=&quot;autoconfig distlocks sandbox sfperms strict&quot;
GENTOO_MIRRORS=&quot;http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo&quot;
MAKEOPTS=&quot;-j2&quot;
PKGDIR=&quot;/usr/portage/packages&quot;
PORTAGE_TMPDIR=&quot;/var/tmp&quot;
PORTDIR=&quot;/usr/portage&quot;
SYNC=&quot;rsync://rsync.gentoo.org/gentoo-portage&quot;
USE=&quot;amd64 X a52 aac aalib acpi alsa apache2 avi bash-completion berkdb
bitmap-fonts bonobo browserplugin cdr crypt cups curl dts dvd dvdr dvdread dxr3
eds encode esd fam flac foomatic foomaticdb fortran g77 gd gdbm gif gpm
gstreamer gtk gtk2 imagemagick imlib innodb ipv6 ithreads java jpeg junit kde
ldap libcaca libwww lzw lzw-tiff mad mozilla mp3 mpeg mysql ncurses nls nptl
nsplugin ogg oggvorbis opengl oss pam pdflib perl php png postgres ppds pthreads
python qt quicktime readline samba sdl spell ssl tcpd tetex tiff truetype
truetype-fonts type1-fonts usb userlocales v4l vcd vorbis winbind xine xinerama
xml xml2 xmms xpm xv xvmc zlib userland_GNU kernel_linux elibc_glibc&quot;
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>tsunam@gentoo.org</who>
            <bug_when>2005-08-28 22:54:31 0000</bug_when>
            <thetext>vanilla kernel is not officially supported in gentoo. As per the gentoo
documentation.

Important: Use sys-kernel/gentoo-sources line of kernels! It has AMD64-specific
patches, as well as additional enhancements. We will not be able to support you
if you use another source.

I&apos;m fairly sure that if you were to use the gentoo-sources, you&apos;d not be having
this isue. Also you could look into the actual config file for ieee80211 and I&apos;m
sure you could modify it to use AES_x86_64 instead of the AES_586.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>henrik@brixandersen.dk</who>
            <bug_when>2005-08-29 01:36:02 0000</bug_when>
            <thetext>Not correct. Vanilla kernels (as in sys-kernel/vanilla-sources) are supported.

Reporter, can you try changing the ebuild to check for CONFIG_CRYPTO_AES_X86_64
instead of CONFIG_CRYPTO_AES_586 and tell me if the ieee80211 kernel modules
compiles and works with that?

If it does, the check should of course be extended to check for the X86_64
version of the AES algorithm as well.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>tsunam@gentoo.org</who>
            <bug_when>2005-08-29 03:11:41 0000</bug_when>
            <thetext>brix, the vanilla comment (my fault for not making it clear) was in relation to
the x86_64, which is from the amd64 profile. The only supported kernel for the
amd64 team is as the note i posted, from the Technotes.

Again my bad :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>buison01@ie.hva.nl</who>
            <bug_when>2005-08-31 04:00:29 0000</bug_when>
            <thetext>This bug has popped up again.
 
I am still getting this error with gentoo-sources-2.6.13, so the problem is
*not* limited to vanilla kernels.

I compiled ieee80211 manually on this kernel without any problems (extracting
the tarball and running make;make install). Clearly, this is a bug in the ebuild
(1.0.3). The script needs to be corrected to check the arch first, instead of
blindly assuming x86 and demanding CONFIG_CRYPTO_AES_586.

The only remaining question that bugs me is why the same ebuild worked fine on
2.6.12-gentoo-r9. And why am I the only one to report this problem again? Are
there that few x86-64 users with wifi adapters running Gentoo at the moment?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>henrik@brixandersen.dk</who>
            <bug_when>2005-09-02 10:33:01 0000</bug_when>
            <thetext>Fixed in ieee80211-1.0.3-r1.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>henrik@brixandersen.dk</who>
            <bug_when>2005-09-02 10:33:23 0000</bug_when>
            <thetext>Thank you for reporting.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>