Hi Folks,
The Modem Manager service is not being started.
I had a look in /etc/init.d/.depend.start and can see that Network Manager is included but not Modem Manager.
Do I simply need to modify this file to include the Modem Manager? If so, what do I need to add and or modify?
Or is there some other way that this needs to be done?
How can I start the service manually?
Thanks, Michael.
topic title: Modem Manager Service not started - 14R Alpha4
8 posts
• Page 1 of 1
-
cuscotravelservicesPosts: 42
- Joined: 02 Jan 2015
-
capreacapreaPosts: 156
- Joined: 08 Jan 2014
#2
I just read your thread about the 3G modem.Did you get it to work,and if where was the mistake?
Code: Select all
sudo service ModemManager start-
cuscotravelservicesPosts: 42
- Joined: 02 Jan 2015
#3
When I tried"sudo service ModemManager start", the following response was received.
Is this because there is not a corresponding script in /etc/init.d ?
There is a ModemManager executable file in /usr/sbin and there is a ModemManager.service file in /lib/systemd/system.
The NetworkManager service is being started when the system is initialised.
How do we make the ModemManager service recognised and started when the system is initialised?
Thanks, MTB.
Hi,caprea wrote:I just read your thread about the 3G modem.Did you get it to work,and if where was the mistake?Code: Select all
sudo service ModemManager start
When I tried"sudo service ModemManager start", the following response was received.
Code: Select all
ModemManager: unrecognized serviceThere is a ModemManager executable file in /usr/sbin and there is a ModemManager.service file in /lib/systemd/system.
The NetworkManager service is being started when the system is initialised.
How do we make the ModemManager service recognised and started when the system is initialised?
Thanks, MTB.
-
BitJamPosts: 1,308
- Joined: 31 Aug 2009
#4
The modem manager program should be started by networkmanager. That's why there is not a separate modemmanager service that you can start and stop.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://gnome-networkmanager.2324886.n4.nabble.com/stopping-modem-manager-t d11658.html"
linktext was:"For example"
====================================
:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://gnome-networkmanager.2324886.n4.nabble.com/stopping-modem-manager-t d11658.html"
linktext was:"For example"
====================================
:
I'm not certain this applies to antiX-14 but this might be a good place to start.modem-manager is complementary program to NetworkManager and it is used to
manage modems. You don't have to execute it manually. It is run automatically
by NetworkManager. So, you just have to plug your modem and that's it.
-
cuscotravelservicesPosts: 42
- Joined: 02 Jan 2015
#5
I thought that was what was supposed to be happening but I couldn't find where NetworkManager is supposed to initiate ModemManager.
NetworkManager appears as a process in the Process Viewer (htop) but not ModemManager after the system is started.
nm-applet is also not being started.
In /usr/share/dbus-1/system-services are the following files.
org.freedesktop.NetworkManager.service
org.freedesktop.ModemManager1.service
Should the above file be renamed to org.freedesktop.ModemManager.service with the Name parameter changed to"org.freedesktop.ModemManager"?
I couldn't find any logs to see what is happening when Network Manager is started.
When the modem is connected to a USB port it is switched (converted) correctly (attached to ttyUSB0, ttyUSB1 and ttyUSB2).
When I start nm-applet there is no option displayed for"Enable Mobile Broadband" when I right-click on its systray icon.
antiX-14RAlpha4 is using SysVinit.
Is there something missing pertaining to SysVinit?
Thanks, MTB.
Hi BitJam,BitJam wrote:The modem manager program should be started by networkmanager. That's why there is not a separate modemmanager service that you can start and stop.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://gnome-networkmanager.2324886.n4.nabble.com/stopping-modem-manager-t d11658.html"
linktext was:"For example"
====================================
:I'm not certain this applies to antiX-14 but this might be a good place to start.modem-manager is complementary program to NetworkManager and it is used to
manage modems. You don't have to execute it manually. It is run automatically
by NetworkManager. So, you just have to plug your modem and that's it.
I thought that was what was supposed to be happening but I couldn't find where NetworkManager is supposed to initiate ModemManager.
NetworkManager appears as a process in the Process Viewer (htop) but not ModemManager after the system is started.
nm-applet is also not being started.
In /usr/share/dbus-1/system-services are the following files.
org.freedesktop.NetworkManager.service
Code: Select all
# This D-Bus service activation file is only for systemd support since
# an auto-activated NetworkManager would be quite surprising for those people
# who have NM installed but turned off. Thus the Exec path available to
# D-Bus is /bin/false, but systemd knows the real Exec path due to the NM
# systemd .service file.
[D-BUS Service]
Name=org.freedesktop.NetworkManager
Exec=/bin/false
User=root
SystemdService=dbus-org.freedesktop.NetworkManager.serviceCode: Select all
# This D-Bus service activation file is only for systemd support since
# an auto-activated ModemManager would be quite surprising for those people
# who have MM installed but turned off. Thus the Exec path available to
# D-Bus is /bin/false, but systemd knows the real Exec path due to the MM
# systemd .service file.
[D-BUS Service]
Name=org.freedesktop.ModemManager1
Exec=/usr/bin/ModemManager
User=root
SystemdService=dbus-org.freedesktop.ModemManager1.serviceI couldn't find any logs to see what is happening when Network Manager is started.
When the modem is connected to a USB port it is switched (converted) correctly (attached to ttyUSB0, ttyUSB1 and ttyUSB2).
When I start nm-applet there is no option displayed for"Enable Mobile Broadband" when I right-click on its systray icon.
antiX-14RAlpha4 is using SysVinit.
Is there something missing pertaining to SysVinit?
Thanks, MTB.
-
rokytnjiPosts: 4,164
- Joined: 20 Feb 2009
#6
When I experimented with installing network manager in Antix 14 patch5 version testing. It wanted to pull in systemd libraries.
Which because I was running sysvinit. It said it could not do. I did not post about it because
I had other issues on my IBM T23 posts I was dealing with.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/network-manager"
linktext was:"https://packages.debian.org/jessie/network-manager"
====================================
So I bailed on the idea of installing network manager in my testing install.
I am actually surprised you got a successful install going with testing repos.
But. It don't sound like it was all the way successful.
I guess you can individually search out each dependency in the link I provided and see if it got installed or not.
YepantiX-14RAlpha4 is using SysVinit.
Is there something missing pertaining to SysVinit?
When I experimented with installing network manager in Antix 14 patch5 version testing. It wanted to pull in systemd libraries.
Which because I was running sysvinit. It said it could not do. I did not post about it because
I had other issues on my IBM T23 posts I was dealing with.
Fromdep: libpam-systemd
system and service manager - PAM module
dep: libsystemd0
systemd utility library
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/network-manager"
linktext was:"https://packages.debian.org/jessie/network-manager"
====================================
So I bailed on the idea of installing network manager in my testing install.
I am actually surprised you got a successful install going with testing repos.
But. It don't sound like it was all the way successful.
I guess you can individually search out each dependency in the link I provided and see if it got installed or not.
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#7
there is a seperate modemanager-gui available in the repos...no experience with it, and I have no way to test it.
-
cuscotravelservicesPosts: 42
- Joined: 02 Jan 2015
#8
Hi Folks,
A bit of success to report. __{{emoticon}}__ I say a bit because there is still a problem to solve with Network Manager which is outside of my programming capabilities at present and the foreseeable future.
After further analysis and trial and error based on the above suggestions by Roky and D.O., I was able to determine that the Modem Manager service could be activated by installing the modem-manager-gui package and then activating the Modem Manager GUI applet from the Applications/System Tools sub-menu.
Once the Modem Manager service was activated, the Modem Manager GUI applet could be shut down (Quit) and the nm-applet could be launched with the Enable Mobile Broadband option becoming displayed in the right-click context menu from the systray icon.
The Modem was also recognised when creating a Mobile Broadband Network Connection.
However, the password was not being remembered for the Network Connection that I added for the Modem. This was partly solved by installing the gnome-keyring package but it appears to only work whilst the session is active. After rebooting, when I Edit the Connection and enter the keyring password, when prompted, the Password field for the Network Connection is vacant again. The same issue exists if attempting to activate the connection is your first interaction with the nm-applet. I haven't been able to find a solution for this. Is it a Live environment problem?
So, it appears that Network Manager has been broken with regards to launching the Modem Manager service. I've since discovered that this may be due to it expecting bloody systemd to be PID 1 which has probably been cause by some systemd moronic proponent or elitist schmuck. This was noted on the associated Debian bugs page 24/11/2014.
From that bug report, I discovered that executing the command sudo /usr/sbin/ModemManager from a Terminal will also activate the Modem Manager service. So, there is no need to install the modem-manager-gui package which can't be used for establishing a connection anyway.
If the Debian Wheezy repository was added to Synaptic and the Network Manager packages etc were downgraded, does anyone think that would provide a more reliable and convenient solution?
Thanks and hasta pronto, Sherlock __{{emoticon}}__
A bit of success to report. __{{emoticon}}__ I say a bit because there is still a problem to solve with Network Manager which is outside of my programming capabilities at present and the foreseeable future.
After further analysis and trial and error based on the above suggestions by Roky and D.O., I was able to determine that the Modem Manager service could be activated by installing the modem-manager-gui package and then activating the Modem Manager GUI applet from the Applications/System Tools sub-menu.
Once the Modem Manager service was activated, the Modem Manager GUI applet could be shut down (Quit) and the nm-applet could be launched with the Enable Mobile Broadband option becoming displayed in the right-click context menu from the systray icon.
The Modem was also recognised when creating a Mobile Broadband Network Connection.
However, the password was not being remembered for the Network Connection that I added for the Modem. This was partly solved by installing the gnome-keyring package but it appears to only work whilst the session is active. After rebooting, when I Edit the Connection and enter the keyring password, when prompted, the Password field for the Network Connection is vacant again. The same issue exists if attempting to activate the connection is your first interaction with the nm-applet. I haven't been able to find a solution for this. Is it a Live environment problem?
So, it appears that Network Manager has been broken with regards to launching the Modem Manager service. I've since discovered that this may be due to it expecting bloody systemd to be PID 1 which has probably been cause by some systemd moronic proponent or elitist schmuck. This was noted on the associated Debian bugs page 24/11/2014.
From that bug report, I discovered that executing the command sudo /usr/sbin/ModemManager from a Terminal will also activate the Modem Manager service. So, there is no need to install the modem-manager-gui package which can't be used for establishing a connection anyway.
If the Debian Wheezy repository was added to Synaptic and the Network Manager packages etc were downgraded, does anyone think that would provide a more reliable and convenient solution?
Thanks and hasta pronto, Sherlock __{{emoticon}}__