asterisk users - Jan 2004 - Asterisk with a laptop with built-in Intel 537 modem

I have * working on my Sony Vaio PCG-FX120 laptop.  I am trying to get * to 
recognize my internal PCI Intel modem as an FXO port.  I have modified 
wcfxo.c in order to identify the PCI modem properly.  Based on output from 
dmesg, wcfxo didn't recognize the modem until I inserted the proper vendor 
and device IDs into wcfxo.c and re-compiled.  Note that the error message 
from "modprobe wcfxo" still returns "No such devices", but
the card IS now
recognized based upon my dmesg results.  However, now I'm running into the 
error "Out of space to write register 06 with e0" as reported by
dmesg.

I tried changing ZT_CHUNKSIZE from 8 to 4 to no avail.  Per a FAQ at 
www.digium.com, my problem is that my modem shares interrupts with other 
devices on my laptop.  This is indeed the case based upon dmesg output.  It 
appears the SMbus (controller?), audio controller, and modem all share Int 
9.

Questions:
1) Is IRQ sharing really causing this problem?
2) Why can't wcfxo handle shared IRQ's, or does it not have anything to
do
with wcfxo?
3) Is there some way to force the kernel to pick a different IRQ for the 
modem?  If so, how?

Note that the BIOS for my laptop is VERY limited and appears to have no way 
to change IRQ's for devices.  I'm not very PCI literate, so perhaps (on
a
laptop), the IRQ's are hardwired and unchangable and I'm doomed
entirely?

Any help or ideas would be appreciated.

---
Following are outputs of modprobe, dmesg, lspci (you may notice the 
debugging output I added to wcfxo.c where I spit out values for x, reg, and 
value as wcfxo tries to write to the modem).

[prompt]# modprobe wcfxo
/lib/modules/2.4.20-8/misc/wcfxo.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including 
invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-8/misc/wcfxo.o: insmod 
/lib/modules/2.4.20-8/misc/wcfxo.o failed
/lib/modules/2.4.20-8/misc/wcfxo.o: insmod wcfxo failed

[prompt]# dmesg  <SNIPPET>
Zapata Telephony Interface Registered on major 196
PCI: Found IRQ 9 for device 00:1f.6
PCI: Sharing IRQ 9 with 00:1f.3
PCI: Sharing IRQ 9 with 00:1f.5
x=0000 reg=05 value=00
x=0001 reg=05 value=08
PCI: Setting latency timer of device 00:1f.6 to 64
x=0002 reg=01 value=80
x=0003 reg=07 value=00
x=0004 reg=08 value=01
x=0005 reg=09 value=89
x=0006 reg=0a value=00
x=0007 reg=05 value=0a
wcfxo: Out of space to write register 06 with e0
Failed to initailize DAA, giving up...
Zapata Telephony Interface Unloaded

[prompt]# lspci
00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory 
Controller Hub (rev 11)
00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics 
Controller] (rev 11)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 03)
00:1f.0 ISA bridge: Intel Corp. 82801BAM ISA Bridge (LPC) (rev 03)
00:1f.1 IDE interface: Intel Corp. 82801BAM IDE U100 (rev 03)
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 03)
00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 03)
00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 03)
00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio 
(rev 03)
00:1f.6 Modem: Intel Corp. Intel 537 [82801BA/BAM AC'97 Modem] (rev 03)
01:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AA22 IEEE-1394 
Controller (PHY/Link Integrated) (rev 02)
01:02.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
01:02.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
01:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet 
Controller (rev 03)

/**************************************************************
 Ken Alker         ken@impulse.net            ham radio: KA6SDU
 Impulse Internet Services               http://www.impulse.net
 Santa Barbara,  San Luis Obispo,  Ventura, Los Angeles, Orange
 T-3 / T-1 / ADSL / ISDN / 56K / web hosting / wireless / co-lo
***************************************************************/

Dear All,

 

Even its not much relevant to ask at this forum but If anyone can commnet..

I m trying to run CP4/LSI on Linux RHL 8.0 box, tried with LINUX_SR5.1.tgz,
LiS-2.17.A.tgz


It gives errors like..

Dialogic Shared RAM Protocol Module
Version 2.0
Linux  2.x.x
Kernel 2.4.x
Copyright (C) 2001 Intel Corp.
ALL RIGHTS RESERVED

Unable to demand load configured STREAMS object mercdDriver, device major 233


 

Anyone any idea?

Someone said that this ver of dialogic card is not supported at linux at all. is
there anysuch thing?

 

Thanks in advance

JF



---------------------------------
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040130/65510483/attachment.htm

Below...
> -----Original Message-----
> From: asterisk-users-admin@lists.digium.com 
> [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Ken Alker
> Sent: Friday, 30 January 2004 22:07
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] Asterisk with a laptop with 
> built-in Intel 537 modem
> 
> I have * working on my Sony Vaio PCG-FX120 laptop.  I am 
> trying to get * to 
> recognize my internal PCI Intel modem as an FXO port.  I have 
> modified 
> wcfxo.c in order to identify the PCI modem properly.  Based 
> on output from 
> dmesg, wcfxo didn't recognize the modem until I inserted the 
> proper vendor 
> and device IDs into wcfxo.c and re-compiled.  Note that the 
> error message 
> from "modprobe wcfxo" still returns "No such devices",
but
> the card IS now 
> recognized based upon my dmesg results.  However, now I'm 
> running into the 
> error "Out of space to write register 06 with e0" as reported 
> by dmesg.
> 
> I tried changing ZT_CHUNKSIZE from 8 to 4 to no avail.  Per a FAQ at 
> www.digium.com, my problem is that my modem shares interrupts 
> with other 
> devices on my laptop.  This is indeed the case based upon 
> dmesg output.  It 
> appears the SMbus (controller?), audio controller, and modem 
> all share Int 
> 9.
> 
> Questions:
> 1) Is IRQ sharing really causing this problem?
I don't think so.  I think what you are doing is hacking the driver to think
that your built-in modem is an X100P you are successful in this.  The
problem is that your internal modem is not an X100P, and is not compatible,
and you haven't hacked your driver at all to to speak Intel 537, it still
speaks X100P, so driver-hardware communication doesn't work.

I think an alternative would be to get a separate box (mediatrix?) which has
FXO ports and can talk to asterisk using SIP.  I think this would be the
quickest solution which is almost as portable as your laptop.

Cheers,
Woody