modprobe bonding fails without error
insmod seems to work
Can someone explain this? (Hand typed from a remote "console" excuse typos.)
[root@XXXXXXX bonding_not_working]# depmod -a
[root@XXXXXXX bonding_not_working]# lsmod|grep bonding
[root@XXXXXXX bonding_not_working]# modprobe bonding
[root@XXXXXXX bonding_not_working]# lsmod|grep bonding
[root@XXXXXXX bonding_not_working]# uname -r
2.6.32-504.16.2.el6.x86_64
[root@XXXXXXX bonding_not_working]# insmod /lib/modules/2.6.32-504.16.2.el6.x86_64/kernel/drivers/net/bonding/bonding.ko
[root@XXXXXXX bonding_not_working]# lsmod|grep bonding
bonding 130997 0
ipv6 334740 1 bonding
8021q 25527 1 bonding
[root@XXXXXXX bonding_not_working]# #why?
No errors that I can find. strace output shows the "open" of the module at the path above followed by a "stat" of /sys/module/bonding => No such file or directory.
Puzzle of the day: modprobe isn't probing
Re: Puzzle of the day: modprobe isn't probing
See if you have anything in /etc/modprobe.conf or in /etc/modprobe.d/*.conf that might mention "install bonding"
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke