search for: wait_for_sysf

I've been testing * on FC3. I have everything compiled and installed. However, when I do 'modprobe wcfxo' (I have an X100P clone), I get the following in /var/log/messages: Nov 24 10:23:40 jfd wait_for_sysfs[3366]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/zaptel/zaptimer' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug- devel@lists.sourceforge.net> Nov 24 10:23:40 jfd wai...

...igress. I chose FC3 (Fedora Core) for the install, and now I'm sorry that I did. At least with unix I was able to get a dial tone! Not so much with this flavor of linux. Each time I run "modprobe wcfxs" I get the following errors in /var/log/messages: Jan 5 17:57:59 asterisk wait_for_sysfs[2782]: either wait_for_sysfs (udev 039)needs an update to handle the device '/class/zaptel/zap1' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> Jan 5 17:57:59 asterisk w...

Hello, I can''t seem to get the network going. I found this message in the log of Domain0: ----------------------------------------------------------------------- Dec 1 15:39:18 zms wait_for_sysfs[4180]: either wait_for_sysfs (udev 039) needs an update to handle the device ''/class/net/br0'' properly (no device symlink) or the sysfs-support of your device''s driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net> ----------------...

...GBAMNiy1zXS6k3s+ocIdFWKU6MbpW3rQXGp7yIL+baY7GMxhOmsgZdyc1B yQLJferCAhnR3gtU/zkeTASJOlTiZgmzwWSC0Ob4BOc5fUf6Uk6erVcPirzFe8G1 VNyagm1w/4L92hla8Xmw8rjxnNo6r2Jf/JfTZ/i3CbnIAZhPLuopAgMBAAE= -----END RSA PUBLIC KEY----- When I do "tincd -n saaotun", I get this message in the error logs: "wait_for_sysfs[3643]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/net/saaotun' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>" I removed /dev/net...

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

On Apr 23, 2014, at 3:47 AM, Frantz de Germain wrote: > I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP > 1.6/Centos 5.7) to manage a Dell UPS 2700W. > > Here is my ups.conf : > > [SU27003U-08] > driver = usbhid-ups > port = auto > desc = "SU27003U-08" > > 52-nut-usbups.rules have well been installed in

Hello, I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP 1.6/Centos 5.7) to manage a Dell UPS 2700W. Here is my ups.conf : [SU27003U-08] driver = usbhid-ups port = auto desc = "SU27003U-08" 52-nut-usbups.rules have well been installed in /lib/udev/rules.d/. I've put it in /etc/udev/rules.d/ too. I've rebooted the machine.

...145600 512-byte > hdwr sectors (322123 MB) > Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off > Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back > Apr 29 10:24:41 vz-10 iscsid: connection1:0 is operational now > Apr 29 10:24:44 vz-10 udevd-event[23432]: wait_for_sysfs: waiting > for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ > ioerr_cnt' failed > Apr 29 10:25:06 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:0 state (3). Dropping session. > Apr 29 10:25:10 vz-10 iscsid: connection1:0 is operational...

...y) and will need to recreate it on destination servers. My coworker said that udev may be assigning the /dev/sdj (and other) identifier so I checked this. In /etc/udev/rules.d/* I see rules for scsi subsystem (sysfs type 0 is "disk"): ACTION=="add", SUBSYSTEM=="scsi", WAIT_FOR_SYSFS="ioerr_cnt" ACTION=="add", SUBSYSTEM=="scsi_device", SYSFS{type}=="0", RUN+="socket:/org/kernel/diskres/uevents" ACTION=="remove", SUBSYSTEM=="scsi_device", RUN+="socket:/org/kernel/diskres/uevents" So I do not see an...