1 |
Did a new install, the new kernel can't load modules: |
2 |
|
3 |
# modprobe nfsv3 |
4 |
modprobe: ERROR: could not insert 'nfsv3': Exec format error |
5 |
|
6 |
Odd. Never had this before. The module file itself is a regular 64-bit |
7 |
ELF file, just as it should be (compared to a working module on another |
8 |
machine) |
9 |
|
10 |
gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2: |
11 |
# gcc -v |
12 |
Using built-in specs. |
13 |
COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc |
14 |
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrapper |
15 |
Target: x86_64-pc-linux-gnu |
16 |
Configured with: |
17 |
/var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure |
18 |
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr |
19 |
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4 |
20 |
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include |
21 |
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4 |
22 |
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man |
23 |
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info |
24 |
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++-v4 |
25 |
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python |
26 |
--enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt |
27 |
--disable-werror --with-system-zlib --enable-nls |
28 |
--without-included-gettext --enable-checking=release |
29 |
--with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4 |
30 |
p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared |
31 |
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu |
32 |
--enable-multilib --with-multilib-list=m32,m64 --disable-altivec |
33 |
--disable-fixed-point --enable-targets=all --disable-libgcj |
34 |
--enable-libgomp --disable-libmudflap --disable-libssp --enable-lto |
35 |
--without-cloog --enable-libsanitizer |
36 |
Thread model: posix |
37 |
gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1) |
38 |
|
39 |
make.conf seems correct: |
40 |
CHOST="x86_64-pc-linux-gnu" |
41 |
CFLAGS="-march=native -O2 -pipe" |
42 |
CXXFLAGS="${CFLAGS}" |
43 |
ACCEPT_KEYWORDS="~amd64" |
44 |
|
45 |
The kernel loads and runs OK: |
46 |
# uname -a |
47 |
Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64 |
48 |
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux |
49 |
|
50 |
and the kernel was built with gcc auto-detection: |
51 |
# grep NATIVE /boot/config-4.1.2-gentoo |
52 |
CONFIG_MNATIVE=y |
53 |
|
54 |
and the .config was grabbed from a working machine with very similar |
55 |
hardware (one minor hardware upgrade ahead) |
56 |
|
57 |
I haven't done a full world update yet, most code is still what's in the |
58 |
stage3, but always in the past that hasn't been a problem; the stage |
59 |
must successfully build a kernel and load the modules. |
60 |
|
61 |
Module loading works just fine when booted from the Gentoo minimal |
62 |
install image. |
63 |
|
64 |
So, what dumbass n00b error did I make today? |
65 |
|
66 |
|
67 |
-- |
68 |
Alan McKinnon |
69 |
alan.mckinnon@×××××.com |