Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 16089 - still usb problems in initscripts
still usb problems in initscripts
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Bill Nottingham
Winston gold
Depends On:
  Show dependency treegraph
Reported: 2000-08-13 00:39 EDT by Gene Czarcinski
Modified: 2014-03-16 22:15 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-14 11:31:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2000-08-13 00:39:36 EDT
I am openint this as new since the base problem (15518) was not beta-only
(it was from the open beta).

This is also related to closed problems bug 15464 and bug 13605.

1.  USB support in intiscripts is still broken.

2. I am still getting the error messages reported in bug 13605.

3. Using NOUSB appended to the kernel parameters still has no effect (bug

4. It is now worse -- if I append NOUSB, I get a "FAILED" durring the boot
process for the usb startup.

Comment 1 Glen Foster 2000-08-13 16:15:44 EDT
This defect is considered MUST-FIX for Winston Gold-release
Comment 2 Trond Eivind Glomsrxd 2000-08-13 16:29:03 EDT
Did you do an upgrade from previous betas? kudzu should not add new controllers 
without IRQs, but won't remove them either.
Comment 3 Gene Czarcinski 2000-08-13 16:39:55 EDT
Nope ... fresh install.  This is highly repeatable.
Comment 4 Bill Nottingham 2000-08-14 01:02:05 EDT
In what way is it broken (how does it fail)?

nousb works fine here; did you actually specify
it in all caps?
Comment 5 Bill Nottingham 2000-08-14 01:04:03 EDT
(allcaps 'nousb' won't work in the current package, but has
been fixed in CVS.)
Comment 6 Gene Czarcinski 2000-08-14 03:42:26 EDT
Specified in all lower case.

I have no idea how it failed.  The "message" during bootup is "FAILED" after
saying Starting USB and the silly insmod error messages.
Comment 7 Bill Nottingham 2000-08-14 10:47:47 EDT
What initscripts do you have installed?
Comment 8 Gene Czarcinski 2000-08-14 11:26:25 EDT
I have initscripts-5.44-1 from rc1.

Bill -- important point:  I have some of the usb stuff disabled in the BIOS so
that I could "free up" an IRQ.  This may be "causing" the error messages.  On
other systems with USB such as the one I am on now, they also have USB but no
error messages and no problems.

BTW, if you have a newer version of initscripts you want me to test, give a

Comment 9 Bill Nottingham 2000-08-14 11:31:32 EDT
How are you doing 'nousb'?

Also, if you remove the usb-controller alias from
/etc/modules.conf, and then reboot (without 'nousb')
does it proceed normally?
Comment 10 Gene Czarcinski 2000-08-15 04:12:16 EDT
Removing "alias usc-controller ..." from /etc/modules works -- no error

More to the point, I am marking this bug resolved.  My brain must not have been
engaged -- I had NOUSB rather than nousb specified in a lilo append.  That,
coupled with the fact that I have a "partially" bios-disable usb resulted in the
error messages.

Thanks for the help and sorry for time lost.

On other systems I have with usb fully enabled, everything seems to work fine.


Note You need to log in before you can comment on or make changes to this bug.