On 03/06/2012 05:37 PM, Mathieu Trudel-Lapierre wrote:
> Well, the error is really pretty much just cosmetic; the modeswitch does
> get done so the devices should be available regardless -- the fix is
> just to make sure the switching is properly listed as completed and
> successful.
>
> There's a new revision of the package on my ppa; https://launchpad.net
> /~mathieu-tl/+archive/ppa/+sourcepub/2289618/+listing-archive-extra. By
> now I do think I've got all these annoying little mistakes ironed out.
>
Mathieu,
with the new version i got more indicative error:
Device not in "bind_list" yet, bind it now
modprobe not foundModule loader is (null)
Can't do anymore without module loader; get "modtools"!
driver binding failed
On 03/06/2012 05:37 PM, Mathieu Trudel-Lapierre wrote: /launchpad. net tl/+archive/ ppa/+sourcepub/ 2289618/ +listing- archive- extra. By
> Well, the error is really pretty much just cosmetic; the modeswitch does
> get done so the devices should be available regardless -- the fix is
> just to make sure the switching is properly listed as completed and
> successful.
>
> There's a new revision of the package on my ppa; https:/
> /~mathieu-
> now I do think I've got all these annoying little mistakes ironed out.
>
Mathieu,
with the new version i got more indicative error:
Device not in "bind_list" yet, bind it now
modprobe not foundModule loader is (null)
Can't do anymore without module loader; get "modtools"!
driver binding failed
the full log is attached.