Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 05 Jan 2018 20:10:07 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 224940] PPC64: No input on VNC console due to xhci driver not present as built-in module
Message-ID:  <bug-224940-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224940

            Bug ID: 224940
           Summary: PPC64: No input on VNC console due to xhci driver not
                    present as built-in module
           Product: Base System
           Version: CURRENT
          Hardware: powerpc
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: gromero@br.ibm.com

QEMU for PowerPC usually provides the following devices that will be used o=
n a
VNC console:

Populating /vdevice methods
Populating /vdevice/l-lan@1000
Populating /vdevice/v-scsi@2000
       SCSI: Looking for devices
          8001000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      2.5+"
          8000000000000000 DISK     : "QEMU     QEMU HARDDISK    2.5+"
Populating /vdevice/vty@30000000
Populating /vdevice/nvram@71000000
Populating /pci@800000020000000
                     00 0800 (B) : 1b36 0001    pci*
                     00 1000 (D) : 1b36 000d    serial bus [ usb-xhci ]
                     00 1800 (D) : 1234 1111    qemu vga
                     00 2000 (D) : 1af4 1002    unknown-legacy-device*
Installing QEMU fb



Scanning USB=20
  XHCI: Initializing
    USB Keyboard=20
    USB mouse=20

If xhci driver is not available as a built-in module login console on VNC w=
ill
end with no input devices making it impossible to login through the VNC
console.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224940-8>