Re: Performance and mouse problems
On Fri, 8 Jun 2012, Albert Shih wrote: After some time, and read new messages ont this mailing list, I find a solution. Deactivate hald deactivate dbus Option AutoAddDevices Off put moused_enable=On in /etc/rc.conf and reboot and everything work fine again. I don't known why by using /usr/local/etc/rc.d/hald stop /usr/local/etc/rc.d/dbus stop /etc/rc.d/moused start it's not working It should not be a dbus problem, and some things can benefit from dbus. Try it and see if the problem comes back. FWIW, I thought I suggested this a while back. It is what I run: hal not installed, but moused enabled. When hal is not installed, turning AutoAddDevices off should also not be needed. ___ 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: Performance and mouse problems
Le 29/04/2012 ? 00:58:01+0200, Jerome Herman a écrit I've got two very strange problem I'm running 9-stable on a Dell Laptop E4200. Since this morning when I put a USB mouse (I've try three mouses to be sure) it's not working. The kernel and HAL see the mouse but Xorg don't seem do anything. The second point is the load of the system is alway more than 1 (~1.5-2) event I do nothing. I kill all services, daemon, software and the load never drop. I've stop : hald dbus powerd etc... and ps don't show any process eating some ressource. But the load is high (and the laptop is very hot). I make a csup of world and build new userland, and news kernel. And nothing change http://www.wonkity.com/~wblock/docs/html/aei.html Well I don't see why this can be from a misconfiguration, the usb mouse work well before I update hald and world. But I read you link and I don't have those option in my configuration of xorg. Any other idea ? But thanks. For the problem about performance I submit this problem on stable mailing list. Regards JAS I was afraid this would happen. And I fear it is just the begining. I assume you did not create any custom hald rule. Did you ? The first thing to do is to add Option AutoAddDevices Off In your ServerLayout section of xorg.conf. Then restart X and try to plug a mouse again. It may result in your mouse not working in X, but at least it should stop your computer from using all it's CPU trying to map the mouse. If indeed the CPU load does not reach skyhigh levels when you plug a USB mouse, we will be able to conclude that there is a DBus/hald problem. After some time, and read new messages ont this mailing list, I find a solution. Deactivate hald deactivate dbus Option AutoAddDevices Off put moused_enable=On in /etc/rc.conf and reboot and everything work fine again. I don't known why by using /usr/local/etc/rc.d/hald stop /usr/local/etc/rc.d/dbus stop /etc/rc.d/moused start it's not working Thank all those help. Regards. -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@jabber.obspm.fr Heure local/Local time: ven 8 jui 2012 23:06:01 CEST ___ 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: Performance and mouse problems
Le 02/05/2012 ? 22:44:19+0200, Jerome Herman a écrit
Ok here is what happens,
In your system you have your touchpad declared both in a static way in
your xorg config, and probed by HAL.
What happens is that when xorg starts it first install the touchpad as
required by the config file, and then tries to install it again via
autodetection. Of course the second installation of the same device
doesn't work as the device is already busy with xorg, and xorg stops to
try to auto-install devices.
When you plug another mouse, xorg is notified that there are new
devices, but starts by trying to reinstall the touchpad, fails again for
the same reason as above and stops trying.
In order to solve your problem you can try the following :
a) remove the touchpad lines from your xorg config. This way the
touchpad should be installed by auto detection. (simply comment it as
you might be needing it back soon)
b) forbid hal from probing the touchpad. If solution a fails, I would
explain to you how to do this if solution a) fails.
I try this.
I do a hal-device find the unique udi to have /dev/psm0 in input.device,
udi = '/org/freedesktop/Hal/devices/psm_0'
freebsd.driver = 'psm' (string)
freebsd.unit = 0 (0x0) (int)
platform.id = 'psm.0' (string)
freebsd.device_file = '/dev/psm0' (string)
info.capabilities = { 'input', 'input.mouse' } (string list)
info.category = 'input' (string)
input.device = '/dev/psm0' (string)
input.x11_driver = 'mouse' (string)
info.addons = { 'hald-addon-mouse-sysmouse' } (string list)
info.udi = '/org/freedesktop/Hal/devices/psm_0' (string)
info.parent = '/org/freedesktop/Hal/devices/atkbdc_0' (string)
info.product = 'PS/2 Mouse' (string)
info.subsystem = 'platform' (string)
and add a new file in /usr/local/etc/hal/fdi/policy/ with
?xml version=1.0 encoding=UTF-8?
deviceinfo version=0.2
device
match key=info.product string=PS/2 Mouse
merge key=info.ignore type=booltrue/merge
/match
/device
/deviceinfo
restart hald, reboot and...nothing :-(
I've try also with something like
?xml version=1.0 encoding=UTF-8?
deviceinfo version=0.2
device
match key=freebsd.driver string=psm
match key=info.product string=PS/2 Mouse
merge key=info.ignore type=booltrue/merge
/match
/match
/device
/deviceinfo
but same result.
The touchpad still working and most important the mouse still NOT working.
Any help ?
Thanks.
Regards.
JAS
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
xmpp: j...@obspm.fr
Heure local/Local time:
ven 4 mai 2012 14:42:00 CEST
___
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: Performance and mouse problems
Le 02/05/2012 ? 22:44:19+0200, Jerome Herman a écrit Hi. Ok here is what happens, In your system you have your touchpad declared both in a static way in your xorg config, and probed by HAL. What happens is that when xorg starts it first install the touchpad as required by the config file, and then tries to install it again via autodetection. Of course the second installation of the same device doesn't work as the device is already busy with xorg, and xorg stops to try to auto-install devices. When you plug another mouse, xorg is notified that there are new devices, but starts by trying to reinstall the touchpad, fails again for the same reason as above and stops trying. OK. In order to solve your problem you can try the following : a) remove the touchpad lines from your xorg config. This way the touchpad should be installed by auto detection. (simply comment it as you might be needing it back soon) I've no idea how I can do that. Here my xorg.conf (without font/driver for graphics etc..): Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 # InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Module Load extmod Load record Load dbe Load glx Load dri Load dri2 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection I've try to comment out Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 without any result. b) forbid hal from probing the touchpad. If solution a fails, I would explain to you how to do this if solution a) fails. Any solution ;-) Thanks again. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: jeu 3 mai 2012 09:27:51 CEST ___ 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: Performance and mouse problems
Le 02/05/2012 ? 10:27:56-0600, Warren Block a écrit On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. Sorry. I forget to thanks you the first time you answer me. But just after you send the message, I already try that, without any result. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: jeu 3 mai 2012 09:32:16 CEST ___ 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: Performance and mouse problems
On Thu, 3 May 2012, Albert Shih wrote: Le 02/05/2012 ? 10:27:56-0600, Warren Block a écrit On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. Sorry. I forget to thanks you the first time you answer me. But just after you send the message, I already try that, without any result. Different hardware, possibly. For completeness, this machine has dbus running, hal is not installed, moused_enable=YES is in /etc/rc.conf, and it requires a restart. Probably the touchpad on this system is USB internally, and a normal moused can't be started after devd starts a nondefault moused. xorg.conf has no InputDevice entries at all. The scroll wheel and middle click buttons work.___ 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: Performance and mouse problems
Can you disable the touchpad? In my laptop (Asus K5) if i press Fn+F9 the touchpad is disabled via ACPI and not detected by HAL nor Xorg. ___ 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: Performance and mouse problems
Le 30/04/2012 ? 17:19:35+0200, Jerome Herman a écrit I was afraid this would happen. And I fear it is just the begining. Why you say that ? Short answer : I am a proud member of the HAL and DBus are evil group. Middle answer : HAL and DBus were made, maintained and tuned with pretty much nothing but Linux in mind. As a result they hardly play well with other OS, and will tend to play worse as the time goes by. In fact general opinion is that HAL never truly worked under Linux either, it is now officially deprecated. OK. I'm just a basic user. Event I use FreeBSD since 3.x I'm sysadmin so I use lot of FreeBSD for the server side. On my laptop I use...vim/X11/Firefox/ion3 and that is almost everything I knwon. I remenber when hal is release I lost lot of time to configure X11 to use my keyboard map (us_intl) and hate hal for that ;-) ugen5.2:vendor 0x413c at usbus5 ums1:vendor 0x413c Dell Premium USB Optical Mouse, class 0/0, rev 2.00/0.09, addr 2 on usbus5 ums1: 5 buttons and [XYZT] coordinates ID=0 Ok looking at your files, it does not appear to be a hal/dbus problem either : The device is correctly probed and registered with DBus, known as /dev/ums1, and the x11 driver is mapped to mouse which should be correct. For one reason or another, xorg is not catching/processing the info. Can you send the Xorg log ? Just wait until X is up and then plug the mouse. I am curious to see what happens inside xorg. I think the problem is indeed comme from Xorg. Before I plug (Notice my touchpad working) http://dl.free.fr/nkZEuk5nZ I plug the mouse http://dl.free.fr/vEn4bnirv Thanks. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: mer 2 mai 2012 17:01:21 CEST ___ 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: Performance and mouse problems
On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. ___ 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: Performance and mouse problems
On Wed, 2 May 2012, Warren Block wrote: On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. My experience corresponds with Warren's thoughts on this. I was running the exact levels of software on an old Dell 800Mhz desktop and new aDell laptop many many times faster, 4 cpu's etc, etc. HAL (which is well named I think) did not work very well on the laptop and I would lose the mouse and keyboard when I disabled the touchpad. On the Desktop HAL worked fine. The laptop (keyboard and mouse anyway) works fine without HAL. ___ 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: Performance and mouse problems
On Wed, 2 May 2012 13:19:05 -0400 (EDT) d...@safeport.com articulated: On Wed, 2 May 2012, Warren Block wrote: On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. My experience corresponds with Warren's thoughts on this. I was running the exact levels of software on an old Dell 800Mhz desktop and new aDell laptop many many times faster, 4 cpu's etc, etc. HAL (which is well named I think) did not work very well on the laptop and I would lose the mouse and keyboard when I disabled the touchpad. On the Desktop HAL worked fine. The laptop (keyboard and mouse anyway) works fine without HAL. HAL is now deprecated on GNU/Linux systems. Why it is still being kept on life support in FreeBSD is the question that needs to be addressed. This didn't just happen yesterday either. We continue to bump version numbers yet fail to repair/replace crucial elements of the operating system. What is even better, depending on whose forum you choose to read, the problem is FreeBSD -- Linux -- Gnome -- KDE -- The Cat in the Hat (no one has blamed Microsoft for this fiasco as far as I know) yet the problem still exists. Since 2008, when HAL was being deprecated, no one has properly addressed the problem. Everyone plays the blame game. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ signature.asc Description: PGP signature
Re: Performance and mouse problems
On 02/05/2012 19:40, Jerry wrote: On Wed, 2 May 2012 13:19:05 -0400 (EDT) d...@safeport.com articulated: On Wed, 2 May 2012, Warren Block wrote: On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. My experience corresponds with Warren's thoughts on this. I was running the exact levels of software on an old Dell 800Mhz desktop and new aDell laptop many many times faster, 4 cpu's etc, etc. HAL (which is well named I think) did not work very well on the laptop and I would lose the mouse and keyboard when I disabled the touchpad. On the Desktop HAL worked fine. The laptop (keyboard and mouse anyway) works fine without HAL. HAL is now deprecated on GNU/Linux systems. Why it is still being kept on life support in FreeBSD is the question that needs to be addressed. This didn't just happen yesterday either. We continue to bump version numbers yet fail to repair/replace crucial elements of the operating system. What is even better, depending on whose forum you choose to read, the problem is FreeBSD -- Linux -- Gnome -- KDE -- The Cat in the Hat (no one has blamed Microsoft for this fiasco as far as I know) yet the problem still exists. Since 2008, when HAL was being deprecated, no one has properly addressed the problem. Everyone plays the blame game. Be carefull that Linux notion of Deprecated is not exactly on par with standard meaning of the term. ifconfig has been deprecated since 1999 in Linux, OSS since 2001. Both are still alive and kicking. So it might be that Linux will keep HAL for a while still. ___ 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: Performance and mouse problems
On Wed, 2 May 2012, Jerome Herman wrote: On 02/05/2012 19:40, Jerry wrote: On Wed, 2 May 2012 13:19:05 -0400 (EDT) d...@safeport.com articulated: On Wed, 2 May 2012, Warren Block wrote: On Wed, 2 May 2012, Albert Shih wrote: I think the problem is indeed comme from Xorg. Just to repeat: on this Gateway notebook, only one or the other of the touchpad or mouse would work until I enabled moused in /etc/rc.conf. Now either or both work, including when the USB mouse is connected after X starts. My experience corresponds with Warren's thoughts on this. I was running the exact levels of software on an old Dell 800Mhz desktop and new aDell laptop many many times faster, 4 cpu's etc, etc. HAL (which is well named I think) did not work very well on the laptop and I would lose the mouse and keyboard when I disabled the touchpad. On the Desktop HAL worked fine. The laptop (keyboard and mouse anyway) works fine without HAL. HAL is now deprecated on GNU/Linux systems. Why it is still being kept on life support in FreeBSD is the question that needs to be addressed. This didn't just happen yesterday either. We continue to bump version numbers yet fail to repair/replace crucial elements of the operating system. What is even better, depending on whose forum you choose to read, the problem is FreeBSD -- Linux -- Gnome -- KDE -- The Cat in the Hat (no one has blamed Microsoft for this fiasco as far as I know) yet the problem still exists. Since 2008, when HAL was being deprecated, no one has properly addressed the problem. Everyone plays the blame game. Be carefull that Linux notion of Deprecated is not exactly on par with standard meaning of the term. ifconfig has been deprecated since 1999 in Linux, OSS since 2001. Both are still alive and kicking. So it might be that Linux will keep HAL for a while still. I guess my comments were not clear. If something does not work for a particular configuration, why use it? Given the 1000s of different BIOSs, PCs and the fact that everything is written to work with windows, to expect no issues is not realistic. My only point was/is if it does not work for your configuration, you are not likely (in my experience) to be able to get it working without a pretty good knowledge of fbsd, xorg and C. The handbook is very clear on how to configure without HAL, so that should be the first thing to try. ___ 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: Performance and mouse problems
On 02/05/2012 17:06, Albert Shih wrote: Le 30/04/2012 ? 17:19:35+0200, Jerome Herman a écrit I was afraid this would happen. And I fear it is just the begining. Why you say that ? Short answer : I am a proud member of the HAL and DBus are evil group. Middle answer : HAL and DBus were made, maintained and tuned with pretty much nothing but Linux in mind. As a result they hardly play well with other OS, and will tend to play worse as the time goes by. In fact general opinion is that HAL never truly worked under Linux either, it is now officially deprecated. OK. I'm just a basic user. Event I use FreeBSD since 3.x I'm sysadmin so I use lot of FreeBSD for the server side. On my laptop I use...vim/X11/Firefox/ion3 and that is almost everything I knwon. I remenber when hal is release I lost lot of time to configure X11 to use my keyboard map (us_intl) and hate hal for that ;-) ugen5.2:vendor 0x413c at usbus5 ums1:vendor 0x413c Dell Premium USB Optical Mouse, class 0/0, rev 2.00/0.09, addr 2 on usbus5 ums1: 5 buttons and [XYZT] coordinates ID=0 Ok looking at your files, it does not appear to be a hal/dbus problem either : The device is correctly probed and registered with DBus, known as /dev/ums1, and the x11 driver is mapped to mouse which should be correct. For one reason or another, xorg is not catching/processing the info. Can you send the Xorg log ? Just wait until X is up and then plug the mouse. I am curious to see what happens inside xorg. I think the problem is indeed comme from Xorg. Before I plug (Notice my touchpad working) http://dl.free.fr/nkZEuk5nZ I plug the mouse http://dl.free.fr/vEn4bnirv Thanks. Regards. JAS Ok here is what happens, In your system you have your touchpad declared both in a static way in your xorg config, and probed by HAL. What happens is that when xorg starts it first install the touchpad as required by the config file, and then tries to install it again via autodetection. Of course the second installation of the same device doesn't work as the device is already busy with xorg, and xorg stops to try to auto-install devices. When you plug another mouse, xorg is notified that there are new devices, but starts by trying to reinstall the touchpad, fails again for the same reason as above and stops trying. In order to solve your problem you can try the following : a) remove the touchpad lines from your xorg config. This way the touchpad should be installed by auto detection. (simply comment it as you might be needing it back soon) b) forbid hal from probing the touchpad. If solution a fails, I would explain to you how to do this if solution a) fails. Jerome Herman ___ 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: Performance and mouse problems
On Mon, Apr 30, 2012 at 05:19:35PM +0200, Jerome Herman wrote: Short answer : I am a proud member of the HAL and DBus are evil group. Middle answer : HAL and DBus were made, maintained and tuned with pretty much nothing but Linux in mind. As a result they hardly play well with other OS, and will tend to play worse as the time goes by. In fact general opinion is that HAL never truly worked under Linux either, it is now officially deprecated. I fully agree and propose a slightly longer answer « by example » because I just got rid of hald and dbus, and I am very happy with the following configurations for both my desktop and laptop machines. /boot/loader.conf on both: -- ums_load=YES -- rc.conf on desktop: # Note that moused_enable is set to NO # by /etc/default/rc.conf ! -- keymap=us.iso # Next line required after switching locale from iso-8859-15 to utf-8 scrnmap=us-ascii_to_cp437 # See rc.conf(5) and /etc/default/rc.conf # for default and non-default moused settings. # moused_ums0_flags=-a 0.3# decelerate Labtec mouse -- rc.conf on laptop: -- keymap=fr.iso.acc # Next line required after switching locale from iso-8859-15 to utf-8 scrnmap=us-ascii_to_cp437 # See rc.conf(5) and /etc/default/rc.conf # for default and non-default moused settings. # moused_enable=YES # touchpad on laptops moused_flags=-3 moused_ums0_flags=# non-default moused -- xorg.conf on both: -- Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard Option AutoAddDevices false EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection -- The following configures the keyboard map under X with the option for typing all sorts of non-ascii characters. .xinitrc on desktop: -- setxkbmap -model pc104 -layout us -option compose:ralt -- .xinitrc on laptop: -- setxkbmap -model pc102 -layout fr -option compose:menu -- That works on 8.2-RELEASE-p3. -- Harald Weis ___ 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: Performance and mouse problems
Le 29/04/2012 ? 00:58:01+0200, Jerome Herman a écrit I was afraid this would happen. And I fear it is just the begining. Why you say that ? I assume you did not create any custom hald rule. Did you ? I have one, but I try with him (I use since hal existe on BSD) and without him. For the same result. The pad in the laptop working but not the usb mouse. In fact I don't think the cpu load is connected to this problem. I already send a email to freebsd-stable. Well but that not a solve the Xorg don't see the mouse. The first thing to do is to add Option AutoAddDevices Off In your ServerLayout section of xorg.conf. Then restart X and try to plug a mouse again. It may result in your mouse not working in X, but at least it should stop your computer from using all it's CPU trying to map the mouse. If indeed the CPU load does not reach skyhigh levels when you plug a USB mouse, we will be able to conclude that there is a DBus/hald problem. Also could you do the following - Mouse unplugged : # /usr/local/etc/rc.d/hald stop # /usr/local/sbin/hald --daemon=no --verbose=yes /tmp/hald_debug.log 21 # dbus-launch lshal /tmp/dbus_hal_debug.log 21 - plug mouse # dbus-launch lshal /tmp/dbus_hal_debug.log 21 And post the content of both log files ? That should help in understanding what is going on. In the worst case there are mecanism that will keep HAL from tinkering/probing usb mouse. Here : the hald log file : http://dl.free.fr/rqLTgOvPS (I put some blank ligne juste before I plug the mouse) the dbus log file before I plug the mouse : http://dl.free.fr/iDgqyLgu6 and the dbus log file after I plug the mouse : http://dl.free.fr/lZuRadJFx I'm not qualified to said if it's hald/dbus problem, FreeBSD-Stable problem or both. I don't think it's a FreeBSD-Stable problem because in the dmesg we see the mouse plug ugen5.2: vendor 0x413c at usbus5 ums1: vendor 0x413c Dell Premium USB Optical Mouse, class 0/0, rev 2.00/0.09, addr 2 on usbus5 ums1: 5 buttons and [XYZT] coordinates ID=0 Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: lun 30 avr 2012 13:22:45 CEST ___ 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: Performance and mouse problems
On Mon, 30 Apr 2012, Albert Shih wrote: Le 29/04/2012 ? 00:58:01+0200, Jerome Herman a écrit I was afraid this would happen. And I fear it is just the begining. Why you say that ? I assume you did not create any custom hald rule. Did you ? I have one, but I try with him (I use since hal existe on BSD) and without him. For the same result. The pad in the laptop working but not the usb mouse. In fact I don't think the cpu load is connected to this problem. On one computer here, only one of the touchpad or external mouse works unless moused is enabled in rc.conf. That's without hal, but worth trying even with hal. Just 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: Performance and mouse problems
On 30/04/2012 13:39, Albert Shih wrote: Le 29/04/2012 ? 00:58:01+0200, Jerome Herman a écrit I was afraid this would happen. And I fear it is just the begining. Why you say that ? Short answer : I am a proud member of the HAL and DBus are evil group. Middle answer : HAL and DBus were made, maintained and tuned with pretty much nothing but Linux in mind. As a result they hardly play well with other OS, and will tend to play worse as the time goes by. In fact general opinion is that HAL never truly worked under Linux either, it is now officially deprecated. I assume you did not create any custom hald rule. Did you ? I have one, but I try with him (I use since hal existe on BSD) and without him. For the same result. The pad in the laptop working but not the usb mouse. In fact I don't think the cpu load is connected to this problem. I already send a email to freebsd-stable. Well but that not a solve the Xorg don't see the mouse. The first thing to do is to add Option AutoAddDevices Off In your ServerLayout section of xorg.conf. Then restart X and try to plug a mouse again. It may result in your mouse not working in X, but at least it should stop your computer from using all it's CPU trying to map the mouse. If indeed the CPU load does not reach skyhigh levels when you plug a USB mouse, we will be able to conclude that there is a DBus/hald problem. Also could you do the following - Mouse unplugged : # /usr/local/etc/rc.d/hald stop # /usr/local/sbin/hald --daemon=no --verbose=yes /tmp/hald_debug.log 21 # dbus-launch lshal /tmp/dbus_hal_debug.log 21 - plug mouse # dbus-launch lshal /tmp/dbus_hal_debug.log 21 And post the content of both log files ? That should help in understanding what is going on. In the worst case there are mecanism that will keep HAL from tinkering/probing usb mouse. Here : the hald log file : http://dl.free.fr/rqLTgOvPS (I put some blank ligne juste before I plug the mouse) the dbus log file before I plug the mouse : http://dl.free.fr/iDgqyLgu6 and the dbus log file after I plug the mouse : http://dl.free.fr/lZuRadJFx I'm not qualified to said if it's hald/dbus problem, FreeBSD-Stable problem or both. I don't think it's a FreeBSD-Stable problem because in the dmesg we see the mouse plug ugen5.2:vendor 0x413c at usbus5 ums1:vendor 0x413c Dell Premium USB Optical Mouse, class 0/0, rev 2.00/0.09, addr 2 on usbus5 ums1: 5 buttons and [XYZT] coordinates ID=0 Ok looking at your files, it does not appear to be a hal/dbus problem either : The device is correctly probed and registered with DBus, known as /dev/ums1, and the x11 driver is mapped to mouse which should be correct. For one reason or another, xorg is not catching/processing the info. Can you send the Xorg log ? Just wait until X is up and then plug the mouse. I am curious to see what happens inside xorg. Regards. Jerome Regards. JAS ___ 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: Performance and mouse problems
Le 27/04/2012 ? 12:14:04-0500, Adam Vande More a écrit On Fri, Apr 27, 2012 at 11:13 AM, Albert Shih albert.s...@obspm.fr wrote: Hi all I've got two very strange problem I'm running 9-stable on a Dell Laptop E4200. Since this morning when I put a USB mouse (I've try three mouses to be sure) it's not working. The kernel and HAL see the mouse but Xorg don't seem do anything. The second point is the load of the system is alway more than 1 (~1.5-2) event I do nothing. I kill all services, daemon, software and the load never drop. I've stop : hald dbus powerd etc... and ps don't show any process eating some ressource. But the load is high (and the laptop is very hot). I make a csup of world and build new userland, and news kernel. And nothing change http://www.wonkity.com/~wblock/docs/html/aei.html Well I don't see why this can be from a misconfiguration, the usb mouse work well before I update hald and world. But I read you link and I don't have those option in my configuration of xorg. Any other idea ? But thanks. For the problem about performance I submit this problem on stable mailing list. Regards JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: sam 28 avr 2012 22:49:23 CEST ___ 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: Performance and mouse problems
On 28/04/2012 22:52, Albert Shih wrote: Le 27/04/2012 ? 12:14:04-0500, Adam Vande More a écrit On Fri, Apr 27, 2012 at 11:13 AM, Albert Shihalbert.s...@obspm.fr wrote: Hi all I've got two very strange problem I'm running 9-stable on a Dell Laptop E4200. Since this morning when I put a USB mouse (I've try three mouses to be sure) it's not working. The kernel and HAL see the mouse but Xorg don't seem do anything. The second point is the load of the system is alway more than 1 (~1.5-2) event I do nothing. I kill all services, daemon, software and the load never drop. I've stop : hald dbus powerd etc... and ps don't show any process eating some ressource. But the load is high (and the laptop is very hot). I make a csup of world and build new userland, and news kernel. And nothing change http://www.wonkity.com/~wblock/docs/html/aei.html Well I don't see why this can be from a misconfiguration, the usb mouse work well before I update hald and world. But I read you link and I don't have those option in my configuration of xorg. Any other idea ? But thanks. For the problem about performance I submit this problem on stable mailing list. Regards JAS I was afraid this would happen. And I fear it is just the begining. I assume you did not create any custom hald rule. Did you ? The first thing to do is to add Option AutoAddDevices Off In your ServerLayout section of xorg.conf. Then restart X and try to plug a mouse again. It may result in your mouse not working in X, but at least it should stop your computer from using all it's CPU trying to map the mouse. If indeed the CPU load does not reach skyhigh levels when you plug a USB mouse, we will be able to conclude that there is a DBus/hald problem. Also could you do the following - Mouse unplugged : # /usr/local/etc/rc.d/hald stop # /usr/local/sbin/hald --daemon=no --verbose=yes /tmp/hald_debug.log 21 # dbus-launch lshal /tmp/dbus_hal_debug.log 21 - plug mouse # dbus-launch lshal /tmp/dbus_hal_debug.log 21 And post the content of both log files ? That should help in understanding what is going on. In the worst case there are mecanism that will keep HAL from tinkering/probing usb mouse. Jerome Herman ___ 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
Performance and mouse problems
Hi all I've got two very strange problem I'm running 9-stable on a Dell Laptop E4200. Since this morning when I put a USB mouse (I've try three mouses to be sure) it's not working. The kernel and HAL see the mouse but Xorg don't seem do anything. The second point is the load of the system is alway more than 1 (~1.5-2) event I do nothing. I kill all services, daemon, software and the load never drop. I've stop : hald dbus powerd etc... and ps don't show any process eating some ressource. But the load is high (and the laptop is very hot). I make a csup of world and build new userland, and news kernel. And nothing change HELP...please. Regards. -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: ven 27 avr 2012 18:08:24 CEST ___ 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: Performance and mouse problems
On Fri, Apr 27, 2012 at 11:13 AM, Albert Shih albert.s...@obspm.fr wrote: Hi all I've got two very strange problem I'm running 9-stable on a Dell Laptop E4200. Since this morning when I put a USB mouse (I've try three mouses to be sure) it's not working. The kernel and HAL see the mouse but Xorg don't seem do anything. The second point is the load of the system is alway more than 1 (~1.5-2) event I do nothing. I kill all services, daemon, software and the load never drop. I've stop : hald dbus powerd etc... and ps don't show any process eating some ressource. But the load is high (and the laptop is very hot). I make a csup of world and build new userland, and news kernel. And nothing change http://www.wonkity.com/~wblock/docs/html/aei.html -- Adam Vande More ___ 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.
Thank You. It is working now. -- Best Regards, Mubeesh Ali.V.M On Fri, Jul 8, 2011 at 11:11 PM, Lokadamus lokada...@gmx.de 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
Mouse Problems.
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 ) Freebsd# cat /root/xorg.conf.new Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection Section Module Load dbe Load dri Load dri2 Load extmod Load glx Load record EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option Emulate3Buttons true Option EmulateWheeel true Option EmulateWheelButton 2 Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional Identifier Card0 Driver vboxvideo VendorName InnoTek Systemberatung GmbH BoardName VirtualBox Graphics Adapter BusID PCI:0:2:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection 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 -- Best Regards, Mubeesh Ali.V.M ___ 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 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 09:03:21 -0600 (MDT), Warren Block wbl...@wonkity.com 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, 13 Oct 2010 10:29:31 -0700, Gary Kline kl...@thought.org 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, Oct 13, 2010 at 11:11:22PM +0200, Polytropon wrote:
On Wed, 13 Oct 2010 10:29:31 -0700, Gary Kline kl...@thought.org 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, Polytropon wrote: On Wed, 13 Oct 2010 10:29:31 -0700, Gary Kline kl...@thought.org 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, 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 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 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 Tue, 12 Oct 2010 08:43:43 +0100, Arthur Chance free...@qeng-ho.org 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, 12 Oct 2010 08:48:07 -0700, Gary Kline kl...@thought.org 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, Oct 12, 2010 at 10:10:20PM +0200, Polytropon wrote: On Tue, 12 Oct 2010 08:43:43 +0100, Arthur Chance free...@qeng-ho.org 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 16:30:02 -0700, Gary Kline kl...@thought.org 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....
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 kl...@thought.org 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 ethic [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 untill I sh-exec /etc/rc.d/mouse with the poll arg.
Re: mouse problems....
On Tue, 12 Oct 2010 20:20:18 -0700, Gary Kline kl...@thought.org 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 ethic [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 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 kl...@thought.org 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 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=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x408e39dSSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 real memory = 3478716416 (3317 MB) avail memory = 3399180288 (3241 MB) ACPI APIC Table: DELL FX09 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL FX09on 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: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: PCI bus on pcib1 vgapci0: VGA-compatible display port 0xff00-0xff07 mem 0xfdf0-0xfdf7,0xd000-0xdfff,0xfdb0-0xfdbf irq 16 at device 2.0 on pci0 agp0: Intel G33 SVGA controller on vgapci0 agp0: detected 7164k stolen memory agp0: aperture size is 256M em0: Intel(R) PRO/1000 Network Connection 6.9.6 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: UHCI (generic) USB controller port 0xfd00-0xfd1f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: UHCI (generic) USB controller port 0xfc00-0xfc1f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: UHCI (generic) USB controller port 0xfb00-0xfb1f irq 19 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: UHCI (generic) USB controller on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: EHCI (generic) USB 2.0 controller 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: EHCI (generic) USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb3 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x05e3 USB2.0 Hub, class
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=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x408e39dSSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 real memory = 3478716416 (3317 MB) avail memory = 3399180288 (3241 MB) ACPI APIC Table: DELL FX09 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL FX09on 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: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: PCI bus on pcib1 vgapci0: VGA-compatible display port 0xff00-0xff07 mem 0xfdf0-0xfdf7,0xd000-0xdfff,0xfdb0-0xfdbf irq 16 at device 2.0 on pci0 agp0: Intel G33 SVGA controller on vgapci0 agp0: detected 7164k stolen memory agp0: aperture size is 256M em0: Intel(R) PRO/1000 Network Connection 6.9.6 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: UHCI (generic) USB controller port 0xfd00-0xfd1f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: UHCI (generic) USB controller port 0xfc00-0xfc1f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: UHCI (generic) USB controller port 0xfb00-0xfb1f irq 19 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: UHCI (generic) USB controller on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: EHCI (generic) USB 2.0 controller 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
Re: mouse problems....
On Mon, 11 Oct 2010 09:41:52 -0700, Gary Kline kl...@thought.org 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....
On Mon, Oct 11, 2010 at 07:31:53PM +0200, Polytropon wrote: On Mon, 11 Oct 2010 09:41:52 -0700, Gary Kline kl...@thought.org 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 11:14:38 -0700, Gary Kline kl...@thought.org 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 08:27:41PM +0200, Polytropon wrote: On Mon, 11 Oct 2010 11:14:38 -0700, Gary Kline kl...@thought.org 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 12:14:43 -0700, Gary Kline kl...@thought.org 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 09:32:16PM +0200, Polytropon wrote: On Mon, 11 Oct 2010 12:14:43 -0700, Gary Kline kl...@thought.org 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: rand Combo Free KVM, class 0/0, rev 1.10/0.00, addr 3 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:49:07 -0700, Gary Kline kl...@thought.org 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: rand Combo Free KVM, class 0/0, rev 1.10/0.00, addr 3 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 10:16:09PM +0200, Polytropon wrote: On Mon, 11 Oct 2010 12:49:07 -0700, Gary Kline kl...@thought.org 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: rand Combo Free KVM, class 0/0, rev 1.10/0.00, addr 3 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 13:56:10 -0700, Gary Kline kl...@thought.org 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 11:13:20PM +0200, Polytropon wrote: On Mon, 11 Oct 2010 13:56:10 -0700, Gary Kline kl...@thought.org 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
mouse problems....
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? gary -- 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
mouse problems-version 7.1
Hi all: After I did portupgrade -fa -y and I have mouse problem: it works under the test of sysinstall but it would not work when I start KDE environment. What went wrong? How could i fix this? Thanks ___ 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: Graphics tablet / Xorg / mouse problems
I think it should be sufficient to set hald_enable=FALSE in etc/rc.conf to deactivate hald instead of chmod usr/local/etc/rc.d/hald. Rainer Am 04.02.2009 05:23 (UTC+1) schrieb Antonio Rieser: Hi, Thanks a million for your help. Many thanks to Bartosz, too! Just to be sure I understood how to deactivate hald, I ran (as root) the command chmod -x /usr/local/etc/rc.d/hald which should prevent it from running in the future, then, for this session pkill hald That should do it, right? Also, I reported earlier that everything seems to be normal if I boot with the tablet plugged in, but that's not always true. I now think that if I log in and out enough I get the same error messages. I have enclosed my Device Section of /etc/X11/Xorg.conf below. All the best, Tony - Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor# [bool] #Option ColorKey# i #Option CacheLines # i #Option Dac6Bit # [bool] #Option DRI # [bool] #Option NoDDC # [bool] #Option ShowCache # [bool] #Option XvMCSurfaces# i #Option PageFlip# [bool] Identifier Card0 Driver intel VendorName Intel Corporation BoardName 82852/855GM Integrated Graphics Device BusID PCI:0:2:0 Option Accel On EndSection On Mon, Feb 2, 2009 at 4:36 AM, Dominic Fandrey kamik...@bsdforen.de wrote: Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: ... Just to keep you up to date, Bartosz is on it. Of course, I cannot give you a schedule. With the involvement of hald things seem to get much more complicated. It might be a temporary solution to deactivate hald support. Regards ___ 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
Graphics tablet / Xorg / mouse problems
Hi, Whatever I did before, it had no effect. The temporary fix, for some reason, has been to deactivate kdm. Can anyone explain this? All the best, Tony ___ 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: Graphics tablet / Xorg / mouse problems
On Wed, 2009-02-04 at 23:32 -0500, Antonio Rieser wrote: Hi, Whatever I did before, it had no effect. The temporary fix, for some reason, has been to deactivate kdm. Can anyone explain this? For starters hald should probably be disabled in rc.conf: hald_enable=NO. That said; how are you disabling kdm? Whats working now? This could be a case of root and user permissions, once one has a hold of the device another may not be able to control it and permissions are not passed on. ___ 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: Graphics tablet / Xorg / mouse problems
Hi, Thanks a million for your help. Many thanks to Bartosz, too! Just to be sure I understood how to deactivate hald, I ran (as root) the command chmod -x /usr/local/etc/rc.d/hald which should prevent it from running in the future, then, for this session pkill hald That should do it, right? Also, I reported earlier that everything seems to be normal if I boot with the tablet plugged in, but that's not always true. I now think that if I log in and out enough I get the same error messages. I have enclosed my Device Section of /etc/X11/Xorg.conf below. All the best, Tony - Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor # [bool] #Option ColorKey # i #Option CacheLines# i #Option Dac6Bit # [bool] #Option DRI # [bool] #Option NoDDC # [bool] #Option ShowCache # [bool] #Option XvMCSurfaces # i #Option PageFlip # [bool] Identifier Card0 Driver intel VendorName Intel Corporation BoardName 82852/855GM Integrated Graphics Device BusID PCI:0:2:0 Option Accel On EndSection On Mon, Feb 2, 2009 at 4:36 AM, Dominic Fandrey kamik...@bsdforen.de wrote: Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: ... Just to keep you up to date, Bartosz is on it. Of course, I cannot give you a schedule. With the involvement of hald things seem to get much more complicated. It might be a temporary solution to deactivate hald support. Regards ___ 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: Graphics tablet / Xorg / mouse problems
Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: ... Just to keep you up to date, Bartosz is on it. Of course, I cannot give you a schedule. With the involvement of hald things seem to get much more complicated. It might be a temporary solution to deactivate hald support. Regards ___ 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: Graphics tablet / Xorg / mouse problems
Antonio Rieser said: 2) If I remove the tablet from the computer (I've only tried it during an X session), the system panics and shuts down, whether or not I stop the wacom driver before removing the tablet. Can you replicate this while viewing the console [ctrl+alt+f1] rather than an X session, to see exactly what the kernel is panicing from? (I know systems don't really like being forcibly paniced, but it may help figure out what is happening.) -- Glen Barber ___ 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: Graphics tablet / Xorg / mouse problems
Antonio Rieser wrote: Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: 1) If I boot without the tablet plugged in, then plug it in later and restart X, the error message (EE) intel(0): [DRI] Unlocking inconsistency: Context 676684348 trying to unlock lock held by context 2 (EE) intel(0): [DRI] Locking deadlock. Already locked with context 676684348, trying to lock with context 2. is written to Xorg.0.log and kdm-bin.log so many times that it fills my /var partition and locks my system. Note that if I boot with the tablet already plugged in, this error doesn't appear, and everything works fine. This is actually not connected to the tablet in my opinion, it's a problem with 3D-acceleration of your video card, which apparently does not like being reset/restarted. Can you show us your Device Section? I loading the driver via the line 'uwacom_load=YES in /boot/loader.conf 2) If I remove the tablet from the computer (I've only tried it during an X session), the system panics and shuts down, whether or not I stop the wacom driver before removing the tablet. OK, this sounds like a serious kernel problem. 3) If I stop the wacom driver, then start it again, I cannot simply restart X and have the tablet work. I have to reboot in order for the tablet to be recognized, even in mouse mode. That's because the driver can not start a rescan of the hardware. It can only hook in when the tablet gets first detected. This is why the module has to be loaded from loader.conf. 4) Occasionally the pointer refuses to stay put and drifts to the top of the screen. Controlling the pointer with the mouse becomes difficult at this point, too, since it wants to float upwards. Unfortunately, I have difficulty reproducing this reliably. Once it starts, though, it doesn't stop until I end the X session. If the problem starts and then I stop the wacom driver without restarting X, it continues anyway. I have that with a cheap optical mouse sometimes, I plug it out and back in and the problem is gone. Since that panics your system this is hardly an acceptable solution. Anyway it looks to me like that is a hardware problem. 5) Xorg.0.log contains the following error (also included below): pad Wacom X driver can't grab event device, errno=1005 (I haven't honestly noticed any strange behavior on the 'pad' device, however.) Well, I have taken the liberty to forward this mail to Bartosz, he might be able to do something with that. Obviously the driver does not handle all data generated by the pad. Regarding 1) - and maybe 3) 4) - my guess is that the tablet is fighting with the mouse for control of the pointer, but I don't know how to check if that's the case or how to fix it if it is. No, that's not the way things work. I think you are facing two distinct problems here. One with your video card and one with the tablet driver. ___ 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
Graphics tablet / Xorg / mouse problems
Hi, I recently installed FreeBSD 7.1 on an ACER Aspire 1680 laptop. I'm running KDE 3.5 and the most recent Xorg port with a Wacom Bamboo tablet and the wacom driver from the ports collection. I have the following problems with the tablet and mouse: 1) If I boot without the tablet plugged in, then plug it in later and restart X, the error message (EE) intel(0): [DRI] Unlocking inconsistency: Context 676684348 trying to unlock lock held by context 2 (EE) intel(0): [DRI] Locking deadlock. Already locked with context 676684348, trying to lock with context 2. is written to Xorg.0.log and kdm-bin.log so many times that it fills my /var partition and locks my system. Note that if I boot with the tablet already plugged in, this error doesn't appear, and everything works fine. I loading the driver via the line 'uwacom_load=YES in /boot/loader.conf 2) If I remove the tablet from the computer (I've only tried it during an X session), the system panics and shuts down, whether or not I stop the wacom driver before removing the tablet. 3) If I stop the wacom driver, then start it again, I cannot simply restart X and have the tablet work. I have to reboot in order for the tablet to be recognized, even in mouse mode. 4) Occasionally the pointer refuses to stay put and drifts to the top of the screen. Controlling the pointer with the mouse becomes difficult at this point, too, since it wants to float upwards. Unfortunately, I have difficulty reproducing this reliably. Once it starts, though, it doesn't stop until I end the X session. If the problem starts and then I stop the wacom driver without restarting X, it continues anyway. 5) Xorg.0.log contains the following error (also included below): pad Wacom X driver can't grab event device, errno=1005 (I haven't honestly noticed any strange behavior on the 'pad' device, however.) Regarding 1) - and maybe 3) 4) - my guess is that the tablet is fighting with the mouse for control of the pointer, but I don't know how to check if that's the case or how to fix it if it is. Thanks in advance for any help! All the best, Tony Rieser PS This post is a repost/summary of a recent thread posted under a less transparent subject line. I apologize for the redundancy. ___ 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
USB mouse problems
I have one Razer Lachesis USB mouse attached to the rear usb ports of my pc. This mouse has never worked, however when I plug in another USB mouse in the front of my pc it works?! I wonder; how do I get the Razer Lachesis working without plugging it in the front? Furthermore I wondered if there is a way to use both the mouse in a terminal (gpm) and in xorg? -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems
Le Mon, 06 Oct 2008 08:41:59 +0200, Aniruddha [EMAIL PROTECTED] a écrit : I have one Razer Lachesis USB mouse attached to the rear usb ports of my pc. This mouse has never worked, however when I plug in another USB mouse in the front of my pc it works?! I wonder; how do I get the Razer Lachesis working without plugging it in the front? I don't know. Furthermore I wondered if there is a way to use both the mouse in a terminal (gpm) and in xorg? Yes, see moused(8) and vidcontrol(1). Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems
Patrick Lamaizière wrote: Le Mon, 06 Oct 2008 08:41:59 +0200, Aniruddha [EMAIL PROTECTED] a écrit : I have one Razer Lachesis USB mouse attached to the rear usb ports of my pc. This mouse has never worked, however when I plug in another USB mouse in the front of my pc it works?! I wonder; how do I get the Razer Lachesis working without plugging it in the front? I don't know. Some motherboards have a jumper (or BIOS option) to that has to be set, so that the front connectors work at the expense of other ports. Furthermore I wondered if there is a way to use both the mouse in a terminal (gpm) and in xorg? Yes, see moused(8) and vidcontrol(1). Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, 2008-10-06 at 13:09 +0200, Patrick Lamaizière wrote: Le Mon, 06 Oct 2008 08:41:59 +0200, Aniruddha [EMAIL PROTECTED] a écrit : I have one Razer Lachesis USB mouse attached to the rear usb ports of my pc. This mouse has never worked, however when I plug in another USB mouse in the front of my pc it works?! I wonder; how do I get the Razer Lachesis working without plugging it in the front? I don't know. Furthermore I wondered if there is a way to use both the mouse in a terminal (gpm) and in xorg? Yes, see moused(8) and vidcontrol(1). Regards. ___ Thanks for your help! I'll look into moused and vidcontrol. -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, 2008-10-06 at 22:10 +1030, Andrew D wrote: Patrick Lamaizière wrote: Le Mon, 06 Oct 2008 08:41:59 +0200, Aniruddha [EMAIL PROTECTED] a écrit : I have one Razer Lachesis USB mouse attached to the rear usb ports of my pc. This mouse has never worked, however when I plug in another USB mouse in the front of my pc it works?! I wonder; how do I get the Razer Lachesis working without plugging it in the front? I don't know. Some motherboards have a jumper (or BIOS option) to that has to be set, so that the front connectors work at the expense of other ports. I don't think this has something to with a bios setting/jumper. My other USB ports are working fine ( I also have an USB keyboard plugged in). Furthermore in Linux nor Vista I've encountered this problem. Therefor I suspect it must have something to do with FreeBSD. Maybe it's an bug? If someone has an solution that would be great! -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, Oct 06, 2008 at 06:52:22PM +0200, Aniruddha wrote: On Mon, 2008-10-06 at 22:10 +1030, Andrew D wrote: Patrick Lamaizière wrote: Le Mon, 06 Oct 2008 08:41:59 +0200, Aniruddha [EMAIL PROTECTED] a écrit : I have one Razer Lachesis USB mouse attached to the rear usb ports of my pc. This mouse has never worked, however when I plug in another USB mouse in the front of my pc it works?! I wonder; how do I get the Razer Lachesis working without plugging it in the front? I don't know. Some motherboards have a jumper (or BIOS option) to that has to be set, so that the front connectors work at the expense of other ports. I don't think this has something to with a bios setting/jumper. My other USB ports are working fine ( I also have an USB keyboard plugged in). Furthermore in Linux nor Vista I've encountered this problem. Therefor I suspect it must have something to do with FreeBSD. Maybe it's an bug? If someone has an solution that would be great! FreeBSD's existing USB stack is known to be... shall we say, flaky. It's well-established at this point. The possibility of it being related to FreeBSD's USB stack is very likely. A new USB stack is available for CURRENT, but requires manual patching. If you're willing to try this, you should get in contact with Alfred Perlstein [EMAIL PROTECTED] to discuss/get the patch. Keep in mind that this patch, as I stated, only applies to CURRENT, and not to FreeBSD 7 or earlier. You can download a CURRENT ISO here: ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ -- | Jeremy Chadwickjdc at 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 [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote: I don't think this has something to with a bios setting/jumper. My other USB ports are working fine ( I also have an USB keyboard plugged in). Furthermore in Linux nor Vista I've encountered this problem. Therefor I suspect it must have something to do with FreeBSD. Maybe it's an bug? If someone has an solution that would be great! FreeBSD's existing USB stack is known to be... shall we say, flaky. It's well-established at this point. The possibility of it being related to FreeBSD's USB stack is very likely. A new USB stack is available for CURRENT, but requires manual patching. If you're willing to try this, you should get in contact with Alfred Perlstein [EMAIL PROTECTED] to discuss/get the patch. Keep in mind that this patch, as I stated, only applies to CURRENT, and not to FreeBSD 7 or earlier. You can download a CURRENT ISO here: ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ Lol, during my search for a solution I did see numerous problems with mice. Out of curiosity; is CURRENT the same as FreeBSD 7.1-BETA? -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, Oct 06, 2008 at 07:23:00PM +0200, Aniruddha wrote: On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote: I don't think this has something to with a bios setting/jumper. My other USB ports are working fine ( I also have an USB keyboard plugged in). Furthermore in Linux nor Vista I've encountered this problem. Therefor I suspect it must have something to do with FreeBSD. Maybe it's an bug? If someone has an solution that would be great! FreeBSD's existing USB stack is known to be... shall we say, flaky. It's well-established at this point. The possibility of it being related to FreeBSD's USB stack is very likely. A new USB stack is available for CURRENT, but requires manual patching. If you're willing to try this, you should get in contact with Alfred Perlstein [EMAIL PROTECTED] to discuss/get the patch. Keep in mind that this patch, as I stated, only applies to CURRENT, and not to FreeBSD 7 or earlier. You can download a CURRENT ISO here: ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ Lol, during my search for a solution I did see numerous problems with mice. Out of curiosity; is CURRENT the same as FreeBSD 7.1-BETA? No -- significantly different. CURRENT is super alpha it's probably going to break, while 7.1-BETA is simply the upcoming release of 7.1 which is slated to become -STABLE after a few months. -- | Jeremy Chadwickjdc at 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 [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, 2008-10-06 at 11:00 -0700, Jeremy Chadwick wrote: On Mon, Oct 06, 2008 at 07:23:00PM +0200, Aniruddha wrote: On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote: I don't think this has something to with a bios setting/jumper. My other USB ports are working fine ( I also have an USB keyboard plugged in). Furthermore in Linux nor Vista I've encountered this problem. Therefor I suspect it must have something to do with FreeBSD. Maybe it's an bug? If someone has an solution that would be great! FreeBSD's existing USB stack is known to be... shall we say, flaky. It's well-established at this point. The possibility of it being related to FreeBSD's USB stack is very likely. No -- significantly different. CURRENT is super alpha it's probably going to break, while 7.1-BETA is simply the upcoming release of 7.1 which is slated to become -STABLE after a few months. Ah I see. Unfortunately I think I have found the problem. My Razer Lachesis doesn't work with FreeBSD. It doesn't matter which USB port I use. I found this patch though: http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/118670 What does 3-20-2008: Fix merged to RELENG_7 mean? Is this fix available in the FreeBSD 7 (stable) release I'm running? Thanks in advance! -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, Oct 06, 2008 at 08:53:30PM +0200, Aniruddha wrote: On Mon, 2008-10-06 at 11:00 -0700, Jeremy Chadwick wrote: On Mon, Oct 06, 2008 at 07:23:00PM +0200, Aniruddha wrote: On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote: I don't think this has something to with a bios setting/jumper. My other USB ports are working fine ( I also have an USB keyboard plugged in). Furthermore in Linux nor Vista I've encountered this problem. Therefor I suspect it must have something to do with FreeBSD. Maybe it's an bug? If someone has an solution that would be great! FreeBSD's existing USB stack is known to be... shall we say, flaky. It's well-established at this point. The possibility of it being related to FreeBSD's USB stack is very likely. No -- significantly different. CURRENT is super alpha it's probably going to break, while 7.1-BETA is simply the upcoming release of 7.1 which is slated to become -STABLE after a few months. Ah I see. Unfortunately I think I have found the problem. My Razer Lachesis doesn't work with FreeBSD. It doesn't matter which USB port I use. I found this patch though: http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/118670 What does 3-20-2008: Fix merged to RELENG_7 mean? Is this fix available in the FreeBSD 7 (stable) release I'm running? Thanks in advance! It means the original fix was applied to CURRENT (what is also known as HEAD), and then backported to RELENG_7 (what you would call FreeBSD 7.x-STABLE) on 2008/03/20. MFC stands for Merge From CURRENT. You can confirm this by looking at cvsweb for the file in question: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ums.c The change for HEAD/CURRENT was made in Revision 1.98 (date = Mar 12) The MFC to RELENG_7 was made in Revision 1.96.2.1 (date = Mar 20) If you csup your src tree (use /usr/share/examples/cvsup/stable-supfile) the patched code will be downloaded and used. You'll have to rebuild world to get the changes, of course. See the FreeBSD Handbook for doing a csup as well as for rebuilding world. -- | Jeremy Chadwickjdc at 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 [EMAIL PROTECTED]
Re: USB mouse problems
On Mon, 2008-10-06 at 12:03 -0700, Jeremy Chadwick wrote: It means the original fix was applied to CURRENT (what is also known as HEAD), and then backported to RELENG_7 (what you would call FreeBSD 7.x-STABLE) on 2008/03/20. MFC stands for Merge From CURRENT. You can confirm this by looking at cvsweb for the file in question: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ums.c The change for HEAD/CURRENT was made in Revision 1.98 (date = Mar 12) The MFC to RELENG_7 was made in Revision 1.96.2.1 (date = Mar 20) If you csup your src tree (use /usr/share/examples/cvsup/stable-supfile) the patched code will be downloaded and used. You'll have to rebuild world to get the changes, of course. See the FreeBSD Handbook for doing a csup as well as for rebuilding world. Thanks for your help and patience. If I'm not mistaken I can also install 7.1 Beta. It would be logical to assume it contains the fix right? -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems (SOLVED)
On Mon, 2008-10-06 at 21:58 +0200, Aniruddha wrote: On Mon, 2008-10-06 at 12:03 -0700, Jeremy Chadwick wrote: It means the original fix was applied to CURRENT (what is also known as HEAD), and then backported to RELENG_7 (what you would call FreeBSD 7.x-STABLE) on 2008/03/20. MFC stands for Merge From CURRENT. You can confirm this by looking at cvsweb for the file in question: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ums.c The change for HEAD/CURRENT was made in Revision 1.98 (date = Mar 12) The MFC to RELENG_7 was made in Revision 1.96.2.1 (date = Mar 20) If you csup your src tree (use /usr/share/examples/cvsup/stable-supfile) the patched code will be downloaded and used. You'll have to rebuild world to get the changes, of course. See the FreeBSD Handbook for doing a csup as well as for rebuilding world. Thanks for your help and patience. If I'm not mistaken I can also install 7.1 Beta. It would be logical to assume it contains the fix right? I just installed 7.1 Beta and now my Razer Lachesis works :D -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems.
On Tue, 12 Aug 2008 16:00:24 +0200, Bernt Hansson [EMAIL PROTECTED] wrote: So if I want to use the mouse I have to leave it unconnected until I get the login prompt and then connect the mouse. Just out of curiosity, did you try to use another mouse to ensure that it's not the mouse's problem? I have a similar problem since updating to FreeBSD 7 with my Sun Type 6 USB mouse which is recognized some time after the system startup has finished. (Same for the Sun USB keyboard.) -- Polytropon From 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 [EMAIL PROTECTED]
Re: USB mouse problems.
El Mar 12 Ago 2008, Bernt Hansson escribió: Yes but only if I connect the mouse after the boot process has finished. If I have it connected during boot it's not found. Moused is started but gives /dev/ums0 not found. So if I want to use the mouse I have to leave it unconnected until I get the login prompt and then connect the mouse. leave it disconected and use the command # usbdevs maps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems.
El Sáb 09 Ago 2008, Bernt Hansson escribió: ums0: A4Tech PS/2+USB Mouse, class 0/0, rev 1.10/0.02, addr 2 on uhub1 ums0: 8 buttons and Z dir if you see those lines, means the kernel found your mouse, run the command ps axw|grep -i mouse to see if moused is running maps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse problems.
Yes but only if I connect the mouse after the boot process has finished. If I have it connected during boot it's not found. Moused is started but gives /dev/ums0 not found. So if I want to use the mouse I have to leave it unconnected until I get the login prompt and then connect the mouse. Try a different usb port. On my box, only the two in the front work right. br - N :o) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 RC2 usb keyboard and mouse problems
--On Thursday, February 21, 2008 20:41:59 +0100 Nikolaj Thygesen [EMAIL PROTECTED] wrote: Paul Schmehl wrote: I just installed 7.0 RC2 on a brand new Dell - dual processor dual core Intel (so four processors), and I'm losing the keyboard and mouse after taking certain actions. For example, I started setting up X (Xorg --configure) and then launched it (X -config /root/xorg.conf-new), and when I get to the GUI the mouse and keyboard are gone. Sometimes I can restore functionality by unplugging the devices and then plugging them back in. This is happening in the console as well, not just in the GUI. I've fetched the latest sources using cvsup. Will rebuilding the kernel solve this problem? Is this a known issue? usbhidctl shows ums0, ums1, ukbd0 and ukbd1 to be busy. [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ums0 usbhidctl: /dev/ums0: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ums1 usbhidctl: /dev/ums1: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd ukbd0 ukbd1 [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd0 usbhidctl: /dev/ukbd0: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd1 usbhidctl: /dev/ukbd1: Device busy This is what I see after unplugging both devices and plugging them in to different usb receptacles. usbdevs addr 1: UHCI root hub, Intel addr 2: product 0x2105, vendor 0x413c addr 3: product 0x4d15, vendor 0x0461 addr 1: UHCI root hub, Intel addr 1: EHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 3: product 0x2105, vendor 0x413c addr 2: product 0x4d15, vendor 0x0461 addr 1: EHCI root hub, Intel FreeBSD utd65257.utdallas.edu 7.0-RC2-p1 FreeBSD 7.0-RC2-p1 #0: Tue Feb 12 22:23:33 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 grep usb /var/run/dmesg.boot usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: EHCI (generic) USB 2.0 controller on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb2 usb3: UHCI (generic) USB controller on uhci2 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3 usb4: UHCI (generic) USB controller on uhci3 usb4: USB revision 1.0 uhub4: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb4 usb5: UHCI (generic) USB controller on uhci4 usb5: USB revision 1.0 uhub5: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb5 usb6: waiting for BIOS to give up control usb6: timed out waiting for BIOS usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: EHCI (generic) USB 2.0 controller on ehci1 usb6: USB revision 2.0 uhub6: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb6 Any clues or help would be appreciated. Hi Paul I just spent about a week solving that very same issue. The thing is that in order for the usb mouse and keyboard to work during the initial boot sequence, ps/2 style devices are needed, so your bios is probably configured for simulating ps/2 (legacy) devices on usb. Keep it that way! As the kernel boots, usb devices are suddenly supported, but present ps/2 devices (even the simulated legacy ones) will hide the usb devices from the kernel, so in order to get access to these the following lines must be added to /boot/device.hints: hint.atkbd.0.disable=1 hint.atkbdc.0.disable=1 I understand that only one of them is needed, but I have no idea which one. It supposedly differs from machine to machine. The last crucial point (and the one I really fought with) is the fact that not all usb ports are created equal! If the above doesn't work, try switching usb ports. It seems some usb ports/hubs are preferred over others. On my machine the two front ports work, but the six ports on the rear of the machine don't :o( At least it works now, and I no longer need to have two keyboards attached. br - N :o) I found a post in stable describing the exact same issue. The OP solved it by connecting a hub to a port on the back of the machine and then connecting the keyboard and mouse to the hub. So, I plugged in one of my monitors and then connected the keyboard and mouse to the monitor, and they work fine. I joined the stable list so I can report this and possibly help troubleshoot it. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL
Re: 7.0 RC2 usb keyboard and mouse problems
Paul Schmehl wrote: I just installed 7.0 RC2 on a brand new Dell - dual processor dual core Intel (so four processors), and I'm losing the keyboard and mouse after taking certain actions. For example, I started setting up X (Xorg --configure) and then launched it (X -config /root/xorg.conf-new), and when I get to the GUI the mouse and keyboard are gone. Sometimes I can restore functionality by unplugging the devices and then plugging them back in. This is happening in the console as well, not just in the GUI. I've fetched the latest sources using cvsup. Will rebuilding the kernel solve this problem? Is this a known issue? usbhidctl shows ums0, ums1, ukbd0 and ukbd1 to be busy. [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ums0 usbhidctl: /dev/ums0: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ums1 usbhidctl: /dev/ums1: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd ukbd0 ukbd1 [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd0 usbhidctl: /dev/ukbd0: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd1 usbhidctl: /dev/ukbd1: Device busy This is what I see after unplugging both devices and plugging them in to different usb receptacles. usbdevs addr 1: UHCI root hub, Intel addr 2: product 0x2105, vendor 0x413c addr 3: product 0x4d15, vendor 0x0461 addr 1: UHCI root hub, Intel addr 1: EHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 3: product 0x2105, vendor 0x413c addr 2: product 0x4d15, vendor 0x0461 addr 1: EHCI root hub, Intel FreeBSD utd65257.utdallas.edu 7.0-RC2-p1 FreeBSD 7.0-RC2-p1 #0: Tue Feb 12 22:23:33 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 grep usb /var/run/dmesg.boot usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: EHCI (generic) USB 2.0 controller on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb2 usb3: UHCI (generic) USB controller on uhci2 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3 usb4: UHCI (generic) USB controller on uhci3 usb4: USB revision 1.0 uhub4: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb4 usb5: UHCI (generic) USB controller on uhci4 usb5: USB revision 1.0 uhub5: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb5 usb6: waiting for BIOS to give up control usb6: timed out waiting for BIOS usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: EHCI (generic) USB 2.0 controller on ehci1 usb6: USB revision 2.0 uhub6: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb6 Any clues or help would be appreciated. Hi Paul I just spent about a week solving that very same issue. The thing is that in order for the usb mouse and keyboard to work during the initial boot sequence, ps/2 style devices are needed, so your bios is probably configured for simulating ps/2 (legacy) devices on usb. Keep it that way! As the kernel boots, usb devices are suddenly supported, but present ps/2 devices (even the simulated legacy ones) will hide the usb devices from the kernel, so in order to get access to these the following lines must be added to /boot/device.hints: hint.atkbd.0.disable=1 hint.atkbdc.0.disable=1 I understand that only one of them is needed, but I have no idea which one. It supposedly differs from machine to machine. The last crucial point (and the one I really fought with) is the fact that not all usb ports are created equal! If the above doesn't work, try switching usb ports. It seems some usb ports/hubs are preferred over others. On my machine the two front ports work, but the six ports on the rear of the machine don't :o( At least it works now, and I no longer need to have two keyboards attached. br - N :o) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mouse problems booting rebooting
I have a laptop with a touchpad which is seen by FreeBSD 5.4 as a ps/2 mouse. I configured moused and xorg.conf where the mouse has protocol Auto and device /dev/sysmouse. now, 1) if I turn ON the pc and boot the mouse works flawlessly as expected. Specifically I mean, among other things, that double-hitting the pad an application icon the application is selected and launched, hitting the pad open a menu and select an item of it, etc.. 2) if I reboot into FreeBSD without turning off the computer from either win XP or Freebsd 5.4 itself, the mouse can only move around but it is unable to launch anything by double-hitting the pad or even to open any menu by hitting the pad. It all goes as though when rebooting without turning off the pc something alien is kept in the memory of the mousepad, in its wires and this disturbs the consequent setting. My question is: Is there any way under freebsd 5.4 at boot time to completely reset the mouse, to clear anything alien from it? Ciao Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg mouse problems
I had similar issues with Xorg and moused on an Apex Outlook KVM. I sumply disabled moused.. and just use the device section6 of my Xorg.conf to enable the mouse. You could also try compiling the kernel with device hints and add hint.psm.0.flags=0x100 to your hint file T - Original Message - From: Alexander Chamandy [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Sunday, March 27, 2005 5:39 PM Subject: Xorg mouse problems Hi all, I've got a PS/2 Labtech optical mouse with and Xorg 6.8.2 running on FreeBSD 5.4PR with an AMD Athlon and a GeForce 2 MX and I'm having some strange problems with Xorg and moused. This all worked fine under NetBSD (1.6.x and 2.0) with the wsmouse driver, but strangely, now when I use Xorg and/or moused on FreeBSD the mouse skips on verticle or horizontal movement all the way across the screen. I've tried changing the resolution, disabling ACPI, using different protocols and nothing has resolved the problem. Has anyone experienced this before and if so, how have they resolved it? dmesg included: Copyright (c) 1992-2005 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 5.4-PRERELEASE #0: Sun Mar 27 08:12:11 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ambrosia Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Processor (1343.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x644 Stepping = 4 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 805224448 (767 MB) avail memory = 782417920 (746 MB) npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 9 Entries on motherboard $PIR: BIOS IRQ 15 for 0.4.INTC is not valid for link 0x3 pci0: PCI bus on pcib0 $PIR: ROUTE_INTERRUPT failed. agp0: VIA 82C8363 (Apollo KT133x/KM133) host to PCI bridge mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 7 at device 4.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 7 at device 4.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 4.4 (no driver attached) pci0: multimedia, audio at device 4.5 (no driver attached) xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xa400-0xa47f mem 0xd580-0xd580007f irq 7 at device 13.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:e3:6d:42 atapci1: Promise PDC20265 UDMA100 controller port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xd500-0xd501 irq 10 at device 17.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 orm0: ISA Option ROMs at iomem 0xd-0xd07ff,0xcc000-0xce7ff,0xc-0xcb7ff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNPb002 can't assign resources (irq) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0303 can't assign resources (port) Timecounter TSC frequency 1343055484 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDROM CRD-8320B/1.24 at ata0-master PIO4 ad4: 76319MB WDC WD800JB-00CRA1/17.07W17 [155061/16/63] at ata2-master UDMA100 Mounting root from ufs:/dev/ad4s1a -- Best wishes, Alexander G. Chamandy Webmaster www.bsdfreak.org Your Source For BSD News! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED
Xorg mouse problems
Hi all, I've got a PS/2 Labtech optical mouse with and Xorg 6.8.2 running on FreeBSD 5.4PR with an AMD Athlon and a GeForce 2 MX and I'm having some strange problems with Xorg and moused. This all worked fine under NetBSD (1.6.x and 2.0) with the wsmouse driver, but strangely, now when I use Xorg and/or moused on FreeBSD the mouse skips on verticle or horizontal movement all the way across the screen. I've tried changing the resolution, disabling ACPI, using different protocols and nothing has resolved the problem. Has anyone experienced this before and if so, how have they resolved it? dmesg included: Copyright (c) 1992-2005 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 5.4-PRERELEASE #0: Sun Mar 27 08:12:11 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ambrosia Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Processor (1343.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x644 Stepping = 4 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 805224448 (767 MB) avail memory = 782417920 (746 MB) npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 9 Entries on motherboard $PIR: BIOS IRQ 15 for 0.4.INTC is not valid for link 0x3 pci0: PCI bus on pcib0 $PIR: ROUTE_INTERRUPT failed. agp0: VIA 82C8363 (Apollo KT133x/KM133) host to PCI bridge mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 7 at device 4.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 7 at device 4.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 4.4 (no driver attached) pci0: multimedia, audio at device 4.5 (no driver attached) xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xa400-0xa47f mem 0xd580-0xd580007f irq 7 at device 13.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:e3:6d:42 atapci1: Promise PDC20265 UDMA100 controller port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xd500-0xd501 irq 10 at device 17.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 orm0: ISA Option ROMs at iomem 0xd-0xd07ff,0xcc000-0xce7ff,0xc-0xcb7ff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNPb002 can't assign resources (irq) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0303 can't assign resources (port) Timecounter TSC frequency 1343055484 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDROM CRD-8320B/1.24 at ata0-master PIO4 ad4: 76319MB WDC WD800JB-00CRA1/17.07W17 [155061/16/63] at ata2-master UDMA100 Mounting root from ufs:/dev/ad4s1a -- Best wishes, Alexander G. Chamandy Webmaster www.bsdfreak.org Your Source For BSD News! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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! - Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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]
Mouse problems
Hi My name is Tomas. I've recently installed FreeBSD and this is the first time ever that I install a UNIX system. I use Solaris at work but as said this is the first time for me as root. Everything worked fine and I now have my file/printserver up and running. However a while ago I decided to add a graphical environment for convenience and that is when I ran into trouble. My problem is that when I start X (Gnome or KDE) my PS/2 mouse goes bananas. Basically it moves in the inverse direction on both axises (up and right) and does not respont on movements down or left. (The pointer then ends down in the bottom left corner.) Buttons seem to work. Here is what I know. I run BSD version 5.2.1, XFree86 and latest releases of Gnome/KDE. In the mousedeamon test program in found in the sysinstall program, the mouse works properly. If I start X and then exit it, the mouse is still activated and it works properly! This is the reason I thought it might be related to Gnome but I get the same behaviour after installing KDE. I then add a plug and pray compatible USB mouse from logitech and it acts identically. (Yes I've tried different PS/2:s aswell, 2,3 buttons with or without scroll.) According to documentation auto detection should work for all PS/2 mouses. XFree homepage states that the BSD mouse deamon should work fine. The XFree config says nothing that to me indicates problems. As I understand You've terminated cooperation with XFree but I doubt that a change to Xorg will solve this particular problem. I have tried to find this problem on the web but failed, and now i really dont know where to go but to call you. Please tell me that I am just a stupid user who forgot to do something really trivial. 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. Thanx in advance Tomas ___ [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 ProtocolSysMouse 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
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
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
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]
Mouse problems with KVM switch
Hi, I have just brought this KVM switch: http://www.level1.com/products3.php?sklop=20id=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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mouse problems with KVM switch
Hi, I have just brought this KVM switch: http://www.level1.com/products3.php?sklop=20id=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 ps: sorry if this is posted one time already... I have hade some problems with my MUA. ___ [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
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=20id=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 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=20id=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
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=20id=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 looking for others who had problems. Best of Luck Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To
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
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=20id=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
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
From: Mattias Björk [EMAIL PROTECTED] Hello, [EMAIL PROTECTED] wrote: From: thrawn [EMAIL PROTECTED] Date: Thursday, August 19, 2004 6:18 am snip 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 snip 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
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=20id=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
