Sorry. Not sure where this bug ought to go. The packages 'madwifi-driver' (which compiles kernel modules) depends on 'ieee80211', but this is apprarently not reflected in the dependency list. The build succeeds, but the kernel modules fail to load, because the kernel procedures of `ieee80211' do not necessarily exist. Because this was requested ... Portage 2.0.54 (default-linux/x86/2005.1, gcc-3.3.5-20050130, glibc-2.3.5-r2, 2.6.12-gentoo-r6--andreis-second-compile i686) ================================================================= System uname: 2.6.12-gentoo-r6--andreis-second-compile i686 Intel(R) Xeon(TM) CPU 3.06GHz Gentoo Base System version 1.6.14 dev-lang/python: 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.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -pipe -march=pentium4 -fomit-frame-pointer" CHOST="i686-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/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://adelie.polymtl.ca/ ftp://cs.ubishops.ca/pub/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://mirror.espri.arizona.edu/gentoo/" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts audiofile avi berkdb bitmap-fonts bzip2 crypt cups curl directfb dri eds emboss encode esd exif expat fam foomaticdb fortran gd gdbm gif glut gnome gpm gstreamer gtk gtk2 gtkhtml idn imlib ipv6 isdnlog java jpeg kde lcms libg++ libwww mad mikmod mng motif mozilla mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pcre pdflib perl png pppd python qt quicktime readline recode samba sdl spell ssl tcpd tetex tiff truetype truetype-fonts type1-fonts udev vorbis xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
False. The madwifi-driver does not depend on the ieee80211 package, it provides it's own implementation. What made you think it needed ieee80211?
(In reply to comment #1) > False. The madwifi-driver does not depend on the ieee80211 package, it provides > it's own implementation. > > What made you think it needed ieee80211? > You're right. Why I thought so: I emerged 'iwconfig' but it wouldn't execute. Being a novice, I didn't really know what was going on, but I could not see the network interface my wireless card from 'iwconfig', so I assumed the kernel needed additional support for its particular chipset. I thought I needed madwifi in addition because its docs seemed to suggest that it supported my chipset explicitly, where `iwconfig''s docs did not indicate this explicitly. Without understanding that it is mutually exclusive to iwconfig, I emerged madwifi, and I saw that the source for my kernel was added to and recompiled, convincing me that this was the fix I needed. But, when it didn't work, I looked at dmesg and saw that the ieee80211 procedures were not being found but didn't pay attention to what module was complaining. So, I emerged the ieee80211 package, and all worked well. I assumed that it was `madwifi' that required `ieee80211'. Now that you tell me otherwise, the explanation must be that `iwconfig' requires `ieee80211'. Perhaps the 'iwconfig' dependency list (?) is missing `ieee80211' .... ?
