Well, it isn't necessarily a bug. It's just that we don't know how to tell the BIOS to enable to modem.
I'm not even sure what the modem means by "BIOS" wrt forced LPM. The "W_DISABLE" flag...
Type: Posts; User: bmork; Keyword(s):
Well, it isn't necessarily a bug. It's just that we don't know how to tell the BIOS to enable to modem.
I'm not even sure what the modem means by "BIOS" wrt forced LPM. The "W_DISABLE" flag...
Yes, I agree. You are using the MC7710 in DirectIP mode (notice that the USB PID is different from QMI/MBIM mode: 68a3 != 68a2) with the sierra and sierra_net drivers, and all should be fine from the...
Thanks for the confidence, but I don't think I have much help to offer here. If it works with wvdial and sakis3g, then it isn't likely to be related to drivers. And I don't know much about the...
Yes, you have definitely found the problem. The modem is forced into "flight mode" by the pc. The modem works as expected, and there is really nothing you can do on that side to avoid this problem. ...
They've been on to that for a while already:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1102343
But please realise that this transition is all but trivial. The interface between...
Just FYI: I went on and enabled the "ZLP workaround" by default in the cdc_mbim driver. The patch should go in Linux v3.13.
It's far too intrusive to be a candidate for stable kernel releases,...
This device is supported by the CDC MBIM class driver, so it doesn't need any device specific entry. In theory.... But that's before we get to the long list of firmware bugs most likely present in...
That's odd. The 19d2:0326 ID is supposed to be the switched (modem) ID, which would indicate that usb-modeswitch had already done it's job. The unswitched ID of this device should be 19d2:0325. ...
That would be the netdev mailing list, with a CC to the linux-usb list. Both lists are @vger.kernel.org
Please make it clear that this is intended for the "net" tree (i.e destined for v3.11), and...
Great! Looking good so far.
No, this is a brand new one :-)
I do not have an immediate explanation for the WARNING. That's definitely a driver bug regardless of what trigged it. Looks like...
You already got the correct driver for this modem, so looking for other drivers is pointless.
Now, what you need is the userspace application able to configure and connect it. MBIM is a pretty...
The modem was disconnected from the USB bus. Based on your report I assume that you didn't trigger this (using rfkill or a radio killswitch). The only likely cause remaining is a firmware crash. I...
This looks fishy, but apparently it's working despite those warnings....
OK, so you got one mass storage interface. That's typical for mode switching devices. Good start. Looking at the...
Thanks for the confidence, but I would have to see a lot more logs and command output to have any clue what's going on here. So far I've only seen "it doesn't work" and that could have a gazillion...
Someone should really rewrite that script....
Anyway, the C: line is the only interesting one here. Configuration #0 means that the USB core has failed to configure this device at all. No need...
I don't think that modem is supported just yet. But if you're lucky, adding the support shouldn't take long. Could you start with posting the output of
lsusb -vd 0408:ea25
?
And if that...
Neither ModemManager nor NetworkManager require a GUI. They are dbus based daemons. The use cases definitely includes more than just laptops, but of course not complex routers or really advanced...
Yes, you will most likely want some monitoring daemon of some sort to manage those interfaces. The modems will respond to dhcp requests, but only after the connection is up. So you need something...
Well, that was an assumption. I haven't really verified it. Sierra Wireless could have implemented support for these commands regardless of mode I guess, and your success with them supports that.
...
This all looks good. Is routing OK? What does "ip route" say? The netmask looks weird for a mobile broadband modem. How did you configure these addresses? I assume this didn't come from the...
Aw, right. Thanks for clarifying. I should have noticed the serial number...
The procedure for changing PID is documented here: http://forum.sierrawireless.com/viewtopic.php?f=117&t=6759
...
Right. That's nice. Yes, your modeswitch configuration looks fine based on that lsusb output, and there should be a number of drivers picking up this device. Does it work better if you run
sudo...
This device seems to be unknown so far, so I guess we should add it here and there. Could you post the output of "lsusb -vd 230d:0103" for a start?
How did you come up with exactly that...
Look at the "runtime_*" files to verify that autosuspend works. If runtime_suspended_time > 0 then the device has been autosuspended. Example:
bjorn@nemi:~$ grep ....
This was a bit surprising to me. I've so far only seen the MC7710 appear as 68a3 in DirectIP mode and 68a2 in QMI mode. Do you happen to know why the ID is what it is here (like: you've set it to...