12.01.2018 13:24, Paul Neuwirth пишет:
On Thu, 11 Jan 2018 14:08:50 +0300 Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Thu, Jan 11, 2018 at 1:46 PM, Paul Neuwirth <mail@paul-neuwirth.nl> wrote:
Hello, doing a new ISDN capi setup... didn't do for many years. using leap 42.3 i currently struggle with following:
the module for the active ISDN controller (AVM C2) is not being loaded at boot. even modprobe c4 doesn't work, I have to do insmod /lib/modules/4.4.104-39-default/kernel/drivers/isdn/hardware/avm/c4.ko to load the driver.
This module is apparently blacklisted by default. I have no idea why.
just one question over. I think you one of the experts for udev..
the rules in /usr/lib/udev/rules.d/45-isdn.rules: # CAPI devices SUBSYSTEM=="capi", KERNEL=="capi", NAME="capi20", GROUP="dialout"
You log below does not show and kernel device with name "capi", only with name "capi20". You probably want to change it to KERNEL=="capi20", but I am not familiar with this subsystem to know whether this is the right chane.
SUBSYSTEM=="tty", KERNEL=="capi[0-9]*", NAME="capi/%n"
do not get applied.
this is output from udevadm monitor when enabling isdn: monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent
KERNEL[87.005589] add /module/kernelcapi (module) UDEV [87.014019] add /module/kernelcapi (module) KERNEL[87.018486] add /module/capi (module) KERNEL[87.018524] add /class/capi (class) KERNEL[87.022017] add /devices/virtual/capi/capi20 (capi) UDEV [87.028631] add /module/capi (module) UDEV [87.030378] add /class/capi (class) UDEV [87.035189] add /devices/virtual/capi/capi20 (capi) KERNEL[98.844062] add /module/b1 (module) KERNEL[98.870296] add /module/c4 (module) KERNEL[98.870331] add /bus/pci/drivers/c4 (drivers) UDEV [98.876854] add /module/b1 (module) UDEV [98.878899] add /module/c4 (module) UDEV [98.880900] add /bus/pci/drivers/c4 (drivers) KERNEL[102.325443] add /module/slhc (module) UDEV [102.329357] add /module/slhc (module) KERNEL[102.335003] add /module/isdn (module) KERNEL[102.336807] add /devices/virtual/tty/ttyI0 (tty) ... KERNEL[102.352290] add /devices/virtual/tty/ttyI57 (tty) UDEV [102.354118] add /module/isdn (module) UDEV [102.356355] add /devices/virtual/tty/ttyI0 (tty) ... UDEV [102.555881] add /devices/virtual/tty/ttyI12 (tty) KERNEL[102.555947] add /module/capidrv (module) ... UDEV [102.561707] add /devices/virtual/tty/ttyI62 (tty) UDEV [102.561806] add /module/capidrv (module)
the device is created at this time, but still owned by root:root: # ls -l /dev/capi20 crw------- 1 root root 68, 0 12. Jan 11:16 /dev/capi20
the ttyS show correct ownership and mode # ls -l /dev/ttyI* crw-rw---- 1 root dialout 43, 0 12. Jan 11:17 /dev/ttyI0 crw-rw---- 1 root dialout 43, 1 12. Jan 11:17 /dev/ttyI1 crw-rw---- 1 root dialout 43, 10 12. Jan 11:17 /dev/ttyI10 crw-rw---- 1 root dialout 43, 11 12. Jan 11:17 /dev/ttyI11 crw-rw---- 1 root dialout 43, 12 12. Jan 11:17 /dev/ttyI12 crw-rw---- 1 root dialout 43, 13 12. Jan 11:17 /dev/ttyI13 crw-rw---- 1 root dialout 43, 14 12. Jan 11:17 /dev/ttyI14 [...]
how can I apply a rule for /dev/capi20 (also mode 660 and root:dialout)
thank you
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org