On Sat, Jun 16, 2007 at 06:04:27PM -0400, Alan Stern wrote:
> What about unplugging the device, turning its power off, then turning
> its power on and replugging it?
>
> For that matter, have you ever tried running brltty immediately after
> turning the device on? Perhaps the device needs time to "warm up".
Where a friend just reported she had to reboot some device to get
it to work again after interrupting a command or trying somethign
that didn't work, I told her that I managed to revive my devices
by removing the low level driver and then modprobing it again.
Works for me. YMMV
Roger.
--
** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
