Syba ExpressCard serial ports recognized but not working

Issues related to hardware problems

Syba ExpressCard serial ports recognized but not working

Postby mikeu » 2012/02/01 17:51:22

I am trying to install a Syba SD-EXP15010 2 x Serial Ports ExpressCard in a Dell Precision M6400 laptop. CentOS appears to recognize the device and load the drivers, linking the two ports to ttyS0 and ttyS1. In /var/log/messages there are lines showing "modem-manager" trying to open and close the ports, which is something that I would like to turn off. I can't communicate over the serial lines using miniterm.py (which worked fine with a usb serial port and the same cables/device) or any other way. I did wait for modem-manager to close the ports before I tried to use them, otherwise there is a conflict. I added my (non-priv) username to the group dialout, but also tried changing the ownership for the ttyS0 dev to my login, Also tried to use the ports as root.

I found drivers for the MCS9901 Chipset (a bit old, dating from 2008) but I'd like to see if I can get the stock Centos install to work before I try that, as CentOS does seem to mostly recognize the device.

As an aside, does anyone know of a laptop card (ExpressCard or CardBus) with two or more standard UART serial ports that is known to work with CentOS? I've tried using USB serial ports but the latency is too great for my application (real-time control of a telescope and some lab equipment)

-mikeu

Booted at about 10:20, card inserted at about 11:27

Code: Select all
[root@rigel Desktop]# cat /etc/redhat-release
CentOS release 6.2 (Final)


[root@rigel Desktop]# uname -a
Linux rigel 2.6.32-220.4.1.el6.centos.plus.x86_64 #1 SMP Fri Jan 27 04:56:11 GMT 2012 x86_64 x86_64 x86_64 GNU/Linux


[root@rigel log]# tail -f /var/log/messages
Feb  1 11:27:17 rigel kernel: pci 0000:0e:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Feb  1 11:27:17 rigel kernel: pci 0000:0e:00.0: PME# disabled
Feb  1 11:27:17 rigel kernel: pci 0000:0e:00.1: PME# supported from D0 D1 D2 D3hot D3cold
Feb  1 11:27:17 rigel kernel: pci 0000:0e:00.1: PME# disabled
Feb  1 11:27:17 rigel kernel: pci 0000:0e:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
Feb  1 11:27:17 rigel kernel: pci 0000:0e:00.0: no hotplug settings from platform
Feb  1 11:27:17 rigel kernel: pci 0000:0e:00.1: no hotplug settings from platform
Feb  1 11:27:17 rigel kernel: serial 0000:0e:00.0: enabling device (0000 -> 0003)
Feb  1 11:27:17 rigel kernel: serial 0000:0e:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Feb  1 11:27:17 rigel kernel: 0000:0e:00.0: ttyS0 at I/O 0xc000 (irq = 19) is a ST16650V2
Feb  1 11:27:17 rigel kernel: serial 0000:0e:00.1: enabling device (0000 -> 0003)
Feb  1 11:27:17 rigel kernel: serial 0000:0e:00.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
Feb  1 11:27:17 rigel kernel: 0000:0e:00.1: ttyS1 at I/O 0xc008 (irq = 16) is a ST16650V2
Feb  1 11:27:17 rigel modem-manager: (ttyS1) opening serial device...
Feb  1 11:27:17 rigel modem-manager: (ttyS0) opening serial device...
Feb  1 11:27:30 rigel modem-manager: (ttyS1) closing serial device...
Feb  1 11:28:00 rigel modem-manager: (ttyS1) opening serial device...
Feb  1 11:28:00 rigel modem-manager: (ttyS0) closing serial device...
Feb  1 11:28:30 rigel modem-manager: (ttyS0) opening serial device...
Feb  1 11:28:33 rigel modem-manager: (ttyS1) closing serial device...
Feb  1 11:29:03 rigel modem-manager: (ttyS0) closing serial device...


[root@rigel Desktop]# ls -l /dev/ttyS?
crw-rw----. 1 root dialout 4, 64 Feb  1 11:28 /dev/ttyS0
crw-rw----. 1 root dialout 4, 65 Feb  1 11:28 /dev/ttyS1
crw-rw----. 1 root dialout 4, 66 Feb  1 10:20 /dev/ttyS2
crw-rw----. 1 root dialout 4, 67 Feb  1 10:20 /dev/ttyS3


[root@rigel Desktop]# lspci -v
0e:00.0 Serial controller: NetMos Technology PCIe 9901 Multi-I/O Controller (prog-if 02 [16550])
   Subsystem: Device a000:1000
   Flags: fast devsel, IRQ 19
   I/O ports at c000 [size=8]
   Memory at f1c00000 (32-bit, non-prefetchable) [size=4K]
   Memory at f1c01000 (32-bit, non-prefetchable) [size=4K]
   Capabilities: [80] Power Management version 3
   Capabilities: [88] MSI: Enable- Count=1/32 Maskable- 64bit+
   Capabilities: [c0] Express Legacy Endpoint, MSI 00
   Capabilities: [100] Power Budgeting <?>
   Capabilities: [200] Device Serial Number 88-99-ff-ee-dd-cc-bb-aa
   Kernel driver in use: serial
0e:00.1 Serial controller: NetMos Technology PCIe 9901 Multi-I/O Controller (prog-if 02 [16550])
   Subsystem: Device a000:1000
   Physical Slot: 1
   Flags: fast devsel, IRQ 16
   I/O ports at c008 [size=8]
   Memory at f1c02000 (32-bit, non-prefetchable) [size=4K]
   Memory at f1c03000 (32-bit, non-prefetchable) [size=4K]
   Capabilities: [80] Power Management version 3
   Capabilities: [88] MSI: Enable- Count=1/32 Maskable- 64bit+
   Capabilities: [c0] Express Legacy Endpoint, MSI 00
   Capabilities: [100] Power Budgeting <?>
   Capabilities: [200] Device Serial Number 00-00-00-00-00-00-00-00
   Kernel driver in use: serial


After ejecting the card:

Code: Select all
[root@rigel log]# tail -f /var/log/messages
Feb  1 12:35:57 rigel kernel: serial 0000:0e:00.0: PCI INT A disabled


[root@rigel Desktop]# ls -l /dev/ttyS?
crw-rw----. 1 root dialout 4, 64 Feb  1 12:35 /dev/ttyS0
crw-rw----. 1 root dialout 4, 65 Feb  1 11:28 /dev/ttyS1
crw-rw----. 1 root dialout 4, 66 Feb  1 10:20 /dev/ttyS2
crw-rw----. 1 root dialout 4, 67 Feb  1 10:20 /dev/ttyS3


Note that only PCI INT A is now disabled, and timestamp on ttyS0 dev is updated.
However, timestamp on S1 has not changed. PCI INT B has not been released?

Code: Select all
[root@rigel Desktop]# lspci -v
0e:00.1 Serial controller: NetMos Technology PCIe 9901 Multi-I/O Controller (rev ff) (prog-if ff)
   !!! Unknown header type 7f
   Kernel driver in use: serial


After re-inserting card:

Code: Select all
[root@rigel log]# tail -f /var/log/messages
Feb  1 12:47:55 rigel kernel: pci 0000:0e:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Feb  1 12:47:55 rigel kernel: pci 0000:0e:00.0: PME# disabled
Feb  1 12:47:55 rigel kernel: serial 0000:0e:00.1: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
Feb  1 12:47:55 rigel kernel: serial 0000:0e:00.1: no hotplug settings from platform
Feb  1 12:47:55 rigel kernel: pci 0000:0e:00.0: no hotplug settings from platform
Feb  1 12:47:55 rigel kernel: serial 0000:0e:00.0: enabling device (0000 -> 0003)
Feb  1 12:47:55 rigel kernel: serial 0000:0e:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Feb  1 12:47:55 rigel kernel: 0000:0e:00.0: ttyS0 at I/O 0xc000 (irq = 19) is a ST16650V2


Another error message that I have seen in /var/log/messages is:

Code: Select all
Feb  1 13:12:16 rigel kernel: ttyS1: LSR safety check engaged!
mikeu
 
Posts: 6
Joined: 2012/02/01 16:36:53
Location: Providence, RI

Syba ExpressCard serial ports recognized but not working

Postby pschaff » 2012/02/02 02:26:38

Welcome to the CentOS fora. Please see the recommended reading for new users linked in my signature.

It may help to provide more information about your system by running "./getinfo.sh" and showing us the output file.
pschaff
Retired Moderator
 
Posts: 18277
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America

Re: Syba ExpressCard serial ports recognized but not working

Postby mikeu » 2012/02/02 02:50:39

Information for driver problems.
Code: Select all
== BEGIN uname -rmi ==
2.6.32-220.4.1.el6.centos.plus.x86_64 x86_64 x86_64
== END   uname -rmi ==

== BEGIN rpm -qa \*-release\* ==
centos-release-6-2.el6.centos.7.x86_64
rpmforge-release-0.5.2-2.el6.rf.x86_64
== END   rpm -qa \*-release\* ==

== BEGIN cat /etc/redhat-release ==
CentOS release 6.2 (Final)
== END   cat /etc/redhat-release ==

== BEGIN getenforce ==
Enforcing
== END   getenforce ==

== BEGIN free -m ==
             total       used       free     shared    buffers     cached
Mem:          3692       1453       2238          0         69        683
-/+ buffers/cache:        701       2991
Swap:         5999          0       5999
== END   free -m ==

== BEGIN rpm -qa kernel\* | sort ==
kernel-2.6.32-131.21.1.el6.centos.plus.x86_64
kernel-2.6.32-220.2.1.el6.centos.plus.x86_64
kernel-2.6.32-220.4.1.el6.centos.plus.x86_64
kernel-2.6.32-220.el6.centos.plus.x86_64
kernel-2.6.32-71.29.1.el6.centos.plus.x86_64
kernel-devel-2.6.32-131.21.1.el6.centos.plus.x86_64
kernel-devel-2.6.32-220.2.1.el6.centos.plus.x86_64
kernel-devel-2.6.32-220.4.1.el6.centos.plus.x86_64
kernel-devel-2.6.32-220.el6.centos.plus.x86_64
kernel-devel-2.6.32-71.29.1.el6.centos.plus.x86_64
kernel-firmware-2.6.32-220.4.1.el6.centos.plus.noarch
kernel-headers-2.6.32-220.4.1.el6.centos.plus.x86_64
== END   rpm -qa kernel\* | sort ==

== BEGIN lspci -nn ==
00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e10] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e11] (rev 03)
00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02)
00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02)
00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02)
00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02)
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 02)
00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 02)
00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 02)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02)
00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 02)
00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02)
00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02)
00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02)
00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 92)
00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M-E LPC Interface Controller [8086:2917] (rev 02)
00:1f.2 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
01:00.0 VGA compatible controller [0300]: nVidia Corporation G94M [Quadro FX 2700M] [10de:063a] (rev a1)
03:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev ba)
03:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 04)
03:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 21)
03:01.3 System peripheral [0880]: Ricoh Co Ltd R5C843 MMC Host Controller [1180:0843] (rev 11)
03:01.4 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 11)
03:01.5 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev 11)
09:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5761e Gigabit Ethernet PCIe [14e4:1680] (rev 10)
0c:00.0 Network controller [0280]: Intel Corporation Ultimate N WiFi Link 5300 [8086:4235]
0e:00.0 Serial controller [0700]: NetMos Technology PCIe 9901 Multi-I/O Controller [9710:9901]
0e:00.1 Serial controller [0700]: NetMos Technology PCIe 9901 Multi-I/O Controller [9710:9901]
== END   lspci -nn ==

== BEGIN lsusb ==
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick
Bus 003 Device 005: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card
== END   lsusb ==

== BEGIN rpm -qa kmod\* kmdl\* ==
== END   rpm -qa kmod\* kmdl\* ==

mikeu
 
Posts: 6
Joined: 2012/02/01 16:36:53
Location: Providence, RI

Re: Syba ExpressCard serial ports recognized but not working

Postby pschaff » 2012/02/02 03:27:16

Seems (somewhat oddly) that your hardware is supported by the parport_pc driver.
Code: Select all
$ grep -i 9710 /lib/modules/*/modules.alias | grep -i 9901
/lib/modules/2.6.32-131.12.1.el6.i686/modules.alias:alias pci:v00009710d00009901sv0000A000sd00002000bc*sc*i* parport_pc
/lib/modules/2.6.32-131.17.1.el6.i686/modules.alias:alias pci:v00009710d00009901sv0000A000sd00002000bc*sc*i* parport_pc
/lib/modules/2.6.32-131.21.1.el6.i686/modules.alias:alias pci:v00009710d00009901sv0000A000sd00002000bc*sc*i* parport_pc
/lib/modules/2.6.32-220.2.1.el6.i686/modules.alias:alias pci:v00009710d00009901sv0000A000sd00002000bc*sc*i* parport_pc
/lib/modules/2.6.32-220.4.1.el6.i686/modules.alias:alias pci:v00009710d00009901sv0000A000sd00002000bc*sc*i* parport_pc
/lib/modules/2.6.32-71.18.1.el6.i686/modules.alias:alias pci:v00009710d00009901sv0000A000sd00002000bc*sc*i* parport_pc


A google on 9710:9901 site:redhat.com seems to indicate it should use 8250_pci for the serial ports, and it seems that is compiled into the kernel:
Code: Select all
# grep -i 8250 /boot/config-2.6.32-220.4.1.el6.x86_64
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
# Non-8250 serial port support

I'm not clear on exactly what your issue is. Seems it should work.
pschaff
Retired Moderator
 
Posts: 18277
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America

Re: Syba ExpressCard serial ports recognized but not working

Postby mikeu » 2012/02/02 04:11:48

pschaff wrote:
I'm not clear on exactly what your issue is. Seems it should work.


Yes, it does look like the correct drivers are loading but I was not able to get the serial ports to communicate at all. I have tried a few new things since my original post.

If I insert the ExpressCard before powering up the laptop - the serial ports work fine. However, I have to wait for modem-manager to stop trying to access them. I would like to disable modem-manager from using the ttyS? devices.

If eject the card, and then reinsert it - the serial ports no longer work. If I watch /proc/tty/driver/serial I see:

Code: Select all
0: uart:ST16650V2 port:0000C000 irq:19 tx:117 rx:56 RTS|DTR


After I put a loopback connector on the serial port it changes to:

Code: Select all
0: uart:ST16650V2 port:0000C000 irq:19 tx:117 rx:56 RTS|CTS|DTR|DSR|CD


So the driver seems to detect the new connection on the handshake pins, but no characters are transmitted or received on the port.

-mikeu
mikeu
 
Posts: 6
Joined: 2012/02/01 16:36:53
Location: Providence, RI

Re: Syba ExpressCard serial ports recognized but not working

Postby pschaff » 2012/02/02 17:27:54

mikeu wrote:
...
If eject the card, and then reinsert it - the serial ports no longer work.
...

So, is not doing that an option?

Patient: Doctor it hurts when I do this!
Doctor: Don't do that.

:-)
pschaff
Retired Moderator
 
Posts: 18277
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America

Re: Syba ExpressCard serial ports recognized but not working

Postby mikeu » 2012/02/02 18:48:32

pschaff wrote:
mikeu wrote:
...
If eject the card, and then reinsert it - the serial ports no longer work.
...

So, is not doing that an option?

Patient: Doctor it hurts when I do this!
Doctor: Don't do that.

:-)


Having to press Ctrl-Alt-Del every time a problem like this occurs is one of the reasons I'm trying to migrate off MicroSoft Windows ;)

The card is designed to support hot-swap and I would frequently use that feature to switch between different pieces of equipment, if it worked. I have only just got to the point where I can use the card at all, and have yet to test it under realistic conditions. At this point I'm not at all confident that the drivers can work with the card reliably. If something as simple as bumping the cable will cause it to disconnect that would be more than an inconvenience if I am doing real time data acquisition.

I'm going to continue trying to get this card to work reliably, but I've also ordered another card to see if one using a different chip set will work better.

I would also really like to know how to control the ModemManager to prevent it from tying up a particular /dev/ttyS port.

-mikeu
mikeu
 
Posts: 6
Joined: 2012/02/01 16:36:53
Location: Providence, RI

Re: Syba ExpressCard serial ports recognized but not working

Postby pschaff » 2012/02/02 18:56:30

Not quite sure what you mean by ModemManager (getty or mgetty?) but perhaps see /etc/init/tty.conf and /etc/init/start-ttys.conf
pschaff
Retired Moderator
 
Posts: 18277
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America

Re: Syba ExpressCard serial ports recognized but not working

Postby mikeu » 2012/02/02 23:32:14

pschaff wrote:
Not quite sure what you mean by ModemManager (getty or mgetty?) but perhaps see /etc/init/tty.conf and /etc/init/start-ttys.conf


I'm seeing modem-manager in /var/log/messages (snipped for brevity)

Code: Select all
Feb  2 14:21:04 rigel NetworkManager[1825]: <info> NetworkManager (version 0.8.1-15.el6) is starting...
Feb  2 14:21:04 rigel NetworkManager[1825]: <info> trying to start the modem manager...
Feb  2 14:21:04 rigel modem-manager: ModemManager (version 0.4.0-3.git20100628.el6) starting...
Feb  2 14:21:04 rigel modem-manager: (ttyS0) opening serial device...
Feb  2 14:21:04 rigel NetworkManager[1825]: <info> modem-manager is now available


The NetworkManager website mentions ModemManager but the link was dead the last several time's I've checked. From what I understand ModemManager is used when I connect my CentOS laptop through the 3G internet connection on my cell phone. [see blurb here] I can't see why a mobile broadband application would want to grab a plain old db9 serial port. It doesn't look like getty is involved. -mikeu

Code: Select all
::::::::::::::
/etc/init/tty.conf
::::::::::::::
# tty - getty
#
# This service maintains a getty on the specified device.

stop on runlevel [S016]

respawn
instance $TTY
exec /sbin/mingetty $TTY
Code: Select all
::::::::::::::
/etc/init/start-ttys.conf
::::::::::::::
#
# This service starts the configured number of gettys.

start on stopped rc RUNLEVEL=[2345]

env ACTIVE_CONSOLES=/dev/tty[1-6]
env X_TTY=/dev/tty1
task
script
   . /etc/sysconfig/init
   for tty in $(echo $ACTIVE_CONSOLES) ; do
      [ "$RUNLEVEL" = "5" -a "$tty" = "$X_TTY" ] && continue
      initctl start tty TTY=$tty
   done
end script
mikeu
 
Posts: 6
Joined: 2012/02/01 16:36:53
Location: Providence, RI

Re: Syba ExpressCard serial ports recognized but not working

Postby pschaff » 2012/02/03 01:02:27

OK - have not used a modem in so long I was unfamiliar with it. Does seem to be part of NetworkManager automagic configuration. I'm not sure how to shut it off.
Code: Select all
# which modem-manager
/usr/sbin/modem-manager
# rpm -qif `which modem-manager`
Name        : ModemManager                 Relocations: (not relocatable)
Version     : 0.4.0                             Vendor: CentOS
Release     : 3.git20100628.el6             Build Date: Wed 10 Nov 2010 06:38:04 PM EST
Install Date: Sun 25 Dec 2011 08:29:48 AM EST      Build Host: c6b1.bsys.dev.centos.org
Group       : System Environment/Base       Source RPM: ModemManager-0.4.0-3.git20100628.el6.src.rpm
Size        : 603939                           License: GPLv2+
Signature   : RSA/8, Sun 03 Jul 2011 12:45:39 AM EDT, Key ID 0946fca2c105b9de
Packager    : CentOS BuildSystem <http://bugs.centos.org>
URL         : http://www.gnome.org/projects/NetworkManager/
Summary     : Mobile broadband modem management service
Description :
The ModemManager service provides a consistent API to operate many different
modems, including mobile broadband (3G) devices.
pschaff
Retired Moderator
 
Posts: 18277
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America

Next

Return to CentOS 6 - Hardware Support

Who is online

Users browsing this forum: No registered users and 1 guest