The zaptel runs this check to make sure your kernel is built with RTC if you have the rtc useflag enabled: if ! linux_chkconfig_present RTC; then eerror "rtc: Your kernel lacks RealTime-Clock support!" result=$((result+1)) fi under PPC, the RTC kernel config option is called GEN_RTC. So the x86-specific check always fails. I was able to successfully build and run zaptel 1.2.1 under PPC with rtc enabled by setting the config check to GEN_RTC. I only tested it for about a half hour under very little load, but it seems to work ok. In fact, when i loaded the RTC-driven zaptel drivers, i dropped calls like crazy. It wasn't until i noticed a T1 timing mis-configuration on my zaptel.conf file that was causing intermittent dropped calls.
I can't say for sure if forcing the ebuild to ignore the RTC option is stable or not on PPC. We had intermittant T1 issues the last two weeks at the office, so i haven't been able to test.
Rob, did adding a check for GEN_RTC fix the problem for you?
I had other unrelated stability issues with my PPC-based asterisk install, so i never got a chance to test out the GEN_PPC ebuild hack. doing google searches for PPC RTC linux and such, i came across this article: http://www.informit.com/articles/article.asp?p=414983&seqNum=4&rl=1 I'm not very versed on kernel hacking, but it seems like using the PPC's GEN_RTC isn't a 1:1 replacement for X86-RTC. "The ioctl() control functions are listed in include/linux/rtc.h. At this writing[nov2005], not all the ioctl() calls for the RTC are implemented for the PPC architecture. These control functions each call lower-level hardware-specific functions (if implemented). The example in this section uses the RTC_RD_TIME function."
Alright, I guess we'll close this "WONTFIX" for now. Feel free to reopen if you think this the wrong thing to do. :)
