I've got the same problem with ZTE MF636 - modem manager uses ttyUSB2, while it
should be ttyUSB3.
I think I found a little simpler solution to this problem, just added one line
to /lib/udev/rules.d/77-mm-zte-port-types.rules:
ATTRS{idProduct}=="0033", ENV{.MM_USBIFNUM}=="04",
ENV{ID_MM_ZTE_PO
Still nothing I've disabled PIN, restart modemmanager and network-
manager but nothing start the modem
Samsung RC530
Ubuntu Precise 12.04 - amd64 - 3.5.0-030500-generic
Bus 001 Device 023: ID 19d2:0031 ZTE WCDMA Technologies MSM MF110/MF627/MF636
usb_modeswitch corrrectly switch from 19d2:2000
Still nothing I've disabled PIN, restart modemmanager and network-
manager but nothing start the modem
Using Ubuntu Precise 12.04 - 3.5.0-030500-generic
Bus 001 Device 023: ID 19d2:0031 ZTE WCDMA Technologies MSM
MF110/MF627/MF636
** Attachment added: "syslog"
https://bugs.launchpad.net/ubu
Running 12.04 on Asus UX21.
"#lsusb -d 19d2:0031 " results in nothing but:
Bus 002 Device 007: ID 19d2:0031 ZTE WCDMA Technologies MSM MF110/MF627/MF636
When connecting to another USB port:
"#lsusb -d 19d2:2000" results in nothing but:
Bus 003 Device 003: ID 19d2:2000 ZTE WCDMA Technologies MSM
The device needs to be connected. If it's listed in lsusb itself, then
running the same "sudo lsusb -d 19d2:0033" command should list the
device properties. Without those, there is nothing I can do about this
bug.
Maybe try another number for the modem if that's what shows up; anything
starting wi
** Also affects: baltix
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04 11.10 12.04)
T
still none ??
no output at all ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04 11.10 12.04)
To manage notifications about this b
What is the output of "sudo lsusb -d 19d2:0033" ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04 11.10 12.04)
To manage notificat
this is my lsusb output
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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
No, we can't use this workaround at all. Sorry.
If lsusb just returns, that means it's the wrong USB ID. Does lsusb
(without parameters) list a device starting with 12d1? That's the one
you'll want to use, with vendor and product ID to pass to lsusb with the
-d switch.
--
You received this bug n
and I can confir, this workaround makes my modem works >> usb-storage / cdrom /
modem
so , untill someone fixes this issue plz consider make the modem usable for
users :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
actually when i execute the command nothing appear only gives me the prompt
again ?
sudo lsusb -d 12d1:0033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on
This is not something we can use as a workaround, since you'd be losing
USB2 which has a purpose (otherwise it wouldn't be provided).
This needs a fix in the modemmanager whitelist udev rules, or in the
kernel driver in use.
These are the revelant udev lines from modemmanager's
/lib/udev/rules.d/
actually it's a workaround that using udev rules to execute a patch when
connecting the modem
the patch delete /dev/ttyUSB2
and symlink /dev/ttyUSB3 to /dev/ttyUSB2
the dev rules
/etc/udev/rules.d/90-zte.rules
##
ACTION!="add", GOTO="ZTE_End"
Amr Osman, please provide a proper patch instead of a deb package, we
can't review a deb package.
Also, it would be nice if someone having this issue could report it
upstream as suggested by Aleksander.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
i have create a udev patch that fixes the issue in a dirty way until a fix is
commited
this is the deb file
** Attachment added: "zte patch"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441/+attachment/2878735/+files/zte-patch_0.1_all.deb
--
You received this bug notifica
I have discovered a workaround
http://ubuntuforums.org/showpost.php?p=11768480&postcount=10
check it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad ttyU
This bug is worth reporting upstream.
https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad tt
** Summary changed:
- ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04)
+ ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04 11.10 12.04)
** Description changed:
Hi,
ZTE MF190 = ID 19d2:0124 ONDA Communication S.p.A.= (0x0149/0x124 CD/3g
Modem)
+
+ also (19d2:0033)
This
19 matches
Mail list logo
