Driver Not Starting

Owned by Nathaniel Halbrooks
Last updated: Mar 26, 2024 by Kelli Higdon
3 min read

Follow the steps below if your driver is not starting properly

 

1. Verify your Sangoma hardware is detected by your server

First of all make sure your Sangoma Card is properly inserted in the PCI/PCI express slot.

For analog models such as A200 or A400 make sure the main card is energized from the system's Power Supply Unit. 

You must attach a Molex Power Connector from your computer’s Power Supply Unit to the A200/A400 main card.

 

On your Linux Command line, type wanrouter hwprobe which lists details of all your installed Sangoma hardware.

If you notice the following error message when typing the command, then type lspci linux command to verify your server detects Sangoma hardware inserted in the PCI/PCIe slot(s)

 

Example of driver not starting:

wanrouter hwprobe      FATAL: Error inserting wanpipe (/lib/modules/2.6.18-194.el5PAE/kernel/drivers/net/wan/wanpipe.ko): Unknown symbol in module, or unknown parameter (see dmesg

 

 Successful lspci output where Sangoma hardware is detected by your server:

If lspci does detect Sangoma hardware inside your PCI/PCIe slot (as show in picture above), then you simply need to re-install your Wanpipe driver.
Also you can check /var/log/messages file for details on what when wrong 

 

lspci command should not be used to find out which Sangoma hardware you have.  Most of our cards share the same baseboard so there is high probability the wrong model number will show up.
As long as you see 'Sangoma Technologies.......' this is enough to prove your hardware is detected by your server, then use the wanrouter hwprobe command to provide hardware details 

  • Use lsusb in place of lspci if you are using a Sangoma USBFXO or Voicetime (UT50/51)

 

2. You rebooted your server and now Wanpipe will not start

Try typing the wanrouter hwprobe  command which should list details of your Sangoma hardware.
If you see an error message when you do this, most likely the issue is that at some point your kernel
was updated and only took affect after the server was rebooted.
 

Error message: FATAL: Error inserting wanpipe (/lib/modules/2.6.18../kernel/drivers..wanpipe.ko)

 

Solution: Select one of the two options below:

-> Re-install Wanpipe on the new system kernel

-> edit the grub.conf file of your Linux operating system and change default to value that represents previous kernel, then reboot

 
-> In above example, default=0  means the system will boot using the first kernel listed (2.6.358.
-> to load the older kernel (2.6.274) we simply change default=1 then reboot the system      
    

3. Wanpipe Driver not installed correctly

Verify that you have installed Wanpipe properly by using the wanrouter hwprobe command.
 

When you type wanrouter hwprobe on your command line, details on all your Sangoma hardware should present on screen.
If you notice an error message, Wanpipe driver is not starting because it was not installed correctly. Go through the Wanpipe driver installation page again

Example of successful wanrouter hwprobe :

 

example of server with A102 installed

wanrouter hwprobe ------------------------------- | Wanpipe Hardware Probe Info | ------------------------------- 1.  AFT-A102-SH : SLOT=0 : BUS=7 : IRQ=10 : CPU=A : PORT=1 : HWEC=64 : V=37 2 . AFT-A102-SH : SLOT=0 : BUS=7 : IRQ=10 : CPU=A : PORT=2 : HWEC=64 : V=37

 

Error when running wanrouter hwprobe:
 

Always view /var/log/messages to understand why your Wanpipe driver did not start correctly

Return to Documentation Home I Return to Sangoma Support