I just now received this from peebee:
I do not see the blacklist-ssb file in the main SFS file. Is there something in precise that creates that /etc/modprobe.d file?peebee wrote:Thats how Precise came OOTB - I didn't do anything specific to cause that.......nor to un-blacklist it....rerwin wrote:I noticed in your first diag file that you had ssb blacklisted. But that disappeared in the other diags.
Richard
Cheers...
The ssb module should not be blacklisted. It gets loaded very early regardless of the blacklisting. The firmware that did not activate takes care of ssb and its friends. Please avoid forcing that blacklisting. In the diag file peebee sent me, the blacklist file was not present in bootups after the first. So, it may not be as effective as someone intended. Anyway, it should not be there. It would prevent my "firmware" module management logic from operating correctly, so must be resolved. Thanks.
Richard