You are not logged in.
Pages: 1
Heya,
Just to let you know, I created a new wiki entry on how I got my gobi 3000 modem working:
I have a HP EliteBook 8560p with a HP un2430 broadband modem.
Offline
Great! I'll definitely check it out. I got a ThinkPad X220 with a gobi 3000 modem.
Offline
Sadly, this method still doesn't work for me.
After install gobi-loader from AUR and re-modprobe "qcserial", wdial indeed can recognize my Gobi 3k device:
Bus 004 Device 003: ID 1199:9013 Sierra Wireless, Inc.
However, after the first unsuccessful trial for dialing, wvdial cannot communicate with that device anymore.
Wvdial prompt:
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.
Same error even *after rebooting.*
Also, I noticed that if install gobi-loader, then reboot, during "init", gobi-loader seems lead to Udev failed to load (other devices are still functional; remove gobi-loader can avoid this problem).
Last edited by cap_sensitive (2011-11-17 05:40:06)
Offline
How did you obtain your firmware files, have you tried using different firmware files?
I also had simillar problems, sometimes the device would stop responding, but a reboot helped, and since configuring gobi_loader I haven't experienced those lock-ups. Can you show me your 60-gobi.rules file?
Offline
How did you obtain your firmware files
I obtain my firmware files directly from the same computer, since I have a dual-boot configuration in it. (Win 7 X64 and Archlinux X64)
have you tried using different firmware files?
Yes, I have tried all firmwires. (from 1 to 9)
I also had simillar problems, sometimes the device would stop responding, but a reboot helped, and since configuring gobi_loader I haven't experienced those lock-ups. Can you show me your 60-gobi.rules file?
Here's my 60-gobi.rules:
# udev rules for firmware loading on qualcomm gobi devices
ACTION=="add", SUBSYSTEM=="tty" KERNEL=="ttyUSB*" GOTO="gobi_rules"
GOTO="gobi_rules_end"
LABEL="gobi_rules"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9211", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="201d", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="04da", ATTRS{idProduct}=="250c", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="413c", ATTRS{idProduct}=="8171", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="1410", ATTRS{idProduct}=="a008", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="1774", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="fff2", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="1557", ATTRS{idProduct}=="0a80", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9008", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9201", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9221", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9231", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="1f45", ATTRS{idProduct}=="0001", RUN+="gobi_loader $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="16d8", ATTRS{idProduct}=="8001", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9000", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="241d", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9204", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9214", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9224", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9234", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9244", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9264", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9274", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
ATTRS{idVendor}=="413c", ATTRS{idProduct}=="8185", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi"
LABEL="gobi_rules_end"
Offline
Sorry it took me so long to answer, work is overwhelming, but hey, at last I have a solution
Forget the wiki, I'm going to update it soon, in the meantime, grab GobiSerial from here:
Before running make install, be sure to change the vendor id in GobiSerial.c, blacklist qcserial module and then just use /dev/ttyUSB0 in wvdial or whatever to connect.
That's it!
Offline
make install results in:
[paul@moses GobiSerial]$ make install
rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c .tmp_versions Module.* modules.order
make -C /lib/modules/3.1.4-1-ARCH/build SUBDIRS=/tmp/GobiSerial modules
make: *** /lib/modules/3.1.4-1-ARCH/build: No such file or directory. Stop.
make: *** [all] Error 2
Offline
make install results in:
[paul@moses GobiSerial]$ make install rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c .tmp_versions Module.* modules.order make -C /lib/modules/3.1.4-1-ARCH/build SUBDIRS=/tmp/GobiSerial modules make: *** /lib/modules/3.1.4-1-ARCH/build: No such file or directory. Stop. make: *** [all] Error 2
make && make install...
There is nothing to install before you compile...
Offline
OK - make && make install results:
[paul@moses GobiSerial]$ make && make install
rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c .tmp_versions Module.* modules.order
make -C /lib/modules/3.1.4-1-ARCH/build SUBDIRS=/tmp/GobiSerial modules
make: *** /lib/modules/3.1.4-1-ARCH/build: No such file or directory. Stop.
make: *** [all] Error 2
Offline
OK - make && make install results:
... make: *** /lib/modules/3.1.4-1-ARCH/build: No such file or directory. Stop. ...
/lib/modules/3.1.4-1-ARCH/build is defined by a line in the Makefile:
KDIR := /lib/modules/$(shell uname -r)/build
I assume it's just a build dir, in which case you could create it manually or change that line.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
OK - apologies for being dense and I'm really not trying to be difficult here. Now I have:
[root@moses GobiSerial]# make && make install
rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c .tmp_versions Module.* modules.order
make -C /lib/modules/3.1.5-1-ARCH/build SUBDIRS=/tmp/GobiSerial modules
make[1]: Entering directory `/lib/modules/3.1.5-1-ARCH/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/3.1.5-1-ARCH/build'
make: *** [all] Error 2
Offline
OK - apologies for being dense and I'm really not trying to be difficult here. Now I have:
[root@moses GobiSerial]# make && make install rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c .tmp_versions Module.* modules.order make -C /lib/modules/3.1.5-1-ARCH/build SUBDIRS=/tmp/GobiSerial modules make[1]: Entering directory `/lib/modules/3.1.5-1-ARCH/build' make[1]: *** No rule to make target `modules'. Stop. make[1]: Leaving directory `/lib/modules/3.1.5-1-ARCH/build' make: *** [all] Error 2
You need linux-headers installed to build kernel modules.
Offline
OK - it now compiles fine - thanks for the help. I'm now going back to the step which says replace the vendor id in GobiSerial.c - first of all I can't see a vendor id anywhere in GobiSerial.c and secondly how do I know what to replace it with?
Having just compiled and loaded the module (after blacklisting qcserial and rebooting) I'm not seeing a /dev/ttyUSBX at all, which I'm guessing is down to this vendor id business?
Offline
It's around the 150 line number, you should see 2 ID's defined, I deleted one and edited the remaining one to match my ID, you can get it by issuing the lsusb command, my device line is:
Bus 004 Device 004: ID 03f0:231d Hewlett-Packard
This is the line in GobiSerial.c:
{ USB_DEVICE( 0x03f0, 0x371d ) },
Offline
Jumping into this old thread but for the good reason.
We've (colleague goll, other colleagues in the company and myself) found out that GobiSerial is a problematic piece of software, because it's completely unmaintained and kernel is going through major rewrites for USB support lately in versions 3.4 and 3.5.
All that rendered GobiSerial unusable in new kernels. So here you are, an attempt to maintain GobiSerial updated for new kernel versions. :-)
https://github.com/casastorta/gobiserial/
DKMS install method is described here:
https://github.com/casastorta/gobiseria … GobiSerial
Wiki documents for contributors will follow soon (I hope today). This is completely public project, so we accept any kind of improvements to it - no matter if it's only new devices added to device ID lists or some bigger improvement. In code, wiki documents, or anything else really.
I hope you'll find this project useful.
Offline
Pages: 1