[asterisk-users] BN8S0, dahdi, wcb4xxp

Claire Sinn hlx at h3c.de
Wed Apr 28 08:56:04 CDT 2010


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:0000: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 0000:01:00.0: probe called for b4xx...
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: PCI INT A -> GSI 21 
(level, low) -> IRQ 21
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Identified BeroNet BN8S0 
(controller rev 1) at 0000000000019480, IRQ 21
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: NOTE: hardware echo 
cancellation has been disabled
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 1: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 2: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 3: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 4: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 5: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 6: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 7: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Port 8: TE mode
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: Did not do the 
highestorder stuff
Apr 28 07:03:28 bishop kernel: wcb4xxp 0000:01:00.0: new card sync source: 
port 3

Can I force wcb4xxp to configure some ports in NT mode?
Clairef



More information about the asterisk-users mailing list