Hi All, I have been able to resolve this issue , hence would like to conclude this thread,. I was provided the latest drivers by Moxa for my version of kernel. Although I had compiled the latest drivers provided by Moxa, I was still using the native driver. In Ubuntu, modprobe seems to pick-up the ko from /lib/modules/3.2.0-33-generic/misc/mxser.ko whereas the driver installed by moxa was at: /lib/modules/3.2.0-33-generic/kernel/drivers/char/mxser.ko After correcting this, I am able to open up the port which is on /dev/ttyMUE0 (depends on the cable connected - could be in between MUE0-MUE3), and talk to the modem. Thanks for all the help!!!! With regards, Sirish -----Original Message----- From: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] Sent: Wednesday, 19 December 2012 11:38 PM To: Antonio Olivares Cc: Sirish Masur Mohan; discuss@xxxxxxxxxxxxx Subject: Re: Connecting serial based modem to Ubuntu via a PCI express multiport Serial board There was an earlier similar case of a Linux compatible serial multi-board. Though there was a Linux driver provided, some modification was necessary to acquire functionality in the specific host environment. Afterwards the procedures Antonio described worked for a serial modem attached. Unfortunately, I'm travling now with only occassional Internet access, through Tuesday. If our Archives are searched for "multi-board" or similar, you may be able to retrieve the record. MarvS > > On Tue, Dec 18, 2012 at 7:57 PM, Antonio Olivares > <olivares14031@xxxxxxxxx> > wrote: >> >> Sirish, >> >> As your modem is serial based, it should work straight out with the >> native drivers. Try the following which is suggested by >> ModemData.txt: >> >> >> 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: >> ------------------------------------------------ >> 08:00.0 Serial controller: Moxa Technologies Co Ltd CP-104EL-A >> (4-port >> RS-232 PCI Express Serial Board) >> ------------------------------------------------ >> 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 >> >> Please do where the ----> is at, >> ---> $ sudo wvdialconf /etc/wvdial.conf >> and you should be able to access the modem through a /dev/ttyS* where >> * can be an integer 0 or greater which is the true modem port. Let >> us know if the above command was successful, otherwise wvdial may >> need to be installed or you may try out the graphical utilities kppp, >> NetworkManager, etc. >> >> Best Regards, >> >> >> Antonio >> >> On Tue, Dec 18, 2012 at 4:21 PM, Sirish Masur Mohan >> <Sirish.MasurMohan@xxxxxxxxx> wrote: >> > 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! >> > > >
