[Asterisk-Users] wcte11xp works only after cold reboot

[Ron Wellsted]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart Hirst wrote:
> 
> Stuart Hirst wrote:
> 
>>Alessio,
>>
>>I have also seen this problem on two different asterisk servers using
>>TDM400p cards.
>>
>>I have not been able to resolve it. If you do an lspci you can see that
>>the system can see the devices but the zaptel drivers don't see them.
>>
>>I have other systems that work fine and so this has to be down to the
>>combination of motherboard and Digium PCI devices. It would seem that
>>this is a problem with the the Digium hardware because it works after a
>>cold boot.
>>
>>Does anyone else have a view ?
>>
>>Stuart
>>
>>Stuart
>>
>>On Wed, 2005-04-06 at 12:26 +0200, Alessio Focardi wrote:
>>
>>
>>>Hi,
>>>
>>>my brand new wcte11xp works like a charme of first boot, then if I
>>>
>>>shutdown -r now
>>>
>>>the server is not detected at reboot ("no such device" after modprobe).
>>>
>>>Turning off the pc and cold restarting fixes the problem.
>>>
>>>Has someone experienced such behaviour before ?
>>>
>>>Tnx for any help!
> 
> 
>>>>This is a known issue and crops up on the list from time to time.  For
>>>>some reason, the card will change is PCI bus ID.  It is set back to the
>>>>correct ID by a cold reboot.
>>>>
>>>>To work around this, edit the wcte1xxp.c in the zaptel directory so that
>>>>the pci_device_id structure becomes:
>>>>
>>>>static struct pci_device_id t1xxp_pci_tbl[] = {
>>>>       { 0xe159, 0x0001, 0x71fe, PCI_ANY_ID, 0, 0, (unsigned long)
>>>>"Digium Wildcard TE110P T1/E1 Board" },
>>>>       { 0xe159, 0x0001, 0x79fe, PCI_ANY_ID, 0, 0, (unsigned long)
>>>>"Digium Wildcard TE110P T1/E1 Board" },
>>>>       { 0xe159, 0x0001, 0x795e, PCI_ANY_ID, 0, 0, (unsigned long)
>>>>"Digium Wildcard TE110P T1/E1 Board" },
>>>>       { 0xe159, 0x0001, 0x79de, PCI_ANY_ID, 0, 0, (unsigned long)
>>>>"Digium Wildcard TE110P T1/E1 Board" },
>>>>       { 0xe159, 0x0001, 0x797e, PCI_ANY_ID, 0, 0, (unsigned long)
>>>>"Digium Wildcard TE110P T1/E1 Board" },
>>>>       { 0 }
>>>>};
>>>>
>>>>This should allow reboots but YMMV (well, it works on my server!).
>>>>
>>>>HTH
>>>>
>>>>- --
>>>>Ron Wellsted
> 
> 
> I don't suppose any one can confirm this type of fix for the TDM boards. I
> can make a guess but the systems are live and I will need to schedule outage
> to attempt this fix.
> 
> Thanks,
> 
> Stuart

My mistake, the above fix is for the TE110P, however I seem to recall a
similar problem being reported on the TDM board,certainly the symptom
and the cure is the same.  You can try using "lspci -vn" to check the
pci and subsytem IDs being returned by your card and check that these
match the values in the relevant source code file.  If not try adding
the relevant entries to the pci_device_id table.

- --
Ron Wellsted
http://www.wellsted.org.uk
ron at wellsted.org.uk
FWD:519961  Gossiptel:9309811
N 52.567623, W 2.137621
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQEVAwUBQlRXUUtP/KMNOfRbAQJsaAf/ViBcBLbmGu5b4XJzSJRtY1wwMq/4Qu0M
aprF1F9kXkuR/tVATUF1lN8+UNGR5nSvkTmkwS5p4AJSvkDUdtqD11v6OVkslILN
1HU6Fl7Es8qgImFKtF3TB/hVTB4NdKkKbyqhR3IFIjWubTl1rxrGHri6e7Kqqpa5
v8eLRywvOp7pzXpKqJ4YjNQpMM6mUJ0N4yvFIBBW7ERdaU2V83x5yeN2TNzh/k/W
MBKZY1HNYUhmBsvnp6gxHrEGOgjbnZ/bWt9Bgpkra5+rSYizUdegDdxpyIPE4OHE
0U2sUGWOYntUvWdjWBCejdozGTO3oGwZaVHlIANvMCvJ+G5H4xy8ZA==
=DviD
-----END PGP SIGNATURE-----