Re: [asterisk-users] BN8S0, dahdi, wcb4xxp
On Wed, Apr 28, 2010 at 07:12:57AM +0200, Claire Sinn wrote: Hi, a few month ago, I tried to install zaptel for my Beronet BN8S0 pci card... I gave up and took hfcmulti/lcr. Now dahdi (2.2.1.1) seems to support the card and I'm very interested to get it to work. But how to get rid of these annoying qozap driver? bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: wcb4xxp, hfcmulti bishop dahdi # modprobe wcb4xxp bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: wcb4xxp Kernel modules: wcb4xxp, hfcmulti bishop dahdi # dahdi_hardware -v driver should be 'qozap' but is actually 'wcb4xxp' pci::01:00.0 qozap+ 1397:16b8 Junghanns OctoBRI ISDN card Seems like the list of devices in Dahdi::Hardware::PCI is not up-to-date. -- 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] BN8S0, dahdi, wcb4xxp
Am Mittwoch, 28. April 2010 09:58:14 schrieb Tzafrir Cohen: On Wed, Apr 28, 2010 at 07:12:57AM +0200, Claire Sinn wrote: Hi, a few month ago, I tried to install zaptel for my Beronet BN8S0 pci card... I gave up and took hfcmulti/lcr. Now dahdi (2.2.1.1) seems to support the card and I'm very interested to get it to work. But how to get rid of these annoying qozap driver? bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: wcb4xxp, hfcmulti bishop dahdi # modprobe wcb4xxp bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: wcb4xxp Kernel modules: wcb4xxp, hfcmulti bishop dahdi # dahdi_hardware -v driver should be 'qozap' but is actually 'wcb4xxp' pci::01:00.0 qozap+ 1397:16b8 Junghanns OctoBRI ISDN card Seems like the list of devices in Dahdi::Hardware::PCI is not up-to-date. Sorry, what does that mean and how can I fix it temporarily? Claire -- _ -- 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] BN8S0, dahdi, wcb4xxp
Am Mittwoch, 28. April 2010 09:58:14 schrieb Tzafrir Cohen: On Wed, Apr 28, 2010 at 07:12:57AM +0200, Claire Sinn wrote: Hi, a few month ago, I tried to install zaptel for my Beronet BN8S0 pci card... I gave up and took hfcmulti/lcr. Now dahdi (2.2.1.1) seems to support the card and I'm very interested to get it to work. But how to get rid of these annoying qozap driver? bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: wcb4xxp, hfcmulti bishop dahdi # modprobe wcb4xxp bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: wcb4xxp Kernel modules: wcb4xxp, hfcmulti bishop dahdi # dahdi_hardware -v driver should be 'qozap' but is actually 'wcb4xxp' pci::01:00.0 qozap+ 1397:16b8 Junghanns OctoBRI ISDN card Seems like the list of devices in Dahdi::Hardware::PCI is not up-to-date. I tried to ignore the output of dahdi_hardware, but it seems to be more than a cosmetic problem. The half of the ports are jumpered for TE mode (port 1,2,7 and 8) and they work fine. The remaining ports are jumpered for NT use and produce a RED alarm. bishop asterisk # grep wcb4xxp /var/log/kern.log |tail -n 14 Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: probe called for b4xx... Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: PCI INT A - GSI 21 (level, low) - IRQ 21 Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Identified BeroNet BN8S0 (controller rev 1) at 00019480, IRQ 21 Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: NOTE: hardware echo cancellation has been disabled Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 1: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 2: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 3: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 4: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 5: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 6: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 7: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 8: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Did not do the highestorder stuff Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: new card sync source: port 3 Can I force wcb4xxp to configure some ports in NT mode? Clairef -- _ -- 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] BN8S0, dahdi, wcb4xxp
Am Mittwoch, 28. April 2010 16:21:44 schrieben Sie: On Wed, Apr 28, 2010 at 03:56:04PM +0200, Claire Sinn wrote: Am Mittwoch, 28. April 2010 09:58:14 schrieb Tzafrir Cohen: On Wed, Apr 28, 2010 at 07:12:57AM +0200, Claire Sinn wrote: Hi, a few month ago, I tried to install zaptel for my Beronet BN8S0 pci card... I gave up and took hfcmulti/lcr. Now dahdi (2.2.1.1) seems to support the card and I'm very interested to get it to work. But how to get rid of these annoying qozap driver? bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: wcb4xxp, hfcmulti bishop dahdi # modprobe wcb4xxp bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: wcb4xxp Kernel modules: wcb4xxp, hfcmulti bishop dahdi # dahdi_hardware -v driver should be 'qozap' but is actually 'wcb4xxp' pci::01:00.0 qozap+ 1397:16b8 Junghanns OctoBRI ISDN card Seems like the list of devices in Dahdi::Hardware::PCI is not up-to-date. I tried to ignore the output of dahdi_hardware, but it seems to be more than a cosmetic problem. The half of the ports are jumpered for TE mode (port 1,2,7 and 8) and they work fine. The remaining ports are jumpered for NT use and produce a RED alarm. bishop asterisk # grep wcb4xxp /var/log/kern.log |tail -n 14 Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: probe called for b4xx... Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: PCI INT A - GSI 21 (level, low) - IRQ 21 Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Identified BeroNet BN8S0 (controller rev 1) at 00019480, IRQ 21 Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: NOTE: hardware echo cancellation has been disabled Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 1: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 2: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 3: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 4: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 5: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 6: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 7: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Port 8: TE mode Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: Did not do the highestorder stuff Apr 28 07:03:28 bishop kernel: wcb4xxp :01:00.0: new card sync source: port 3 Can I force wcb4xxp to configure some ports in NT mode? Clairef I suspect this should be easy to fix. Any chance you can try it with the SVN version? Try test: svn checkout http://svn.digium.com/svn/dahdi/linux/trunk dahdi-linux cd dahdi-linux make # but don't install The following must be run as root: # Unload existing drivers (you may also want to stop asterisk first: /etc/init.d/dahdi stop # load local drivers: modprobe crc-ccitt # just in case it's not yet loaded insmod ./drivers/dahdi/dahdi.ko insmod ./drivers/dahdi/wcb4xxp/wcb4xxp.ko I suspect this won't fix the issue, but it will shorten the test cycle. Mission accomplished. crc-ccitt is compiled into the kernel, but not as a module. bishop dahdi-linux # dahdi_hardware -v driver should be 'qozap' but is actually 'wcb4xxp' pci::01:00.0 qozap+ 1397:16b8 Junghanns OctoBRI ISDN card Where is the difference? C.e -- _ -- 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] BN8S0, dahdi, wcb4xxp
Hi, a few month ago, I tried to install zaptel for my Beronet BN8S0 pci card... I gave up and took hfcmulti/lcr. Now dahdi (2.2.1.1) seems to support the card and I'm very interested to get it to work. But how to get rid of these annoying qozap driver? bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: wcb4xxp, hfcmulti bishop dahdi # modprobe wcb4xxp bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S] [1397:16b8] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b562] Flags: medium devsel, IRQ 21 I/O ports at 9480 [size=8] Memory at fb9bb000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: wcb4xxp Kernel modules: wcb4xxp, hfcmulti bishop dahdi # dahdi_hardware -v driver should be 'qozap' but is actually 'wcb4xxp' pci::01:00.0 qozap+ 1397:16b8 Junghanns OctoBRI ISDN card Completely confused: Clairet -- _ -- 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
