Description of problem: The key is not automatically recognized by the network manager solution found: http://www.mageialinux-online.org/articles/articles-15-94+cle-3g-non-reconnue-automatiquement-par-magei.php
The link doesn't work for me, it says "Vous n'avez pas le niveau requis".
CC: (none) => stormi
correct link: http://www.mageialinux-online.org/articles/articles-15-94+cle-3g-non-reconnue-automatiquement-par-mageia.php add the file /etc/udev/rules.d/99-3g.rules with: SUBSYSTEM=="usb", ATTRS{idProduct}=="1446", ATTRS{idVendor}=="12d1", RUN+="/usr/sbin/usb_modeswitch -v 0x12d1 -p 0x1446 -V 0x12d1 -P 0x1001 -M 55534243123456780000000000000011062000000100000000000000000000 -s 10 -W"
URL: (none) => http://www.mageialinux-online.org/articles/articles-15-94+cle-3g-non-reconnue-automatiquement-par-mageia.phpAssignee: bugsquad => eandry
I still get "Vous n'avez pas le niveau requis" :/
Keywords: (none) => PATCHSource RPM: (none) => udev
http://www.mageialinux-online.org/wiki/cle-3g-non-reconnue-automatiquement-par-mageia should be correct
URL: http://www.mageialinux-online.org/articles/articles-15-94+cle-3g-non-reconnue-automatiquement-par-mageia.php => http://www.mageialinux-online.org/wiki/cle-3g-non-reconnue-automatiquement-par-mageia
I've got the same problem with the modem 3g on eeepc 901. drakconnect don't detect the 3g device, even when I add a 99-3g.rules files with values from /usr/share/_usb_modeswitch.
CC: (none) => tremyfr
lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 003 Device 002: ID 04fc:05da Sunplus Technology Co., Ltd
driver option detect the device : USB Serial support registered for GSM modem (1-port) option 1-6:1.0: GSM modem (1-port) converter detected usb 1-6: GSM modem (1-port) converter now attached to ttyUSB0 option 1-6:1.1: GSM modem (1-port) converter detected usb 1-6: GSM modem (1-port) converter now attached to ttyUSB1 option 1-6:1.2: GSM modem (1-port) converter detected usb 1-6: GSM modem (1-port) converter now attached to ttyUSB2 usbcore: registered new interface driver option option: v0.7.2:USB Driver for GSM modems but 3g can't be configured in drakconnect ...
Hum why I have assigned this bug to eandry ? :/ Add blino in CC (cf comment 7)
CC: (none) => mageiaSource RPM: udev => udev ?
My 3g key is detected and works fine if I mount /proc/bus/usb To get his, I have used this command: mount -n -t usbfs -o devmode=0664,devgid=43 /proc/bus/usb /proc/bus/usb
(In reply to comment #9) > My 3g key is detected and works fine if I mount /proc/bus/usb > > To get his, I have used this command: > mount -n -t usbfs -o devmode=0664,devgid=43 /proc/bus/usb /proc/bus/usb That's already being done by line 968 of /etc/rc.d/rc.sysinit (line 90, or 92 if speedboot has been selected), so that shouldn't make any difference.
CC: (none) => davidwhodgins
(In reply to comment #9) > My 3g key is detected and works fine if I mount /proc/bus/usb > > To get his, I have used this command: > mount -n -t usbfs -o devmode=0664,devgid=43 /proc/bus/usb /proc/bus/usb You have another issue which is specific to systemd and Mageia Cauldron, please open another bug report
3-monthly ping
CC: (none) => marja11
Assignee: eandry => bugsquad
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and 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. 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. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX