Red Hat Bugzilla – Bug 223055
Fails to install on a dual-CPU Pentium II system
Last modified: 2008-05-06 13:25:45 EDT
Description of problem:
I am attempting to install Fedora Core 6 on an old dual Pentium II system. This
system was previously running FC2 with no problems.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a set of FC6 install CDs (media check successfully done on another
2. Boot from install CD 1.
3. Choose "re-install" rather than upgrade; choose "delete all partitions and
use default partition layout"
4. Accept default partition layout.
5. Accept default package installation (no customization)
6. Choose DHCP network configuration. De-select "activate on boot" for eth0,
and select "activate on boot" for eth1. (Only eth1 has a cable installed.)
7. Proceed with install.
While installing the 7th package (glibc-common) the install fails with the
rpmdb: DB_LOCK->lock_put lock is no longer valid
I was hoping for a successful install!
How much mmeory does the machine have?
The machine has 128 meg (i.e. 131072K)
Other details about the machine:
ASUS P2L97-DS Dual Pentium Motherboard
CPU 0: 266 mHz Intel Pentium II (Klamath) Stepping 04
CPU 1: same
Master hard drive on primary IDE controller:
Landing Zone 29764
Slave on primary IDE controller: None
Master on secondary IDE controller: ATAPI CD-ROM
Slave on secondary IDE controller: None
That's all I know about this box. It's a rackmount server I picked up on E-Bay
a few years ago (and it was ancient even then). I put Fedora Core 2 on it when
I bought it & it's been running like a champ. It's been down for a few months,
and I wanted to put it back into service with an OS that is a bit more
up-to-date than FC2.
requested by Jams Antill
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.