← Back to team overview

sony-vaio-z-series team mailing list archive

Re: [VPCZ2] How to get Huawei Gobi 3000 working with kernel 3.2 ?

 

@Rob
sudo modprobe GobiSerial  debug=y give:

[ 1466.820862] usbcore: registered new interface driver usbserial
[ 1466.820878] USB Serial support registered for generic
[ 1466.820914] usbcore: registered new interface driver usbserial_generic
[ 1466.820916] usbserial: USB Serial Driver core
[ 1466.821175] USB Serial support registered for GobiSerial
[ 1466.821191] GobiSerial::GobiProbe
[ 1466.821194] GobiSerial::GobiProbe Num Interfaces = 3
[ 1466.821197] GobiSerial::GobiProbe This Interface = 1
[ 1466.821199] GobiSerial::GobiProbe Unsupported interface number
[ 1466.821208] GobiSerial::GobiProbe
[ 1466.821211] GobiSerial::GobiProbe Num Interfaces = 3
[ 1466.821213] GobiSerial::GobiProbe This Interface = 2
[ 1466.821215] GobiSerial::GobiProbe Modem port found
[ 1466.822269] GobiSerial 1-1.4:1.2: GobiSerial converter detected
[ 1466.822393] usb 1-1.4: GobiSerial converter now attached to ttyUSB0
[ 1466.822423] usbcore: registered new interface driver GobiSerial
[ 1466.822426] GobiSerial: 2011-07-29-1026

@Vick
I am not a kernel expert and I am pretty lost on the way to recompile qcserial.c without recompiling all the kernel. So I have linux-source installed and I copied qcserial.c from the source tree to another folder. I made the change adding a line with the appropriate vendor and product ID. Big question now ! How to recompile it ? I tried to copy the Makefile and run it in the same folder as qcserial.c and I got this:

hadim boromir /home/hadim/qcserial $ make qcserial
cc     qcserial.c   -o qcserial
qcserial.c:15:28: fatal error: linux/tty_flip.h: No such file or directory
compilation terminated.
make: *** [qcserial] Error 1

Is this Makfile appropriate ? If it does. How can I add linux include file in ?

Cheers,

On 11/29/2011 12:00 AM, Rob Mukai wrote:
HadiM, That is definitely strange. What does dmesg say?

Mine says this: dmesg | grep GobiSerial [    9.176518] USB Serial
support registered for GobiSerial [    9.185275] GobiSerial
1-1.4:1.2: GobiSerial converter detected [    9.185352] usb 1-1.4:
GobiSerial converter now attached to ttyUSB0 [    9.191359]
GobiSerial 1-1.4:1.3: GobiSerial converter detected [    9.191440]
usb 1-1.4: GobiSerial converter now attached to ttyUSB1 [ 9.191459]
usbcore: registered new interface driver GobiSerial [ 9.191461]
GobiSerial: 2011-07-29-1026

Not sure if that helps or not...

Rob

On Mon, Nov 28, 2011 at 3:44 PM, HadiM <marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx>> wrote:

I change GobiSerial.c code source as you did and I was using Ubuntu
Oneiric one week ago with the same issue... that's definitivly
strange... Maybe it's an hardware problem. I check the bios and
didnt notice anything wrong. Anyway we keep in touch for the GPS.

Cheers,


On 11/28/2011 09:49 PM, Rob Mukai wrote:

HadiM, Yes we have the same config. I am using a compiled 3.2 rc2
from kernel.org <http://kernel.org> <http://kernel.org>, device id on
the Gobi Module is the same

as well. Only difference is I am running Oneiric. The ttyUSB1 just
loaded once I modprobed GobiSerial. Did you change the VIDPID in the
 GobiSerial.c to this: [code]
/*============================__==============================__===============*/



// Qualcomm Gobi 3000 VID/PIDs
/*============================__==============================__===============*/



static struct usb_device_id GobiVIDPIDTable[] =
{ { USB_DEVICE( 0x12d1, 0x14f1 ) },   // Gobi 3000 QDL device {
USB_DEVICE( 0x12d1, 0x14f1 ) },   // Gobi 3000 Composite Device { }
// Terminating entry }; MODULE_DEVICE_TABLE( usb, GobiVIDPIDTable );
 [/code] That's all I did, then do make, sudo make install

I can't seem to get GobiNet working but as you mentioned earlier,
GobiSerial works with wvdial or gnome-ppp.

So hopefully we can figure out why the GPS is not working.

Rob

On Mon, Nov 28, 2011 at 12:18 PM, HadiM <marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx> <mailto:marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx>>> wrote:

I just saw on your www.codeaurora.org <http://www.codeaurora.org>
<http://www.codeaurora.org>

post that you get ttyUSB1 created after loading GobiSerial. How did
yout get that ?

Is your configuration same as mine ?

Vaio Z2 kernel 3.2 Gobi module with lsusb command: Bus 001 Device
008: ID 12d1:14f1 Huawei Technologies Co., Ltd. Linux Mint 12 (same
as Ubuntu Oneiric)

-- Hadrien



On Mon, Nov 28, 2011 at 20:13, HadiM <marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx> <mailto:marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx>>> wrote:
Ok we keep in touch for the GPS. Seems to be an Huawei problem
because
I saw on other Gobi 3000 mobile (sierra if I remember well), GPS
working (ttyUSB1 appears after modprobe GobiSerial).

Last point: if any NetworkManager or close to NetworkManager
developer
see this: any chance to get GobiSerial working with
NetworkManager ?

Cheers,

-- Hadrien



On Mon, Nov 28, 2011 at 18:25, Rob Mukai
<dothedog2010@xxxxxxxxx <mailto:dothedog2010@xxxxxxxxx>
<mailto:dothedog2010@xxxxxxxxx <mailto:dothedog2010@xxxxxxxxx>__>>
wrote:
Hadrien, Thanks for the hint on compiling. I never got GobiNet
working
before.
Although now with your hint, I have the GobiSerial and wvdial
working. As
for the GPS, I have a post at codeaurora.org
<http://codeaurora.org> <http://codeaurora.org>
here:
https://www.codeaurora.org/__forums/viewtopic.php?f=15&t=__134
<https://www.codeaurora.org/forums/viewtopic.php?f=15&t=134>

<https://www.codeaurora.org/__forums/viewtopic.php?f=15&t=__134
<https://www.codeaurora.org/forums/viewtopic.php?f=15&t=134>>
looking for help with the GPS. Looks like they want the GobiAPI
stuff
working as well. Please keep us updated on how you go with the
GPS. I am
very interested in getting it to work. Rob

On Sun, Nov 27, 2011 at 4:25 PM, HadiM <marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx> <mailto:marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx>>> wrote:

For GobiNet I found this

https://www.codeaurora.org/__forums/viewtopic.php?f=15&t=__144
<https://www.codeaurora.org/forums/viewtopic.php?f=15&t=144>
<https://www.codeaurora.org/__forums/viewtopic.php?f=15&t=__144
<https://www.codeaurora.org/forums/viewtopic.php?f=15&t=144>>. The
patch

is working for me and shows eth1 interface. NetworkManager
see it
simply at a unplugged cable...

(Anyway GobiNet is not a big deal for me because I have 3G
connection
working with GobiSerial, I am much more interested in
getting GPS
working :-))

Cheers,

-- Hadrien



On Mon, Nov 28, 2011 at 00:16, HadiM <marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx> <mailto:marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx>>> wrote:
Hi all,

Since kernel 3.2 Gobi drivers cannot be compiled. Here you
have a tiny
trick to get it compile. It works for
GobiSerial_2011-07-29-1026.__tar.gz and
GobiNet_2011-07-29-1026.tar.__gz.

## Trick ##

add "#include <linux/module.h>" at the beginning of
GobiSerial.c and
GobiNet.c

## Trick end ##

Now I've got three small questions for you:

1. Does GobiNet work for you ? It is loaded on my computer
but I dont
know how to use it... 2. Did you success to get the GPS
working with GobiSerial
drivers ?
When I load GobiSerial, it just show ttyUSB0 (for 3G
connection which
works perfectly by the way) but no ttyUSB1 for the GPS... 3.
Any chance to get GobiSerial working with NetworkManager ?
I am
using wvdial for now...

I use Linux Mint 12 with this kernel Linux boromir
3.2.0-1-generic
x86_64 GNU/Linux (coming from precise repository)

Cheers,

-- HadiM


_________________________________________________ Mailing
list: https://launchpad.net/~sony-__vaio-z-series
<https://launchpad.net/~sony-vaio-z-series>
Post to     : sony-vaio-z-series@lists.__launchpad.net
<mailto:sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx>
<mailto:sony-vaio-z-series@__lists.launchpad.net
<mailto:sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx>>

Unsubscribe : https://launchpad.net/~sony-__vaio-z-series
<https://launchpad.net/~sony-vaio-z-series>
More help   : https://help.launchpad.net/__ListHelp
<https://help.launchpad.net/ListHelp>






-- HadiM



--
HadiM


Follow ups

References