Re: Update 3 scroll wheel no longer working
Posted: Sat Sep 03, 2011 11:50 pm
Just to let you know after a hard reset everything was working fine, just don't know why it chose the wrong device/driver in the first place!
Support Forum
https://forum.hyperion-entertainment.com/
https://forum.hyperion-entertainment.com/viewtopic.php?t=272
ChrisH wrote:I don't have exactly the same problem, but I believe the cause is the same:
After my Sam440 finishes booting OS4.1u3, my KVM's mouse & keyboard simply don't work (or I only get Y-axis movement of mouse). I had similar (or possibly not so bad) problems with all earlier versions of OS4.1 too. The only way I solved it was by disabling bootmouse & bootkeyboard in Kicklayout. So given this part of the original Kicklayout:I modified it to look like this:MODULE Kickstart/hub.usbfd
MODULE Kickstart/bootmouse.usbfd
MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcdNote that the new "hid" line has to be after some of the usb (uhci/etc) stuff or it doesn't work at all.MODULE Kickstart/hub.usbfd
;MODULE Kickstart/bootmouse.usbfd
;MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcd
;added hid to replace boot#?
MODULE Kickstart/hid.usbfd
From the sound of it, the logic used to disable boot mouse/keyboard needs to be completely rewritten from scratch.
ChrisH wrote:I don't have exactly the same problem, but I believe the cause is the same:
After my Sam440 finishes booting OS4.1u3, my KVM's mouse & keyboard simply don't work (or I only get Y-axis movement of mouse). I had similar (or possibly not so bad) problems with all earlier versions of OS4.1 too. The only way I solved it was by disabling bootmouse & bootkeyboard in Kicklayout. So given this part of the original Kicklayout:I modified it to look like this:MODULE Kickstart/hub.usbfd
MODULE Kickstart/bootmouse.usbfd
MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcdNote that the new "hid" line has to be after some of the usb (uhci/etc) stuff or it doesn't work at all.MODULE Kickstart/hub.usbfd
;MODULE Kickstart/bootmouse.usbfd
;MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcd
;added hid to replace boot#?
MODULE Kickstart/hid.usbfd
From the sound of it, the logic used to disable boot mouse/keyboard needs to be completely rewritten from scratch.
EDIT: I had it pointed out to me that my instructions were incomplete. I forgot to say:Delete SYS:Kickstart/bootkeyboard.usbfd and bootmouse.usbfd.
Delete DEVS:USB/fdclasses/bootkeyboard.fdclass and bootmouse.usbfd.
Move hid.usbfd from DEVS:USB/fd/ to SYS:Kickstart/
I cannot do so much without testing this myself. According to the log, the mouse sends more data than expected in the initial configuration phase. It may be that the ehci driver is more picky about this as the ohci driver is. In the second attempt (after "usbctrl start") it looks like the problem I described in my previous post. If this is true, it would be worth to try another USB 2.0 hub in-between.ssolie wrote:I was thinking the other way around. Software is tad cheaper to send around.mrdarek wrote:well, I live in Poland and not have much money for sending mouse to Hyperion for testing. I suggest buing esperanza mouse EM-102 for test - it low end device and cheap. Google image give picture this mouse on string "ESPERANZA EM102K" - but I not have "K" letter - but mouse looking similar
Man, thank you so much!ChrisH wrote:I don't have exactly the same problem, but I believe the cause is the same:
After my Sam440 finishes booting OS4.1u3, my KVM's mouse & keyboard simply don't work (or I only get Y-axis movement of mouse). I had similar (or possibly not so bad) problems with all earlier versions of OS4.1 too. The only way I solved it was by disabling bootmouse & bootkeyboard in Kicklayout. ...
Solution:
;MODULE Kickstart/bootmouse.usbfd
;MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcd
;added hid to replace boot#?
MODULE Kickstart/hid.usbfd