Greg KH wrote:

>On Wed, Jan 28, 2004 at 12:58:33AM +0100, mjl wrote:
>  
>
>>>Build udev with DEBUG=true and USE_LOG=true and show us what the debug
>>>logs say when you run udev.  
>>>
>>>
>>>      
>>>
>>the only things that seems to be usefull is "udev_hotplug : no devpath?"
>>looking into the test scripts I saw that the script set DEVPATH and then 
>>call udev.... and this way work so it seems that hotplug don't set DEVPATH
>>    
>>
>
>The kernel sets up DEVPATH when it calls hotplug.  You are using a 2.6
>kernel for your device, right?  :)
>  
>
of course :)
today investigations :
1)pci.rc don't work for me, (log reports no modules found for device XXX 
when running 'pci.rc start' and this for each onboard pci devices ) with 
this patch this works smoothly :) (see included patch)
2)I palyed with udev on a 2.6.1 the logs are included into backup.tar.gz 
the gameplay included :
-> using testscripts,
-> activating DEBUG into hotplug (see event log) the DEVPATH is set.... 
so normaly udev should work (since it works with tests)
->in debug log you'll fing udev debug output, there is two parts : the 
1rst (tty) is when I palyed with test.tty (question : is it normal that 
udev make about 1s for each tty entries?)
the 2nd is when I played with the new pci.rc

in all case no udev entries are created.... it looks like udev was never 
called

jlm@Sorcerer:~/devel$ ls -l /etc/hotplug.d/default/
total 5
-rwxr-xr-x    1 root     root         2852 2004-01-28 21:34 default.hotplug
lrwxrwxrwx    1 root     root           10 2004-01-28 01:08 udev.hotplug 
-> /sbin/udev

thanks