Adrian,
Not having found Nework Manager to be reliable with winmodems. I don't use it.
Just use wvdial instead. It is much more transparent. Once the driver
is loaded:
$ sudo wvdialconf /etc/wvdial.conf
to assess if the modem is detected. If so edit with
$ sudo gedit /etc/wvdial.conf
and dialout with:
$ sudo wvdial
MarvS
On 3/9/07, adrian GREEMAN <adriangreeman@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I reloaded with the newest driver as you recommend (the March07 one?)
[incidentally this was with a reinstall of Xubuntu I did for other reasons
In case I need to do it again - I don't know how to uninstall a driver).
So - this gave the same result with gnomeppp.
Then I looked at the dev folder and worked out it is called /dev/536ep0 in
the file and there is not a /dev/modem. Entered this in gnomeppp but still
nothing.
But now it gets a bit odd. I tried Network Manager and entered /dev/536ep0
for the "port" setting which before I had entered /dev/modem.
Nothing seemed to happen though it was "enabled" (is there anyway in Network
Manager to know when you are connected?
But then I went back to gnomeppp and entered all the details again and tried
the "connect" button. Lo, all the noises started on the modem and it did its
dialling stuff. (Why it needed the Network Manager entry first is puzzling
but it seemed to be what did the trick)
Then I followed the gnomeppp log and it shows that it connects. I get
something like this (apologies I don't know how to copy the output from the
prompt line or logs exactly - it is probably very simple but my Linux is
basic). Anyway:
"Modem initialized
Connect 37333"
The line
ATMIL3DTXXXXXXXXXX (XXX is my dial-up number)
appears.
Then
"carrier detected:waiting for prompt
Connect but carrier signal lost."
This repeats over and over. The number is correct.
I disabled the wifi card while doing all this.
So now I tried wvdialconfig on the command line as you recommended.
wvdial tests ptty0 and ptty1 at various speeds and then reports that "sorry
it cannot find a modem".
But clearly gnomeppp does get the modem going.
It is tantalisingly close. I really want it to work and also to understand
how it gets there (in case I need to do it on another computer which also
has a 536ep0.)
It must be something to do with configurations??
I have not set the country (UK) and am unsure how to do that - is it
important or a possible reason?
And somewhere I read about modem being set on stupid mode (or not) which I
do not understand - is this a possible reason?
Many thanks for your previous reply which was:
Adrian
For
CPU=i686, Ubuntu 6.10
Linux version 2.6.17-10-generic
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:0e.0 8086:1040 8086:1000 Communication controller: Intel
Corporation 536EP Data Fax Modem
Did you use the most current support is provided at:
http://phep2.technion.ac.il/linmodems/packages/intel/Philippe.Vouters/
??
If not you should uninstall the current support and use the current package.
If you did use the most current package.
1) check that the driver does load
Gnome-ppp doesn't do well with winmodems sometimes. SO do a first test:
$ sudo wvdialconf /etc/wvdial.conf
to assess if the modem is detected. If so edit with
$ sudo gedit /etc/wvdial.conf
and dialout with:
$ sudo wvdial
MarvS
scanModem maintainer
Regards
Adrian Greeman
