[Samsung CMC-370] MEZON modem not detected

I tried: Ubuntu 11.10 32 and 64 bib, Ubuntu DVD version on three different computers. Always the same problem.

Thanks for your report.

I think that part of this problem may be related to NetworkManager (the Ubuntu subsystem responsible for detecting and handling network and Internet connections).

Please check your network icon at the top right of your screen (next to the clock). Does the icon say that the connection is working (it should not show a red cross)?

Yes. When the MEZON modem are connected network icon does not show any network, but the internet works. Through the command line I can download and install all the programs, but software center are not installing programs. But it is downloading all information about software and comments, but not installing.

A similar problem was on Ubuntu 10.10 with Mezon modem. Firefox always run disconnected from the network.

it definitely seems to be a NetworkManager problem. Software Center relies on it to detect if the connection is present or not, so if it does not sense your modem connection Software Center believes you are not connected.

Could you please open a terminal and then perform the following actions?

1) Install the latest development version of NetworkManager by running:
sudo apt-add-repository ppa:network-manager/trunk
sudo apt-get update
sudo apt-get dist-upgrade

2) Stop NetworkManager with:
sudo stop network-manager

3) Start to capture the system logs by opening another terminal and running:
tail -n0 -f /var/log/syslog > /tmp/syslog
The command will not stop, it's normal.

4) Return to the first opened terminal. Restart ModemManager (a NetworkManager component) and NetworkManager itself with:
logger "Killing Modem Manager"
sudo killall modem-manager
logger "Starting Modem Manager"
sudo modem-manager --debug 2>&1 | tee /tmp/modem.log.txt
export NM_PPP_DEBUG=1
logger "Starting NetworkManager"
sudo NetworkManager --no-daemon 2>&1 | tee /tmp/nm.log.txt
logger "Starting new connection creation"

Try then to create a new connection (in NetworkManager itself) using the MEZON modem. Don't worry if it does not work, the exact causes of the error will be recorded.

5) Run some quick modem and network tests:
wget http://cgit.freedesktop.org/ModemManager/ModemManager/plain/test/mm-test.py
logger "Starting Modem Manager test"
python ./mm-test.py >/tmp/mmtest.log 2>&1
logger "Starting NetworkManager debug"
sudo python debug-helper.py --nm debug
logger "Getting WPA logs"
sudo python debug-helper.py --wpa msgdump

6) Switch back to the second terminal (the one where you started to capture system logs) and press Ctrl+C. This will stop the capture.

7) Finally, collect some information about your hardware with:
udevadm info --query=all --path=/sys/class/tty/... --attribute-walk >/tmp/udevadm.log 2>&1
lsusb >/tmp/lsusb.log 2>&1

8) Attach the files "/tmp/syslog", "/tmp/modem.log.txt", "/tmp/mmtest.log", "/tmp/nm.log.txt", "/tmp/udevadm.log", "/tmp/lsusb.log" to this bug report.

The procedure is fairly complicated, but it will help us establishing the exact nature of the bug.

Thanks!

I got stuck on
~$ sudo modem-manager --debug 2>&1 | tee /tmp/modem.log.txt

It returns a lot of similar lines
modem-manager[2210]: <info> [1321108444.103642] [main.c:167] main(): ModemManager (version 0.5) starting...
And stops on line
modem-manager[2210]: <debug> [1321108444.116024] [mm-manager.c:793] device_added(): (net/wimax0): could not get port's parent device

pointer stay on new empty line. Do not returns to line. ~$
Is the way it should be? Because it seem to be not execute other commands. So I went back to normal with Ctrl+C. I executed other commands.

I think that's the way it should be (ModemManager is in fact running and the terminal will not return to the prompt ~$ until the program terminates).

Anyway, I've looked at your logs, it seems that your modem is not supported. Could you please post here the output of "lsusb" again (and give me the exact make and model of your modem, preferably also a link to its manufacturer's Web page) so that I'll be able to determine the chipset? Thanks!

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 001 Device 004: ID 04e8:6780 Samsung Electronics Co., Ltd
Bus 002 Device 004: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 004 Device 002: ID 056e:005a Elecom Co., Ltd
Bus 006 Device 002: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
Bus 006 Device 003: ID 04f2:0200 Chicony Electronics Co., Ltd

Name: SAMSUNG SWC-U200 MEZON USB MODEM
I bought it in the store (in Lithuanian)
http://www.mezon.lt/isigyk/papildoma-informacija/atnaujinkite-mezon-usb-modemo-tvarkykles/id/712/
I use these drivers madwimax_160-0ubuntu1_amd64.deb

Only now I noticed that after all these commands program center began working.
NetworkManager are stoped. Maybe because of this?
Installation buttons are active even when no Internet connection. Now I can install the deb files from the hard disk.

Yes, I think that if NetworkManager is stopped Software Center just presumes that a connection is active and lets you continue.

Could you see if installing the madwimax package from the Ubuntu repositories solves the problem?

In Software Center I found only one wimax driver "madwimax 160-0ubuntu1" which is already installed (based on Samsung CMC-730 chip). I can only uninstall it. But if I will uninstall it I can not install it from Software Center because I have only Wimax internet.
Well stopping NetworkManager solves the problem of deb files installation, but when it is running again, the problem recurs (after you reboot computer).
Thus, the temporary solution for installation deb files can be solved by switching off NetworkManager or installing through the command line.

I have updated your original bug description so that bug testers will be able to find all the relevant information quickly. Now, if another Ubuntu user manages to reproduce the bug, we will be certain that it does not depend on your particular system
configuration.

As I don't have a MEZON modem myself, if you know someone else that is willing to try out on his Ubuntu installation, please ask him to test and report here. I'm also asking on the Ubuntu IRC channels. For the moment, I'll leave the report status as "New".

As I said in my first comment.
I tried: Ubuntu 11.10 32 bit, 64 bit and Ubuntu DVD version on three different computers. With the same modem. And got always the same problem.

What about installing deb files? If you are not online, you can not install deb files.

It's an established Ubuntu policy that another person (not the original reporter) should confirm the bug separately: <https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming>. I have searched for existing bug reports and upstream reports (that would have allowed me to confirm your report straight away), but with no success. (Sorry if I may seem rude or absurd).

As for your second observation, I'm trying to reproduce the bug myself and (in case) open a second separate bug report. Thanks for pointing it out.

I tried ubuntu 11.10 32 bit, 64 bit and Linux Mint 64 bit, based on ubuntu 11.10. same problem. the only way to install u200 modem was to shut down network manager.
i am not a linux-genius and i can't stand having network problems. it's ok, when bugs are not related to networking, because i can figure out those by myself, using google. but if a problem is related to network and i CAN'T reach google because i have only wimax connection then i have no other option than installing older version of linux, which supports my network device.

sorry, too sad for me ;D

thank you guys for teaching me how to shut down network manager, that was SO helpful yet, at least until i can install deb files from my hard <;

good luck!!

NetworkManager doesn't have WiMAX enabled; so confirming the bug. I don't think this would be working in Precise either, but worth a test.

There's a substancial amount of work necessary to make this work in Ubuntu, and is currently being done in parallel in Debian. The biggest issue will be to enable libeap building as a separate part from wpasupplicant, at which point we'll then be able to release the wimax drivers and sdk, and in turn, enable WiMAX support in NetworkManager.

Setting Triaged/Medium -- the work needed is clear, just needs to be done and it's non-trivial.

Status changed to 'Confirmed' because the bug affects multiple users.

Latest Wimax (4G, named 'Mezon' in Lithuania) modem drivers for Ubuntu and other Linux distributions are available at http://mezon.crit.lt/ and at http://ftp.akl.lt/Linux/Baltix/Baltix-Ubuntu-packages/baltix-4.x/madwimax-mezon/