Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Sun, 30 May 2010 02:45:51 +0300, Tzafrir Cohen tzafrir.co...@xorcom.com wrote: 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. [Snip details] If nobody beats me to it, I'll try submitting a (untested) extended list of exceptions over the weekend. Submitted: http://marc.info/?l=linux-netdevm=127517632426217w=2 That said, I believe it would help if we also had explicit sub product IDs to exclude, rather than just exclude by sub vendor ID. The sub-product ID is listed in e.g. the output of lspci -v: (I use -s below to get just a single device this time) tzaf...@sweetmorn:~$ lspci -s 0c:00.0 -vn 0c:00.0 0280: 8086:4229 (rev 61) Subsystem: 8086:1121 Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at fe8fe000 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlagn tzaf...@sweetmorn:~$ lspci -s 0c:00.0 -vnn 0c:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61) Subsystem: Intel Corporation Device [8086:1121] Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at fe8fe000 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlagn The Subsystem line has sub-vendor-ID:sub-product-ID. Thus for this device the sub-product ID is 1121. FWIW, here's the output of lspci -vv on an OpenVox A400P with a single FXO module: == 03:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Device b100:0003 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (250ns min, 32000ns max) Interrupt: pin A routed to IRQ 20 Region 0: I/O ports at a000 [size=256] Region 1: Memory at e200 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: wctdm Kernel modules: wctdm, hisax, netjet == HTH, -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Thu, May 27, 2010 at 12:29:05PM +0300, Tzafrir Cohen wrote: On Wed, May 26, 2010 at 09:52:52PM +0200, Vincent wrote: On Wed, 26 May 2010 17:30:08 +0200, Vincent codecompl...@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. [Snip details] If nobody beats me to it, I'll try submitting a (untested) extended list of exceptions over the weekend. Submitted: http://marc.info/?l=linux-netdevm=127517632426217w=2 That said, I believe it would help if we also had explicit sub product IDs to exclude, rather than just exclude by sub vendor ID. The sub-product ID is listed in e.g. the output of lspci -v: (I use -s below to get just a single device this time) tzaf...@sweetmorn:~$ lspci -s 0c:00.0 -vn 0c:00.0 0280: 8086:4229 (rev 61) Subsystem: 8086:1121 Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at fe8fe000 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlagn tzaf...@sweetmorn:~$ lspci -s 0c:00.0 -vnn 0c:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61) Subsystem: Intel Corporation Device [8086:1121] Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at fe8fe000 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwlagn The Subsystem line has sub-vendor-ID:sub-product-ID. Thus for this device the sub-product ID is 1121. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Wed, May 26, 2010 at 09:52:52PM +0200, Vincent wrote:
On Wed, 26 May 2010 17:30:08 +0200, Vincent codecompl...@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.co...@xorcom.com
+972-50-7952406 mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
DON'T RUN dahdi_genconf, as it overwrites system.conf. Yes. dahdi_genconf reads /etc/dahdi/genconf_parameters and writes /etc/dahdi/system.conf and /etc/asterisk/dahdi_channels.conf. You can set the country as lc_country fr in /etc/dahdi/genconf_parameters. 1. When I run dahdi_genconf: /usr/sbin/dahdi_genconf: Failed to open /etc/asterisk/dahdi-channels.conf: No such file or directory Do you have asterisk installed? You neet at least to mkdir /etc/asterisk. Ciao Leo -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Thu, 27 May 2010 12:29:05 +0300, Tzafrir Cohen tzafrir.co...@xorcom.com wrote: 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. Thanks for the explanation. On this exact same hardware, I didn't have this problem with Dahdi/Zaptel 1.4. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Thu, 27 May 2010 11:41:09 +0200, Leonardo Pistone l.pist...@sispac.it wrote: Yes. dahdi_genconf reads /etc/dahdi/genconf_parameters and writes /etc/dahdi/system.conf and /etc/asterisk/dahdi_channels.conf. Thanks for the tip. Do you have asterisk installed? You neet at least to mkdir /etc/asterisk. Nope, and running mkdir /etc/asterisk solved this issue. There's one thing left: # /etc/init.d/dahdi restart Unloading DAHDI hardware modules: done Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing astribank_is_starting Running dahdi_cfg: [ OK ] I assume this reference to astribank is due to default settings. How can I remove unneeded drivers/modules? Thank you. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Thu, May 27, 2010 at 03:03:21PM +0200, Vincent wrote: On Thu, 27 May 2010 12:29:05 +0300, Tzafrir Cohen tzafrir.co...@xorcom.com wrote: 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. Thanks for the explanation. On this exact same hardware, I didn't have this problem with Dahdi/Zaptel 1.4. Older kernel did not have the netjet module? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Thu, 27 May 2010 16:12:57 +0300, Tzafrir Cohen tzafrir.co...@xorcom.com wrote: Thanks for the explanation. On this exact same hardware, I didn't have this problem with Dahdi/Zaptel 1.4. Older kernel did not have the netjet module? Yup, that could be the reason. Anyway, problem solved :-) Thank you. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Thu, 27 May 2010 15:09:45 +0200, Vincent codecompl...@free.fr wrote: /usr/share/dahdi/waitfor_xpds: Missing astribank_is_starting Running dahdi_cfg: [ OK ] it's harmless. but it's a symtom of building dahdi-tools without libusb https://issues.asterisk.org/view.php?id=17189 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
Hello I'm trying to install Dahdi through source code on a Fedora 13 host to use an OpenVox PCI card with a single FXO port, but dahdi_cfg -vv isn't happy. 1. After successfully running make all; make install; make config, I edited /etc/dahdi/system.conf thusly: loadzone=fr defaultzone=fr fxsks=1 2. Then ran dahdi_cfg -vv which says: - DAHDI Tools Version - 2.3.0 DAHDI Version: 2.3.0 Echo Canceller(s): Configuration == Channel map: Channel 01: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 01) 1 channels to configure. DAHDI_CHANCONFIG failed on channel 1: No such device or address (6) - 3. So I ran lscpi -v: 03:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Device b100:0003 Flags: bus master, medium devsel, latency 64, IRQ 20 I/O ports at a000 [size=256] Memory at e200 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: netjet Kernel modules: wctdm, hisax, netjet FWIW, when I run modprobe wctdm followed by lsmod: # lsmod Module Size Used by wctdm 31892 0 dahdi 180789 1 wctdm netjet 12563 0 isdnhdlc3343 1 netjet crc_ccitt 1217 2 dahdi,isdnhdlc mISDNipac 28346 1 netjet mISDN_core 61414 3 netjet,mISDNipac I'm not sure whether I should use the wctdm driver or this netjet driver which I've never seen before. Could it be that dahdi_genconf modules added some ISDN-related items that I don't need? Thank you. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Wed, 26 May 2010 17:17:08 +0200, Vincent codecompl...@free.fr wrote: I'm trying to install Dahdi through source code on a Fedora 13 host to use an OpenVox PCI card with a single FXO port, but dahdi_cfg -vv isn't happy. More information, as I investigate: # vi /etc/modprobe.d/dahdi.blacklist.conf #blacklist wct4xxp #blacklist wcte12xp #blacklist wct1xxp #blacklist wcte11xp #blacklist wctdm24xxp #blacklist wcfxo blacklist wctdm #blacklist wctc4xxp #blacklist wcb4xxp # /etc/init.d/dahdi stop Unloading DAHDI hardware modules: done # /etc/init.d/dahdi start Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing astribank_is_starting No hardware timing source found in /proc/dahdi, loading dahdi_dummy Running dahdi_cfg: DAHDI_CHANCONFIG failed on channel 1: No such device or address (6) [FAILED] -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [Dahdi] DAHDI_CHANCONFIG failed on channel 1?
On Wed, 26 May 2010 17:30:08 +0200, Vincent codecompl...@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 2. To configure Dahdi, edit /etc/dahdi/system.conf: #For France loadzone= fr defaultzone = fr fxsks = 1 Next, start Dahdi... /etc/init.d/dahdi start ... and check /var/log/messages. DON'T RUN dahdi_genconf, as it overwrites system.conf. == I still have a couple of issues left: 1. When I run dahdi_genconf: /usr/sbin/dahdi_genconf: Failed to open /etc/asterisk/dahdi-channels.conf: No such file or directory 2. /etc/init.d/dahdi start: Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing astribank_is_starting Running dahdi_cfg: [ OK ] Thank you. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
