1 |
Le 2015-08-16 17:07, walt a écrit : |
2 |
> On Sun, 16 Aug 2015 21:48:04 +0200 |
3 |
> Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
4 |
> |
5 |
>> On 16/08/2015 21:42, walt wrote: |
6 |
>>> On Sun, 16 Aug 2015 18:58:27 +0200 |
7 |
>>> Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
8 |
>>> |
9 |
>>>> On 16/08/2015 18:45, walt wrote: |
10 |
>>>>> I've been seeing this keyboard problem for the past few weeks: |
11 |
>>>>> after running some command from a bash prompt (haven't tried zsh |
12 |
>>>>> yet) the keyboard stops working. Almost like somebody unplugged |
13 |
>>>>> the keyboard from its usb port (except that the LED on the |
14 |
>>>>> keyboard stays lit so I know the power is still on). |
15 |
>>>>> |
16 |
>>>>> There are no error messages in journalctl or |
17 |
>>>>> in /var/log/Xorg.0.log |
18 |
>>>>> |
19 |
>>>>> I don't know how to change to a console without using a |
20 |
>>>>> ctrl-alt-Fn keystroke from the keyboard (anyone know if it's |
21 |
>>>>> possible?). |
22 |
>>>>> |
23 |
>>>>> When I unplug the keyboard from the usb port I can see the kernel |
24 |
>>>>> recognize the unplug event, which makes me think that it's not a |
25 |
>>>>> kernel/usb bug or a broken wire in the keyboard cable. |
26 |
>>>>> |
27 |
>>>>> When I re-plug the keyboard into a usb port the keyboard |
28 |
>>>>> immediately starts working normally again until the next time I |
29 |
>>>>> happen to trigger the problem by running some black-magical |
30 |
>>>>> command from a command prompt. There is no particular command |
31 |
>>>>> that causes it--it can be any arbitrary command AFAICT. |
32 |
>>>>> |
33 |
>>>>> Just one weird example: I can be typing a URL in a web browser |
34 |
>>>>> window when a bash command finishes running in a terminal window |
35 |
>>>>> and the keyboard stops working in the middle of my typing :( |
36 |
>>>>> |
37 |
>>>>> Any debugging suggestions would be most welcome. |
38 |
>>>> |
39 |
>>>> First step (more to half the problem space than anything else): |
40 |
>>>> |
41 |
>>>> Does the same happen if you use another keyboard? |
42 |
>>> I agree with your assessment -- and I will buy another usb keyboard |
43 |
>>> tomorrow because I'm using the only one I have and this machine has |
44 |
>>> no ps/2 ports. Never thought I'd miss the ps/2 ports til now :) |
45 |
>> I kind of assumed you'd have lots of spare keyboards lying around and |
46 |
>> had already done the test :-) |
47 |
> I do have spares, all ps/2 :-( |
48 |
> |
49 |
>> I recall something similar happening to me, |
50 |
>> perhaps a year ago or longer. I tried to debug it and gave up, then |
51 |
>> one day it was no longer happening. I assumed it was a fixed kernel |
52 |
>> bug then promptly forgot all about it. |
53 |
>> |
54 |
>> While you are waiting on a new keyboard, do you have the same bug on |
55 |
>> different kernels? |
56 |
> Affirmative, and thereby hangs yet another woeful tale. I've been |
57 |
> running the gentoo-sources-3.14.xx series forever because I wearied of |
58 |
> spending so many hours debugging unstable kernels. |
59 |
> |
60 |
> This morning I decided to take a giant leap forward all the way to |
61 |
> 3.18.19 (BTW 3.18.20 is already on kernel.org) because, surely, I |
62 |
> wouldn't need to debug a kernel as old as that, right? |
63 |
> |
64 |
> Wrong. Linus and friends have been marking lots of existing kernel |
65 |
> symbols with the SYMBOL_EXPORT_GNU macro, which was designed to block |
66 |
> the loading of any kernel module not explicitly licensed as GNU |
67 |
> software. (see output of modinfo) |
68 |
> |
69 |
> x11-drivers/ati-drivers installs a proprietary binary blob (as does |
70 |
> nvidia-drivers) so the linker refused even to link the kernel module |
71 |
> into a .ko file, nevermind the kernel actually loading the module at |
72 |
> runtime. |
73 |
> |
74 |
> The remedy for ati-drivers is well-hidden in a comment in a gentoo bug |
75 |
> report that I found at oh-dark-hundred hours this morning. Only two |
76 |
> hours later I got the module installed and loaded :) |
77 |
> |
78 |
> But yes, kernel 3.18.19 still has my same keyboard halting problem, so |
79 |
> I'm back to 3.14.50 until the ati-drivers package is patched. I'm sure |
80 |
> gentoo-sources-3.18.20 will be available almost immediately and I'm not |
81 |
> going through that hell again. |
82 |
> |
83 |
> |
84 |
> |
85 |
I am running Kernel 4.0.5 with no problem with the keyboards. I did encounter one issue, I purchased a French Canadian keyboard off ebay, turned out that the computer box had to be close to the mouse/keyboard otherwise I either lost signal or it was very |
86 |
slow. It seemed that when I would connect and reconnect it would work correctly again. That mouse/keyboard combo was from HP. |
87 |
|
88 |
Is your issue with Logitech remote mouse/keyboard? If so you may want to read about my experience on the subject. |
89 |
|
90 |
I had an issue with Debian on an Olimex A20 Arm board, no issue with ArchLinux on the same board with the same kernel. I found out that the difference was some special options for HID support for Logitech that were disabled by default. Archlinux noticed |
91 |
but not debian, in the debian world they must think that nobody uses logitech devices. |
92 |
|
93 |
This morning I downloaded the latest kernel from sunxi that supports the mali GPU (3.4.103) for my old Mele A2000G, I wanted to upgrade it to Gentoo from SuSE. Someone seemed to have backport the debian bug into it as my logitech keyboard didn't work. |
94 |
After I enabled the HID special support for Logitech, both mouse and keyboard now work perfectly. |
95 |
|
96 |
|
97 |
Michel |
98 |
|
99 |
-- |
100 |
For Linux Software visit |
101 |
http://home.comcast.net/~mcatudal |
102 |
http://sourceforge.net/projects/suzielinux/ |