Bug 1712 - GPRS HDSPA modem fails (missing softlink from /dev/ttyHS1 to /dev/ttyHS)
Summary: GPRS HDSPA modem fails (missing softlink from /dev/ttyHS1 to /dev/ttyHS)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on: 6675
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-09 14:26 CEST by Franz Holzinger
Modified: 2015-10-27 06:57 CET (History)
9 users (show)

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


Attachments

Description Franz Holzinger 2011-06-09 14:26:00 CEST
When I try to connect with the O2 Globetrotter then I get an error dialog box:
Unable to open device /dev/ttyHS

This USB stick UMTS modem did work fine under Mandriva 2009-2010.
Comment 1 Franz Holzinger 2011-06-09 19:50:35 CEST
The kernel is 2.6.38.7-desktop-1.mga.
Comment 2 Franz Holzinger 2011-06-09 20:53:18 CEST
Identification
Vendor: âOption N.V.
Description: âGlobetrotter HSDPA Modem  
Media class: â
Connection
Bus: âUSB
Bus PCI #: â6
PCI device #: â5
Vendor ID: â0x0af0
Device ID: â0x6971
Misc
Module: âhso
Comment 3 Franz Holzinger 2011-06-12 10:44:57 CEST
here are more details with the steps I have tried:

[root@localhost ~]#   usb_modeswitch -v 0x0af0 -p 0x6971

Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 003 on bus 006 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x03 (out) and 0x83 (in)
Using endpoints 0x03 (out) and 0x83 (in)
Not a storage device, skipping SCSI inquiry

USB description data (for identification)
-------------------------
Manufacturer: Option N.V.
     Product: Globetrotter HSDPA Modem
  Serial No.: Serial Number
-------------------------
Warning: no switching method given.
-> Run lsusb to note any changes. Bye.


[root@localhost ~]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b053 Chicony Electronics Co., Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 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 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 003: ID 0af0:6971 Option Globetrotter HSDPA Modem
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


# modprobe usbserial vendor=0x0af0 product=0x6971

# uname -r
2.6.38.7-tmb-desktop-1.mga
Comment 4 Franz Holzinger 2011-06-12 13:43:18 CEST
I have found the soltution thanks to the forum

http://www.mandrivauser.de/forum/viewtopic.php?f=95&t=29500&p=262764#p262764

[root@localhost]# ln -s  /dev/ttyHS1 /dev/ttyHS

The O2 USB Globetrotter works after having created this symbolic link.




[root@localhost]# ls -l /dev/ttyHS*
lrwxrwxrwx 1 root root        11 juin  12 13:25 /dev/ttyHS -> /dev/ttyHS1
crw-rw---- 1 root dialout 251, 0 juin  12 13:28 /dev/ttyHS0
crw-rw---- 1 root dialout 251, 1 juin  12 13:29 /dev/ttyHS1
crw-rw---- 1 root dialout 251, 2 juin  12 13:28 /dev/ttyHS2
Manuel Hiebel 2011-10-03 01:30:32 CEST

Keywords: (none) => PATCH
Source RPM: (none) => udev

Comment 5 Samuel Verschelde 2011-10-04 21:33:36 CEST
Adding udev committers in CC. Can one of you help identify the problem reported here?

CC: (none) => anssi.hannula, dmorganec, eugeni, mageia, stormi, thierry.vignaud, tmb

Comment 6 Thierry Vignaud 2011-10-06 10:22:01 CEST
Or a config bug (drakx-net used to configure ttyHS0, not ttyHS).
How did you configure it?

Keywords: PATCH => NEEDINFO
CC: (none) => mageia

Comment 7 Marja Van Waes 2011-12-06 15:24:17 CET
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, we can close this bug as OLD. Thank you.

CC: (none) => marja11

Comment 8 Marja Van Waes 2011-12-06 19:27:37 CET
Op 06-12-11 17:52, Franz Holzinger wrote:
> Hello Marja van Waes,
>
> I am sorry to write to you directly.
> I am not able to login, because it never accepts my password.
> So I tried to reset the password. I tried it for 3 times. It always fails. I do not know how to report this.
>
> I wanted to post, that this is a USB modem. I do never configure a USB hardware. It must autoconfigure itself.
>
> Regards,
>
> Franz Holzinger
Comment 9 Marja Van Waes 2011-12-06 19:32:03 CET
@ Franz

IIRC, your bugzilla identity is the same as your Mageia identity.

Try getting a new password here:

https://identity.mageia.org/forgot_password

and fill out the e-mail address that bugzilla daemon uses to mail you.
Comment 10 Marja Van Waes 2011-12-06 20:01:01 CET
(In reply to comment #8)

> > I wanted to post, that this is a USB modem. I do never configure a USB hardware. It must autoconfigure itself.

@ Thierry
Do you need more information?
Comment 11 Marja Van Waes 2011-12-09 11:53:32 CET
On 09/12/11 11:28, Franz Holzinger wrote:
> Dear Marja van Waes,
>
> unfortunately I have no success in changing the password for my user account <snip>
> It always fails to accept my modified password. " Incorrect username or 
> password". Why does this not work? I am not able to report this anywhere.
>

When logging in after receiving a new password, you use your nick as username and not your e-mail address. Sorry I didn't tell you :/

Please mail me again if you still can't get it to work

>
> The bug #1712 can be closed.
> There is no problem with the USB modem under the kernel 2.6.38.8-desktop-6.mga .
>
> Regards,
>
> Franz Holzinger

So apparently fixed by an update
Thanks for giving the feedback :)

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

Comment 12 Franz Holzinger 2012-08-10 20:21:44 CEST
This bug is back again in Mageia 2. You must mount the internet USB stick manually.
However it is worse than ever before. No connection with 02 is possible at all. The usb stick never connects to the internet.

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

Comment 13 Franz Holzinger 2012-08-17 15:24:36 CEST
These are the messages from the syslog after I insert the Globetrotter Internet stick and try to connect via the NetApplet. It then hangs trying to connect to the internet.


Aug 17 15:18:25 localhost mtp-probe: checking bus 7, device 63: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-5"
Aug 17 15:18:25 localhost mtp-probe: bus: 7, device: 63 was not an MTP device
Aug 17 15:18:30 localhost kernel: [  387.675243] usb 7-5: USB disconnect, device number 63
Aug 17 15:18:30 localhost kernel: [  387.786037] usb 7-5: new high-speed USB device number 64 using ehci_hcd
Aug 17 15:18:30 localhost kernel: [  387.947096] usb 7-5: New USB device found, idVendor=04f2, idProduct=b053
Aug 17 15:18:30 localhost kernel: [  387.947100] usb 7-5: New USB device strings: Mfr=2, Product=1, SerialNumber=3
Aug 17 15:18:30 localhost kernel: [  387.947103] usb 7-5: Product: CKA7216
Aug 17 15:18:30 localhost kernel: [  387.947104] usb 7-5: Manufacturer: Chicony Electronics Co., Ltd.
Aug 17 15:18:30 localhost kernel: [  387.947106] usb 7-5: SerialNumber: SN0001
Aug 17 15:18:30 localhost kernel: [  387.949537] uvcvideo: Found UVC 1.00 device CKA7216 (04f2:b053)
Aug 17 15:18:30 localhost kernel: [  387.965878] input: CKA7216 as /devices/pci0000:00/0000:00:1a.7/usb7/7-5/7-5:1.0/input/input70
Aug 17 15:18:30 localhost mtp-probe: checking bus 7, device 64: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-5"
Aug 17 15:18:30 localhost mtp-probe: bus: 7, device: 64 was not an MTP device
Aug 17 15:19:16 localhost net_applet[18005]: ### Program is starting ###
Aug 17 15:19:16 localhost net_applet[18005]: ### Program is exiting ###
Aug 17 15:19:35 localhost net_applet[3347]: running: /usr/bin/draknetcenter
Aug 17 15:19:36 localhost draknetcenter[18701]: ### Program is starting ###
Aug 17 15:19:39 localhost draknetcenter[18701]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Aug 17 15:19:43 localhost draknetcenter[18701]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Aug 17 15:19:43 localhost draknetcenter[18701]: running: /bin/rpm -q --qf %{name}
Aug 17 15:19:43 localhost draknetcenter[18701]: Found settings for driver "hso" in category "network::connection::cellular_card"
Aug 17 15:19:44 localhost draknetcenter[18701]: Required kernel_module package for module "hso" is already installed, skipping
Aug 17 15:19:44 localhost draknetcenter[18701]: Required tools package for module "hso" is already installed, skipping
Aug 17 15:19:44 localhost draknetcenter[18701]: No firmware package for module "hso" is required, skipping
Aug 17 15:19:44 localhost draknetcenter[18701]: Loading module hso
Aug 17 15:19:44 localhost draknetcenter[18701]: Settings for driver "hso" applied
Aug 17 15:19:44 localhost draknetcenter[18701]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Comment 14 Franz Holzinger 2012-08-17 15:29:18 CEST
Then I create the symbolic link manually and retry it with the netapplet.
[root@localhost log]#  ln -s  /dev/ttyHS1 /dev/ttyHS

syslog:

Aug 17 15:26:50 localhost net_applet[3347]: running: /usr/bin/draknetcenter
Aug 17 15:26:50 localhost draknetcenter[32082]: ### Program is starting ###
Aug 17 15:26:52 localhost draknetcenter[32082]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Aug 17 15:26:53 localhost draknetcenter[32082]: running: /bin/rpm -q --qf %{name}
Aug 17 15:26:54 localhost draknetcenter[32082]: Found settings for driver "hso" in category "network::connection::cellular_card"
Aug 17 15:26:54 localhost draknetcenter[32082]: Required kernel_module package for module "hso" is already installed, skipping
Aug 17 15:26:54 localhost draknetcenter[32082]: Required tools package for module "hso" is already installed, skipping
Aug 17 15:26:54 localhost draknetcenter[32082]: No firmware package for module "hso" is required, skipping
Aug 17 15:26:54 localhost draknetcenter[32082]: Loading module hso
Aug 17 15:26:54 localhost draknetcenter[32082]: Settings for driver "hso" applied
Aug 17 15:26:54 localhost draknetcenter[32082]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Aug 17 15:26:54 localhost draknetcenter[32082]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Aug 17 15:26:54 localhost draknetcenter[32082]: running: comgt -d /dev/ttyHS PIN
Aug 17 15:26:55 localhost draknetcenter[32082]: modified file /etc/ppp/pap-secrets
Aug 17 15:26:56 localhost draknetcenter[32082]: modified file /etc/ppp/chap-secrets
Aug 17 15:26:56 localhost draknetcenter[32082]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Aug 17 15:26:56 localhost draknetcenter[32082]: modified file /etc/sysconfig/network-scripts/ifcfg-hso0
Aug 17 15:26:56 localhost NetworkManager[1204]: <warn> failed to allocate link cache: (-10) Operation not supported
Aug 17 15:26:56 localhost draknetcenter[32082]: modified file /etc/sysconfig/network-scripts/ifcfg-hso0
Aug 17 15:26:56 localhost draknetcenter[32082]: changed mode of /etc/sysconfig/network-scripts/ifcfg-hso0 to 755
Aug 17 15:26:56 localhost draknetcenter[32082]: written hso0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-hso0
Aug 17 15:26:56 localhost draknetcenter[32082]: modified file /etc/modprobe.conf
Aug 17 15:26:56 localhost draknetcenter[32082]: running: dmidecode
Aug 17 15:26:56 localhost draknetcenter[32082]: to put in /etc/modprobe.preload nvram, sdhci_pci, evdev
Aug 17 15:26:56 localhost draknetcenter[32082]: modified file /etc/modprobe.preload
Aug 17 15:26:56 localhost draknetcenter[32082]: running: udevadm info --query=property --path=/sys/bus/usb/devices/4-1
Aug 17 15:26:56 localhost NetworkManager[1204]: <warn> failed to allocate link cache: (-10) Operation not supported
Aug 17 15:26:56 localhost NetworkManager[1204]:    ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-hso0.
Aug 17 15:26:56 localhost NetworkManager[1204]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-hso0 ...
Aug 17 15:26:56 localhost NetworkManager[1204]: <warn> failed to allocate link cache: (-10) Operation not supported
Aug 17 15:26:56 localhost NetworkManager[1204]:    ifcfg-rh:     read connection 'Système hso0'
Aug 17 15:26:56 localhost NetworkManager[1204]:    ifcfg-rh: Ignoring connection 'Système hso0' and its device due to NM_CONTROLLED/BRIDGE/VLAN.
Aug 17 15:26:56 localhost NetworkManager[1204]: <warn> failed to allocate link cache: (-10) Operation not supported
Comment 15 Marja Van Waes 2012-08-28 17:39:51 CEST
@ Blino

Is it possible uninstalling networkmanager helps here, too?

Keywords: NEEDINFO => (none)
CC: eugeni => (none)
Version: 1 => 2

Comment 16 Colin Guthrie 2012-08-29 22:36:56 CEST
@Marja Unlikely uninstalling networkmanager would help. as the log clearly states it's ignoring the connection (the link cache warnings seem odd tho' I'll admit).

Last time I used a 3G dongle, NetworkManager just worked flawlessly and got me connected in no time. YMMV.
Comment 17 Franz Holzinger 2012-09-14 22:22:39 CEST
Thanks.
Comment 18 Franz Holzinger 2012-09-14 22:24:50 CEST
I deinstalled the GNOME Networkmanager.
Then I typed.

[root@localhost ~]#  ln -s  /dev/ttyHS1 /dev/ttyHS

And then I have used the NetApplet to connect using the UMTS USB stick. And it works.

I leave this issue open until it works without having to do manual tasks.
Franz Holzinger 2012-09-15 11:04:13 CEST

Depends on: (none) => 6675

Comment 19 Manuel Hiebel 2013-10-22 12:18:42 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 2'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 2 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.

-- 
The Mageia Bugsquad
Comment 20 Manuel Hiebel 2013-11-23 16:15:26 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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: REOPENED => RESOLVED
Resolution: (none) => OLD

Comment 21 Dan Joita 2014-05-08 13:17:26 CEST
fresh install of mageia 4 dual dvd comes up with same problem

Identification
Vendor: âOption N.V.
Description: âGlobetrotter HSUPA Modem  
Media class: â
Connection
Bus: âUSB
Bus PCI #: â1
PCI device #: â16
Vendor ID: â0x0af0
Device ID: â0x7251
Misc
Module: âhso

made ln -s  /dev/ttyHS1 /dev/ttyHS

now when I try to connect the modem restarts and I have no internet

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

Dan Joita 2014-05-08 13:20:01 CEST

Version: 2 => 4

Thierry Vignaud 2015-02-06 14:05:23 CET

Summary: GPRS HDSPA modem fails => GPRS HDSPA modem fails (missing softlink from /dev/ttyHS1 to /dev/ttyHS)
Source RPM: udev => udev, drakx-net

Comment 22 Colin Guthrie 2015-02-06 14:59:31 CET
Commenting on the change of subject and the fact that a known device name is "required".

FWIW, the approach of requiring a known name is generally invalid in this hotplug world. Using something like NetworkManager is the correct solution here to ensure that proper device enumeration is done and reliance on known names is avoided.

NetApplet is sadly no longer up to the job and it doesn't look like anyone is going to give it much TLC going forward :(
Comment 23 Thierry Vignaud 2015-03-11 16:23:30 CET
Colin, I doubt there's that many machines with more than such modems...
But here the issue is that we didn't get the interface.
See http://gitweb.mageia.org/software/drakx-net/tree/lib/network/connection/cellular_card.pm#n97

Dan, can you try adding alter /usr/lib/libDrakX/network/connection/cellular_card.pm in order to get more data?
eg at line 70:
print "udevadm info --query=property --path=$self->{device}{sysfs_device}";
use Data::Dumper; warn Dumper \%udev_env;

Please make a backup of that file first!

Keywords: (none) => NEEDINFO

Comment 24 Samuel Verschelde 2015-09-21 13:20:49 CEST
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/
Comment 25 Marja Van Waes 2015-10-27 06:57:58 CET
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


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