Re: stretch: amd64, no dmesg when usb stuff plugged in
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.gheskett@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 <http://geneslinuxbox.net:6309/gene>
Reply to: