Gene, another common thing to your keyboard problem is that you use USB. Try gpio maybe, see https://www.raspberrypi.org/forums/viewtopic.php?t=155973 3 suggestions there. let the system run till your usb kbs craps out and check a few test keys tied to gpio. if the test keys are good and the usb is bad, then make a matrix keyboard. i didnt look for gpio mouse yet but expect i can find something since there are tiny trackballs for sale. hth tomp btw i just repaired a KIngston USB thumbdrive where the 'media bar' interface chip failed between the usb plug and the memory chips. so i know how fragile usb hdwr is.
On Wed, Jul 10, 2019 at 5:44 AM Gene Heskett <[email protected]> wrote: > I've just had the dead keyboard again, forceing a reboot. > > This is all I can glean from the syslog: > > Jul 9 10:15:11 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 10:16:03 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 10:17:01 coyote CRON[13035]: (root) CMD ( cd / && > run-parts --report /etc/cron.hourly) > Jul 9 10:39:01 coyote CRON[13696]: (root) CMD ( > [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; > then /usr/lib/php/sessionclean; fi) > Jul 9 10:39:30 coyote systemd[1]: Starting Clean php session files... > Jul 9 10:39:30 coyote systemd[1]: Started Clean php session files. > Jul 9 10:42:35 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 10:44:24 coyote smartd[534]: Device: /dev/sda [SAT], SMART Usage > Attribute: 190 Airflow_Temperature_Cel changed from 62 to 61 > Jul 9 10:44:24 coyote smartd[534]: Device: /dev/sda [SAT], SMART Usage > Attribute: 194 Temperature_Celsius changed from 38 to 39 > Jul 9 10:44:24 coyote smartd[534]: Device: /dev/sdc [SAT], SMART Usage > Attribute: 190 Airflow_Temperature_Cel changed from 52 to 51 > Jul 9 10:44:24 coyote smartd[534]: Device: /dev/sdc [SAT], SMART Usage > Attribute: 194 Temperature_Celsius changed from 48 to 49 > Jul 9 10:44:24 coyote smartd[534]: Device: /dev/sdd [SAT], SMART Usage > Attribute: 190 Airflow_Temperature_Cel changed from 60 to 59 > Jul 9 10:44:24 coyote smartd[534]: Device: /dev/sdd [SAT], SMART Usage > Attribute: 194 Temperature_Celsius changed from 40 to 41 > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> > Received signal: wake up > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> ClamAV > update process started at Tue Jul 9 10:48:00 2019 > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> ^Your > ClamAV installation is OUTDATED! > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> ^Local > version: 0.100.3 Recommended version: 0.101.2 > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> DON'T > PANIC! Read > https://www.clamav.net/documents/upgrading-clamav > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> > main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, > builder: sigmgr) > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> > daily.cld is up to date (version: 25505, sigs: 1614490, f-level: > 63, builder: raynman) > Jul 9 10:48:00 coyote freshclam[497]: Tue Jul 9 10:48:00 2019 -> > bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, > builder: neo) > Jul 9 10:50:21 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 10:56:01 coyote CRON[14266]: (gene) CMD (/home/gene/bin/remindX) > Jul 9 11:00:01 coyote clamd[554]: Tue Jul 9 11:00:01 2019 -> SelfCheck: > Database status OK. > Jul 9 11:00:30 coyote systemd[1]: Started Run anacron jobs. > Jul 9 11:00:30 coyote anacron[14433]: Anacron 2.3 started on 2019-07-09 > Jul 9 11:00:30 coyote anacron[14433]: Normal exit (0 jobs run) > Jul 9 11:00:30 coyote systemd[1]: anacron.timer: Adding 3min 53.459313s > random time. > Jul 9 11:05:01 coyote CRON[14553]: (root) CMD > (/usr/bin/clamscan -i -r /opt --log=/root/.clamtk/history/$(date > +%b-%d-%Y).log > 2>/dev/null # clamtk-scan) > Jul 9 11:09:01 coyote CRON[14694]: (root) CMD ( > [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; > then /usr/lib/php/sessionclean; fi) > Jul 9 11:09:30 coyote systemd[1]: Starting Clean php session files... > Jul 9 11:09:30 coyote systemd[1]: Started Clean php session files. > Jul 9 11:17:01 coyote CRON[14936]: (root) CMD ( cd / && > run-parts --report /etc/cron.hourly) > Jul 9 11:22:01 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 11:25:45 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 11:28:23 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 11:39:01 coyote CRON[15569]: (root) CMD ( > [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; > then /usr/lib/php/sessionclean; fi) > Jul 9 11:39:30 coyote systemd[1]: Starting Clean php session files... > Jul 9 11:39:30 coyote systemd[1]: Started Clean php session files. > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> > Received signal: wake up > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> ClamAV > update process started at Tue Jul 9 11:48:00 2019 > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> ^Your > ClamAV installation is OUTDATED! > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> ^Local > version: 0.100.3 Recommended version: 0.101.2 > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> DON'T > PANIC! Read > https://www.clamav.net/documents/upgrading-clamav > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> > main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, > builder: sigmgr) > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> > daily.cld is up to date (version: 25505, sigs: 1614490, f-level: > 63, builder: raynman) > Jul 9 11:48:00 coyote freshclam[497]: Tue Jul 9 11:48:00 2019 -> > bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, > builder: neo) > Jul 9 11:51:50 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 11:56:01 coyote CRON[16070]: (gene) CMD (/home/gene/bin/remindX) > Jul 9 11:59:18 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 12:00:01 coyote clamd[554]: Tue Jul 9 12:00:01 2019 -> SelfCheck: > Database status OK. > Jul 9 12:03:34 coyote usbhid-ups[757]: libusb_get_report: could not > claim interface 0: Device or resource busy > Jul 9 12:04:24 coyote systemd[1]: Started Run anacron jobs. > Jul 9 12:04:24 coyote anacron[16305]: Anacron 2.3 started on 2019-07-09 > Jul 9 12:04:24 coyote anacron[16305]: Normal exit (0 jobs run) > Jul 9 12:04:24 coyote systemd[1]: anacron.timer: Adding 2min 25.947281s > random time. > Jul 9 12:09:01 coyote CRON[16428]: (root) CMD ( > [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; > then /usr/lib/php/sessionclean; fi) > Jul 9 12:09:14 coyote systemd[1]: Starting Clean php session files... > Jul 9 12:09:14 coyote systemd[1]: Started Clean php session files. > Jul 9 12:09:16 coyote org.a11y.atspi.Registry[2141]: XIO: fatal IO > error 11 (Resource temporarily unavailable) on X server ":0" > Jul 9 12:09:16 coyote org.a11y.atspi.Registry[2141]: after 121757 > requests (121757 known processed) with 0 events remaining. > > Note that both libusb, and usbhid are fussing although usbhid is my ups > and doesn't normally fuss loud enough to get my attention and since I > have a 20kw generac in the back yard that starts in just 3 or 4 secs on > a power failure, I really don't care. I think, since its running a > nearly constant stream of data every 3 or 4 seconds, that its serving > as a watchdog for libusb performance. I note the above doesn't mention > the keyboard, but with one exception, the mouse remains functional. > That points at the keyboard. but this is the 3rd copy of that keyboard > since all this fufurah started. A brand new one this time. > > But because of this, I have not updated any of my x86 machines from > wheezy. > > Because I am playing with the pi-3b, currently running the new buster > with > 11x faster video, ( yippee! ) and I've built its kernel, a 4.19.50-rt-v7, > but I have yet to convince dpkg-buildpackage to make me a u-boot > version, missing the debian/config file. I can't find it either despite > installing a gig+ of new stuff that apt-catche search *thinks* might be > related. > > Thats a several year old error that my web search's say has long been > fixed on x86 stuff. But I've not found WHAT fixed it. > > Point being I have that kernel src, and if no one has any ideas how to > keep > my keyboard working, I might see if I can build it for this machine and > take it for a walk... > > 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> > > > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
