| View previous topic :: View next topic |
| Author |
Message |
Fog_Watch
Apprentice
Joined: 24 Jul 2006
Posts: 268
Location: Utility Muffin Research Kitchen
|
 Posted: Mon Nov 06, 2017 10:30 pm Post subject: How to get DAHDI working with kernel 4.13 |
 |
|
What follows is a dirty way of getting DAHDI working with a new 4.13 kernel. The instructions worked for me today, but tomorrow who knows.
They are a slight variation of the OSLEC instructions and patching:
Make sure /usr/src/linux is linked properly.
| Code: | cd #somewhere sensible
wget https://github.com/asterisk/dahdi-linux/archive/next.zip
unzip next.zip
cd dahdi-linux-next/
mkdir drivers/staging
cp -fR /usr/src/linux/drivers/misc/echo drivers/staging
sed -i "s|#obj-m += dahdi_echocan_oslec.o|obj-m += dahdi_echocan_oslec.o|" drivers/dahdi/Kbuild
sed -i "s|#obj-m += ../staging/echo/|obj-m += ../staging/echo/|" drivers/dahdi/Kbuild
echo 'obj-m += echo.o' > drivers/staging/echo/Kbuild |
| Code: | wget https://issues.asterisk.org/jira/secure/attachment/56083/dev_attrs_groups-v3.patch
patch -p1 < dev_attrs_groups-v3.patch
make
make install |
| Code: | /etc/init.d/asterisk stop
/etc/init.d/dahdi-autoconf restart
/etc/init.d/dahdi restart
/etc/init.d/asterisk start |
|
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23066
|
| Posted: Wed Nov 08, 2017 2:42 am Post subject: |
|
|
| What problem(s) preclude using the Portage ebuild for this package, possibly with these patches auto-applied by the ebuild? |
|
| Back to top |
|
|
Fog_Watch
Apprentice
Joined: 24 Jul 2006
Posts: 268
Location: Utility Muffin Research Kitchen
|
| Posted: Thu Nov 09, 2017 4:00 am Post subject: |
|
|
| I believe that the only way of circumventing this error is to use the unfathomably named next.zip, which in turn needs to be patched. That is, emerging dahdi-2.11.1.ebuild returns the error implicit declaration of function ‘touch_softlockup_watchdog’. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23066
|
| Posted: Fri Nov 10, 2017 2:11 am Post subject: |
|
|
| Then isn't the solution to create an ebuild that sets the poorly named next.zip as its SRC_URI, to then put an appropriate patch in $FILESDIR, and to use eapply to apply that patch automatically? This would save users both the trouble of performing those steps by hand and the uncertainty of using unverified downloads. |
|
| Back to top |
|
|
Fog_Watch
Apprentice
Joined: 24 Jul 2006
Posts: 268
Location: Utility Muffin Research Kitchen
|
| Posted: Fri Nov 10, 2017 4:12 am Post subject: |
|
|
| Hu wrote: | | create an ebuild |
Well, yes, but that puts a hurt on my brain. One day I'll make an ebuild. |
|
| Back to top |
|
|
Fog_Watch
Apprentice
Joined: 24 Jul 2006
Posts: 268
Location: Utility Muffin Research Kitchen
|
| Posted: Thu Feb 08, 2018 12:53 am Post subject: |
|
|
For kernel 4.15, in addition to dev_attrs_groups-v3.patch:
| Code: | wget https://issues.asterisk.org/jira/secure/attachment/56745/0001-xpp-move-command_timer-functions-to-xbus-core.patch
wget https://issues.asterisk.org/jira/secure/attachment/56746/0002-fix-building-with-4.15-init_timer-setup_timer.patch
patch -p1 < 0001-xpp-move-command_timer-functions-to-xbus-core.patch
patch -p1 < 0002-fix-building-with-4.15-init_timer-setup_timer.patch
|
And one other thing, boot into the new kernel before building DAHDI.
Fog_Watch. |
|
| Back to top |
|
|
jkroon
Tux's lil' helper
Joined: 15 Oct 2003
Posts: 110
Location: South Africa
|
| Posted: Fri Jun 08, 2018 11:47 am Post subject: |
|
|
https://bugs.gentoo.org/617876
Please use the bug reporting system to deal with such issues. We really do try but can't monitor the forums too. Just found this by accident looking for a fix for this too.
_________________
There are 10 kinds of people in the world,
those who understand binary and who don't |
|
| Back to top |
|
|
PatG
n00b
Joined: 27 Oct 2003
Posts: 63
Location: texas
|
| Posted: Sun Oct 21, 2018 1:40 am Post subject: this post saved me |
|
|
One correction, the second patch set has an incorrect jira location. It should read
| Code: | | wget https://issues.asterisk.org/jira/secure/attachment/57149/0002-fix-building-with-4.15-init_timer-setup_timer.patch |
|
|
| Back to top |
|
|
|
Documentation, Tips & Tricks
