Sierra Wireless Compass 597 problem

Hello!

I’ve successfully set up CDMA USB modem Sierra Wireless Compass 597 with SuSE 11.1 on Compaq 6710b and everything works fine until transfer speed reaches 20KB/s or more. Then desktop freezes until notebook is powered off.
Hardware is OK, because the same modem on the same notebook works fine under Win Vista. Switching kernels 2.6.27-2.6.30 (with and without PAE) has no effect.

Anyone saw something like that?

siy adjusted his/her AFDB on Thursday 23 Jul 2009 20:06 to write:

>
> Hello!
>
> I’ve successfully set up CDMA USB modem Sierra Wireless Compass 597
> with SuSE 11.1 on Compaq 6710b and everything works fine until transfer
> speed reaches 20KB/s or more. Then desktop freezes until notebook is
> powered off.
> Hardware is OK, because the same modem on the same notebook works fine
> under Win Vista. Switching kernels 2.6.27-2.6.30 (with and without PAE)
> has no effect.
>
> Anyone saw something like that?
>
>

Any errors reported in any of the log files in /var/log ( messages, warn )

Have you tried having top running in a console while this is happening to
see if you can see if anything is eating you CPU or your memory?

Or you could run ksysguard and watch that ( bit prettier I suppose ) start
it by pressing Ctrl+Esc.

HTH


Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

No error messages. Desktop just freezes, even mouse cursor stops moving. No CPU consumption or any other sign of problem. And there is no reaction on any key combinations such as Ctrl+Esc, Alt+Backspace, etc.

General impression is that interrupts are disabled and not enabled until system is not powered off. From the other hand, power off button works (although after very long press)…

siy adjusted his/her AFDB on Thursday 23 Jul 2009 21:36 to write:

>
> baskitcaise;2016584 Wrote:
>>
>> Any errors reported in any of the log files in /var/log ( messages,
>> warn )
>>
>> Have you tried having top running in a console while this is happening
>> to
>> see if you can see if anything is eating you CPU or your memory?
>>
>> Or you could run ksysguard and watch that ( bit prettier I suppose )
>> start
>> it by pressing Ctrl+Esc.
>
> No error messages. Desktop just freezes, even mouse cursor stops
> moving. No CPU consumption or any other sign of problem. And there is no
> reaction on any key combinations such as Ctrl+Esc, Alt+Backspace, etc.
>
> General impression is that interrupts are disabled and not enabled
> until system is not powered off. From the other hand, power off button
> works (although after very long press)…
>
>

Must admit I am not experienced with that hardware but one thing you could
try is to enable the SysRq key sequence in the kernel by going to
YaST>System>sysconfig editor an then search for SysRq and enable it.

At least this might get you out of a hole if the kernel is not totally
b0rked, have a look here:

http://en.wikipedia.org/wiki/Magic_SysRq_key

Have a look down the page for the “raising elephants” section

At least it might stop you having to sit through a disk scan and the
possibility of data loss, also might write out some errors to a log file if
you are extremely lucky.

HTH


Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

Thanks, I’ll try it.

Unfortunately, SysReq also does not work. I’ve enabled all options in the sysconfig, but this didn’t help. Also, I’ve noticed that when system hangs, notebook turns on a signal at the sensor panel between “presentation” button and “mute” button. This signal looks like a tiny lock with letter “A”. Strangely enough that I found no mentioning of this signal in the manual.

Update: this LED is just a CapLock signal. And it was definitely off before system hang.

siy adjusted his/her AFDB on Friday 24 Jul 2009 10:36 to write:

>
> Unfortunately, SysReq also does not work. I’ve enabled all options in
> the sysconfig, but this didn’t help. Also, I’ve noticed that when system
> hangs, notebook turns on a signal at the sensor panel between
> “presentation” button and “mute” button. This signal looks like a tiny
> lock with letter “A”. Strangely enough that I found no mentioning of
> this signal in the manual.
>
>

Yeah the led lights for num-lock, caps-lock and scroll lock are indications
of a kernel panic, I cannot find the right docs to tell you what each mean
at the moment.

If the SysRq does not work then it means it is a real bad kernel
panic/crash.

If the modem is not connected does the machine run OK?

I will try and find out some more info on that hardware and let you know if
there is anything that can be done to cure the error.


Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

baskitcaise adjusted his/her AFDB on Friday 24 Jul 2009 15:06 to write:

> will try and find out some more info on that hardware and let you know
> if there is anything that can be done to cure the error.
>
>

Have had a gurgle search and found a bit of info on your modem.

What driver version are you using?

Try

modinfo sierra

if it is earlier than

v.1.3.1.b

Which is for the 2.6.27 kernel

Then here is the site with newer drivers for your card ( I think, I just did
a quick look ) there are also ppp scripts and instructions on there on how
to install.

http://www.dc425.org/sierralinux

HTH


Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

baskitcaise adjusted his/her AFDB on Friday 24 Jul 2009 15:27 to write:

> Have had a gurgle search and found a bit of info on your modem.
>
> What driver version are you using?
>
> Try
>
> modinfo sierra
>
> if it is earlier than
>
> v.1.3.1.b
>
> Which is for the 2.6.27 kernel
>
> Then here is the site with newer drivers for your card ( I think, I just
> did a quick look ) there are also ppp scripts and instructions on there on
> how to install.
>
> http://www.dc425.org/sierralinux
>
> HTH
>

Addendum, have just tried the modinfo sierra here on a 64bit 2.6.27 kernel
( latest version after update earlier this week ) and the supplied module is
definitely an earlier version

version: v.1.3.2

So you might give the later one a go it might fix or f… it.

:slight_smile:

HTH


Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

Yes, it works just fine with connected modem. Hang happens only when some significant amount (10+ KB) of data is received from modem.

Initially I’ve encountered problem with 2.6.30 kernel, and then tried 2.6.27. Result is the same with both kernels. At present I have installed 2.6.30 with sierra driver 1.3.3. I guess this is the latest one.

Also, I think that it is also possible that problem is related to USB driver.

Sorry, I did mean that everything works fine even with the connected modem.

I’ve replaced Sierra Compass 597 modem with Novatel Wireless Ovation U720 and now everything works just fine. This message I’m writing from the notebook connected to Internet via this modem.

siy adjusted his/her AFDB on Tuesday 28 Jul 2009 15:06 to write:

>
> I’ve replaced Sierra Compass 597 modem with Novatel Wireless Ovation
> U720 and now everything works just fine. This message I’m writing from
> the notebook connected to Internet via this modem.
>
>

Glad you got it sorted,

I have been away till now so sorry I did not reply earlier.


Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum