Re: Mouse Problems.
Thank You. It is working now. -- Best Regards, Mubeesh Ali.V.M On Fri, Jul 8, 2011 at 11:11 PM, Lokadamus wrote: > Put in your rc.conf this: > dbus_enable="YES" > hald_enable="YES" > > reboot your system or start it with: > > # /usr/local/etc/rc.d/hald start > # /usr/local/etc/rc.d/dbus start > > then your mouse and keybord should working. > > > > Am 07.07.2011 09:31, schrieb Mubeesh ali: >> >> Hi List, >> >> I have freebsd 8.2 installed on a windows host with virtualbox and >> have xfce4. From sysinstall i was able to enable and move the mouse. >> But as soon as i do a startx it gets frozen(pointer is visible at >> center of the screen ) >> >> reebsd# cat /etc/rc.conf >> >> # -- sysinstall generated deltas -- # Tue Jul 5 16:03:57 2011 >> # Created: Tue Jul 5 16:03:57 2011 >> # Enable network daemons for user convenience. >> # Please make all changes to this file, not to /etc/defaults/rc.conf. >> # This file now contains just the overrides from /etc/defaults/rc.conf. >> check_quotas="NO" >> hostname="Freebsd.merunetworks.com" >> ifconfig_em0="DHCP" >> inetd_enable="YES" >> ipv6_enable="YES" >> keymap="us.iso" >> moused_enable="YES" >> moused_port="/dev/psm0" >> moused_flags="-z 4" >> moused_type="auto" >> ntpdate_enable="YES" >> ntpdate_hosts="asia.pool.ntp.org" >> sshd_enable="YES" >> # -- sysinstall generated deltas -- # Wed Jul 6 11:35:07 2011 >> #moused_flags="" >> #moused_port="/dev/psm0" >> #moused_type="microsoft" >> #moused_enable="YES" >> > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Mouse Problems.
Put in your rc.conf this: dbus_enable="YES" hald_enable="YES" reboot your system or start it with: # /usr/local/etc/rc.d/hald start # /usr/local/etc/rc.d/dbus start then your mouse and keybord should working. Am 07.07.2011 09:31, schrieb Mubeesh ali: Hi List, I have freebsd 8.2 installed on a windows host with virtualbox and have xfce4. From sysinstall i was able to enable and move the mouse. But as soon as i do a startx it gets frozen(pointer is visible at center of the screen ) reebsd# cat /etc/rc.conf # -- sysinstall generated deltas -- # Tue Jul 5 16:03:57 2011 # Created: Tue Jul 5 16:03:57 2011 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. check_quotas="NO" hostname="Freebsd.merunetworks.com" ifconfig_em0="DHCP" inetd_enable="YES" ipv6_enable="YES" keymap="us.iso" moused_enable="YES" moused_port="/dev/psm0" moused_flags="-z 4" moused_type="auto" ntpdate_enable="YES" ntpdate_hosts="asia.pool.ntp.org" sshd_enable="YES" # -- sysinstall generated deltas -- # Wed Jul 6 11:35:07 2011 #moused_flags="" #moused_port="/dev/psm0" #moused_type="microsoft" #moused_enable="YES" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, 13 Oct 2010, Polytropon wrote: Finally, a "jumpy mouse" problem with moused on console screams that it's the KVM, not moused or USB or xorg config. I'm not 100% sure about that. Your article located at http://www.wonkity.com/~wblock/docs/html/aei.html states: Other times, particularly if hald is running, typed characters don't show up on the screen until the mouse is moved, and mouse movement itself is jerky and doesn't react smoothly. I thought about something like that. That happens in X. I don't recall any problems in console mode, but may not have tested it. USB mice cause moused to be run anyway, but there are differences. If you want switching between X and console to be fast, enable moused. And this is possible in combination with devd that "remote-contols" moused for USB mice? And does moused handle "disappearing" and "reappearing" devices properly? AFAIK, yes. Try it: with a USB mouse, set moused_enable="NO", reboot, switch from console to X and back with alt-f9 and then ctrl-alt-f1. Note the delay, particularly switching from console to X. Now enable moused, reboot, and try it again. I don't know what causes the difference. Certainly it's something that could be tolerated if you don't switch between console and X much. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, 13 Oct 2010, Polytropon wrote: On Wed, 13 Oct 2010 10:29:31 -0700, Gary Kline wrote: I just noticed that in rc.conf is: # -- sysinstall generated deltas -- # Wed Oct 13 08:03:06 2010 moused_port="/dev/ums0" moused_type="auto" moused_enable="NO" and yet the console mouse is present. Strange... . Explaination: USB mice are handled by devd. So if the system detects the presence of a ums device, devd "remote-controls" moused to activate this mouse. See also the entry in /etc/defaults/rc.conf: moused_nondefault_enable="YES" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, Oct 13, 2010 at 11:11:22PM +0200, Polytropon wrote:
> On Wed, 13 Oct 2010 10:29:31 -0700, Gary Kline wrote:
> > I just noticed that in rc.conf is:
> >
> >
> > # -- sysinstall generated deltas -- # Wed Oct 13 08:03:06 2010
> > moused_port="/dev/ums0"
> > moused_type="auto"
> > moused_enable="NO"
> >
> > and yet the console mouse is present. Strange... .
>
> Explaination: USB mice are handled by devd. So if the system
> detects the presence of a ums device, devd "remote-controls"
> moused to activate this mouse.
>
> # The entry below starts moused when a mouse is plugged in. Moused
> # stops automatically (actually it bombs :) when the device disappears.
> attach 100 {
> device-name "ums[0-9]+";
> action "/etc/rc.d/moused start $device-name";
> };
>
> This is from /etc/devd.conf.
>
>
Thanks for the pointer. It got me curious about what parsed
this file and I'm scanning devd.cc. ...
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
The 7.90a release of Jottings: http://jottings.thought.org/index.php
http://journey.thought.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, 13 Oct 2010 10:29:31 -0700, Gary Kline wrote:
> I just noticed that in rc.conf is:
>
>
> # -- sysinstall generated deltas -- # Wed Oct 13 08:03:06 2010
> moused_port="/dev/ums0"
> moused_type="auto"
> moused_enable="NO"
>
> and yet the console mouse is present. Strange... .
Explaination: USB mice are handled by devd. So if the system
detects the presence of a ums device, devd "remote-controls"
moused to activate this mouse.
# The entry below starts moused when a mouse is plugged in. Moused
# stops automatically (actually it bombs :) when the device disappears.
attach 100 {
device-name "ums[0-9]+";
action "/etc/rc.d/moused start $device-name";
};
This is from /etc/devd.conf.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, 13 Oct 2010 09:03:21 -0600 (MDT), Warren Block wrote: > I've followed only parts of this thread, and there are multiple > problems. First is installing X on a server. And first + one half is running X as root. :-) As it is only for testing, no big deal, but I did want to just mention it. > Second is a KVM switch, > many of which are problematic. That's true. The key problem is the switching from / to a particular machine, and how it handles this process. On the early models where wires were switched "purely electrically", this caused the system to lose a device. Some more modern KVM switches seem to provide a "dummy" signal so the device isn't lost (as in the view of the system), but I doubt this is a standard method. > Next is that the KVM converts USB to > PS/2, which... well, maybe it's fine. Erm, no. As far as I understood now, the KVM switch is USB only, or to be more precise: At least the mouse is USB - no PS/2 handling in between. > Finally, a "jumpy mouse" problem > with moused on console screams that it's the KVM, not moused or USB or > xorg config. I'm not 100% sure about that. Your article located at http://www.wonkity.com/~wblock/docs/html/aei.html states: Other times, particularly if hald is running, typed characters don't show up on the screen until the mouse is moved, and mouse movement itself is jerky and doesn't react smoothly. I thought about something like that. > My suggestion would be to *not* install X on a server. And this would eliminate the problem, as the keyboard (the main input method for console-driven dialog) seems to work as inteded through the KVM switch. > If it's really > required, use an actual keyboard and monitor on that server for those > times when ssh -X/-Y aren't enough, and avoid the KVM. Often the best solution, at least im ny experience. I have used KVM switches in the past, but found them often problematic (as shown in this thread), so my first choice is networked access, and if neccessary, "hardware access". In some cases, a serial line with a terminal (or an old laptop resembling a terminal, using DOS and the KERMIT terminal emulator) is fully sufficient, and VERY well supported by FreeBSD. > USB mice cause moused to be run anyway, but there are differences. If > you want switching between X and console to be fast, enable moused. And this is possible in combination with devd that "remote-contols" moused for USB mice? And does moused handle "disappearing" and "reappearing" devices properly? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, Oct 13, 2010 at 09:03:21AM -0600, Warren Block wrote: > On Wed, 13 Oct 2010, Polytropon wrote: > > >Correct. If you disable HAL, and your X is configured to run *WITH* > >HAL, it won't run anymore. Edit /etc/X11/xorg.conf (and if not > >present, create it) to make X work *WITHOUT* HAL. > > > >How it is to be done is described here: > > > >http://www.wonkity.com/~wblock/docs/html/aei.html > > I've followed only parts of this thread, and there are multiple > problems. First is installing X on a server. Second is a KVM > switch, many of which are problematic. Next is that the KVM > converts USB to PS/2, which... well, maybe it's fine. Finally, a > "jumpy mouse" problem with moused on console screams that it's the > KVM, not moused or USB or xorg config. Interesting that the mouse jumpiness has disappeared. I can switch to <-> computers by KVM and no problem. I'm about to add: Option "AutoAddDevices" "Off" to my xorg.conf Done. I just noticed that in rc.conf is: # -- sysinstall generated deltas -- # Wed Oct 13 08:03:06 2010 moused_port="/dev/ums0" moused_type="auto" moused_enable="NO" and yet the console mouse is present. Strange... . > > My suggestion would be to *not* install X on a server. If it's > really required, use an actual keyboard and monitor on that server > for those times when ssh -X/-Y aren't enough, and avoid the KVM. > > >If you use a USB mouse, set moused_enable="NO", as the USB subsystem > >will call moused with the correct settings automatically. > > USB mice cause moused to be run anyway, but there are differences. > If you want switching between X and console to be fast, enable > moused. I vastly prefer X11 because it allows xterms and more. X is necessary on my server because of my UPS as well as because it will be my new printserver. okay, time for the big reboot... . > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, 13 Oct 2010, Polytropon wrote: Correct. If you disable HAL, and your X is configured to run *WITH* HAL, it won't run anymore. Edit /etc/X11/xorg.conf (and if not present, create it) to make X work *WITHOUT* HAL. How it is to be done is described here: http://www.wonkity.com/~wblock/docs/html/aei.html I've followed only parts of this thread, and there are multiple problems. First is installing X on a server. Second is a KVM switch, many of which are problematic. Next is that the KVM converts USB to PS/2, which... well, maybe it's fine. Finally, a "jumpy mouse" problem with moused on console screams that it's the KVM, not moused or USB or xorg config. My suggestion would be to *not* install X on a server. If it's really required, use an actual keyboard and monitor on that server for those times when ssh -X/-Y aren't enough, and avoid the KVM. If you use a USB mouse, set moused_enable="NO", as the USB subsystem will call moused with the correct settings automatically. USB mice cause moused to be run anyway, but there are differences. If you want switching between X and console to be fast, enable moused. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Wed, Oct 13, 2010 at 05:59:06AM +0200, Polytropon wrote: > On Tue, 12 Oct 2010 20:20:18 -0700, Gary Kline wrote: > > Will you please check out this posting: > > > > http://osdir.com/ml/freebsd.bugs/2002-03/msg00032.html > > > > The way that the mose config worked as to turn off the > > moused_enable, to moused_enable="NO". Didn't seem to do > > anything... > > Yes, sounds familiar... > > It is to be interpreted as follows: > > If you use a USB mouse, set moused_enable="NO", as the USB subsystem > will call moused with the correct settings automatically. Correction -- it's devd(8) which auto-launches moused, not the USB subsystem. See /etc/devd.conf and look for the 'ums[0-9]+' entries. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Tue, 12 Oct 2010 20:20:18 -0700, Gary Kline wrote: > I just looked at the handbook "2.10.10 Mouse Settings" I am > running 7.2 on the server, not that old, but the text does not > match what I see on my sysinstall screen. > > // cut and paste > > > This option will allow you to cut and paste text in the console and > user programs with a 3-button mouse. If using a 2-button mouse, > refer to manual page, moused(8), after installation for details on > emulating the 3-button style. This example depicts a non-USB mouse > configuration (such as a PS/2 or COM port mouse): > > User Confirmation Requested > Does this system have a PS/2, serial, or bus mouse? > > [ Yes ]No > > Select [ Yes ] for a PS/2, serial or bus mouse, or [ No ] for a USB > mouse and press Enter. > > Figure 2-42. Select Mouse Protocol Type > > [[ GRAPHIC ]] > > I mouse down to the Post-install section of the sysinstall menu. > I do not see anything like the > > "User Confirmation Requested, [[etc]]" > > that lets me select Yes or No. *This may be what has been > causing the trouble. What I _do_ see is just the graph that > begins, "You can cut and paste text... ." etc. Nowhere do I > see an option to select the USB protocol; it is only the PS/2 > stuff. . USB mice get autodetected and autoactivated (by the USB subsystem), so there is no need to configure them. Currently I have no such setting in /etc/rc.conf, and mouse works. I think you should look at "Configuring X" rather than the system's mouse setting, as X seems to work independently. There's a section about that in the handbook. http://www.freebsd.org/doc/handbook/x-config.html > > > The kernel is set for PS/2 mice and evidently sticks them on > > > /dev/sysmouse. > > > > Yes - if one is present. At least X can be set to use sysmouse as > > pointer device, but it is not a symlink to either a USB or PS/2 > > mouse. Currently, I'm using a Sun USB mouse, and there is > > > > crw--- 1 root wheel 0, 10 Oct 13 01:31 /dev/sysmouse > > > > as well as > > > > crw-r--r-- 1 root operator0, 122 Oct 13 01:31 /dev/ums0 > > > > If this does survive a KVM switch-over, all is fine. > > > Yup:: > > p0 19:51 Server [5002] ll sysmouse > 0 crw--- 1 root wheel0, 11 Oct 12 17:12 sysmouse > > and, > > 0 crw-r--r-- 1 root operator0, 44 Oct 12 17:12 ums0 > > > So, both devices are there. Just that when I set the mouse to > the latter, /dev/ums0, the kernel sees it always as busy. A > poster to our -stable lists thought it might be hald bug, so I > commented out that in /etc/rc.conf. BZZZT. It's back:) Correct. If you disable HAL, and your X is configured to run *WITH* HAL, it won't run anymore. Edit /etc/X11/xorg.conf (and if not present, create it) to make X work *WITHOUT* HAL. How it is to be done is described here: http://www.wonkity.com/~wblock/docs/html/aei.html You can only have ONE of the following settings, as far as I understood the current state of X: a) X with HAL and DBUS, no xorg.conf b) X with HAL and DBUS, with xorg.conf c) X without HAL and DBUS, with xorg.conf So your way would be now to (1st) disable HAL and DBUS from the system and then (2nd) configure X not to require them. Another (maybe 3rd) option is to recompile X without HAL and DBUS require- ments. > Will you please check out this posting: > > http://osdir.com/ml/freebsd.bugs/2002-03/msg00032.html > > The way that the mose config worked as to turn off the > moused_enable, to moused_enable="NO". Didn't seem to do > anything... Yes, sounds familiar... It is to be interpreted as follows: If you use a USB mouse, set moused_enable="NO", as the USB subsystem will call moused with the correct settings automatically. If you use a PS/2 or serial mouse, set moused_enable="YES" and also set the needed options like _port and _type, and maybe _flags, so moused can take care of the mouse. The USB system is not involved here. I really think you should concentrate on configuring X's mouse handling, as the system's seems to work in a correct manner. Suggested TODO: 1. Disable HAL and DBUS per rc.conf 2. Create xorg.conf # X -configure # cp /root/xorg.conf.new /etc/X11/xorg.conf 3. Enter AutoAddDevices setting to xorg.conf as described http://www.wonkity.com/~wblock/docs/html/aei.html 4. ??? 5. Profit! :-) Oh, and don't forget to reboot. Medieval times... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubsc
Re: mouse problems....
New issues below... On Wed, Oct 13, 2010 at 01:43:26AM +0200, Polytropon wrote: > On Tue, 12 Oct 2010 16:30:02 -0700, Gary Kline wrote: > > The guy who set up my KVM/mouse deal thinks I would be better > > off just having a service do my hosting; I am close to agreeing. > > It it possible that you recently had mail problems? When fetchmail'ing > today's bunch of messages, I got the error message that thought.org > did not resolve... but seems to work again now. > Right. For some reason my server has seemed to die without notice. I'm pretty sure it is operator error, :-) ... things seem stable for the past few hours. --One thing is that I have been rebooting or deliberately crashing/rebooting when there was no other way. Be nice if ctl-alt-delete still worked > > > > Clearly, the Beklin model I have only supports USB keybd+mouse. > > They sell another that does USB and PS/2, but I didn't think of > > that gotcha. > > The problem might be related to USB handling on FreeBSD, I think. > >From your reports I see that there are no keyboard problems when > switching from / to the FreeBSD box, but the mouse doesn't fully > work. Did you get X working in the meantime? Switching around by the buttons [say from my new desktop to the server] is not a problem. The mouse only works in certain rare cases. Sometimes the mouse shakes violently and jumps around. I tried the "poll" string, but it died after a few moments, so I sh moused stop. And the server was okay. I have gotten # startx to present the trio of twm screens. Usually the keyboard is dead and the mouse cursor is frozen. The times I _have_ gotten the mouse to act smoothly [in console mode], when I do a `startx', someimes I can type into the center xterm [twm], but there is no mouse cursor. I just looked at the handbook "2.10.10 Mouse Settings" I am running 7.2 on the server, not that old, but the text does not match what I see on my sysinstall screen. // cut and paste This option will allow you to cut and paste text in the console and user programs with a 3-button mouse. If using a 2-button mouse, refer to manual page, moused(8), after installation for details on emulating the 3-button style. This example depicts a non-USB mouse configuration (such as a PS/2 or COM port mouse): User Confirmation Requested Does this system have a PS/2, serial, or bus mouse? [ Yes ]No Select [ Yes ] for a PS/2, serial or bus mouse, or [ No ] for a USB mouse and press Enter. Figure 2-42. Select Mouse Protocol Type [[ GRAPHIC ]] I mouse down to the Post-install section of the sysinstall menu. I do not see anything like the "User Confirmation Requested, [[etc]]" that lets me select Yes or No. *This may be what has been causing the trouble. What I _do_ see is just the graph that begins, "You can cut and paste text... ." etc. Nowhere do I see an option to select the USB protocol; it is only the PS/2 stuff. . > > > > > The kernel is set for PS/2 mice and evidently sticks them on > > /dev/sysmouse. > > Yes - if one is present. At least X can be set to use sysmouse as > pointer device, but it is not a symlink to either a USB or PS/2 > mouse. Currently, I'm using a Sun USB mouse, and there is > > crw--- 1 root wheel 0, 10 Oct 13 01:31 /dev/sysmouse > > as well as > > crw-r--r-- 1 root operator0, 122 Oct 13 01:31 /dev/ums0 > > If this does survive a KVM switch-over, all is fine. Yup:: p0 19:51 Server [5002] ll sysmouse 0 crw--- 1 root wheel0, 11 Oct 12 17:12 sysmouse and, 0 crw-r--r-- 1 root operator0, 44 Oct 12 17:12 ums0 So, both devices are there. Just that when I set the mouse to the latter, /dev/ums0, the kernel sees it always as busy. A poster to our -stable lists thought it might be hald bug, so I commented out that in /etc/rc.conf. BZZZT. It's back:) > > > > > Thru the sysinstall script, I see a mouse active > > in not-X11 but in console-mode. And the /device for that tweak > > is missing from the /dev table. > > I read that as follows: The sysinstall program initializes a mouse > and provides a cursor in text mode, means: mouse DOES WORK in text > mode, but not in X. > > This is part 1 of the solution. You can now check what happens when > you switch off / to the FreeBSD box - to see if the mouse does still > work in text mode. > > Part 2 would be to review X settings. > > > > > I *can* get some mouse pointer working in one of at least two > > ways. AS plain /dev/sysinstall, the mouse pointer jumps all > > over the screen unt
Re: mouse problems....
On Tue, 12 Oct 2010 16:30:02 -0700, Gary Kline wrote: > The guy who set up my KVM/mouse deal thinks I would be better > off just having a service do my hosting; I am close to agreeing. It it possible that you recently had mail problems? When fetchmail'ing today's bunch of messages, I got the error message that thought.org did not resolve... but seems to work again now. > Clearly, the Beklin model I have only supports USB keybd+mouse. > They sell another that does USB and PS/2, but I didn't think of > that gotcha. The problem might be related to USB handling on FreeBSD, I think. >From your reports I see that there are no keyboard problems when switching from / to the FreeBSD box, but the mouse doesn't fully work. Did you get X working in the meantime? > The kernel is set for PS/2 mice and evidently sticks them on > /dev/sysmouse. Yes - if one is present. At least X can be set to use sysmouse as pointer device, but it is not a symlink to either a USB or PS/2 mouse. Currently, I'm using a Sun USB mouse, and there is crw--- 1 root wheel 0, 10 Oct 13 01:31 /dev/sysmouse as well as crw-r--r-- 1 root operator0, 122 Oct 13 01:31 /dev/ums0 If this does survive a KVM switch-over, all is fine. > Thru the sysinstall script, I see a mouse active > in not-X11 but in console-mode. And the /device for that tweak > is missing from the /dev table. I read that as follows: The sysinstall program initializes a mouse and provides a cursor in text mode, means: mouse DOES WORK in text mode, but not in X. This is part 1 of the solution. You can now check what happens when you switch off / to the FreeBSD box - to see if the mouse does still work in text mode. Part 2 would be to review X settings. > I *can* get some mouse pointer working in one of at least two > ways. AS plain /dev/sysinstall, the mouse pointer jumps all > over the screen untill I sh-exec /etc/rc.d/mouse with the "poll" > arg. Having a pointer in console mode tells me that at least > FreeBSD does know the mouse is there, but I am out of ideas. I think it is X (again, ah...) having problems here. > Nutshell:: whatever, nothing mouse works in X11. That was the > whole point of this exercise. Then you might be able to solve the problem when you check the configuration file for X (or its absence, but then, the presence of HAL and DBUS services). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Tue, Oct 12, 2010 at 10:10:20PM +0200, Polytropon wrote: > On Tue, 12 Oct 2010 08:43:43 +0100, Arthur Chance wrote: > > On 10/11/10 18:31, Polytropon wrote: > > [snip] > > > The psm device can be configured per /etc/rc.conf using moused. > > > While USB mice get configured by the USB subsystem automatically, > > > PS/2 and serial mice do not. > > > > > > Here's an example entry: > > > > > > moused_enable="YES" > > > moused_port="/dev/psm0" > > > moused_flags="-z 4" > > > moused_type="auto" > > > > I'm not sure that bit about PS/2 mice not being configured automatically > > is true. > > PS/2 mice usually GET configured automatically, so type=auto is > sufficient in MOST cases. In my case (where I took those lines > from) I had to specify additional flags to make sure some specific > functionality of THAT mouse runs properly. > > > > > I run 8.1-RELEASE-p1 on amd64 with a PS/2 mouse and my > > /etc/rc.conf contains > > > > moused_enable="NO" > > moused_nondefault_enable="NO" > > moused_type="NO" > > > > and X has no problem seeing the mouse. OK, I don't have a mouse in > > console mode, but that's a personal foible of mine. > > As I mentioned in another message, X should pick up the mouse > INDEPENDENTLY from the system (moused), and if my memory serves > me, this works both in combination with HAL + DBUS, but should > work also without them. > > The idea of trying to get a mouse pointer in console mode is a > means of diagnostics, where "choose lowest level to check" is > often the best idea. The fewer components are involved, and > the better you can CONTROL those components, the easier it is > to check if something works. > The guy who set up my KVM/mouse deal thinks I would be better off just having a service do my hosting; I am close to agreeing. Clearly, the Beklin model I have only supports USB keybd+mouse. They sell another that does USB and PS/2, but I didn't think of that gotcha. The kernel is set for PS/2 mice and evidently sticks them on /dev/sysmouse. Thru the sysinstall script, I see a mouse active in not-X11 but in console-mode. And the /device for that tweak is missing from the /dev table. I *can* get some mouse pointer working in one of at least two ways. AS plain /dev/sysinstall, the mouse pointer jumps all over the screen untill I sh-exec /etc/rc.d/mouse with the "poll" arg. Having a pointer in console mode tells me that at least FreeBSD does know the mouse is there, but I am out of ideas. Nutshell:: whatever, nothing mouse works in X11. That was the whole point of this exercise. > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Tue, 12 Oct 2010 08:48:07 -0700, Gary Kline wrote: > I didn't realize how nice a GUI can be until I discovered the > xterm! At any rate, my mouse+keyboard are both USB. Still not > working with X Then you should check the typical (oh god!) HAL + DBUS trouble. If mouse and keyboard work properly in text mode console, it looks like an X configuration issue. I think this of documentation will be very helpful (at least it was for me - for the attempt of decoupling X from HAL + DBUS, as I do not have any use for them): http://www.freebsd.org/doc/handbook/x-config.html http://www.wonkity.com/~wblock/docs/html/aei.html http://www.kite.ping.de/xorg-hal-migration.html -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Tue, 12 Oct 2010 08:43:43 +0100, Arthur Chance wrote: > On 10/11/10 18:31, Polytropon wrote: > [snip] > > The psm device can be configured per /etc/rc.conf using moused. > > While USB mice get configured by the USB subsystem automatically, > > PS/2 and serial mice do not. > > > > Here's an example entry: > > > > moused_enable="YES" > > moused_port="/dev/psm0" > > moused_flags="-z 4" > > moused_type="auto" > > I'm not sure that bit about PS/2 mice not being configured automatically > is true. PS/2 mice usually GET configured automatically, so type=auto is sufficient in MOST cases. In my case (where I took those lines from) I had to specify additional flags to make sure some specific functionality of THAT mouse runs properly. > I run 8.1-RELEASE-p1 on amd64 with a PS/2 mouse and my > /etc/rc.conf contains > > moused_enable="NO" > moused_nondefault_enable="NO" > moused_type="NO" > > and X has no problem seeing the mouse. OK, I don't have a mouse in > console mode, but that's a personal foible of mine. As I mentioned in another message, X should pick up the mouse INDEPENDENTLY from the system (moused), and if my memory serves me, this works both in combination with HAL + DBUS, but should work also without them. The idea of trying to get a mouse pointer in console mode is a means of diagnostics, where "choose lowest level to check" is often the best idea. The fewer components are involved, and the better you can CONTROL those components, the easier it is to check if something works. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Tue, Oct 12, 2010 at 08:43:43AM +0100, Arthur Chance wrote: > On 10/11/10 18:31, Polytropon wrote: > [snip] > >The psm device can be configured per /etc/rc.conf using moused. > >While USB mice get configured by the USB subsystem automatically, > >PS/2 and serial mice do not. > > > >Here's an example entry: > > > > moused_enable="YES" > > moused_port="/dev/psm0" > > moused_flags="-z 4" > > moused_type="auto" > > I'm not sure that bit about PS/2 mice not being configured > automatically is true. I run 8.1-RELEASE-p1 on amd64 with a PS/2 > mouse and my /etc/rc.conf contains > > moused_enable="NO" > moused_nondefault_enable="NO" > moused_type="NO" > > and X has no problem seeing the mouse. OK, I don't have a mouse in > console mode, but that's a personal foible of mine. (Well, ASR33s > didn't have mice did they? :-) I didn't realize how nice a GUI can be until I discovered the xterm! At any rate, my mouse+keyboard are both USB. Still not working with X > > -- > "Although the wombat is real and the dragon is not, few know what a > wombat looks like, but everyone knows what a dragon looks like." > > -- Avram Davidson, _Adventures in Unhistory_ > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On 10/11/10 18:31, Polytropon wrote: [snip] The psm device can be configured per /etc/rc.conf using moused. While USB mice get configured by the USB subsystem automatically, PS/2 and serial mice do not. Here's an example entry: moused_enable="YES" moused_port="/dev/psm0" moused_flags="-z 4" moused_type="auto" I'm not sure that bit about PS/2 mice not being configured automatically is true. I run 8.1-RELEASE-p1 on amd64 with a PS/2 mouse and my /etc/rc.conf contains moused_enable="NO" moused_nondefault_enable="NO" moused_type="NO" and X has no problem seeing the mouse. OK, I don't have a mouse in console mode, but that's a personal foible of mine. (Well, ASR33s didn't have mice did they? :-) -- "Although the wombat is real and the dragon is not, few know what a wombat looks like, but everyone knows what a dragon looks like." -- Avram Davidson, _Adventures in Unhistory_ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, Oct 11, 2010 at 11:13:20PM +0200, Polytropon wrote: > On Mon, 11 Oct 2010 13:56:10 -0700, Gary Kline wrote: > > i tried this remove on _this_ console; then buttoned over to > > `ethic' [server], killed the moused that was running. Indeed it > > was /dev/ums0! But the mouse was frozen, and afer I killed it, > > gone. > > It seems that disconnect / reconnect (performed by the KVM switch) > causes some problems. > > > > > Then I tried your line and got the data stream. But > > there was no mouse. ... > > But if you moved the mouse, status messages appeared? Remove the > -d option and try > > # moused -f -p /dev/ums0 -t auto > > Now a mouse cursor should be present in text mode. > > > > > There are two buttons and the mouse "wheel"; I have no clue what's > > next. > > I'm using such mice (with wheel) since FreeBSD 5.0, so there should > be sufficient support if the mouse it not "broken by design". > > > > > Clearly, my 7.2.X sees the mouse. But when I typed simply > > > > # startx > > > > the windows are there; the mouse cursor hangs, dead-center. > > If you've tried the moused example above - and it WORKS, remove > the -f option. > > # moused -p /dev/ums0 -t auto > > It should then become a daemon. Right after that, run > > # startx > > and X should use the mouse access provided by moused - unless, of > course, there's HAL and DBUS trouble ahead. > > > > > Dunno; I do have hal and dbus there; that's about all I > > can say. Do I check with ps -ax | egrep "hal|dbus"? > > If it was THAT obvious... :-) > > Check > > # grep "hal" /etc/rc.conf > # grep "dbus" /etc/rc.conf > > to see if they are enabled. You should also have hal-x.y.z and > dbus-x.y.z packages installed. If you installed X from package or used > the port with default options, it relies on their presence. That's > nothing bad per se, especially if you're using KDE, Gnome or Xfce, > those seem to run better with HAL and DBUS, especially all the > autodetection and automount stuff. If you intendedly do NOT want > to use that, you can code AAD in your xorg.conf (you need to have > one for that). > > There's a section in the handbook covering that topic: > > 5.4 X11 Configuration > http://www.freebsd.org/doc/handbook/x-config.html > > Especially see 5.4.2. Also don't miss > > http://www.wonkity.com/~wblock/docs/html/aei.html > > And maybe > > http://www.kite.ping.de/xorg-hal-migration.html > > This should give sufficient information to find out what is the best > solution for your setting. > I thank you sincerely. I will try one last thing before I abandon my post: namely, to try a hard reset of the KVM switch. If nothing, then it is over my head. I'll vheck the site mentioned, who knows? gary PS: to the list: if this has happened to anyone else onlist, i would like to hear about it. I bought a Belkin circa '05 and it worked flalessly gor years ... until something burned out! > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, 11 Oct 2010 13:56:10 -0700, Gary Kline wrote: > i tried this remove on _this_ console; then buttoned over to > `ethic' [server], killed the moused that was running. Indeed it > was /dev/ums0! But the mouse was frozen, and afer I killed it, > gone. It seems that disconnect / reconnect (performed by the KVM switch) causes some problems. > Then I tried your line and got the data stream. But > there was no mouse. ... But if you moved the mouse, status messages appeared? Remove the -d option and try # moused -f -p /dev/ums0 -t auto Now a mouse cursor should be present in text mode. > There are two buttons and the mouse "wheel"; I have no clue what's > next. I'm using such mice (with wheel) since FreeBSD 5.0, so there should be sufficient support if the mouse it not "broken by design". > Clearly, my 7.2.X sees the mouse. But when I typed simply > > # startx > > the windows are there; the mouse cursor hangs, dead-center. If you've tried the moused example above - and it WORKS, remove the -f option. # moused -p /dev/ums0 -t auto It should then become a daemon. Right after that, run # startx and X should use the mouse access provided by moused - unless, of course, there's HAL and DBUS trouble ahead. > Dunno; I do have hal and dbus there; that's about all I > can say. Do I check with ps -ax | egrep "hal|dbus"? If it was THAT obvious... :-) Check # grep "hal" /etc/rc.conf # grep "dbus" /etc/rc.conf to see if they are enabled. You should also have hal-x.y.z and dbus-x.y.z packages installed. If you installed X from package or used the port with default options, it relies on their presence. That's nothing bad per se, especially if you're using KDE, Gnome or Xfce, those seem to run better with HAL and DBUS, especially all the autodetection and automount stuff. If you intendedly do NOT want to use that, you can code AAD in your xorg.conf (you need to have one for that). There's a section in the handbook covering that topic: 5.4 X11 Configuration http://www.freebsd.org/doc/handbook/x-config.html Especially see 5.4.2. Also don't miss http://www.wonkity.com/~wblock/docs/html/aei.html And maybe http://www.kite.ping.de/xorg-hal-migration.html This should give sufficient information to find out what is the best solution for your setting. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, Oct 11, 2010 at 10:16:09PM +0200, Polytropon wrote: > On Mon, 11 Oct 2010 12:49:07 -0700, Gary Kline wrote: > > I got a reply from grepping ums and a truckload from usbdev -s. > > Copied to my `posit' notes or whatever: > > > > > > ethic# dmesg | grep ums > > ums0: on uhub4 > > ums0: 5 buttons and Z dir. > > ethic# > > The mouse is detected. Good. > > A problem that now comes to my mind is that switching from / to > the "ethic" machine might confuse the USB subsystem, as a device > disappears and later appears. Although USB is capable of hot plug, > the USB subsystem might not be able to pick up the mouse correctly. > > You could try: > > # moused -d -f -p /dev/ums0 -t auto > > Then debugging messages should appear on the console, and a moving > mouse cursor should be visible. > i tried this remove on _this_ console; then buttoned over to `ethic' [server], killed the moused that was running. Indeed it was /dev/ums0! But the mouse was frozen, and afer I killed it, gone. Then I tried your line and got the data stream. But there was no mouse. ... > > > > I was able to balanced anf get forward enough to see what my > > friend did. The keyboard *is* a PS/2; it is plugged into a new > > adaptor that plugs into the USM slot. The (`Logitech') mouse is > > already a USB and plugs nto the second USB slot/jack on the KVM. > > So it's a "pure USB" solution for the mouse - should be no problem. > > > > > As noted, things are happy on my linux desktop, but not on my > > FBSD boxen. Any ideas how to rebuild things to the new USB > > protocol? > > Which "new" protocol? USB 3.0 for the three buttons? :-) There are two buttons and the mouse "wheel"; I have no clue what's next. Clearly, my 7.2.X sees the mouse. But when I typed simply # startx the windows are there; the mouse cursor hangs, dead-center. > > No, honestly: I think the problem is somewhere in the interaction > of the KVM switch and the FreeBSD USB subsystem which has influence > on how moused handles the mouse. > > Can you check "forcing the mouse on" as described above? If it is > present in dmesg (from boot time on, and NOT switched away and on > again), and also listed in the current state per usbdevs command, > it should be picked up. > > As far as I understood in regards of X, there is > > a) X using the mouse provided through moused, or > > b) X detecting it "itself" by HAL and DBUS. > > Do you use HAL and DBUS with X? > Dunno; I do have hal and dbus there; that's about all I can say. Do I check with ps -ax | egrep "hal|dbus"? gary > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, 11 Oct 2010 12:49:07 -0700, Gary Kline wrote: > I got a reply from grepping ums and a truckload from usbdev -s. > Copied to my `posit' notes or whatever: > > > ethic# dmesg | grep ums > ums0: on uhub4 > ums0: 5 buttons and Z dir. > ethic# The mouse is detected. Good. A problem that now comes to my mind is that switching from / to the "ethic" machine might confuse the USB subsystem, as a device disappears and later appears. Although USB is capable of hot plug, the USB subsystem might not be able to pick up the mouse correctly. You could try: # moused -d -f -p /dev/ums0 -t auto Then debugging messages should appear on the console, and a moving mouse cursor should be visible. > I was able to balanced anf get forward enough to see what my > friend did. The keyboard *is* a PS/2; it is plugged into a new > adaptor that plugs into the USM slot. The (`Logitech') mouse is > already a USB and plugs nto the second USB slot/jack on the KVM. So it's a "pure USB" solution for the mouse - should be no problem. > As noted, things are happy on my linux desktop, but not on my > FBSD boxen. Any ideas how to rebuild things to the new USB > protocol? Which "new" protocol? USB 3.0 for the three buttons? :-) No, honestly: I think the problem is somewhere in the interaction of the KVM switch and the FreeBSD USB subsystem which has influence on how moused handles the mouse. Can you check "forcing the mouse on" as described above? If it is present in dmesg (from boot time on, and NOT switched away and on again), and also listed in the current state per usbdevs command, it should be picked up. As far as I understood in regards of X, there is a) X using the mouse provided through moused, or b) X detecting it "itself" by HAL and DBUS. Do you use HAL and DBUS with X? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, Oct 11, 2010 at 09:32:16PM +0200, Polytropon wrote: > On Mon, 11 Oct 2010 12:14:43 -0700, Gary Kline wrote: > > This mouse is A USB type. > > Okay, in THAT case, the system should recognize a USB mouse, > as /dev/ums. Check > > # dmesg | grep ums > > if a mouse is present. Then > > # usbdevs -v > > should also report it. > > Additionally, there's no need to employ moused for a USB mouse > as this kind is automatically set up by the USB subsystem (which > uses moused for that purpose, I think). > > > > > The KVM only has two USM slots, > > nothing for a PS/2 type anything... I think. Wait. the keyboard > > is old enough to be PS/2. Trouble is that I can't see back > > behind the KVM box. > > Just for understanding: You are connecting a USB mouse and a PS/2 > keyboard to the KVM switch. The switch then connects to various > systems, by a PS/2 plug (keyboard connector) and a USB plug (mouse > connector). Additionally, a cable for the monitor is used. Is that > correct? > > Essentially; but using PS/2 -> USB adaptors ... . I got a reply from grepping ums and a truckload from usbdev -s. Copied to my `posit' notes or whatever: ethic# dmesg | grep ums ums0: on uhub4 ums0: 5 buttons and Z dir. ethic# > I was able to balanced anf get forward enough to see what my friend did. The keyboard *is* a PS/2; it is plugged into a new adaptor that plugs into the USM slot. The (`Logitech') mouse is already a USB and plugs nto the second USB slot/jack on the KVM. As noted, things are happy on my linux desktop, but not on my FBSD boxen. Any ideas how to rebuild things to the new USB protocol? gary > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, 11 Oct 2010 12:14:43 -0700, Gary Kline wrote: > This mouse is A USB type. Okay, in THAT case, the system should recognize a USB mouse, as /dev/ums. Check # dmesg | grep ums if a mouse is present. Then # usbdevs -v should also report it. Additionally, there's no need to employ moused for a USB mouse as this kind is automatically set up by the USB subsystem (which uses moused for that purpose, I think). > The KVM only has two USM slots, > nothing for a PS/2 type anything... I think. Wait. the keyboard > is old enough to be PS/2. Trouble is that I can't see back > behind the KVM box. Just for understanding: You are connecting a USB mouse and a PS/2 keyboard to the KVM switch. The switch then connects to various systems, by a PS/2 plug (keyboard connector) and a USB plug (mouse connector). Additionally, a cable for the monitor is used. Is that correct? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, Oct 11, 2010 at 08:27:41PM +0200, Polytropon wrote: > On Mon, 11 Oct 2010 11:14:38 -0700, Gary Kline wrote: > > Bah, or Bah-humbug! I tried the quick-fix mod and get the > > following: > > > > > > moused_type="auto" > > moused: optind: 9, optarg: '4' > > moused: unable to open /dev/psm0: No such file or directory > > ethic# > > This was to be expected. Check > > # dmesg | grep psm > > If no PS/2 mouse shows up, moused has nothing to connect to. Maybe > resetting (power-cycling) the KVM switch helps? > > > > > Then i dropped in your four line into /etc/rc.conf and rebooted. > > A few lines before the prompt was the message that "/dev/psm0" > > was not file nor directory. > > Same thing - no device there. > > > > > Suggestions? The kernel on this '09 Dell is from last December. > > I'll rebuild. > > I've been using PS/2 mice with 4.0 GENERIC kernel, so there will > surely be no "bleeding edge" technology needed. :-) > > The psm driver has been part of the GENERIC kernel for years, and > I doubt is has been removed lately... > > > > > I finished upgrading kernel and world on my 2003 Dell. Will > > drop in your 4 lines and see what happened after reboot. > > Also check dmesg. The psm device MUST be found. It should "come through" > the same controller mechanism as the keyboard (atkbdc), so if the > keyboard works, the mouse should, too. > > Oh, just a suggestion: if you can directly connect a mouse, check > if it works. Do NOT connect anything from or to a PS/2 connector > while the system is powered on! PS/2 is NOT hot-pluggable! > This mouse is A USB type. The KVM only has two USM slots, nothing for a PS/2 type anything... I think. Wait. the keyboard is old enough to be PS/2. Trouble is that I can't see back behind the KVM box. The 'user manual' has few diagrams. gary > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, 11 Oct 2010 11:14:38 -0700, Gary Kline wrote: > Bah, or Bah-humbug! I tried the quick-fix mod and get the > following: > > > moused_type="auto" > moused: optind: 9, optarg: '4' > moused: unable to open /dev/psm0: No such file or directory > ethic# This was to be expected. Check # dmesg | grep psm If no PS/2 mouse shows up, moused has nothing to connect to. Maybe resetting (power-cycling) the KVM switch helps? > Then i dropped in your four line into /etc/rc.conf and rebooted. > A few lines before the prompt was the message that "/dev/psm0" > was not file nor directory. Same thing - no device there. > Suggestions? The kernel on this '09 Dell is from last December. > I'll rebuild. I've been using PS/2 mice with 4.0 GENERIC kernel, so there will surely be no "bleeding edge" technology needed. :-) The psm driver has been part of the GENERIC kernel for years, and I doubt is has been removed lately... > I finished upgrading kernel and world on my 2003 Dell. Will > drop in your 4 lines and see what happened after reboot. Also check dmesg. The psm device MUST be found. It should "come through" the same controller mechanism as the keyboard (atkbdc), so if the keyboard works, the mouse should, too. Oh, just a suggestion: if you can directly connect a mouse, check if it works. Do NOT connect anything from or to a PS/2 connector while the system is powered on! PS/2 is NOT hot-pluggable! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, Oct 11, 2010 at 07:31:53PM +0200, Polytropon wrote: > On Mon, 11 Oct 2010 09:41:52 -0700, Gary Kline wrote: > > I'm including the dmesg output from the server. Is there a > > mouse driver I can compile that will get the mouse working on my > > two FreeBSD platforms? > > This is not needed - the mouse driver is already in the default > kernel. For a PS/2 mouse, dmesg should show a "psm" entry, and > there should be /dev/psm0. > > I think I don't see a mouse in this dmesg, so there is NO mouse. > The keyboard seems to be present. > > The psm device can be configured per /etc/rc.conf using moused. > While USB mice get configured by the USB subsystem automatically, > PS/2 and serial mice do not. > > Here's an example entry: > > moused_enable="YES" > moused_port="/dev/psm0" > moused_flags="-z 4" > moused_type="auto" > > If you're using X, it should pick up a mouse configured this > way. There should be no need to edit xorg.conf (unless you intendedly > need nonstandard settings that the autodetection magic won't get > right). > > You can check if the mouse works if you move the cursor in text > mode. An arrow should be visible. If you just want to check things > without file modifying (and rebooting), you can invoke moused > directly, e. g. > > moused -d -f -p /dev/psm0 -t auto -z 4 > > Here, -d enables debugging messages, and -f forces moused NOT to > become a daemon, so you can ^C to purge it when done. If you see that > the settings are working properly, modify the rc.conf file as shown > above. > > > > Compiling kernel & world to get a mouse working, bah... :-) > Bah, or Bah-humbug! I tried the quick-fix mod and get the following: moused_type="auto" moused: optind: 9, optarg: '4' moused: unable to open /dev/psm0: No such file or directory ethic# Then i dropped in your four line into /etc/rc.conf and rebooted. A few lines before the prompt was the message that "/dev/psm0" was not file nor directory. Suggestions? The kernel on this '09 Dell is from last December. I'll rebuild. I finished upgrading kernel and world on my 2003 Dell. Will drop in your 4 lines and see what happened after reboot. [??] gary > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.90a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mouse problems....
On Mon, 11 Oct 2010 09:41:52 -0700, Gary Kline wrote: > I'm including the dmesg output from the server. Is there a > mouse driver I can compile that will get the mouse working on my > two FreeBSD platforms? This is not needed - the mouse driver is already in the default kernel. For a PS/2 mouse, dmesg should show a "psm" entry, and there should be /dev/psm0. I think I don't see a mouse in this dmesg, so there is NO mouse. The keyboard seems to be present. The psm device can be configured per /etc/rc.conf using moused. While USB mice get configured by the USB subsystem automatically, PS/2 and serial mice do not. Here's an example entry: moused_enable="YES" moused_port="/dev/psm0" moused_flags="-z 4" moused_type="auto" If you're using X, it should pick up a mouse configured this way. There should be no need to edit xorg.conf (unless you intendedly need nonstandard settings that the autodetection magic won't get right). You can check if the mouse works if you move the cursor in text mode. An arrow should be visible. If you just want to check things without file modifying (and rebooting), you can invoke moused directly, e. g. moused -d -f -p /dev/psm0 -t auto -z 4 Here, -d enables debugging messages, and -f forces moused NOT to become a daemon, so you can ^C to purge it when done. If you see that the settings are working properly, modify the rc.conf file as shown above. Compiling kernel & world to get a mouse working, bah... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: mouse problems....
> Date: Mon, 11 Oct 2010 09:41:52 -0700 > From: kl...@thought.org > To: freebsd-questions@freebsd.org > Subject: Re: mouse problems > > On Sun, Oct 10, 2010 at 08:26:45PM -0700, Gary Kline wrote: > > I'm lost. Aday ago when I rebooted my old Dell, the mouse wouldn't > > work. A hour ago I got X booting on my server, but the same thing: > > no mouse. I see the cursor, but it is frozen. The only place my > > mouse works is on my linux system. The KVM connections seem soild; > > the only problem is the mouse.The brand is "Logitech" but it is > > a PS/2 mouse. > > > > > > I have tried the sysinstall utility; nothing. Would completely > > rebuilding the kernels and worlds do any good? Any other ideas? > > > > > Here is more from dmesg on my server. startx brings up three > twm xterms and a tiny xclock in the upper right corner, but the > mouse cursor is frozen. The KVM unit is a Belkin SOHO, if that > means anything. The KVM box is balanced on the edge of a small > platic table; my 20" widescreen display is jury-rigged behind > and balanced on surplus plastic. I can't do much of anything > because I can't tell where the mouse is plugged i to the KVM > unit. > > I'm including the dmesg output from the server. Is there a > mouse driver I can compile that will get the mouse working on my > two FreeBSD platforms? [Right now, things only work on my > Ubuntu desktop. ... ] > > thanks for any help. > > gary > > Enc: dmesg fron ethic > > > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.2-RELEASE-p4 #2: Sat Nov 21 05:52:04 PST 2009 > r...@ethic.thought.org:/usr/obj/usr/src/sys/ETHIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2793.01-MHz 686-class > CPU) > Origin = "GenuineIntel" Id = 0x1067a Stepping = 10 > > Features=0xbfebfbff > > Features2=0x408e39d > AMD Features=0x2010 > AMD Features2=0x1 > Cores per package: 2 > real memory = 3478716416 (3317 MB) > avail memory = 3399180288 (3241 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 4 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a (3) failed > acpi0: reservation of 10, cf49 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 > device_attach: acpi_hpet0 attach returned 12 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xff00-0xff07 mem > 0xfdf0-0xfdf7,0xd000-0xdfff,0xfdb0-0xfdbf irq 16 at > device 2.0 on pci0 > agp0: on vgapci0 > agp0: detected 7164k stolen memory > agp0: aperture size is 256M > em0: port 0xfe00-0xfe1f mem > 0xfdfc-0xfdfd,0xfdfff000-0xfdff irq 20 at device 25.0 on pci0 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: 00:24:e8:17:88:61 > uhci0: port 0xfd00-0xfd1f irq 16 at device > 26.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xfc00-0xfc1f irq 21 at device > 26.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xfb00-0xfb1f irq 19 at device > 26.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xfdffe000-0xfdffe3ff irq 18 > at device 26.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > uhub4: on uhub3 > uhub4: s
Re: mouse problems....
On Sun, Oct 10, 2010 at 08:26:45PM -0700, Gary Kline wrote: > I'm lost. Aday ago when I rebooted my old Dell, the mouse wouldn't > work. A hour ago I got X booting on my server, but the same thing: > no mouse. I see the cursor, but it is frozen. The only place my > mouse works is on my linux system. The KVM connections seem soild; > the only problem is the mouse.The brand is "Logitech" but it is > a PS/2 mouse. > > > I have tried the sysinstall utility; nothing. Would completely > rebuilding the kernels and worlds do any good? Any other ideas? > Here is more from dmesg on my server. startx brings up three twm xterms and a tiny xclock in the upper right corner, but the mouse cursor is frozen. The KVM unit is a Belkin SOHO, if that means anything. The KVM box is balanced on the edge of a small platic table; my 20" widescreen display is jury-rigged behind and balanced on surplus plastic. I can't do much of anything because I can't tell where the mouse is plugged i to the KVM unit. I'm including the dmesg output from the server. Is there a mouse driver I can compile that will get the mouse working on my two FreeBSD platforms? [Right now, things only work on my Ubuntu desktop. ... ] thanks for any help. gary Enc: dmesg fron ethic Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-RELEASE-p4 #2: Sat Nov 21 05:52:04 PST 2009 r...@ethic.thought.org:/usr/obj/usr/src/sys/ETHIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2793.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x1067a Stepping = 10 Features=0xbfebfbff Features2=0x408e39d AMD Features=0x2010 AMD Features2=0x1 Cores per package: 2 real memory = 3478716416 (3317 MB) avail memory = 3399180288 (3241 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, cf49 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xff00-0xff07 mem 0xfdf0-0xfdf7,0xd000-0xdfff,0xfdb0-0xfdbf irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7164k stolen memory agp0: aperture size is 256M em0: port 0xfe00-0xfe1f mem 0xfdfc-0xfdfd,0xfdfff000-0xfdff irq 20 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:24:e8:17:88:61 uhci0: port 0xfd00-0xfd1f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xfc00-0xfc1f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xfb00-0xfb1f irq 19 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfdffe000-0xfdffe3ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered uhub4: on uhub3 uhub4: single transaction translator uhub4: 4 ports with 4 removable, self powered ukbd0: on uhub4 kbd2 at ukbd0 uhid0: on uhub4 pci0: at device 27.0 (no driver attached) uhci3: port 0xfa00-0xfa1f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub5: on usb4 uhub5: 2 ports with 2 removable, self powered uhci4: port 0xf900-0xf91f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub6: on usb5 uhub6: 2 ports with 2 removable, self powered uhci5: port 0xf800-0xf81f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub7: on usb6 uhub7: 2 ports with 2 removable, self powered ehci1: mem 0xfdffd000-0xfdffd3ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [I
RE: mouse problems
> -Original Message- > From: cris rizzo [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 19, 2004 9:59 AM > To: [EMAIL PROTECTED] > Subject: mouse problems > > > I would like to know if there is another way to configure my > mouse. I have a Belkin mini optical USB and a three button > Belkin PS/2. Whenever I configure them by selecting TYPE, > PORT and then ENABLE, they both seem to work fine during the > test. However, when I start the "X" window desktop (KDE), I > barely touch the mouse and the cursor jumps to the top right > corner of the desktop and gets stuck there. I have even tried > to use a serial adapter and tried to configure it that way, > still, I had no luck. Any help you can provide will be appreciated! Have you tried sysmouse for the device? dave > > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems
Thomas, [ PS/2 mouse woes ] which mouse device are you using? Section "InputDevice" in /etc/X11/XF86Config should look like this (at least it works for me...) Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol""SysMouse" Option "Device" "/dev/sysmouse" For your reference: My /etc/rc.conf entry looks like this: moused_enable="YES" moused_flags="" moused_port="/dev/psm0" moused_type="auto" If that doesn't help, please provide more information, i.e. post the mentioned config files, along with the output of `dmesg'. > I really like BSD so far and am very impressed with it. I'm working > on contributing and am already trying to convince all my friends. Excellent! :-) HTH, Simon pgpXV8DAxBlvg.pgp Description: PGP signature
Re: Mouse problems with KVM switch
Hi, Joe Kraft wrote: For what it's worth, I have a cheap 4 port KVM which works fine (scroll wheel and all) with Win2k, FBSD 4.10, FBSD5.2 etc. As long as I use a PS2 mouse, if I use a converter on either end it none of the machines recognize the mouse in varying degrees of failure. Okey, so I should try and test with a real PS/2 mouse. Well it could solve the problem. As I said erlier my brand is a LevelOne, and on the homepage it says that it support FreeBSD. The mouse be the problem, I have to check it out. My KVM is marked "PS-104" on the front, but I can't see any visible brand names its buried so I can't dig it out. It supports hotkeys, and works fine with PS2 keyboards/mice. It fails if you attach a USB mouse with a USB/PS2 converter, or if you use a PS2/USB converter to attach it to a USB port on the PC. I have no clue, but perhaps the signals from a USB mouse/keyboard is not the same as from a PS/2 mouse. The might be some diffrences in any case. I've just resigned myself to use a PS2 mouse with my KVM, and hoping it doesn't break. Joe. As long as I can get a descent optical mouse with scroll wheel, I should manage it. :) Mattias Björk wrote: Hi, Jay O'Brien wrote: I had the same problems with a 4-port KVM. I am using a 2-port KVM successfully between an XP box and a FreeBSD 4.10 box. I've found that the scroll wheel doesn't work after switching back to Windows unless I also "reset" the KVM (Scroll Lock twice + End), but that's not a big deal. I have tryed to reset/rescan but it does not seem to help or even work. But I will try it out. It says for Auto Scan: "To start Auto Scan automatically scans all ports one by one at a fixed interval: "left Ctrl + left Ctrl + F1" But that does not help or even work, but perhaps im doing something wrong. Manual scan is the same but F2 instead of F1. Perhaps the problem is the mouse, Im using a "Logitech Click! optical mouse". I have also tried my trackball "Marbel Mouse" and both are USB with a PS/2 converter. Perhaps that is the problem, but then again I have tryed a none mouse as well. But still that did not solve the problem. Here's the 2-port KVM switch: http://airlinkplus.com/kvm/akvm2.htm It's available at Fry's: http://shop1.outpost.com/product/3891817 Jay O'Brien Rio Linda, CA USA I live in sweden so I have to find a shop here in sweden. But I will solve this problem some how. Thanks for the reply anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks for the help/answer Mvh Mattias Björk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks for the reply Mvh Mattias Björk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
Hi, Leonard Zettel wrote: On Thursday 19 August 2004 07:46 pm, Mattias Björk wrote: Hi, Leonard Zettel wrote: (snip) Duh. All this newbie can add is that of all the dropped balls and blind alleys I have experienced wrestling with FreeBSD, problems with my four port KVM switch have not been among them. Make of said switch is lost in the mists of time - it is whatever CompUSA sells. I have a Logitech track ball; It and the keyboard have functioned well through various permutations of 5.1, 5.2, and 4.10, native and under KDE. -LenZ- What you are saying In short is that you did not experince any problems? Correct. Very occasionally keyboard input would not show up on either the FreeBSD box or the Windows XP box, although the mouse still worked. Jiggling the cables cured that in all cases. Zero mouse problems. -LenZ- (snip) Hmm I don't think that this is a cable problem that Im having. Still I will not give it up just yet. As someone else sugested, I will try a real PS/2 mouse not a one with USB connector and PS/2 converter attched to it. Thanks for the answer Mvh Mattias Björk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
For what it's worth, I have a cheap 4 port KVM which works fine (scroll wheel and all) with Win2k, FBSD 4.10, FBSD5.2 etc. As long as I use a PS2 mouse, if I use a converter on either end it none of the machines recognize the mouse in varying degrees of failure. My KVM is marked "PS-104" on the front, but I can't see any visible brand names its buried so I can't dig it out. It supports hotkeys, and works fine with PS2 keyboards/mice. It fails if you attach a USB mouse with a USB/PS2 converter, or if you use a PS2/USB converter to attach it to a USB port on the PC. I've just resigned myself to use a PS2 mouse with my KVM, and hoping it doesn't break. Joe. Mattias Björk wrote: Hi, Jay O'Brien wrote: I had the same problems with a 4-port KVM. I am using a 2-port KVM successfully between an XP box and a FreeBSD 4.10 box. I've found that the scroll wheel doesn't work after switching back to Windows unless I also "reset" the KVM (Scroll Lock twice + End), but that's not a big deal. I have tryed to reset/rescan but it does not seem to help or even work. But I will try it out. It says for Auto Scan: "To start Auto Scan automatically scans all ports one by one at a fixed interval: "left Ctrl + left Ctrl + F1" But that does not help or even work, but perhaps im doing something wrong. Manual scan is the same but F2 instead of F1. Perhaps the problem is the mouse, Im using a "Logitech Click! optical mouse". I have also tried my trackball "Marbel Mouse" and both are USB with a PS/2 converter. Perhaps that is the problem, but then again I have tryed a none mouse as well. But still that did not solve the problem. Here's the 2-port KVM switch: http://airlinkplus.com/kvm/akvm2.htm It's available at Fry's: http://shop1.outpost.com/product/3891817 Jay O'Brien Rio Linda, CA USA I live in sweden so I have to find a shop here in sweden. But I will solve this problem some how. Thanks for the reply anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks for the help/answer Mvh Mattias Björk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
On Thursday 19 August 2004 07:46 pm, Mattias Björk wrote: > Hi, > > Leonard Zettel wrote: (snip) > > Duh. All this newbie can add is that of all the dropped balls > > and blind alleys I have experienced wrestling with FreeBSD, > > problems with my four port KVM switch have not been among > > them. Make of said switch is lost in the mists of time - it is > > whatever CompUSA sells. I have a Logitech track ball; > > It and the keyboard have functioned well through various > > permutations of 5.1, 5.2, and 4.10, native and under KDE. > > -LenZ- > > What you are saying In short is that you did not experince any problems? > Correct. Very occasionally keyboard input would not show up on either the FreeBSD box or the Windows XP box, although the mouse still worked. Jiggling the cables cured that in all cases. Zero mouse problems. -LenZ- (snip) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
Hi, [EMAIL PROTECTED] wrote: From: Mattias Björk <[EMAIL PROTECTED]> Hello, [EMAIL PROTECTED] wrote: From: thrawn <[EMAIL PROTECTED]> Date: Thursday, August 19, 2004 6:18 am Does anybody have a clue or have hade any similar problems and/or who could shine some light on this problem? Mvh Mattias Björk Does your KVM support hotkey? I have another KVM switch erlier that did work better but It didn't have support for hotkey. But It did not work perfectly but atleast the mouse worked mutch better if you compare to this. Yes, the hotkeys work as designed. Aha okey, sometimes they don't work for me. Strange. I came to the conclusion that the mouse will not work through the KVM switch using FBSD, or at> > Aloha Mattias Actually, I tried two with the same problem you are alluding to. least I never got it to. I had bought one on the mainland last month. When I couldn't get the mouse to work, I bought another here on the Big Island. I acted the same so I returned it and am using the original. Okey, no help in chaning the mice for you either. Or perhaps the KVM that I have been using are Crap or something in that direction. Me Too!! I have connected a mouse directly to each computer. Forgot to mention that both rodents are usb. What do you mean with rodents, you mean the mice right? Have to luck up the word to understand. :) Then again its kind of dumb to have a KVM if you still have to use the mouse directly connected to the computer. At least I don't have to have 2 monitors and 2 keyboards on the desk. Well it would be near impossible for me to have 4x keyboards,mice and 21" monitors. But then again I might get a switch just for keyboard and monitor, save space anyway. What is the brand and model of your KVM? "Made in China" I guess you don't know, mine is LevelOne. Perhaps I should buy something more expensive. I think that I would be worth it, the price with cables for me was about 106 $. Perhaps It could be some interfarence that causes this problem. Robert Once again thanks for the answer. Mvh Mattias Björk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
Foster, ThomasX wrote: You apparently did try the device hints.. but is your kernel compiled to use that hints file? Also.. if you cat the output of the mouse device.. what do you get? Thom You mean on the FreeBSD 5.2.1-p9 box? If so, check below: [snip] machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident THRAWN #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options SCHED_4BSD #4BSD scheduler options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. options PFIL_HOOKS # pfil(9) framework device isa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering device atapicam device scbus # Needed for CAM device device pass# Needed to connect scsi to cam device cd # SCSI cd connected through CAM # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm [snip] I don't know exactly if I have done it right but I should check "/boot/devices.hints" for input right? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mattias Björk Sent: Thursday, August 19, 2004 2:30 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Mouse problems with KVM switch Hello, [EMAIL PROTECTED] wrote: From: thrawn <[EMAIL PROTECTED]> Date: Thursday, August 19, 2004 6:18 am Hi, I have just brought this KVM switch: http://www.level1.com/products3.php?sklop=20&id=590430 But Im having major problems with getting the mouse to work under FreeBSD. Even the keyboard does not work sometimes. This KVM switch has support for hotkey and also supports emulation on both mouse and keyboard. When I boot up my system and see the BIOS on the computer the keyboard works just fine. Then when it continues to boot and comes to the loader, it still works. And the it starts to load the kernel. But then when i get to the login prompt the keyboard does not work. And sometimes even thought I stay with the computer the hole boot process I can't even use the keyboard. So I have to use ssh to login to the computer and make it reboot to regain the keyboard. I have also tried to change the cables but I get the same results. And It works with no problems under Windows XP Pro. The system that im using is FreeBSD 5.2.1-p9, at least on this system. I have also two other computers that Im running FreeBSD-stable on. On one of my FreeBSD-stable machines I have hade a working mouse under X Windows System (Xorg latest from ports). But then I rebooted the system and when I started xdm, it found the mouse but when I move it around It didn't move like it should. It took some seconds before it moved and it did not move like it should, jumps several ramdom cm/inches on the screen (Perhaps in the direction that I move the mouse im not sure). Its on usab
Re: Mouse problems with KVM switch
From: Mattias Björk <[EMAIL PROTECTED]> > Hello, > > [EMAIL PROTECTED] wrote: > > From: thrawn <[EMAIL PROTECTED]> > > Date: Thursday, August 19, 2004 6:18 am > >> > >>Does anybody have a clue or have hade any similar problems and/or > >>who > >>could shine some light on this problem? > >> > >>Mvh Mattias Björk > > > > > > > > Does your KVM support hotkey? I have another KVM switch erlier that > did > work better but It didn't have support for hotkey. But It did not > work > perfectly but atleast the mouse worked mutch better if you compare > to this. Yes, the hotkeys work as designed. > > > I came to the conclusion that the mouse will not work > > through the KVM switch using FBSD, or at> > Aloha Mattias > > >> Actually, I tried two with the same > > problem you are alluding to. least I never > > got it to. I had bought one on the mainland last month. When I couldn't get the mouse to work, I bought another here on the Big Island. I acted the same so I returned it and am using the original. >> Or perhaps the KVM that I have been using are Crap or something in that direction. Me Too!! > > > > I have connected a mouse directly to each computer. Forgot to mention that both rodents are usb. >Then again its kind of dumb to have a KVM if you >still have to use the mouse directly connected > to the computer. At least I don't have to have 2 monitors and 2 keyboards on the desk. > What is the brand and model of your KVM? "Made in China" Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
Hi, Jay O'Brien wrote: I had the same problems with a 4-port KVM. I am using a 2-port KVM successfully between an XP box and a FreeBSD 4.10 box. I've found that the scroll wheel doesn't work after switching back to Windows unless I also "reset" the KVM (Scroll Lock twice + End), but that's not a big deal. I have tryed to reset/rescan but it does not seem to help or even work. But I will try it out. It says for Auto Scan: "To start Auto Scan automatically scans all ports one by one at a fixed interval: "left Ctrl + left Ctrl + F1" But that does not help or even work, but perhaps im doing something wrong. Manual scan is the same but F2 instead of F1. Perhaps the problem is the mouse, Im using a "Logitech Click! optical mouse". I have also tried my trackball "Marbel Mouse" and both are USB with a PS/2 converter. Perhaps that is the problem, but then again I have tryed a none mouse as well. But still that did not solve the problem. Here's the 2-port KVM switch: http://airlinkplus.com/kvm/akvm2.htm It's available at Fry's: http://shop1.outpost.com/product/3891817 Jay O'Brien Rio Linda, CA USA I live in sweden so I have to find a shop here in sweden. But I will solve this problem some how. Thanks for the reply anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks for the help/answer Mvh Mattias Björk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
Hi, Leonard Zettel wrote: On Thursday 19 August 2004 04:55 pm, [EMAIL PROTECTED] wrote: From: thrawn <[EMAIL PROTECTED]> Date: Thursday, August 19, 2004 6:18 am Hi, I have just brought this KVM switch: http://www.level1.com/products3.php?sklop=20&id=590430 But Im having major problems with getting the mouse to work under FreeBSD. Even the keyboard does not work sometimes. This KVM switch has support for hotkey and also supports emulation on both mouse and keyboard. When I boot up my system and see the BIOS on the computer the keyboard works just fine. Then when it continues to boot and comes to the loader, it still works. And the it starts to load the kernel. But then when i get to the login prompt the keyboard does not work. And sometimes even thought I stay with the computer the hole boot process I can't even use the keyboard. So I have to use ssh to login to the computer and make it reboot to regain the keyboard. I have also tried to change the cables but I get the same results. And It works with no problems under Windows XP Pro. The system that im using is FreeBSD 5.2.1-p9, at least on this system. I have also two other computers that Im running FreeBSD-stable on. On one of my FreeBSD-stable machines I have hade a working mouse under X Windows System (Xorg latest from ports). But then I rebooted the system and when I started xdm, it found the mouse but when I move it around It didn't move like it should. It took some seconds before it moved and it did not move like it should, jumps several ramdom cm/inches on the screen (Perhaps in the direction that I move the mouse im not sure). Its on usable in other words. I have also tryied to use moused under FreeBSD but I get the same fault/problem. I also have a problem if I do not have this machine selected when I boot. Then when I switch to it when the boot of the FreeBSD system has complete, The screen on the monitor just blinks. Still the keyboard works because I can press two times Left Ctrl and then 1 to 4 to change the computer Im controlling. This I can not do with the FreeBSD 5.2.1-p9 system I can only see the screen but have to change the computer im controlling by pressing the button on the switch box. I have tried to remove the cables and put them back again. But that does not help, the only solution I can see is to reboot the system and let it boot with it selected. I have also booted up with the mouse directly connected to the computer. Then when the system boot was completed I moved the mouse around to see that it did work. After that I plugged back the cable from the switch in to the computers mouse port. And the plugged the mouse back in the switch box, that did not work either. I have also added flags to both psm0 and atkbd in my kernel config: # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x0 device psm0at atkbdc? irq 12 flags 0x0 I have also tried with the flags set to 0x100 on both atkbd0 and psm0, but that doesn't seem to make any diffrance. I have done this on my FreeBSD 5.2.1-p9 box as well. I have also changed it in: /boot/device.hints But I don't get it working correctly either by that. Does anybody have a clue or have hade any similar problems and/or who could shine some light on this problem? Mvh Mattias Björk Aloha Mattias This all sounds familiar. I too had a lot of trouble with a KVM switch. Actually, I tried two with the same problem you are alluding to. I came to the conclusion that the mouse will not work through the KVM switch using FBSD, or at least I never got it to. Duh. All this newbie can add is that of all the dropped balls and blind alleys I have experienced wrestling with FreeBSD, problems with my four port KVM switch have not been among them. Make of said switch is lost in the mists of time - it is whatever CompUSA sells. I have a Logitech track ball; It and the keyboard have functioned well through various permutations of 5.1, 5.2, and 4.10, native and under KDE. -LenZ- What you are saying In short is that you did not experince any problems? I have two computers that are both running 5.2.1 I have connected a mouse directly to each computer. I still had to shutdown both computers and connect the cables for the monitor and keyboard from each to the KVM. I also connected and old mouse to the output of the KVM. With all this connected, I then powered up both computers. All seems to work fine with the inconvenience of having to use 2 meese. I seldom have to go into one fo the computers, so I can live with it. This is probably not the answer you were looking for but you were also looking for others who had problems. Best of Luck Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Thanks for the answer. Mvh Mattias Björk ___
Re: Mouse problems with KVM switch
I had the same problems with a 4-port KVM. I am using a 2-port KVM successfully between an XP box and a FreeBSD 4.10 box. I've found that the scroll wheel doesn't work after switching back to Windows unless I also "reset" the KVM (Scroll Lock twice + End), but that's not a big deal. Here's the 2-port KVM switch: http://airlinkplus.com/kvm/akvm2.htm It's available at Fry's: http://shop1.outpost.com/product/3891817 Jay O'Brien Rio Linda, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
On Thursday 19 August 2004 04:55 pm, [EMAIL PROTECTED] wrote: > From: thrawn <[EMAIL PROTECTED]> > Date: Thursday, August 19, 2004 6:18 am > > > Hi, > > > > I have just brought this KVM switch: > > http://www.level1.com/products3.php?sklop=20&id=590430 > > > > But Im having major problems with getting the mouse to work under > > FreeBSD. Even the keyboard does not work sometimes. This KVM switch > > has > > support for hotkey and also supports emulation on both mouse and > > keyboard. > > When I boot up my system and see the BIOS on the computer the > > keyboard > > works just fine. Then when it continues to boot and comes to the > > loader, > > it still works. And the it starts to load the kernel. But then when > > i > > get to the login prompt the keyboard does not work. > > > > And sometimes even thought I stay with the computer the hole boot > > process I can't even use the keyboard. So I have to use ssh to > > login to > > the computer and make it reboot to regain the keyboard. I have also > > tried to change the cables but I get the same results. And It works > > with > > no problems under Windows XP Pro. > > > > The system that im using is FreeBSD 5.2.1-p9, at least on this system. > > > > I have also two other computers that Im running FreeBSD-stable on. > > On > > one of my FreeBSD-stable machines I have hade a working mouse under > > X > > Windows System (Xorg latest from ports). > > > > But then I rebooted the system and when I started xdm, it found the > > mouse but when I move it around It didn't move like it should. It > > took > > some seconds before it moved and it did not move like it should, > > jumps > > several ramdom cm/inches on the screen (Perhaps in the direction > > that I > > move the mouse im not sure). Its on usable in other words. > > > > I have also tryied to use moused under FreeBSD but I get the same > > fault/problem. I also have a problem if I do not have this machine > > selected when I boot. Then when I switch to it when the boot of the > > FreeBSD system has complete, The screen on the monitor just blinks. > > > > Still the keyboard works because I can press two times Left Ctrl > > and > > then 1 to 4 to change the computer Im controlling. This I can not > > do > > with the FreeBSD 5.2.1-p9 system I can only see the screen but have > > to > > change the computer im controlling by pressing the button on the > > switch box. > > > > I have tried to remove the cables and put them back again. But that > > does > > not help, the only solution I can see is to reboot the system and > > let it > > boot with it selected. I have also booted up with the mouse > > directly > > connected to the computer. Then when the system boot was completed > > I > > moved the mouse around to see that it did work. After that I > > plugged > > back the cable from the switch in to the computers mouse port. And > > the > > plugged the mouse back in the switch box, that did not work either. > > > > I have also added flags to both psm0 and atkbd in my kernel config: > > > > # atkbdc0 controls both the keyboard and the PS/2 mouse > > device atkbdc0 at isa? port IO_KBD > > device atkbd0 at atkbdc? irq 1 flags 0x0 > > device psm0at atkbdc? irq 12 flags 0x0 > > > > I have also tried with the flags set to 0x100 on both atkbd0 and > > psm0, > > but that doesn't seem to make any diffrance. I have done this on my > > FreeBSD 5.2.1-p9 box as well. I have also changed it in: > > > > /boot/device.hints > > > > But I don't get it working correctly either by that. > > > > Does anybody have a clue or have hade any similar problems and/or > > who > > could shine some light on this problem? > > > > Mvh Mattias Björk > > Aloha Mattias > > This all sounds familiar. I too had a lot of trouble > with a KVM switch. Actually, I tried two with the same > problem you are alluding to. > > I came to the conclusion that the mouse will not work > through the KVM switch using FBSD, or at least I never > got it to. > Duh. All this newbie can add is that of all the dropped balls and blind alleys I have experienced wrestling with FreeBSD, problems with my four port KVM switch have not been among them. Make of said switch is lost in the mists of time - it is whatever CompUSA sells. I have a Logitech track ball; It and the keyboard have functioned well through various permutations of 5.1, 5.2, and 4.10, native and under KDE. -LenZ- > I have two computers that are both running 5.2.1 > > I have connected a mouse directly to each computer. > I still had to shutdown both computers and connect > the cables for the monitor and keyboard from each to > the KVM. I also connected and old mouse to the output > of the KVM. > > With all this connected, I then powered up both computers. All seems to > work fine with the inconvenience of having to use 2 meese. I seldom have to > go into one > fo the computers, so I can live with it. > > This is probably not the answer you were looking for > but you were also look
Re: Mouse problems with KVM switch
Hello, [EMAIL PROTECTED] wrote: From: thrawn <[EMAIL PROTECTED]> Date: Thursday, August 19, 2004 6:18 am Hi, I have just brought this KVM switch: http://www.level1.com/products3.php?sklop=20&id=590430 But Im having major problems with getting the mouse to work under FreeBSD. Even the keyboard does not work sometimes. This KVM switch has support for hotkey and also supports emulation on both mouse and keyboard. When I boot up my system and see the BIOS on the computer the keyboard works just fine. Then when it continues to boot and comes to the loader, it still works. And the it starts to load the kernel. But then when i get to the login prompt the keyboard does not work. And sometimes even thought I stay with the computer the hole boot process I can't even use the keyboard. So I have to use ssh to login to the computer and make it reboot to regain the keyboard. I have also tried to change the cables but I get the same results. And It works with no problems under Windows XP Pro. The system that im using is FreeBSD 5.2.1-p9, at least on this system. I have also two other computers that Im running FreeBSD-stable on. On one of my FreeBSD-stable machines I have hade a working mouse under X Windows System (Xorg latest from ports). But then I rebooted the system and when I started xdm, it found the mouse but when I move it around It didn't move like it should. It took some seconds before it moved and it did not move like it should, jumps several ramdom cm/inches on the screen (Perhaps in the direction that I move the mouse im not sure). Its on usable in other words. I have also tryied to use moused under FreeBSD but I get the same fault/problem. I also have a problem if I do not have this machine selected when I boot. Then when I switch to it when the boot of the FreeBSD system has complete, The screen on the monitor just blinks. Still the keyboard works because I can press two times Left Ctrl and then 1 to 4 to change the computer Im controlling. This I can not do with the FreeBSD 5.2.1-p9 system I can only see the screen but have to change the computer im controlling by pressing the button on the switch box. I have tried to remove the cables and put them back again. But that does not help, the only solution I can see is to reboot the system and let it boot with it selected. I have also booted up with the mouse directly connected to the computer. Then when the system boot was completed I moved the mouse around to see that it did work. After that I plugged back the cable from the switch in to the computers mouse port. And the plugged the mouse back in the switch box, that did not work either. I have also added flags to both psm0 and atkbd in my kernel config: # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x0 device psm0at atkbdc? irq 12 flags 0x0 I have also tried with the flags set to 0x100 on both atkbd0 and psm0, but that doesn't seem to make any diffrance. I have done this on my FreeBSD 5.2.1-p9 box as well. I have also changed it in: /boot/device.hints But I don't get it working correctly either by that. Does anybody have a clue or have hade any similar problems and/or who could shine some light on this problem? Mvh Mattias Björk Aloha Mattias This all sounds familiar. I too had a lot of trouble with a KVM switch. Actually, I tried two with the same problem you are alluding to. Does your KVM support hotkey? I have another KVM switch erlier that did work better but It didn't have support for hotkey. But It did not work perfectly but atleast the mouse worked mutch better if you compare to this. I came to the conclusion that the mouse will not work through the KVM switch using FBSD, or at least I never got it to. Im afraid that I can only agree. I have googled some also and there are quite a few posts that have the same topic. Some some years old. Not to blame FreeBSD but it seems that its a common problem. Or perhaps the KVM that I have been using are Crap or something in that direction. I have two computers that are both running 5.2.1 I have two with FreeBSD-Stable and one with 5.2.1-p9. I have connected a mouse directly to each computer. I still had to shutdown both computers and connect the cables for the monitor and keyboard from each to the KVM. I also connected and old mouse to the output of the KVM. I know that is a solution, don't need the mouse for the most of the time on the servers. But my Workstation Its requierd. Then again its kind of dumb to have a KVM if you still have to use the mouse directly connected to the computer. With all this connected, I then powered up both computers. All seems to work fine with the inconvenience of having to use 2 meese. I seldom have to go into one fo the computers, so I can live with it. As I still can return the KVM im thinking that I should do it. But not until I have got
Re: Mouse problems with KVM switch
From: thrawn <[EMAIL PROTECTED]> Date: Thursday, August 19, 2004 6:18 am > Hi, > > I have just brought this KVM switch: > http://www.level1.com/products3.php?sklop=20&id=590430 > > But Im having major problems with getting the mouse to work under > FreeBSD. Even the keyboard does not work sometimes. This KVM switch > has > support for hotkey and also supports emulation on both mouse and > keyboard. > When I boot up my system and see the BIOS on the computer the > keyboard > works just fine. Then when it continues to boot and comes to the > loader, > it still works. And the it starts to load the kernel. But then when > i > get to the login prompt the keyboard does not work. > > And sometimes even thought I stay with the computer the hole boot > process I can't even use the keyboard. So I have to use ssh to > login to > the computer and make it reboot to regain the keyboard. I have also > tried to change the cables but I get the same results. And It works > with > no problems under Windows XP Pro. > > The system that im using is FreeBSD 5.2.1-p9, at least on this system. > > I have also two other computers that Im running FreeBSD-stable on. > On > one of my FreeBSD-stable machines I have hade a working mouse under > X > Windows System (Xorg latest from ports). > > But then I rebooted the system and when I started xdm, it found the > mouse but when I move it around It didn't move like it should. It > took > some seconds before it moved and it did not move like it should, > jumps > several ramdom cm/inches on the screen (Perhaps in the direction > that I > move the mouse im not sure). Its on usable in other words. > > I have also tryied to use moused under FreeBSD but I get the same > fault/problem. I also have a problem if I do not have this machine > selected when I boot. Then when I switch to it when the boot of the > FreeBSD system has complete, The screen on the monitor just blinks. > > Still the keyboard works because I can press two times Left Ctrl > and > then 1 to 4 to change the computer Im controlling. This I can not > do > with the FreeBSD 5.2.1-p9 system I can only see the screen but have > to > change the computer im controlling by pressing the button on the > switch box. > > I have tried to remove the cables and put them back again. But that > does > not help, the only solution I can see is to reboot the system and > let it > boot with it selected. I have also booted up with the mouse > directly > connected to the computer. Then when the system boot was completed > I > moved the mouse around to see that it did work. After that I > plugged > back the cable from the switch in to the computers mouse port. And > the > plugged the mouse back in the switch box, that did not work either. > > I have also added flags to both psm0 and atkbd in my kernel config: > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 flags 0x0 > device psm0at atkbdc? irq 12 flags 0x0 > > I have also tried with the flags set to 0x100 on both atkbd0 and > psm0, > but that doesn't seem to make any diffrance. I have done this on my > FreeBSD 5.2.1-p9 box as well. I have also changed it in: > > /boot/device.hints > > But I don't get it working correctly either by that. > > Does anybody have a clue or have hade any similar problems and/or > who > could shine some light on this problem? > > Mvh Mattias Björk Aloha Mattias This all sounds familiar. I too had a lot of trouble with a KVM switch. Actually, I tried two with the same problem you are alluding to. I came to the conclusion that the mouse will not work through the KVM switch using FBSD, or at least I never got it to. I have two computers that are both running 5.2.1 I have connected a mouse directly to each computer. I still had to shutdown both computers and connect the cables for the monitor and keyboard from each to the KVM. I also connected and old mouse to the output of the KVM. With all this connected, I then powered up both computers. All seems to work fine with the inconvenience of having to use 2 meese. I seldom have to go into one fo the computers, so I can live with it. This is probably not the answer you were looking for but you were also looking for others who had problems. Best of Luck Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems in XFree86
>All, > >I've installed FreeBSD 4.7-Release, everything is fine. When >configuring the mouse deamon with /stand/sysinstall, the mouse works >correctly. Configuration of XFree86 server works fine aswell. > >When I load my KDE wm with startx (or with KDM), I have a problem with >my mouse. Whenever I move the mouse, it goes back to the upper left >corner of my screen - which makes the mouse useless and makes it also >impossible to run KDE. I've already tried with other window managers >(GNOME) but the same problem happens. > >Plain old serial mouse connected to com1. > >What do I need to do to solve this problem? > >Thanks in advance. > > >Alain > _ Try to set the "mouse type" option in your XF86Config file to "Auto". That should do the trick. -- Odd Rune Strømmen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems
On Friday 19 September 2003 21:10, Dave Wiebe wrote: > Hi, > > Thanks for reading my email. I recently installed Free BSD and when I run X > windows, whenever I move my mouse, the cursor moves to the top left of the > screen. I set it up as best as possible(making sure it is setup as a ps2 > mouse in the config file). I even tried a serial mouse but the same thing > happened(Yes I did change the config file to accomodate this). Other than > that, everything works fine. I'd say, enter auto for the protocol and /dev/sysmouse as the mouse device. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mouse problems
Roman Neuhauser writes: > > From: Petre Bandac <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: mouse problems > > Date: Tue, 9 Jul 2002 21:52:06 +0300 > > > > I have a problem with the mouse in x-window on my fresh-installed 4.6 release > > box. > > > > initially I have installed wmaker and all went okay, except for the mouse > > which started to click and move by itself ... just like a mouse with the > > wrong drivers on a winblows machine :-) > > > > so I switched to enlightenment - and same problem ... > > the mouse is ps2 > > and the error I get sometimes when I Ctr-Alt-Backspace to kill x-window is > > > > (EE)Mouse1: Write to mouse failed. > > > > and in the console the mouse works ok that's what I dont understand .. > > > ps - and yes, I did xf86config and set it all ok there > > I could never get mouse work under X with any protocol other than "auto" > > roman@freepuppy ~ > grep auto /etc/rc.conf /etc/X11/XF86Config292:0 > /etc/rc.conf:moused_type="auto" > /etc/X11/XF86Config:Option "Protocol""auto" > > I use a Genius Netscroll+ here (4.5-STABLE - 4.6-STABLE), and > another (old 3-button) Genius on another 4.5-RELEASE with these > settings. > Hi, I had similar problems . I disabled moused and set mouse device to ps2 in XF86Config Option "Device" "/dev/psm0" I dont use mouse on the console. lutz To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: mouse problems
> From: Petre Bandac <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: mouse problems > Date: Tue, 9 Jul 2002 21:52:06 +0300 > > I have a problem with the mouse in x-window on my fresh-installed 4.6 release > box. > > initially I have installed wmaker and all went okay, except for the mouse > which started to click and move by itself ... just like a mouse with the > wrong drivers on a winblows machine :-) > > so I switched to enlightenment - and same problem ... > the mouse is ps2 > and the error I get sometimes when I Ctr-Alt-Backspace to kill x-window is > > (EE)Mouse1: Write to mouse failed. > > and in the console the mouse works ok that's what I dont understand .. > ps - and yes, I did xf86config and set it all ok there I could never get mouse work under X with any protocol other than "auto" roman@freepuppy ~ > grep auto /etc/rc.conf /etc/X11/XF86Config292:0 /etc/rc.conf:moused_type="auto" /etc/X11/XF86Config:Option "Protocol""auto" I use a Genius Netscroll+ here (4.5-STABLE - 4.6-STABLE), and another (old 3-button) Genius on another 4.5-RELEASE with these settings. -- FreeBSD 4.6-STABLE 9:02PM up 12 days, 5:39, 23 users, load averages: 0.00, 0.00, 0.00 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
