gmane.linux.hotplug.devel

usb coldplug problem

Bernd Porr — 2008-12-01T08:46:52

Hi! I'm the maintainter of the USBDUX board which connects via the USB to linux. In order to work properly the USBDUX needs firmware uploaded. So, I wrote a udev rule which uploads the firmware as soon as there's a udev event from the USB BUS (this is done via comedi_config). This works fine for hotplug but not for coldplug. So I need to pull the USB plug and back again to get the firmware loaded. I've checked with udevadm monitor and there are indeed no udev events during boot relating to the usbdux. Even a udevadm trigger produces no hotplug events for the USBDUX during boot time -- however later it does. It seems so that the usb subsystem is loading the usbdux module earlier on in the boot process so that no udev events are triggered later in the boot process. Any other ideas? It is really annoying that one has to pull out the plug and plug it back in again to trigger the firmware upload. I've been trying to solve the problem for a couple of weeks but without success. With the old hotplug m

Help to create a rule for UDEV

2008-11-29T23:25:54

Hi! I have 3 usb devices connected to my PC. All of them are identical. Lets call them device1, device2 and device3 They are beeing detected as ttyUSB0 (device1), ttyUSB1(device2) and ttyUSB2(device3), which is exactly what I want. The only problem is that when I restart, they often get mixed, and detected ttyUSB0(device2), ttyUSB1(device3) and ttyUSB2(device1) or any other order. I can't create rules for these device from serialnumber, or other details other than usb-connection port. This is what I get from udevinfo, hoping that someone can help me create a rule, for all 3. looking at device '/class/tty/ttyUSB0': KERNEL=="ttyUSB0" SUBSYSTEM=="tty" DRIVER=="" ATTR{dev}=="188:0" looking at parent device '/devices/pci0000:00/0000:00:10.2/usb4/4-2/4-2:1.0/ttyUSB0': KERNELS=="ttyUSB0" SUBSYSTEMS=="usb-serial" DRIVERS=="ftdi_sio" ATTRS{port_number}=="0" looking at parent device '/devices/pci0000:00/0000:00:10.2/usb4/4-2/4-2:1.0': KERNELS=="4-2:1.0" SUBSYSTEMS=="usb" DRIVERS=="ftdi_sio" ATTRS{bInterfaceNu

Udev rule for HSDPA modem

Jar — 2008-11-28T17:56:53

Hello I hope this is the correct list to ask this. I am not subscribed, so add me to cc. HSDPA modem (usb_serial+option modules) creates three ttyUSB devices. The first one is the modem interface used for ppp connection. How to write udev rule which will match to the first ttyUSB device? E.g. if the devices are ttyUSB1, ttyUSB2 and ttyUSB3, how to create e.g. symlinks modem0, modem1 and modem2, then it would be guaranteed that the modem0 device would be the first one. I tried the above rule, but it's problem is that it match only ttyUSB0 and that is not always the HSDPA modem device. ACTION=="add", \ KERNEL=="ttyUSB0", \ SUBSYSTEMS=="usb", \ ATTRS{idVendor}=="12d1", \ ATTRS{idProduct}=="1003", \ SYMLINK+="modem", \ RUN+="/tmp/udev_test.sh" Rule below will match all ttyUSB* devices and then the udev_test.sh will run several times. I would want to run it only once for the first ttyUSB of the modem. ACTION=="add", \ KERNEL=="ttyUSB*", \ ... ...

mtd and udev

Sven Fischer — 2008-11-28T16:08:21

Hi, I'm trying to use udev to dynamically generate mtd devices like mtdblock0 or mtd0 etc. I'm using Linux Kernel 2.6.24 on an ARM board. I have setup two rules but to no avail: ACTION=="add", KERNEL=="mtdblock[0-9]", SUBSYSTEMS=="block", NAME="mtdblock/%n", SYMLINK+="%k" ACTION=="add", KERNEL=="mtd[0-9]", SUBSYSTEMS=="mtd", NAME="%k" I tried to check them with udevtest, but it doesn't work. strace shows that it runs through the /sys subtree but it doesn't match anything against the above rules. I have the impression mtd isn't meant to work together with udev at all. Am I right ? Or what can be the reason for this issue. Help appreciated. Best regards Sven -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH]: USB, Infiniband and X0R rules

Piter PUNK — 2008-11-28T00:06:14

Hi, Those are the last custom slackware rules. They creates some devices in correct place (following devices.txt). USB devices are moved to /dev/usb/name and Infiniband to /dev/infiniband/name. The patch fixes X0R symlink, too. From devices.txt: --- /dev/X0R null symbolic Required by iBCS-2 Note: /dev/X0R is --. --- Well, the patch is below: ---patch here--- diff -Naur udev-134-orig/rules/rules.d/50-udev-default.rules udev-134/rules/rules.d/50-udev-default.rules --- udev-134-orig/rules/rules.d/50-udev-default.rules2008-11-19 18:46:39.000000000 -0200 +++ udev-134/rules/rules.d/50-udev-default.rules2008-11-27 21:36:51.000000000 -0200 < at >< at > -20,7 +20,7 < at >< at > # mem KERNEL=="null|zero|full|random|urandom", MODE="0666" -KERNEL=="null",SYMLINK+="XOR" +KERNEL=="null",SYMLINK+="X0R" KERNEL=="mem|kmem|port|nvram",GROUP="kmem", MODE="0640" KERNEL=="ram0",SYMLINK+="ramdisk" KERNEL=="ram1",SYMLINK+="ram" < at >< at > -59,6 +59,20 < at >< at > # firmware clas

[PATCH] Fix switch statement for video type

Marcel Holtmann — 2008-11-26T05:30:53

Introducing the video type, creating a fall-through case where other devices might now be declared as type video. diff --git a/extras/usb_id/usb_id.c b/extras/usb_id/usb_id.c index 91e3ecc..ce1eb0b 100644 --- a/extras/usb_id/usb_id.c +++ b/extras/usb_id/usb_id.c < at >< at > -70,6 +70,7 < at >< at > static void set_usb_iftype(char *to, int if_class_num, size_t case 0x0a: /* CDC-Data */ case 0x0b: /* Chip/Smart Card */ case 0x0d: /* Content Security */ + break; case 0x0e: type = "video"; break; -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[ANNOUNCE] udev 134 release

Kay Sievers — 2008-11-26T03:54:02

[RFC] network devices generating uevents?

Stephen Hemminger — 2008-11-22T07:41:10

Perhaps the following would make it easier for applications to track network device events without having to use netlink. Compile tested only so far. The implementation is almost trivial... --- a/net/core/Makefile2008-11-21 12:25:31.000000000 -0800 +++ b/net/core/Makefile2008-11-21 13:32:30.000000000 -0800 < at >< at > -17,3 +17,4 < at >< at > obj-$(CONFIG_NET_PKTGEN) += pktgen.o obj-$(CONFIG_NETPOLL) += netpoll.o obj-$(CONFIG_NET_DMA) += user_dma.o obj-$(CONFIG_FIB_RULES) += fib_rules.o +obj-$(CONFIG_HOTPLUG) += uevent.o --- /dev/null1970-01-01 00:00:00.000000000 +0000 +++ b/net/core/uevent.c2008-11-21 13:42:13.000000000 -0800 < at >< at > -0,0 +1,45 < at >< at > +/* + * Linux network device event notification + * + * Author: + *Stephen Hemminger vyatta.com> + */ + +#include +#include +#include +#include + +static int netdev_event(struct notifier_block *this, unsigned long event, void *ptr) +{ +struct net_device *netdev = ptr; + +switch (event) { +ca

山鉧科技網頁設計

謝珮蓁 — 2008-11-22T05:49:40

山鉧科技網頁設計 ■我們的宗旨：客戶的每ㄧ件小事情，都是山鉧的大事情￥我們在推出企業形象網站包含前台網頁美工+後台管理程式 ⊙限時限量專案價只要$29,900 ∴(在送ㄧ年100MB不限流量網站空間) ↖我們做的不只是網站，而是您企業的入口 ÷ㄧ個好的企業網站資料即時更新的速度是很重要的 €企業ｅ化的高品質團隊，打造您的網路門面＝＝選擇山鉧成就您的夢想～～～～～～～～～～～～～～～～～～～～～～～～～～ PS: 線上購物網站我們還可提供刷卡機制，　　與線上列印帳單全省超商+郵局繳費......等金流服務機制～～～～～～～～～～～～～～～～～～～～～～～～～～歡迎來電洽詢黃專員（Sam）：0980119812 / 0938764395 ～～～～～～～～～～～～～～～～～～～～～～～～～～本公司另外提供關鍵字SEO排序服務保證將您的網站在Yx / Gx ...排

Are there events when eth carrier changes state?

Karl O. Pinc — 2008-11-21T18:24:24

Hi, I see that eth0 has a ATTR{carrier}. Are there any events that could be used to trigger RUN rules when that changes? How about ATTR{operstate}? If not, is there somewhere I should be looking besides udev? There's a comment in the list archives back in 2001 from Andrew Morton saying that "better netdevice manageability" is a goal, but I can't find any further reference. Thank you. Karl meme.com> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after

Toralf Förster — 2008-11-21T14:54:15

Hello WIth 2.6.28-rc6-00007-ged31348 I get that warning message within dmesg udner a stable Gentoo system with udev-124. With the current kernel I'm using (2.6.26.8) however there isn't such a warning.

udev-133: build failure and 3 small patches

Peter Breitenlohner — 2008-11-21T09:07:47

Hi, attached are three small patches for udev-133. The first one fixes a build problem (!HAVE_INOTIFY needs ). The other two correct minor manpage typos. Regards Peter Breitenlohner mppmu.mpg.de>diff -ur udev-133.orig/udev/udev-sysdeps.h udev-133/udev/udev-sysdeps.h --- udev-133.orig/udev/udev-sysdeps.h2008-11-13 01:51:54.000000000 +0100 +++ udev-133/udev/udev-sysdeps.h2008-11-20 15:10:21.000000000 +0100 < at >< at > -21,6 +21,7 < at >< at > #define _UDEV_SYSDEPS_H_ #include +#include /* needed for our signal handlers to work */ #undef asmlinkage diff -ur udev-133.orig/extras/floppy/create_floppy_devices.8 udev-133/extras/floppy/create_floppy_devices.8 --- udev-133.orig/extras/floppy/create_floppy_devices.82008-10-16 18:03:43.000000000 +0200 +++ udev-133/extras/floppy/create_floppy_devices.82008-11-20 14:56:47.000000000 +0100 < at >< at > -28,7 +28,7 < at >< at > Set device node mode. .TP \fB\-t\fR -Sed floppy type number. +Set floppy type number. .SH SEE ALSO .B

WAIT_FOR_SYSFS error, Is my udev rule wrong?

Karl O. Pinc — 2008-11-20T05:47:44

Hello, I've written a udev rule and am looking for comment by those with more experience to see if there are improvements to be made. I'm running Debian Etch Linux 2.6.24-etchnhalf.1-486 Udev package version: 0.105-4 I've a USB LCD panel and found that the lcd4linux daemon that controls it dies when the device is unplugged. It seemed smart to write udev rules that start and stop the daemon whenever the device was plugged or unplugged. This is what I came up with: ----------------------------------- # /etc/udev/rules.d/z75_lcd4linux.rules # Copyright (C) 2008, Karl O. Pinc meme.com> # Distributed under the GPL V3 or later. # Adjust file name for your distro. # # Rules to start/stop the lcd4linux daemon as USB lcd devices # are detected. # # When using this be sure to remove the link in /etc/rc?.d/S*lcd4linux # so that the daemon is not started twice at boot. # Start the daemon whenever ttyUSB0 is plugged in KERNEL=="ttyUSB0", ACTION=="add", WAIT_FOR_SYSFS="subsystem/ttyUSB0" RUN+="/etc\ /in

persistent rules for memory stick block devices

Harald Hoyer — 2008-11-19T10:24:03

commit 5a9aed145ac0ffb3e29b1c8e0f19b34e277f9117 Author: Harald Hoyer redhat.com> Date: Wed Nov 19 11:22:30 2008 +0100 added persistent rules for memory stick block devices diff --git a/rules/rules.d/60-persistent-storage.rules b/rules/rules.d/60-persistent-storage.rules index 4f8de28..b9298f7 100644 --- a/rules/rules.d/60-persistent-storage.rules +++ b/rules/rules.d/60-persistent-storage.rules < at >< at > -44,6 +44,9 < at >< at > KERNEL=="sd*[0-9]", ENV{ID_ATA_COMPAT}=="?*", SYMLINK+="disk/by-id/ata-$env{ID_A KERNEL=="mmcblk[0-9]", SUBSYSTEMS=="mmc", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}" KERNEL=="mmcblk[0-9]p[0-9]", ENV{ID_NAME}=="?*", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}-part%n" +KERNEL=="mspblk[0-9]", SUBSYSTEMS=="memstick", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/memsti

[ANNOUNCE] udev 133 release

Kay Sievers — 2008-11-18T02:56:36

Here comes a new udev version. Thanks to all who have contributed to this release. The tarball can be found here: ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug/ The development repository can be found here: http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=summary The ChangeLog can be found here: http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=ChangeLog udev 133 ======== Bugfix for kernels using the SYSFS_DEPRECATED* option and finding parent block devices in some cases. No common distro uses this option anymore, and we do not get enough testing for this and recent udev versions. If this option is not needed to run some old distro with a new kernel, it should be disabled in the kernel config. Bugfix for the $links substitution variable, which may crash if no links are created. This should not happen in usual setups because we always create /dev/{block,char}/ links. The strings of the parsed rules, which are kept in memory, no longer contain duplicate entries, or duplic

Crash when udev detects my swap partition (only ?)

Michel Hermier — 2008-11-17T13:25:16

Hi, I have a repeatable crash in udev when it tries to detect my swap partition (and maybe in other cases that I didn't had the time to investigate more) With the udev-132 on frugalware, I get the following backtrace, when I: udevadm test /block/hda/hda2 I get the following stack trace: #0 0x08054150 in util_strlcat () #1 0x0804a8aa in udev_event_apply_format () #2 0x0804e2c6 in udev_rules_apply_to_event () #3 0x080497ae in udev_event_execute_rules () #4 0x0805b704 in udevadm_test () #5 0x08059b83 in run_command () #6 0x08059e24 in main () or in valgrind ==21311== Invalid read of size 1 ==21311== at 0x8054150: util_strlcat (in /sbin/udevadm) ==21311== by 0x804A8A9: udev_event_apply_format (in /sbin/udevadm) ==21311== by 0x804E2C5: udev_rules_apply_to_event (in /sbin/udevadm) ==21311== by 0x80497AD: udev_event_execute_rules (in /sbin/udevadm) ==21311== by 0x805B703: udevadm_test (in /sbin/udevadm) ==21311== by 0x8059B82: run_command (in /sbin/udevadm) ==21311== by 0x8059E23:

multi-user, udev, consolkit, oh my

Yan Seiner — 2008-11-16T15:31:54

I'm working on multi-user setups. I'd like to be assign some resources - like a USB hub - to a seat and have hotplug for that hub work only for that seat. Currently, what happens is that a user plugs in a camera, and hal reports the event. All of the concurrent gnome-volume-manager instances then try to grab that resource, and what results is a mess. consolekit has been suggested as a way to resolve this, but I can't figure out how to use it. googling around, I've found suggestions for using udev to limit access to usb devices by creating a group that only has access to the usb subsystem. If I want to group some resources and only have those resources on behalf of a specific user, and not any other, is there a way to do that? Can I set up groups for hotplugging usb devices and set it up so that the event is only reported to specific group members? Thanks., --Yan -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo< at >vger.kernel.org

udev and network devices

Michel Rode — 2008-11-15T10:02:31

Hello, i tried to rename my network device - this works, but the symlink are not exists. This is my rule: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:6f:b5:8b:76", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0", SYMLINK+="eth1" Now i have the idea, that it could not work because there are not such device in /dev - is it true ? Thanks, Michel

[PATCH] udevadm: fix option parsing breakage with klibc

Sergey Vlasov — 2008-11-14T21:34:43

The klibc implementation of getopt_long() behaves slightly different from the glibc one - in particular, it treats the change of the option string argument between invocations as start of parsing a different command line, and resets its state. However, the udevadm code expected getopt_long() invocations in subcommands to continue parsing the rest of command line after initial options has been parsed at the top level; with klibc this broke, causing all udevadm subcommands to stop recognizing their options. Instead of relying on the glibc behavior, reset the getopt_long() state properly before invoking the subcommand handler: move argv to point to the subcommand name, decrease argc appropriately, and set optind = 0. This also fixes a minor bug visible with glibc - without setting optind = 0 all getopt_long() calls in subcommand handlers were behaving as if "+" was specified as the first character of the option string (which disables option reordering), because that state was set by the first getopt_long() c

Some rules do not work in udev 131 and 132

Mikhail Kolesnik — 2008-11-12T19:00:52

Hello. udev was built from sources with no patching or very special rulesets installed. After a simple update from 130 to 131 some of my custom rules stopped working. And I can't find information about syntax change in git log. In the example below the first rule creates a symlink, but the second one creates none. It works with 130 but does not work on 131 and 132. The same results for another device (and partitions are there untouched). BUS=="usb", ATTRS{serial}=="A500000000025423", KERNEL=="sd?", NAME="%k", SYMLINK+="usbflash", GROUP="cdrom" BUS=="usb", ATTRS{serial}=="A500000000025423", KERNEL=="sd?[1-3]", NAME="%k", SYMLINK+="usbflash%n", GROUP="cdrom" Target: i686-pc-linux-gnu Configured with: ../gcc-4.2.4/configure --prefix=/usr --libexecdir=/usr/lib --enable-languages=c,c++,objc --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-shared --disable-nls --with-x=no Thread model: posix gcc version 4.2.4 (CRUX) libtool 2.2.6 Linux amilo.home 2.6.26.1-mk38 #1 Sun Aug 3 17:08:1

[PATCH] scsi_id: we don't use DEVPATH env var anymore, update man page

Alan Jenkins — 2008-11-12T16:23:17

Signed-off-by: Alan Jenkins tuffmail.co.uk> diff --git a/extras/scsi_id/scsi_id.8 b/extras/scsi_id/scsi_id.8 index 4656e68..5f4d997 100644 --- a/extras/scsi_id/scsi_id.8 +++ b/extras/scsi_id/scsi_id.8 < at >< at > -98,13 +98,6 < at >< at > Generate verbose debugging output. Display version number and exit. .RE -.SH ENVIRONMENT - -If the DEVPATH environment variable is set, scsi_id assumes it has been -invoked via udev (or some other hotplug program), and all errors or -warnings are sent using syslog. -.P - .SH "FILES" .nf .ft B -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html