Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trouble finding device file on X30-E #2

Open
charliebarber opened this issue Nov 10, 2020 · 3 comments
Open

Trouble finding device file on X30-E #2

charliebarber opened this issue Nov 10, 2020 · 3 comments

Comments

@charliebarber
Copy link

Thanks for taking the time to create this.
I have a Portégé X30-E-12W with Manjaro installed.
I'm having a bit of trouble finding the device file for the accupoint as it is not located in hidraw0. Would you happen to know where to look/how to find it?

xinput shows the SynPS/2 Synaptics TouchPad as well as a Virtual core pointer, which I'm guessing is the accupoint

@GRbit
Copy link
Owner

GRbit commented Nov 10, 2020

Thank you for your question!

On my machine xinput gives me this:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Siliconworks SiW HID Touch Controller   	id=11	[slave  pointer  (2)]
⎜   ↳ TOSB1004:00 06CB:CDDC Mouse             	id=12	[slave  pointer  (2)]
⎜   ↳ TOSB1004:00 06CB:CDDC Touchpad          	id=13	[slave  pointer  (2)]

I'm definitely know that TOSB1004:00 06CB:CDDC Mouse is my accupoint, but I've no clue how it can help me to find dev file.

I've found device file it by running

$ ls /dev/hidraw*
/dev/hidraw0  /dev/hidraw1  /dev/hidraw2

And after that just testing every device if it generates some output when I touch accupoint

$ sudo cat /dev/hidraw0 
���������������� 

"?" symbols are generated only when I touch accupoint.

So after now I can run sudo ./accupoint -d -t 200ms -p /dev/hidraw0

Do not forget sudo since only super user can read hidraw* files

@charliebarber
Copy link
Author

My xinput gets me this:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ TOSHIBA Web Camera - HD: TOSHIB         	id=9	[slave  keyboard (3)]
    ↳ TOSHIBA Web Camera - HD: TOSHIB         	id=10	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=11	[slave  keyboard (3)]
    ↳ Toshiba input device                    	id=13	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]

It seems like the OS isn't recognizing the AccuPoint at all. Libinput also doesn't show it either.
Perhaps it's a kernel or even BIOS related thing. What kernel are you on?

@GRbit
Copy link
Owner

GRbit commented Nov 12, 2020

Now I'm on 5.9.6, but I've got this fix working on X30-F since 5.7.x versions.

I'm regularly update kernel and waiting for a fix, but no one is working on it =( Unfortunately I've got no skills and no time to fix this in kernel.

P.S. If it's not bother you, write in this thread that you are affected with this bug on your X30-E https://bugzilla.kernel.org/show_bug.cgi?id=205817

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants