Dialogic Blue Telephony Boards can be started in kernel or user mode. Normally, they are started in kernel mode. If the kernel mode fails, they are started in user mode. Using 64bit Linux kernels, the driver runs in kernel mode. Using 32bit Linux kernels, the driver runs in user mode. If an advanced user likes to change the 32bit driver to run in kernel mode (not recommended), the variable "vmalloc=512M" can be set in the kernel boot parameters (e.g. grub configuration files). To verify the mode of your Telephony Board, use one of the following tools:
To verify in which mode your Telephony Board is running, either:
Click System control (driver start/stop) on the left hand side of the web interface.
The Last operation log shows you in which mode the driver was started.
or:
Click Board monitor on the left hand side of the web interface.
Click the management interface icon of the M-Board, to which the Telephony Board belongs.
Go to Status\XDI\A1\UserMode.
A value of 0 indicates that the board is running in kernel mode.
A value of 1 indicates that it is running in user mode.
When using the mantool, the following message shows you whether the board was loaded in user mode:
--------bol-[Status\XDI\A1\UserMode .....] = TRUE
If the board was loaded in kernel mode, the following message appears:
--------bol-[Status\XDI\A1\UserMode .....] = FALSE
See Management Interface Access and Monitoring Utility for more information on the mantool.
You may also check the modus with tools like telnet or putty.
To see whether the board is stared in kernel mode, enter:
# lsmod | grep DivasL
and the following message appears:
DivasL 1973792 0
divadidd 68684 9 divacapi,diva_mtpx,diva_idi,DivasL,divas
To see whether the board is running in user mode enter:
# ps | grep DivasL
and the following message should appear:
root 8962 1 0 09:26 ? 00:00:00 /usr/lib/eicon/divas/DivasL