Kudzu Segmentation Fault

[Madison Kelly]

Hi everyone,

   Yesterday I needed a distraction so I upgraded (hardware) my home 
machine from a Pentium III 850 (based on the Via133 chipset) to an AMD 
Athlon 1700+ (1.1GHz with the KT266 chipset, iirc). I am running Fedora 
and when I rebooted after upgrading 'kudzu' reported a "Segmentation 
Fault" on boot. I didn't worry about it until I downloaded the latest 
kernel for the athlon.

   A bit of an oddity, when I tried to install the kernel via 'rpm -Uvh 
<kernel>' is kept failing saying that the kernel was intended for an 
Athlon CPU. I checked 'dmesg' and sure enough it reported being on an 
athlon. '--force' didn't work but then I read about the '--noarch' 
switch and voila! Okay, so I am under the new kernel but it still seg 
faults when kudzu runs. I tried deleting '/etc/sysconfig/hwconf' but 
that didn't help. Then I tried reinstalling, then updating, rebuilding 
the latest version from .src.rpm and finally I even tried the very 
latest CVS and everyone of them seg faults.

   I have also tried removing -all- non essential hardware including 
disabling everything in the BIOS and that too didn't help. I tried 
checking '/var/log/messages|dmesg|ksyms.0' but non of them had any 
errors about kudzu. Does anyone have a suggestion for me? Does anyone 
know how to make kudzu a little more verbose or where it logs errors to? 
Failing all this, is there another hardware detection tool I can drop in 
to replace kudzu?

   Thanks everyone!

Madison

ps - I tried 'kudzu --safe', no luck.

--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml