Guess that was udev and not modprobe, where changes made are picked up immediately? My bad.
What i do have though, is a bunch of scripts in /etc/modprobe.d, with a comment:
<span style="color:#323232;"># 'modinfo -p your-module' to list possible values
</span><span style="color:#323232;"># 'systool -m your-module -av' to list active modules
</span><span style="color:#323232;"># modinfo -p your-module |sort |awk -F':' '{print "n# "$2"n#options your-module "$1"="}' for a preset
</span>
Maybe there is a module-functionality active that causes trouble? Btw, dmesg -H says nothing? Looks like brcmfmac is troublesome generally (of course broadcum, huh).
Bttw: if you can’t /etc/modprobe for some reason, you can load module settings as kernel parameters (via Grub or whatever) like module.option=value.
About the wakeup script, i have this in mine:
<span style="color:#323232;">#!/bin/sh
</span><span style="color:#323232;">case $1/$2 in
</span><span style="color:#323232;"> pre/*)
</span><span style="color:#323232;"> # Put here any commands expected to be run when suspending or hibernating.
</span><span style="color:#323232;">
</span><span style="color:#323232;"> # so bluetooth doesn't prevent sleep
</span><span style="color:#323232;"> /usr/bin/bluetoothctl power off ;;
</span><span style="color:#323232;"> post/*)
</span><span style="color:#323232;"> # Put here any commands expected to be run when resuming from suspension or thawing from hibernation.
</span><span style="color:#323232;">
</span><span style="color:#323232;"> # bluetooth on after resume
</span><span style="color:#323232;"> /usr/bin/bluetoothctl power on ;;
</span><span style="color:#323232;">esac
</span>
Sorry, this is about as far as i can help without access to your computer.