Bug 76762

Summary:	Initializing USB HID interface: when no HID interface
Product:	[Retired] Red Hat Linux	Reporter:	Greg Shaw <greg>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:	Brock Organ <borgan>
Severity:	low	Docs Contact:
Priority:	medium
Version:	8.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-10-25 23:32:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Greg Shaw 2002-10-25 23:32:03 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
System has usb but no HID devices (keyboard/mouse).
/etc/rc.d/rc.sysinit _always_ runs the lines noted below to install
HID devices. These should be conditional on Cls=03 from
/proc/bus/usb/devices. This will detect if there are any HID devices attached.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.No usb keyboard or mouse
2.reboot
3.system displays that initialisation of usb keyboard/mouse FAILED
	

Expected Results:  Should not attempt to initialise devices that are not present and
therefore shoul ddisplay FAILED for devices.

Additional info:

replace /etc/rc.d/rc.sysint lines:
    action $"Initializing USB HID interface: " modprobe hid 2> /dev/null
    action $"Initializing USB keyboard: " modprobe keybdev
    action $"Initializing USB mouse: " modprobe mousedev
with the following:
    if grep -e "^I.*Cls=03" /proc/bus/usb/devices 2>/dev/null ; then
        action $"Initializing USB HID interface: " modprobe hid 2> /dev/null
        action $"Initializing USB keyboard: " modprobe keybdev
        action $"Initializing USB mouse: " modprobe mousedev
    fi

Comment 1 Bill Nottingham 2002-10-26 05:21:38 UTC

This is intentional, to have the device always present even between plug/unplug
events. (needed for X, among other things)