Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 79706 - kudzu 0.99.69 misconfigures internal pnpisa modem
kudzu 0.99.69 misconfigures internal pnpisa modem
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-12-15 18:09 EST by Charles A Crayne
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-23 15:54:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output from /proc/isapnp (854 bytes, text/plain)
2002-12-16 20:49 EST, Charles A Crayne
no flags Details

  None (edit)
Description Charles A Crayne 2002-12-15 18:09:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
Kudzu 0.99.69 correctly configures US Robotics External modem, but configures
the internal version of the same modem as:
class: UNSPEC
driver: unknown

and does not assign a device.

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

How reproducible:

Steps to Reproduce:
1.Run kudzu with isa internal modem installed

Actual Results:  Modem incorrectly identified.

Additional info: Worked correctly in Redhat 7.1
Comment 1 Bill Nottingham 2002-12-16 19:25:02 EST
What's your /proc/isapnp look like?
Comment 2 Charles A Crayne 2002-12-16 20:49:36 EST
Created attachment 88772 [details]
output from /proc/isapnp
Comment 3 Bill Nottingham 2005-09-23 15:54:24 EDT
Apologies for the slow response. Since this bug was filed, this code has changed
significantly, not the least in how ISAPnP is handled in the kernel.

Please attempt to reproduce on a current release, such as Fedora Core 4, and
open a new bug if it fails there as well.

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