Summary: | DAHLIN-00167: [patch] typo in Junghanns QuadBRI PCI id | ||
Reporter: | Leonardo Pistone (lpistone) | Labels: | |
Date Opened: | 2009-12-15 09:42:50.000-0600 | Date Closed: | 2010-03-25 09:46:42 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | wcb4xxp |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) base.c.diff ( 1) dmesg.txt ( 2) lsdahdi.txt ( 3) lspci-nv.txt ( 4) PCI.pm.diff | |
Description: | Subsystem ID for the Junghanns QuadBRI card is 1397:b550 and not 1397:b520. | ||
Comments: | By: Tzafrir Cohen (tzafrir) 2009-12-16 12:31:41.000-0600 Just a sanity check: is the old IS valid as well? IIRC there were reports of this driver working with Junghanns cards. By: Jason Parker (jparker) 2009-12-16 14:57:33.000-0600 According to pci.ids, b520 is an HFC-4S "IOB4ST". I think simply adding b550 as another HFC-4S would be appropriate, rather than replacing b520. By: Leonardo Pistone (lpistone) 2009-12-17 08:54:07.000-0600 Reading through notes on issue 0013897, I didn't see anyone reporting success on a Junghanns QuadBRI. I only know my card was bought in 2007 and have no idea wheather there are other versions of it with different pciid's. I didn't get much success. Dahdi_tool shows my alarm status as "OK" but when I try to call I get strange error messages: dahdi_call: unrecognized prilocaldialplan NPI modifier: s where "s" is the first character of the SIP name of the device i'm using to place the call. I also configured a port as NT, but connecting it to a legacy PBX, the alarm is still RED. Tried with a isdn cross cable, but no luck: still RED. By: Olivier Krief (okrief) 2009-12-17 17:01:29.000-0600 I think 3 types of Junghanns QuadBRI exist: 1 is PCIe, 2 are PCI-based. Among those later two, one is labelled "v2.0". I can post the output of lspci, here, if needed. I may add something, I think this issue title is a bit misleading, as it mentions a typo and discussion shows other issues (error messages, ...). Even if the typo was the root cause, the title should describe the symptoms. By: Tzafrir Cohen (tzafrir) 2009-12-17 17:20:18.000-0600 I still think it's a typo. But please do provide the output of lspci (-v) from those cards. By: Leonardo Pistone (lpistone) 2009-12-21 03:30:16.000-0600 I mentioned the other issues just to make clear that after correcting the typo, the card is recognized but still doesn't really work. Maybe I could open another bug about the other issues? Thanks By: Tzafrir Cohen (tzafrir) 2009-12-21 03:58:53.000-0600 What doesn't work exactly? What does? Does it register DAHDI spans for the ports of the card? What's the output of lsdahdi ? Could you provide relevant dmesg lines? By: Leonardo Pistone (lpistone) 2009-12-21 05:16:36.000-0600 Attached relevant dmesg and lsdahdi output. Span 1 (TE) is connected to a Telecom Italia line. Span 3 (NT) is connected to a Samsung PBX. 2 and 4 not connected. If I try to dial out to Telecom Italia, I get cause 34 - Circuit/channel congestion. By: Olivier Krief (okrief) 2009-12-21 12:33:24.000-0600 Before patching anything (Dahdi, ...) with Dahdi revision 7672, my Junghanns is a PCIexpress QuadBRI, with ports 1 and 2, in TE/ptp, and Ports 3 and 4, in NT/ptp, with jumpers set appropriately : # lspci -v -nn -s 06:04.0 06:04.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] [1397:08b4] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b752] Flags: medium devsel, IRQ 11 I/O ports at ec00 [size=8] Memory at feaff000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 # lspci -v -nn -s 06:04.0 06:04.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] [1397:08b4] (rev 01) Subsystem: Cologne Chip Designs GmbH Device [1397:b752] Flags: medium devsel, IRQ 11 I/O ports at ec00 [size=8] Memory at feaff000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 # cat /etc/dahdi/system.conf # Autogenerated by /usr/sbin/dahdi_genconf on Wed Dec 16 16:37:55 2009 # If you edit this file and execute /usr/sbin/dahdi_genconf again, # your manual changes will be LOST. # Dahdi Configuration File # # This file is parsed by the Dahdi Configurator, dahdi_cfg # # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) span=1,1,0,ccs,ami # termtype: te bchan=1-2 hardhdlc=3 echocanceller=oslec,1-2 # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" span=2,2,0,ccs,ami # termtype: te bchan=4-5 hardhdlc=6 echocanceller=oslec,4-5 # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" span=3,0,0,ccs,ami # termtype: nt bchan=7-8 hardhdlc=9 echocanceller=oslec,7-8 # Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" span=4,0,0,ccs,ami # termtype: nt bchan=10-11 hardhdlc=12 echocanceller=oslec,10-11 # Global data loadzone = fr defaultzone = fr Is there any missing data to add this card to the list of Dahdi supported hardware ? By: Olivier Krief (okrief) 2009-12-23 01:21:02.000-0600 If this helps, I can dedicate a Lenny box with a Junghanns PCIe QuadBRI (or a PCI OctoBRI) with SSH remote access, for testing. As I can't provide ISDN lines, plugging one BRI port to another (in PtP) could possible. By: Digium Subversion (svnbot) 2010-03-25 09:43:32 Repository: dahdi Revision: 8421 U linux/trunk/drivers/dahdi/wcb4xxp/base.c ------------------------------------------------------------------------ r8421 | tzafrir | 2010-03-25 09:43:29 -0500 (Thu, 25 Mar 2010) | 10 lines Some more wcb4xxp PCI IDs for Junghanns cards Resolve two open issues. One of them that accidentally wasn't closed. (closes issue DAHLIN-122) (closes issue DAHLIN-167) Reported by: lpistone Tested by: okrief ------------------------------------------------------------------------ http://svn.digium.com/view/dahdi?view=rev&revision=8421 By: Digium Subversion (svnbot) 2010-03-25 09:46:42 Repository: dahdi Revision: 8422 U tools/trunk/xpp/perl_modules/Dahdi/Hardware/PCI.pm ------------------------------------------------------------------------ r8422 | tzafrir | 2010-03-25 09:46:41 -0500 (Thu, 25 Mar 2010) | 8 lines Some more wcb4xxp PCI IDs for Junghanns cards (issue DAHLIN-122) (issue DAHLIN-167) Reported by: lpistone Tested by: okrief ------------------------------------------------------------------------ http://svn.digium.com/view/dahdi?view=rev&revision=8422 |