HadiM,
So doing a "modprobe GobiSerial debug=y" I get:
[ 7495.941558] USB Serial support registered for GobiSerial
[ 7495.941622] GobiSerial::GobiProbe
[ 7495.941630] GobiSerial::GobiProbe Num Interfaces = 4
[ 7495.941636] GobiSerial::GobiProbe This Interface = 0
[ 7495.941641] GobiSerial::GobiProbe Unsupported interface number
[ 7495.941674] GobiSerial::GobiProbe
[ 7495.941680] GobiSerial::GobiProbe Num Interfaces = 4
[ 7495.941685] GobiSerial::GobiProbe This Interface = 1
[ 7495.941691] GobiSerial::GobiProbe Unsupported interface number
[ 7495.941714] GobiSerial::GobiProbe
[ 7495.941719] GobiSerial::GobiProbe Num Interfaces = 4
[ 7495.941726] GobiSerial::GobiProbe This Interface = 2
[ 7495.941730] GobiSerial::GobiProbe Modem port found
[ 7495.947914] GobiSerial 1-1.4:1.2: GobiSerial converter detected
[ 7495.948847] usb 1-1.4: GobiSerial converter now attached to ttyUSB0
[ 7495.948884] GobiSerial::GobiProbe
[ 7495.948889] GobiSerial::GobiProbe Num Interfaces = 4
[ 7495.948893] GobiSerial::GobiProbe This Interface = 3
[ 7495.948896] GobiSerial::GobiProbe GPS port found
[ 7495.952101] GobiSerial 1-1.4:1.3: GobiSerial converter detected
[ 7495.952522] usb 1-1.4: GobiSerial converter now attached to ttyUSB1
[ 7495.952593] usbcore: registered new interface driver GobiSerial
[ 7495.952597] GobiSerial: 2011-07-29-1026
Not sure why yours only finds 3 Interfaces and mine finds 4...
Also, I'm sure that Vicki is correct that GobiSerial is deprecated or
maybe about to be, but I couldn't get GobiNet to work. Hopefully the
patched qcserial will work for you
Let me know.
Rob
On Mon, Nov 28, 2011 at 3:47 PM, HadiM <marelo64@xxxxxxxxx
<mailto:marelo64@xxxxxxxxx>> wrote:
So if I well understood GobiSerial is kind of deprecated and will be
replaced by GobiSerial ? What about GPS ? Can GobiNet handle GPS ?
Will we keep GobiSerial only for the GPS ?
I will try to patch qcserial to get Gobi 3000 working.
Thank for the help.
Cheers,
On 11/28/2011 08:26 PM, vick wrote:
I modified the qcserial driver to include the hardware IDs for
the gobi
3000 and the NetworkManager developers had to do a small fix to
get it
to run but it is working. There is a bigger change required to
get it to
work with GobiSerial and they are waiting on some google
developers to
get the GobiNet actually running (which is the replacement for
GobiSerial) so I don't think there's much of a chance to see
GobiSerial
supported in NetworkManager.
So just patch your qcserial module to include the gobi hardware
IDs and
use that instead of GobiSerial and make sure you have the latest
NetworkManager.
Last point: if any NetworkManager or close to NetworkManager
developer
see this: any chance to get GobiSerial working with
NetworkManager ?
_________________________________________________
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>
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
_________________________________________________
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>
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>