RE: ip-config -> failed for GlobeTrotter HSDPA Modem
- From: Dan Williams <dcbw redhat com>
- To: richter ecos de
- Cc: "networkmanager-list gnome org" <networkmanager-list gnome org>
- Subject: RE: ip-config -> failed for GlobeTrotter HSDPA Modem
- Date: Tue, 13 Sep 2011 12:08:05 -0500
On Tue, 2011-09-13 at 18:07 +0200, richter ecos de wrote:
> Hi,
>
> here ist he output for hso0.
Which version of udev do you have, and do you have the 'usb_id' program
in /lib/udev anywhere, and the
corresponding /lib/udev/rules.d/75-net-description.rules file that
includes a rule like so?
SUBSYSTEMS=="usb", ENV{ID_MODEL}=="", IMPORT{program}="usb_id --export %p"
That appears to be what provides the ID_MODEL / ID_VENDOR stuff that
ModemManager will be looking for.
Dan
> Regards
>
> Gerald
>
> ------------------------------------------------------
> Name: hso0
> Type: wwan
> Subsys: net
> Number: 0
> Path: /sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/net/hso0
> Driver: (null)
> Action: (null)
> Seq Num: 0
> Dev File: (null)
>
> Properties:
> UDEV_LOG: 3
> DEVPATH: /devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/net/hso0
> DEVTYPE: wwan
> INTERFACE: hso0
> IFINDEX: 36
> SUBSYSTEM: net
>
> ------------------------------------------------------
> Name: 2-1:1.0
> Type: usb_interface
> Subsys: usb
> Number: 0
> Path: /sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0
> Driver: hso
> Action: (null)
> Seq Num: 0
> Dev File: (null)
>
> Properties:
> UDEV_LOG: 3
> DEVPATH: /devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0
> DEVTYPE: usb_interface
> DRIVER: hso
> DEVICE: /proc/bus/usb/002/027
> PRODUCT: af0/6971/0
> TYPE: 255/255/255
> INTERFACE: 255/255/255
> MODALIAS: usb:v0AF0p6971d0000dcFFdscFFdpFFicFFiscFFipFF
> SUBSYSTEM: usb
>
> ------------------------------------------------------
> Name: 2-1
> Type: usb_device
> Subsys: usb
> Number: 1
> Path: /sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1
> Driver: usb
> Action: (null)
> Seq Num: 0
> Dev File: /dev/bus/usb/002/027
>
> Properties:
> UDEV_LOG: 3
> DEVPATH: /devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1
> MAJOR: 189
> MINOR: 154
> DEVNAME: /dev/bus/usb/002/027
> DEVTYPE: usb_device
> DRIVER: usb
> DEVICE: /proc/bus/usb/002/027
> PRODUCT: af0/6971/0
> TYPE: 255/255/255
> BUSNUM: 002
> DEVNUM: 027
> SUBSYSTEM: usb
> ID_VENDOR: Option_N.V.
> ID_VENDOR_ENC: Option\x20N.V.
> ID_VENDOR_ID: 0af0
> ID_MODEL: Globetrotter_HSDPA_Modem
> ID_MODEL_ENC: Globetrotter\x20HSDPA\x20Modem\x20\x20
> ID_MODEL_ID: 6971
> ID_REVISION: 0000
> ID_SERIAL: Option_N.V._Globetrotter_HSDPA_Modem_Serial_Number
> ID_SERIAL_SHORT: Serial_Number
> ID_BUS: usb
> ID_USB_INTERFACES: :ffffff:
>
> ------------------------------------------------------
> Name: usb2
> Type: usb_device
> Subsys: usb
> Number: 2
> Path: /sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2
> Driver: usb
> Action: (null)
> Seq Num: 0
> Dev File: /dev/bus/usb/002/001
>
> Properties:
> UDEV_LOG: 3
> DEVPATH: /devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2
> MAJOR: 189
> MINOR: 128
> DEVNAME: /dev/bus/usb/002/001
> DEVTYPE: usb_device
> DRIVER: usb
> DEVICE: /proc/bus/usb/002/001
> PRODUCT: 1d6b/1/300
> TYPE: 9/0/0
> BUSNUM: 002
> DEVNUM: 001
> SUBSYSTEM: usb
> ID_VENDOR: Linux_3.0.3-BB5000-mthc-R249_uhci_hcd
> ID_VENDOR_ENC: Linux\x203.0.3-BB5000-mthc-R249\x20uhci_hcd
> ID_VENDOR_ID: 1d6b
> ID_MODEL: UHCI_Host_Controller
> ID_MODEL_ENC: UHCI\x20Host\x20Controller
> ID_MODEL_ID: 0001
> ID_REVISION: 0300
> ID_SERIAL: Linux_3.0.3-BB5000-mthc-R249_uhci_hcd_UHCI_Host_Controller_0000:02:00.0
> ID_SERIAL_SHORT: 0000:02:00.0
> ID_BUS: usb
> ID_USB_INTERFACES: :090000:
>
> ------------------------------------------------------
> Name: 0000:02:00.0
> Type: (null)
> Subsys: pci
> Number: 0
> Path: /sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0
> Driver: uhci_hcd
> Action: (null)
> Seq Num: 0
> Dev File: (null)
>
> Properties:
> UDEV_LOG: 3
> DEVPATH: /devices/pci0000:00/0000:00:11.0/0000:02:00.0
> DRIVER: uhci_hcd
> PCI_CLASS: C0300
> PCI_ID: 8086:7112
> PCI_SUBSYS_ID: 15AD:1976
> PCI_SLOT_NAME: 0000:02:00.0
> MODALIAS: pci:v00008086d00007112sv000015ADsd00001976bc0Csc03i00
> SUBSYSTEM: pci
>
> ------------------------------------------------------
> Name: 0000:00:11.0
> Type: (null)
> Subsys: pci
> Number: 0
> Path: /sys/devices/pci0000:00/0000:00:11.0
> Driver: (null)
> Action: (null)
> Seq Num: 0
> Dev File: (null)
>
> Properties:
> UDEV_LOG: 3
> DEVPATH: /devices/pci0000:00/0000:00:11.0
> PCI_CLASS: 60401
> PCI_ID: 15AD:0790
> PCI_SUBSYS_ID: 15AD:0790
> PCI_SLOT_NAME: 0000:00:11.0
> MODALIAS: pci:v000015ADd00000790sv000015ADsd00000790bc06sc04i01
> SUBSYSTEM: pci
>
> ------------------------------------------------------
> Name: pci0000:00
> Type: (null)
> Subsys: (null)
> Number: 00
> Path: /sys/devices/pci0000:00
> Driver: (null)
> Action: (null)
> Seq Num: 0
> Dev File: (null)
>
> Properties:
> UDEV_LOG: 3
> DEVPATH: /devices/pci0000:00
>
>
>
> > -----Original Message-----
> > From: Dan Williams [mailto:dcbw redhat com]
> > Sent: Monday, September 12, 2011 11:29 PM
> > To: Gerald Richter - ECOS
> > Cc: networkmanager-list gnome org
> > Subject: RE: ip-config -> failed for GlobeTrotter HSDPA Modem
> >
> > On Fri, 2011-09-09 at 06:46 +0200, richter ecos de wrote:
> > > Hi Dan,
> > >
> > > my teststick was "Out Of Office", but now I have it back again and here is
> > what I found..
> > >
> > > > For your device we're not seeing the OWANDATA call there. That
> > > > appears to be because MM is not recognizing your modem's network
> > > > device which should be called 'hso0'. Can you provide logs of
> > > > starting up ModemManager with the device plugged in so we can debug
> > > > what's not happening about the detection process? Also, when you
> > > > plug the modem in, do you see 'hso0' (or
> > > > hso1 or whatever) in the output of 'ifconfig -a' ?
> > > >
> > >
> > > Attached are two log files. Umts3.log shows starting up modem manager
> > with device already pluged in, umts_plugin.log shows pluging in the device,
> > while modem manager is already running.
> >
> > So here's the issue:
> >
> > Sep 9 06:22:38 ThinClient modem-manager[3980]: <warn> [mm-
> > manager.c:574] do_grab_port(): plugin 'Option High-Speed' claimed to
> > support net/hso0 but couldn't: (0) Could not get modem product ID.
> >
> > That indicates something odd with the sysfs/udev hierarchy, which is how
> > you figure out what USB vendor and product the device has. This could
> > indicate a buggy kernel driver, though the upstream kernel 'hso' driver hasn't
> > changed in a while. It could also indicate something wrong with udev or
> > sysfs. So heres what we do:
> >
> > 1) grab
> > http://cgit.freedesktop.org/ModemManager/ModemManager/plain/test/ls
> > udev.c
> > 2) grab udev development headers (libudev-dev or libudev-devel or
> > libudev1-dev or whatever your distro calls them)
> > 3) grab gudev development headers (libgudev-dev or libgudev1-devel or
> > whatever)
> > 4) build lsudev.c like so:
> >
> > gcc -o lsudev `pkg-config --cflags --libs gudev-1.0` lsudev.c
> >
> > 5) with the modem plugged in and already switched to modem mode, run
> > lsudev like so:
> >
> > sudo lsudev net
> >
> > And report the output. That will print out the sysfs/udev device hierarchy for
> > this device and let us figure out what's wrong.
> >
> > Dan
> >
> > > Ifconfig -a shows the hso0 device (see ifconfig.log) and the kernel loads the
> > hso driver (start of umts3.log). Also /sys/class/net has an entry for hso0.
> > >
> > > Are there any hso udev rules necessary? I saw in the internet that there is a
> > hso udev rule file which sets several devices with fixed names. It seems that
> > this is not necessary for ModemManager, but maybe I am wrong?
> > >
> > > Thanks & Regards
> > >
> > > Gerald
> > >
> > >
> >
>
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
