When emerging net-misc/e1000-5.2.52 against sys-kernel/gentoo-dev-sources-2.6.11-r3 the module does not get built. I've emerged the new kernel sources and headers, but I haven't rebooted yet, so the running kernel is still 2.6.10 Reproducible: Always Steps to Reproduce: Actual Results: /usr/src/linux/include/asm/system.h:193: warning: dereferencing type-punned pointer w ill break strict-aliasing rules e1000_main.c: In function `e1000_suspend': e1000_main.c:2924: error: too many arguments to function `pci_save_state' e1000_main.c: In function `e1000_resume': e1000_main.c:2952: error: too many arguments to function `pci_restore_state' make: *** [e1000_main.o] Error 1 >>> Test phase [not enabled]: net-misc/e1000-5.2.52 >>> Install e1000-5.2.52 into /var/tmp/portage/e1000-5.2.52/image/ category net-misc install: cannot stat `/var/tmp/portage/e1000-5.2.52/work/e1000-5.2.52/src/e1000.o': N o such file or directory Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20050125-r0, 2.6.10-gentoo-r6 i686) ================================================================= System uname: 2.6.10-gentoo-r6 i686 Intel(R) Pentium(R) M processor 1400MHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 24 2005, 14:17:46)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -msse2 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/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/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -msse2 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.ise.co.za http://mirrors.tds.net/gentoo http://gentoo.seren.com/gentoo ftp:/ftp.gtlib.cc.gatech.edu/pub/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://vlaai.snt.ipv4.utwente.nl/pub/os/linux/gentoo/ http://vlaai.snt.ipv4.utwente.nl/pub/os/linux/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aac acpi aim alsa apm arts avi bash-completion berkdb bitmap-fonts bzlib cdb cdparanoia cdr crypt cups curl curlwrappers dba dga divx4linux dvd dvdread emboss encode esd exif expat fam ffmpeg flac flash flatfile font-server foomaticdb fortran ftp gd gdbm gif gnome gnutls gphoto2 gpm gtk gtk2 guile iconv icq imagemagick imap imlib inifile ipv6 jabber jack java javascript jpeg kde lcms ldap libedit libg++ libwww mad maildir mikmod mime ming mmx motif mozilla mp3 mpeg msn ncurses nls offensive ofx ogg oggvorbis openal opengl oscar oss pam pcmcia pcre pdflib perl plotutils png pnp python qt quicktime readline recode samba sdl sockets socks5 sox spell sqlite sse sse2 ssl svg svga tcltk tcpd theora tidy tiff truetype truetype-fonts trusted type1-fonts unicode usb v4l vcd vhosts wifi wmf wxwindows xml xml2 xmlrpc xmms xosd xpm xsl xv xvid yahoo zeo zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
e1000 (the ebuild) is unsupported. Please use the in-kernel drivers when using 2.6
Thanks! Could this possibly be reflected in the ebuild? E.g. could it depend on kernel <2.6, or just say: * Note: this ebuild isn't supposed to work with 2.6 ?
Got hit by this bug the other day after I got hit by another issue using the in-kernel driver. The other issue is described at: http://support.intel.com/support/network/adapter/pro100/sb/cs-007655.htm Apparently the e1000 driver is meant to fix it, so do you mind if I test it, fix the ebuild to die properly and bump it?
Feel free to test it, but please don't bump it. If there is an issue with in-kernel driver we should fix that instead.
It didn't fix the issue either. IOW, the in-kernel and external drivers are as good as each other already. :(
