[Asterisk-Users] X100p on VIA EPIA-V problems

Lyle Giese lyle at lcrcomputer.net
Sun Sep 19 07:32:37 MST 2004 

Why is wsusb loading?  The X101P uses the wcfxo module.

Lyle

----- Original Message ----- 
From: "Andy" <akgmartinns at austin.rr.com>
To: <asterisk-users at lists.digium.com>; <asterisk-dev at lists.digium.com>
Sent: Sunday, September 19, 2004 7:29 AM
Subject: [Asterisk-Users] X100p on VIA EPIA-V problems


> Hi All,
>
> I hope I'm posting this to the appriopriate list, and that cross posting
> to two lists is OK. (If not, I'm sure I'll hear about it quickly :))
>
> I'm running Asterisk on my (new) VIA EPIA-V motherboard.
> This seems to be the ideal platform for a home version of asterisk - its
> small, quiet, low power, and should have plenty of computing horsepower
> if only it would work!
>
> I'm running Redhat 9, Kernel 2.4.20-8, and Asterisk from
> CVS-HEAD-07/07/04-21:01:10
> The phones in my house talk to asterisk via  a Sipura SPA-2000.
> I have a X100p card (not from Digium, I regret, but one of the "OEM"
> cards sold by Diginetworks).  Here' is a snipit from the boot log:
>
> > Sep 14 06:32:18 anchor kernel: Zapata Telephony Interface Registered on
major 196
> > Sep 14 06:32:18 anchor zaptel: Loading zaptel framework:  succeeded
> > Sep 14 06:32:19 anchor kernel: wcfxo: DAA mode is 'FCC'
> > Sep 14 06:32:19 anchor kernel: Found a Wildcard FXO: Wildcard X101P
> > Sep 14 06:32:20 anchor kernel: usb.c: registered new driver wcusb
> > Sep 14 06:32:20 anchor kernel: Wildcard USB FXS Interface driver
registered
> > Sep 14 06:32:21 anchor kernel: Registered tone zone 0 (United States /
North America)
> > Sep 14 06:32:21 anchor zaptel: Running ztcfg:  succeeded
>
> Everything works perfectly, except for the following problem:
> Sporadically -- about once in 6 hrs, Asterisk reports a "Red Alarm" from
> the X100p.  Thereafter, the X100p no longer works -- no outgoing calls
> can be placed; no incoming calls answered.
> The problem can be cleared in one of two ways - the phone line can be
> unplugged and plugged back in again, or asterisk can be shut down, the
> zaptel module uloaded from the kernel, and then reloaded.
>
> Here is another snipit from the log:
> > Sep 13 05:40:50 NOTICE[16384]: registered database handle 'mysql1'
dsn->[MySQL-asterisk]
> > Sep 13 05:40:50 NOTICE[16384]: registered database handle 'mysql2'
dsn->[MySQL-asterisk]
> > Sep 13 05:40:50 NOTICE[16384]: res_odbc loaded.
> > Sep 13 05:40:50 NOTICE[16384]: Registered Config Engine odbc
> > Sep 13 05:40:50 NOTICE[16384]: res_config_odbc loaded.
> > Sep 13 05:40:53 WARNING[16384]: Unable to get our IP address, Skinny
disabled
> > Sep 13 05:40:53 WARNING[16384]: Unable to open /dev/dsp: No such device
> > Sep 13 07:48:14 NOTICE[98311]: Registration from
'<sip:022 at 192.168.1.92>' failed for '192.168.1.93'
> > Sep 13 08:30:29 NOTICE[98311]: Registration from
'<sip:021 at 192.168.1.92>' failed for '192.168.1.93'
> > Sep 13 08:30:29 NOTICE[98311]: Registration from
'<sip:021 at 192.168.1.92>' failed for '192.168.1.93'
> > Sep 13 08:33:11 NOTICE[262160]: Unable to create channel of type 'SIP'
> > Sep 13 08:33:11 NOTICE[262160]: Unable to create channel of type 'SIP'
> > Sep 13 08:36:39 WARNING[180236]: Detected alarm on channel 1: Red
AlarmSep 13 05:40:50 NOTICE[16384]: registered database handle 'mysql1'
dsn->[MySQL-asterisk]
>
>
> Also, from time to time something goes wrong (maybe one call in 5) while
> a call is in progress, and instead of hearing the person's voice, one
> hears garbage sounds -- odd tones and pops.
>
> The X100p worked reliably for several weeks on my old dual processor
> 400Mhz pentium box running the same Redhat kernel and Asterisk source.
>
> The Via box is otherwise completely stable.  I've tried just about every
> conievable BIOS setting on the Via box,  I've recompiled asterisk,
> zaptel and the kernel specifying i386 as the archetecture. I've run
> memtest86 in the hope of finding a memory problem.
> I've tried a 2.6 kernel (2.6.6 with special "via" patches) with exactly
> the same results.
>
> Has anyone else out there got this configuration to work?
>
> My choices now seem to be
>     1) Buy a new X100p (from Digium this time!)
>     2) Buy a new motherboard - (I'd like to keep the low-power, low noise
> and mini-itx form factor)
>     3) Give up on the X100p and get a Sipura SPA-3000 for an FXO port -
> I'd loose the timer, so music-on-hold might not work so well
>
> Anyone have any other suggestions?  Other things I might try?
> Ways I could go about debugging this?
>
> Here is what lspci says about the installed pci devices:
>
> > lspci -vvv
> > 00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia]
(rev 05)
> > Subsystem: VIA Technologies, Inc.: Unknown device aa03
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR+
> > Latency: 8
> > Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
> > Capabilities: [a0] AGP version 2.0
> > Status: RQ=7 SBA+ 64bit- FW- Rate=x1,x2,x4
> > Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
> >
> > 00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
(prog-if 00 [Normal decode])
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR+
> > Latency: 0
> > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
> > I/O behind bridge: 0000f000-00000fff
> > Memory behind bridge: e4000000-e6ffffff
> > Prefetchable memory behind bridge: fff00000-000fffff
> > BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
> > Capabilities: [80] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge]
(rev 10)
> > Subsystem: VIA Technologies, Inc.: Unknown device aa03
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Latency: 0
> > Capabilities: [c0] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus
Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
> > Subsystem: VIA Technologies, Inc.: Unknown device aa03
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Latency: 32
> > Region 4: I/O ports at d000 [size=16]
> > Capabilities: [c0] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1e) (prog-if 00
[UHCI])
> > Subsystem: VIA Technologies, Inc.: Unknown device aa03
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Latency: 32, cache line size 08
> > Interrupt: pin D routed to IRQ 3
> > Region 4: I/O ports at d400 [size=32]
> > Capabilities: [80] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1e) (prog-if 00
[UHCI])
> > Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Latency: 32, cache line size 08
> > Interrupt: pin D routed to IRQ 3
> > Region 4: I/O ports at d800 [size=32]
> > Capabilities: [80] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10)
> > Subsystem: VIA Technologies, Inc. VT8235 ACPI
> > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Capabilities: [68] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686
AC97 Audio Controller (rev 40)
> > Subsystem: VIA Technologies, Inc.: Unknown device aa03
> > Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Interrupt: pin C routed to IRQ 10
> > Region 0: I/O ports at dc00 [size=256]
> > Region 1: I/O ports at e000 [size=4]
> > Region 2: I/O ports at e400 [size=4]
> > Capabilities: [c0] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 51)
> > Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet
Controller on VT8235
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Latency: 32 (750ns min, 2000ns max), cache line size 08
> > Interrupt: pin A routed to IRQ 11
> > Region 0: I/O ports at e800 [size=256]
> > Region 1: Memory at e7000000 (32-bit, non-prefetchable) [size=256]
> > Capabilities: [40] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 00:14.0 Communication controller: Tiger Jet Network Inc. Intel 537
> > Subsystem: Unknown device 8085:0003
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Latency: 32 (250ns min, 32000ns max)
> > Interrupt: pin A routed to IRQ 5
> > Region 0: I/O ports at ec00 [size=256]
> > Region 1: Memory at e7001000 (32-bit, non-prefetchable) [size=4K]
> > Capabilities: [40] Power Management version 2
> > Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA
PME(D0+,D1-,D2+,D3hot+,D3cold+)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1
(rev 6a) (prog-if 00 [VGA])
> > Subsystem: Trident Microsystems CyberBlade/i1
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
> > Latency: 32
> > Interrupt: pin A routed to IRQ 11
> > Region 0: Memory at e5800000 (32-bit, non-prefetchable) [size=8M]
> > Region 1: Memory at e6000000 (32-bit, non-prefetchable) [size=128K]
> > Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=8M]
> > Expansion ROM at <unassigned> [disabled] [size=64K]
> > Capabilities: [80] AGP version 2.0
> > Status: RQ=32 SBA+ 64bit- FW- Rate=x1,x2,x4
> > Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
> > Capabilities: [90] Power Management version 1
> > Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> Here's the contents of /proc/interrupts
> > cat /proc/interrupts
> >            CPU0
> >   0:   69499742          XT-PIC  timer
> >   1:      16980          XT-PIC  i8042
> >   2:          0          XT-PIC  cascade
> >   3:          0          XT-PIC  uhci_hcd, uhci_hcd
> >   5:   67957058          XT-PIC  wcfxo
> >   8:          1          XT-PIC  rtc
> >  10:    1044947          XT-PIC  via82cxxx
> >  11:     562610          XT-PIC  eth0
> >  12:     161145          XT-PIC  i8042
> >  14:     190384          XT-PIC  ide0
> > NMI:          0
> > ERR:         87
>
>
>
> Thanks,
> Andy
>
>
>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

More information about the asterisk-users mailing list