Description of problem:
> I got exactly the same kudzu problems in fresh Fedora Core. All reboots
> after first kudzu prompts me if I want to remove realtek 8139 and then
> add exactly the same device. If I do not ignore and let it add/remove
> there is no network and questions will still show up next reboot.
OK, please file a bug, attach lspci output, /etc/sysconfig/hwconf
when booted in single user mode, and the output of kudzu -p once
the system is booted.
Version-Release number of selected component (if applicable):
Created attachment 95045 [details]
lspci -vn output
Created attachment 95046 [details]
kudzu -p output
Created attachment 95047 [details]
hwconf captured in single user mode
Same in fedora core 2 fresh install.
Anaconda tries to configure network cards with kudzu at post installation, but
fails because network interface is active at that time. I had similiar situation
with my 8139 network card.
See comments #11, #12 and #13 from the bug:
Please try the kudzu-18.104.22.168-1 packages at:
These may resolve some of your issues.
Behavior is present in RHEL 3 as well. (And no updated kudzu package
frsh install FC2 test1 and updates from rawhide up to test2 seems to
Marking resolved in rawhide.
Michael Ellis - an updated kudzu package for RHEL 3 is in the U2 beta
Is there a date (or good estimate) for when RHEL3 U2 will officially
be released? We're going to redo our PXE-based installs, and if U2
will fix the problem and is out soon, we'll just wait for that rather
than redoing based on U1.
I don't have the date off the top of my head, but there are beta
packages and ISOs in RHN now that you can check.