RE: KVM switch support?

From: Dan MacMillan (flowers_at_users.sourceforge.net)
Date: 03/18/05

  • Next message: Elifarley Callado Coelho Cruz: "Problem compiling Rhythmbox"
    Date: Fri, 18 Mar 2005 10:47:50 -0700
    To: beowuff <beowuff@gmail.com>
    
    

    > -----Original Message-----
    > From: owner-freebsd-newbies@freebsd.org
    > [mailto:owner-freebsd-newbies@freebsd.org]On Behalf Of beowuff
    > Sent: March 12, 2005 19:16
    > To: freebsd-newbies@freebsd.org
    > Subject: KVM switch support?
    >
    >
    > On Fri, 11 Mar 2005 22:25:10 -0500, Andrew Batson
    > <abatson@twcny.rr.com> wrote:
    > > Hello Eric,
    > >
    > > > I'm trying to install 5.3-STABLE on an HP Pavilion box I have
    > > > laying around. For some reason the installer is not handling
    > > > the output from my KVM switch. The model is IOGear
    > > > MiniView(tm) II USB KVM Model # GCS124U.
    > >
    > > I have a IOGear MiniView KVM too and when I tired to
    > install FreeBSD
    > > 5.3, I had the same problem. After I did a little googleing, I found the
    > > answer. When you first boot with FreeBSD 5.3 bootable CD-ROM,
    > wait for the
    > > FreeBSD boot menu to appear and choose option number 6. Then at the OK
    > > prompt, type the following and hit the enter key.
    > >
    > > set hint.atkbd.0.flags="0x1"
    > >
    > > Note the Quote makes are needed. At the next OK prompt, type
    > >
    > > boot
    > >
    > > And the system should boot to sysinstall menu where you will
    > find the USB
    > > keyboard working. At least that is what work for me.
    > >
    > > Hope this helps,
    > > Andrew
    >
    > Any idea if this will be fixed in the next release? I too have a usb
    > keyboard. I've been avoiding 5.3 for this usb bug. Not having this
    > problem with any other OS.
    >

    I doubt any development resources are being consumed to change this
    behaviour, as it can be made to work quite satisfactorily as things stand
    now. I doubt it can even be considered a bug. If you don't want to enter
    the hint each time you boot, just put it in your device.hints file.

    --
    Danny
    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"
    

  • Next message: Elifarley Callado Coelho Cruz: "Problem compiling Rhythmbox"

    Relevant Pages

    • Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
      ... 8.0-RELEASE-i386-memstick fixit prompt up. ... It boots fine, and sysinstall comes up, but I continually get "No USB ... has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit ... I was being very careful, as I wanted to install 8.0 on ad0s4, hopefully ...
      (freebsd-questions)
    • Re: Booting from usb hard disk
      ... The machines that it doesn't work on, boot the ... prompt, which is immediately followed by the message saying that da0 ... I have been using tunefslabeled partitions on my usb hard disk ...
      (freebsd-current)
    • Re: Booting from usb hard disk
      ... The machines that it doesn't work on, boot the ... prompt, which is immediately followed by the message saying that da0 ... I have been using tunefslabeled partitions on my usb hard disk ...
      (freebsd-current)
    • Re: [patch, -git] media/video/sound build fix, TEA5761/TEA5767
      ... A webcam would not depends on USB, ... auto-selects or prompt to the users. ... The auto-select feature, without prompting could be very helpful to allow testing kconfig items, since, instead of running all randomconfig's, subsystem maintainers can use scripts that will do something like allnoconfig, and then select just the symbols requested by each driver. ...
      (Linux-Kernel)

  • Quantcast