Topic: After SME updates SAIL no longer finds my TDM

[Franco]

I ran the latest SME updates and Sail can no longer detect my TDM:

Code: [Select]

Found following card...

06:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Unknown device b119:0003
Flags: bus master, medium devsel, latency 32, IRQ 177
I/O ports at 1000 [size=256]
Memory at 50105000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2

Requesting Load of wctdm ...

Loaded wctdm...

No Telephony Boards found - check admin-error log for probe failures...

Signalling asterisk daemon to load ZTDUMMY for timing purposes

[SARK devs]

This is because your kernel release has changed.  If you are running ATrpms asterisk then, after you have done your sme yum update and rebooted your system, simply do...

Code: [Select]

yum install zaptel-kmdl-`uname -r` --enablerepo=atrpms
This will download the correct modules for your new kernel.

You should not need to reprobe your card.

You should issue this command after each sme update and restart if you know or suspect that a new kernel has been installed.

Alternatively, if you are running selintra bristuff asterisk then you should simply do a reboot after the yum update (you need to be running bristuff-1.4.17 or higher and sail-612 or higher).  SAIL will automatically handle the kernel change for you.

Kind Regards

S

[Franco]

I did update the system completelly, including asterisk and all the modules!
When I reboot the system I get the V3 signatures problem:

Code: [Select]

[root@sme ~]# rpm -qa  | grep zaptel
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
zaptel-kmdl-2.6.9-67.0.1.ELsmp-1.4.10-50.el4
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
zaptel-1.4.10-50.el4
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature


Code: [Select]

uname -r
2.6.9-67.0.7.ELsmp


[Franco]

OK, Just ran the command you suggested and found a new update 

Crossing fingers...

[Franco]

OK!
So for the record, my mistake was run a single command

yum update zaptel libpri asterisk zaptel-kmdl-`uname -r` asterisk-addons --enablerepo=atrpms

instead of one per line like the manual said!
Back in business
Thanks again Jeff!

[SARK devs]

nstead of one per line like the manual said!

No.  Asterisk zaptel modules are saved in /lib/modules/{kernel-release}/extra.  When a new kernel release gets loaded by yum, the /extra directory gets left behind.  So, you have to run the yum install for the new kernel release to create the new /extra directory.  You don't need to run any of the other asterisk or sail installs, just the one for zaptel-kmdl.

Best

S

[Franco]

Ahh!
Thanks again!

Now I need to fix all the rest of the problems that these updates brought 
My panels are all messed up!

Best,

[SARK devs]

Yes. I have seen a few posts on this issue.  It does not seem to affect SAIL but I think it screws a lot of the other contribs.

Best

S

[chris burnat]

Yes. I have seen a few posts on this issue.  It does not seem to affect SAIL but I think it screws a lot of the other contribs.

Actually, it is not as bad - I panicked myself a little when faced with the nice mess my panel had become, but in the end, it was caused by one contrib only (smeserver-saco-qmHandle).  Check: http://wiki.contribs.org/Translations#Outdated_contribs for more info.
Phew....
Best.
chris.