linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hamza Attak <hamza@attak.fr>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: "Filipe Laíns" <lains@archlinux.org>,
	"Nestor Lopez Casado" <nlopezcasad@logitech.com>,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: hid-logitech-hidpp / hid-logitech-dj driver hiding inputs and breaking Logitech G700s buttons
Date: Mon, 16 Dec 2019 17:33:07 +0000	[thread overview]
Message-ID: <1576517587.26677.1@auth.smtp.1and1.fr> (raw)
In-Reply-To: <CAN+gG=HP2gW3TTeAapb5p5DfVY3QKFmprFw3NZgJTA9Xi1V3xg@mail.gmail.com>

Hi Benjamin,

Yes I have macros on these buttons, most of them are the ones 
pre-recorded from
the Logitech Windows software (Previous, Forward, Ctrl+Tab, 
Ctrl+Shift+Tab). I
also have two custom ones which are Ctrl+W and Ctrl+T, respectively on 
G9 and
G10.

I do have an input recorded on hid-recorder. Thank you for the link.
Please find below the isolated output for each of the problematic 
buttons:

g06_ctrl_alt_tab.txt
	# ReportID: 16 /Vendor Defined Page 1 ['01', '41', '07', '12', '2a', 
'10']
	E: 000229.982728 7 10 01 41 07 12 2a 10
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000229.985686 9 02 00 00 00 00 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '00', '10', '00', 
'00']
	E: 000229.993657 7 10 01 81 00 10 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '80', '00', '00', '00', 
'00']
	E: 000230.005685 7 10 01 80 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '07', '01', '00', 
'00']
	E: 000230.017710 7 10 01 81 07 01 00 00
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000230.170755 9 02 00 00 00 00 00 00 00 00

g07_ctrl_tab.txt
	# ReportID: 16 /Vendor Defined Page 1 ['01', '41', '07', '12', '2a', 
'10']
	E: 000204.737718 7 10 01 41 07 12 2a 10
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000204.740705 9 02 00 00 00 00 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '00', '10', '00', 
'00']
	E: 000204.748724 7 10 01 81 00 10 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '80', '00', '00', '00', 
'00']
	E: 000204.760914 7 10 01 80 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '07', '01', '00', 
'00']
	E: 000204.772824 7 10 01 81 07 01 00 00
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000204.907710 9 02 00 00 00 00 00 00 00 00

g08_battery_level.txt (on-mice LED display only)
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000635.415154 9 02 00 00 00 00 00 00 00 00
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000635.718188 9 02 00 00 00 00 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '07', '01', '00', 
'00']
	E: 000635.970283 7 10 01 81 07 01 00 00

g09_ctrl_w.txt
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000162.848869 9 02 00 00 00 00 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '41', '07', '12', '2a', 
'10']
	E: 000162.858891 7 10 01 41 07 12 2a 10
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '00', '10', '00', 
'00']
	E: 000162.875925 7 10 01 81 00 10 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '80', '00', '00', '00', 
'00']
	E: 000162.887846 7 10 01 80 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '07', '01', '00', 
'00']
	E: 000162.899826 7 10 01 81 07 01 00 00
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000163.100815 9 02 00 00 00 00 00 00 00 00

g10_ctrl_t.txt
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000046.352043 9 02 00 00 00 00 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '41', '07', '12', '2a', 
'10']
	E: 000046.364976 7 10 01 41 07 12 2a 10
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '00', '10', '00', 
'00']
	E: 000046.381939 7 10 01 81 00 10 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '80', '00', '00', '00', 
'00']
	E: 000046.394148 7 10 01 80 00 00 00 00
	# ReportID: 16 /Vendor Defined Page 1 ['01', '81', '07', '01', '00', 
'00']
	E: 000046.406072 7 10 01 81 07 01 00 00
	# ReportID: 2 / Button: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	| X: 0 | Y: 0 | Wheel: 0 | AC Pan: 0
	E: 000046.600971 9 02 00 00 00 00 00 00 00 00

For info, all the mouse functionalities seems to work fine with bare 
usbhid
driver and upower picking up the battery level, is there a feature 
added or a
specific reason to use Logitech drivers?

Thanks,
Hamza.


On Mon, 16 Dec, 2019 at 3:41 PM, Benjamin Tissoires 
<benjamin.tissoires@gmail.com> wrote:
> On Mon, Dec 16, 2019 at 2:48 AM Filipe Laíns <lains@archlinux.org> 
> wrote:
>> 
>>  On Mon, 2019-12-16 at 01:12 +0000, Hamza Attak wrote:
>>  > Hi Filipe,
>>  >
>>  > I'm on the latest 5.4.3 from kernel from kernel.org git 
>> repository. Only
>>  > a few security options are tweaked in the kconfig.
>>  > For your information, I am also facing the same issue on untouched
>>  > Ubuntu
>>  > built kernels,
>>  >
>>  > I never followed linux-input before and don't know how active was 
>> the
>>  > code
>>  > taking care of the G700s, but do you think there might have been a
>>  > regression
>>  > since you say that it was a fixed issue?
>>  >
>>  > Unfortunately, I didn't keep track on when it happened, ie after a
>>  > kernel
>>  > upgrade or if it was always there and I only noticed after trying 
>> the
>>  > mouse
>>  > wirelessly.
>>  >
>>  > Thanks,
>>  > Hamza ATTAK.
>>  >
>> 
>>  Okay. Do the logs show anything interesting?
>> 
>>  I don't have the mouse but I think Benjamin does. Let's see if he 
>> knows
>>  what's going on.
> 
> Hmm, I just gave a test on the G700 (not s) that I have, and  in both
> cases (wired or not), I can see the incoming button events *when they
> are mapped to something meaningful*.
> 
> FYI, 0xC531 wireless receiver has been added in v5.4, so that is when
> you must have seen your problem appearing.
> 
> So:
> - have you mapped any special buttons/macros to those buttons 
> (G6-G10)?
> - can we get the output of hid-recorder[1] so see what the mouse
> actually sends (both in wired or wireless mode)?
> 
> Cheers,
> Benjamin
> 
> [1] https://gitlab.freedesktop.org/libevdev/hid-tools


      reply	other threads:[~2019-12-16 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15 19:34 hid-logitech-hidpp / hid-logitech-dj driver hiding inputs and breaking Logitech G700s buttons Hamza Attak
2019-12-16  0:49 ` Filipe Laíns
2019-12-16  1:12   ` Hamza Attak
2019-12-16  1:48     ` Filipe Laíns
2019-12-16 15:41       ` Benjamin Tissoires
2019-12-16 17:33         ` Hamza Attak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1576517587.26677.1@auth.smtp.1and1.fr \
    --to=hamza@attak.fr \
    --cc=benjamin.tissoires@gmail.com \
    --cc=lains@archlinux.org \
    --cc=linux-input@vger.kernel.org \
    --cc=nlopezcasad@logitech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).