Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: brianjester@gmail.com Newsgroups: comp.sys.sun.admin Subject: Solaris 10 Unable to use "Dumb" KVM (Avocent SwitchView USB 4-Port), Works Under Solaris 8 Date: Tue, 28 Feb 2012 09:27:45 -0800 (PST) Organization: http://groups.google.com Lines: 26 Message-ID: <197456.6.1330450065657.JavaMail.geo-discussion-forums@pbcrt4> NNTP-Posting-Host: 128.49.66.118 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1330450163 11614 127.0.0.1 (28 Feb 2012 17:29:23 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 28 Feb 2012 17:29:23 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=128.49.66.118; posting-account=XAB8CwoAAAD2D48E_TY-CdPxtzjEelb9 User-Agent: G2/1.0 X-Google-Web-Client: true X-Received-Bytes: 2029 Xref: x330-a1.tempe.blueboxinc.net comp.sys.sun.admin:136 I have two Sun Blade 150 clients, one loaded with Solaris 8, the other Sola= ris 10. I noticed that if I put the clients on a "dumb" KVM (Avocent SwitchView USB= 4-Port), that the Solaris 8 machine works when switching between KVM chann= els (the /var/adm/messages log shows 20+ usb related events from kernel and= usba) The Solaris 10 machine will not reconnect to the KVM, and I have to SSH int= o the box and reboot it. What's going on with Solaris 10? Why is it not as robust as Solaris 8 when= the USB keyboard/mouse is switched on a "dumb" KVM? Anyone had similar experiences? When I SSH into the misbehaving Solaris 10 machine and do a "cfgadm", I can= see that the USB devices have disconnected, but they are never able to rec= onnect, no matter what combination of cfgadm commands I try. Only a reboot= of Solaris 10 fixes the problem. A sub-optimal solution. And yes, newer "smart" KVM's work (IOGear GCS1734), just not the Avocent. Any help is appreciated. Brian