Bug 1031 - mobile internet doesn't work
Summary: mobile internet doesn't work
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-04-28 17:27 CEST by Henk Elbers
Modified: 2012-06-16 19:05 CEST (History)
3 users (show)

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


Attachments
logfiles concerning bug 1031 (34.98 KB, application/octet-stream)
2011-11-15 20:32 CET, Henk Elbers
Details

Description Henk Elbers 2011-04-28 17:27:55 CEST
Setting up a network with a USB-modem  (Huawei, idVendor=12d1, idProduct=1001)
does not work.

Mageia 1 beta-2 with all updates until 28-04-2011 14:00


How reproducible:

- plug in usb-modem
  it is recognised by the kernel
- start drakconf - network&internet - setup new network - GPRS/Edge/3G
  - ppp0: YYYYYYYY HUAWEI Mobile - next
  - Pin: #### - next
  - select network: 20404 - next
  - provide: NL - vodafone - next
  - access point name: live.vodafone.com
  - user: vodafone
  - password: vodafone - next
  - next
  - start connection: yes - next
Please wait ...

last part of logging:

Apr 28 14:39:39 hardy chat[17540]: ATDT*99***3#^M^M
Apr 28 14:39:39 hardy chat[17540]: CONNECT
Apr 28 14:39:39 hardy chat[17540]:  -- got it
Apr 28 14:39:39 hardy chat[17540]: send (^M)
Apr 28 14:39:39 hardy chat[17540]: timeout set to 5 seconds
Apr 28 14:39:39 hardy chat[17540]: expect (~)
Apr 28 14:39:39 hardy chat[17540]: ^M
Apr 28 14:39:44 hardy chat[17540]: alarm
Apr 28 14:39:44 hardy chat[17540]: send (^M)
Apr 28 14:39:44 hardy chat[17540]: send (^M)
Apr 28 14:39:44 hardy pppd[17508]: Serial connection established.
Apr 28 14:39:44 hardy pppd[17508]: Using interface ppp0
Apr 28 14:39:44 hardy pppd[17508]: Connect: ppp0 <--> /dev/ttyUSB0
Apr 28 14:39:48 hardy pppd[17508]: CHAP authentication succeeded
Apr 28 14:39:48 hardy pppd[17508]: CHAP authentication succeeded
Apr 28 14:39:50 hardy pppd[17508]: Hangup (SIGHUP)
Apr 28 14:39:50 hardy pppd[17508]: Modem hangup
Apr 28 14:39:50 hardy pppd[17508]: Connection terminated.
Apr 28 14:39:50 hardy avahi-daemon[3100]: Withdrawing workstation service for ppp0.
Ahmad Samir 2011-07-20 16:53:19 CEST

Source RPM: (none) => drakx-net

Comment 1 Marja Van Waes 2011-10-10 21:54:30 CEST
@ Henk

Is the problem still there in current cauldron?

If so:

Are there errors in /var/log/messages related with connection and in dmesg.txt that results from running "dmesg > /tmp/dmesg.txt"

Also, if the problem still exists, please provide the output of

lspcidrake -v

output and of

iwconfig

and

iwlist scan

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 Marja Van Waes 2011-10-23 15:20:03 CEST
Henk sent a mail, telling that it doesn't work with present cauldron, but that one of his HD's died and he'll supply more information when he's got a working cauldron again
Marja Van Waes 2011-10-24 21:25:30 CEST

CC: (none) => mageia

Comment 3 Henk Elbers 2011-11-15 20:32:35 CET
Created attachment 1062 [details]
logfiles concerning bug 1031
Comment 4 Henk Elbers 2011-11-15 20:33:46 CET
I have some new HD's, a new motherboard and a fresh up-to-date Cauldron.
The bug is still there. See logfiles in the attachment.
Comment 5 Marja Van Waes 2011-11-15 20:56:13 CET
(In reply to comment #4)
> I have some new HD's, a new motherboard and a fresh up-to-date Cauldron.
> The bug is still there. See logfiles in the attachment.

Thanks, Henk, for providing all the requested information.

Assigning to maintainer.

Keywords: NEEDINFO => (none)
Assignee: bugsquad => mageia

Comment 6 Derek Jennings 2012-02-05 17:19:15 CET
I have the same problem with the same device and managed to get it working with a workaround.

On inserting the modem dmesg shows
usb 1-1: new high speed USB device using ehci_hcd and address 4
usb 1-1: New USB device found, idVendor=12d1, idProduct=1001
usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 1-1: Product: HUAWEI Mobile
usb 1-1: Manufacturer: HUAWEI Technology
option 1-1:1.0: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
option 1-1:1.1: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
option 1-1:1.2: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2

but if you look at the actual devices created ttyUSB0 has become ttyUSB_utps_modem

# ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 1 Feb  5 15:48 /dev/ttyUSB_utps_diag
crw-rw---- 1 root dialout 188, 0 Feb  5 15:51 /dev/ttyUSB_utps_modem
crw-rw---- 1 root dialout 188, 2 Feb  5 15:48 /dev/ttyUSB_utps_pcui

Create a symlink to ttyUSB0 and drakconnect works.
ln -s /dev/ttyUSB_utps_modem /dev/ttyUSB0

Editing /etc/sysconfig/network-scripts/ifcfg-ppp0
to set
MODEMPORT=/dev/ttyUSB_utps_modem
also works

CC: (none) => derekjenn

Comment 7 Derek Jennings 2012-02-06 01:36:35 CET
Sorry, Ignore Comment 6. I had some udev rules left over from an old proprietary dialler which created those nodes. With them removed drakx-net works for me.
Comment 8 Marja Van Waes 2012-05-09 15:18:06 CEST
3 monthly ping

@ Henk

is this bug still valid with Mageia 2 rc?
http://blog.mageia.org/en/2012/05/09/almost-there-download-mageia-2-rc-new-date-for-final-release/

Keywords: (none) => NEEDINFO

Comment 9 Marja Van Waes 2012-05-26 13:08:02 CEST
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
Comment 10 Marja Van Waes 2012-06-16 19:05:20 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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


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