Bug 112699 - External modem disappears on first reboot
External modem disappears on first reboot
Product: Fedora
Classification: Fedora
Component: kudzu (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-12-28 20:41 EST by Ken Taylor
Modified: 2014-03-16 22:41 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-20 13:33:41 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 Ken Taylor 2003-12-28 20:41:40 EST
Description of problem: Install works OK including external US
Robotics 56k Sportster Faxmodem.  After initial reboot, kudzu tells me
"Removed Hardware" - "USR|2082 US Robotics 56K FAX EXT"  Modem is
there and powered on.

Version-Release number of selected component (if applicable): 1.1.36
Hardware Discovery Utility

How reproducible: every time (4 separate installs to date)

Steps to Reproduce:
1.Perform basic install (Personal Desktop is enough).  Problem is seen
on first reboot.

Actual results:

Expected results:

Additional info: Modem is on Com1 on an MSI motherboard.  Works OK
with Win 2k.  Works OK with Redhat Linux 9 (Hardware Discovery Utility
v. 0.99.99)
Comment 1 Jason Booker 2004-06-01 22:54:08 EDT
I also get this problem:

I installed Fedora Core 2 test3 on my machine, it picked up the modem
during install then during the reboot Removes the modem configuration.

I have a different brand external modem, it was also plugged in and
switched on during the whole process.
Modem is also on Com1, on an ASUS P4S533-MX motherboard.

This worked fine with RedHat 9 and still works ok with Win2k Pro.
Comment 2 Bill Nottingham 2005-04-28 14:06:00 EDT
Does this persist on FC3 and later?
Comment 3 Bill Nottingham 2005-09-20 13:33:41 EDT
Closing, no response.

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