Hi, just want to update that the problem still exists under 19.10 live system.
I couldn't test whether the 77-mm-huawei-net-port-types.rules fix works,
since I only have a live-USB system where I can't add the file early enough.
How do we get the Modem Manager people to decide whether the above d
And then I changed the file below and now have a working connection:
sneumann@msbi-corei:/lib/udev/rules.d$ rcsdiff -u
./77-mm-huawei-net-port-types.rules
===
RCS file: ./77-mm-huawei-net-port-types.rules,v
retrieving revision 1.1
d
And then I changed the file below and now have a working connection:
sneumann@msbi-corei:/lib/udev/rules.d$ rcsdiff -u
./77-mm-huawei-net-port-types.rules
===
RCS file: ./77-mm-huawei-net-port-types.rules,v
retrieving revision 1.1
d
Hi, just an update, no connectivity out-of-the-box
with 18.04:
Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6615]
device (ttyUSB0): Activation: starting connection 'E-Plus connection'
(bfe0f53f--cafebf693838)
Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6
Hi, just an update, no connectivity out-of-the-box
with 18.04:
Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6615]
device (ttyUSB0): Activation: starting connection 'E-Plus connection'
(bfe0f53f--cafebf693838)
Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6
I can confirm that the workaround above by Philipp Hufnagl
indeed does the job. I am writing this comment from aboard a train ;-)
The connction setup is not very robust, and sometimes
fails at Simple connect state (4/8): Wait to get fully enabled
How to get a proper fix upstream now ?
Yours, St
Even after a few apt dist-upgrades over time, no change.
dmesg has as last two lines
[ 3427.065250] cdc_ncm 1-9:2.0 wwp0s20f0u9c2: 5 mbit/s downlink 43 mbit/s uplink
[ 3443.039348] cdc_ncm 1-9:2.0 wwp0s20f0u9c2: network connection: disconnected
and journalctl has
Jan 17 07:12:03 msbi-corei Net
I also have no success with
nmcli con up id "FONIC Default"
Error: Connection activation failed: Unknown error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1735981
T
So mmcli will show me that the modem is alive,
but still the issue that I don't get an IP. Thoughts ?
mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id '0ea...129')
-
Hardware | manufacturer: 'Huawei Technologies Co., Ltd.'
| model: 'ME
And just double-checked, works under Windows.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1735981
Title:
Huawei ME936 mobile broadband can't connect
Status in mod
Hi, this is the excerpt from the journal from ModemManager and
NetworkManager
** Attachment added: "Output of journalctl -u system.slice"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+attachment/5017697/+files/network
--
You received this bug notification because you a
Public bug reported:
Hi, I have an Acer Travelmate P648 with a Huawei ME936
internal USB mobile broadband card, and can't connect.
This didn't work in 17.04, and still does not work in 17.10.
The USB device is successfully connected,
ModemManager gets as far as "Simple connect state (8/8): All d
Hi Raymond, thanks for that blazingly fast answer. I created a file
/etc/asound.conf
with the content for contro.l23/25/26/14 you posted above, was that the right
thing to do ?
This solved my other problem with automagically switching to headphones
when they are inserted, that's great! I can no
Public bug reported:
Hi,
I have an issue using the headset microphone.
hdajacksensetest will happily report the insertion and presence
of the headset (with two separate 3.5mm for input and output):
Pin 0x18 (Pink Mic, Left side): present = Yes
If I use alsamixer to increase the levels, and ena
Hi,
I can confirm the hanging on both a laptop running 14.04 and a freshly
installed 14.04,
the cups client is on a Ubuntu 10.04.4 LTS running cups 1.4.3-1ubuntu1.13
But in our case the cups server IS perfectly accessible with ping,
and nmap shows an open port 631/tcp open ipp
Removing Serv
Affected here too after creating a new key in ~/.ssh, this is 14.04 with
all updates as of today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1380084
Title:
SSH client
16 matches
Mail list logo