Does the firmware for Logitech’s G305 mouse get updated through kernel updates? I’ve installed Solaar and don’t see anything about updating the mouse’s firmware. I’ve also looked at fwupdmgr and that doesn’t seem to even see the mouse as something it’ll update.
Hi @heosketelyan Try logitech site for updates for the mouse. You know after update you need to reconnect the mouse.
I don’t see any Downloads on Logitech’s page; is the firmware actually updateable?
I haven’t found any linux downloads at all on Logitech’s sites. As to the firmware being upgradeable, that’s a good question. I THINK it is. On Windows, I had the following software:
which would occasionally say it was updating firmware as well as updating itself. I don’t really care about G-Hub, but I was wondering about the firmware.
I’ll also include the output from:
fwupdmgr get-devices
System Product Name
│
├─KINGSTON SKC3000D2048G:
│ Device ID: 71b677ca0f1bc2c5b804fa1d59e52064ce589293
│ Summary: NVM Express solid state drive
│ Current version: EIFK31.6
│ Vendor: Kingston Technology Company, Inc. (NVME:0x2646)
│ GUIDs: b184d815-dbe0-5c0f-81f2-0b9501d80313
│ e33407c5-cd9a-5688-a7a5-76a1a02b211f
│ fece2d79-2905-5eef-a350-42f09e13e81b
│ a3b32ef4-275f-5e41-badb-43f398f5a799
│ 8db91c1f-712d-5fc3-b251-b7659a22be2e
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs shutdown after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
│
├─System Firmware:
│ │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f
│ │ Summary: UEFI ESRT device
│ │ Current version: 9731
│ │ Minimum Version: 9731
│ │ Vendor: ASUS (DMI:American Megatrends Inc.)
│ │ Update State: Success
│ │ GUIDs: 910a1b7b-350d-507a-b4fd-5512b632202f
│ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • System requires external power source
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI revocation database
│ Current version: 83
│ Minimum Version: 83
│ Vendor: UEFI:Linux Foundation
│ Install Duration: 1 second
│ GUIDs: fda6234b-adcb-5105-8515-9af647d29775
│ f8ff0d50-c757-5dc3-951a-39d86e16f419
│ c6682ade-b5ec-57c4-b687-676351208742
│ f8ba2887-9411-5c36-9cee-88995bb39731
│ 7d5759e5-9aa0-5f0c-abd6-7439bb11b9f6
│ 0c7691e1-b6f2-5d71-bc9c-aabee364c916
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Only version upgrades are allowed
│ • Signed Payload
│
├─UEFI Device Firmware:
│ Device ID: 349bb341230b1a86e5effe7dfe4337e1590227bd
│ Summary: UEFI ESRT device
│ Current version: 335609894
│ Vendor: DMI:American Megatrends Inc.
│ Update State: Success
│ GUID: f766f6e6-b43d-4acd-a4bd-80ff2f0af5cc
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
└─UEFI Device Firmware:
Device ID: 2292ae5236790b47884e37cf162dcf23bfcd1c60
Summary: UEFI ESRT device
Current version: 196608
Vendor: DMI:American Megatrends Inc.
Update State: Success
GUID: f5536e63-e4c0-4e0d-84d4-e8e152b1ba65
Device Flags: • Internal device
• Updatable
• System requires external power source
• Needs a reboot after installation
• Device is usable for the duration of the update
None of that leaps out at me as being for a Logitech mouse or its Unifying Receiver:
lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 08bb:2704 Texas Instruments PCM2704 16-bit stereo audio DAC
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 2516:014d Cooler Master Co., Ltd. ARES
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 046d:c53f Logitech, Inc. USB Receiver
Bus 001 Device 004: ID 1b1c:1b39 Corsair Corsair Gaming K65 RGB RAPIDFIRE Keyboard
Bus 001 Device 003: ID 0b05:1939 ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It seems that Logitech takes care of the firmware updates for LVFS here:
But I do not think I see any for the mice, only some receivers and keyboards. There was also a question here, but it doesn’t seem like they have any plans to add any:
https://github.com/Logitech/fw_updates/issues/31
Perhaps filing an issue there would get more answers, if Logitech is still handling it.
I never thought to check Github (it never occurred to me that a company like Logitech would ever open source anything). That’s pretty amazing. But, I’ve got wonder if that repository has been abandoned. It looks like the last update was 2 years ago and just this morning, I fired up G-Hub on my wife’s Windows 10 machine and it noted one new firmware update to some other mouse.
Oddly, I did find a reference to firmware on:
https://wiki.archlinux.org/title/Logitech_Unifying_Receiver#MouseJack_Vulnerability
Obviously, not Fedora, but in that paragraph, it talks about firmware not being up-to-date and mentions ltunify to check the version and fwupdmgr to update it. I installed ltunify and ran it, but it just throws various errors. And, since it’s version 0.1 from 2013, I guess I can understand why. And, I’ve mentioned above that fwupdmgr doesn’t seem to see anything Logitech on the system.
Interesting that the timestamp at the bottom of the Archwiki page says it was last updated only a couple of months ago. Yet some of what they say just doesn’t work. Of course, that’s Arch and this is Fedora.
Yes, that MouseJack vulnerability is why Logitech added firmware to LVFS:
https://blogs.gnome.org/hughsie/2017/05/22/updating-logitech-hardware-on-linux/
But that seems to have only really affected Unifying receivers, so I’m not sure that running ltunify would be much use, as I don’t think LIGHTSPEED is one?
It looks like the issue is that the G305 uses a Lightspeed receiver instead of the Unifying one:
https://github.com/fwupd/fwupd/issues/4648
hughsie: “I’m afraid the Lightspeed devices don’t have a firmware update capability (at least in fwupd, no idea about Windows) – We only support the Unifying and Bolt devices I’m afraid.”
Oh, well.