Re: KVM USB

Brooks,

What I actually did and it seems to work was that I changed dev.conf  
this way: (I changed the device name to "ukbd1" instead of "ukbd0" 
because when my keyboard remounts itself after being unplugged its 
called "ukbd1". Do you think this may cause some other issues Im not 
aware of yet? Here is my modified dev.conf snippet.


# When a USB keyboard arrives, attach it as the console keyboard
attach 100 {
         device-name "ukbd1";
         action "test -c /dev/kbd1 && kbdcontrol -k /dev/kbd1 < 
/dev/console";
};
detach 100 {
         device-name "ukbd1";
         action "kbdcontrol -k /dev/kbd0 < /dev/console";
};


On Mar 9, 2005, at 2:40 PM, Brooks Davis wrote:

> On Wed, Mar 09, 2005 at 02:10:49PM -0500, Alex Welycz wrote:
>> All,
>>
>> I'm using FreeBSD 5.3 and I've run into a bit of a problem. I am using
>> a KVM switch that does not keep a live connection to the computer when
>> switching between computers ie. the computers show that the usb
>> keyboard/mouse are unplugged when you switch between them. My problem
>> occurs when the i switch from my Windows box back to my FreeBSD box.
>> The USB deamon on the BSD box shows that the keyboard is recognized
>> and loads it but when i try to use the keyboard nothing comes up. The
>> USB keyboard does work when I reboot the BSD box and dont switch
>> between computers. Now how I get the USB keyboard to work when i
>> switch between computers I have to run this script.
>>
>> sleep 15
>> kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null
>>
>> Apparently when I reboot the box everything works fine, the USB
>> keyboard is accessed as
>>
>> kbd0 -> ukbd0
>>
>> but when I switch between boxes and switch back the keyboard doesnt
>> get mounted at
>>
>> kbd0 -> ukbd0 but instead is mounted at kbd1 -> ukbd1.
>>
>> So my question is how do I get FreeBSD to always mount the keyboard as
>> kbd0 -> ukbd0 and not kbd1 -> ukbd1
>>
>> Because upon bootup my kbdcontrol is called as:
>>
>>  kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null and cannot be called
>> wih kbd1 because at bootup that device does not exist, and also that
>> device disappears when I swicth to my other computer so kbdcontrol
>> sets itself back to kbd0.
>
> This is caused by a bug in /etc/devd.conf that I fixed a week ago in 5.
> Just change the line to refer to ukbd0 instead of bogusly refering to
> kbd1.  The problem was caused by crappy examples in the manpage making
> me think you had to use the generic /dev/kbd# device not the specific
> /dev/ukdb# device with kbdcontrol.
>
> -- Brooks
>
> -- 
> Any statement of the form "X is the one, true Y" is FALSE.
> PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4