Hello Andrew, [...] > Although, my dmesg is now peppered with messages like : > uhub1: port error, restarting port 1 > uhub1: port error, giving up port 1 > > And i'm sure that wasn't the case before. Is this just some new > verbosity or does is point to a subtle problem? There doesn't seem to be > any problem probing or using my USB devices, a complete dmesg is > included below. > > Also - I was wondering if there was any particular reason why the rc > script for starting the bluetooth stack is hidden away in > /usr/share/examples instead of being part of the /etc/rc mechanism? I > had to copy the script out and call it from /usr/local/etc/rc.d - not > exactly a problem of course but we don't have to do that with any other > device support. Do we? bluetooth devices may come and go at any time. normally rc.bluetooth script would be called in response to device arrival or departure by some other process (i.e. usbd(8) or devd(8) for example). thanks, max __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonusReceived on Thu Jan 08 2004 - 15:50:47 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:37 UTC