Hi MiLo,
thanks for your reply !
It looks like a usb-to-serial, that should just work without any changes.
it's a external cardreader which is needed the module usbserial and ftdi_sio.
if this modules are loaded then the smargo is identified as /dev/ttyUSB0 if we have only one Smargo on the box
and so the smargo is working with oscam in mouse mode and it's enough to make in the oscam.server an entry as;
device = /dev/ttyUSB0
but much better (and if we have more then one smargo on the box it's necessary) to use the smargo instead in the mouse mode in smargo or smartreader mode
otherwise it is possible that the devices on the box as example for two smargos /dev/ttyUSB0 and /dev/ttyUSB1 are changed after a reboot.
to solve this problem we can use the smargo in smargo or smartreader mode but for this we must link the smargo with his serial
to a special device as example /devSmargoV2 and i know the way for that with udev, but i didn't know this way with mdev.
for udev it's easy i need only the output from the following command in telnet;
udevadm info --name=/dev/ttyUSB0 --attribute-walk
now the important detail from the output to this command;
looking at device '/devices/platform/ehci-brcm.1/usb2/2-1/2-1.1/2-1.1:1.0/ttyU
SB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
DRIVER==""
looking at parent device '/devices/platform/ehci-brcm.1/usb2/2-1/2-1.1/2-1.1:1
.0/ttyUSB0':
KERNELS=="ttyUSB0"
SUBSYSTEMS=="usb-serial"
DRIVERS=="ftdi_sio"
ATTRS{port_number}=="0"
ATTRS{latency_timer}=="1"
looking at parent device '/devices/platform/ehci-brcm.1/usb2/2-1/2-1.1/2-1.1:1
.0':
KERNELS=="2-1.1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="ftdi_sio"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceSubClass}=="ff"
ATTRS{bInterfaceProtocol}=="ff"
ATTRS{bNumEndpoints}=="02"
ATTRS{supports_autosuspend}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
ATTRS{interface}=="Smartreader2 plus"
looking at parent device '/devices/platform/ehci-brcm.1/usb2/2-1/2-1.1':
KERNELS=="2-1.1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="1.1"
ATTRS{idVendor}=="0403"
ATTRS{speed}=="12"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="2"
ATTRS{devnum}=="3"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="100mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="a0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0500"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="RKABD247"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="98666"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Argolis BV"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="6001"
ATTRS{bDeviceClass}=="00"
ATTRS{product}=="Smartreader2 plus"
and with that output i can generate the 52-smargo.rules which looks then as following;
## Smargo Smartreader+ rules
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idProduct}=="6001", ATTRS{serial}=="RKABD247", SYMLINK+="SmargoV2", MODE="660"
that's very easy and works perfectly but if i can make the same with mdev then that's better because pli use out of the box mdev
and you wrote the following;
I'd expect udev to conflict horribly with the pre-installed mdev which is already managing hardware devices. I'm surprised your box actually still boots after installing it.
so i'am now unsure to use udev in pli and i would much rather to use mdev for that.
regards
Biki3
