Marco d'Itri wrote on Wed, Mar 03, 2010 at 05:31:38PM +0100:
> On Mar 03, Martin Cracauer <[email protected]> wrote:
>
> > Can we move this to a more constructive base and you give me something
> > to try to debug this further? I honestly thought this is a matter of
> > just disabling something in the current udev configuration and the
> > device is left alone.
> grep -r usb_id /etc/udev/ and find out which instance breaks your
> device.
> So with the default udev configuration usb_id is used only on storage
> and input devices. Is your device one of these?
>
> But I really recommend you upgrade to testing, because even if you find
> out what is triggering this problem I will not care unless you can
> reproduce it with udev from testing (and then I may still not care
> unless somebody shows that udev is actually at fault).
No problem, I have -testing elsewhere. I'll give it a spin with the
device in question when I get home and get the info needed.
Thanks
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <[email protected]> http://www.cons.org/cracauer/
FreeBSD - where you want to go, today. http://www.freebsd.org/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
