udev config to load module for hardware / capi setup

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

udev config to load module for hardware / capi setup

Paul Neuwirth-3
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. dmesg:
[  313.028674] CAPI 2.0 started up with major 68 (middleware)
[  313.058011] b1: revision 1.1.2.2
[  373.508650] c4 0000:03:02.0: PCI IRQ 35 -> rerouted to legacy IRQ 19
[  373.508667] c4: PCI BIOS reports AVM-C2 at i/o 0xdc80, irq 19, mem
0xfe7ffc00 [  373.548032] kcapi: controller [001]: c2-dc80 attached
[  373.548036] kcapi: controller [002]: c2-dc80 attached
[  373.548038] c4: AVM C2 at i/o 0xdc80, irq 19, mem 0xfe7ffc00
[  373.548078] c4: revision 1.1.2.2

to get capi working I have to do `capiinit` additionaly, dmesg:

[ 1079.116796] c2-dc80: card 1 "C2" ready.
[ 1079.116801] c2-dc80: card 1 Protocol: DSS1
[ 1079.116803] c2-dc80: card 1 Linetype: point to multipoint
[ 1079.116804] c2-dc80: C2-card (3.11-04) now active
[ 1079.116806] kcapi: controller [001] "c2-dc80" ready.
[ 1079.116836] c2-dc80: card 2 "C2" ready.
[ 1079.116839] c2-dc80: card 2 Protocol: DSS1
[ 1079.116840] c2-dc80: card 2 Linetype: point to multipoint
[ 1079.116841] c2-dc80: C2-card (3.11-04) now active
[ 1079.116842] kcapi: controller [002] "c2-dc80" ready.

what config do I miss to get everything be done by udev, which
should(?) handle this?


here the config files

# cat /usr/lib/udev/rules.d/45-isdn.rules
# do not edit this file, it will be overwritten on update

# CAPI devices
SUBSYSTEM=="capi", KERNEL=="capi", NAME="capi20", GROUP="dialout"
SUBSYSTEM=="tty", KERNEL=="capi[0-9]*", NAME="capi/%n"

# ISDN devices
KERNEL=="isdn*", MODE="600"
KERNEL=="isdnctrl*", MODE="600"
KERNEL=="ippp*", MODE="600"
KERNEL=="isdninfo*", MODE="444"

# ISDN USB
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/c00*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/1000*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/1900*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2000*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2200*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2300*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2800*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/3000*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/3500*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/3600*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2805*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2806*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/4401*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/4601*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="483/4810*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="959/2bd0*", RUN+="isdn.sh"
SUBSYSTEM=="usb", ENV{PRODUCT}=="9bf/*", RUN+="isdn.sh"

# ISDN PCMCIA
# AVM B1 models
SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pb845DC335pc*pd*",
RUN+="isdn.sh b1 1" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pb81E10430pc*pd*",
RUN+="isdn.sh b1 2" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pb18E8558Apc*pd*",
RUN+="isdn.sh b1 3" # AVM A1 models (aka Fritz!Card PCMCIA)
SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pbADC9D4BBpc*pd*",
RUN+="isdn.sh a1 1" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa8D9761C8pb01C5AA7Bpc*pd*",
RUN+="isdn.sh a1 2" # teles SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa67B50EAEpbE9E70119pc*pd*",
RUN+="isdn.sh teles 1" # sedlbauer SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbF3612E1Dpc6B95C78Apd*",
RUN+="isdn.sh sedlbauer 1" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pc397B7E90pd*",
RUN+="isdn.sh sedlbauer 2" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pc2E5C7FCEpd*",
RUN+="isdn.sh sedlbauer 3" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pc8DB143FEpd*",
RUN+="isdn.sh sedlbauer 4" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pcB391AB4Cpd*",
RUN+="isdn.sh sedlbauer 5" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*paD79E0B84pb21D083AEpc*pd*",
RUN+="isdn.sh sedlbauer 6" # elsa SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa983DE2C4pb333BA257pc*pd*",
RUN+="isdn.sh elsa 1" SUBSYSTEM=="pcmcia",
ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa639E5718pb333BA257pc*pd*",
RUN+="isdn.sh elsa 2"

# cat /etc/capi.conf
# card  file    proto   io      irq     mem     cardnr  options
c2      c4.ko   DSS1    -       -       -       -
c2      -       DSS1    -       -       -       -


isdn/capi packages:
# rpm -qa | grep -Ei 'capi|isdn|i4l'
capi4linux-2011.8.29-93.1.x86_64
libcapi20-2-2011.8.29-93.1.x86_64
i4lfirm-2011.8.29-93.1.x86_64
i4l-base-2011.8.29-25.25.x86_64
libcapi20-3-2011.8.29-93.1.x86_64
i4l-isdnlog-2011.8.29-93.1.x86_64
capi4linux-devel-2011.8.29-93.1.x86_64

udev rules do not get applied at all:
# ls -l /dev/cap*
crw------- 1 root root 68, 0 11. Jan 11:19 /dev/capi20


thank you for any tips

Paul

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: udev config to load module for hardware / capi setup

Andrei Borzenkov
On Thu, Jan 11, 2018 at 1:46 PM, Paul Neuwirth <[hidden email]> 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.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: udev config to load module for hardware / capi setup

Paul Neuwirth-3
On Thu, 11 Jan 2018 14:08:50 +0300
Andrei Borzenkov <[hidden email]> wrote:

> On Thu, Jan 11, 2018 at 1:46 PM, Paul Neuwirth
> <[hidden email]> 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.
>

it is stated above:
# ISDN modules are load from /lib/udev/isdn.sh

but udev does not seem to recognize the avm c2 card..

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: udev config to load module for hardware / capi setup

Paul Neuwirth-3
In reply to this post by Paul Neuwirth-3
On Thu, 11 Jan 2018 11:46:54 +0100
Paul Neuwirth <[hidden email]> 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. dmesg:
> [  313.028674] CAPI 2.0 started up with major 68 (middleware)
> [  313.058011] b1: revision 1.1.2.2
> [  373.508650] c4 0000:03:02.0: PCI IRQ 35 -> rerouted to legacy IRQ
> 19 [  373.508667] c4: PCI BIOS reports AVM-C2 at i/o 0xdc80, irq 19,
> mem 0xfe7ffc00 [  373.548032] kcapi: controller [001]: c2-dc80
> attached [  373.548036] kcapi: controller [002]: c2-dc80 attached
> [  373.548038] c4: AVM C2 at i/o 0xdc80, irq 19, mem 0xfe7ffc00
> [  373.548078] c4: revision 1.1.2.2
>
> to get capi working I have to do `capiinit` additionaly, dmesg:
>
> [ 1079.116796] c2-dc80: card 1 "C2" ready.
> [ 1079.116801] c2-dc80: card 1 Protocol: DSS1
> [ 1079.116803] c2-dc80: card 1 Linetype: point to multipoint
> [ 1079.116804] c2-dc80: C2-card (3.11-04) now active
> [ 1079.116806] kcapi: controller [001] "c2-dc80" ready.
> [ 1079.116836] c2-dc80: card 2 "C2" ready.
> [ 1079.116839] c2-dc80: card 2 Protocol: DSS1
> [ 1079.116840] c2-dc80: card 2 Linetype: point to multipoint
> [ 1079.116841] c2-dc80: C2-card (3.11-04) now active
> [ 1079.116842] kcapi: controller [002] "c2-dc80" ready.
>
> what config do I miss to get everything be done by udev, which
> should(?) handle this?
>
>
> here the config files
>
> # cat /usr/lib/udev/rules.d/45-isdn.rules
> # do not edit this file, it will be overwritten on update
>
> # CAPI devices
> SUBSYSTEM=="capi", KERNEL=="capi", NAME="capi20", GROUP="dialout"
> SUBSYSTEM=="tty", KERNEL=="capi[0-9]*", NAME="capi/%n"
>
> # ISDN devices
> KERNEL=="isdn*", MODE="600"
> KERNEL=="isdnctrl*", MODE="600"
> KERNEL=="ippp*", MODE="600"
> KERNEL=="isdninfo*", MODE="444"
>
> # ISDN USB
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/c00*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/1000*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/1900*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2000*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2200*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2300*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2800*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/3000*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/3500*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/3600*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2805*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/2806*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/4401*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="57c/4601*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="483/4810*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="959/2bd0*", RUN+="isdn.sh"
> SUBSYSTEM=="usb", ENV{PRODUCT}=="9bf/*", RUN+="isdn.sh"
>
> # ISDN PCMCIA
> # AVM B1 models
> SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pb845DC335pc*pd*",
> RUN+="isdn.sh b1 1" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pb81E10430pc*pd*",
> RUN+="isdn.sh b1 2" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pb18E8558Apc*pd*",
> RUN+="isdn.sh b1 3" # AVM A1 models (aka Fritz!Card PCMCIA)
> SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa95D42008pbADC9D4BBpc*pd*",
> RUN+="isdn.sh a1 1" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa8D9761C8pb01C5AA7Bpc*pd*",
> RUN+="isdn.sh a1 2" # teles SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa67B50EAEpbE9E70119pc*pd*",
> RUN+="isdn.sh teles 1" # sedlbauer SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbF3612E1Dpc6B95C78Apd*",
> RUN+="isdn.sh sedlbauer 1" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pc397B7E90pd*",
> RUN+="isdn.sh sedlbauer 2" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pc2E5C7FCEpd*",
> RUN+="isdn.sh sedlbauer 3" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pc8DB143FEpd*",
> RUN+="isdn.sh sedlbauer 4" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa81FB79F5pbE4E9BC12pcB391AB4Cpd*",
> RUN+="isdn.sh sedlbauer 5" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*paD79E0B84pb21D083AEpc*pd*",
> RUN+="isdn.sh sedlbauer 6" # elsa SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa983DE2C4pb333BA257pc*pd*",
> RUN+="isdn.sh elsa 1" SUBSYSTEM=="pcmcia",
> ENV{MODALIAS}=="pcmcia:m*c*f*fn*pfn*pa639E5718pb333BA257pc*pd*",
> RUN+="isdn.sh elsa 2"
>
> # cat /etc/capi.conf
> # card  file    proto   io      irq     mem     cardnr  options
> c2      c4.ko   DSS1    -       -       -       -
> c2      -       DSS1    -       -       -       -
>
>
> isdn/capi packages:
> # rpm -qa | grep -Ei 'capi|isdn|i4l'
> capi4linux-2011.8.29-93.1.x86_64
> libcapi20-2-2011.8.29-93.1.x86_64
> i4lfirm-2011.8.29-93.1.x86_64
> i4l-base-2011.8.29-25.25.x86_64
> libcapi20-3-2011.8.29-93.1.x86_64
> i4l-isdnlog-2011.8.29-93.1.x86_64
> capi4linux-devel-2011.8.29-93.1.x86_64
>
> udev rules do not get applied at all:
> # ls -l /dev/cap*
> crw------- 1 root root 68, 0 11. Jan 11:19 /dev/capi20
>
>
> thank you for any tips
>
> Paul
>

for those who are interested, or find this. I found the solution.. the
"old" i4l-base package relies on config in /etc/sysconfig/isdn which
were created by yast2 network/isdn module, which does not exist
anymore. creating the file manually (in my case:
AREACODE="+49"
DIALPREFIX=""
DRIVER="c4"
ISDNLOG_START="yes"
NAME="AVM C2"
PARA_SUBTYPE="1"
PARA_TYPE="8001"
PROTOCOL="euro"
STARTMODE="auto"
UNIQUE="M8BZ.9mryWKq1N65"
)
and doing systemctl enable isdn.service / systemctl start isdn.service
made it run on boot :)

because everything is handled by these isdn-scripts, all modules are
blacklisted or disabled (e.g. in modprobe.d onfig: INSTALL
c4 /bin/true)..


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: udev config to load module for hardware / capi setup

Paul Neuwirth-3
In reply to this post by Andrei Borzenkov
On Thu, 11 Jan 2018 14:08:50 +0300
Andrei Borzenkov <[hidden email]> wrote:

> On Thu, Jan 11, 2018 at 1:46 PM, Paul Neuwirth
> <[hidden email]> 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"
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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: udev config to load module for hardware / capi setup

Andrei Borzenkov
12.01.2018 13:24, Paul Neuwirth пишет:

> On Thu, 11 Jan 2018 14:08:50 +0300
> Andrei Borzenkov <[hidden email]> wrote:
>
>> On Thu, Jan 11, 2018 at 1:46 PM, Paul Neuwirth
>> <[hidden email]> 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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: udev config to load module for hardware / capi setup

Paul Neuwirth-3
On Fri, 12 Jan 2018 20:32:18 +0300
Andrei Borzenkov <[hidden email]> wrote:

> 12.01.2018 13:24, Paul Neuwirth пишет:
> > On Thu, 11 Jan 2018 14:08:50 +0300
> > Andrei Borzenkov <[hidden email]> wrote:
> >  
> >> On Thu, Jan 11, 2018 at 1:46 PM, Paul Neuwirth
> >> <[hidden email]> 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.
>

thank you, creating config file
/etc/udev/rules.d/45-isdn.rules with
SUBSYSTEM=="capi", KERNEL=="capi20", NAME="capi20", GROUP="dialout"
indeed worked:
# ls -l /dev/capi20
crw-rw---- 1 root dialout 68, 0 13. Jan 09:50 /dev/capi20

great

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]