Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.misc > #16904
| From | no.top.post@gmail.com |
|---|---|
| Newsgroups | alt.os.linux.slackware, comp.os.linux.misc, alt.os.linux.debian |
| Subject | Re: Debugging advice? |
| Followup-To | alt.os.linux.slackware, comp.os.linux.misc, alt.os.linux.debian |
| Date | 2016-03-02 17:36 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <nb78aa$ebf$1@dont-email.me> (permalink) |
| References | <n8spbf$p8a$4@dont-email.me> |
Cross-posted to 3 groups.
Followups directed to: alt.os.linux.slackware, comp.os.linux.misc, alt.os.linux.debian
In article <n8spbf$p8a$4@dont-email.me>, Rich <rich@example.invalid> wrote:
> In alt.os.linux.slackware no.top.post@gmail.com wrote:
> > In article <n8r57s$p3q$1@dont-email.me>, Rich <rich@example.invalid> wrote:
--- snip ---
> > Assume that your assistant spilled the water, while you were at Davos
> > for the week. So you don't know the simplistic answer/reason why
> > after several hours usage the system's kybrd & mouse fail. One is
> > ps2, one is USB.
>
> Because your water spill damaged the motherboard, and now some subset
> of components are operating just slightly outside of their engineered
> margins. When digital circuits operate just slightly outside of their
> engineered margins, the result is exactly what you see. Sometimes they
> work, sometimes they don't, for seemingly random occurrences.
>
> Your *only* fix is to replace the motherboard that *you damaged* with a
> new, undamaged, motherboard. And then to keep yourself far away from
> it because you have admitted that you can not be trusted to protect
> your things from damage by your own actions.
>
My syntax is terse.
Subject: Re: *Debugging* advice?
Means I don't need to be told how-to-buy-a-new-one. That's easy.
I want the *knowledge* which the bebugging exercise may provide.
It's interesting [to me] that sometimes the loss of keybrd+mouse
happens a few seconds after I plug the <USB WiFi>.
Which suggests: not a simple hardware error, without some
software <timingloop>.
Since the RPi is next to it and connectable via eth0 [another
absurdity by the 'industry' pretending I need FBI security beween
the 2] perhaps Rpi could look what's happening with the X86?
But I'd need a plan before I tried that.
Especially since this absurd ssh is complaining, and I read there's
a new security protocol with ssh-N?
Why is it more reliable with a short USB-cable to the <WiFi-phone> ?
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Debugging advice? noSpam@gmail.com - 2016-02-02 19:33 +0000
Re: Debugging advice? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2016-02-02 12:05 -0800
Re: Debugging advice? Chick Tower <c.tower@deadspam.com> - 2016-02-04 18:18 +0000
Re: Debugging advice? Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-02-04 12:10 -0800
Re: Debugging advice? Chick Tower <c.tower@deadspam.com> - 2016-02-05 15:07 +0000
Re: Debugging advice? Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-02-05 13:16 -0800
Re: Debugging advice? Michael Black <et472@ncf.ca> - 2016-02-04 15:27 -0500
Re: Debugging advice? Chick Tower <c.tower@deadspam.com> - 2016-02-05 15:07 +0000
Re: Debugging advice? Tonton Th <tTh@nowhere.invalid> - 2016-02-10 16:05 +0000
Re: Debugging advice? Chick Tower <c.tower@deadspam.com> - 2016-02-11 19:13 +0000
Re: Debugging advice? Rich <rich@example.invalid> - 2016-02-02 20:57 +0000
Re: Debugging advice? no.top.post@gmail.com - 2016-02-03 08:24 +0000
Re: Debugging advice? Rich <rich@example.invalid> - 2016-02-03 11:46 +0000
Re: Debugging advice? no.top.post@gmail.com - 2016-03-02 17:36 +0000
Re: Debugging advice? Haines Brown <haines@engels.histomat.net> - 2016-02-20 07:02 -0500
Re: Debugging advice? John Hasler <jhasler@newsguy.com> - 2016-02-20 07:42 -0600
Re: Debugging advice? "Carlos E.R." <robin_listas@invalid.es> - 2016-03-02 19:48 +0100
Re: Debugging advice? Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-02-03 00:46 -0800
Re: Debugging advice? philo <philo@privacy.net> - 2016-02-03 08:34 -0600
Re: Debugging advice? John Hasler <jhasler@newsguy.com> - 2016-02-03 10:06 -0600
csiph-web