I found the bad commit.
git bisect gave me the following:
--------------------------
ab94e562ed45c99914fe874b7feaf75b80ceea84 is the first bad commit
commit ab94e562ed45c99914fe874b7feaf75b80ceea84
Author: Benjamin Tissoires <benjamin.tissoi...@redhat.com>
Date: Tue Sep 30 13:18:28 2014 -0400
HID: logitech: move dj devices to the HID++ module
Devices connected through the Logitech Wireless Receiver are HID++
devices.
We can handle them here to benefit from this new module and activate
enhaced support of the various wireless touchpad or mice with touch
sensors on them.
Signed-off-by: Benjamin Tissoires <benjamin.tissoi...@redhat.com>
Tested-by: Andrew de los Reyes <a...@chromium.org>
Signed-off-by: Jiri Kosina <jkos...@suse.cz>
:040000 040000 d6253d6fe42eba7b80315a2a8a5974afd1d07fa8
c135f1f4cb14cdc5f43595481bfc44f6b074fc45 M drivers
--------------------------
So should I do anything else now, liek pos this info on:
https://bugzilla.kernel.org/show_bug.cgi?id=100631
where I first reported it.
And Is there a way I can track the progres sof this bug?
(First time reporting a kernel bug for me)
Op 01-07-15 om 16:17 schreef Alan Stern:
> On Wed, 1 Jul 2015, Glasswall Information Point wrote:
>
>> Bug as submitted on: https://bugzilla.kernel.org/show_bug.cgi?id=100631
>>
>> Mailing it to this mailing list on advice of greg k-h
>>
>> ------------------------------------------------------------------------------
>>
>> Cannot use the logitech k520 (046d:c52b) to unlock my luks disk at boot time
>>
>> Hitting keyboard keys of this specific kayboard does not register while
>> entering the disk unlock password
>>
>> In the 3.x mail line kernels this does work.
>> in the 4.1 mainline kernel a corded hid keyboard does work but this specific
>> keyboard does not work anymore.
>>
>> The keybaord works fine after boot
>
> Have you tried using "git bisect" to find the kernel commit which
> caused this change in behavior?
>
> Alan Stern
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
