Subject: port-i386/17294: 1.6 BETA install kernel doesn't listen to USB keyboard on AMD EasyNow PC
To: None <>
From: Erik E. Fair <>
List: netbsd-bugs
Date: 06/16/2002 14:40:42
>Number:         17294
>Category:       port-i386
>Synopsis:       1.6 BETA install kernel doesn't listen to USB keyboard on AMD EasyNow PC
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jun 16 14:41:00 PDT 2002
>Originator:     Erik E. Fair
>Release:        NetBSD 1.6 BETA
International Organization of Internet Clock Watchers
Architecture: i386
Machine: i386
	The install kernel from "boot-big.fs" doesn't listen to
	the USB keyboard on the "AMD EasyNow! PC" so it is impossible
	to get beyond the sysinst menu.

	This system is based around SiS chips and the AMD K6-2.
	The USB controller is a SiS OHCI.

	FreeBSD 4.3, 4.5 and 4.6 all handle this USB keyboard/controller
	correctly (i.e. it works) but their driver for the SiS 900
	10/100 Ethernet controller is hosed, which is why I'm not
	using that.

	Grabbed the 20020613 i386 build from

	made CD-ROM for booting with boot-big.fs and mkisofs

	attempted to boot AMD EasyNow! PC (450 MHz K6-2 "legacy free" PC)

	boot succeeds, devices recognized, but when sysinst comes up,
	no response from any keyboard sequence.

	unplugging and replugging the keyboard elicits kernel USB
	autoconfig messages, but has no effect on keyboard useability.

	attempting to use another USB keyboard gives same result:
	kernel autoconfig recognized, but no response to keypresses.

	the initial autoconfig flashes by too quickly for me to
	record what's going on, and this "legacy free" PC has no
	standard or parallel serial ports - just USB.

	I suspect it might be that the integrated system chips
	include a standard PC Keyboard controller, which despite
	having no keyboard on it (probably not connected to anything),
	is being given some precedence by the NetBSD kernel as console
	or we still have bugs in our USB controller/keyboard drivers.