Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: ZTE MF637 and NetwokManager .service

  1. #1

    Default ZTE MF637 and NetwokManager .service

    This is my very firs attempt with openSUSE.
    I am to setting up a ZTE MF637 mobilinternet stick. I got the next error:
    "The name org.freedesktop.NetworkManager was not provided by any .service files"
    Any help please!

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: ZTE MF637 and NetwokManager .service

    You'll need to detail:

    Which distro and version
    Which Desktop
    If this is a brand new install, have you rebooted? There is a well known bug that the networking services don't always start in the correct order, the simplest solution is to simply reboot.

    You may also need to post a few more log entries before the one you posted so that context can be given when the error was generated.

    TSU

  3. #3

    Default Re: ZTE MF637 and NetwokManager .service

    Yes, you are right! I was in a hurry and made a mistake, sorry!
    My system is openSUSE 13.1, KDE desktop, installed yesterday (3-3-2014), updated at once. I have rebooted several times.
    Find attached logs, and the output of systemctl status NetworkManager.service.

    [attache]file:///home/sp/Dokumentumok/tail50_NetworkManager[/attache]
    [attache]file:///home/sp/Dokumentumok/tail50_messages[/attache]
    [attache]file:///home/sp/Dokumentumok/NM.status[/attache]

  4. #4

    Default Re: ZTE MF637 and NetwokManager .service

    Actually I didn't attached any file. There is probably some old text in FAQ, or I am lame a little. Sorry

  5. #5

    Default Re: ZTE MF637 and NetwokManager .service

    On 03/04/2014 05:26 PM, susyp pecked at the keyboard and wrote:
    > Actually I didn't attached any file. There is probably some old text in
    > FAQ, or I am lame a little. Sorry
    >
    >


    Use susepaste.org to paste contents and provide the links here.

    Ken

  6. #6

    Default Re: ZTE MF637 and NetwokManager .service

    Thank you Ken!
    http://www.susepaste.org/49783744 - Networkmanager.log
    http://www.susepaste.org/23421605 - Messages.log
    http://www.susepaste.org/85762541 - output of systemctl status NetworkManager.service

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: ZTE MF637 and NetwokManager .service

    Unfortunately,
    At least to my eye your posted logs don't display sufficient information, no errors I see of note.

    So, I suspect...
    Network Manager itself seems to be running properly (status is active and running).
    That leads me to suspect that the problem more likely has something to do with your modem.

    Are you sure you've configured its dialup properties correctly in NM?

    Note that <some> people have more success using something like wvdial instead of nm for dialup connections.
    Been awhile since I've used dialup, so I can't personally opine.

    TSU

  8. #8
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: ZTE MF637 and NetwokManager .service

    This is the log section that reports intialization of the mobile broadbnad device
    Code:
    1. 2014-03-04T22:14:51.052087+01:00 linux-o5ix NetworkManager[725]: <warn> (ttyUSB2): failed to look up interface index
    2. 2014-03-04T22:14:51.055050+01:00 linux-o5ix NetworkManager[725]: <info> (ttyUSB2): new Broadband device (driver: 'option1' ifindex: 0)
    3. 2014-03-04T22:14:51.055451+01:00 linux-o5ix NetworkManager[725]: <info> (ttyUSB2): exported as /org/freedesktop/NetworkManager/Devices/2
    4. 2014-03-04T22:14:51.055800+01:00 linux-o5ix NetworkManager[725]: <info> (ttyUSB2): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    5. 2014-03-04T22:14:51.057594+01:00 linux-o5ix NetworkManager[725]: <info> (ttyUSB2): deactivating device (reason 'managed') [2]
    6. 2014-03-04T22:14:51.058146+01:00 linux-o5ix NetworkManager[725]: <info> (ttyUSB2): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
    7. 2014-03-04T22:16:34.837665+01:00 linux-o5ix NetworkManager[725]: <warn> (ttyUSB2) cannot enable modem: locked
    8. 2014-03-04T22:16:34.838723+01:00 linux-o5ix NetworkManager[725]: <info> (ttyUSB2): device state change: disconnected -> need-auth (reason 'none') [30 60 0]
    9. 2014-03-04T22:16:34.839260+01:00 linux-o5ix NetworkManager[725]: <info> NetworkManager state is now CONNECTING
    Unfortunately, it is not clear to me about what is failing. This might take time to research further.

    Here is a ModemManager debug guide

    http://www.freedesktop.org/wiki/Soft...ger/Debugging/

    It shows how to generate verbose debug logs specifically for reporting ModemManager issues.

  9. #9

    Default Re: ZTE MF637 and NetwokManager .service

    So! I generated logs. I don't know what output has ModemManager logging. Anyway I couldn't find it.

    http://www.susepaste.org/2756781
    http://www.susepaste.org/41106308

    But my mind mistake is in configuring. According to my ISP in this network mobilinternet doesn't need any DNS address. Among NetworkManager settings I can find DNS addresses and I can not disable or delete them.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,704
    Blog Entries
    1

    Default Re: ZTE MF637 and NetwokManager .service

    Quote Originally Posted by susyp View Post
    So! I generated logs. I don't know what output has ModemManager logging. Anyway I couldn't find it.
    The ModemManager logging needs to be enabled as explained in the guide I linked to. It then logs to /var/log/NetworkManager

    Anyway, I note the following warning could well be to do with incorrect or missing PIN (so that the modem can then be unlocked). Not all SIM cards are set that way, but maybe yours is?
    Code:
    2014-03-04T18:07:02.037869+01:00 linux-o5ix NetworkManager[754]: <warn> (ttyUSB2) cannot enable modem: locked
    The configuration settings are provider specific, and if ModemManager doesn't cater to your service povider, it is possnile to enter the required settings manually.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •