Magic Mouse Scrolling not working in Ubuntu 19.04 #38
Comments
|
This is what gets loaded at startup (lsmod | grep hid): hid_apple 16384 0 |
|
(--Moving from a closed issue--) @romanAbrahamovic how much work would supporting Magic Mouse 2 take? (Enabling scrolling, that is) I recon there would be many Linux users happy to buy you a coffee if you got this working... |
|
I found that there is a branch in @rohitpid's fork that is at least a start on getting MM2 to work, but I haven't tested it: https://github.com/rohitpid/Linux-Magic-Trackpad-2-Driver/tree/magicmouse2 |
|
It work i tested |
You mean Magi Mouse 2 scrolling with the above repository link? |
I tested it today, and it worked! thanks @rohitpid |
|
Hi, wondering if anyone can help with debugging an issue on this magicmouse2 driver. I'm using the fork from @rohitpid, unfortunately there's no way to file issues on that repo so I'm commenting here. The mouse connects over bluetooth successfully every time but the scroll wheel does not work until I reload the driver using: These are the logs in |
|
I had the same issue and my mouse would randomly disconnect. I ended up getting rid of my magic mouse and switched to a logitech bluetooth mouse after I couldn't find a solution to the scrolling issue. You may have luck with the "unstable" branch mentioned above. |
|
Hello, I have been scrolling through several of these issues and found some solutions, I decided to pick some of them up and compiled them. Can you please try my solution out? https://github.com/RicardoEPRodrigues/Linux-Magic-Trackpad-2-Driver This should fix 2 problems: Magic Mouse 2 driver not loading after reconnection and random Bluetooth disconnections. |
|
@RicardoEPRodrigues, thanks! I tested out your instructions and they worked well. A couple minor suggestions. This udev configuration works well for me, in your version the second line is missing a comma and a backslash I believe. I was able to view the properties on the mouse via dbus: |
|
Hello, thank you for the input! I updated the Correct me if I'm wrong, but I think this rule goes like: "if an usb device with the product id of I read more info on the device based on this command |
|
Hello again, sorry for the SPAM. My solution doesn't work as is. The way I was trying to do things was to read an id from I trying to find a solution. If we can find a Magic Mouse 2 ID in the If not, then I'm trying to find an ID in the Bluetooth info, with that we can have a script running every time an input device is plugged in, but that script will only load the drive if that device is a Magic Mouse 2. You can help me by posting a file with the output of this command |
|
Ok, I figured it out. I rewrote the rule to catch all the Magic Mouse 2. FINALLY. Check this out: Remember to try my |
|
The second rule works for me. Thanks for your effort! |
|
This isn't working on Elementary OS 5.1.5. Here's the steps I'm taking. Move the original kernel driver hid-magicmouse.ko from my 5.3.0-59-generic kernel and running "depmod -a" then reboot. After the system comes back up I'm following the install instructions (git clone and then running the install.sh as root) and reboot. When the system is back up and I click the mouse it is seen and paired but the pointer doesn't move, the track-pad still works though. Here's the output from my xorg.log: [ 546.767] (II) config/udev: Adding input device (unnamed) (/dev/input/mouse0) Please let me know if you need more info from me. |
|
@ralphsc did you try my fork? https://github.com/RicardoEPRodrigues/Linux-Magic-Trackpad-2-Driver I have a pending pull-request (rohitpid#1) where some discussion has been going on. It might help. |
|
Hi Ricardo,
Yes I was using your fork for this.
I'll take a look at
rohitpid#1 and let
you know how it goes.
…On Fri, Jun 12, 2020 at 9:20 AM Ricardo Rodrigues ***@***.***> wrote:
@ralphsc <https://github.com/ralphsc> did you try my fork?
https://github.com/RicardoEPRodrigues/Linux-Magic-Trackpad-2-Driver
I have a pending pull-request (rohitpid#1
<rohitpid#1>) where
some discussion has been going on. It might help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEM4WWIFX33SAHI74QPYPELRWITQXANCNFSM4HKH6HEQ>
.
|
|
Ricardo,
I tried the suggestions in the link you sent but it's still not working.
This time I installed by running install-fix.sh, the mouse now moves but
without scrolling. I also removed / moved the original kernel
hid-magicmouse.ko driver before starting. Here's the xorg log when the
mouse is loaded:
[ 805.929] (II) config/udev: Adding input device Magic Mouse 2
(/dev/input/mouse0)
[ 805.929] (II) No input driver specified, ignoring this device.
[ 805.929] (II) This device may have been added with another device file.
[ 806.011] (II) config/udev: Adding input device Magic Mouse 2
(/dev/input/event7)
[ 806.011] (**) Magic Mouse 2: Applying InputClass "libinput pointer
catchall"
[ 806.011] (II) Using input driver 'libinput' for 'Magic Mouse 2'
[ 806.011] (**) Magic Mouse 2: always reports core events
[ 806.012] (**) Option "Device" "/dev/input/event7"
[ 806.012] (**) Option "_source" "server/udev"
[ 806.012] (II) event7 - Magic Mouse 2: is tagged by udev as: Mouse
[ 806.012] (II) event7 - Magic Mouse 2: device is a pointer
[ 806.012] (II) event7 - Magic Mouse 2: device removed
[ 806.067] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0/bluetooth/hci0/hci0:12/0005:004C:0269.000A/input/input225/event7"
[ 806.067] (II) XINPUT: Adding extended input device "Magic Mouse 2"
(type: MOUSE, id 13)
[ 806.068] (**) Option "AccelerationScheme" "none"
[ 806.069] (**) Magic Mouse 2: (accel) selected scheme none/0
[ 806.069] (**) Magic Mouse 2: (accel) acceleration factor: 2.000
[ 806.069] (**) Magic Mouse 2: (accel) acceleration threshold: 4
[ 806.070] (II) event7 - Magic Mouse 2: is tagged by udev as: Mouse
[ 806.070] (II) event7 - Magic Mouse 2: device is a pointer
On Fri, Jun 12, 2020 at 9:35 AM Ralph Crongeyer <[email protected]>
wrote:
… Hi Ricardo,
Yes I was using your fork for this.
I'll take a look at
rohitpid#1 and let
you know how it goes.
On Fri, Jun 12, 2020 at 9:20 AM Ricardo Rodrigues <
***@***.***> wrote:
> @ralphsc <https://github.com/ralphsc> did you try my fork?
>
> https://github.com/RicardoEPRodrigues/Linux-Magic-Trackpad-2-Driver
>
> I have a pending pull-request (rohitpid#1
> <rohitpid#1>)
> where some discussion has been going on. It might help.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#38 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEM4WWIFX33SAHI74QPYPELRWITQXANCNFSM4HKH6HEQ>
> .
>
|
|
And just so you can see what happens with the udev rule in place here's the
xorg log output when the mouse is connected:
[ 1845.138] (II) config/udev: Adding input device Magic Mouse 2
(/dev/input/event7)
[ 1845.139] (**) Magic Mouse 2: Applying InputClass "libinput pointer
catchall"
[ 1845.139] (II) Using input driver 'libinput' for 'Magic Mouse 2'
[ 1845.139] (**) Magic Mouse 2: always reports core events
[ 1845.139] (**) Option "Device" "/dev/input/event7"
[ 1845.139] (**) Option "_source" "server/udev"
[ 1845.155] (EE) xf86OpenSerial: Cannot open device /dev/input/event7
No such device.
[ 1845.155] (II) event7: opening input device '/dev/input/event7' failed
(No such device).
[ 1845.155] (II) event7 - failed to create input device
'/dev/input/event7'.
[ 1845.155] (EE) libinput: Magic Mouse 2: Failed to create a device for
/dev/input/event7
[ 1845.155] (EE) PreInit returned 2 for "Magic Mouse 2"
[ 1845.155] (II) UnloadModule: "libinput"
[ 1849.370] (II) config/udev: Adding input device (unnamed)
(/dev/input/mouse0)
[ 1849.370] (II) No input driver specified, ignoring this device.
[ 1849.370] (II) This device may have been added with another device file.
On Fri, Jun 12, 2020 at 9:58 AM Ralph Crongeyer <[email protected]>
wrote:
… Ricardo,
I tried the suggestions in the link you sent but it's still not working.
This time I installed by running install-fix.sh, the mouse now moves but
without scrolling. I also removed / moved the original kernel
hid-magicmouse.ko driver before starting. Here's the xorg log when the
mouse is loaded:
[ 805.929] (II) config/udev: Adding input device Magic Mouse 2
(/dev/input/mouse0)
[ 805.929] (II) No input driver specified, ignoring this device.
[ 805.929] (II) This device may have been added with another device file.
[ 806.011] (II) config/udev: Adding input device Magic Mouse 2
(/dev/input/event7)
[ 806.011] (**) Magic Mouse 2: Applying InputClass "libinput pointer
catchall"
[ 806.011] (II) Using input driver 'libinput' for 'Magic Mouse 2'
[ 806.011] (**) Magic Mouse 2: always reports core events
[ 806.012] (**) Option "Device" "/dev/input/event7"
[ 806.012] (**) Option "_source" "server/udev"
[ 806.012] (II) event7 - Magic Mouse 2: is tagged by udev as: Mouse
[ 806.012] (II) event7 - Magic Mouse 2: device is a pointer
[ 806.012] (II) event7 - Magic Mouse 2: device removed
[ 806.067] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0/bluetooth/hci0/hci0:12/0005:004C:0269.000A/input/input225/event7"
[ 806.067] (II) XINPUT: Adding extended input device "Magic Mouse 2"
(type: MOUSE, id 13)
[ 806.068] (**) Option "AccelerationScheme" "none"
[ 806.069] (**) Magic Mouse 2: (accel) selected scheme none/0
[ 806.069] (**) Magic Mouse 2: (accel) acceleration factor: 2.000
[ 806.069] (**) Magic Mouse 2: (accel) acceleration threshold: 4
[ 806.070] (II) event7 - Magic Mouse 2: is tagged by udev as: Mouse
[ 806.070] (II) event7 - Magic Mouse 2: device is a pointer
On Fri, Jun 12, 2020 at 9:35 AM Ralph Crongeyer ***@***.***>
wrote:
> Hi Ricardo,
> Yes I was using your fork for this.
>
> I'll take a look at
> rohitpid#1 and
> let you know how it goes.
>
> On Fri, Jun 12, 2020 at 9:20 AM Ricardo Rodrigues <
> ***@***.***> wrote:
>
>> @ralphsc <https://github.com/ralphsc> did you try my fork?
>>
>> https://github.com/RicardoEPRodrigues/Linux-Magic-Trackpad-2-Driver
>>
>> I have a pending pull-request (rohitpid#1
>> <rohitpid#1>)
>> where some discussion has been going on. It might help.
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <#38 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/AEM4WWIFX33SAHI74QPYPELRWITQXANCNFSM4HKH6HEQ>
>> .
>>
>
|
|
@ralphsc Unfortunately I don't have a lot of time to try to debug this issue, but here are my thoughts. The Magic Mouse 2 creates 2 devices, one What my repo does is to load the driver for the I believe that for some reason, either the rule isn't being called and that is why you have a mouse moving and no scroll, or the udev rules are removing the If you have some time, please read through 0xABAD repo where the process to get the driver loaded is described. My repo is inspired and improves on his work. |
|
Hey Ricardo,
No worries man. Thanks for the info I'll read through it and if I do figure
it out I'll share what works with this thread.
Thanks again for your time.
Sincerely,
Ralph
…On Sun, Jun 14, 2020 at 3:07 PM Ricardo Rodrigues ***@***.***> wrote:
@ralphsc <https://github.com/ralphsc> Unfortunately I don't have a lot of
time to try to debug this issue, but here are my thoughts.
The Magic Mouse 2 creates 2 devices, one /dev/input/eventX (the touchpad)
and a /dev/input/mouseX (the mouse and buttons). libinput picks up any
mouseX event and loads a driver for it, that is why by default you have a
mouse with no scroll.
What my repo does is to load the driver for the eventX that knows how to
deal with the touchpad.
I believe that for some reason, either the rule isn't being called and
that is why you have a mouse moving and no scroll, or the udev rules are
removing the mouseX, but still loading the driver, which results in the
touchpad working, but not the mouse.
If you have some time, please read through 0xABAD repo
<https://github.com/0xABAD/magic-mouse-2> where the process to get the
driver loaded is described. My repo is inspired and improves on his work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEM4WWM5Y6I2XMK2WEWOJM3RWUNYNANCNFSM4HKH6HEQ>
.
|
|
On Elementary OS I had to add a DRIVER section to get it to work, like so:
SUBSYSTEM=="input", \
KERNEL=="mouse*", \
KERNELS=="0005:004C:0269.*"
SUBSYSTEMS=="hid", \
DRIVERS=="hid-generic", \
ACTION=="add", \
SYMLINK+="input/magicmouse-%k", \
RUN+="/opt/magic-mouse-fix/magic-mouse-2-add.sh"
…On Sun, Jun 14, 2020 at 3:07 PM Ricardo Rodrigues ***@***.***> wrote:
@ralphsc <https://github.com/ralphsc> Unfortunately I don't have a lot of
time to try to debug this issue, but here are my thoughts.
The Magic Mouse 2 creates 2 devices, one /dev/input/eventX (the touchpad)
and a /dev/input/mouseX (the mouse and buttons). libinput picks up any
mouseX event and loads a driver for it, that is why by default you have a
mouse with no scroll.
What my repo does is to load the driver for the eventX that knows how to
deal with the touchpad.
I believe that for some reason, either the rule isn't being called and
that is why you have a mouse moving and no scroll, or the udev rules are
removing the mouseX, but still loading the driver, which results in the
touchpad working, but not the mouse.
If you have some time, please read through 0xABAD repo
<https://github.com/0xABAD/magic-mouse-2> where the process to get the
driver loaded is described. My repo is inspired and improves on his work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEM4WWM5Y6I2XMK2WEWOJM3RWUNYNANCNFSM4HKH6HEQ>
.
|
|
@ralphsc Great to know you got it working! I tried to use your Thank you! |
|
I tried it and it didn't work for me. If I change the udev rule, disconnect
the mouse, unload the driver and click the mouse it pair's with BT and is
connected but no mouse movement. When I change the rule back and disconnect
the mouse, unload the driver and click the mouse it pair's with BT and it
all works.
This is on:
elementary OS 5.1.5 Hera
5.3.0-59-generic
On a MAC Book Pro 2013 era.
…On Thu, Jun 18, 2020 at 5:56 PM Ricardo Rodrigues ***@***.***> wrote:
@ralphsc <https://github.com/ralphsc> Great to know you got it working!
I tried to use your udev rule and it didn't work for me. I don't have any
parent with DRIVERS=="hid-generic". I made some changes, can you try to
run this version and check if it works?
SUBSYSTEM=="input", \
KERNEL=="mouse*", \
DRIVER=="", \
SUBSYSTEMS=="hid", \
KERNELS=="0005:004C:0269*", \
DRIVERS=="magicmouse", \
ACTION=="add", \
SYMLINK+="input/magicmouse-%k", \
RUN+="/opt/magic-mouse-fix/magic-mouse-2-add.sh"
Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEM4WWKY3Y5PTEPAG7BV4GLRXKEQJANCNFSM4HKH6HEQ>
.
|
|
Can you show me the output of I edited my previous answer to have Can you try the following option (I removed the Also, what is the version of you |
|
udev: |
|
It didn't work with that rule either. It seems that if I have "magicmouse" as a driver it fails to function. lsmod | grep hid |
|
Can you show me the output of |
|
Sure thing. FYI, it does show DRIVERS=="magicmouse" but it doesn't work in
my udev rule.
udevadm info -a -p $(udevadm info -q path -n /dev/input/mouse0)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0017/input/input143/mouse0':
KERNEL=="mouse0"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0017/input/input143':
KERNELS=="input143"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="Magic Mouse 2"
ATTRS{phys}=="3c:15:c2:da:0a:27"
ATTRS{properties}=="0"
ATTRS{uniq}=="ac:bc:32:e6:54:80"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0/bluetooth/hci0/hci0:11/0005:004C:0269.0017':
KERNELS=="0005:004C:0269.0017"
SUBSYSTEMS=="hid"
DRIVERS=="magicmouse"
ATTRS{country}=="00"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0/bluetooth/hci0/hci0:11':
KERNELS=="hci0:11"
SUBSYSTEMS=="bluetooth"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0/bluetooth/hci0':
KERNELS=="hci0"
SUBSYSTEMS=="bluetooth"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3/1-8.3:1.0':
KERNELS=="1-8.3:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="btusb"
ATTRS{authorized}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bInterfaceProtocol}=="01"
ATTRS{bInterfaceSubClass}=="01"
ATTRS{bNumEndpoints}=="03"
ATTRS{supports_autosuspend}=="1"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.3':
KERNELS=="1-8.3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{authorized}=="1"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bDeviceClass}=="ff"
ATTRS{bDeviceProtocol}=="01"
ATTRS{bDeviceSubClass}=="01"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bMaxPower}=="0mA"
ATTRS{bNumConfigurations}=="1"
ATTRS{bNumInterfaces}==" 4"
ATTRS{bcdDevice}=="0137"
ATTRS{bmAttributes}=="e0"
ATTRS{busnum}=="1"
ATTRS{configuration}==""
ATTRS{devnum}=="6"
ATTRS{devpath}=="8.3"
ATTRS{idProduct}=="8289"
ATTRS{idVendor}=="05ac"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Apple Inc."
ATTRS{maxchild}=="0"
ATTRS{product}=="Bluetooth USB Host Controller"
ATTRS{quirks}=="0x0"
ATTRS{removable}=="fixed"
ATTRS{rx_lanes}=="1"
ATTRS{speed}=="12"
ATTRS{tx_lanes}=="1"
ATTRS{urbnum}=="137628"
ATTRS{version}==" 2.00"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-8':
KERNELS=="1-8"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{authorized}=="1"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bMaxPacketSize0}=="8"
ATTRS{bMaxPower}=="94mA"
ATTRS{bNumConfigurations}=="1"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bcdDevice}=="0100"
ATTRS{bmAttributes}=="e0"
ATTRS{busnum}=="1"
ATTRS{configuration}==""
ATTRS{devnum}=="2"
ATTRS{devpath}=="8"
ATTRS{idProduct}=="4500"
ATTRS{idVendor}=="0a5c"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Apple Inc."
ATTRS{maxchild}=="3"
ATTRS{product}=="BRCM20702 Hub"
ATTRS{quirks}=="0x0"
ATTRS{removable}=="unknown"
ATTRS{rx_lanes}=="1"
ATTRS{speed}=="12"
ATTRS{tx_lanes}=="1"
ATTRS{urbnum}=="4430"
ATTRS{version}==" 2.00"
looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{authorized}=="1"
ATTRS{authorized_default}=="1"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceProtocol}=="01"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bMaxPower}=="0mA"
ATTRS{bNumConfigurations}=="1"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bcdDevice}=="0503"
ATTRS{bmAttributes}=="e0"
ATTRS{busnum}=="1"
ATTRS{configuration}==""
ATTRS{devnum}=="1"
ATTRS{devpath}=="0"
ATTRS{idProduct}=="0002"
ATTRS{idVendor}=="1d6b"
ATTRS{interface_authorized_default}=="1"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 5.3.0-59-generic xhci-hcd"
ATTRS{maxchild}=="14"
ATTRS{product}=="xHCI Host Controller"
ATTRS{quirks}=="0x0"
ATTRS{removable}=="unknown"
ATTRS{rx_lanes}=="1"
ATTRS{serial}=="0000:00:14.0"
ATTRS{speed}=="480"
ATTRS{tx_lanes}=="1"
ATTRS{urbnum}=="2072"
ATTRS{version}==" 2.00"
looking at parent device '/devices/pci0000:00/0000:00:14.0':
KERNELS=="0000:00:14.0"
SUBSYSTEMS=="pci"
DRIVERS=="xhci_hcd"
ATTRS{ari_enabled}=="0"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0330"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{d3cold_allowed}=="1"
ATTRS{device}=="0x8c31"
ATTRS{dma_mask_bits}=="64"
ATTRS{driver_override}=="(null)"
ATTRS{enable}=="1"
ATTRS{irq}=="37"
ATTRS{local_cpulist}=="0-7"
ATTRS{local_cpus}=="ff"
ATTRS{msi_bus}=="1"
ATTRS{numa_node}=="-1"
ATTRS{revision}=="0x05"
ATTRS{subsystem_device}=="0x7270"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{vendor}=="0x8086"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
|
|
This is going to be a long text. Sorry in advance. So, the I think you can try this out the following way:
Sorry for the work, but can you check if this happens? Another thing also came to mind from your previous comments. First off, it seems you only have one mouse connect and it is the magic mouse (because the mouse is assigned Second, Why am I asking these questions? I think that when the |
|
Sorry for the spam. I now believe this is not an ElementaryOS issue, but rather I believe this is an issue that happens only when you don't have another mouse connected. (Can you give me the output of I made a commit to my repo. Before loading the magic mouse driver, the script now also loads the 🤞Let's hope it works! |
|
OK, I'll give it a shot and report back. Here's you go:
ls /dev/input/
by-id event1 event12 event15 event3 event6 event9 mouse1
by-path event10 event13 event16 event4 event7 mice
event0 event11 event14 event2 event5 event8 mouse0
…On Fri, Jun 19, 2020 at 6:13 AM Ricardo Rodrigues ***@***.***> wrote:
Sorry for the spam.
I now believe this is not an ElementaryOS issue, but rather I believe this
is an issue that happens only when you don't have another mouse connected.
(Can you give me the output of ls /dev/input)
I made a commit to my repo. Before loading the magic mouse driver, the
script now also loads the hid-generic driver. @ralphsc
<https://github.com/ralphsc> can you please give it a try?
🤞Let's hope it works!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEM4WWLKGXOLATGZOZP5G3LRXM23HANCNFSM4HKH6HEQ>
.
|
|
I only have one mouse and of course the trackpad on the laptop. I don't have another mouse at the moment. I tried your changes to the script, mine looks like this now: #!/bin/sh FILE=/tmp/magicmouse-driveload reload() { } reload & The udev rule just will not load the driver with "magicmouse" in it. my current working rule is this: SUBSYSTEM=="input", Thanks for all your help with this. |
|
Use my |
|
I've tried it that way, it fails to load the driver. |
|
I believe your version of Also, can you get to the situation where the mouse connects but does nothing and send me the |
|
I have fought this for a day. I've managed to get basically nowhere. I've tried every reasonable variation I can think of, but ultimately, this just isn't working for me. I tried removing the line where I'm on ubuntu 18.04, kernel version 5.4.0-52-generic. My mouse is recognized on my system as I have a lot of different outputs, but this one seems to be the one that is most common. Nothing at all works with the mouse, neither motion nor scrolling. I am using the udev rule and the shell script at the head of the Disconnecting and reconnecting without changing anything results in this similar log output: This is the I have verified that in the I'm not using anything special in terms of system configuration. My system is pretty vanilla. I can't help but wonder if it's because I'm still on 18.04. I learned earlier today that ubuntu 20.04.1 LTS is available. I can't now, but at some point in the near future, I'll upgrade the OS and maybe try again. If there's anything y'all know of or can suggest or recommend, I would appreciate it. |
|
Sorry for spam. I also found this. Perhaps I should look at altering my xorg conf files to recogize this particular device? |
|
@landon-hemsley you might be on to something. I know it works on newer systems, but I also have complaints about it not working on ElementaryOS 5 which is based on Ubuntu 18.04 if I'm not wrong. After a quick search I found this sentence online:
It come from Kubuntu Wiki and it is a worthy read. I tested it on Pop_OS 20.04 and even with an X.org file it works fine, yet my guess is that it does not apply to older X.org versions. In the same page, I also found this section interesting:
Which got me thinking if changing the name of the PS: I'm no expert and I'm learning as I go, so for me it is a lot of trial and error. I wish I knew more to be able to great an actual great driver. (Just placing a useful URL for later use regarding mouse X.org rules) |
|
FWIW, and just to close the loop on this, I upgraded my system to 20.04.1, went through the process of re-installing the driver and applied @RicardoEPRodrigues 's fix. It worked! So, my recommendation: Upgrade! lol. |
|
trying on Manjaro - scrolling worked fine ~ 5 hours and after that doesn't work again. I followed all steps from instruction from forked README. @RicardoEPRodrigues any ideas, what can be wrong? |
|
@akozyreva hey! I don't know if I commented this or not, but normally after some OS updates the drivers stops working and I have to "reinstall" it. Normally running |
|
It worked for me too but I find that often the right mouse button is registered as a left mouse button or some time both. Also when selecting text and trying to right click it. It just deselects it and moves the text cursor just as a left click would. I'm on Ubuntu 20.04 is anybody able to reproduce this? |
I had this module working in 18.04 with the 4.20... kernel without issues. I know it has been implemented into the release but the scrolling isn't working. I've tried rmmod and insmod under the 5.0.0-13 kernel with 19.04 but no joy. This is with the Magic Mouse 2 and not the trackpad.
Am I missing something? Any info that could be relevant I can provide?
The text was updated successfully, but these errors were encountered: