I have a Linksys WUSB11 version 3 wifi adapter... uses the at76c503a driver (requires atmel_firmware as these devices must have firmware loaded by driver). The lack of this driver makes doing Stage1/Stage2 impossible; and the only real work to get Gentoo working is to do a Stage3 install... boot into the bare bones Linux install... and issue: # emerge at76c503a They must then fetch -- one at a time unless they know what to look for -- the files on another computer and put on floppy / CD -- and put them in the distfiles folder. Requesting these two (fairly small) packages be included on LiveCD for those with at76c503a based wifi. I think this is already in the hardened sources InstallCD; or so someone on #gentoo said. I'm filing this under major; as it prevents somebody from doing a Stage1 or Stage2 install. I'm guessing this constitutes a major broken feature. Reproducible: Always Steps to Reproduce: 1. Boot into LiveCD 2. Try to setup your atmel based usb wifi 3. Bang head on nearest blunt object Though I'm pretty sure it's useless in this case; I'll include emerge --info for kicks and giggles: Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.12-gentoo-r6 i686) ================================================================= System uname: 2.6.12-gentoo-r6 i686 Celeron (Mendocino) Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.5, 2.4.2 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-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aac aim alsa apm arts avi berkdb bitmap-fonts bzip2 bzlib clamav codecs crypt cups dhcp divx4linux dvd dvdread eds emboss encode foomaticdb fortran freetype gdbm gif gimp gkrellm gnome gpm gstreamer gtk gtk2 icq imlib ipv6 java jpeg kde kdeenablefinal libclamav libg++ libwww live mad mikmod mmx motif mozilla mp3 mpeg mplayer msn ncurses nls offensive ogg oggvorbis opengl oss pam pdf pdflib perl png python qt quicktime rar readline sdl spell ssl svg tcpd truetype truetype-fonts type1-fonts usb vorbis wifi win32codecs xml2 xmms xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Actually, it is a feature request, making it an enhancement. This driver was not stable at release time for 2005.1, so it was not included. It will not be included in any release until it goes stable, as we do not artificially stabilize anything for the releases. Also, if you can still install networkless, then this isn't a "bug" per se, but will always be a feature request. There's nothing preventing you from installing Gentoo, just from installing from a stage1/stage2. ;] At any rate, I have this in my list of wireless packages to add, in fact, I'm pretty sure I've already had a bug for this opened before, but I can't find it. I would suggest filing a separate bug to have the package stabilized, which would be assigned to the package maintainers, and set it up to block this bug. That way I'll be notified when the maintainers stabilize the package and will know to include it on the releases.
What is the licensing policy for the stuff we put on the live cds? Looking at the license the firmware is not open source but we are allowed to redistribute it.
If there are no redistribution restrictions, then we redistribute it. We already do this for the ipw2x00 firmwares.
WONTFIX due to bug #114419 Feel free to REOPEN this if a version of the driver ever makes it to stable.
