Automatic Activation, Hotplug and UDEV, Configuration
Post Reply
Vanaprastha
Posts: 2
Joined: 30 Mar 2013, 11:13

Sewonintech's GCT M-WiMAX usb network adaptor

Post by Vanaprastha » 04 Apr 2013, 12:43

The Kernel

Code: Select all

3.5.0-17-generic
Using Linux Mint 14 Nadia(not upgraded).

Result of lsusb

Code: Select all

Bus 002 Device 009: ID 1076:7f00 GCT Semiconductor, Inc. 
Result of Dmesg

Code: Select all

[ 1212.257527] usb 2-1.4: >Product: M-WiMAX Network Adaptor
[ 1212.257528] usb 2-1.4: >Manufacturer: GCT Semiconductor, Inc.
[ 1212.257530] usb 2-1.4: >SerialNumber: 72050203
[ 1212.258707] scsi8 : usb-storage 2-1.4:34.0
[ 1213.881777] scsi 8:0:0:0: >CD-ROM            GCT Semi CD-ROM           312e PQ: 0 ANSI: 0 CCS
[ 1213.885162] sr1: scsi3-mmc drive: 0x/0x caddy
[ 1213.885288] sr 8:0:0:0: >Attached scsi CD-ROM sr1
[ 1213.885361] sr 8:0:0:0: >Attached scsi generic sg3 type 5
[ 1214.013876] usb 2-1.4: >USB disconnect, device number 8
[ 1214.979251] usb 2-1.4: >new high-speed USB device number 9 using ehci_hcd
[ 1215.072208] usb 2-1.4: >New USB device found, idVendor=1076, idProduct=7f00
[ 1215.072213] usb 2-1.4: >New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1215.072215] usb 2-1.4: >Product: M-WiMAX Network Adaptor
[ 1215.072218] usb 2-1.4: >Manufacturer: GCT Semiconductor, Inc.
[ 1215.072220] usb 2-1.4: >SerialNumber: 72050203
[ 1215.110509] gdmwm: module is from the staging directory, the quality is unknown, you have been warned.
[ 1215.110879] Found GDM USB VID = 0x1076 PID = 0x7f00...
[ 1215.110880] GCT WiMax driver version 3.2.3
[ 1215.111057] GDM WiMax Set CAPABILITY: 0x0000000F
[ 1215.111074] usbcore: registered new interface driver gdm_wimax
[ 1215.113512] MAC change [00:0a:3b:f0:01:30]->[00:21:07:11:2c:d1]
[ 1215.120167] IPv6: ADDRCONF(NETDEV_UP): wm0: link is not ready
[ 1215.122504] IPv6: ADDRCONF(NETDEV_UP): wm0: link is not ready
[ 1215.129447] IPv6: ADDRCONF(NETDEV_UP): wm0: link is not ready
[ 1215.129538] IPv6: ADDRCONF(NETDEV_UP): wm0: link is not ready
[ 1218.074375] usb_modeswitch_[4362]: segfault at 0 ip 00007fbac9acf101 sp 00007fff70ddf268 error 4 in libc-2.15.so[7fbac9a46000+1b5000]
Result of usb_modeswitch -v 1076 -p 7f00 -d -G -W

Code: Select all

GCT M-WiMax Network Adapter.
Bus 002 Device 007: ID 1076:7f00 GCT Semiconductor, Inc. 
3.5.0-17-generic

---------
DefaultVendor=  0x1076
DefaultProduct= 0x7f00
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set
TargetProductList=""

DetachStorageOnly=1
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=1
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint=  not set
MessageContent=""
NeedResponse=0
ResponseEndpoint= not set

InquireDevice enabled (default)
Success check disabled
System integration mode disabled


usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 007 on 002
usb_os_find_devices: Found 004 on 002
usb_os_find_devices: Found 003 on 002
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 003 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
Looking for default devices ...
  searching devices, found USB ID 1076:7f00
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 14cd:6116
  searching devices, found USB ID 0461:0010
  searching devices, found USB ID 8087:0024
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 046d:c05a
  searching devices, found USB ID 8087:0024
  searching devices, found USB ID 1d6b:0002
 Found device in default mode, class or configuration (1)
Accessing device 007 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (17)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x82 (in)
Not a storage device, skipping SCSI inquiry

USB description data (for identification)
-------------------------
Manufacturer: GCT Semiconductor, Inc.
     Product: M-WiMAX Network Adaptor
  Serial No.: 72050203
-------------------------
Only detaching storage driver for switching ...
Looking for active driver ...
 OK, driver found ("gdm_wimax")
 OK, driver "gdm_wimax" detached
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached
Sending GCT control message 1 ...
USB error: error sending control message: Broken pipe
Sending GCT control message 2 ...
USB error: error sending control message: Broken pipe
 OK, GCT control messages sent
-> Run lsusb to note any changes. Bye.
=======================================================

I have posted this problem in Linux Question, but they just referred me to this page. I did everything that what should have been done, and I still don't see any positive result.

Either I am doing this wrong, or I just don't know how to set it all up. And thank you.

LOM
Posts: 1404
Joined: 11 Jul 2012, 15:14
Location: Koh Samui, TH

Re: Sewonintech's GCT M-WiMAX usb network adaptor

Post by LOM » 04 Apr 2013, 15:47

Report the usb_modeswitch segfault error to Linux Mint maintainers, looks like it is caused by libc.
This error is however not the reason for the device not working, the device does switch from initial cd-rom mode into wimax modem mode.

The linux gdm72xx driver is a staging driver which means it is experimental, a work in progress, but not stable enough for production use.
There has been recent changes to it which are not in the 3.5.0-17 kernel, you may be lucky and get it working with a later kernel but it is still in staging in the latest kernel..

Sorry, but I can't see this being a matter for this forum now since usb_modeswitch does what it should do - the problem is elsewhere and most likely a gdm72xx driver problem.

Edit:
Paste the output from lsusb -vd 1076:7f00 before running usb_modeswitch manually, I get a feeling that your manual modeswitch is not needed since the stick is already switched.

Vanaprastha
Posts: 2
Joined: 30 Mar 2013, 11:13

Re: Sewonintech's GCT M-WiMAX usb network adaptor

Post by Vanaprastha » 06 Apr 2013, 08:35

LOM wrote:Report the usb_modeswitch segfault error to Linux Mint maintainers, looks like it is caused by libc.
This error is however not the reason for the device not working, the device does switch from initial cd-rom mode into wimax modem mode.

The linux gdm72xx driver is a staging driver which means it is experimental, a work in progress, but not stable enough for production use.
There has been recent changes to it which are not in the 3.5.0-17 kernel, you may be lucky and get it working with a later kernel but it is still in staging in the latest kernel..

Sorry, but I can't see this being a matter for this forum now since usb_modeswitch does what it should do - the problem is elsewhere and most likely a gdm72xx driver problem.

Edit:
Paste the output from lsusb -vd 1076:7f00 before running usb_modeswitch manually, I get a feeling that your manual modeswitch is not needed since the stick is already switched.
I have been trying this on different distributions. Lubuntu, CrunchBang(I think they use the same kernel versions but not sure about the drivers). Couldn't get it work on either.

Yeah, I guess it doesn't need the switch. It lights on and gets discovered by the system. Only thing is, I don't know how to set it up to work as it should.

Well, here is the result of lsusb -vd 1076:7f00

Code: Select all

Bus 002 Device 005: ID 1076:7f00 GCT Semiconductor, Inc. 
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1076 GCT Semiconductor, Inc.
  idProduct          0x7f00 
  bcdDevice            0.02
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue    17
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              5 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0

Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Re: Sewonintech's GCT M-WiMAX usb network adaptor

Post by Josh » 06 Apr 2013, 12:34

This line in your first "dmesg" output is showing that the device is mode-switched automatically:

Code: Select all

[ 1214.013876] usb 2-1.4: >USB disconnect, device number 8
There is really no need to try switching it again. Usually, you can't change the mode a second time.
If you are in 'target' mode, all further processing is a matter of udev and the driver.

Post Reply