[gentoo-user] New install, can't load modules

2015-07-13 Thread Alan McKinnon 
Did a new install, the new kernel can't load modules:

# modprobe nfsv3
modprobe: ERROR: could not insert 'nfsv3': Exec format error

Odd. Never had this before. The module file itself is a regular 64-bit
ELF file, just as it should be (compared to a working module on another
machine)

gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2:
# gcc -v
Using built-in specs.
COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++-v4
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python
--enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
--disable-werror --with-system-zlib --enable-nls
--without-included-gettext --enable-checking=release
--with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4
p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--enable-multilib --with-multilib-list=m32,m64 --disable-altivec
--disable-fixed-point --enable-targets=all --disable-libgcj
--enable-libgomp --disable-libmudflap --disable-libssp --enable-lto
--without-cloog --enable-libsanitizer
Thread model: posix
gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1)

make.conf seems correct:
CHOST=x86_64-pc-linux-gnu
CFLAGS=-march=native -O2 -pipe
CXXFLAGS=${CFLAGS}
ACCEPT_KEYWORDS=~amd64

The kernel loads and runs OK:
# uname -a
Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux

and the kernel was built with gcc auto-detection:
# grep NATIVE /boot/config-4.1.2-gentoo
CONFIG_MNATIVE=y

and the .config was grabbed from a working machine with very similar
hardware (one minor hardware upgrade ahead)

I haven't done a full world update yet, most code is still what's in the
stage3, but always in the past that hasn't been a problem; the stage
must successfully build a kernel and load the modules.

Module loading works just fine when booted from the Gentoo minimal
install image.

So, what dumbass n00b error did I make today?


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Alan McKinnon 
On 13/07/2015 18:42, Alexander Kapshuk wrote:
 On Mon, Jul 13, 2015 at 5:29 PM, Alan McKinnon alan.mckin...@gmail.com 
 wrote:
 Did a new install, the new kernel can't load modules:

 # modprobe nfsv3
 modprobe: ERROR: could not insert 'nfsv3': Exec format error

 Odd. Never had this before. The module file itself is a regular 64-bit
 ELF file, just as it should be (compared to a working module on another
 machine)

 gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2:
 # gcc -v
 Using built-in specs.
 COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc
 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrapper
 Target: x86_64-pc-linux-gnu
 Configured with:
 /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure
 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
 --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4
 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include
 --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4
 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man
 --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info
 --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++-v4
 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python
 --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
 --disable-werror --with-system-zlib --enable-nls
 --without-included-gettext --enable-checking=release
 --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4
 p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared
 --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
 --enable-multilib --with-multilib-list=m32,m64 --disable-altivec
 --disable-fixed-point --enable-targets=all --disable-libgcj
 --enable-libgomp --disable-libmudflap --disable-libssp --enable-lto
 --without-cloog --enable-libsanitizer
 Thread model: posix
 gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1)

 make.conf seems correct:
 CHOST=x86_64-pc-linux-gnu
 CFLAGS=-march=native -O2 -pipe
 CXXFLAGS=${CFLAGS}
 ACCEPT_KEYWORDS=~amd64

 The kernel loads and runs OK:
 # uname -a
 Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64
 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux

 and the kernel was built with gcc auto-detection:
 # grep NATIVE /boot/config-4.1.2-gentoo
 CONFIG_MNATIVE=y

 and the .config was grabbed from a working machine with very similar
 hardware (one minor hardware upgrade ahead)

 I haven't done a full world update yet, most code is still what's in the
 stage3, but always in the past that hasn't been a problem; the stage
 must successfully build a kernel and load the modules.

 Module loading works just fine when booted from the Gentoo minimal
 install image.

 So, what dumbass n00b error did I make today?


 --
 Alan McKinnon
 alan.mckin...@gmail.com


 
 Does 'modprobe -nv' say anything useful?

It's normal - a list of dependant modules to be insmod'ed

 
 Anything of interest in '/var/log/dmesg'?

Nothing I can see:

# dmesg | egrep -i warn|error
[0.00] ACPI BIOS Warning (bug): 32/64X FACS address mismatch in
FADT: 0xCF7E4E40/0xCF7E4D40, using 32-bit address
(20150410/tbfadt-283)
[1.455621] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[2.278571] i8042: Warning: Keylock active
[3.798045] EXT3-fs (sdb3): error: couldn't mount because of
unsupported optional features (240)
[3.798411] EXT2-fs (sdb3): error: couldn't mount because of
unsupported optional features (240)


Digging a little deeper, I see that the kernel IS auto-loading modules
on start-up. My e1000e NIC is compiled as a module, and works:

00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit
Network Connection [8086:1502] (rev 04)
DeviceName:  Onboard LAN
Subsystem: Dell Precision M4600 [1028:04a3]
Kernel driver in use: e1000e
Kernel modules: e1000e


lsmod returns null output (just a header line, no data), and modprobe
fails with every module tried so far.

A dim memory is tickling my brain, something about module loading from
userspace post-startup being disabled - I'll google some more.


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Alan McKinnon 
On 13/07/2015 19:47, Mick wrote:
 On Monday 13 Jul 2015 17:42:22 Alexander Kapshuk wrote:
 On Mon, Jul 13, 2015 at 5:29 PM, Alan McKinnon alan.mckin...@gmail.com 
 wrote:
 Did a new install, the new kernel can't load modules:

 # modprobe nfsv3
 modprobe: ERROR: could not insert 'nfsv3': Exec format error

 Odd. Never had this before. The module file itself is a regular 64-bit
 ELF file, just as it should be (compared to a working module on another
 machine)

 gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2:
 # gcc -v
 Using built-in specs.
 COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc
 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrappe
 r Target: x86_64-pc-linux-gnu
 Configured with:
 /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure
 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
 --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4
 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include
 --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4
 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man
 --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info
 --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++
 -v4 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python
 --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
 --disable-werror --with-system-zlib --enable-nls
 --without-included-gettext --enable-checking=release
 --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4
 p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared
 --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
 --enable-multilib --with-multilib-list=m32,m64 --disable-altivec
 --disable-fixed-point --enable-targets=all --disable-libgcj
 --enable-libgomp --disable-libmudflap --disable-libssp --enable-lto
 --without-cloog --enable-libsanitizer
 Thread model: posix
 gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1)

 make.conf seems correct:
 CHOST=x86_64-pc-linux-gnu
 CFLAGS=-march=native -O2 -pipe
 CXXFLAGS=${CFLAGS}
 ACCEPT_KEYWORDS=~amd64

 The kernel loads and runs OK:
 # uname -a
 Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64
 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux

 and the kernel was built with gcc auto-detection:
 # grep NATIVE /boot/config-4.1.2-gentoo
 CONFIG_MNATIVE=y

 and the .config was grabbed from a working machine with very similar
 hardware (one minor hardware upgrade ahead)

 I haven't done a full world update yet, most code is still what's in the
 stage3, but always in the past that hasn't been a problem; the stage
 must successfully build a kernel and load the modules.

 Module loading works just fine when booted from the Gentoo minimal
 install image.

 So, what dumbass n00b error did I make today?


 --
 Alan McKinnon
 alan.mckin...@gmail.com

 Does 'modprobe -nv' say anything useful?

 Anything of interest in '/var/log/dmesg'?
 
 
 Just in case you missed it on the enthusiasm of a new install, have you set:
 
 CONFIG_MODULES=y

Yes, that's set. And the kernel correctly loads modules it finds it
needs on startup. I just can't do it from userspace.

 
 and of course built as modules whatever you're modprobing.
 
 BTW, is the module in question called 'nfsv3', or is it 'nfs'?  I don't use 
 it 
 myself to know.

The name is correct. There's a module nfs for core stuff and nfsv3 
nfsv4 fr the different versions.



-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Alexander Kapshuk 
On Mon, Jul 13, 2015 at 5:29 PM, Alan McKinnon alan.mckin...@gmail.com wrote:
 Did a new install, the new kernel can't load modules:

 # modprobe nfsv3
 modprobe: ERROR: could not insert 'nfsv3': Exec format error

 Odd. Never had this before. The module file itself is a regular 64-bit
 ELF file, just as it should be (compared to a working module on another
 machine)

 gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2:
 # gcc -v
 Using built-in specs.
 COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc
 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrapper
 Target: x86_64-pc-linux-gnu
 Configured with:
 /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure
 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
 --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4
 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include
 --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4
 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man
 --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info
 --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++-v4
 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python
 --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
 --disable-werror --with-system-zlib --enable-nls
 --without-included-gettext --enable-checking=release
 --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4
 p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared
 --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
 --enable-multilib --with-multilib-list=m32,m64 --disable-altivec
 --disable-fixed-point --enable-targets=all --disable-libgcj
 --enable-libgomp --disable-libmudflap --disable-libssp --enable-lto
 --without-cloog --enable-libsanitizer
 Thread model: posix
 gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1)

 make.conf seems correct:
 CHOST=x86_64-pc-linux-gnu
 CFLAGS=-march=native -O2 -pipe
 CXXFLAGS=${CFLAGS}
 ACCEPT_KEYWORDS=~amd64

 The kernel loads and runs OK:
 # uname -a
 Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64
 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux

 and the kernel was built with gcc auto-detection:
 # grep NATIVE /boot/config-4.1.2-gentoo
 CONFIG_MNATIVE=y

 and the .config was grabbed from a working machine with very similar
 hardware (one minor hardware upgrade ahead)

 I haven't done a full world update yet, most code is still what's in the
 stage3, but always in the past that hasn't been a problem; the stage
 must successfully build a kernel and load the modules.

 Module loading works just fine when booted from the Gentoo minimal
 install image.

 So, what dumbass n00b error did I make today?


 --
 Alan McKinnon
 alan.mckin...@gmail.com



Does 'modprobe -nv' say anything useful?

Anything of interest in '/var/log/dmesg'?

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Mick 
On Monday 13 Jul 2015 17:42:22 Alexander Kapshuk wrote:
 On Mon, Jul 13, 2015 at 5:29 PM, Alan McKinnon alan.mckin...@gmail.com 
wrote:
  Did a new install, the new kernel can't load modules:
  
  # modprobe nfsv3
  modprobe: ERROR: could not insert 'nfsv3': Exec format error
  
  Odd. Never had this before. The module file itself is a regular 64-bit
  ELF file, just as it should be (compared to a working module on another
  machine)
  
  gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2:
  # gcc -v
  Using built-in specs.
  COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc
  COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrappe
  r Target: x86_64-pc-linux-gnu
  Configured with:
  /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure
  --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
  --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4
  --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include
  --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4
  --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man
  --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info
  --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++
  -v4 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python
  --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
  --disable-werror --with-system-zlib --enable-nls
  --without-included-gettext --enable-checking=release
  --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4
  p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared
  --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
  --enable-multilib --with-multilib-list=m32,m64 --disable-altivec
  --disable-fixed-point --enable-targets=all --disable-libgcj
  --enable-libgomp --disable-libmudflap --disable-libssp --enable-lto
  --without-cloog --enable-libsanitizer
  Thread model: posix
  gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1)
  
  make.conf seems correct:
  CHOST=x86_64-pc-linux-gnu
  CFLAGS=-march=native -O2 -pipe
  CXXFLAGS=${CFLAGS}
  ACCEPT_KEYWORDS=~amd64
  
  The kernel loads and runs OK:
  # uname -a
  Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64
  Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux
  
  and the kernel was built with gcc auto-detection:
  # grep NATIVE /boot/config-4.1.2-gentoo
  CONFIG_MNATIVE=y
  
  and the .config was grabbed from a working machine with very similar
  hardware (one minor hardware upgrade ahead)
  
  I haven't done a full world update yet, most code is still what's in the
  stage3, but always in the past that hasn't been a problem; the stage
  must successfully build a kernel and load the modules.
  
  Module loading works just fine when booted from the Gentoo minimal
  install image.
  
  So, what dumbass n00b error did I make today?
  
  
  --
  Alan McKinnon
  alan.mckin...@gmail.com
 
 Does 'modprobe -nv' say anything useful?
 
 Anything of interest in '/var/log/dmesg'?


Just in case you missed it on the enthusiasm of a new install, have you set:

CONFIG_MODULES=y

and of course built as modules whatever you're modprobing.

BTW, is the module in question called 'nfsv3', or is it 'nfs'?  I don't use it 
myself to know.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Alan McKinnon 
On 13/07/2015 18:42, Alexander Kapshuk wrote:
 On Mon, Jul 13, 2015 at 5:29 PM, Alan McKinnon alan.mckin...@gmail.com 
 wrote:
 Did a new install, the new kernel can't load modules:

 # modprobe nfsv3
 modprobe: ERROR: could not insert 'nfsv3': Exec format error

 Odd. Never had this before. The module file itself is a regular 64-bit
 ELF file, just as it should be (compared to a working module on another
 machine)

 gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2:
 # gcc -v
 Using built-in specs.
 COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc
 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrapper
 Target: x86_64-pc-linux-gnu
 Configured with:
 /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure
 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
 --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4
 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include
 --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4
 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man
 --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info
 --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++-v4
 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python
 --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
 --disable-werror --with-system-zlib --enable-nls
 --without-included-gettext --enable-checking=release
 --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4
 p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared
 --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
 --enable-multilib --with-multilib-list=m32,m64 --disable-altivec
 --disable-fixed-point --enable-targets=all --disable-libgcj
 --enable-libgomp --disable-libmudflap --disable-libssp --enable-lto
 --without-cloog --enable-libsanitizer
 Thread model: posix
 gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1)

 make.conf seems correct:
 CHOST=x86_64-pc-linux-gnu
 CFLAGS=-march=native -O2 -pipe
 CXXFLAGS=${CFLAGS}
 ACCEPT_KEYWORDS=~amd64

 The kernel loads and runs OK:
 # uname -a
 Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64
 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux

 and the kernel was built with gcc auto-detection:
 # grep NATIVE /boot/config-4.1.2-gentoo
 CONFIG_MNATIVE=y

 and the .config was grabbed from a working machine with very similar
 hardware (one minor hardware upgrade ahead)

 I haven't done a full world update yet, most code is still what's in the
 stage3, but always in the past that hasn't been a problem; the stage
 must successfully build a kernel and load the modules.

 Module loading works just fine when booted from the Gentoo minimal
 install image.

 So, what dumbass n00b error did I make today?


 --
 Alan McKinnon
 alan.mckin...@gmail.com


 
 Does 'modprobe -nv' say anything useful?
 
 Anything of interest in '/var/log/dmesg'?
 




I hang my head in shame (and not for the first time either)

/boot in fstab had option noauto, so all my kernels were installed to
the / volume.

The real /boot volume had a valid kernel on it, from the initial install
with the minimal CD, and the .config was made with localyesconfig. It
was a perfectly valid working kernel, that just happened to NOT match
/lib/modules anymore

Fixing fstab, a few make install  make modules_install lus a
grub-install just for fun fixed the whole lot.

Sorry for the noise



-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Neil Bothwick 
On Mon, 13 Jul 2015 23:02:15 +0100, Mick wrote:

  /boot in fstab had option noauto, so all my kernels were installed
  to the / volume.  
 
 Ahh!  I always mount /boot BEFORE I cd into /usr/src out of habit, to
 avoid such a problem (my /boot is also set to noauto).
 
 If I were 10 years younger I would remember a trick I've read in this
 M/L to have /boot warn you, if it is not mounted.  Hmm ... now, who
 posted this, ... Neil?

The approach I've used is to mount /boot ro. It still protects /boot from
writes, as with noauto, but it shouts at you if you try to writ to /boot
instead of just pretending it succeeded and hiding the files somewhere
else.


-- 
Neil Bothwick

Can vegetarians eat animal crackers?


pgpOvU5krPtyP.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Mick 
On Monday 13 Jul 2015 20:50:47 Alan McKinnon wrote:

 /boot in fstab had option noauto, so all my kernels were installed to
 the / volume.

Ahh!  I always mount /boot BEFORE I cd into /usr/src out of habit, to avoid 
such a problem (my /boot is also set to noauto).

If I were 10 years younger I would remember a trick I've read in this M/L to 
have /boot warn you, if it is not mounted.  Hmm ... now, who posted this, ... 
Neil?

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] New install, can't load modules

2015-07-13 Thread Alan McKinnon 
On 14/07/2015 00:02, Mick wrote:
 On Monday 13 Jul 2015 20:50:47 Alan McKinnon wrote:
 
 /boot in fstab had option noauto, so all my kernels were installed to
 the / volume.
 
 Ahh!  I always mount /boot BEFORE I cd into /usr/src out of habit, to avoid 
 such a problem (my /boot is also set to noauto).
 
 If I were 10 years younger I would remember a trick I've read in this M/L to 
 have /boot warn you, if it is not mounted.  Hmm ... now, who posted this, ... 
 Neil?
 

I usually have /boot mounted - I don't see a threat model for my usage -
and edit fstab with care, but this time I ... forgot :-(

There's an envvar that helps remind you of /boot:
DONT_MOUNT_BOOT
it's mentioned in the elog for grub

-- 
Alan McKinnon
alan.mckin...@gmail.com