I bought one K270 it was not unifying but nano receiver. I chose the K270 because it is cheap in Brazil and does what I need. Last week I was looking for a pair of keyboards, on for home desktop and other for work notebook. I have a Anywhere MX at work, I will verify the receiver to see if ti is a older version.Ī side note: Logitech already sneaked new features in unlabeled newer products. Although I have 2 unifying receivers at home, both have same versions so I cannot confirm is this mouse would work with old receiver. So, besides Mouse HID protocol everything is like and I have same problem here. Solaar-cli show does not information like put, but I can see it through GUI My M510 mouse reports as HID++ 1.0, wireless PID 4051 My receiver looks exactly like the newer receiver has, firmware 12.03.B0025 and bootloader 02.15 and other AA.AA It does not report battery nor does it allow turn on/off scrolling and side scrolling features Solaar cannot read my M510 properties too. I just bought a M510 today and here is what I found: I've also tried swapping the pairings (newer mouse paired to older receiver and vice versa), but I still get the same result: Solaar can't read from the newer mouse. I'll admit I am unfamiliar with the exact underlying protocols in play here, but if I were to take an educated guess, I'd say the culprit might be Logitech sneaking newer code into an unlabeled newer model of the M510, specifically the HID++ 4.5 protocol. Plus, the newer mouse is reporting the HID++ 4.5 protocol, not HID++ 1.0 from the older mouse. It looks to me like there's slightly newer firmware on newer receivers (12.03.B0019 compared with 12.03.B0025, with a newer bootloader as well). Notifications: wireless, software present (0x000900) Has 1 paired device(s) out of a maximum of 6. (solaar:17533): Gtk-WARNING **: Theme parsing error: gtk.css:28:4: Junk at end of value for paddingġ2:07:24,779 INFO solaar.ui.notify: starting desktop notificationsġ2:07:24,800 INFO solaar.listener: starting receiver listening threadsġ2:07:24,805 INFO solaar.listener: receiver event add DeviceInfo(path=u'/dev/hidraw0', vendor_id=u'046d', product_id=u'c52b', serial=u'', release='1203', manufacturer='Logitech', product='USB Receiver', interface=2, driver=u'logitech-djreceiver')ġ2:07:24,810 INFO logitech_receiver.listener: started with (13)ġ2:07:24,810 INFO solaar.listener: : notifications listener has started (13)ġ2:07:24,814 INFO logitech_receiver.receiver: : receiver notifications enabled => ('wireless', 'software present')ġ2:07:24,820 INFO solaar.listener: status_changed : present, No paired devices. (solaar:17533): Gtk-WARNING **: Theme parsing error: gtk.css:1:8: Expected a valid selector Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.ġ2:07:24,745 INFO solaar.upower: connected to system dbus, watching for suspend/resume events usr/lib/python2.7/site-packages/solaar/ui/tray.py:148: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('Notify', '0.7') before import to ensure that the right version gets loaded. usr/lib/python2.7/site-packages/solaar/ui/notify.py:33: PyGIWarning: Notify was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded. usr/lib/python2.7/site-packages/solaar/gtk.py:34: PyGIWarning: Gtk was imported without specifying a version first. 12:07:24,679 INFO root: language en_IE (UTF-8), translations path None
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |