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 4067 - I have one e-mail with this bug report handy:
I have one e-mail with this bug report handy:
Product: Red Hat Linux
Classification: Retired
Component: isapnptools (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-07-16 02:57 EDT by Milan Kerslager
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-07-20 17:31:28 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 Milan Kerslager 1999-07-16 02:57:31 EDT
There is a lot of error reports for this package. The
temprary solution that works is downgrade to isapnptools
from RH5.2. I never tryed compile newer version for myself.
Comment 1 Bill Nottingham 1999-07-16 10:18:59 EDT
Do you have any specific examples?

In any case, the isapnptools in Raw Hide contains a couple
of fixes for IO port handling.
Comment 2 Milan Kerslager 1999-07-19 14:55:59 EDT
SCSI driver sym53c416:
started at the first time:

Setting up ISA PNP devices
Board 1 has Identity 62 ff ff ff ff 61 41 9 4d: SLI4161 Serial No -1
[checksum 62]
/etc/isapmp.conf:46 -- Fatal - resource conflict allocating IRQ10
(see /proc/interrupts)
/etc/isapnp.conf:46 -- Fatal - Error occurred executing request 'IRQ
10' --- further action aborted

The second time (manual run) is OK.

As this is not my card I asked its owner to try RawHide version and I
am waiting for his reply now.
Comment 3 Milan Kerslager 1999-07-20 13:22:59 EDT
I have two OK reports now.
Newer version from RawHide seems to fully solve the problem above.
Comment 4 Bill Nottingham 1999-07-20 17:31:59 EDT
That's good - marking bug fixed in next release.

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