14.x kernel driver : bonding

[CentralWare]

13.1 network "bonding" driver was just tested - works fine; 14.x complains at modprobe that things are missing.
* The way it was worded sounds as though it may be looking for variables to be passed?

Code: [Select]

modprobe bonding mode=0
(mode=0 is default and otherwise unnecessary to pass along, but somewhere since 13.x "something" changed!   Adding a number of settings to the command didn't affect the outcome.)

Reproduction: Boot 14.x x86_64 (I'm assuming via USB should do the same, though I had TC installed with 14 when I noticed the problem) and simply load the module "bonding" with no variables afterward.
It's also assumed the other releases will have the same hiccup, though I don't imagine it's used too often in ARM beyond bonding eth0 to wlan0 for outage redundancy.

Thanks!

[Juanito]

13.1 network "bonding" driver was just tested - works fine; 14.x complains at modprobe that things are missing.

It’s hard to help if you don’t say what’s missing

[Rich]

Hi Juanito
It's missing a symbol:

Code: [Select]

tc@box:~$ sudo modprobe bonding
modprobe: can't load module bonding (kernel/drivers/net/bonding/bonding.ko.gz): unknown symbol in module, or unknown parameter
tc@box:~$
Checking dependencies:

Code: [Select]

tc@box:~$ modinfo bonding | grep depends
depends:        ipv6
tc@box:~$
Checking ipv6:

Code: [Select]

tc@box:~$ modinfo ipv6
modinfo: module '/lib/modules/6.1.2-tinycore64/ipv6' not found
tc@box:~$
Which is provided by:
ipv6-netfilter-6.1.2-tinycore64.tcz

[Rich]

Hi CentralWare
It appears the  bonding  driver changed. Under TC13 x86_64
modinfo reports no dependencies for the  bonding  driver.

[CentralWare]

Thanks guys, the machine in question was at the bottom of a rack (where I was virtually up-side-down looking at the screen) thus the post here was somewhat vague due to being from memory AFTER having already down-graded to 13.1 as I had to test the network cards to see if any obstacles were foreseen and build the script to make it functional.

Bonding now requires IPv6...  interesting twist, but...  okay!

[Rich]

Hi CentralWare
There are parameters to disable ipv6 if you want to. This way
the symbols still get resolved without ipv6 being operational:

Code: [Select]

tc@E310:~$ modinfo ipv6
filename:       /lib/modules/4.19.10-tinycore/kernel.tclocal/net/ipv6/ipv6.ko.gz
 ----- Snip -----
parm:           autoconf:Enable IPv6 address autoconfiguration on all interfaces
parm:           disable_ipv6:Disable IPv6 on all interfaces
parm:           disable:Disable IPv6 module such that it is non-functional
depends:       
 ----- Snip -----
tc@E310:~$I'm not sure how parm #2 differs from #3. This is from TC10 x86 but
I expect it's probably the same in more current releases.