sony-vaio-z-series team mailing list archive
-
sony-vaio-z-series team
-
Mailing list archive
-
Message #00802
Re: vaio Z 3G Modem
Hi,
Can anyone provide me the firmware or where I can find it? I only use Linux
so I cant boot windows here.
I dont know the location options either.. But I am form Portugal.
Thanks for the help.
On Mon, Nov 16, 2009 at 4:30 PM, pierre.fr34 <pierre.fr34@xxxxxxxxx> wrote:
> Here is what I did to install the Qualcomm 3 G modem on my Z31 (Ubuntu 9.04
> Jaunty). From several sources, thanks to all.
>
> 1. install qcserial module (maybe not necessary anymore in 9.10)
>
> copy qserial.c et Makefile from
> http://vaioz31.blogspot.com/2009/04/3g-support-qualcomm-gobi-chipset-step1.html
> make
> sudo make install
>
> 2. install gobi_loader
>
> download from http://www.codon.org.uk/~mjg59/gobi_loader/<http://www.codon.org.uk/%7Emjg59/gobi_loader/>
> make
> sudo make install
>
> 3. install firmware
>
> Boot in Windows, look for the right driver for your region in C:\Documents
> and Settings\All Users\Application Data\QUALCOMM\QDLService\Options.txt
> then copy amss.mbn et apss.mbn from the corresponding directory (the one
> listed in Options.txt) to /lib/firmware/gobi that you have to create in
> Ubuntu using administrative privileges
>
> 4. reload qcserial
>
> sudo modprobe -r qcserial
> sudo modprobe qcserial
>
> 5. To activate the modem and make it load the driver when I want ot use it,
> I use the following script with the Wireless switch on the ON position (
> https://lists.launchpad.net/sony-vaio-z-series/msg00411.html):
>
> #!/bin/sh
> echo 0 > /sys/class/rfkill/rfkill2/state
> sleep 1
> modprobe -r qcserial
> #modprobe -r usbserial
> #modprobe usbserial vendor=0x05c6 product=0x9222
> #modprobe usbserial
> modprobe qcserial
> echo 1 > /sys/class/rfkill/rfkill2/state
>
> Then the modem appear in network-manager and you can configure the
> connection with your 3G provider's settings.
>
> Hope this helps. Nothing new. Just compilation of different informations.
>
> Regards,
>
> Pierre
>
>
>
> Yes, that's your WWAN. The ID 05c6:9221 means, that the correct
>> firmware has not yet been loaded. After successfully loading the
>> firmware, the entry reads:
>>
>> Bus 001 Device 005: ID 05c6:9222 Qualcomm, Inc.
>>
>> Now, how to load the firmware? The loader itself, a small C program,
>> should come with 9.10, along with the required udev rule to do the
>> loading automatically.
>>
>> What is probably missing is the firmware itself. You need to copy two
>> files over from Windows. These are
>>
>> /lib/firmware/gobi/amss.mbn
>> /lib/firmware/gobi/apps.mbn
>>
>> The loader should pick them up automatically.
>>
>> On my Z31 these files can be found here:
>>
>> <Windows-Volume>/QUALCOMM/QDLService/Packages/
>>
>> You need to find the firmware appropriate for your region. I did this
>> back in April and can't remember offhand which the one was I am using.
>>
>> To make sure that UDEV has a rule for Gobi, check if this file exists:
>>
>> /etc/udev/rules.d/60-gobi.rules
>>
>> These are the contents:
>>
>> ---SNIP---
>> # 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"
>> LABEL="gobi_rules_end"
>> ---SNIP---
>>
>> Hope that helps,
>> Mike
>>
>>
>> 2009/11/16 André Bergner <andre.bergner.0@xxxxxxxxxxxxxx>:
>>
>>> Now, with `lsusb` I get:
>>>
>>> Bus 003 Device 002: ID 147e:1000 Upek
>>> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 001 Device 004: ID 05c6:9221 Qualcomm, Inc.
>>> <-------------------
>>> (*)
>>> Bus 001 Device 003: ID 05ca:18b0 Ricoh Co., Ltd
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 008 Device 002: ID 044e:3017 Alps Electric Co., Ltd
>>> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>
>>> If I understood right (*) is my 3G modem, correct?
>>> So I see it as usb device but Gnome network-manager does not recognize
>>> it.
>>> What alternative do I have to get a working connection.
>>> HSOconnect? Or is their something similiar to pppoefconf?
>>>
>>>
>>>
>>> 2009/11/15 vick <weasalandme@xxxxxxxxx>
>>>
>>>> Here is the patch agains the sony-laptop-zseries-0.9np3 version of the
>>>> module, no clue why diff is not producing the headers with the file name
>>>> info.
>>>>
>>>> 1469c1469
>>>> < ret = sony_call_snc_handle(0x124, 0x00, &result);
>>>> ---
>>>>
>>>>> ret = sony_call_snc_handle(0x124, 0xb00, &result);
>>>>>
>>>> 1476c1476
>>>> < if ((result & 0xff) == 0x00)
>>>> ---
>>>>
>>>>> if (result & 0x1)
>>>>>
>>>> 1478c1478
>>>> < if (((result & 0xff00) >> 8) == 0x10)
>>>> ---
>>>>
>>>>> if (result & 0x2)
>>>>>
>>>> 1480c1480
>>>> < if (((result & 0xff0000) >> 20) == 0x2)
>>>> ---
>>>>
>>>>> if (result & 0x1c)
>>>>>
>>>> 1482c1482
>>>> < if ((result >> 24) == 0x30)
>>>> ---
>>>>
>>>>> if (result & 0x20)
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
>>>> Post to : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
>>> Post to : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
>> Post to : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>>
> _______________________________________________
> Mailing list: https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
> Post to : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~sony-vaio-z-series<https://launchpad.net/%7Esony-vaio-z-series>
> More help : https://help.launchpad.net/ListHelp
>
References