Udev with kudzu disabled?

[dragoran]

dragoran schrieb:

> Jim Cornette schrieb:
>
>> dragoran wrote:
>>
>>> Paul Nasrat schrieb:
>>>
>>>> On Sat, Aug 28, 2004 at 09:41:18AM +0200, dragoran wrote:
>>>>  
>>>>
>>>>> Does udev works when kudzu is disabled?
>>>>>   
>>>>
>>>>
>>>>
>>>>
>>>>  
>>>>
>>>>> I am asking this because i have to disable kudzu to get my network 
>>>>> car (3com) working.
>>>>>   
>>>>
>>>>
>>>>
>>>>
>>>> I'd guess this is completely unrelated to udev:
>>>>
>>>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119965
>>>>
>>>> Paul
>>>>
>>>>
>>>>  
>>>>
>>> I now this but i want to test fc3 test2 when it comes out. in fc2 
>>> (which I am using now) i have disabled kudzu to get it working. Now 
>>> I want to know if this could cause problems when using udev (because 
>>> it needs to probe all hardware at boot time)
>>>
>>>
>> I had the problem ever since the RHL beta phase 1, which turned into 
>> Fedora Core. I ditched the boomerang card and installed a 3Com 
>> Corporation 3c905C-TX/TX-M [Tornado] (rev 74) card instead. I had a 
>> REV A for the Boomerang card. I believe the newer version is much 
>> like the boomerang, except it is a REV B.
>>
>> rpm -q --whatrequires udev
>> hal-0.2.97.cvs20040827-2
>> hal-0.2.97.cvs20040827-3
>>
>> rpm -q --whatrequires hal
>> kudzu-1.1.81-1
>> kudzu-1.1.82-1
>>
>> rpm -q --whatrequires kudzu
>> hwbrowser-0.15-3
>> system-config-mouse-1.2.7-1
>> pcmcia-cs-3.2.7-1.7
>> system-config-display-1.0.18-2
>> system-config-network-tui-1.3.19-1
>>
>> If I'm reading the trail correctly. Hal requires udev, which requires 
>> kudzu.
>> Out of curiousity, does hotplug work for you now?
>> Also, checking for udev with rpm. I got multiple packages for udev.
>>
>> rpm -q udev
>> udev-030-7
>> udev-030-10
>> [jim at cornette-fc3 ~]$ rpm -e --justdb udev-030-7
>> error: package udev-030-7 is not installed
>> [jim at cornette-fc3 ~]$ rpm -q udev
>> udev-030-10
>> [jim at cornette-fc3 ~]$ rpm -q --verify udev
>> nothing came back from the verify. I hope things are correct now.
>>
>> I'd say get another NIC.
>>
>> Jim
>>
>>
> I will try with my onboard via NIC,
>
>
the via NIC seems to work fine....