ZTE k3805-z USB pen works with wvdial, as long as one uses wvdialconf before the first run and uses *99***1# as the phone number (you may have also to add "Stupid mode = 1" to wvdial.conf).
ZTE k3805-z USB pen works with wvdial, as long as one uses wvdialconf before the first run and uses *99***1# as the phone number (you may have also to add "Stupid mode = 1" to wvdial.conf).
hi pedrogfrancisco
The k3805-z has a icera chipset , and may need special init codes and udev rules to enable the device to use the cdc_ether connection, if using wvdial can check which interface is been used with "ifconfig" command
if only showing as standard ppp connection , then possible to point you in a direction, as to which sofware may work with this device, to enable use of cdc_ether connect
if have read first post as regards New Devices , using the "usb-devices" or "lsusb -t" or "lsusb -v" may show if it has a cdc_ether interface
regards
alexfish
Last edited by alexfish; February 26th, 2011 at 12:03 PM.
It works on Ubuntu 11.04
To anyone else reading this:
The two times I tried it didn't work the first time, connect a second and third time before giving up. Also, doing ifconfig usb0 -arp may or may not help, didn't experiment enough times.
Natty users: Betavine: BCM connection manager ( Vodafone devices)
BCM failing to initialize ;
test BCM from the terminal,
if you get the following error messageCode:bcm
you will need to create a symlink for python 2.6 to 2.7 (wader)Traceback (most recent call last):
File "/usr/bin/bcm", line 10, in <module>
from wader.common.utils import save_file, get_file_data
ImportError: No module named wader.common.utils
of note the dbus spec is not sameCode:sudo ln -s /usr/local/lib/python2.6/dist-packages/wader /usr/local/lib/python2.7/dist-packages/wader
this is the diff between the existing BCM and the modem-manager
to view the bits check before install and after ;; save a coppy , of each it may save you a headache , if know how to use itCode:--- /etc/dbus-1/system.d/org.freedesktop.ModemManager.conf 2011-06-07 16:09:55.799695594 +0100 +++ /etc/dbus-1/system.d/org.freedesktop.ModemManager.conf.dpkg-new 2011-04-11 00:09:10.000000000 +0100 @@ -5,12 +5,10 @@ <!-- This config allows anyone to control ModemManager --> <policy context="default"> - <allow own="org.freedesktop.ModemManager.Modem.Gsm.SMS"/> <allow send_destination="org.freedesktop.ModemManager"/> </policy> <policy user="root"> - <allow own="org.freedesktop.ModemManager.Modem.Gsm.SMS"/> <allow own="org.freedesktop.ModemManager"/> </policy>
RE: Wader-core , now available as for (Precise Pangolin), if have Next Generation Huawei device , possibly look to Huawie Mobile Partner first . RE foot of post #60Code:cat /etc/dbus-1/system.d/org.freedesktop.ModemManager.conf
alexfish
Last edited by alexfish; February 21st, 2012 at 09:11 PM. Reason: cat /etc/dbus-1/system.d/org.freedesktop.ModemManager.conf
Part of Betavine Site has show to be using invalild security certificate (14 Aug 2011) so have copied the data
Copy of Betavine Know Working devices
Huawei devices that work with bcm
- Huawei B970
- Huawei E1550
- Note: the E1550 Sometimes requires prodding with Sakis3g to get it recognized (modeswitch, setup TTY, register network).
- Huawei E160B
- Huawei E172
- Huawei E220
- Huawei E270
- Huawei E272
- Huawei E3735
- Huawei E510
- Huawei E620
- Huawei E630
- Huawei E660a
- Huawei E870
- Huawei EM730V
- Huawei EM770
- Huawei K2540
- Huawei K3520
- Huawei K3565
- Huawei K3565rev2
- Huawei K3715
- Huawei K3765
- Huawei K4505
Huawei Devices that do not work with bcm as of 2011-02-28
- Huawei E153
ZTE
- ZTE K2525
- ZTE K3520-Z
- ZTE K3565-Z
- ZTE K3570-Z
- ZTE K3571-Z
- ZTE K3765-Z
- ZTE K3805-Z
- ZTE K4505-Z
- ZTE MF651
Option
- Option Colt
- Option E3730
- Option Fuji-Lite(PPPD)
- Option Etna(PPPD)
- Option Etna(NDIS)
- Option Globe Surfer Icon
- Option GT Fusion
- Option GT Fusion Quad-lite
- Option GTM378
- Option GTMAX36
- Option Icon
- Option K3760
- Option Nozomi(Needs update to gudev parsing)
Sierra Wireless
- Sierrawireless 875
- Sierrawireless MC8755
Sony Ericsson
- Sony Ericsson K610i
- Sony Ericsson K618i
Ericsson
- Ericsson MD300
- Ericsson F3307
- Ericsson F3507g
- Ericsson F3607gw
Dell
- Dell D5520
- Dell D5530
- Dell D5540
Novatel
- Novatel U630(Needs update to gudev parsing)
- Novatel U740
- Novatel XU870
- Novatel X950
- Novatel MC950D
- Novatel MC990D
- Novatel MiFi2352
Nokia
- Nokia 6230
Thankfully all the major network in Philippines work right out of the box, in case of Smart, all one needs is to enter smartbro in APN, in case of SUN its fbband and viola, net works real good, only hitch in Philippines is upgrading the subscription as it needs a Windows based applet. For Postpaid, its not an issue.
Hi,
I went through the above processes and all was fine up to the command:
echo -e "AT+CPIN?\r" > /dev/ttyUSB2
This command gave me the error:
+CME ERROR: 10
When I run the command:
sudo sakis3g
I get the error:
Modem responded "ERROR" while checking for PIN.
Does this mean that I have locked my SIM?
When I put the SIM in a mobile phone the simPID works but the phone gives and error:
SIM card not valid
I thought that this might mean that the Telstra SIM card isn't registered to run on my phone which has a vodafone SIM. Something about having to unlock the vodafone SIM before changing to another SIM.
I am running on an ASUS eePC 10H:
Ubuntu 11.04 - the Natty Narwhal
Telstra Ultimate AirCard 312U Sierra Wireless USB modem
Can someone help me get my mobile broadband working?
Thanks.
John H.
for error codes can look here
http://www.smssolutions.net/tutorial...gsmerrorcodes/
if having incompatible problems with equipment then look to your isp or supplier,
regards
alexfish
RE 11.04 may apply to 11.10
Note:
Do not install usb_modeswitch from debian ;if have upgraded and and wondered why the device no longer works :
Answer usb_modeswitch debian may have a different dispatcher
Device not switching
try connect at boot and also after boot
Still not switching try the Disk Utility .
if the device list as sr* the chances are it may switch by using the the eject command
check for changes in the usb IDs with the lsusb command from the terminal
If the device has change IDs then it indicates switching
List the new ids with the lsusb Command " lsusb -t -d ****:**** " : edit the ****:**** for the device
IE:
Example outputCode:lsusb -t -d 19d2:0031
the above shows the device has configured and drivers are bound to the deviceCode:/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M |__ Port 1: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 1: Dev 2, If 1, Class=HID, Driver=usbhid, 1.5M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M |__ Port 2: Dev 3, If 0, Class=stor., Driver=usb-storage, 480M |__ Port 8: Dev 30, If 0, Class=vend., Driver=option, 480M |__ Port 8: Dev 30, If 1, Class=vend., Driver=option, 480M |__ Port 8: Dev 30, If 2, Class=stor., Driver=usb-storage, 480M |__ Port 8: Dev 30, If 3, Class=vend., Driver=option, 480M
if most of the above shows
Driver=,****
then the device has not fully configured
can check by
this should show the device and the ports it is connected toCode:ls -al /dev/serial/by-id/*
Example
if an err = cannot access /dev/serial/by-id/$: No such file or directory . then the device has not configuredCode:/dev/serial/by-id/usb-ZTE_Incorporated_ZTE_CDMA_Technologies_MSM_1234567890ABCDEF-if00-port0 -> ../../ttyUSB0 /dev/serial/by-id/usb-ZTE_Incorporated_ZTE_CDMA_Technologies_MSM_1234567890ABCDEF-if01-port0 -> ../../ttyUSB1 /dev/serial/by-id/usb-ZTE_Incorporated_ZTE_CDMA_Technologies_MSM_1234567890ABCDEF-if03-port0 -> ../../ttyUSB2
No driver loading then best try sakis3g , use the sakis3g setup option , it may find a suitable driver and load it.
Device still not recognized
see if your device is supported on Ubuntu
this will list the device database , if the device is listed and not switching then there is a problemCode:tar tf /usr/share/usb_modeswitch/configPack.tar.gz
follow this change the device id highlighted in blue for the device
note if there are any changesCode:sudo su cd /etc/usb_modeswitch.d tar -x 19d2:2000 -f /usr/share/usb_modeswitch/configPack.tar.gz usb_modeswitch -W -c /etc/usb_modeswitch.d/19d2:2000
:
Not switching report bugs to Ubuntu
Device not listed : Please refer to usb_modeswitch for guidance
Drivers not loading try sakis3g if may find a suitable driver : if this fails assume device is not supported at present ,or report bugs to Ubuntu
How to check driver modules remember to change the device ID's in blue
search the current kernel : all letters must be in upper case
EXAMPLE
search all kernelsCode:grep -i v12D1p1436 /lib/modules/`uname -r`/modules.alias
Example output from current kernelCode:grep -i v12D1p1436 /lib/modules/*/modules.alias
red bit = driver moduleCode:alexfish@alexfish-desktop:~$ grep -i v12D1p1436 /lib/modules/`uname -r`/modules.alias alias usb:v12D1p1436d0000dc*dsc*dp*ic*isc*ip* usb_storage alias usb:v12D1p1436d*dc*dsc*dp*icFFiscFFipFF* option
Note This: from the above have place *'s at the appropriate
could be a pointer to device which does not change Ids , or could be problematic , if a problem can try sakis3g with the no storage option
look through your log files if the device is disconnecting and reconnecting:: link to sakis3g forum , Re: tty_send_command
if the device lists and the module is not loadingCode:alias usb:v12D1p1436d0000dc*dsc*dp*ic**isc**ip* usb_storage alias usb:v12D1p1436d****dc*dsc*dp*icFFiscFFipFF* option
Note: all new usb_modeswitch device switching data should be placed in the /etc/usb_modeswitch.d folderCode:sudo modprobe <driver>
If have upgraded to Debian Packages and the device is not switching then it could be the usb_modeswitch dispatcher
Reinstall the Ubuntu version of usb_modeswtch + the data
if can't role back the version and have saved a copy of the original dispatcher try
go to the usb_modeswitch_dispatcher(copy) : ensure named "usb_modeswitch_dispatcher" copy itCode:gksu nautilus
goto the /usr/sbin/
remove the usb_modeswitch_dispatcher exec (recognized as a diamond) to the rubbish bin
paste the usb_modeswitch_dispatcher(copy)
ensure it is named "usb_modeswitch_dispatcher"
exit the terminal , plug the device in and see what happens
ALSO CHECK OUT POSTS #60 and #61
Last edited by alexfish; December 4th, 2011 at 12:55 PM. Reason: sudo
First Read Foot of page, RE: IMPORTANT NOTIFICATION . prior to committing.
Also worth downloading if at this Post: Linux USB drivers : Related post #68
how to find a suitable module: try this
look through the list to identify the deviceCode:grep usb /sys/bus/usb/devices/*/modalias
example
take the last 4 bits of the modalias of each line of the device and check allCode:alexfish@alexfish-desktop:~$ grep usb /sys/bus/usb/devices/*/modalias /sys/bus/usb/devices/1-0:1.0/modalias:usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00 /sys/bus/usb/devices/1-2:1.0/modalias:usb:v059Bp047Ad0000dc00dsc00dp00ic08isc06ip50 /sys/bus/usb/devices/1-8:1.0/modalias:usb:v19D2p0031d0000dc00dsc00dp00icFFiscFFipFF /sys/bus/usb/devices/1-8:1.1/modalias:usb:v19D2p0031d0000dc00dsc00dp00icFFiscFFipFF /sys/bus/usb/devices/1-8:1.2/modalias:usb:v19D2p0031d0000dc00dsc00dp00ic08isc06ip50 /sys/bus/usb/devices/1-8:1.3/modalias:usb:v19D2p0031d0000dc00dsc00dp00icFFiscFFipFF /sys/bus/usb/devices/2-0:1.0/modalias:usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00 /sys/bus/usb/devices/2-1:1.0/modalias:usb:v0603p00F2d0112dc00dsc00dp00ic03isc01ip01 /sys/bus/usb/devices/2-1:1.1/modalias:usb:v0603p00F2d0112dc00dsc00dp00ic03isc00ip00
from example
: use "ipFF"Code:/sys/bus/usb/devices/1-8:1.3/modalias:usb:v19D2p0031d0000dc00dsc00dp00icFFiscFFipFF
find a suitable driver
say for instance
normal usb devices like cdma and option drivers
fast interface devicesCode:grep -i ipFF /lib/modules/`uname -r`/modules.alias
look through the list,Code:grep -i ip00 /lib/modules/`uname -r`/modules.alias
Example of List (part of)
check your device modalias listing IE:Code:alias usb:v12D1p1401d*dc*dsc*dp*icFFiscFFipFF* option alias usb:v12D1p1004d*dc*dsc*dp*icFFiscFFipFF* option alias usb:v12D1p1003d*dc*dsc*dp*icFFiscFFipFF* option alias usb:v12D1p1001d*dc*dsc*dp*icFFiscFFipFF* option alias usb:v106Cp3718d*dc*dsc*dp*icFFiscFFipFF* qcaux alias usb:v1199p6892d*dc*dsc*dp*icFFiscFFipFF* sierra alias usb:v1199p6891d*dc*dsc*dp*icFFiscFFipFF* sierra alias usb:v1199p6890d*dc*dsc*dp*icFFiscFFipFF* sierra
copy and paste the device modalias + a line from the grep modules ;Code:usb:v19D2p0031d0000dc00dsc00dp00icFFiscFFipFF
Now use * to line up the two modalias :: look at the pattern
Example
if the driver looks promising ; load the driver. use the modprobe <module>Code:usb:v19D2p0031d0000dc00dsc00dp00icFFiscFFipFF usb:v1199p6891d****dc**dsc**dp**icFFiscFFipFF* sierra
example
]check the system to see if a file new-id ; usualy in the path /sys/bus/drivers/<module name>/new_idCode:sudo su modprobe sierra
this gives the pathCode:ls /sys/bus/usb/drivers/*/module/drivers/*/new_id
Huawie Mobile Partner (Drivers) if you have installed the drivers then if connected via usb port , the net part shows asCode:/sys/bus/usb/drivers/sierra/module/drivers/usb-serial:sierra/new_id
The Actual Driver is " hw_cdc_driver" try "modinfo hw_cdc_driver" to see details.Code:/sys/bus/usb/drivers/huawei_ether/module/drivers/usb:huawei_ether/new_id
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~
Here is a example of a device which normally uses the option driver
to force the driver example change the ID's of the device highlighted in blue : Also not the change from upper case to lower case
check the results in the /dev/tty or the dev/serialCode:sudo su echo "19d2 0031" > /sys/bus/usb/drivers/sierra/module/drivers/usb-serial:sierra/new_id
also list usb devices with this codeCode:ls -al /dev/serial/by-id/*
To List the modules by vendor remember to change the id in blue, and note the lower case if lsusb listing is "19D2 then = 19d2"Code:usb-devices
Code:grep -i v19d2 /lib/modules/`uname -r`/modules.alias
USB ID's:
don,t forget to keep the usb ids up to date
to view the usb.ids paste this in the browser
or can wget daily snapshotCode:file:///var/lib/usbutils/usb.ids
file will be in the home directory , open with your browserCode:wget http://www.linux-usb.org/usb.ids
the info may indicate the type of driver required for the device :IE wimax ,gobi etc etc not always specific , but usually confirmed by the modalias
to update the usb.ids
Remember before going out to buy the Latest gadget check the device ID's : a little research helpsCode:sudo /usr/sbin/update-usbids
Here I am assuming you Are connected by one means or another. if the info not available , It is your decision
Finally : check out #61
If have a device and found a suitable driver using the above Please report at Launch Pad :also feel free to post Here
Device description : Device USB-IDs : Driver Module : The Path to the new_id :: IE: echo "19d2 0031" > /sys/bus/usb/drivers/sierra/module/drivers/usb-serial:sierra/new_id"
OR how it was achieved
A driver to play about with , try safe-serial use at own risk
use grep to find devices which can be used
below is the modinfo of the driverCode:grep -i 02ip /lib/modules/`uname -r`/modules.alias
Question What is the deference between searching a hard link and a sym linkCode::~$ modinfo safe-serial filename: /lib/modules/2.6.38-12-generic/kernel/drivers/usb/serial/safe_serial.ko license: GPL description: USB Safe Encapsulated Serial author: sl@lineo.com, tbr@lineo.com, Johan Hovold <jhovold@gmail.com> srcversion: 7F505336AEAE3A308E5D19D alias: usb:v0000p0000d*dc02dsc*dp*icFFisc02ip* alias: usb:v05F9pFFFFd*dc02dsc*dp*icFFisc02ip* alias: usb:v04DDp8004d*dc02dsc*dp*icFFisc02ip* alias: usb:v04DDp8003d*dc02dsc*dp*icFFisc02ip* alias: usb:v04DDp8002d*dc02dsc*dp*icFFisc02ip* alias: usb:v04DDp8001d*dc02dsc*dp*icFFisc02ip* alias: usb:v03F0p2101d*dc02dsc*dp*icFFisc02ip* alias: usb:v049FpFFFFd*dc02dsc*dp*icFFisc02ip* depends: usbserial vermagic: 2.6.38-12-generic SMP mod_unload modversions 686 parm: vendor:User specified USB idVendor (required) (ushort) parm: product:User specified USB idProduct (required) (ushort) parm: debug:Debug enabled or not (bool) parm: safe:Turn Safe Encapsulation On/Off (bool) parm: padded:Pad to full wMaxPacketSize On/Off (bool)
Answer: if your looking to install a driver at connection there is less to look at See Below
also note the base driver: Example also reason to highlight in BLUE
/sys/bus/usb-serial/drivers/generic/new_id < This one , say if the option 1 driver will not Bind to the device or Problematic then look to use the base driver example at Post #2 shows the original method to bind to the id's at boot
/sys/bus/usb-serial/drivers/option1/new_idHas anyone got the Huawei E586 working on ubuntu 11.10?Code:1./sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id 2 . /sys/bus/usb-serial/drivers/option1/new_id 1) ls /sys/bus/usb/drivers/*/module/drivers/*/new_id /sys/bus/usb/drivers/hub/module/drivers/usb:hub/new_id /sys/bus/usb/drivers/hub/module/drivers/usb:usbfs/new_id /sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id /sys/bus/usb/drivers/uas/module/drivers/usb:uas/new_id /sys/bus/usb/drivers/usbfs/module/drivers/usb:hub/new_id /sys/bus/usb/drivers/usbfs/module/drivers/usb:usbfs/new_id /sys/bus/usb/drivers/usbhid/module/drivers/hid:generic-usb/new_id /sys/bus/usb/drivers/usbhid/module/drivers/usb:usbhid/new_id /sys/bus/usb/drivers/usbserial_generic/module/drivers/usb-serial:generic/new_id /sys/bus/usb/drivers/usbserial/module/drivers/usb-serial:generic/new_id /sys/bus/usb/drivers/usb-storage/module/drivers/usb:usb-storage/new_id 2) ls /sys/bus/*/drivers/*/new_id /sys/bus/hid/drivers/generic-usb/new_id /sys/bus/pci/drivers/agpgart-amdk7/new_id /sys/bus/pci/drivers/agpgart-intel/new_id /sys/bus/pci/drivers/agpgart-nvidia/new_id /sys/bus/pci/drivers/agpgart-via/new_id /sys/bus/pci/drivers/asiliantfb/new_id /sys/bus/pci/drivers/ata_generic/new_id /sys/bus/pci/drivers/ata_piix/new_id /sys/bus/pci/drivers/ce4100_spi/new_id /sys/bus/pci/drivers/C-Media PCI/new_id /sys/bus/pci/drivers/ehci_hcd/new_id /sys/bus/pci/drivers/forcedeth/new_id /sys/bus/pci/drivers/imsttfb/new_id /sys/bus/pci/drivers/Intel ICH/new_id /sys/bus/pci/drivers/ioapic/new_id /sys/bus/pci/drivers/k8temp/new_id /sys/bus/pci/drivers/langwell_gpio/new_id /sys/bus/pci/drivers/nForce2_smbus/new_id /sys/bus/pci/drivers/nvidia/new_id /sys/bus/pci/drivers/ohci_hcd/new_id /sys/bus/pci/drivers/parport_pc/new_id /sys/bus/pci/drivers/pata_acpi/new_id /sys/bus/pci/drivers/pata_amd/new_id /sys/bus/pci/drivers/pata_sis/new_id /sys/bus/pci/drivers/pci_eisa/new_id /sys/bus/pci/drivers/pcieport/new_id /sys/bus/pci/drivers/pdc_adma/new_id /sys/bus/pci/drivers/sata_nv/new_id /sys/bus/pci/drivers/serial/new_id /sys/bus/pci/drivers/uhci_hcd/new_id /sys/bus/usb/drivers/hub/new_id /sys/bus/usb/drivers/uas/new_id /sys/bus/usb/drivers/usbfs/new_id /sys/bus/usb/drivers/usbhid/new_id /sys/bus/usb/drivers/usb-storage/new_id /sys/bus/usb-serial/drivers/generic/new_id /sys/bus/usb-serial/drivers/option1/new_id
worth following, but don't know if the outcome will be a success :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~
IMPORTANT NOTIFICATION
HUAWEI PRODUCT E585 (12d1:1446) :3g/4g read
Example of devices with different switching modes
http://www.draisberghof.de/usb_modes...opic.php?t=836
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~
also look at
HUAWEI PRODUCT E353 (0x1506)
http://www.kernel.org/pub/linux/kern...hangeLog-3.1.6
definitely look here
[SOLVED] Huawei E5832 and Ubuntu 12.04
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~
have check latest updates on Ubuntu 11.04 as regards this driver cdc-wdm
so if have Huawei device similar to the above check the Modalias , info for driver shows
You may have to load the driver , then put the device id's into the new id / pathCode:alexfish@alexfish-desktop:~$ modinfo cdc-wdm filename: /lib/modules/2.6.38-13-generic/kernel/drivers/usb/class/cdc-wdm.ko license: GPL description: USB Abstract Control Model driver for USB WCM Device Management author: Oliver Neukum srcversion: CAFE8B3EA57870E596D4DA7 alias: usb:v*p*d*dc*dsc*dp*ic02isc09ip* depends: vermagic: 2.6.38-13-generic SMP mod_unload modversions 686
According to info it only engages the cdc-ether type interface so will also have to bind the option or usb-serial driver after binding the cdc-wdm driver moduleCode:/sys/bus/usb/drivers/cdc_wdm/module/drivers/usb:cdc_wdm/new_id
Note: part of the device Modalias should show
http://lists.openwall.net/netdev/2012/01/20/7Code:usb:v*p*d*dc*dsc*dp*ic02isc09ip*
Please read though the next few posts if have one of these devices
alexfish
Last edited by alexfish; March 24th, 2012 at 01:47 PM. Reason: update :
Bookmarks