Moused
Hi, I cant get PS/2 mouse enabled at boot. I have tried moused -f -p */dev/psm0* *-t ps/2* It then starts moused for that particular session but the scroll doesnt work. How do I enable it at boot. Best, Dave
Odp: Moused
try moused_enable=YES in rc.conf Dnia 3-01-2011 o godz. 4:35 Dragon Fly napisał(a): Hi, I cant get PS/2 mouse enabled at boot. I have tried moused -f -p /dev/psm0 -t ps/2 It then starts moused for that particular session but the scroll doesnt work. How do I enable it at boot. Best, Dave
Re: moused + modular xorg 'sticking' ?
On Nov 8, 2007 6:07 AM, Sepherosa Ziehau [EMAIL PROTECTED] wrote: On Nov 8, 2007 10:14 AM, Joe Talbott [EMAIL PROTECTED] wrote: On Wed, Nov 07, 2007 at 07:25:48PM -0500, Chris Turner wrote: Hello all - fishing for similar experiences - has anyone had any problems with ps2 mice getting 'stuck' under X? My problem with /dev/sysmouse is that my mouse pointer will go to upper left corner and can't move anymore. This can easily be reproduced by trying to select a bootmark entry in firefox bookmarks manual. After I switched to use /dev/psm0, the problem seems to go away. I have the exact same problem, only in my case I use a usb mouse. I thought this was related to somebody adding floating point operations in a signal handler or something, possibly related to the following link. http://mail-index.netbsd.org/pkgsrc-users/2007/08/06/0008.html But maybe I am just confused. Nuno
Re: moused + modular xorg 'sticking' ?
On Thu, Nov 08, 2007 at 02:07:55PM +0800, Sepherosa Ziehau wrote: My problem with /dev/sysmouse is that my mouse pointer will go to upper left corner and can't move anymore. Sounds like the FPU-used-in-signal handler issue. Joerg
Re: moused + modular xorg 'sticking' ?
On Thu, Nov 08, 2007 at 11:43:46AM +0100, Simon 'corecode' Schubert wrote: First, I am surprised that we don't know about this bug. Second, maybe somebody could elaborate on the manifestation of this bug and if the use of floating point arithmetic is allowed in signal handlers. At least about the second: there's nothing in ISO C suggesting anything else. Joerg
Re: moused + modular xorg 'sticking' ?
Joerg Sonnenberger wrote: On Thu, Nov 08, 2007 at 02:07:55PM +0800, Sepherosa Ziehau wrote: My problem with /dev/sysmouse is that my mouse pointer will go to upper left corner and can't move anymore. Sounds like the FPU-used-in-signal handler issue. do you know what is going on there or do you only know that the fpu has to do something with this? cheers simon signature.asc Description: OpenPGP digital signature
Re: moused + modular xorg 'sticking' ?
On Thu, Nov 08, 2007 at 02:17:21PM +0100, Simon 'corecode' Schubert wrote: Joerg Sonnenberger wrote: On Thu, Nov 08, 2007 at 02:07:55PM +0800, Sepherosa Ziehau wrote: My problem with /dev/sysmouse is that my mouse pointer will go to upper left corner and can't move anymore. Sounds like the FPU-used-in-signal handler issue. do you know what is going on there or do you only know that the fpu has to do something with this? I know that various signal handlers used floating point and the issues reported fall into the category of likely overwritten FPU state. Joerg
Re: moused + modular xorg 'sticking' ?
Matthew Dillon wrote: Should we start saving and restoring the FP context? The ucontext structure does have enough space reserved for it. During the LWP work we expanded the FP save space to 512 bytes. Aaaight .. I took a naive look at trying your idea, and my stack-discipline-foo isn't up to snuff enough to even submit a buggy patch for the time I have to work on it tonight.. in any case, I suppose I'll save my notes, sulk away with my tail between my legs, summarize everything said here into a coherent bug report, and stick with userland patches for a while :) good to hear others have the problem and there's something to try in the future - wish I could do more to fix it right now. Thanks, - Chris
Re: moused + modular xorg 'sticking' ?
:I know that various signal handlers used floating point and the issues :reported fall into the category of likely overwritten FPU state. : :Joerg Should we start saving and restoring the FP context? The ucontext structure does have enough space reserved for it. During the LWP work we expanded the FP save space to 512 bytes. Basically code would have to be added to sendsig() and sigreturn(). sendsig(): * Check if the FP is used by the process. If not, nothing to do. * If it is, but it isn't active, copy the saved state to the ucontext * If it is, and it is currently active, save the current state tp the ucontext. * Set flags in ucontext appropriately to indicate that the FP state has been saved. sigreturn(): * If ucontext has flagged that it holds FP state, restore the FP state from the ucontext. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: moused + modular xorg 'sticking' ?
On Thu, Nov 08, 2007 at 12:05:25PM -0800, Matthew Dillon wrote: :I know that various signal handlers used floating point and the issues :reported fall into the category of likely overwritten FPU state. : :Joerg Should we start saving and restoring the FP context? The ucontext structure does have enough space reserved for it. During the LWP work we expanded the FP save space to 512 bytes. Yes, please. This is a bug after all :-) Joerg
Re: moused + modular xorg 'sticking' ?
On Nov 8, 2007 9:06 PM, Joerg Sonnenberger [EMAIL PROTECTED] wrote: On Thu, Nov 08, 2007 at 12:05:25PM -0800, Matthew Dillon wrote: :I know that various signal handlers used floating point and the issues :reported fall into the category of likely overwritten FPU state. : :Joerg Should we start saving and restoring the FP context? The ucontext structure does have enough space reserved for it. During the LWP work we expanded the FP save space to 512 bytes. Yes, please. This is a bug after all :-) Here's a nice regression test for this issue. http://www.openbsd.org/cgi-bin/cvsweb/src/regress/sys/kern/signal/fpsig/ Nuno
Re: moused + modular xorg 'sticking' ?
Chris Turner wrote: Matthew Dillon wrote: Should we start saving and restoring the FP context? The ucontext I suppose I'll save my notes, sulk away with my tail between my legs, summarize everything said here into a coherent bug report, and stick with userland patches for a while :) one other little detail before I do this - does anyone know what posix has to say about fp in signal handlers? perhaps this is a 'bug' w/r/t standards in xf86-input-mouse ...
moused + modular xorg 'sticking' ?
Hello all - fishing for similar experiences - has anyone had any problems with ps2 mice getting 'stuck' under X? just updated my 1.8 laptop to -HEAD before the Hammer work started + 2007Q3 Pkgsrc (modular-xorg-server-1.3.0) this seems to happen, but only when using sysmouse or perhaps even sysmouse with radeon.. I tried several variations of acpi/noacpi/sysmouse/psm/radeon/vesa and even reverted to the previous 1.24 psm.c, but it seems like only using the direct /dev/psm0 will work 100% with this particular combination since the upgrade.. or perhaps this is something in xorg (was previously on monolithic 2007Q1 build) In any case, since there's so many factors need to do more tests to zero in on this for sure, but thought I'd ask.. Thanks, - Chris
Re: moused + modular xorg 'sticking' ?
On Wed, Nov 07, 2007 at 09:14:47PM -0500, Joe Talbott wrote: On Wed, Nov 07, 2007 at 07:25:48PM -0500, Chris Turner wrote: Hello all - fishing for similar experiences - has anyone had any problems with ps2 mice getting 'stuck' under X? just updated my 1.8 laptop to -HEAD before the Hammer work started + 2007Q3 Pkgsrc (modular-xorg-server-1.3.0) this seems to happen, but only when using sysmouse or perhaps even sysmouse with radeon.. I tried several variations of acpi/noacpi/sysmouse/psm/radeon/vesa and even reverted to the previous 1.24 psm.c, but it seems like only using the direct /dev/psm0 will work 100% with this particular combination since the upgrade.. or perhaps this is something in xorg (was previously on monolithic 2007Q1 build) In any case, since there's so many factors need to do more tests to zero in on this for sure, but thought I'd ask.. I had the same issue with sysmouse but my video is i810. This started when I switched to modular xorg. I haven't tried to use sysmouse lately so don't know if I'm seeing the same thing now. Next time I start Xorg it will be with sysmouse so I'll report here. I have had the same problem recently. I fixed it by downgrading x11/xf86-input-mouse. I am now using xf86-input-mouse-1.2.1 with sysmouse, and all is fine. -- Francois Tigeot
Re: moused + modular xorg 'sticking' ?
On Nov 8, 2007 10:14 AM, Joe Talbott [EMAIL PROTECTED] wrote: On Wed, Nov 07, 2007 at 07:25:48PM -0500, Chris Turner wrote: Hello all - fishing for similar experiences - has anyone had any problems with ps2 mice getting 'stuck' under X? just updated my 1.8 laptop to -HEAD before the Hammer work started + 2007Q3 Pkgsrc (modular-xorg-server-1.3.0) this seems to happen, but only when using sysmouse or perhaps even sysmouse with radeon.. I tried several variations of acpi/noacpi/sysmouse/psm/radeon/vesa and even reverted to the previous 1.24 psm.c, but it seems like only using the direct /dev/psm0 will work 100% with this particular combination since the upgrade.. or perhaps this is something in xorg (was previously on monolithic 2007Q1 build) In any case, since there's so many factors need to do more tests to zero in on this for sure, but thought I'd ask.. I had the same issue with sysmouse but my video is i810. This started when I switched to modular xorg. I haven't tried to use sysmouse lately so don't know if I'm seeing the same thing now. Next time I start Xorg it will be with sysmouse so I'll report here. My problem with /dev/sysmouse is that my mouse pointer will go to upper left corner and can't move anymore. This can easily be reproduced by trying to select a bootmark entry in firefox bookmarks manual. After I switched to use /dev/psm0, the problem seems to go away. Best Regards, sephe -- Live Free or Die
Re: moused + modular xorg 'sticking' ?
On Wed, Nov 07, 2007 at 07:25:48PM -0500, Chris Turner wrote: Hello all - fishing for similar experiences - has anyone had any problems with ps2 mice getting 'stuck' under X? just updated my 1.8 laptop to -HEAD before the Hammer work started + 2007Q3 Pkgsrc (modular-xorg-server-1.3.0) this seems to happen, but only when using sysmouse or perhaps even sysmouse with radeon.. I tried several variations of acpi/noacpi/sysmouse/psm/radeon/vesa and even reverted to the previous 1.24 psm.c, but it seems like only using the direct /dev/psm0 will work 100% with this particular combination since the upgrade.. or perhaps this is something in xorg (was previously on monolithic 2007Q1 build) In any case, since there's so many factors need to do more tests to zero in on this for sure, but thought I'd ask.. I had the same issue with sysmouse but my video is i810. This started when I switched to modular xorg. I haven't tried to use sysmouse lately so don't know if I'm seeing the same thing now. Next time I start Xorg it will be with sysmouse so I'll report here. Joe
Re: moused + modular xorg 'sticking' ?
On Thu, 8 Nov 2007 08:22:13 +0100 Francois Tigeot [EMAIL PROTECTED] wrote: On Wed, Nov 07, 2007 at 09:14:47PM -0500, Joe Talbott wrote: On Wed, Nov 07, 2007 at 07:25:48PM -0500, Chris Turner wrote: Hello all - fishing for similar experiences - has anyone had any problems with ps2 mice getting 'stuck' under X? just updated my 1.8 laptop to -HEAD before the Hammer work started + 2007Q3 Pkgsrc (modular-xorg-server-1.3.0) this seems to happen, but only when using sysmouse or perhaps even sysmouse with radeon.. I tried several variations of acpi/noacpi/sysmouse/psm/radeon/vesa and even reverted to the previous 1.24 psm.c, but it seems like only using the direct /dev/psm0 will work 100% with this particular combination since the upgrade.. or perhaps this is something in xorg (was previously on monolithic 2007Q1 build) In any case, since there's so many factors need to do more tests to zero in on this for sure, but thought I'd ask.. I had the same issue with sysmouse but my video is i810. This started when I switched to modular xorg. I haven't tried to use sysmouse lately so don't know if I'm seeing the same thing now. Next time I start Xorg it will be with sysmouse so I'll report here. I have had the same problem recently. I fixed it by downgrading x11/xf86-input-mouse. I am now using xf86-input-mouse-1.2.1 with sysmouse, and all is fine. I have two machines - both with radeons, both using sysmouse one of which suffers the problem described the other does not. The one that works is using 1.2.1. I hadn't noticed because I always use the keyboard and mouse form that machine with x2x. -- C:WIN | Directable Mirror Arrays The computer obeys and wins.| A better way to focus the sun You lose and Bill collects. |licences available see |http://www.sohara.org/
