Re: stretch: amd64, no dmesg when usb stuff plugged in

[Gene Heskett]

On Friday 06 September 2019 12:53:54 Charles Curley wrote:

> On Fri, 6 Sep 2019 10:44:45 -0400
>
> Gene Heskett  wrote:
> > I found it. A staples brand usb hub that has served on the end of an
> > extension cable, as a place to plugin the dongles for the
> > keyboard/mouse for the last 8 or so years was doing funkity things
> > to udev. Replaced with another off brand slow hub with power buttons
> > for each socket, and the system is back to something resembling
> > normal operation.
>
> Good job.
>
> Here is what may be going on: the USB spec requires that plugs make .5
> amps (I think) available to devices. Hubs which do not use an external
> power supply cannot supply that to all the devices on that hub, so
> they do wonky things. So if you must have a USB hub, get one with an
> external power source.

It (the staples branded hub) has been running without external power for 
5 or 6 years, with up to 2 keyboard/mouse dongles and a card writer 
plugged in maybe 5% of that 5 or 6 years. And a fresh one, different 
make, non-powered, is working just fine.  I've no clue how much current 
its drawing but I'd have to say under .2 amps based on the fact that its 
generating no detectable heat. The one I took out had been making about 
1 watts worth of heat that I had just noticed over the last couple of 
months. I had also been losing that keyboard, and rarely the mouse too. 
And I was blaming that on the kernel, but it did not get better 
switching to the same kernel w/o the preempt-rt build, so next time I 
reboot I'll go back to the preempt-rt version and tell the linuxcnc 
developers I found the problem, if it doesn't recur in a week.

But I've no clue how long it will be before a buster compatible linuxcnc 
comes out, some python stuff it depends on has been removed from buster, 
requiring write-arounds.

Thanks Charles.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: stretch: amd64, no dmesg when usb stuff plugged in

[Charles Curley]

On Fri, 6 Sep 2019 10:44:45 -0400
Gene Heskett  wrote:

> I found it. A staples brand usb hub that has served on the end of an 
> extension cable, as a place to plugin the dongles for the
> keyboard/mouse for the last 8 or so years was doing funkity things to
> udev. Replaced with another off brand slow hub with power buttons for
> each socket, and the system is back to something resembling normal
> operation.

Good job.

Here is what may be going on: the USB spec requires that plugs make .5
amps (I think) available to devices. Hubs which do not use an external
power supply cannot supply that to all the devices on that hub, so they
do wonky things. So if you must have a USB hub, get one with an
external power source.

-- 
"When we talk of civilization, we are too apt to limit the meaning of
the word to its mere embellishments, such as arts and sciences; but
the true distinction between it and barbarism is, that the one
presents a state of society under the protection of just and
well-administered law, and the other is left to the chance government
of brute force."
- The Rev. James White, Eighteen Christian Centuries, 1889
Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB
https://charlescurley.com

Re: stretch: amd64, no dmesg when usb stuff plugged in

[Gene Heskett]

On Thursday 05 September 2019 19:11:42 Gene Heskett wrote:

> Greetings all;
>
> So what utility thats supposed to monitor that, has taken a holiday?
>
> Thanks All.
>
> Cheers, Gene Heskett

I found it. A staples brand usb hub that has served on the end of an 
extension cable, as a place to plugin the dongles for the keyboard/mouse 
for the last 8 or so years was doing funkity things to udev. Replaced 
with another off brand slow hub with power buttons for each socket, and 
the system is back to something resembling normal operation.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: stretch: amd64, no dmesg when usb stuff plugged in

[tomas]

On Thu, Sep 05, 2019 at 08:10:07PM -0400, bw wrote:
> In-Reply-To: <201909051911.42570.ghesk...@shentel.net>
> 
> Why do you continue with this type of post?  It's a joke.  I'm shocked 
> that anybody even answers this stupidity.

If you don't like the thread, just keep out of it.

If yo've got difficulties managing your aggressions (we all do,
from time to time), I'd recommend a punching-ball.

Cheers
-- t


signature.asc
Description: Digital signature

Re: stretch: amd64, no dmesg when usb stuff plugged in

[deloptes]

Gene Heskett wrote:

> Which made no diff. Whatever is supposed to be monitoring for new usb
> connections is not. So what do I look at next?

I suggest do a default installation from scratch to a disk (I know you have
some) and try again. I guess you are messing too much with your system.

AFAIK it is the udev that is responsible, so 

kernel driver -> udev -> user space

so it is either udev or the driver that is messed up. The driver of course
handles the hardware, so to be able to help we should know what is the
hardware (PC and USB stick), kernel version, udev etc.

better do it on default stretch or buster, without your endless
customizations all over the place ;-).

I have experienced similar if you plug in USB2 into USB1 port, but it was
time ago. 

regards

Re: stretch: amd64, no dmesg when usb stuff plugged in

[Gene Heskett]

On Friday 06 September 2019 00:28:54 Gene Heskett wrote:

> On Thursday 05 September 2019 20:10:07 bw wrote:
> > In-Reply-To: <201909051911.42570.ghesk...@shentel.net>
> >
> > Why do you continue with this type of post?  It's a joke.  I'm
> > shocked that anybody even answers this stupidity.
>
> Because something has failed. dmesg after a boot has quite a few of
> these but I have no clue how to identify which cable from this:
> [   11.166853] usb 1-4-port4: Cannot enable. Maybe the USB cable is
> bad? [   11.167222] usb 1-4-port4: unable to enumerate USB device
>
> Without dmesg to tell me which cable I just unplugged, how do I
> identify which one?
>
> It is also refusing to enable a card reader with a new 64GB card
> plugged in, which is normally /dev/sdf#, and which I would like to
> write a netboot image to for debian-arm.  The led on the reader blinks
> normally, but there is no corresponding dmesg output report.
>
> dirmngr is also complaining in the syslog:
>
> Sep  5 23:58:42 coyote dirmngr[2677]: no CRL available for issuer id
> 5E6738A53D3E002778FCD309C3695592BBBC4318
> Sep  5 23:58:42 coyote dirmngr[2677]: error
> retrieving 'http://crl.disa.mil/crl/DODEMAILCA_31.crl': http status
> 404 Sep  5 23:58:42 coyote dirmngr[2677]: crl_fetch via DP failed: No
> data Sep  5 23:58:42 coyote dirmngr[2677]: command 'ISVALID' failed:
> No data Sep  5 23:58:42 coyote dirmngr[2677]: command 'ISVALID'
> failed: No CRL known
> Sep  5 23:58:43 coyote dirmngr[2677]: no CRL available for issuer id
> 5E6738A53D3E002778FCD309C3695592BBBC4318
> Sep  5 23:58:43 coyote dirmngr[2677]: error
> retrieving 'http://crl.disa.mil/crl/DODEMAILCA_31.crl': http status
> 404 Sep  5 23:58:43 coyote dirmngr[2677]: crl_fetch via DP failed: No
> data Sep  5 23:58:43 coyote dirmngr[2677]: command 'ISVALID' failed:
> No data Sep  5 23:58:43 coyote dirmngr[2677]: command 'ISVALID'
> failed: No CRL known
>
> I have replaced the bios battery, and restored the bios defaults to no
> avail.
>
> I'll next try an older but still stretch kernel.
>
Which made no diff. Whatever is supposed to be monitoring for new usb 
connections is not. So what do I look at next?

> Cheers, Gene Heskett


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: stretch: amd64, no dmesg when usb stuff plugged in

[Gene Heskett]

On Thursday 05 September 2019 20:10:07 bw wrote:

> In-Reply-To: <201909051911.42570.ghesk...@shentel.net>
>
> Why do you continue with this type of post?  It's a joke.  I'm shocked
> that anybody even answers this stupidity.

Because something has failed. dmesg after a boot has quite a few of these 
but I have no clue how to identify which cable from this:
[   11.166853] usb 1-4-port4: Cannot enable. Maybe the USB cable is bad?
[   11.167222] usb 1-4-port4: unable to enumerate USB device

Without dmesg to tell me which cable I just unplugged, how do I identify 
which one?

It is also refusing to enable a card reader with a new 64GB card plugged 
in, which is normally /dev/sdf#, and which I would like to write a 
netboot image to for debian-arm.  The led on the reader blinks normally, 
but there is no corresponding dmesg output report.

dirmngr is also complaining in the syslog:

Sep  5 23:58:42 coyote dirmngr[2677]: no CRL available for issuer id 
5E6738A53D3E002778FCD309C3695592BBBC4318
Sep  5 23:58:42 coyote dirmngr[2677]: error 
retrieving 'http://crl.disa.mil/crl/DODEMAILCA_31.crl': http status 404
Sep  5 23:58:42 coyote dirmngr[2677]: crl_fetch via DP failed: No data
Sep  5 23:58:42 coyote dirmngr[2677]: command 'ISVALID' failed: No data
Sep  5 23:58:42 coyote dirmngr[2677]: command 'ISVALID' failed: No CRL 
known
Sep  5 23:58:43 coyote dirmngr[2677]: no CRL available for issuer id 
5E6738A53D3E002778FCD309C3695592BBBC4318
Sep  5 23:58:43 coyote dirmngr[2677]: error 
retrieving 'http://crl.disa.mil/crl/DODEMAILCA_31.crl': http status 404
Sep  5 23:58:43 coyote dirmngr[2677]: crl_fetch via DP failed: No data
Sep  5 23:58:43 coyote dirmngr[2677]: command 'ISVALID' failed: No data
Sep  5 23:58:43 coyote dirmngr[2677]: command 'ISVALID' failed: No CRL 
known

I have replaced the bios battery, and restored the bios defaults to no 
avail.

I'll next try an older but still stretch kernel.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: stretch: amd64, no dmesg when usb stuff plugged in

[deloptes]

bw wrote:

> Why do you continue with this type of post?  It's a joke.  I'm shocked
> that anybody even answers this stupidity.

Have you not learned to show respect to elderly people?

stretch: amd64, no dmesg when usb stuff plugged in

[Gene Heskett]

Greetings all;

So what utility thats supposed to monitor that, has taken a holiday?

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page