Laudeci Oliveira, this bug was reported a while ago and there hasn't
been any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live
Would it be possible for you to open an upstream bug report at
bugzilla.kernel.org [1]? That will allow the upstream Developers to
examine the issue, and may provide a quicker resolution to the bug.
If you are comfortable with opening a bug upstream, It would be great if
you can report back the u
The fix is definitely not upstream; it's easy enough to verify in the
code, so I'm adding the kernel-bug-exists-upstream tag and setting back
to Confirmed.
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete =>
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested
the upstream kernel, please remove the 'needs-upstream-testing' tag(Only
that one
So it indeed looks like that modem is also not currently supported at
all from what is in the debug logs for MM: it's getting claimed by the
generic plugin.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: bot-stop-nagging
--
You received this bug notification
All information as requested. Same proposed kernel and still not working
** Attachment added: "modem.log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/959863/+attachment/3041945/+files/modem.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
Setting back to Confirmed for the kernel test with 3.2.0-19.31; from
what I see in the debug log the ID is indeed still missing from the
option driver.
To continue debugging this in parallel: could you also provide debug
logs from ModemManager as it behaves after you've done the new_id
command?
*
** Attachment added: "debug.log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/959863/+attachment/290/+files/debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959863
Title:
Sending the results in the attachment.
The modem still as reported above.
** Attachment added: "ttyUSB0"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/959863/+attachment/2909997/+files/ttyUSB0
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
>From here, the best guess is that ModemManager doesn't see the modem.
Normally we should be seeing traces of it being detected in the
WifiSyslog file (which is actually just a snapshot of a grep of
/var/log/syslog).
Please follow the steps in
https://wiki.ubuntu.com/DebuggingNetworkManager#Gettin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959863
Title:
3G modem Device 1d09:1010 TechFaith Wireless Technology Limited not
detected
To manage notifications about this bug go to:
https://bugs.
13 matches
Mail list logo
