The openvz-sources-2.6.18.028.053-r2 version doesn't find my Broadcom NIC. There is a tg3 patch here: http://forum.openvz.org/index.php?t=msg&goto=30735& I'v applied the patch, and now my NIC recognized as should. Is there any way to apply this patch to the portage.
Created attachment 169056 [details, diff] tg3.patch tg3 patch from here: http://forum.openvz.org/index.php?t=msg&goto=30735&
Copied from bug 242728, in case it's of some use: Here is my emerge --info: emerge --info Portage 2.1.4.5 (hardened/linux/amd64, gcc-3.4.6, glibc-2.6.1-r0, 2.6.18-028stab053 x86_64) ================================================================= System uname: 2.6.18-028stab053 x86_64 Dual-Core AMD Opteron(tm) Processor 1212 Timestamp of tree: Fri, 17 Oct 2008 10:45:01 +0000 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] app-shells/bash: 3.2_p33 dev-lang/python: 2.5.2-r7 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.61-r2 sys-devel/automake: 1.10.1-r1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=opteron -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=opteron -O2 -pipe" DISTDIR="/_gentoo_portage/distfiles" FEATURES="ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://de-mirror.org/distro/gentoo http://gentoo.inode.at http://gentoo.inf.elte.hu" LANG="hu_HU.UTF-8" LC_ALL="hu_HU.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="hu" MAKEOPTS="-j4" PKGDIR="/_gentoo_portage/packages/opteron64" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/_gentoo_portage/tmp" PORTDIR="/_gentoo_portage/portage" PORTDIR_OVERLAY="/_gentoo_portage/overlay" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dnow 3dnowext acpi amd64 berkdb bzip2 caps cli cracklib crypt dri hardened iconv isdnlog justify midi mmx mudflap multilib ncurses nls nptl nptlonly openmp pam pcre perl pic pppd python readline reflection session slang spl sse sse2 sse3 ssl tcpd unicode urandom xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" APACHE2_MPMS="peruser" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="hu" USERLAND="GNU" VIDEO_CARDS="vesa" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Thank you for report Balazs. Although this is an issue with stable openvz sources if you really need kernel to work with newer hardware you'll have to use ~arch kernels (openvz-sources-2.6.18.028.059.3). They support this NIC. Another solution is to patch your stable kernel manually. So no, I think it's not sane to start adding patches which add support for new hardware into vanilla kernels at this moment as the list of hardware which is not supported by this stable vanilla based kernels is toooooo long and it'll be impossible to improve this situation. Sorry I have to close WONTFIX, and yes, try ~arch kernels they are more fragile to build options but they are better maintained from the security and hardware point of views.
(In reply to comment #3) > Thank you for report Balazs. Although this is an issue with stable openvz > sources if you really need kernel to work with newer hardware you'll have to > use ~arch kernels (openvz-sources-2.6.18.028.059.3). They support this NIC. > Another solution is to patch your stable kernel manually. So no, I think it's > not sane to start adding patches which add support for new hardware into > vanilla kernels at this moment as the list of hardware which is not supported > by this stable vanilla based kernels is toooooo long and it'll be impossible to > improve this situation. Sorry I have to close WONTFIX, and yes, try ~arch > kernels they are more fragile to build options but they are better maintained > from the security and hardware point of views. > Okay, I see your point. Thank you.
