Newsgroup: it.comp.hardware.modem
Titolo: Diamond modem problems

I have a Diamond Supraexpress 56e voice modem that I have
been trying to use with both windows and Linux. I can set it
up and make a connection with no problem, but after a period
it hangs up on me. Under windows I had no idea what was
happening but, thanks to the logging abilities of linux I
have a few non-pointers. These are that there are no errors
of the type caused by line noise, and my pppd logfile
records what appears to me to be a normal disconnection. I
am still very much a newbie, so maybe someone can tell me if
the entry "hangup (sighup) in the pppd logfile means
anything.
This is not a pure Linux problem, as the same thing happens
when I run the same modem under W98. Intermittent
disconnections after periods of time varying between a few
seconds and over 30 minutes. I have an idea that a command
string may have been posted on the Diamond site some time
ago to correct hangup problems, but I can't find it now.
Is there anyone who can help me? I am (fortunately) not
entirely reliant on this modem as I have a 3.6 internal
winmodem as well, but I have to boot into windows to use it
and downloading Linux software onto my Windows disk is not
what I really want, especially as the Diamond is a V.90
modem.
-- 
Lesley Anna

 Wouter
Thanks for the encouragement. It is annoying having to use
my old winmodem most of the time. If things don't improve it
seems as if I'll have to get another modem. I didn't need
the external one before I started using Linux 2 months ago
and this is driving me mad. The modem in question is about 2
years old, from the days when you had to flash upgrade to
v.90.
-- 
Lesley Anna

 Lesley Anna
-- 
Lesley Anna

 > yet.
Can't check that, since my other computer (the one that modem is connected
to) has had a short circuit, so it is in for reparation :(
But I have not upgraded any firmware, and I bought it in January of this
year. Perhaps you'll be able to find out what firmware is on it...

I use nothing else than AT&F... should work...
If it doesn't, you may want to try the '+ms='-initstrings. This puts the
maximum speed lower than it originally is, so that if you connect, it wont
choose a connection speed it can't keep up...
These are the values accepted for +ms:
0: disable V90 entirely.
1: enable V90 completely (no AT-string intervention)
2: maximum speed is 28800 bps
3:    "      "    " 29333 bps
4: 30666 bps
5: 32000 bps
6: 33333 bps
7: 34666 bps
8: 36000 bps
9: 37333 bps
10:38666 bps
11:40000 bps
12:41333 bps
13:42666 bps
14:44000 bps
15:45333 bps
16:46666 bps
17:48000 bps
18:49333 bps
19:50666 bps
20:52000 bps
21:53333 bps
example: AT&F+MS=16
which means: Reset to factory defaults, and connect at maximum speed of
46666 bps
You may want to lower the maximum speed your modem will allow, so that, as I
said above, he will not try to connect at a speed he cannot keep up because
of a bad telephoneline on the way to your ISP.
If this solves the problem, contact your telephone company and ask them if
they could be so kind to test your line for problems...


 
Thank you for the init strings. I tried it out last night
and, although one session is not enough to be certain, I was
connected for over an hour without any hangups at a
reasonable speed. I was even able to download the active
newsgroup list from my ISP, for the first time ever, in krn.
I used +ms=10 with the line speed set at 57600 and I had
reasonable speeds without hangups.
--
Lesley Anna


 reasonable speeds without hangups.
Lesley ... Diamond Multimedia supplies the following init string ... and
it works like a charm via kppp with my SupraExpress 56i Sp (P/N
23540019-002)
AT&F2M0Q0E0    ( "0" = zero, not the letter "O"
DO be sure to use a serial port away from the mouse or any other serial
device. You can force this by adding the following line to the end of
the /etc/rc.d/rc.local text file (you must be root to edit this file)
setserial /dev/ttyS# irq #
look at the setserial man page for more details. That text file is read
at boot. It is the last file read at boot and will absolutely govern.
Getting a modem to work is usually the most difficult (initial)
challenge faced by a newbie. Congratulations on having this problem ...
it means everything else went well :-)
Bill