Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 46793 - compile order of modutils and module-init-tools causes errors on reboot
Summary: compile order of modutils and module-init-tools causes errors on reboot
Status: RESOLVED DUPLICATE of bug 33605
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-04 12:56 UTC by Andre Hinrichs
Modified: 2005-07-17 13:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Hinrichs 2004-04-04 12:56:05 UTC
I'm having both kernel version 2.4.x and kernel version 2.6.x on my system.
After installing kernel version 2.6.x I recognized that I need module_init_tools instead of modutils on my system. I saw that same binaries as of modutils package were installed by the module_init_tools package.
After rebooting everything was fine.
Then I did a 'emerge -e world' and rebooted the system having the same problems again. Checking the emerge.log I saw that module_init_tools was installed first and then modutils which caused the problem.

Is there a chance to change the compile order?
Or should there be a 'kernel26' use flag introduced?
Shouldn't modutils and module_init_tools block each other?


Reproducible: Always
Steps to Reproduce:
1.emerge module_init_tools
2.emerge modutils
3.reboot with kernel 2.6.x

Actual Results:  
system starts with the usual 'QM_MODULES function not implemented...' errors

Expected Results:  
system should start without errors

Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.3-gentoo-r1)
=================================================================
System uname: 2.6.3-gentoo-r1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.4.3.13
distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=i686 -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config
/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/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distcc sandbox"
GENTOO_MIRRORS="ftp://ftp.uninett.no/pub/linux/Gentoo
http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/
http://ftp.snt.utwente.nl/pub/os/linux/gentoo
http://ftp.linux.ee/pub/gentoo/distfiles/"
MAKEOPTS="-j 3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://192.168.68.1/gentoo-portage"
USE="X Xaw3d aalib acl alsa apache2 apm arts audiofile avi berkdb bonobo cdr
crypt cups curl dvd emacs encode esd flac flash foomaticdb gd gdbm ggi gif gmp
gnome gphoto2 gpm gtk gtk2 gtkhtml guile icq imagemagick imlib java jpeg kde
lcms ldap leim libg++ libwww mad maildir mikmod motif mozilla mpeg mysql nas
ncurses nls nocardbus odbc oggvorbis opengl oss pam pcmcia pda pdflib perl
plotutils png python qt quicktime readline samba sasl scanner sdl slang spell
ssl svga tcltk tcpd tetex theora tiff truetype unicode usb wmf wxwindows x86 xml
xml2 xmms xv zlib"
Comment 1 SpanKY gentoo-dev 2004-04-04 23:14:12 UTC
you cant use both packages at the same time

if you plan on using 2.6, then only use module-init-tools ... it installs <program>.old so that you can do module related stuff in 2.4.x and earlier
Comment 2 Andre Hinrichs 2004-04-05 01:04:36 UTC
Then they should really block each other, shouldn't they?
Means, if somebody installs module-init-tools he should be forced to
remove modutils.
Comment 3 gentoo-bugs 2004-07-09 16:35:13 UTC
No, as stated before, module-init-tools has an intelligent backup function. The problem is that modutils don't. So there'd have to be something like re-emerging module-init-tools after every merge of modutils only if module-init-tools are installed. At least give the poor users a warning what they should do if they're running 2.6 kernels, I spent some time figuring this one out with a kernel without loaded modules ;)
Comment 4 Bob Thomas 2004-07-11 19:41:59 UTC
But module-init-tools builds modutils. If you have module-init-tools installed, then you don't need modutils. Isn't that enough reason for a block?

P.S. - I just ran into this problem. Luckily it didn't take me too long to figure out that I just needed to re-emerge module-init-tools. I don't know why I had modutils installed anyway, since I only run 2.6.x
Comment 5 SpanKY gentoo-dev 2004-08-25 17:55:21 UTC

*** This bug has been marked as a duplicate of 33605 ***