Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
How to get DAHDI working with kernel 4.13
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
Fog_Watch
Apprentice
Apprentice


Joined: 24 Jul 2006
Posts: 190
Location: Utility Muffin Research Kitchen

PostPosted: Mon Nov 06, 2017 10:30 pm    Post subject: How to get DAHDI working with kernel 4.13 Reply with quote

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
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 11434

PostPosted: Wed Nov 08, 2017 2:42 am    Post subject: Reply with quote

What problem(s) preclude using the Portage ebuild for this package, possibly with these patches auto-applied by the ebuild?
Back to top
View user's profile Send private message
Fog_Watch
Apprentice
Apprentice


Joined: 24 Jul 2006
Posts: 190
Location: Utility Muffin Research Kitchen

PostPosted: Thu Nov 09, 2017 4:00 am    Post subject: Reply with quote

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
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 11434

PostPosted: Fri Nov 10, 2017 2:11 am    Post subject: Reply with quote

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
View user's profile Send private message
Fog_Watch
Apprentice
Apprentice


Joined: 24 Jul 2006
Posts: 190
Location: Utility Muffin Research Kitchen

PostPosted: Fri Nov 10, 2017 4:12 am    Post subject: Reply with quote

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
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum