Chatre, Reinette wrote:
Very strange. Would it be possible to load the module with "debug=0x43fff"? This will capture a detailed event log and error log from uCode, so we can see what caused the uCode error.
I will try. Is there some way to turn debug on and off after the module has been loaded, e.g. by running echo 0x43fff >/proc/some/fancy/path ? Regards Harri - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
