system: Opensuse 11.1 with custom kernel from Kernelorg and KDE3.5
uname -a
Linux linux-2c5j **3.0.4-41-desktop** #1 SMP PREEMPT Sun Sep 4 18:51:01 CEST 2011 i686 i686 i386 GNU/Linux
The device is correctly visible:
lsusb
**Bus 002 Device 003: ID 05c6:9204 Qualcomm, Inc.**
Bus 002 Device 002: ID 8087:0020
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 046d:c012 Logitech, Inc. Mouseman Dual Optical
Bus 001 Device 005: ID 045e:00dd Microsoft Corp.
Bus 001 Device 003: ID 0a5c:217f Broadcom Corp.
Bus 001 Device 004: ID 17ef:1005 Lenovo
Bus 001 Device 002: ID 8087:0020
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The modem responds with O.K if interrogated in kppp but the response on AT are not there. It does not dial. The modem has been installed as dev/tty/USB0
I did compile Gobi loader 0.7 and it did run make and make install without error. The gobi rules are correctly installed and I did copy the firmware in the respective directory. The problem is: did I copy the right firmware? Is there some other problem. How can I diagnose if the firmware is the correct one (I unpacked the windows ones on a windows machine and there are 6)? I do not see usb0 offered by networkmanager (the network traffic is regulated through networkmanager).
Thank you to everybody who has further info on this.
I hope someone who is familiar with this hardware can assist you more specifically. Here’s a potentially useful link that may help clarify any doubt you may have about firmware:
It also shows you the idea behind dialling with the wvdial CLI utility. (Good for testing).
BTW, I note you’re using openSUSE 11.1, albeit with a custom kernel. There are some notes here (concerning openSUSE 11.3) which may (or may not be) relevant.
my perception of gobi2000; from following various threads on other forums; is that if you want to slowly drive yourself mad; and quietly pull all your hair out at home; all by yourself; is:…get yourself a gobi2000 and attempt to get it to work;
Well, I know now that my Gobi2000 currently does not charge the firmware. This because the
ID 05c6:9204
should change into
ID 05c6:9205
I will try one by one the different combinations proposed and then I will also try the trick with the battery (pull out the battery and the take of the laptop from the sector - switched off of course - and press the on switch for 30 seconds. Gobi2000 is a very common device and its functionality should be addressed conveniently by a modern distribution. Shame on Qualcomm! Huawei would be my preferred choice. But you are told only that the laptop has WWAN not always you know about the chip-set problem.
Well there is a feature threat request for this in OpenFATE. You may vote for it to fix the inconvenience in the future. I will report back on the issues and thanks up to now for the links provided. I really do appreciate.
Ok, having followed the indications of Qualcomm Gobi 2000 - ThinkWiki I was now able to start the Gobi.
The device actually does not appear anymore as Qualcomm in the lsusb listing but does appear correctly during boot. It is not recognized (could it have been different) by the networkmanager applett of KDE (0,7) but is functional with umtsmon. It also reacts correctly with kppp.
I am not currently in the country where I have the 3G subscription. Once returned I will update on the result.
For the record:
Laptop is an Lenovo X201 12’ Notebook. It was sold with WWAN (generical, not bound to provider - at least sold like this) and sold without any O.S. (which made me avoid the MS tax. The unpacking of the latest driver was done with wine, The option choosen was to combine the firmware solution “6” and “UMTS”. I copied all 3 files in /lib/firware/gobi (after having compiled successfully Gobiloader 0.7 from the wesite of the project beforehand).
Watch out to position the sim with the “cut” side versus the outer border (direction of battery) of the notebook and contact plate vs the bottom. This seems to be a bit “counterintuitive” but gives the desired result.
The device mounts under /dev/ttsy/usb1 (and not /dev//usb0 or 2). The other two positons are also claimed, maybe that part is the GPS I guess.
Cheers to all who gave links and input. Thank you very much.
One last update on the question: is it worth the effort? The short answer version is: yes, definitely.
My former setting was Sony Ericsson’s Hazel J20 with UBS connect on fastport and interface /dev/tty/usb0. The main differences are not only in the portability and the energy consumption (as the connect feeds also the phone). Outstanding is the difference in the transmission performance and the signal strength. Apparently it is a major advantage to be able to use the internal G3/WLAN antenna inside the laptop X201 cover if compared with the hidden small antenna of the Hazel.
The establishment of the connect is also much faster, the transmission as well (I would say that the speed is about 25% higher) and the delay between request and charge of the pages did vanish.
So, yes, although it is a major search for info and trial and error for the right firmware, once it is done, it is worth it.
As I do still run KDE3.5 and openSUSE 11.1, I cannot tell you if the network manager is now effective. I do run on machines with 11.4 installed the networkmanager plasmoid applet that seem to work. But there I know only the functionality with WLAN and LAN. No experience with mixed use on laptops.
If you have still 11.1 alternatives to umtsmon (that appears not really stable) are kppp and wvdial. Both seem to work well where wvdial does not work for me complaining that there is no directory /dev/modem. Well, I know that there isn’t, but apparently “wvdial” expects it to be there.
I will try to do a short and complete write up of what I did but it will be most valid for user with self compiled kernel that are doing all from source code (as I did with the compile of “Gobi-loader”. I do know anything about the functionality of the rpm packed Gobi-loader of the 11.4 repositories. If anybody has experienced a success with it, feel free to post here to complete the information for who is in search for answers.
Cheers.
- and press the on switch for 30 seconds. Gobi2000 is a very common device and its functionality should be addressed conveniently by a modern distribution. Shame on Qualcomm! Huawei would be my preferred choice. But you are told only that the laptop has WWAN not always you know about the chip-set problem.