Date: Wed, 13 Oct 2010 22:44:46 +0200 From: Polytropon <freebsd@edvax.de> To: Warren Block <wblock@wonkity.com> Cc: Gary Kline <kline@thought.org>, Mailing List <freebsd-stable@freebsd.org>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: mouse problems.... Message-ID: <20101013224446.382b5293.freebsd@edvax.de> In-Reply-To: <alpine.BSF.2.00.1010130854280.12928@wonkity.com> References: <20101011032642.GA3354@thought.org> <20101011164152.GA4652@thought.org> <20101011193153.758efde5.freebsd@edvax.de> <4CB411AF.5050109@qeng-ho.org> <20101012221020.1a8dcd90.freebsd@edvax.de> <20101012233002.GA4957@thought.org> <20101013014326.6630e3b5.freebsd@edvax.de> <20101013032018.GA3163@thought.org> <20101013055906.bdc5f644.freebsd@edvax.de> <alpine.BSF.2.00.1010130854280.12928@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Oct 2010 09:03:21 -0600 (MDT), Warren Block <wblock@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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101013224446.382b5293.freebsd>