has anyone got usb_modeswitch to work with this?
usb_modeswitch -W -c /etc/usb_modeswitch.d/2077:f000
Reading config file: /etc/usb_modeswitch.d/2077:f000 * usb_modeswitch: handle USB devices with multiple modes * Version 1.1.4 (C) Josua Dietze 2010 * Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= not set DefaultProduct= not set TargetVendor= 0x2077 TargetProduct= 0x9000 TargetClass= not set TargetProductList=""
DetachStorageOnly=0 HuaweiMode=0 SierraMode=0 SonyMode=0 GCTMode=0 MessageEndpoint= not set MessageContent="5553424308902082000000000000061b000000020000000000000000000000" NeedResponse=0 ResponseEndpoint= not set Interface=0x00
InquireDevice enabled (default) Success check disabled System integration mode disabled
usb_set_debug: Setting debugging level to 15 (on) usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 001 on 002 usb_os_find_devices: Found 008 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device No default vendor/product ID given. Aborting.
root@in1:~# lsusb Bus 001 Device 008: ID 2077:f000
On 4 Oct 2013 03:36, "J T Dsouza" jtd1959@gmail.com wrote:
has anyone got usb_modeswitch to work with this?
usb_modeswitch -W -c /etc/usb_modeswitch.d/2077:f000
Inappropriate ioctl for device
No default vendor/product ID given. Aborting.
root@in1:~# lsusb Bus 001 Device 008: ID 2077:f000 --
Is the device config present in usb_modeswitch-data?
On Fri, Oct 4, 2013 at 2:21 PM, Nishit Dave stargazer.dave@gmail.comwrote:
On 4 Oct 2013 03:36, "J T Dsouza" jtd1959@gmail.com wrote:
has anyone got usb_modeswitch to work with this?
usb_modeswitch -W -c /etc/usb_modeswitch.d/2077:f000
Inappropriate ioctl for device
No default vendor/product ID given. Aborting.
root@in1:~# lsusb Bus 001 Device 008: ID 2077:f000 --
Is the device config present in usb_modeswitch-data?
yes. extracted from wheezy usb-modeswitch-data_20120815-2_all.deb
//# Telenet 3G dongle (T&W WU160)
TargetVendor= 0x2077 TargetProduct= 0x9000
MessageContent="5553424308902082000000000000061b000000020000000000000000000000" //
The onboard "cdrom" has some a ubuntu driver which is a wcdma thingy. Need to check what those ppp and wvdial scripts are doing.
Earlier dongles had 2 devices the "cdrom" and the modem This one mas a cdrom, a microsd slot and a modem. So when you "eject" the cdrom you get another /dev/sdx device.
Can anyone provide models nums of any gsm dongle working on linux.
--
On 4 Oct 2013 19:50, "J T Dsouza" jtd1959@gmail.com wrote:
usb_modeswitch -W -c /etc/usb_modeswitch.d/2077:f000
root@in1:~# lsusb Bus 001 Device 008: ID 2077:f000 --
yes. extracted from wheezy usb-modeswitch-data_20120815-2_all.deb
//# Telenet 3G dongle (T&W WU160)
TargetVendor= 0x2077 TargetProduct= 0x9000
First, try the full command line providing -v, -p, -V and -P options with the ID pairs above.
The onboard "cdrom" has some a ubuntu driver which is a wcdma thingy. Need to check what those ppp and wvdial scripts are doing.
Don't use it...it will just create a bigger mess with different versions.
Earlier dongles had 2 devices the "cdrom" and the modem This one mas a cdrom, a microsd slot and a modem.
This is standard.
So when you "eject" the
cdrom you get another /dev/sdx device.
Can anyone provide models nums of any gsm dongle working on linux.
The ones for my CDMA modem are 12d1:1446 and 12d1:140b.
It would be a good idea to get the latest usb_modeswitch packages and compile them yourself, even though Debian might not be messing around with the default package them like done by Ubuntu.
On Fri, Oct 4, 2013 at 8:18 PM, Nishit Dave stargazer.dave@gmail.comwrote:
On 4 Oct 2013 19:50, "J T Dsouza" jtd1959@gmail.com wrote:
usb_modeswitch -W -c /etc/usb_modeswitch.d/2077:f000
root@in1:~# lsusb Bus 001 Device 008: ID 2077:f000 --
yes. extracted from wheezy usb-modeswitch-data_20120815-2_all.deb
//# Telenet 3G dongle (T&W WU160)
TargetVendor= 0x2077 TargetProduct= 0x9000
First, try the full command line providing -v, -p, -V and -P options with the ID pairs above.
tried that first.
The onboard "cdrom" has some a ubuntu driver which is a wcdma thingy.
Need
to check what those ppp and wvdial scripts are doing.
Don't use it...it will just create a bigger mess with different versions.
Which is why i did not spend much time on that. In any case I would be just looking at what they are trying rather than install that
Earlier dongles had 2 devices the "cdrom" and the modem This one mas a cdrom, a microsd slot and a modem.
This is standard.
So when you "eject" the
cdrom you get another /dev/sdx device.
Can anyone provide models nums of any gsm dongle working on linux.
The ones for my CDMA modem are 12d1:1446 and 12d1:140b.
Already have that huawei thing working quite some time back. But I now need GSM. I usually use a serial gsm modem, which avoids all of the above rubbish.
It would be a good idea to get the latest usb_modeswitch packages and
compile them yourself, even though Debian might not be messing around with the default package them like done by Ubuntu.
Yes i think i will do that.
got a dlink dwm-156. vendor 2001 product 7d01. They have i386 and amd64 debs. The deb has udev rules, usb_modeswitch renamed to 3g_modem_switch, a script to modprobe usbserial with the vid pid and ppp scripts stuffed into /etc/3g_modem_connection and /etc/ppp.
The udev rules file has some lines to autoconnect, using modem-manager, so comment those lines if you dont want to auto connect and rake up bills.
Essentially one does not require usb_modeswitch. merely ejecting /dev/sr ? and modprobing usbserial with the vendor product that shows up AFTER ejecting /dev/sr ? does the job. With the help of the udev scripts the whole thing is automatic.
-
J T Dsouza -
Nishit Dave