Re: KVM switch vs. FreeBSD psm driver (Solved!)
John Polstra wrote: > > In article <[EMAIL PROTECTED]>, > John Polstra <[EMAIL PROTECTED]> wrote: > > > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > > much smarter than it really is. When I try to use the mouse through > > it with FreeBSD (-current from around Christmas, but I also had > > problems with -stable) it doesn't work right at all. It's got the > > same symptoms everybody else has reported: the cursor jumps around, > > and lots of "psmintr: out of sync" messages get logged. > > I'm happy to report that this problem is solved now. After one fellow > wrote to me and reported that his switch of the same model worked OK, > I hunted around on the Belkin web site. It turns out that Belkin > assembled a few thousand of the units with two EPROMs swapped This is an all time classic! -- "The most difficult thing in the world is to know how to do a thing and to watch someone else do it wrong without comment." -- Theodore H. White Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
On Sat, Jan 06, 2001 at 11:20:43PM -0700, Wes Peters wrote: > John Polstra wrote: > > > > I'm happy to report that this problem is solved now. After one fellow > > wrote to me and reported that his switch of the same model worked OK, > > I hunted around on the Belkin web site. It turns out that Belkin > > assembled a few thousand of the units with two EPROMs swapped, and > > mine was one of them. I moved the chips to their proper sockets, and > > now everything works fine. You can find the gory details here: > > Snort. Let's hear it for good web support, though. Now that's some robust firmware; what's amazing is that it even worked at all! -Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
>So, question: is there a reason why we can't enable both the USB keyboard >and a native PS/2 keyboard with syscons? It seems that I frequently find >myself in a position where I'd like to plug in a keyboard, or switch KVM >choices to a machine, and discover myself with no access to the hardware >console, and I know at least one person who uses FreeBSD in production and >finds this to be a serious impediment (as it requires the system to be >rebooted to regain console access, and when you have 8 machines per KVM, >and you boot them all, switching back and forth to catch each probe is >effectively impossible). Presumably our syscons is intended to select on >source of I/O and use it, but it might be worth considering a change here. This IS already possible in RELENG_4 and -CURRENT. Add the flags 0x100 to syscons (this is default in both RELENG_4 and CURRENT). Then syscons will look for a keyboard if it started without one at boot time. I don't know if this mechanism works well with KVMs. I never tested with KVMs, because I don't use one. But, it works wonderfully with the USB keyboard. As for unplugging/plugging the AT keyboard... Well, I don't recommend that. That will likely fly your keyboard controller... But, still syscons should be able to use the AT keyboard which is plugged after boot, so long as atkbd is forced to install at boot time. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
On Sun, 7 Jan 2001, Kazutaka YOKOTA wrote: > I guess your KVM switch won't let the kernel talk to the keyboard, if > the switch wasn't pointed to the FreeBSD box. > > Remove the flags 0x1 from atkbd in your kernel config file. This flag > makes atkbd fail, if it doesn't detect a keyboard. Without the flag, > atkbd will install regardless of the absence of the keyboard. > > In RELENG_2 and RELENG_3, this flag wasn't specified to atkbd by > default. In RELENG_4, the flag was added to GENERIC so that syscons will > use a USB keyboard, if any, when there is no AT keyboard. So, question: is there a reason why we can't enable both the USB keyboard and a native PS/2 keyboard with syscons? It seems that I frequently find myself in a position where I'd like to plug in a keyboard, or switch KVM choices to a machine, and discover myself with no access to the hardware console, and I know at least one person who uses FreeBSD in production and finds this to be a serious impediment (as it requires the system to be rebooted to regain console access, and when you have 8 machines per KVM, and you boot them all, switching back and forth to catch each probe is effectively impossible). Presumably our syscons is intended to select on source of I/O and use it, but it might be worth considering a change here. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver
>I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's >much smarter than it really is. I've had so many problems with this product that I dumped it for an Apex Outlook. I couldn't be happier. Since I donated the Belkin to another group, I've heard that they were able to send it in to be fixed. There was some manufacturing defect on early boxes that accounted for part of my problem. Since the signal quality through the switch was so poor anyway, I don't regret going to the Apex. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
>Do you know if this fixes the problem the following problem that I started >experiencing somewhere in the RELENG_4 line? For some machines, if the >KVM is not pointed at the box, the keyboard will not probe properly, and >does not respond for that session. As long as I boot with the KVM pointed >at the machine during the boot process, it probes fine. This doesn't seem >to impact the boot loaders, only after the kernel has loaded and probed. >It's really annoying as my crashbox has this problem, so I have to swap to >it every time I boot, and given the need to type continue in the serial >gdb, I often miss the window. I guess your KVM switch won't let the kernel talk to the keyboard, if the switch wasn't pointed to the FreeBSD box. Remove the flags 0x1 from atkbd in your kernel config file. This flag makes atkbd fail, if it doesn't detect a keyboard. Without the flag, atkbd will install regardless of the absence of the keyboard. In RELENG_2 and RELENG_3, this flag wasn't specified to atkbd by default. In RELENG_4, the flag was added to GENERIC so that syscons will use a USB keyboard, if any, when there is no AT keyboard. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
John Polstra wrote: > > In article <[EMAIL PROTECTED]>, > John Polstra <[EMAIL PROTECTED]> wrote: > > > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > > much smarter than it really is. When I try to use the mouse through > > it with FreeBSD (-current from around Christmas, but I also had > > problems with -stable) it doesn't work right at all. It's got the > > same symptoms everybody else has reported: the cursor jumps around, > > and lots of "psmintr: out of sync" messages get logged. > > I'm happy to report that this problem is solved now. After one fellow > wrote to me and reported that his switch of the same model worked OK, > I hunted around on the Belkin web site. It turns out that Belkin > assembled a few thousand of the units with two EPROMs swapped, and > mine was one of them. I moved the chips to their proper sockets, and > now everything works fine. You can find the gory details here: Snort. Let's hear it for good web support, though. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver
John Polstra wrote: > > I realize this is a well-known problem. Although there's much > discussion about it in the mailing list archives, I couldn't find an > actual solution. > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > much smarter than it really is. When I try to use the mouse through > it with FreeBSD (-current from around Christmas, but I also had > problems with -stable) it doesn't work right at all. It's got the > same symptoms everybody else has reported: the cursor jumps around, > and lots of "psmintr: out of sync" messages get logged. I have a Belkin OmniCube 4-Port KVM I use with FreeBSD-notso-current from prior to SMPng and FreeBSD-STABLE, it works fine with my Logitech MouseMan M37. We have a bunch of these OmniCubes at work, and they have fits with some cheap mice, but rarely fail with Logitech or Microsoft (ick!) mice. My brother informs be Belkin KVM switches drive his Linux machines into fits, and to use the other really big brand of KVM switches that isn't coming to mind right now. YMMV. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
On 6 Jan 2001, at 22:10, Robert Watson wrote: > Do you know if this fixes the problem the following problem that I started > experiencing somewhere in the RELENG_4 line? For some machines, if the > KVM is not pointed at the box, the keyboard will not probe properly, and > does not respond for that session. As long as I boot with the KVM pointed > at the machine during the boot process, it probes fine. This doesn't seem > to impact the boot loaders, only after the kernel has loaded and probed. > It's really annoying as my crashbox has this problem, so I have to swap to > it every time I boot, and given the need to type continue in the serial > gdb, I often miss the window. This is probably not helpful to your situation, but thought I should contribute this as it is KVM related. I just bought a KVM switch (My Hopper, by Rextron Technology). I bought 10M cables to use with it. The FreeBSD box won't boot if I use those cables. It thinks the keyboard isn't there. Note: this appears to be a BIOS problem as if I want long enough, I get the "keyboard not found, press F1 to continue" message. If I don't use the 10M cables, the box boots as expected. Yes, I've thought of enabling no-keyboard booting, but there is no setting in the BIOS. It's on the motherboard I'm told and I've yet to open the box and find it. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ FreshPorts - http://freshports.org/ NZ Broadband - http://unixathome.org/broadband/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
On Sat, 6 Jan 2001, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > John Polstra <[EMAIL PROTECTED]> wrote: > > > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > > much smarter than it really is. When I try to use the mouse through > > it with FreeBSD (-current from around Christmas, but I also had > > problems with -stable) it doesn't work right at all. It's got the > > same symptoms everybody else has reported: the cursor jumps around, > > and lots of "psmintr: out of sync" messages get logged. > > I'm happy to report that this problem is solved now. After one fellow > wrote to me and reported that his switch of the same model worked OK, > I hunted around on the Belkin web site. It turns out that Belkin > assembled a few thousand of the units with two EPROMs swapped, and > mine was one of them. I moved the chips to their proper sockets, and > now everything works fine. You can find the gory details here: > > http://www.belkin.com/support/downloads/manuals/Omnipro.pdf Do you know if this fixes the problem the following problem that I started experiencing somewhere in the RELENG_4 line? For some machines, if the KVM is not pointed at the box, the keyboard will not probe properly, and does not respond for that session. As long as I boot with the KVM pointed at the machine during the boot process, it probes fine. This doesn't seem to impact the boot loaders, only after the kernel has loaded and probed. It's really annoying as my crashbox has this problem, so I have to swap to it every time I boot, and given the need to type continue in the serial gdb, I often miss the window. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver (Solved!)
In article <[EMAIL PROTECTED]>, John Polstra <[EMAIL PROTECTED]> wrote: > > I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's > much smarter than it really is. When I try to use the mouse through > it with FreeBSD (-current from around Christmas, but I also had > problems with -stable) it doesn't work right at all. It's got the > same symptoms everybody else has reported: the cursor jumps around, > and lots of "psmintr: out of sync" messages get logged. I'm happy to report that this problem is solved now. After one fellow wrote to me and reported that his switch of the same model worked OK, I hunted around on the Belkin web site. It turns out that Belkin assembled a few thousand of the units with two EPROMs swapped, and mine was one of them. I moved the chips to their proper sockets, and now everything works fine. You can find the gory details here: http://www.belkin.com/support/downloads/manuals/Omnipro.pdf John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: KVM switch vs. FreeBSD psm driver
I have the same problem with Windows, Linux, and FreeBSD. I am using assorted MS wheel mice. Windows I can get to recover, by switching back and forth a couple times. Linux sometimes the problem goes away if I config X for a generic two-button mouse and no three button emulation. FreeBSD the only thing I can do is use the keyboard command to kill X and startx again and everything is fine. Steve B. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > John Polstra > Sent: Saturday, January 06, 2001 2:32 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: KVM switch vs. FreeBSD psm driver > > > In article > <[EMAIL PROTECTED]>, > jack <[EMAIL PROTECTED]> wrote: > > > > I have a Brand X KVM which also claims Intellimouse support. > > I've found that if the switch is set to a machine when that > > machine boots all is well, if I boot a machine with a different > > one active on the KVM when I go to the one that was booted the > > mouse jumps, psm errors, etc. > > That doesn't seem to help in my case, unfortunately. > > John > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver
In article <[EMAIL PROTECTED]>, jack <[EMAIL PROTECTED]> wrote: > > I have a Brand X KVM which also claims Intellimouse support. > I've found that if the switch is set to a machine when that > machine boots all is well, if I boot a machine with a different > one active on the KVM when I go to the one that was booted the > mouse jumps, psm errors, etc. That doesn't seem to help in my case, unfortunately. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KVM switch vs. FreeBSD psm driver
Today John Polstra wrote: > The KVM switch claims to have "Microsoft Intellimouse support and > emulation." However, in the troubleshooting section of its manual it > says you should make sure your driver is "either for a Standard PS/2 > or Microsoft-compatible PS/2" mouse." I have a Brand X KVM which also claims Intellimouse support. I've found that if the switch is set to a machine when that machine boots all is well, if I boot a machine with a different one active on the KVM when I go to the one that was booted the mouse jumps, psm errors, etc. -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -- A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
KVM switch vs. FreeBSD psm driver
I realize this is a well-known problem. Although there's much discussion about it in the mailing list archives, I couldn't find an actual solution. I've got a Belkin OmniView Pro 8-Port KVM switch which thinks it's much smarter than it really is. When I try to use the mouse through it with FreeBSD (-current from around Christmas, but I also had problems with -stable) it doesn't work right at all. It's got the same symptoms everybody else has reported: the cursor jumps around, and lots of "psmintr: out of sync" messages get logged. I found a posting in -hackers where Kazutaka YOKOTA <[EMAIL PROTECTED]> said: > You can force FreeBSD to use the mouse as the standard PS/2 mouse by > specifying the flags 0x200 to the psm driver. This way, the mouse > should always work. But, you cannot use the wheel. However, setting that flag hasn't helped me at all. Here are the relevant parts of "/var/run/dmesg.boot" from a verbose boot-up: psm0: current command byte:0047 psm0: flags 0x200 irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 255-, 2 buttons psm0: config:0200, flags:, packet size:3 psm0: syncmask:c0, syncbits:00 The mouse itself is a no-name 2-button PS/2 mouse. It doesn't have a wheel or anything else "extra". It works fine when connected directly to the computer. I have also tried various combinations of flags 0x100 (NOCHECKSYNC) and 0x400 (NORESET) without any luck. The useless mouse behavior happens with moused and with XFree86 + no moused. It happens whether I specify the protocol as "ps/2" or as "auto". The KVM switch claims to have "Microsoft Intellimouse support and emulation." However, in the troubleshooting section of its manual it says you should make sure your driver is "either for a Standard PS/2 or Microsoft-compatible PS/2" mouse." I don't care about wheels, and I'm even willing to get by with only 2 buttons. I don't mind hacking up the psm driver if necessary. I just want the mouse to work with this switch. Any suggestions? John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
