** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/796871/+attachment/2167802/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Andrew, I've already looked into this with Mauricio outside of this bug
report. The issue is that the firmware doesn't appear to be loaded,
perhaps because there is no "valid" firmware to load for this provider
(possibly, which is why I had Mauricio try all the firmware files
available).
Sorry if
The blacklist lines in the udev rules '77-mm-qdl-device-blacklist' are
to prevent modem-manager grabbing the port before the firmware is
loaded. The firmware is loaded through a serial port on /dev/ttyUSB0.
Once the firmware is correctly loaded a new port will open up on
/dev/ttyUSB1.
The problem
none of those firmwars worked . tried all of them
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Title:
qualcomm modem wont work
To manage notifications about this bug go to:
https://bugs
No, we have everything:
modem-manager[12298]: [1308440689.323452] [mm-manager.c:793]
device_added(): (tty/ttyUSB0): port's parent device is blacklisted
Looking at this it seems as though this particular Gobi modem doesn't
properly gets its firmware loaded, perhaps?
Right now it's blacklisted by
Hi Mathieu,
do you need any other info for debuging ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Title:
qualcomm modem wont work
To manage notifications about this bug go to:
https://bugs
I hope this help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Title:
qualcomm modem wont work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemma
** Attachment added: "modem log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/796871/+attachment/2174594/+files/modem.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Ti
** Attachment added: "modem log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/796871/+attachment/2174593/+files/modem.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Ti
There is no simpler way ;)
The idea is to stop network-manager so that modemmanager can be stopped and
started again with the right switch to list debug information, then restarting
network-manager to test the connection. Then we will see all the messages
passing back and forth
between MM and
is there a simple way to debug that ? I just took a look at that, and seems
very technical .
I'm just a sales guy :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Title:
qualcomm modem wont
Could you please follow the steps here:
https://wiki.ubuntu.com/DebuggingModemmanager under Getting Debug logs
to get the current debugging logs from MM while reproducing the issue?
Also, I suspect this may need to load the correct special firmware with
gobi_loader if it's not already being done.
** Attachment added: "syslog.gz"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/796871/+attachment/2170520/+files/syslog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Title:
Bus 001 Device 003: ID 05c6:9211 Qualcomm, Inc. Acer Gobi Wireless Modem
(QDL mode)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Title:
qualcomm modem wont work
To manage notifications abou
Huh, this seems to have not worked as expected.
To figure out what was doing wrong, we'd need at least /var/log/syslog
after reproducing the problem, and the output of 'lsusb' to know the
exact USB ID for the modem.
Could you please add those to the report? Thanks!
** Changed in: modemmanager (U
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796871
Title:
qualcomm modem wont work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/796871/
16 matches
Mail list logo