Re: FC2 USB keyyboard and mouse via a KVM switch support

From: Kevin Wang (rightsock_at_gmail.com)
Date: 08/11/04

Next message: Robert P. J. Day: "Re: find in conjuction with grep"

Previous message: Kevin Wang: "Re: FC2 Ethernet and Wireless settings"
In reply to: Sterling Lindsey: "FC2 USB keyyboard and mouse via a KVM switch support"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Wed, 11 Aug 2004 12:28:16 -0700
To: For users of Fedora Core releases <fedora-list@redhat.com>

Only thing I might suggest is that you make sure that the usb HID
modules are forced loaded at boot time. If they aren't insmod'ed, X
won't see them, even if they're plugged in after the fact.

I have in my /etc/rc.d/rc.local:

insmod input hid mousedev

IMPORTANT: this is rh8.0. it may vary for FC2.

- Kevin

----- Original Message -----
From: Sterling Lindsey <zoom61@swbell.net>
Date: Wed, 11 Aug 2004 07:10:06 -0700 (PDT)
Subject: FC2 USB keyyboard and mouse via a KVM switch support
To: Fedora List <fedora-list@redhat.com>

I have a small network that includes two FC servers and one XP client.
The two servers, FC1 and FC2, are absolutely identicaI in hardware
and BIOS except that FC1 has a second NIC that isn't needed in FC2. I
am trying to use a USB KVM switch to minimize the amount of hardware
required to implement consoles for the two servers. To avoid a long
description here is my block diagram:



My current situation is that ths console of FC1 works perfectly while
that of FC2 does not.

FC1 runs the 2.4.22-1.2188 kernel. I can select FC1 on the KVM switch
and then boot FC1 and the console always comes up working. I can
switch the KVM switch from FC1 to FC2 then back to FC1 and the console
works fine. Anything I do works fine for FC1.

This is not the case for FC2. With FC2 selected on the KVM switch
it's no telling what will happen to the console when FC2 is booted.
It usually takes around eight boot cycles to get the keyboard and
mouse both to work. Sometimes the keyboard works but the mouse does
not. Sometimes the mouse works but not the keyboard. Sometimes
neither works. However when I finally do get the keyboard and mouse
to work I am then able to switch between FC1 and FC2 with the KVM
switch and continue to have the console for each.

I run Cygwin on my XP client. Using Cygwin I can always login to
either FC1 or FC2 with no problem. It doesn't matter what the current
condition of FC2's console is I can always get access via Cygwin

At times kudzu wants to run at boot time. This is usually of no help
because the keyboard is usually dead so I am unable to enable it.

If there is any way to configure FC2 such that following a boot cycle
its console would always work I would appreciate knowing what it is.

What follows are listings from the FC2 Hardware Browser:

With keyboard detected and mouse detected
ROM Drives Selected Device: Samsung CDRW/DVD SM-352B

Manufacturer: Samsung

Driver: none or built-in

Device: /dev/scd0

Floppy Disks Selected Device: MITSUMI0 MITSUMI USB FDDD

Manufacturer: MITSUMI0

Driver: usb-storage

Hard Drives Selected Device: /dev/hda (Model: ST3120026A)

Selected Device: /dev/sda (Model: IC25N020 ATCS04-0)

Keyboards Selected Device: ATE0 4Ports KVM C

Manufacturer: ATE0

Driver: keybdev

Selected Device: USB MINI-Keyboard

Manufacturer:

Driver: keybdev

Network devices Selected Device: VT6102 [Rhine-II]

Manufacturer: VIA Technologies

Driver: via-rhine

Device: /dev/eth0

Pointing devices Selected Device: ATE0 4Ports KVM C

Manufacturer: ATE0

Driver: genericwheelusb

Device: /dev/input/mice

Selected Device: Microsoft Corp. Wheel Mouse Optical

Manufacturer: Microsoft

Driver: grnericwheelusb

Device: /dev/input/mice

Sound cards Selected Device: VT8233/A/VT8235/8237 AC97 Audio Controller

Manufacturer: VIA Technologies

Driver: snd-via82xx

System Devices Selected Device: Linux 2.6.7-1.494.2.2 ehci_hcd EHCI
Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 ehci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: NEC Corp. HighSpeed Hub

Manufacturer: NEC Corporation

Driver: unknown

Selected Device: unknown

Manufacturer: Unknown

Driver: unknown

USB devices Selected Device: USB 2.0

Manufacturer: VIA Technologies

Driver: ehci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

With keyboard detected but mouse not detected

CD-ROM Drives Selected Device: Samsung CDRW/DVD SM-352B

Manufacturer: Samsung

Driver: none or built-in

Device: /dev/scd0

Floppy Disks Selected Device: MITSUMI0 MITSUMI USB FDDD

Manufacturer: MITSUMI0

Driver: usb-storage

Hard Drives Selected Device: /dev/hda (Model: ST3120026A)

Selected Device: /dev/sda (Model: IC25N020 ATCS04-0)

Keyboards Selected Device: USB MINI-Keyboard

Manufacturer:

Driver: keybdev

Network devices Selected Device: VT6102 [Rhine-II]

Manufacturer: VIA Technologies

Driver: via-rhine

Device: /dev/eth0

Pointing devices Selected Device: Microsoft Corp. Wheel Mouse Optical

Manufacturer: Microsoft

Driver: grnericwheelusb

Device: /dev/input/mice

Sound cards Selected Device: VT8233/A/VT8235/8237 AC97 Audio Controller

Manufacturer: VIA Technologies

Driver: snd-via82xx

System Devices Selected Device: Linux 2.6.7-1.494.2.2 ehci_hcd EHCI
Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 ehci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: NEC Corp. HighSpeed Hub

Manufacturer: NEC Corporation

Driver: unknown

Selected Device: unknown

Manufacturer: Unknown

Driver: unknown

USB devices Selected Device: USB 2.0

Manufacturer: VIA Technologies

Driver: ehci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

With keyboard not detected and mouse not detected

CD-ROM Drives Selected Device: Samsung CDRW/DVD SM-352B

Manufacturer: Samsung

Driver: none or built-in

Device: /dev/scd0

Floppy Disks Selected Device: MITSUMI0 MITSUMI USB FDDD

Manufacturer: MITSUMI0

Driver: usb-storage

Hard Drives Selected Device: /dev/hda (Model: ST3120026A)

Selected Device: /dev/sda (Model: IC25N020 ATCS04-0)

Keyboards Selected Device: ATE0 4Ports KVM C

Manufacturer: ATE0

Driver: keybdev

Selected Device: USB MINI-Keyboard

Manufacturer:

Driver: keybdev

Network devices Selected Device: VT6102 [Rhine-II]

Manufacturer: VIA Technologies

Driver: via-rhine

Device: /dev/eth0

Pointing devices Selected Device: ATE0 4Ports KVM C

Manufacturer: ATE0

Driver: genericwheelusb

Device: /dev/input/mice

Selected Device: Microsoft Corp. Wheel Mouse Optical

Manufacturer: Microsoft

Driver: grnericwheelusb

Device: /dev/input/mice

Sound cards Selected Device: VT8233/A/VT8235/8237 AC97 Audio Controller

Manufacturer: VIA Technologies

Driver: snd-via82xx

System Devices Selected Device: Linux 2.6.7-1.494.2.2 ehci_hcd EHCI
Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 ehci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: Linux 2.6.7-1.494.2.2 uhci_hcd UHCI Host Controller

Manufacturer: Linux 2.6.7-1.494.2.2 uhci_hcd

Driver: unknown

Selected Device: NEC Corp. HighSpeed Hub

Manufacturer: NEC Corporation

Driver: unknown

Selected Device: unknown

Manufacturer: Unknown

Driver: unknown

USB devices Selected Device: USB 2.0

Manufacturer: VIA Technologies

Driver: ehci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

Selected Device: VT82xxxxx UHCI USB 1.1 Controller

Manufacturer: VIA Technologies

Driver: uhci-hcd

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

Next message: Robert P. J. Day: "Re: find in conjuction with grep"

Previous message: Kevin Wang: "Re: FC2 Ethernet and Wireless settings"
In reply to: Sterling Lindsey: "FC2 USB keyyboard and mouse via a KVM switch support"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

FC2 USB keyyboard and mouse via a KVM switch support
... Manufacturer: Samsung ... Driver: none or built-in ... Floppy Disks Selected Device: MITSUMI0 MITSUMI USB FDDD ... Driver: unknown ...
(Fedora)
Re: Divers for USB devices, audio and other
... with audio and other devices plugged into USB. ... laugh when you ask about a driver. ... Maybe you should purchase from a manufacturer who supplies working ... I could do PCMCIA direct to WiFi, ...
(alt.os.linux.suse)
Re: wc10 webcam
... but there /might/ be a driver for the webcam chip ... OK, so plug it in to your usb port, and show us the USB registration ... You can then do a quick google search using the manufacturer # and ...
(comp.os.linux.hardware)
RE: Floppy not shown
... Try visiting the manufacturer for ... Have you try a different USB device to confirm that your ... > and upon rebooting the pc would see and the light goes on momentarily it but ... The driver may be corrupted or missing. ...
(microsoft.public.windowsxp.general)
Re: InstallHinfSection
... How big of a check does it take to WHQ a driver. ... According to the USB interface's manufacturer, ... some Win98 problem. ... Maybe we could work with the manufacturer to get it WHQ'd for XP. ...
(microsoft.public.development.device.drivers)