Bug 93766

Summary:	ipw2100 doesn't survive Linux kernel upgrade
Product:	Gentoo Linux	Reporter:	Clock <clock>
Component:	[OLD] Core system	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	minor
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Clock 2005-05-24 00:31:27 UTC

net-wireless/ipw2100 doesn't survive emerge gentoo-sources. emerge ipw2100 must
be rerun manually after upgrading kernel. Shouldn't the portage system
automatically take care of this?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.200
41102-r1, 2.6.11-gentoo-r5 i686)
=================================================================
System uname: 2.6.11-gentoo-r5 i686 Intel(R) Pentium(R) M processor 1.50GHz
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, May  4 2005, 16:17:52)]
dev-lang/python:     2.3.5
sys-apps/sandbox:    [Not Present]
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-r7
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe"
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/lib/
mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/sh
are/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/te
x/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/
distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl emboss enco
de esd fam foomaticdb fortran gdbm gif gpm gtk gtk2 guile imagemagick imap imlib
 ipv6 jack java jpeg kde ldap libg++ libwww mad mikmod motif mozilla mp3 mpeg my
sql ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime
 readline ruby samba sdl slang spell ssl svga tcltk tcpd tetex tiff tls truetype
 truetype-fonts type1-fonts vorbis xine xml2 xmms xv zlib userland_GNU kernel_li
nux elibc_glibc"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLA

Comment 1 Toralf Förster gentoo-dev

2005-05-24 00:36:03 UTC

This is true for all kernel modules not included in the official kernel tree

Comment 2 Jakub Moc (RETIRED) gentoo-dev

2005-05-24 00:44:23 UTC

No, re-emerge any kernel modules (ipw2100, nvidia-kernel, ...) after any kernel
upgrade. Portage won

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2005-05-24 00:44:23 UTC

No, re-emerge any kernel modules (ipw2100, nvidia-kernel, ...) after any kernel
upgrade. Portage won´t do this. 

If you are using genkernel, run have a look at --callback option. Also Bug 89444
might be interesting for you.

Comment 4 Clock 2005-05-24 05:56:36 UTC

Is this described anywhere?

Comment 5 Jakub Moc (RETIRED) gentoo-dev

2005-05-24 09:41:41 UTC

(In reply to comment #3)
> Is this described anywhere?

http://www.gentoo.org/doc/en/kernel-upgrade.xml#doc_chap6