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

[Alex Regan (JIRA)]

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

Alex Regan edited comment on DAHLIN-368 at 4/28/19 9:14 PM:
------------------------------------------------------------

I have the following in  /etc/dahdi/assigned-spans.conf, which says it was autogenerated in 2017.
      /sys/devices/pci0000:00/0000:00:03.2/0000:04:00.0/0000:05:00.0/pci:0000:05:00.0 1:1:1

I also have /etc/modprobe.d/dahdi.conf with the options you've listed.

There isn't anyone who knows for sure whether this works with a 5.0 kernel?

I also saw a comment about that the timekeeping interface in 5.0 changed, but now can't find it? Does this pertain to this problem?

I have the Tiger3XX card that I believe uses the wctdm driver, but it is not loaded. dahdi also was not loaded after reboot.

[code]05:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
        Subsystem: ATCOM Technology co., LTD. Device 0001
        Flags: bus master, medium devsel, latency 64, IRQ 11, NUMA node 0
        I/O ports at d000 [size=256]
        Memory at fb200000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2
        Kernel modules: hisax[/code]

I used to be much more involved with kernel development, but now just need something that works. I'm really hoping you guys can confirm whether this works on 5.0 and the steps I need to make it work. I'd appreciate any ideas you may have. This has all "just worked" without much fuss since I did the migration to the new dahdi format in like 2010, lol.






was (Author: gossamer):
I have the following in  /etc/dahdi/assigned-spans.conf, which says it was autogenerated in 2017.
[code]/sys/devices/pci0000:00/0000:00:03.2/0000:04:00.0/0000:05:00.0/pci:0000:05:00.0 1:1:1[/code]

I also have /etc/modprobe.d/dahdi.conf with the options you've listed.

There isn't anyone who knows for sure whether this works with a 5.0 kernel?

I also saw a comment about that the timekeeping interface in 5.0 changed, but now can't find it? Does this pertain to this problem?

I have the Tiger3XX card that I believe uses the wctdm driver, but it is not loaded. dahdi also was not loaded after reboot.

[code]05:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
        Subsystem: ATCOM Technology co., LTD. Device 0001
        Flags: bus master, medium devsel, latency 64, IRQ 11, NUMA node 0
        I/O ports at d000 [size=256]
        Memory at fb200000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2
        Kernel modules: hisax[/code]

I used to be much more involved with kernel development, but now just need something that works. I'm really hoping you guys can confirm whether this works on 5.0 and the steps I need to make it work. I'd appreciate any ideas you may have. This has all "just worked" without much fuss since I did the migration to the new dahdi format in like 2010, lol.





> 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)