[asterisk-bugs] [JIRA] (DAHLIN-368) DAHDI fails to build against kernel 5.0

[Anthony Messina (JIRA)]

    [ https://issues.asterisk.org/jira/browse/DAHLIN-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247030#comment-247030 ] 

Anthony Messina commented on DAHLIN-368:
----------------------------------------

Alex, the DAHDI init scripts haven't been necessary for a while.  Most of this is handled by udev and whatever configuration you have in /etc/dahdi/assigned-spans.conf

For example, you would find out where your device is in the sysfs interface and enter something like the following in /etc/dahdi/assigned-spans.conf -- whatever matches your card (see /etc/assigned-spans.conf.sample)
{code}
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:08.0/pci:0000:02:08.0 1:1:
{code}

Then in /etc/modprobe.d/dahdi.conf
{code}
options dahdi auto_assign_spans=0
{code}

Check into http://docs.tzafrir.org.il/dahdi-linux/#_span_assignments -- I am not an expert in the best way to handle this, but the above has worked for me with single and multiple devices for years now.  Also, beware of https://issues.asterisk.org/jira/browse/DAHTOOL-82 -- you may need to edit some of the udev scripts (I haven't yet fixed these via packaging since I'm hoping upstream will be getting some of this done).

I began configuring these devices explicitly a while back since for a time, I had multiple DAHDI devices.

It looks like you already grabbed dahdi-tools from https://copr.fedorainfracloud.org/coprs/amessina/telephony

Alternatively, you could create the systemd.service file yourself based on the upstream sources.

> DAHDI fails to build against kernel 5.0
> ---------------------------------------
>
>                 Key: DAHLIN-368
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-368
>             Project: DAHDI-Linux
>          Issue Type: Bug
>      Security Level: None
>          Components: dahdi (the module)
>    Affects Versions: 3.0.0
>            Reporter: Shaun Ruffell
>            Assignee: Keith Morgan
>
> Linux kernel 5.0 has changed the timekeeping interfaces to fix the 2038 problem.
> I believe the drivers should be standardized on ktime for internal time, but before making any changes to the app drivers, I was looking for some early feedback on the proposed approach.
> The work is currently at http://git.asterisk.org/gitweb/?p=team/sruffell/dahdi-linux.git;a=shortlog;h=refs/heads/for-5.0 if anyone has any comments.



--
This message was sent by Atlassian JIRA
(v6.2#6252)