After testing with a Broadcom Corporation BCM4318 [AirForce One 54g] Rev. 2 PCI controller in both 32- and 64-bit I have yet to find detectable differences in operation or stability. Reproducible: Always Steps to Reproduce: 1. echo "=wpa_supplicant-0.3.9-r1 ~amd64" >> /etc/portage/package.keywords 2. emerge =wpa_supplicant-0.3.9-r1 3. Configure wireless access. 4. Use wireless access. Actual Results: No compilation errors or detectable flaws in operation. Expected Results: As actual. 32-bit drivers installed using ndiswrapper copy of bundled wireless driver. 64-bit drivers installed using ndiswrapper copy of Acer 64-bit Broadcom Corporation BCM4318 [AirForce One 54g] driver. Tested on a HP zv6170ca Laptop for five hours straight. 'emerge info' output: Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-gentoo-r7-titan-r1 x86_64) ================================================================= System uname: 2.6.12-gentoo-r7-titan-r1 x86_64 AMD Athlon(tm) 64 Processor 3800+ Gentoo Base System version 1.6.13 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O3 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /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/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig cccache distlocks sandbox sfperms strict userpriv" GENTOO_MIRRORS="ftp://gentoo.ccccom.com/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac aalib acpi alsa apic arts ati avi berkdb bitmap-fonts bzip2 cdparanoia cdr cdrw crypt cups curl dbus directfb dv dvb dvd dvdr dvdread eds encode examples exif fam fbcon flac foomaticdb fortran gif gimpprint gpm gstreamer gtk gtk2 gtkhtml hal imagemagick imlib ipv6 java javascript jpeg junit kde lcms libcaca lzw lzw-tiff mad matroska mng mozsvg mp3 mpeg mysql ncurses network nls offensive ogg oggvorbis opengl pam pcmcia pda pdflib perl pic png ppds prelink python qt quicktime radeon readline rtc samba scanner sdl spell sqlite ssl svg tcpd theora tiff truetype-fonts type1-fonts usb userlocales utf8 vorbis wmf xanim xml2 xmms xpm xscreensaver xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
I have also experienced no problems at all using wpa_supplicant-0.3.9-r1 on my 64-bit system. I was using 0.3.8 since late February with no issues at all and I moved to 0.3.9-r1 as soon as it was marked stable on x86. I am using a Belkin 54g card which lspci reports as the following: 0000:00:07.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) I have been doing this using ndiswrapper with the 64-bit windows drivers available from http://www.linuxant.com/driverloader/drivers.php (first link in the table). My ndiswrapper versions have matched stable x86 since Februrary. Portage 2.0.51.22-r2 (default-linux/amd64/2005.0/no-multilib, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12-gentoo-r10 x86_64) ================================================================= System uname: 2.6.12-gentoo-r10 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 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.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /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/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LC_ALL="en_AU.UTF-8" LINGUAS="en_GB" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="amd64 X aac alsa avi bash-completion berkdb bitmap-fonts cdr cjk crypt curl dvd dvdr eds emboss exif fam flac foomaticdb fortran gif gtk2 hal ieee1394 imagemagick imlib java jpeg kde kdeenablefinal lm_sensors lzw lzw-tiff mad motif mp3 ncurses nls nptl ogg oggvorbis opengl pam pdflib perl pic png python quicktime readline samba sdl spell ssl tcpd tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis xine xml2 xpm xv zlib linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, PORTDIR_OVERLAY
we're currently testing a new alias system, sorry for the bugspam
Not working under x86: http://bugs.gentoo.org/show_bug.cgi?id=112853#c7
(In reply to comment #3) > Not working under x86: http://bugs.gentoo.org/show_bug.cgi?id=112853#c7 That is totally unrelated to this bug report. Please stop posting comments on random bug reports that look vaguely like something you might think is an issue. Thanks.
> That is totally unrelated to this bug report. Please stop posting comments on > random bug reports that look vaguely like something you might think is an issue. > Thanks. Yeah. I agree this is the wrong place for this buy. I'll investigate further and open a new bug if necessary.
Version 0.3.9-r1 is no longer in portage. Currently (as of 2006-03-06) the current versions are: 0.4.7 stable on x86 and PPC 0.4.8 stable on x86 0.5.2 unstable on all We need to shift focus to getting one of these versions marked as stable. The 0.4.7 version has been stable on x86 and PPC for a while now and would be a good candidate for this. I have tested versions 0.4.8 and 0.5.2 with an INPROCOMM IPN2220 using ndiswrapper for a while now (accessing both WPA-PSK and clear networks). I have had no issues with either version. emerge info as follows: Gentoo Base System version 1.6.14 Portage 2.0.54 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r7 x86_64) ================================================================= System uname: 2.6.15-gentoo-r7 x86_64 AMD Turion(tm) 64 Mobile Technology MT-37 dev-lang/python: 2.3.5-r2, 2.4.2 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-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -march=k8" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /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/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe -march=k8" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://mirrors.blueyonder.co.uk/mirrors/gentoo ftp://ftp.mirrorservice.org/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac acpi alsa apache2 audiofile avi bash-completion berkdb bitmap-fonts bluetooth bzip2 cdparanoia cdr crypt cups divx4linux doc dri dvd dvdr eds emboss encode expat fam ffmpeg foomaticdb fortran ftp gd gif glut gpm gstreamer gtk2 gtkhtml idn imagemagick imap imlib innodb ipv6 java jikes jpeg junit kde lcms ldap lzw lzw-tiff mad mime mng mp3 mpeg msn mysql mysqli ncurses nls ogg oggvorbis openal opengl pam pcmcia pcre pdflib perl php png python qt quicktime readline samba sdl spell ssl svg tcpd tiff truetype truetype-fonts type1-fonts udev usb vcd visualization vorbis wifi xine xml xml2 xmms xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
(In reply to comment #6) > 0.4.7 stable on x86 and PPC > 0.4.8 stable on x86 > 0.5.2 unstable on all > > We need to shift focus to getting one of these versions marked as stable. The > 0.4.7 version has been stable on x86 and PPC for a while now and would be a > good candidate for this. While 0.4.7 of course is a good candidate for stabilization on amd64 I see no reason not to mark 0.4.8 stable. Version 0.4.x is the current stable series of releases from upstream, only bug fixes are applied to these releases. Version 0.5.x is the current development series of releases from upstream and should not yet be considered for being marked stable on any archs. Thank you for your feedback. Hopefully someone from the amd64 herd will soon find a chance to keyword wpa_supplicant-0.4.x accordingly.
can't really test this because i don't have the hardware to, but i never heard of problems with it, so... __ | / / | / / / ___ _ _ ___|(___ (___| ___ (___ ___ (___ ( ___ | )| | )| )| ) ) |___ | | )| )| |___) |__/|| / |__/ |__/ / __/ |__ |__/||__/ | |__
