Summary: | net-misc/zaptel-1.2.8 rtc problems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Timo Gurr (RETIRED) <tgurr> |
Component: | New packages | Assignee: | voip herd (OBSOLETE) <voip+disabled> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | mlspamcb, timmy |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Timo Gurr (RETIRED)
![]() 1.2.8 is bugguy ! I had to downgrade to 1.2.7, because my TD400P didn't work anymore with it. But, 1.2.7 isn't anymore in portage. A chance for me, I saved my modules before upgrading to 1.2.8. I just put them in /lib/modules/2.6.17-gentoo-r7/misc/ And asterisk-1.2.9_p1 is bugguy to, zapbarge doesn't work anymore with it. We really need lastest versions 1.2.12.1 and zaptel 1.2.9.1. rtc should be a flag at least on linux 2.4 kernels where it can't build ztdummy. Also the CRC_CCITT checking on v2.4 kernels is flawed. an finaly, the modules.conf from /etc should be copied to the image BEFORE the make INSTALL_PREFIX=${D}..... appears or else it fails on a v2.4 build. On a V2.4 kernel the check shoulc be for CONFIG_CRC32 if needed. *** Bug 153832 has been marked as a duplicate of this bug. *** I'm not convinced that Bug 153832 is a duplicate of this bug. Basically for x86 and AMD64 on kernel 2.6, rtc support is always enabled, regardless of your rtc USE flag setting. USE_RTC is #defined at about line 50 of ztdummy.c. zaptel 1.2.22.1 in cvs. please reopen if this is still a problem. |