On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M <ben.m.cahill@xxxxxxxxx> wrote: > Try loading driver using module param: > > debug=0x43fff > > This will provide more information in the log, including an event log > (where you see "Microcode SW Error detected" in your log, you would have > captured Event Log if you had the debug=0x43fff setting). > > -- Ben -- Just a question: Why are we using cryptic hex IDs for the debug setting? Is there a specific reason for this, or just noone has yet included proper modparams for the various debugging settings? -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) -- 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
