Bug#413042: zaptel-source: AMD64 KernelFlag

[Karl Schmidt]

Tzafrir Cohen wrote:
> On Thu, Mar 01, 2007 at 02:02:13PM -0600, Karl Schmidt wrote:
> 
>> I think I got things working on AMD64 by adding this kernel flag This needs 
>> verification as I didn't go back and break it again. I found the fix at:
>>
>> http://www.voip-info.org/wiki/index.php?page=zaptel-x86_64  Which said:
>>
>>> I asked Digium sales support about compiling Zaptel on an AMD64 / x86_64 
>> / SMP Opteron system prior to buying a card from them. Their response was:
> 
> Have you had problems either building or using the package as-is with
> amd64?

At first didn't work - I added the flag and it did work - but I am only 95% sure that was 
the only thing changed. My hunch is someone needs to look into what that flag is about that 
understands kernelflags better than I do. I don't think Digium would have told him to add it 
without a good reason. I've copied others asking about the same issue I found on Google - I 
really can't test right now as this system is already live - perhaps one of the others can? 
I was hoping someone would have a contact inside Digium.

grep for amd64 in the changelogs has nothing. The date of that post was Sep of 2005 - not so 
long ago and the amd64 issue is new with etch...

It is working with the change


Re:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413042
http://www.voip-info.org/wiki/index.php?page=zaptel-x86_64

Some more links on zaptel and AMD64 ---

http://threebit.net/mail-archive/asterisk-bsd/msg00014.html
http://www.arcknowledge.com/gmane.comp.telephony.pbx.asterisk.devel/2004-09/msg00037.html
http://lists.digium.com/pipermail/asterisk-bsd/2005-November/001333.html




----------------------------------------------------------------
Karl Schmidt                         EMail Karl at xtronics.com
Transtronics, Inc.                     WEB http://xtronics.com
3209 West 9th Street                    Ph (785) 841-3089
Lawrence, KS 66049                     FAX (785) 841-0434

When everything is coming my way, I'm probably in the wrong lane.

----------------------------------------------------------------