Bug 10854 - UMTS modem fails to initiate in network interface setup ('unable to open device dev/ttyACM00')
Summary: UMTS modem fails to initiate in network interface setup ('unable to open devi...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-27 13:29 CEST by Mike Grahn
Modified: 2020-07-31 12:19 CEST (History)
9 users (show)

See Also:
Source RPM: drakx-net, udev
CVE:
Status comment:


Attachments
Unable to set up UMTS modem (51.09 KB, image/png)
2015-03-05 09:11 CET, Robert Fox
Details

Description Mike Grahn 2013-07-27 13:29:28 CEST
Description of problem:

Option to set up new 3G interface finds my Nokia F3607gw modem but next sep halts with message 'unable to open device dev/ttyACM00'  

This worked using Mageia 2 

Workaround: Installing and using knetworkmanager 3.9.0.7 3.mga3 x86_64 connects the modem with the Drak network center showing the connection as wwan0.  No conflicts noted - yet......:)

I have little skill in these matters, but this may be a continuation of cauldron bug 7039 and/or may possibly be a variation of Mageia 1 bug 3841 where a script/scripts appending the 0 to the ttyACM string twice to give ACM00 rather than ACM0

Version-Release number of selected component (if applicable):
drakx-net 1.24 1.mga3 drakconf 12.38 1.mga3

How reproducible:
Every initialisation attempt on my system. Not sure if this applies to f3607gw only - bug 7039 was with this card.

Steps to Reproduce:
1.  Have system with f3607gw UMTS modem and Mageia3 
2.  Initialise 3G network interface with Mageig Control Center
3.  Obtain message unable to open ttyACM00


Reproducible: 

Steps to Reproduce:
Comment 1 Mike Grahn 2013-07-27 18:07:16 CEST
Better workaround:
Simply use a symlink:
[root@localhost xxxxx]# ln -s /dev/ttyACM0 /dev/ttyACM00

Dual use of MCC and knetworkmanager did result in conflicts.
Thierry Vignaud 2013-12-21 04:25:46 CET

CC: (none) => mageia
Source RPM: drakx-net 1.24 ? drakconf 12.38 => drakx-net-1.24, udev

Comment 2 Robert Fox 2015-03-05 09:10:32 CET
Still broken in Mageia 5 - Cauldron - workaround works but this should be fixed!

CC: (none) => rfox

Comment 3 Robert Fox 2015-03-05 09:11:28 CET
Created attachment 5992 [details]
Unable to set up UMTS modem
Comment 4 Marja Van Waes 2015-03-31 16:02:52 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 5 Vahur Krouverk 2015-06-26 19:00:13 CEST
Having exactly same problem as Robert Fox on Mageia 5 installation from Live CD (KDE 64 bit).
Bug reopened.

Status: RESOLVED => REOPENED
Resolution: OLD => (none)
Version: 3 => 5
CC: (none) => vkrouverk

Samuel Verschelde 2015-07-02 10:01:40 CEST

Assignee: bugsquad => thierry.vignaud
Source RPM: drakx-net-1.24, udev => drakx-net, udev

Samuel Verschelde 2015-07-02 10:04:29 CEST

Assignee: thierry.vignaud => mageia
CC: (none) => thierry.vignaud

Marja Van Waes 2016-02-29 09:14:01 CET

Assignee: mageia => thierry.vignaud
CC: (none) => marja11
Summary: UMTS modem fails to initiate in network interface setup => UMTS modem fails to initiate in network interface setup ('unable to open device dev/ttyACM00')

Comment 6 Marja Van Waes 2016-02-29 09:23:59 CET
The first part of bug 17827 is a duplicate of this one, CC'ing the reporter of that bug.

CC: (none) => pingvin, pkg-bugs

Comment 7 Marja Van Waes 2018-04-15 19:36:30 CEST
@ all

Thank you for having taken the needed time to report or comment about this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja
Comment 8 man draker 2018-04-18 13:51:54 CEST
Error still occures in MGA6 with F5521gw.

CC: (none) => man-draker

Comment 9 Marja Van Waes 2018-10-06 13:01:42 CEST
(In reply to man draker from comment #8)
> Error still occures in MGA6 with F5521gw.

Thx for the feedback.

Changing Version:

Version: 5 => 6

Comment 10 Nicolas Lécureuil 2020-05-30 00:10:33 CEST
is this bug still valid for you ?

CC: (none) => mageia

Comment 11 man draker 2020-05-30 07:59:15 CEST
(In reply to Nicolas Lécureuil from comment #10)
> is this bug still valid for you ?

Not anymore.
Problem vanished, connect over ppp0 is ok.
Comment 12 Robert Fox 2020-05-30 13:23:21 CEST
I think this is now gone - I have a Lenovo X1 Carbon G6 - and a Fibocom L850-GL - which unfortunately doesn't play nice with Linux:

https://forums.lenovo.com/t5/Other-Linux-Discussions/WWAN-Fibocom-L850-GL-and-Linux-support/td-p/4318903

Been struggling withit ever since . . .

This can be closed now - Thanks
Comment 13 Marja Van Waes 2020-07-31 12:19:49 CEST
Thanks for the feedback, good to know it got fixed.
Closing as OLD, because this bug was last set against Mageia 6 and no one said it was already fixed before Mageia 7.

Resolution: (none) => OLD
Status: REOPENED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.