Logitech diNovo Edge TouchDisc (Touchpad) on Fedora 9

[dsuchter]

I recently updated from F8 to F9. I've had this box running with a Logitech diNovo Edge since F7, and it actually worked originally right out of the box - I just plugged the USB Bluetooth dongle in and the entire keyword instantly worked, including the normal keys, the touchdisc/touchpad, and the volume slider. I never bothered to verify if the special keys worked since I never use them.

With the updated to Fedora 9 the touchdisc no longer runs the mouse on my host. I can clearly see output if I watch /dev/input/mice, so I'm sure the computer is at least seeing events. I also see what looks like happy status messages in dmesg:

usb 5-2: Product: Logitech BT Mini-Receiver
usb 5-2: Manufacturer: Logitech
input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2.2/5-2.2:1.0/input/input3
input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.3-2.2
usb 5-2.2: Product: Logitech BT Mini-Receiver
usb 5-2.2: Manufacturer: Logitech
input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2.3/5-2.3:1.0/input/input4
input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.3-2.3
usb 5-2.3: Product: Logitech BT Mini-Receiver
usb 5-2.3: Manufacturer: Logitech

I never needed an InputDevice section for my mouse before, but I thought maybe that's what was missing now, so I tried adding this to my xorg.conf and restarting X:

Section "InputDevice"
	Identifier "Mouse0"
	Driver "mouse"
	Option "Device" "/dev/input/mice"
	Option "Protocol" "Auto"
EndSection

Any ideas how to get the touchpad working, or what I should do next?

I also have a Logitech diNovi Mini and it has the same problem - the keyboard is fine but the touchpad doesn't work at all. In fact, I normally keep both plugged in to this computer and things work just fine. For now, though, I've unplugged the mini and used that USB spot for an old Logitech iFeel optical mouse, which worked as soon as I plugged it in (hence how I'm driving X for now).

Here are two other FedoraForums threads for reference: I've read them and not found anything particularly useful since they both seem to be in regards to people who's kernels were fundamentally not supporting the diNovo stuff. In my case I know that's not the issue since it used to work. Google/Yahoo also didn't provide anything particularly useful, but feel free to suggest any good sites:
http://forums.fedoraforum.org/showthread.php?t=164397
http://forums.fedoraforum.org/showthread.php?t=149826

[gihalu]

I am having the exact same problem with my Dinovo Edge. I was able to use it without any special configuration when I was using FC8, I was even able to use it with my fresh install of FC9, but when my Kernel updated, I lost the ability to use the touchpad on my keyboard. Any assistance that can be offered will be greatly appreciated.

[dsuchter]

Some people suggested HIDPoint, but the installer binary didn't work. It gave a fairly clear, and expected, "Operating System not supported message: http://www.hidpoint.com/supported_platforms.html

[davisj2]

Does anybody have the solution to this problem? After I applied the FC9 updates my bluetooth logitech mouse quit working. Before the updates everything was working fine. My bluetooth logitech keyboard works fine.

[dsuchter]

I found the solution in the Fedora bugzilla product at Redhat. Here's my blog post about how I solved it:

http://www.opcommando.com/?p=54

and here's the actual bug at redhat:

https://bugzilla.redhat.com/show_bug.cgi?id=456936

[davisj2]

thanks for the reply. What would cause intermittent freezes or hangs on the functioning of mouse/keyboard with FC9?

[dsuchter]

Honestly I'm not sure... the bug I found (a) let to the fix in my case and (b) seems to only make sense for a consistent failure of the mouse/trackpad/touchdisc. Have you tried this xorg.conf solution yet?

In a general sense, I'd suggest getting into the precise details of your system setup and configurations so you can identify the triggers for the intermediate problem. I've found that if you can figure out things that seem to happen at the same time as the failure/success modes, you've found the path to your answer. For example, maybe your keyboard has a "sleep" mode to save power. Perhaps you could <b>tail -f /var/log/messages</b> to see if anything happens, like hardware showing up or disappearing, when you notice the switch from either working to failure or from failure to working. I know that's generic advice but I can't think of much else since I do not seem to be observing the same problem you are.