Can someone give me an incantation that will make modem-manager go away? I don't have a modem or wireless network in the box and this thing is triggering my OCD.
Thanks.
John
On 12/19/2012 04:37 PM, John Wendel wrote:
Can someone give me an incantation that will make modem-manager go away? I don't have a modem or wireless network in the box and this thing is triggering my OCD.
yum provides modem-manager
shows that it's supplied by the package ModemManager. If you're not using it, just have yum remove it.
On 12/19/2012 05:12 PM, Joe Zeff wrote:
On 12/19/2012 04:37 PM, John Wendel wrote:
Can someone give me an incantation that will make modem-manager go away? I don't have a modem or wireless network in the box and this thing is triggering my OCD.
yum provides modem-manager
shows that it's supplied by the package ModemManager. If you're not using it, just have yum remove it.
Thanks, but in F17, it takes network-manager and anaconda with it. I'm using network-manager.
John
On Wed, 2012-12-19 at 17:32 -0800, John Wendel wrote:
Thanks, but in F17, it takes network-manager and anaconda with it. I'm using network-manager.
Why would anaconda be installed on a system?
On 12/19/2012 07:23 PM, Tim wrote:
On Wed, 2012-12-19 at 17:32 -0800, John Wendel wrote:
Thanks, but in F17, it takes network-manager and anaconda with it. I'm using network-manager.
Why would anaconda be installed on a system?
Not exactly on topic for my original question. Perhaps you should ask the person who configured the installer.
John
On Wed, 2012-12-19 at 20:31 -0800, John Wendel wrote:
On 12/19/2012 07:23 PM, Tim wrote:
On Wed, 2012-12-19 at 17:32 -0800, John Wendel wrote:
Thanks, but in F17, it takes network-manager and anaconda with it. I'm using network-manager.
Why would anaconda be installed on a system?
Not exactly on topic for my original question. Perhaps you should ask the person who configured the installer.
I think Tim's point was that you can remove anaconda with no consequences. In fact my system (F17 fully updated) does not have anaconda installed, so maybe the OP's system shouldn't have had it in the first place, IOW it wasn't necessarily placed there by the installer.
poc
On 12/20/2012 04:09 AM, Patrick O'Callaghan wrote:
On Wed, 2012-12-19 at 20:31 -0800, John Wendel wrote:
On 12/19/2012 07:23 PM, Tim wrote:
On Wed, 2012-12-19 at 17:32 -0800, John Wendel wrote:
Thanks, but in F17, it takes network-manager and anaconda with it. I'm using network-manager.
Why would anaconda be installed on a system?
Not exactly on topic for my original question. Perhaps you should ask the person who configured the installer.
I think Tim's point was that you can remove anaconda with no consequences. In fact my system (F17 fully updated) does not have anaconda installed, so maybe the OP's system shouldn't have had it in the first place, IOW it wasn't necessarily placed there by the installer.
poc
I never installed anaconda, it must have been a dependency for some other package I installed, though I can' imagine what would require it.
But it doesn't matter because I still require network-manager, so I can't uninstall modem-manager.
John
On Thu, 20 Dec 2012 08:34:56 -0800 John Wendel jwendel10@comcast.net wrote:
I never installed anaconda, it must have been a dependency for some other package I installed, though I can' imagine what would require it.
If you installed from a LiveCD, you get what's pre-installed the LiveCD
Hi
On Thu, Dec 20, 2012 at 11:59 AM, Dr. Michael J. Chudobiak wrote:
It is possible to disable modem-manager (but not remove it, if you need NM). Delete this file:
/usr/share/dbus-1/system-services/org.freedesktop.ModemManager.service
Never do that. It won't serve the purpose since any update will pull it right back in. If you can't remove a package because of dependency but want to be sure to keep it disabled, use systemctl mask <servicename.service> instead and in this case, it really shouldn't be necessary to do that since it only gets started by NetworkManager if you try to establish a new connection using any modem, in-built or otherwise. It is also a very small dependency.
Rahul
On 12/20/2012 10:58 AM, Rahul Sundaram wrote:
Hi
On Thu, Dec 20, 2012 at 11:59 AM, Dr. Michael J. Chudobiak wrote:
It is possible to disable modem-manager (but not remove it, if you need NM). Delete this file: /usr/share/dbus-1/system-services/org.freedesktop.ModemManager.service
Never do that. It won't serve the purpose since any update will pull it right back in. If you can't remove a package because of dependency but want to be sure to keep it disabled, use systemctl mask <servicename.service> instead and in this case, it really shouldn't be necessary to do that since it only gets started by NetworkManager if you try to establish a new connection using any modem, in-built or otherwise. It is also a very small dependency.
Rahul
It doesn't work the way you described on my F17 box, that doesn't have a modem or wireless connection. Network-manager always loads modem-manager which loads the drivers for every modem and wireless device that it knows about (according to the log file). I know it's small, but I'm on a 1 GB box, and besides, it just bugs me. BTW, systemctl doesn't work with modem-manager, so masking it isn't possible.
I finally dumped network-manager and configured the network by hand. Much better. Oh well, looking forward to F18 and different triggers for my OCD.
Thanks,
John
On 12/20/2012 01:37 AM, John Wendel wrote:
Can someone give me an incantation that will make modem-manager go away? I don't have a modem or wireless network in the box and this thing is triggering my OCD.
Thanks.
John
Udev is your friend, i.e. ENV{ID_MM_DEVICE_IGNORE}="1". … /etc/udev/rules.d/78-mm-pci-device-blacklist.rules: This is a custom udev rule file in addition to ModemManager's blacklist files
ACTION!="add|change", GOTO="mm_pci_device_blacklist_end" SUBSYSTEM!="pci", GOTO="mm_pci_device_blacklist_end"
# Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01) ATTR{vendor}=="0x9710", ATTR{device}=="0x9835", ENV{ID_MM_DEVICE_IGNORE}="1"
LABEL="mm_pci_device_blacklist_end"
# udevadm info -a -p /sys/class/pci_bus/0000:01/device/0000:01:06.0 # udevadm info -q env -p /sys/class/pci_bus/0000:01/device/0000:01:06.0 … /etc/udev/rules.d/78-mm-usb-device-blacklist.rules: This is a custom udev rule file in addition to ModemManager's blacklist files
ACTION!="add|change", GOTO="mm_usb_device_blacklist_end" SUBSYSTEM!="usb", GOTO="mm_usb_device_blacklist_end"
# Prolific Technology, Inc. PL2303 Serial Port ATTR{idVendor}=="067b", ATTR{idProduct}=="2303", ENV{ID_MM_DEVICE_IGNORE}="1"
LABEL="mm_usb_device_blacklist_end"
# udevadm info -a -p /sys/devices/pci0000:00/0000:00:04.0/usb4/4-2 # udevadm info -q env -p /sys/devices/pci0000:00/0000:00:04.0/usb4/4-2 … Accordingly On-Chip Debugger's(OCD)/connected controller's Vendor/Product id(s).
Cheers, poma