Error dmesg (module_register_init: MOD_LOAD )
-
You just need to do what the error message says:
Add the following two lines to the file /boot/loader.conf and those messages will be gone:```
legal.intel_ipw.license_ack=1
legal.intel_iwi.license_ack=1Regards Atom2
-
You should put the lines in /boot/loader.conf.local, create that file if you haven't already. The loader.conf file can be overwritten and isn't carried across a firmware update.
Steve
-
Also you do no need that at all unless using Intel WiFi cards.
-
You should put the lines in /boot/loader.conf.local, create that file if you haven't already. The loader.conf file can be overwritten and isn't carried across a firmware update.
Thanks Steve for correcting my answer to do it the proper way in order to survive upgrades.
Also you do no need that at all unless using Intel WiFi cards.
The error message appears on the boot console regardless of whether you have Intel WiFi cards installed in your box: My system has two Atheros Wifi cards only, but the error message nevertheless shows up. In any case, I don't think there's any harm with that setting.
-
@stephenw10
I know this is an old topic, I just wanted to check in if the /boot/loader.conf.local method is still the way to go. I tried this but pfsense doesn't load the file. -
@good4y0u said in Error dmesg (module_register_init: MOD_LOAD ):
I just wanted to check in if the /boot/loader.conf.local method is still the way to go
Yep.
(edit : the file name and location - what's in it and if it exists) is up to you - it will survive updates and upgrades)
It's a FreeBSD thing, it will probably never change :cat /boot/loader.conf.local kern.cam.boot_delay=10000 legal.intel_ipw.license_ack=1
It's the FreeBSD kernel that reads this file.
How do you know it's not reading the file ?file /boot/loader.conf.local /boot/loader.conf.local: ASCII text
-
@gertjan I think it's not reading because I get the warnings for authorizing the License when I put the variables in /boot/loader.conf.local , but not when I put them in /boot/loader.conf
Shell Output - cat /boot/loader.conf
kern.cam.boot_delay=10000 kern.ipc.nmbclusters="1000000" kern.ipc.nmbjumbo9="524288" hint.agp.0.disabled=1 legal.intel_iwi.license_ack=1 legal.intel_ipw.license_ack=1 autoboot_delay="3" hw.usb.no_pf="1" net.pf.request_maxcount="2000000"
Shell Output - cat /boot/loader.conf.local
legal.intel_wpi.license_ack=1 legal.intel_ipw.license_ack=1
-
@good4y0u said in Error dmesg (module_register_init: MOD_LOAD ):
I think it's not reading because .....
Read this again :
@gertjan said in Error dmesg (module_register_init: MOD_LOAD ):
file /boot/loader.conf.local
/boot/loader.conf.local: ASCII text'file' is a command and it will tell you something.
Like : the kernel not being able to read the "/boot/loader.conf.local" because it has no "ASCII text" coding.I have a
legal.intel_ipw.license_ack=1
which removed messages like
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /b
during booting?
-
@gertjan it still says the messages if its not in the default config file. The way I created the .local is by copying the original and renaming . its not really an issue because nothing I have in there is catastrophic.
I'll have to test other methods and report back. I'm almost sure its a layer 8 problem.
-
@Atom2 thanks that fixed it for me for my 2100 I was having that error also.