[asterisk-users] [Dahdi] "DAHDI_CHANCONFIG failed on channel 1"?

[Tzafrir Cohen]

On Wed, May 26, 2010 at 09:52:52PM +0200, Vincent wrote:
> On Wed, 26 May 2010 17:30:08 +0200, Vincent <codecomplete at free.fr>
> wrote:
> >More information, as I investigate:
> 
> For those having the same issue, here's what I learned:
> 
> 1. In /etc/modprobe.d/dahdi.blacklist.conf, blacklist the "netjet"
> driver:
> 
> blacklist netjet

This is a bug of the netjet module. It should not try to handle those
devices. While they use the netjet chipset, they are not the ISDN BRI
devices drivven by it.

Looking at drivers/isdn/hardware/mISDN/netjet.c:

/* We cannot select cards with PCI_SUB... IDs, since here are cards with
 * SUB IDs set to PCI_ANY_ID, so we need to match all and reject
 * known other cards which not work with this driver - see probe
 * function */
static struct pci_device_id nj_pci_ids[] __devinitdata = {
        { PCI_VENDOR_ID_TIGERJET, PCI_DEVICE_ID_TIGERJET_300,
          PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
        { }
};
MODULE_DEVICE_TABLE(pci, nj_pci_ids);


And indeed, nj_probe() above has:

        struct tiger_hw *card;

        if (pdev->subsystem_vendor == 0x8086 &&
            pdev->subsystem_device == 0x0003) {
                pr_notice("Netjet: Digium X100P/X101P not handled\n");
                return -ENODEV;
        }

        if (pdev->subsystem_vendor == 0x55 &&
            pdev->subsystem_device == 0x02) {
                pr_notice("Netjet: Enter!Now not handled yet\n");
                return -ENODEV;
        } 

But sadly, only those.

If nobody beats me to it, I'll try submitting a (untested) extended list
of exceptions over the weekend.

For an initial list:

   grep -i e159 xpp/perl_modules/Dahdi/Hardware/PCI.pm

from the top-level directory of DAHDI-tools.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir