It could still be a driver issue -- as you manually specified the wext driver in that command...
Out of curiosity, what version of network manager are you running? Maybe the jaunty sources got updated (and re-broken)? Get the exact version # from synaptic (should be kinda weird with some ~~ things).
It could still be a driver issue -- as you manually specified the wext driver in that command...
Out of curiosity, what version of network manager are you running? Maybe the jaunty sources got updated (and re-broken)? Get the exact version # from synaptic (should be kinda weird with some ~~ things).
Dan