[asterisk-users] Trying to configure xorcom on Suse 11

[Tim Panton]

On 29 Mar 2010, at 08:13, Tzafrir Cohen wrote:

> On Sun, Mar 28, 2010 at 09:16:48PM -0500, Tim Panton wrote:
>> 
>> On 28 Mar 2010, at 10:13, Tzafrir Cohen wrote:
>> 
>>> On Sat, Mar 27, 2010 at 04:48:41PM -0500, Tim Panton wrote:
>>>> I'm having trouble getting a xorcom set up.
>>>> 
>>>> A large part of the problem is that the box is a _long_ way away and 
>>>> I can't get to/at it easily, so while I could probably fix this in a few
>>>> hours if the machine were in front of me, I'm struggling over a slow
>>>> unreliable laggy link. 
>>>> 
>>>> Ok, enough whining from me.
>>>> 
>>>> I have a new Xorcom plugged into the usb of a Suse 11 machine
>>>> I built Dahdi from trunk (last thursday) 
>>>> 
>>>> # svn checkout http://svn.digium.com/svn/dahdi/linux/trunk dahdi-linux
>>>> # svn checkout http://svn.digium.com/svn/dahdi/tools/trunk dahdi-tools
>>>> 
>>>> dahdihardware -v sees the box but no spans.
>>> 
>>> Generally '/etc/init.d/dahdi start' . Or more specifically,
>>> 'dahdi_registration on' .
>>> 
>>> See also:
>>> 
>>> http://docs.tzafrir.org.il/dahdi-tools/README.Astribank.html#_installation_scenarios
>> 
>> 
>> I've must be missing something here - this is what I see now.....
>> 
>> sh-4.0# dahdi_hardware -v
>> usb:001/020          xpp_usb+     e4e4:1162 Astribank-modular FPGA-firmware
>> LABEL=[usb:X1037246]       CONNECTOR=@usb-0000:00:1a.7-4 
>> 
>> Shouldn't I see spans ??? I think the box (I've never seen it, but I know what I asked for) 
>> has 8fxs+8fxo+2E1 . 
> 
> Yes, you should. Any relevant kernel messages?

2010-03-29T02:50:36.515445-11:00 pbx kernel: [467270.047734] FIRMWARE: : XPD=0-0  (0x0) OP=0x22 LEN=14 BYTES: 0E 00 22 00 02 02 08 00 09 00 04 00 00 00 
2010-03-29T02:50:36.515511-11:00 pbx kernel: [467270.047734] NOTICE-xpp: XBUS-00(00): FIRMWARE ERROR_CODE: category=2 errorbits=0x02 (rate_limit=1669611216)
2010-03-29T02:50:36.515577-11:00 pbx kernel: [467270.047734] FIRMWARE: : XPD=0-0  (0x0) OP=0x22 LEN=14 BYTES: 0E 00 22 00 02 02 08 00 09 00 04 00 00 00 
2010-03-29T02:50:36.515645-11:00 pbx kernel: [467270.047734] NOTICE-xpp: XBUS-00(00): FIRMWARE ERROR_CODE: category=2 errorbits=0x02 (rate_limit=1669611217)
2010-03-29T02:50:36.515711-11:00 pbx kernel: [467270.047734] FIRMWARE: : XPD=0-0  (0x0) OP=0x22 LEN=14 BYTES: 0E 00 22 00 02 02 08 00 09 00 04 00 00 00 
2010-03-29T02:50:36.515789-11:00 pbx kernel: [467270.047734] NOTICE-xpp: XBUS-00(00): FIRMWARE ERROR_CODE: category=2 errorbits=0x02 (rate_limit=1669611218)
2010-03-29T02:50:36.515859-11:00 pbx kernel: [467270.047734] FIRMWARE: : XPD=0-0  (0x0) OP=0x22 LEN=14 BYTES: 0E 00 22 00 02 02 08 00 09 00 04 00 00 00 
2010-03-29T02:50:36.515926-11:00 pbx kernel: [467270.047734] NOTICE-xpp: XBUS-00(00): FIRMWARE ERROR_CODE: category=2 errorbits=0x02 (rate_limit=1669611219)
2010-03-29T02:50:36.515993-11:00 pbx kernel: [467270.047734] FIRMWARE: : XPD=0-0  (0x0) OP=0x22 LEN=14 BYTES: 0E 00 22 00 02 02 08 00 09 00 04 00 00 00 
2010-03-29T02:50:36.516060-11:00 pbx kernel: [467270.047734] 


> 
> If not: try:
> 
>  rmmod xpp_usb
>  modprobe xpp_usb
> 
> What new messages do you then see in /var/log/messages ?



Tim Panton - Web/VoIP consultant and implementor
www.westhawk.co.uk