search for: udevsend

...log > as to why it might be doing this? That is a bit strange. > Our driver triggers the event correctly, as you can see from > the first line, but udev then simply doesn''t pass it on. Actually there are some messages in syslog concerning udev: Dec 6 08:41:51 davetho-intel udevsend[5693]: main: unable to connect to event daemon, try to call udev directly Dec 6 08:41:51 davetho-intel udevsend[5696]: main: unable to connect to event daemon, try to call udev directly Dec 6 08:41:51 davetho-intel udevsend[5699]: main: unable to connect to event daemon, try to call udev directly...

...d the xen-hotplug.log for the vbd failure case. > It would be good to confirm whether the hotplug events are even > getting through, so that we don''t end up looking in > completely the wrong place. Start with "cat > /proc/sys/kernel/hotplug". If that''s udevsend and udevinfo > -V reports greater than 059 then you are using udev, so use > udevmonitor to watch the udev events going past. # cat /proc/sys/kernel/hotplug /sbin/udevsend # udevinfo -V udevinfo, version 068 Here is the output from udevmonitor during the xm create when the vif failed: UE...

...ipped cpio file, then tried to compile image in the kernel or use image with initrd option. In the first case I'm getting "corrupted or invalid kernel" immediately. In the second kernel and initrd can be downloaded but at the certain stage I can see only repeated message "udevsend: error ...". Which additional steps I should take? Regards, Vlad.

...ile, then tried to compile image in the > kernel or use image with initrd option. In the first case I'm getting > "corrupted or invalid kernel" immediately. In the second kernel and > initrd can be downloaded but at the certain stage I can see only > repeated message "udevsend: error ...". > Which additional steps I should take? > > Regards, > Vlad. -- Beer helps the developers to work faster ya know, VoVaN

I have problem to start domU with errors: # xm create -c x335-hien1-vm4.cfg Using config file "x335-hien1-vm4.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working in changeset: changeset: 7700:98bcd8fbd5e36662c10becdcd0222a22161bb2b6 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Nov 8 09:48:42 2005 summary: Fix alloc_skb()

Hi all, I just downloaded, built and installed nut-2.0.4-pre2. I have an APC Smart ups 3000 connected via a usb cable. I have compiled and installed the usb drivers. I installed the libhidups and libhid.usermap per the README. I have the following ups.conf: [APC-3000-ups] driver = newhidups port = auto desc = "APC smart 3000" When I try to start the driver I get the

...[ ok ] * Mounting sysfs at /sys ... [ ok ] * Mounting /dev for udev ... [ ok ] * Configuring system to use udev ... * Populating /dev with device nodes ... * Setting /sbin/udevsend as hotplug agent ... [ ok ] * Mounting devpts at /dev/pts ... [ ok ] * Activating (possible) swap ...Adding 2096440k swap on /dev/hda9. Priority:-1 extents:1 Adding 2096440k swap on /...