Hi,
I installed a Moxa PCI express Multiport Serial Board on Ubuntu 12.04 with 3.2.0-33-generic kernel. I am finding it hard to find the appropriate drivers for the same, as Moxa seems to support drivers only up to 2.6 kernel version
After connecting a DLink serial based modem to this port, when I run the scanModem, I see that it can recognize the Serial board, but not the modem connected to it (via Serial cable).
Would appreciate any inputs on how I could use this setup, especially without the drivers! I tried using my application to open certain ports such as /dev/ttyM0 but it fails with 'No such device or address' error.
Thanks!
Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 3.2.0-33-generic
With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance. Linux experts in YourCountry
can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be essential for dialup service.
Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
-------------------------- System information ----------------------------
CPU=x86_64, Ubuntu , ALSA_version=
Linux version 3.2.0-33-generic (buildd@batsu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #52-Ubuntu SMP Thu Oct 18 16:29:15 UTC 2012
scanModem update of: 2011_08_08
Distrib_ID=Ubuntu
DistribCodeName=precise
AptRepositoryStem=http://au.archive.ubuntu.com/ubuntu/
Presently install your Linux Distributions dkms package. It provides for automated driver updates,
following upgrade of your kernel. For details see http://linux.dell.com/projects.shtml#dkms
Some modem drivers can only be used in 32 bit modem on x86_64 systems,
while some others are competent on x86_64 Systems. Cases are:
1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem controllers.
In both cases, 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component.
2) For USB modems using the slusb.ko driver. 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component
3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are x86_64 competent.
4) agrsm packages for LSI/AgereSystems softmodems are not competent on x86_64 systems.
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
Attached USB devices are:
ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
ID 046d:c30a Logitech, Inc. iTouch Composite
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html
A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx
Candidate PCI devices with modem chips are:
08:00.0 Serial controller: Moxa Technologies Co Ltd CP-104EL-A (4-port RS-232 PCI Express Serial Board)
High Definition Audio cards can host modem chips.
For candidate card in slot 08:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
08:00.0 1393:1045 1393:1045 Serial controller: Moxa Technologies Co Ltd CP-104EL-A
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 08:00.0 ----
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
A candidate modem is not transparent among the PCI devices:
------------------------------------------------
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13)
00:1f.2 IDE interface: Intel Corporation 82801IB (ICH9) 2 port SATA Controller [IDE mode] (rev 02)
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
06:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card
08:00.0 Serial controller: Moxa Technologies Co Ltd CP-104EL-A (4-port RS-232 PCI Express Serial Board)
09:03.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200eW WPCM450 (rev 0a)
------------------------------------------------
with USB, bridge, and RAM devices not displayed.
If a High Definition Audio card is present, if might be hosted on the Subsystem.
If your modem is an
external USB type,
connected by an external serial cable,
or mounted internally on an ISA card,
then scanModem would not access it.
Try with Root permission
$ sudo wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the DOCs/wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
sudo gedit /etc/wvdial.conf
will be able to dial out with Root permission:
sudo wvdial
Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems
If the above tests fail, please provide any independent information available on your modem.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) > System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information. From the Driver Details TAB, copy out the VENdor and DEVice information.
Next do the Query Modem and record the ATI specifications displayed such as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
Predictive diagnostics for card in bus 08:00.0:
Modem chipset not detected on
NAME="Serial controller: Moxa Technologies Co Ltd CP-104EL-A "
CLASS=0700
PCIDEV=1393:1045
SUBSYS=1393:1045
IRQ=40
For candidate modem in: 08:00.0
0700 Serial controller: Moxa Technologies Co Ltd CP-104EL-A
Primary device ID: 1393:1045
Support type needed or chipset:
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.6.3
and the compiler used in kernel assembly: 4.6
linux-headers-3.2.0-33-generic resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
linux-headers-3.2.0-33-generic
If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking pppd properties:
-rwsr-xr-- 1 root dip 325744 Feb 4 2011 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/ get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be changed to match your modem's port.
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1 eth1:avahi w1g1
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
