From: mjl <malet.jean-luc@laposte.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: porting sorcerer to udev
Date: Mon, 02 Feb 2004 22:52:55 +0000 [thread overview]
Message-ID: <401ED4C7.2050101@laposte.net> (raw)
In-Reply-To: <401633EA.4000102@laposte.net>
nobody can help? please I really need to find out what is going wrong....
mjl wrote:
> 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
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-02 22:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 9:48 porting sorcerer to udev MALET JL
2004-01-27 12:43 ` Ananth N Mavinakayanahalli
2004-01-27 16:33 ` Greg KH
2004-01-27 16:35 ` Greg KH
2004-01-27 23:58 ` mjl
2004-01-28 18:56 ` Greg KH
2004-01-28 22:22 ` mjl
2004-01-29 10:00 ` MALET JL
2004-01-30 9:41 ` MALET JL
2004-01-31 23:38 ` mjl
2004-02-02 22:52 ` mjl [this message]
2004-02-02 23:09 ` Greg KH
2004-02-03 9:10 ` MALET JL
2004-02-04 19:46 ` mjl
2004-02-04 20:20 ` mjl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=401ED4C7.2050101@laposte.net \
--to=malet.jean-luc@laposte.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).