Re: had another crash, reboot usb failed, powerdown reboot usb failed
On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> See subject, mouse, keyboard, usb printers working, but /dev/ttyUSB* is
> not,
>
> "sudo lsusb -v|grep -C3 Couldn -" reports most devices can't be opened.
> Example:
> gene@coyote:/etc/nut$ sudo lsusb -v|grep -c3 Couldn -
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
>
> I am uptodate a/o yesterday with debian 11. And nothing was offered just
> now.
>
> Whats changed in the last 10 days?
>
> And where do I start, nut and heyu are both spamming the log. And
> something is beeping at me at 5 minute intervals.
>
Hi Gene,
We've had something similar to this previously when you were talking about
USB->TTY converters for driving your CNC machinery and you were complaining
about accessibility software for blind users being installed.
Pull the leads. Reboot. Insert the leads - check to see whether the leads
ar recognised. Reboot again. Divide and conquer until you find the problematic
lead or component. Treat it like troubleshooting a troublesome TV transmitter
or broadcast system niggle.
The simpler you can make your system while troubleshooting, the easier you
(and the rest of us) may find the whack-a-mole process of trying to
nail down what the actual issue is.
The more you can tell us what _EXACTLY_ you are doing, what you see, what
errors come up and what you have done to try and fix them, the easier we'll
all find it to come up with suggestions or actual answers for you.
There are a bunch of the usual suspects who will attempt to help: we can't
jump on a plane or a bus to see what your screen says and help you debug.
The more you can give us to go on, the easier it will be all round.
All the very best to you, as ever,
Andy Cater
> Thanks all;
>
> Cheers, Gene Heskett.
> --
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
> - Louis D. Brandeis
>
>
>
Reply to: