Jacques,
Thanks again for your comprehensive reply, which I went through in detail.
It led to a solution! I have appended the details at the bottom of this
message
Jacques Goldberg wrote:
Steve,
I will reply point by point inline.
I will mark each reply with a symbol ===> to make it easy to notice
them.
denbigh1974@xxxxxxx wrote:
Jacques Goldberg wrote:
I just talked with Philippe Vouters to check two details.
1- It would be better if you download
http://linmodems.technion.ac.il/packages/Intel/Philippe.Vouters/intel-536EP-537EP_2009_07_07.tar.bz2
rather than 07_04 (slightly more recent). There was a typo in the
file name which had made me believe that 07_04 was younger.
2-Although the file named readme.txt does not explicitly list Ubuntu
among the systems for which automatic boot will work, it DOES work
for Ubuntu. So, when you boot after having succeeded to connect, you
just need to launch wvdial or GnomePPP or whatever you like.
Jacques
Jacques
Many thanks for your time and trouble to instruct me on installing a
new driver for the 537EP.
===> My pleasure
You are correct that the deb driver file that I originally downloaded
and installed was described as Jaunty Jackalope 9.04 Release 2
(Kernel 2.6.28-11-generic). To clarify, I did not install the
Intrepid Ibex 8.10 Release 2 (Kernel 2.6.27-7-generic) by mistake.
===> The mistake was mine, not yours. The Web page which you had
quoted indeed has several "download" buttons for rhe same subject
2.6.28-11 .... actually presenting different files - this fooled me.
That existing installed driver enables me to successfully send faxes
from Efax-gtk using Ubuntu 9.04 kernel 2.6.28-11. You asked: "do you
REALLY need a newer kernel? Can't you stick to 2.6.28.-11 until an
automatic installer for 2.6.28-15 will become available?" - I guess
you're right, I don't really need the newer kernel.
===> Fine. If however you ever change your mind on that, the material
which I sent you earlier today should let you easily install the
driver for 2.6.28-15. You understand, I am sure, that you must be
running 2.6.28-11 to use the driver that works now, while you would
need to be running 2.6.28-15 if interested in the corresponding
version of the SAME driver. It is important to understand that: if you
are running 2.6.28.11 and use the material and instructions which I
sent you, you will just rebuild version 2.6.28-11 !!
I'd appreciate your advice on the following.....
I suppose that my interest in getting GnomePPP to function properly
as well was to increase my fledgling knowledge.
===> Certainly acceptable reason!
I'd like to build the new driver as part of the learning experience
too, but I'm nervous that if I screw up then I'll lose the fax
capability.
Would I have to install the existing driver first or can I just build
the new one and happily ignore the other driver? Would it be better
to just leave things as they are for the moment?
===> To the block above.
Depends how you get organized to use version 11 or version 15.
I hope that you do not reinstall from scratch the distribution which
has 11 or the one which has 15, depending on what you want to do.
Usually, coexistence of both is obtained by having first installed
2.6.28.11 and then applied an upgrade. This way, in my system which IS
NOT UBUNTU the boot-time menu lets me select (when I upgrade I keep
both for a couple of weeks just in case). I **DO NOT KNOW** how Ubuntu
does that.
If you have both installed on your disk, you can see it by READING the
file /boot/grub/menu.lst , it shows (manages) the possibilities
available at boot.
Assuming that you have coexisting 2.6.28-11 and 2.6.28-15, doing the
job of installing a 2.6.28-15 version (having booted 2.6.28-15 for
that purpose) has no effect on what you already have for 2.6.28-11 ,
and vice versa. Kernel dependent objects are stored at different places.
To make the long story short:
-if you have no hardware which does not work with 2.6.28-11,
installing 2.6.28-15 is defiinitely excellent for education but
otherwise useless. The GnomePPP issue has nothing to do with that.
-then, installing 2.6.28-15 makes sense only if you have both versions
coexisting with selection at boot.
-booting 2.6.28-15 and installing the driver which I sent you will not
harm the driver for 2.6.28-11.
With regards to your questions:
If I start up Terminal in Ubuntu 9.04 and type
ls -l /usr/src/linux > sf-kernels.txt
the response is
ls: cannot access /usr/src/linux: No such file or directory
===> You are right. My mistake. I do not remember, obsolete anyway,
why I asked. Using my friend's Ubuntu system I see that under /usr/src
there are immediately and only the kernel headers, and this is
sufficient, I did it today, to build the Intel 537 driver coming from
Philippe Vouters.
Type
sudo ls -l /dev/modem
the response is
lrwxrwxrwx 1 root root 8 2009-10-08 15:04 /dev/modem -> /dev/537
===> OK, perfect, this is what it should be . More on this later.
I then start up GnomePPP, select /dev/modem as my device and click on
Detect. The program responds with
"No modem was found on your system"
(same thing happens when I delete the init strings and re-run Detect)
===> How do you start up GnomePPP ? From some menu or task bar I guess?
I then type in
sudo ln - sf /dev/537 /dev/modem
and the response is
ln: target `/dev/modem' is not a directory
bash: syntax error near unexpected token `newline'
===> Your mistake, this time, or perhaps again a typo on my side
The command is sudo ln -sf /dev/537 /dev/modem , not sudo ln -
sf /dev/537 /dev/modem
NOTICE, NO SPACE BETWEEN - and sf , that's all.
Linux (Unix) options to commands always start with one or two hyphens
immediately followed by letters/numbers.
Anyway this particular command is useless as we have seen before that
this link already exists and is correct by:
ls -l /dev/modem
Just to double-check, I then type in
wvdial
and the response is
--> WvDial: Internet dialer version 1.60
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT&F&D2&C1&K3S7=55
AT&F&D2&C1&K3S7=55
OK
--> Sending: AT&K3
AT&K3
OK
--> Modem initialized.
--> Sending: ATDT08450792829
--> Waiting for carrier.
ATDT08450792829
and then the modem successfully rings that number 0845 0792829.
I should add that I had to edit wvdial's configuration file BY HAND
to get it to work.
==> Yes, of course (usually only your username, password, and the
phone number to be dialled).
I also tried (from the URL
https://bugs.launchpad.net/ubuntu/+source/gnome-ppp/+bug/384060)
sudo gnome-ppp
responds with
WVCONF: /root/.wvdial.conf
and Gnome PPP starts.
===> That one is strange but this may be yet an Ubuntu change to
standard operation.
Again, not knowing Ubuntu, I have just read
http://www.ubuntugeek.com/setting-up-dial-up-connection-in-ubuntu.html
and I would like to ask:
Have you tried to just close the modem setup window without clicking
on "Detect" ?
The reason I ask is that your log shows wvdialconf (which runs in the
back of gnome-ppp) trying standard ports such as ttyS0 etc... BUT NOT
/dev/modem AS IT SHOULD! Thus possibly the Ubuntu "Sages" have set
/dev/modem as default and have given you the possibility to select
something else, rejecting /dev/modem/ via the "Detect" button.
If I had an Ubuntu box I would "die" to know this: before starting
gnome-ppp , once for all I would type the command sudo ln -sf
/dev/537 /dev/ttyS537 and then start gnome-ppp and press Detect.
My bet would be that it will report a modem named ttyS537 and start
to work.
But this is wild guessing.
Simpler to try, again, do NOT press detect ...
Humbly, to further debug this problem I would need to work hands on.
When I click on Detect in Gnome PPP, the terminal responds with
GNOME PPP: STDOUT: Editing `/dev/null'.
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Scanning your serial ports for a modem.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud,
next try: 9600 baud
GNOME PPP: STDERR: ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud,
next try: 115200 baud
GNOME PPP: STDERR: ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDERR: ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud,
next try: 9600 baud
GNOME PPP: STDERR: ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud,
next try: 115200 baud
GNOME PPP: STDERR: ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDERR: ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud,
next try: 9600 baud
GNOME PPP: STDERR: ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud,
next try: 115200 baud
GNOME PPP: STDERR: ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDERR: ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud,
next try: 9600 baud
GNOME PPP: STDERR: ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud,
next try: 115200 baud
GNOME PPP: STDERR: ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDOUT:
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Sorry, no modem was detected! Is it in use by
another program?
GNOME PPP: STDOUT: Did you configure it properly with setserial?
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Please read the FAQ at
http://open.nit.ca/wiki/?WvDial
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: If you still have problems, send mail to
<wvdial-list@xxxxxxxxxxxx>.
>From Mr. Stodolsky's suggestion at
http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:35037:200910:djeohfecbakobbongfdp
===> Look here !!!! You can see that gnome-ppp has set the modem to
/dev/modem by default. When you hit Detect it does NOT try to detect
if /dev/modem is there, because it has already found it (at least,
the link).
Type
cat .wvdial.conf
responds with
[Dialer Defaults]
Modem = /dev/modem
ISDN = off
Modem Type = Analog Modem
Baud = 14400
Init = ATZ
Init2 = ATZ
Init3 =
Init4 =
Init5 = AT&K3
Init6 =
Init7 =
Init8 =
Init9 =
Phone = 494471
Phone1 =
Phone2 =
Phone3 =
Phone4 =
Dial Prefix =
Dial Attempts = 1
Dial Command = ATM1L3DT
Ask Password = on
Password =
Username = steve
Auto Reconnect = off
Abort on Busy = off
Carrier Check = on
Check Def Route = on
Abort on No Dialtone = on
Stupid Mode = on
Idle Seconds = 0
Auto DNS = on
;Minimize = off
;Dock = off
;Do NOT edit this file by hand!
====> EXACT, NEVER edit this file, it is ready to go! If something
needs to be adjusted, use the SETUP menu in gnome-ppp
If wvdial and Gnome-PPP use different configuation files, maybe I
should try editing .wvdial.conf related to Gnome-PPP?
===> NO WAY
I'm not really sure how to. It says 'Do NOT edit this file by hand!'
at the end there.
For completeness, I am attaching my ModemData.txt file.
Thanks again for your guidance. I'm enjoying the challenge of this
new operating system.
Steve
Keep up Steve, you are two fingers away from success.
Jacques
TEST TO DETECT 537EP MODEM:
Open up Terminal in Ubuntu 9.04
Type in
sudo ln -sf /dev/537 /dev/ttyS537
Type in
ls -l /dev/*537*
Response is
crw-rw-rw- 1 root dialout 240, 1 2009-10-09 19:16 /dev/537
crw-rw---- 1 root root 240, 1 2009-10-09 19:01 /dev/5370
lrwxrwxrwx 1 root root 8 2009-10-09 19:21 /dev/ttyS537 -> /dev/537
Type in
sudo gnome-ppp
Terminal responds with
WVCONF: /root/.wvdial.conf
and the graphical interface for Gnome PPP starts up.
Click on Setup
For Device, enter /dev/ttyS537
(Change Init Strings if desired)
Click on Detect
Terminal responds with
GNOME PPP: STDOUT: Editing `/dev/null'.
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Scanning your serial ports for a modem.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next
try: 9600 baud
GNOME PPP: STDERR: ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next
try: 115200 baud
GNOME PPP: STDERR: ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDERR: ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next
try: 9600 baud
GNOME PPP: STDERR: ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next
try: 115200 baud
GNOME PPP: STDERR: ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDERR: ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next
try: 9600 baud
GNOME PPP: STDERR: ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next
try: 115200 baud
GNOME PPP: STDERR: ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDERR: ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next
try: 9600 baud
GNOME PPP: STDERR: ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next
try: 115200 baud
GNOME PPP: STDERR: ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 -- failed with 2400 baud,
next try: 9600 baud
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 -- OK
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 Z -- OK
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 S0=0 -- OK
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
GNOME PPP: STDERR: ttyS537<*1>: Modem Identifier: ATI -- OK
GNOME PPP: STDERR: ttyS537<*1>: Speed 19200: AT -- OK
GNOME PPP: STDERR: ttyS537<*1>: Speed 38400: AT -- OK
GNOME PPP: STDERR: ttyS537<*1>: Speed 57600: AT -- OK
GNOME PPP: STDERR: ttyS537<*1>: Speed 115200: AT -- OK
GNOME PPP: STDERR: ttyS537<*1>: Speed 230400: AT -- OK
GNOME PPP: STDERR: ttyS537<*1>: Speed 460800: AT -- OK
GNOME PPP: STDERR: ttyS537<*1>: Max speed is 460800; that should be safe.
GNOME PPP: STDERR: ttyS537<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Found a modem on /dev/ttyS537.
GNOME PPP: STDERR: ttyS537<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0
&C1 &D2 +FCLASS=0"
GNOME PPP: STDOUT: Modem configuration written to /dev/null.
Excellent - the modem has been detected!
That's terrific. Thank you very much.
