Bug 5232

so networkmanager and drakx-net does'nt work ?

By drakx-net I presume you mean draknetcenter (With four different network tools in the ap list, it's getting hard to tell), because that's the only executable in the drakx-net package that I can identify as being involved....


Yes.

Run draknetcenter.

Device is shown as present, configure button is present. Then a Please Wait window pops up with no further content, then Configure is disabled.

To get the config files for that device written at all, I can run 
/usr/bin/drakconnect which will query me for the pin and the login info. It will end in an error anyway, but it will at least generate the network script for that device in /etc/sysconfig/network-scripts and the resources in /etc/ppp.

However, even this does not change draknetcenter's behaviour.

CC: (none) => morrigan

Yes I use drakx-net to talk of all mageia network apps

Assignee: bugsquad => mageia
Source RPM: (none) => drakx-net

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

2x no reply, closing as old.

Please reopen when needed and tell for which version(s) of Mageia this bug is still valid.

If it is valid for both cauldron and Mageia 2, then please put MGA2TOO on the whiteboard and let version remain set to cauldron

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

#mageia 


2013:01:08:06:20 -!- njathan [0e617e0d@gateway/web/freenode/ip.14.97.126.13] has joined #mageia
2013:01:08:06:25 < njathan> I have been trying to connect to internet using my Huawei USB data modem
                            on mageia, but despite seeming to be successfully connecting thru
                            wvdial, internet does not work. I had used exactly the same method on
                            other distros earlier before and know that the method works. The
                            difference i see in Mageia is that when i take a look at the
                            configuration, it asks me for a pin, which i am not aware of... would
                            appreciate any help on this matte
2013:01:08:06:31 -!- njathan [0e617e0d@gateway/web/freenode/ip.14.97.126.13] has left #mageia []

So seems still valid

Keywords: NEEDINFO => (none)
Status: RESOLVED => REOPENED
Version: Cauldron => 2
Resolution: OLD => (none)

or ...
https://forums.mageia.org/en/viewtopic.php?f=25&t=4193

heres are some links that i have found after some searching
https://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=414b591fd16655871e9f5592a55368b10a3ccc30

heres a swedish link with manny drivers 
http://www.mobilabredband.se/filarkiv/

heres a swedish user that has made just the same modem i uses to work
http://blog.elis.nu/index.php/2011/12/telenor-4g-huawei-e398-med-fri-mjukvara/

im not a skilled user so i cant test this beucose i dont under stand howe to make it work

CC: (none) => mageiasv

this bug afects 32 bit also

@ MÃ¥rten

Sorry, I should have told you that for beta1 bugs, we put "3beta1" on the whiteboard

Thx for having set version to cauldron. We use "MGA2TOO" on the whiteboard to indicate that it should be fixed for Mageia 2 too, and "(MGA2)" for bugs that are present in Mga2, but that can't be fixed there (for instance installer bugs)

Cheers,
Marja

Whiteboard: MGA3 beta1 MGA2 => 3beta1 MGA2TOO

is some one looking at this bug so it will be fixed did look att fedora 18 in a live session and there could i configer but didnt conect i migth have donne something wrong with the settings

nowe its known but its listed as a wierd conection

did try fedora20 nda there can i cofiger it. if this can be to anny help

Version: Cauldron => 4
Whiteboard: 3beta1 MGA2TOO => 3beta1 MGA2TOO

Can you attach (not paste) the output of "lspcidrake -v"?

CC: (none) => thierry.vignaud
Whiteboard: 3beta1 MGA2TOO => 3beta1 MGA2TOO NEEDINFO

mga2/3 are no more supported

Whiteboard: 3beta1 MGA2TOO NEEDINFO => NEEDINFO

Plugging it in on Mageia 4 doesn't give any sign of detection.

Running Network Center shows the device and allows one to configure it (pin required), but connecting to the service provider (A1 here) still doesn't work and ends up with a panel titled "Please ..." an the content "Connecting...".

CC: (none) => herbert

Created attachment 6037 [details]
lspcidrake -v

We would need logs to see what's happening.
Can you look at journalctl output?

journalctl output is 470MB in size, anything specific you're looking for?

(In reply to Herbert Poetzl from comment #20)
> journalctl output is 470MB in size, anything specific you're looking for?

Please run
journalctl -f 2>&1 | tee journalctl-f

let it run while doing again what you described in comment 17
then stop it and attach journalctl-f

(In reply to Herbert Poetzl from comment #17)
> Plugging it in on Mageia 4 doesn't give any sign of detection.
> 
> Running Network Center shows the device and allows one to configure it (pin
> required), but connecting to the service provider (A1 here) still doesn't
> work and ends up with a panel titled "Please ..." an the content
> "Connecting...".

tv will tell you if he needs more journalctl output than that :-)

Created attachment 6042 [details]
journalctl-f

Strange: auth succeeded but then connection is closed...

Summary: HUAWEI Mobile (USB Broadband Modem) cannot be configured => HUAWEI Mobile (USB Broadband Modem) fails to connect

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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