Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 14
Hi all, I have recently bought a Fixed Wireless Terminal for Internet/phone usage. I was using it on WinXP but I would like to get it to work with Linux, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2005
    Location
    Uganda
    Posts
    4

    Huawei ETS2077 Fixed Wireless Terminal


    Hi all,

    I have recently bought a Fixed Wireless Terminal for Internet/phone usage. I was using it on WinXP but I would like to get it to work with Linux, since I've set up a mail-server and want it to be able to forward emails from local network to Internet.


    Computer: Acer (AcerPower F2), P4, Suse 9.2 pro, Kernel 2.6.8-24.16-default

    Internet Connection Device: Huawei ETS2077 Fixed Wireless Terminal (connects via Serial Port)


    I would like to know if its possible to get this device to work under linux and how-to go about it.

    thnx!

  2. #2
    Linux Guru loft306's Avatar
    Join Date
    Oct 2003
    Location
    The DairyLand
    Posts
    1,666
    yeah it should work,linux supports Voip and external serial devices need no drivers though you will need a pkg to use it but the pkge's name is slipping my mind.....
    ~Mike ~~~ Forum Rules
    Testing? What's that? If it compiles, it is good, if it boots up, it is perfect. ~ Linus Torvalds
    http://loft306.org

  3. #3
    Just Joined!
    Join Date
    Jun 2005
    Location
    Uganda
    Posts
    4
    Hi

    The wireless terminal is basically a Telephone that also acts as my
    wireless adapter/ modem

    Pls see link 4 details:
    http://mobile.huawei.com/product_e/c...ed_ets2000.htm

    It connects via USB to the computer. When I plugged it in Suse didnt
    detect it, and also after reboot it didnt.


    This Wireless Terminal is provided by our local telcom, especially for
    remote upcountry areas that have no access to Internet via telephone
    lines.

    In Windows XP you just connect the Wireless Terminal, install the
    drivers and use the Create new connection Wizard to configure the
    terminal to dial a certain Phone #.

  4. #4
    Just Joined!
    Join Date
    Jul 2005
    Posts
    1

    Re: Huawei ETS2077 Fixed Wireless Terminal

    You need to upgrade your kernel. The problem is the serial->usb cable, not the modem. The cable is only supported on recent versions of the kernel.

    I got this running on SuSE 9.1 Pro so it should work for you too.

    Instructions
    -------------
    1. Update the hwinfo, udev and mkinitrd packages. You can find them here:
    http://ftp.gwdg.de/pub/linux/suse/people/agruen/i386/
    2. Download the 9.3 kernel from http://ftp.gwdg.de/pub/suse/i386/9.3...4-20a.i586.rpm
    3. Create an executable script file called /etc/hotplug/usb/ti_usb_3410_5420 and paste the following:
    Code:
    #!/bin/bash
    
    BOOT_CONFIG=1
    ACTIVE_CONFIG=2
    
    if [ "$ACTION" != "add" ]
    then
    exit
    fi
    
    CONFIG_PATH=/sys${DEVPATH%/?*}/bConfigurationValue
    
    if [ 0`cat $CONFIG_PATH` -ne $BOOT_CONFIG ]
    then
    exit
    fi
    
    PRODUCT=${PRODUCT%/?*}# delete version
    VENDOR_ID=`printf "%d" 0x${PRODUCT%/?*}`
    PRODUCT_ID=`printf "%d" 0x${PRODUCT#*?/}`
    
    PARAM_PATH=/sys/module/ti_usb_3410_5052/parameters
    
    function scan() {
    s=$1
    shift
    for i
    do
    if [[ $s -eq $i ]]
    then
    return 0
    fi
    done
    return 1
    }
    
    IFS=$IFS,
    
    if (scan $VENDOR_ID 1105 `cat $PARAM_PATH/vendor_3410` &&
    scan $PRODUCT_ID 13328 `cat $PARAM_PATH/product_3410`) ||
    (scan $VENDOR_ID 1105 `cat $PARAM_PATH/vendor_5052` &&
    scan $PRODUCT_ID 20562 20818 20570 20575 `cat $PARAM_PATH/product_5052`)
    then
    echo $ACTIVE_CONFIG > $CONFIG_PATH
    fi
    3. FINALLY. Create a soft link
    Code:
    ln -s /dev/ttyUSB0 /dev/modem
    You're done! Run YaST and configure your modem.

    Any trouble, email me on pndiku AT gmail DOT com.

    God bless.

  5. #5
    Just Joined!
    Join Date
    Jun 2005
    Location
    Uganda
    Posts
    4
    Thanx for your detailed answer. I am defently goin2 try on testsystem and get back to you when I got results.

  6. #6
    Just Joined!
    Join Date
    Dec 2005
    Location
    Faislabad, Pakistan
    Posts
    2

    Huawei FWT ETS2077 Driver

    I have Huawei FWT ETS2077 and i would use it for voice and data, i want to use it through linux. i have USB to DB9 cable but the problem is i have not software driver. any one know the driver plz help me

  7. #7
    Just Joined!
    Join Date
    Dec 2005
    Location
    Faislabad, Pakistan
    Posts
    2

    Re: Huawei ETS2077 Fixed Wireless Terminal

    Quote Originally Posted by sucram2g
    Hi all,

    I have Huawei FWT ETS2077 and i would use it for voice and data, i want to use it through linux. i have USB to DB9 cable but the problem is i have not software driver. any one know the driver plz help me

    Computer: Acer (AcerPower F2), P4, Suse 9.2 pro, Kernel 2.6.8-24.16-default

    Internet Connection Device: Huawei ETS2077 Fixed Wireless Terminal (connects via Serial Port)


    I would like to know if its possible to get this device to work under linux and how-to go about it.

    thnx!

  8. #8
    Just Joined!
    Join Date
    Jun 2005
    Location
    Uganda
    Posts
    4
    read the complete post and follow the stepts mentioned above by 'pndiku', it works great!

  9. #9
    Just Joined!
    Join Date
    Sep 2006
    Location
    Hyderabad, Pakistan
    Posts
    5

    Huawei ETS 2551 not detected

    I have been wandering around the Linux groups & IRC rooms (where no one likes to help anyone) but could not find the solution to my problem. I have a Huawei ETS 2551 Fixed Wireless Terminal & I cant get it to work on Kubuntu 6.06 LTS & Fedora Core 3. I have seen that these operating systems only detect the wire (TUSB 3410 boot device) that links the terminal to my PC but the terminal itself is not installed anywhere on the system. Since I wandered around a lot I have seen people requiring output of some commands related to hardware. So, I will be pasting the output of 3 such commands. Based on these outputs, I want to know the solution of my problem:

    Output of tail -f /var/log/messages:
    Sep 11 03:43:20 saad-desktop kernel: [4296610.588000] usb 1-2: new full speed USB device using ohci_hcd and address 7
    Sep 11 03:43:20 saad-desktop kernel: [4296610.755000] ti_usb_3410_5052 1-2:1.0: TI USB 3410 1 port adapter converter detected
    Sep 11 03:43:21 saad-desktop kernel: [4296611.734000] usb 1-2: reset full speed USB device using ohci_hcd and address 7
    Sep 11 03:43:21 saad-desktop kernel: [4296611.869000] usb 1-2: device firmware changed
    Sep 11 03:43:21 saad-desktop kernel: [4296611.869000] ti_usb_3410_5052: probe of 1-2:1.0 failed with error -5
    Sep 11 03:43:21 saad-desktop kernel: [4296611.869000] usb 1-2: USB disconnect, address 7
    Sep 11 03:43:21 saad-desktop kernel: [4296611.984000] usb 1-2: new full speed USB device using ohci_hcd and address 8
    Sep 11 03:43:22 saad-desktop kernel: [4296612.180000] usb 1-2: configuration #1 chosen from 2 choices
    Sep 11 03:43:22 saad-desktop kernel: [4296612.184000] ti_usb_3410_5052 1-2:1.0: TI USB 3410 1 port adapter converter detected
    Sep 11 03:43:22 saad-desktop kernel: [4296612.184000] ti_usb_3410_5052: probe of 1-2:1.0 failed with error -5

    Output of cat /proc/bus/usb/devices:
    T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 8 Spd=12 MxCh= 0
    D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 2
    P: Vendor=0451 ProdID=3410 Rev= 1.00
    S: Manufacturer=Texas Instruments
    S: Product=TUSB3410 Boot Device
    S: SerialNumber=TUSB3410
    C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
    I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
    E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    C: #Ifs= 1 Cfg#= 2 Atr=a0 MxPwr=100mA
    I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=
    E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=1ms

    Output of lsusb:
    Bus 004 Device 001: ID 0000:0000
    Bus 001 Device 010: ID 0451:3410 Texas Instruments, Inc. TUSB3410 Microcontroller
    Bus 001 Device 004: ID 09da:002a A4 Tech Co., Ltd Wireless Optical Mouse NB-30
    Bus 001 Device 001: ID 0000:0000
    Bus 003 Device 001: ID 0000:0000
    Bus 002 Device 001: ID 0000:0000

    These outputs were taken while working on Kubuntu 6.06 LTS and as far as I remember the outputs of FC3 were also the same. Waiting for reply.

    Cyborg_sa AKA Saad

  10. #10
    Just Joined!
    Join Date
    Nov 2006
    Posts
    1
    I have a same problem with my data-cabel in RH EL 4 AS.
    # lsusb
    Bus 004 Device 001: ID 0000:0000
    Bus 003 Device 001: ID 0000:0000
    Bus 002 Device 002: ID 0451:3410 Texas Instruments, Inc. (<---- that data-cabel)
    Bus 002 Device 001: ID 0000:0000
    Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. (<----- my flash Mass Storage)
    Bus 001 Device 001: ID 0000:0000

    Frafment regarding Bus 002 Device 002 :
    #lsusb -v
    Bus 002 Device 002: ID 0451:3410 Texas Instruments, Inc.
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 1.10
    bDeviceClass 255 Vendor Specific Class
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor 0x0451 Texas Instruments, Inc.
    idProduct 0x3410
    bcdDevice 1.14
    iManufacturer 1 Texas Instruments
    iProduct 2 TUSB3410 Serial Port
    iSerial 3 0DFF4FE065831B26
    bNumConfigurations 2
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
    MaxPower 100mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 0
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x01 EP 1 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type none
    Usage Type Data
    wMaxPacketSize 0x0040 bytes 64 once
    bInterval 0
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 39
    bNumInterfaces 1
    bConfigurationValue 2
    iConfiguration 0
    bmAttributes 0xa0
    Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 3
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 0
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type none
    Usage Type Data
    wMaxPacketSize 0x0040 bytes 64 once
    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 0x0040 bytes 64 once
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type none
    Usage Type Data
    wMaxPacketSize 0x0002 bytes 2 once
    bInterval 1
    Language IDs: (length=4)
    0409 English(US)
    Frafment dmesg regarding usb-ports:
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    PCI: Setting latency timer of device 0000:00:1d.7 to 64
    ehci_hcd 0000:00:1d.7: irq 10, pci mem d08dc000
    SELinux: initialized (dev usbdevfs, type usbdevfs), uses genfs_contexts
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    PCI: cache line size of 128 is not supported by device 0000:00:1d.7
    ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 6 ports detected
    USB Universal Host Controller Interface driver v2.2
    ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 9 (level, low) -> IRQ 9
    uhci_hcd 0000:00:1d.0: UHCI Host Controller
    PCI: Setting latency timer of device 0000:00:1d.0 to 64
    uhci_hcd 0000:00:1d.0: irq 9, io base 0000d800
    uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 11 (level, low) -> IRQ 11
    uhci_hcd 0000:00:1d.1: UHCI Host Controller
    PCI: Setting latency timer of device 0000:00:1d.1 to 64
    uhci_hcd 0000:00:1d.1: irq 11, io base 0000d000
    uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    ACPI: PCI interrupt 0000:00:1d.2[C] -> GSI 9 (level, low) -> IRQ 9
    uhci_hcd 0000:00:1d.2: UHCI Host Controller
    PCI: Setting latency timer of device 0000:00:1d.2 to 64
    uhci_hcd 0000:00:1d.2: irq 9, io base 0000d400
    uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    usb 1-2: new high speed USB device using address 3
    usb 2-1: new full speed USB device using address 2
    SCSI subsystem initialized
    Initializing USB Mass Storage driver...
    scsi0 : SCSI emulation for USB Mass Storage devices
    Vendor: JetFlash Model: TS1GJF2A/120 Rev: 8.07
    Type: Direct-Access ANSI SCSI revision: 02
    USB Mass Storage device found at 3
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usb 2-1: configuration #1 chosen from 2 choices
    SCSI device sda: 2007040 512-byte hdwr sectors (1028 MB)
    sda: Write Protect is off
    sda: Mode Sense: 03 00 00 00
    sda: assuming drive cache: write through
    sda: sda1
    Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
    SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
    NET: Registered protocol family 10
    Disabled Privacy Extensions on device c0366c20(lo)
    IPv6 over IPv4 tunneling driver
    divert: not allocating divert_blk for non-ethernet device sit0
    What do you think ?

    MotherBoard - i845PE

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •