The device is a Compass 597 by Sierra.
I am currently using KDE 4 but can switch to GNOME if needed.
Can anyone point me in the right direction or give me steps.
Thanks
GB2715 wrote:
> The device is a Compass 597 by Sierra.
>
> I am currently using KDE 4 but can switch to GNOME if needed.
>
> Can anyone point me in the right direction or give me steps.
>
> Thanks
>
>
You should be able to set it up through Yast -> Network Devices ->
Modems. Have you given that a shot yet?
I have a friend trying to do the same thing with Verizons USB modem. He lost intrest and stopped, but he was real close.
From what we’ve gathered you need to run it through a Dialer program like KPPP.
Try doing a google search on using USB Modems with KPPP.
Heres a quick link to a discussion at ubuntus forums…
usb727 verizon wireless air card packages? - Ubuntu Forums
hope it helps,
Rob
It coudln’t be easier. I have had one for abot a year now.
Go into Yast, Software, install smpp and kinternet.
Then go into Yast network devices, select modem add.
The modem device is /dev/ttyUSB0
Select custom provider, you can call it anything you want.
Number to dial is #777, and the username and password can be absolutely anything, it does not matter as that info is already in the modem itself.
Save the settings.
Plug it in, start kinternet, right clcik the kinternet icon in the tray, select modem and dial in.
I have an AT&T sierra aircard 881U. Everything is working and linux is talking to the modem, but the #777 is not accepted. Does anyone have any idea what this should be?
The exact error from kinternet log is:
Modem initialized.
Sending ATDT8163082614
Waiting for carrier
ERROR
Invalid dial command
Disconnecting
Connect script failed
One more thing. The SierraWireless.com has instructions that include patching and recompiling the kernel. I have never done that and am a bit hesitant. If that is the only option, does anyone have any tips or directions on how to safely do that with an 11.0 / 64?
thanks,
Hi
What is in your chat script? What application are you using to
connect? I’m currently trying to get my blackberry to connect, which it
does, but times out with a LCP error sigh.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 15:51, 2 users, load average: 0.07, 0.09, 0.08
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12
What do you mean by chat script? I installed the drivers from the sierrawireless.com site. Then used the information above to use smpppd and kinternet to connect.
hopefully we can get there.
Hi
So it’s dialing the wrong number…? I use the cli (old habits die
hard) until I get things to work then look for a GUI app.
Isn’t the connection setup via YaST first, where you would add #777,
then uses smpppd/kinternet to call?
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 16:05, 1 user, load average: 0.00, 0.01, 0.03
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12
Hi
Chat scripts are the ones that talk to the modem (AT commands), then
there are the options used by pppd to create and negotiate the ppp
connections. look in /etc/chatscripts and /etc/ppp/peers for the other.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 16:54, 1 user, load average: 0.06, 0.19, 0.17
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12
Hi again
Further to above, here is mine for the blackberry 8703e
/etc/chatscripts/blackberry.chat
ABORT ERROR
SAY "Initializing Blackberry IP Modem...
"
'' ATZ
OK ATI
OK ATS0=0
SAY "Dialling .....
"
OK ATDT#777
SAY "Connecting .......
"
CONNECT
/etc/ppp/peers/blackberry
nodetach
connect "/usr/sbin/chat -f /etc/chatscripts/blackberry.chat"
noauth
defaultroute
noipdefault
nomultilink
nocrtscts
local
lock
ipcp-restart 7
ipcp-accept-local
ipcp-accept-remote
# added so not to disconnect after a few minutes
lcp-echo-interval 60
lcp-echo-failure 200
lcp-restart 50
replacedefaultroute
asyncmap 0
novj
noccp
noaccomp
nomagic
receive-all
noipx
debug debug debug
dump
kdebug 7
ktune
pty "/usr/sbin/pppob"
115200
Command to run the script;
malcolml@kermit-opensuse:~> sudo pppd call barry-cellularsouth
Initializing Blackberry IP Modem...
Dialling .....
Connecting .......
Serial connection established.
using channel 22
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
rcvd [LCP ConfReq id=0x2 <asyncmap 0x0> <auth pap> <magic 0x8cc072bb>]
.......
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 16:58, 1 user, load average: 0.12, 0.14, 0.15
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12
Oooops!!
That should be;
sudo pppd call blackberry
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 17:01, 1 user, load average: 0.06, 0.13, 0.15
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12
I originally tried the #777, but got the errors, so looked at what it was doing in windoze and grabbed the phone number from that. I will switch it back to the #777. What is that actually doing?
So then, after I get the #777 I need to look at the scripts you have above. Is that right?
thanks
Hi
Hmm if that’s the number it dials in windows, you would have to assume
that’s the one in linux? I use #777 in windows and linux. Are you sure
that wasn’t a username?
Remember I use a phone, whereas your using a card, but they are both
modems.
What you need to do in windows is query the modem in the settings and
save that information.
I would also have a look at getting a ppp trace log in windows;
start->run->cmd (to open a dos box)
netsh
> ras
> set tracing ppp enabled
> show tracing
> bye
That should produce a PPP log in windows/tracing directory
That should give you an idea of the AT commands etc to use in linux.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 14:26, 1 user, load average: 0.27, 0.20, 0.15
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12
thanks, I’ll be working on it in the next couple of days.
Hello, here’s what we found;
I have it configured with Yast, and it is talking to the modem. It needed /dev/ttyUSB2. I found that little bit on the sierra wireless site. The GSM setting call for using 99#, and the first string of at+cgdcont=1,“IP”,“ISP.CINGULAR”. It initializes the modem, sends the 99# (or #777, I tried that too) then NO CARRIER.
At least its talking! Any thoughts, how do we get it to connect?
As for the windoze ppp.log, here it is, but I can’t make much of it. Perhaps you can. I couldn’t find the script setup.
[3392] 08-21 18:59:28:044: RasCpEnumProtocolIds
[3392] 08-21 18:59:28:044: Protocol 8021
[3392] 08-21 18:59:28:044: Protocol c02b
[3392] 08-21 18:59:28:044: Protocol c029
[3392] 08-21 18:59:28:044: Protocol 80fd
[3392] 08-21 18:59:28:044: Protocol c227
[3392] 08-21 18:59:28:044: Protocol 802b
[3392] 08-21 18:59:28:044: Protocol c023
[3392] 08-21 18:59:28:044: Protocol 8029
[3392] 08-21 18:59:28:044: Protocol 8057
[3392] 08-21 18:59:28:059: RasCpEnumProtocolIds
[3392] 08-21 18:59:28:059: Protocol 8021
[3392] 08-21 18:59:28:059: Protocol c02b
[3392] 08-21 18:59:28:059: Protocol c029
[3392] 08-21 18:59:28:059: Protocol 80fd
[3392] 08-21 18:59:28:059: Protocol c227
[3392] 08-21 18:59:28:059: Protocol 802b
[3392] 08-21 18:59:28:059: Protocol c023
[3392] 08-21 18:59:28:059: Protocol 8029
[3392] 08-21 18:59:28:059: Protocol 8057
[3392] 08-21 18:59:28:059: RasCpGetInfo 8057
[3392] 08-21 18:59:28:059: RasCpGetInfo 8029
[3392] 08-21 18:59:28:059: RasCpGetInfo c023
[3392] 08-21 18:59:28:059: RasCpInit(c023, TRUE)
[3392] 08-21 18:59:28:059: RasCpGetInfo 802b
[3392] 08-21 18:59:28:059: RasCpGetInfo c227
[3392] 08-21 18:59:28:059: RasCpInit(c227, TRUE)
[3392] 08-21 18:59:28:075: RasCpGetInfo 80fd
[3392] 08-21 18:59:28:075: RasCpInit(80fd, TRUE)
[3392] 08-21 18:59:28:075: RasCpGetInfo c029
[3392] 08-21 18:59:28:075: RasCpGetInfo c02b
[3392] 08-21 18:59:28:075: RasCpInit(c02b, TRUE)
[3392] 08-21 18:59:28:075: RasCpGetInfo 8021
[3392] 08-21 18:59:28:075: RasCpInit(c223, TRUE)
[3392] 08-21 18:59:28:075: PPP Initialized successfully.
[3156] 08-21 18:59:28:075: Processing protocol event
[3156] 08-21 18:59:28:075: Processing protocol event
[3156] 08-21 18:59:28:075: Adding IP
[3156] 08-21 18:59:28:075: RasCpInit(8021, TRUE)
[3156] 08-21 18:59:28:075: Processing protocol event
[3156] 08-21 18:59:28:075: Adding IPv6
[3156] 08-21 18:59:28:075: RasCpInit(8057, TRUE)
[3156] 08-21 18:59:28:075: Processing protocol event
[3156] 08-21 18:59:28:075: Processing protocol event
[3156] 08-21 18:59:28:075: Processing protocol event
Hi
In the chat script (the one where you added the AT commands) or
your GUI thing remove the don’t dial on no carrier. I only use ABORT
ERROR and removed anything else.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 3 days 21:34, 2 users, load average: 0.15, 0.12, 0.20
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12
Hello,
Still no success. Below are more details (from sticky advice) and the kinternet log. Hopefully this will help. Thanks again in advance.
kinternet log - 08.24.08:
SuSE Meta pppd (smpppd-ifcfg), Version 1.59_SVN16 on linux-xywo.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: → WvDial: Internet dialer version 1.60
pppd[0]: → Initializing modem.
pppd[0]: → Sending: ATZ
pppd[0]: OK
pppd[0]: → Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: OK
pppd[0]: → Sending: ATM1
pppd[0]: OK
pppd[0]: → Sending: ATX3
pppd[0]: OK
pppd[0]: → Modem initialized.
pppd[0]: → Sending: ATDT99#
pppd[0]: → Waiting for carrier.
pppd[0]: ERROR
pppd[0]: → Invalid dial command.
pppd[0]: → Disconnecting at Sun Aug 24 15:13:01 2008
pppd[0]: Connect script failed
Status is: disconnected
pppd[0] died: Connect script failed (exit code 8)
++++++++++++++++++++++++++++++++++++++++++++++++++++++
sticky #2
lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 15d9:0a33
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 04f2:b057 Chicony Electronics Co., Ltd
Bus 002 Device 004: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1199:6856 Sierra Wireless, Inc.
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
++++++++++++++++++++++++++++++++++++++++++++++++++++++
sticky #3
dmesg|less
usb 1-1: New USB device found, idVendor=1199, idProduct=6856
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: AirCard
usb 1-1: Manufacturer: Sierra Wireless, Incorporated
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
usbcore: registered new interface driver hiddev
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem
input: USB Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input4
input,hidraw0: USB HID v1.10 Mouse [USB Mouse] on usb-0000:00:1d.1-1
sierra 1-1:1.0: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB0
usb 1-1: Sierra USB modem converter now attached to ttyUSB1
usb 1-1: Sierra USB modem converter now attached to ttyUSB2
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
usbcore: registered new interface driver sierra
drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.2.9c
++++++++++++++++++++++++++++++++++++++++++++++++++++++
sticky #4
/usr/sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
++++++++++++++++++++++++++++++++++++++++++++++++++++++
sticky #5
iwlist scan
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
Hi
You need to disable the “wait for dial tone” or anything like that. Is
it CDMA or GPRS connection?
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 1:31, 2 users, load average: 0.10, 0.09, 0.16
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12