[Asterisk-Users] TDM400P hardware problems (fix)

[Cirelle Enterprises]

----- Original Message ----- 
From: "Cirelle Enterprises" <gcirino at cirelle.com>
To: <mike at thevoipconnection.com>; "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com>
Sent: Thursday, October 28, 2004 1:16 PM
Subject: Re: [Asterisk-Users] TDM400P hardware problems



----- Original Message ----- 
From: "Michael Crown" <mike at thevoipconnection.com>
To: "'Asterisk Users Mailing List - Non-Commercial Discussion'" <asterisk-users at lists.digium.com>
Sent: Thursday, October 28, 2004 1:06 PM
Subject: RE: [Asterisk-Users] TDM400P hardware problems


| 
| Some of the "REV H" boards have been problematic.  If you have one of these
| and you are having trouble, you should contact Digium.
| 

That's the one... crappy board



Apparently, this board has a tendency to lose the key required for reboot
and takes several keys to settle down.

an lspci -v will reveal the key it is using

02:03.0 Communication controller: Individual Computers - Jens Schoenfeld Intel 537
>>>>        Subsystem: Unknown device a904:0003
        Flags: bus master, medium devsel, latency 32, IRQ 7
        I/O ports at a000 [size=256]
        Memory at f8100000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

in this case, the a904 is the key

now in wcfxs.c on lines approximately 2127 or there abouts
this key needs to be added  like so:

static struct pci_device_id wcfxs_pci_tbl[] = {
        { 0xe159, 0x0001, 0xa159, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxs },
        { 0xe159, 0x0001, 0xe159, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxs },
        { 0xe159, 0x0001, 0xb100, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxse },
        { 0xe159, 0x0001, 0xa9fd, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxsh },
        { 0xe159, 0x0001, 0xa904, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxsh },
        { 0xe159, 0x0001, 0xa900, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxsh },
        { 0xe159, 0x0001, 0xa901, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxsh },
        { 0 }
};

in this case this procedure needed to happen several times until 0xa904 allowed
the reboot (note the a901, a900)

recompile and see if it works for you... 

It did for me and thanks to Matt at digium for the information of which I am passing
along.


regards
Greg