|
Hi, no there was no device node created named like /dev/hso0, but the sysfs interface was created. Inside the sysfs path i don't see the "file" "dev", which should contain the device node information. So udev has no idea how to create this device node. Dan: What does ls -l /dev/hso0 show for your device? --snip-- #cd /sys/class/net/hso0/ /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls -l -r--r--r-- 1 root root 4096 Jun 7 09:46 addr_assign_type -r--r--r-- 1 root root 4096 Jun 7 2011 addr_len -r--r--r-- 1 root root 4096 Jun 7 09:46 address -r--r--r-- 1 root root 4096 Jun 7 09:46 broadcast -r--r--r-- 1 root root 4096 Jun 7 09:46 carrier -r--r--r-- 1 root root 4096 Jun 7 09:46 dev_id lrwxrwxrwx 1 root root 0 Jun 7 09:46 device -> ../../../1-1.1:1.0 -r--r--r-- 1 root root 4096 Jun 7 09:46 dormant -r--r--r-- 1 root root 4096 Jun 7 09:46 duplex -r--r--r-- 1 root root 4096 Jun 7 09:46 features -rw-r--r-- 1 root root 4096 Jun 7 2011 flags -rw-r--r-- 1 root root 4096 Jun 7 09:46 ifalias -r--r--r-- 1 root root 4096 Jun 7 2011 ifindex -r--r--r-- 1 root root 4096 Jun 7 09:46 iflink -r--r--r-- 1 root root 4096 Jun 7 09:46 link_mode -rw-r--r-- 1 root root 4096 Jun 7 09:46 mtu -r--r--r-- 1 root root 4096 Jun 7 09:46 operstate drwxr-xr-x 2 root root 0 Jun 7 09:46 power drwxr-xr-x 4 root root 0 Jun 7 09:46 queues -r--r--r-- 1 root root 4096 Jun 7 09:46 speed drwxr-xr-x 2 root root 0 Jun 7 09:46 statistics lrwxrwxrwx 1 root root 0 Jun 7 2011 subsystem -> ../../../../../../../../../class/net -rw-r--r-- 1 root root 4096 Jun 7 09:46 tx_queue_len -r--r--r-- 1 root root 4096 Jun 7 2011 type -rw-r--r-- 1 root root 4096 Jun 7 2011 uevent /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls device/dev ls: device/dev: No such file or directory --snip-- Harald Am Montag, 6. Juni 2011, 23:48:42 schrieb Dan Williams: > Just to confirm, you do *not* have a /dev/hso0? Do you > have /sys/class/net/hso0 after plugging the device in? > > I just tried out my iCON 452 and it does provide the hso0 interface that > we'd expect, and that's what ModemManager expects too. > > Dan > |