Bug 105741 - mol modules land in wrong spots
|
Bug#:
105741
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: PPC
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: ppc@gentoo.org
|
Reported By: genfool@cabbey.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: mol modules land in wrong spots
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-09-12 16:21 0000
|
There are two minor issues with the location the MOL kernel modules are getting
installd to with mol-0.9.71_pre1-r2.ebuild:
1. the tun.ko is not placed in the uname sensitive directory.
2. the name of the uname sensitive directory is not taking -smp into account.
1. was a problem in 0.9.70 ebuilds as well, 2 is new in this version.
cabbey@bezerkwookie /usr/lib/mol/0.9.71/modules $ find -type f
./2.6.12-gentoo-r9-g4-cabbey/mol.ko
./tun.ko
cabbey@bezerkwookie /usr/lib/mol/0.9.70/modules $ uname -r
2.6.12-gentoo-r9-g4-cabbey
cabbey@bezerkwookie /usr/lib/mol/0.9.71/modules $ startmol --list
--------------------------------------------------------------
Running kernel: 2.6.12-gentoo-r9-g4-cabbey-smp
--------------------------------------------------------------
Available modules:
2.6.12-gentoo-r9-g4-cabbey in /usr/lib/mol/0.9.71
--------------------------------------------------------------
cabbey@bezerkwookie /usr/lib/mol/0.9.71/modules $ cd ../../0.9.70/modules
cabbey@bezerkwookie /usr/lib/mol/0.9.70/modules $ find -type f
./2.6.10-gentoo-r5-g4-cabbey-smp/tun.ko
./2.6.10-gentoo-r5-g4-cabbey-smp/kuname.ko
./2.6.12-gentoo-r9-g4-cabbey-smp/tun.ko
cabbey@bezerkwookie /usr/lib/mol/0.9.70/modules $ grep cabbey /boot/config*
/boot/config-2.6.10-gentoo-r4-g4-cabbey:CONFIG_LOCALVERSION="-g4-cabbey"
/boot/config-2.6.10-gentoo-r5-g4-cabbey:CONFIG_LOCALVERSION="-g4-cabbey"
/boot/config-2.6.10-gentoo-r6-g4-cabbey:CONFIG_LOCALVERSION="-g4-cabbey"
/boot/config-2.6.12-gentoo-r9-g4-cabbey:CONFIG_LOCALVERSION="-g4-cabbey"
/boot/config-2.6.9-gentoo-r9-g4-cabbey:CONFIG_LOCALVERSION="-g4-cabbey"
(I had worked around #1 in 0.9.70)
I can reproduce this. For now, just insmod the modules by path, I'll get this
fixed as soon as I can figure out why it's doing that. :p
heh, I've actually been working around it by moving the modules after emerging.
I've been looking into this some myself, trying to get a better understanding of
the linux-mod ebuild. Are there any docs on that?
Fixed in mol-0.9.71_pre1-r3.
just emerged mol-0.9.71_pre3 and tun.ko still lands in the wrong spot.
I can't replicate this, can you try with the latest ~ppc version and attach a
log of the build?
tun.ko really shouldn't be built on 2.6 kernels, so I've removed it from pre5.
This fixes the problem. :)