On Wednesday 19 June 2019 12:43:55 pm andy pugh wrote: > On Wed, 19 Jun 2019 at 17:22, Gene Heskett <[email protected]> wrote: > > I ask because I have got to install a kernel that doesn't lose the > > keyboard. My last uptime before it disconnected was about 7 hours. > > Lots of people are using the same kernel. > Not many are using the same keyboard.
The same model of keyboard, a logitech k360 works fine on 4 other machines running older kernels here Andy. This is the only "testing" install. I'm partial to this keyboard as it has square sided keys that reduce the chance of swarf following them down, and locking the key down as it gets wedged between the vertical wall of the key cutout, and the tapered side of the key. Around the machinery its the best keyboard by far. I do have an acer that hasn't a key cutout at all, so swarf doesn't bother it unless its huge but its several inches longer, and theres no place to grab it with one hand and take it to the machine without pressing a bunch of multimedia keys it has a double handfull of around the edges, difficult to pick up with both hands. If I could buy 2 dozen of those, I'd fiddle with the key mapping until those MM keys did nothing and would use them on all my machines. And I think I am buying a discoed item, so anytime I see them I usually buy 2. But they aren't liquid proof, so they eventually succumb to a splash of coffee, darn it. This one is less than 2 weeks old as the previous occupant got wet about 6 weeks back and eventually died. I've just used kpackage to override the hold and install the non-rt version of this same kernel, 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u3, and we'll see how it works. It should be ok since this machine will never actually run hardware, and it will test the fine point of rt vs no rt. It is hard to find in the grub menu, seems the install didn't run grub-update with the right args. I'll think the rt patch is the culprit if, 20 days from now, its still working. But until today, from the testing install, best uptime has been just over 4 days. Thats not at all trustworthy in the shop. IMO. You folks did call it "testing", so I've tested it in everyday use and found it alpha at best when running coyote.coyote.den. But I see something is burning up my cpu, turn out to be heyu relay suck at 100%. Killed it with htop, then sent an off command for a light thats supposed to be off this time of day, which restarts that daemon, and its running fine. And I see kmail is chomping away at something. probably a fouled indice file, but it should get over that in 10-15 minutes. Thanks Andy. 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
