Topic: Sail 2.3.2-17 problem loading TDM410P

[ldkeen]

I couldn't resist - I saw 2.3.2-17 on the SARK website and thought I'd give it a try but I'm having problems with my TDM410P. After the initial install of 2.3.2-17 I noticed there were no PCI cards detected on the system so I tried a probe but it appeared to be looking in /lib/modules/2.6.9-78.0.22.ELsmp/extra/ for the module. I copied the entire /lib/modules/2.6.9-78.0.22.ELsmp/updates/extra directory into the extra directory and tried again, but now I'm getting a different message:

Code: [Select]

Found following card...
05:00.0 Ethernet controller: Digium, Inc.: Unknown device 8005 (rev 11)
Subsystem: Digium, Inc.: Unknown device 8005
Flags: bus master, medium devsel, latency 64, IRQ 217
I/O ports at d000 [size=256]
Memory at e9000000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [c0] Power Management version 2

Requesting Load of wctdm24xxp ...

Loaded wctdm...
Loaded wctdm24xxp...

No Telephony Boards found on second pass ...

Signalling asterisk daemon to load ZTDUMMY for timing purposes
[root@server extra]# rpm -q asterisk sail dahdi-linux dahdi-linux-kmdl-`uname -r`
asterisk-1.4.25.1-78.el4
sail-2.3.2-17
dahdi-linux-2.1.0.4-60.el4
dahdi-linux-kmdl-2.6.9-78.0.22.ELsmp-2.1.0.4-60.el4

[root@server extra]# uname -r
2.6.9-78.0.22.ELsmp


from dmesg
Freed a Wildcard
dahdi: Telephony Interface Unloaded
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.1.0.4
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 20 (level, low) -> IRQ 217
Port 1: Installed -- AUTO FXO (AUSTRALIA mode)
Port 2: Not installed
Port 3: Not installed
Port 4: Not installed
VPM100: Not Present
VPMADT032 Loading firmware... Success
Booting VPMADT032
VPMADT032: Present and operational (Firmware version 107)
Found a Wildcard TDM: Wildcard TDM410P (4 modules)

I'm not sure if there's a problem or whether I've done something wrong. I know you are very busy at the moment so I can drop back to 2.3.2-15 if needed.
Many Thanks, Lloyd

[ldkeen]

Dropping back to 2.3.2-15 fixed the problem.

[SARK devs]

Apologies Lloyd

We didn't publicise the -17 release because it is quite new and also, there isn't anything in it unless you are a SARK High Availability user.

2.3.2-18 (which is up there now) should fix the issue you saw, but it won't give you anything you don't already have in -15.  2.3.4 is the next functional release.


Best Regards and apologies for your inconvenience

J