astlinux-devel Mailing List for AstLinux

The AstLinux Team would like to announce the immediate availability of
the 0.7.8 release.  This release includes either Asterisk 1.4.41 or
Asterisk 1.8.4.  All current users are encouraged to upgrade to this
release to take advantage of bug fixes and other updates to Asterisk.

Please note that there is a bug in Asterisk 1.8.4 that will prevent
Cisco 79xx phones from registering.

A full changelog is available at http://www.astlinux.org

Current users can upgrade from the web interface or from the commandline.

>From the CLI:

(Asterisk 1.4)
  upgrade-run-image check http://mirror.astlinux.org/firmware
  --should report astlinux-0.7.8
  upgrade-run-image upgrade http://mirror.astlinux.org/firmware

(Asterisk 1.8)
  upgrade-run-image check http://mirror.astlinux.org/ast18-firmware
  --should report astlinux-0.7.8
  upgrade-run-image upgrade http://mirror.astlinux.org/ast18-firmware


--
The AstLinux Team
http://www.astlinux.org

Devs,

Any reason not to enable CONFIG_8139CP in all the linux.config's ?

It is interesting that "8139cp" is already defined in all of the targets /etc/rc.modules file, enabled for geni586 (obviously fails).

If yes for above, should the geni586 /etc/rc.modules have both 8139too and 8139cp enabled by default (as it is now), or only the 8139too by default ?

Lonnie

PS: Graham has his Viking card working with AstLinux 0.7.7 using 8139too.  He submitted a WiKi to me.


Begin forwarded message:

> From: Lonnie Abelbeck <li...@lo...>
> Date: May 5, 2011 7:03:21 AM CDT
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] 8139cp driver for Traverse Technologies Viking ADSL2+
> Reply-To: AstLinux Users Mailing List <ast...@li...>
> 
> Hi Graham,
> 
> Yes, in the linux.config kernel config, we do not enable
> --
> # CONFIG_8139CP is not set
> --
> for any of our builds, in the 2.6.27 kernel this driver is labeled as (EXPERIMENTAL).
> 
> I don't have any practical experience with the RealTek 8139 drivers.  It may not make any difference for your application.  I would definitely give the 8139too driver a try and see how it goes.
> 
> It would be easy enough to enable the 8139CP driver across all our supported targets.
> 
> Please, any users or devs have an opinion why suppling the 8139CP driver module is a good/bad idea.
> 
> Lonnie
> 
> 
> On May 5, 2011, at 2:00 AM, Graham S. Jarvis wrote:
> 
>> Thanks Lonnie for your help so far!
>> 
>> 
>> Where do I get a good 8139cp driver and where do I post a request that it be
>> added to the next Astlinux
>> release?
>> 
>> I'm using 0.7.7 and the 8139too driver loads the Viking card.
>> But, dmesg says "Use the "8139cp" driver for improved performance and stability."
>> 
>> astlinux# dmesg|grep 8139
>> 8139too Fast Ethernet driver 0.9.28
>> 8139too 0000:02:04.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip
>> 8139too 0000:02:04.0: Use the "8139cp" driver for improved performance and
>> stability.
>> 8139too 0000:02:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> 8139too 0000:02:04.0: unknown chip version, assuming RTL-8139
>> 8139too 0000:02:04.0: TxConfig = 0x74800000
>> eth1: RealTek RTL8139 at 0xd082a000, 00:0a:fa:20:04:84, IRQ 16
>> eth1:  Identified 8139 chip type 'RTL-8139'
>> 
>> It's not on the 0.7.7 release file system:
>> 
>> astlinux# find / -name "8139*"
>> /sys/bus/pci/drivers/8139too
>> /sys/module/mii/holders/8139too
>> /sys/module/8139too
>> /oldroot/mnt/asturo/lib/modules/2.6.27.49-astlinux/kernel/drivers/net/8139too.ko
>> /lib/modules/2.6.27.49-astlinux/kernel/drivers/net/8139too.ko
>> 
>> 
>> Thanks!
>> 
>> -Graham-

For the record, I have been able to get the iLBC codec to build and work on
Astlinux.  You have to download the iLBC source and there is a script to do
this in the asterisk source.  I added this line to the package/asterisk/
asterisk.mk file...

    (cd $(ASTERISK_DIR); echo | ./contrib/scripts/get_ilbc_source.sh)

At around line 186 (just before the $(ASTERISK_DIR)/.configured: statement)

This downloads the source for iLBC, but it will not build by default.  You
need a patch to codec_ilbc.c file to enable it, which I placed in
package/asterisk/asterisk-1.4-ilbc.patch.  Though the same patch should work
just fine for 1.8 as well.

diff -rup asterisk-1.4.41-a/codecs/codec_ilbc.c
asterisk-1.4.41-b/codecs/codec_ilbc.c
--- asterisk-1.4.41-a/codecs/codec_ilbc.c    2009-11-06 12:07:13.000000000
-0500
+++ asterisk-1.4.41-b/codecs/codec_ilbc.c    2011-04-30 11:42:34.261303001
-0400
@@ -26,7 +26,7 @@
  */

 /*** MODULEINFO
-    <defaultenabled>no</defaultenabled>
+    <defaultenabled>yes</defaultenabled>
  ***/

 #include "asterisk.h"



David

Does anyone know if it would be possible to get the asterisk gtalk channel
to work on astlinux?  It appears to be dependent upon iksemel, which is
itself dependent upon libgnutils and possibly others.  Does anyone know
anything about either of these packages and whether they could be got to
work on Astlinux?

Thank,
David