[ubuntu] Dial up problems with Intel FA82537EP

[ryan mckeown]

Hey.
Ok so heres the problem I'm faced with:

A few weeks ago I received the Ubuntu 9.04 (Jaunty Jackelope) CD and I installed it alongside my Windows XP OS on my Dell Dimension 3000. I think I'm right in saying that Ubuntu 9.04 has the kernal 2.6.28-11 (whether thats important or not is beyond me). Anyway I installed it with sucess and was quite happy until I decided to try to get online. I looked up the installed manual (System > Help and Support) and it said that "NetworkManager manages wired, wireless, mobile broadband, vpn and dsl connections. It does not currently support dialup modem connections but there is help available in Chapter 6 ― Modems". So I went to chapter 6.1 titled "Identifying your modem" and from the instructions there, I downloaded scanModem from http://linmodems.technion.ac.il/packages/scanModem.gz (under Windows XP) and followed the rest of the instructions to open "ModemData.txt". ModemData.txt contains the following information:

 Only plain text email is forwarded by the  Discuss@Linmodems.org List Server,
 as HTML can contain viruses. Use as the email Subject Line:
           YourName, YourCountry  kernel 2.6.28-11-generic 
 With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
 YourCountry will enable Country specific guidance. Linux experts in YourCountry 
 can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be essential for dialup service.
Responses from Discuss@Linmodems.org are sometimes blocked by an Internet Provider mail filters.
 So in a day, also check the Archived responses at http://www.linmodems.org 
--------------------------  System information ----------------------------
CPU=i686,  
Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
 scanModem update of:  2009_05_12

 There are no blacklisted modem drivers in /etc/modprobe*  files 
 Potentially useful modem drivers now loaded are:
                

Attached USB devices are:
 ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
 ID 04f2:a13e Chicony Electronics Co., Ltd 
 ID 0bda:0111 Realtek Semiconductor Corp. Card Reader
 ID 0ea0:2168 Ours Technology, Inc. Transcend JetFlash 2.0 / Astone USB Drive
 ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
 ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever
 ID 413c:5008 Dell Computer Corp. 
 ID 08ca:0021 Aiptek International, Inc. APT-2 Tablet
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html

If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@linmodems.org

For candidate card in slot 01:01.0, firmware information and bootup diagnostics are:
 PCI slot    PCI ID        SubsystemID    Name
 ----------    ---------    ---------    --------------
 01:01.0    8086:1080    1028:1000    Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI 

 Modem interrupt assignment and sharing: 
 --- Bootup diagnostics for card in PCI slot 01:01.0 ----
[    0.678108] pci 0000:01:01.0: reg 10 32bit mmio: [0xfeafe000-0xfeafefff]
[    0.678115] pci 0000:01:01.0: reg 14 io port: [0xde00-0xdeff]
[    0.678152] pci 0000:01:01.0: PME# supported from D0 D3hot D3cold
[    0.678156] pci 0000:01:01.0: PME# disabled
[    1.979232] serial 0000:01:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[    1.979345] 0000:01:01.0: ttyS1 at I/O 0xde08 (irq = 22) is a 16450
[    1.979420] 0000:01:01.0: ttyS2 at I/O 0xde10 (irq = 22) is a 8250
[    1.979494] 0000:01:01.0: ttyS3 at I/O 0xde18 (irq = 22) is a 16450
[    1.979519] Couldn't register serial port 0000:01:01.0: -28

 The PCI slot 01:01.0 of the modem card may be disabled early in 
 a bootup process,  but then enabled later. If modem drivers load 
 but the  modem is not responsive, read DOCs/Bootup.txt about possible fixes.
 Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
 if help is needed.
 

=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive  diagnostics for card in bus 01:01.0:
    Modem chipset  detected on
NAME="Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI "
CLASS=0703
PCIDEV=8086:1080
SUBSYS=1028:1000
IRQ=22
IDENT=INTEL537EP

 For candidate modem in:  01:01.0
   0703 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI 
      Primary device ID:  8086:1080
 Support type needed or chipset:    INTEL537EP
 


 Since 2006, Intel appears to have ceased its modem code updates for Linux.
 The outdated official Intel support packages can be accessed through:
       http://developer.intel.com/design/modems/support/drivers.htm
 Beneficially, Philippe Vouters has been provided updates as the Linux kernel evolves.
 But intensive personal support is not feasible, see:  http://archives.linmodems.org/24939
 The code for the INTEL537 and INTEL536 chipset modems is at
       http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/

 For Ubuntu Linux users with Intel 536 and 537 chipsets, there are driver 
 installation packages available thru http://groups.google.com/group/ubuntu-modems

 Read DOCs/Intel.txt and Modem/DOCs/YourSystem.txt for follow through guidance.


Writing DOCs/Intel.txt

 Completed candidate modem analyses.

 The base of the UDEV device file system is: /dev/.udev

 Versions adequately match for the compiler installed: 4.3.3
             and the compiler used in kernel assembly: 4.3.3

 The patch utility is needed and is needed for compiling ALSA drivers, and possibly others. 

 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.3
   linuc_headers base folder /lib/modules/2.6.28-11-generic/build

 However some compilations and executable functions may need additional files,
 in the FileNames.h (so called kernel "h"eaders) collection installed in  /usr/include/ .
 For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default. 
 Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
 In not included on your install CD, search for them at http://packages.ubuntu.com
 or comparable Repository for other Linux distros.
 When compiling ALSA drivers, the utility "patch" will also be needed.




If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev

If an alternate ethernet connection is available,
$  apt-get update
$  apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:

Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb


Checking pppd properties:
    -rwsr-xr-- 1 root dip 277352 2009-02-20 17:25 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:
    http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html

To enable dialout without Root permission do:
    $ su - root  (not for Ubuntu)
        sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
    sudo chmod a+x /usr/sbin/pppd

Checking settings of:    /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx

In case of a message like:
   Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html

Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.

 Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================

 Checking for modem support lines:
 --------------------------------------
     /device/modem symbolic link:   
slmodemd created symbolic link /dev/ttySL0:  
     Within /etc/udev/ files:

     Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
     Within any ancient /etc/devfs files:

     Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

I also went to the link at the bottom of the page (also under XP): https://help.ubuntu.com/community/DialupModemHowto and I found that installing a dial-up modem should be as simple as:
1. Indentify the modem
2. Download a driver for your modem or buy a more suited modem
3. Configure the connection to your ISP

Seemed staight forward enough. I already had identified my modem using scanModem and its a: Intel Coroperation FA82 537EP 56k V.92 DATA/FAX MODEM found on the PCI. I also know its in (windows settings) COM3.
So then I proceeded and clicked on the link "Setup Intel537EP driver" (https://help.ubuntu.com/community/Di...wto/Intel537EP) and found that the driver was "pre-packaged" for new users (me!) into a .deb file. So I downloaded it and ran it with aparant sucess in Ubuntu.
Therefore, I continued to the third stage, I downloaded gnome-ppp (I heard it was good from threads I read and I found a useful page: https://help.ubuntu.com/community/Di...etUpDialer.htm which gave me instructions as to how to install and run gnome-ppp) along with the dependancies it needed and ran it. I added myself to the dip and dialout groups, configured gnome-ppp and tried to dial. However, when I click "dial" the message appears "sending password" and it stays like that until the thing times out. I then decided to use wvdialconf to see if it detected my modem and it said it didn't.
I've tried loads of things since then and got nowhere. I found out that my modem has a Ambient MD3200 chipset and that Intel's support for the driver has all but ran out. Intel is actually telling me to try to contact the manufacturer because aparently Intel never actually manufactured the product themselves, they just put their name on it. I also learnt that Intel was formerly Ambient which was formerly Cirrus Logic. Aparently too there was a driver released for linux for my modem back in about 2002 but I can't seem to find it anywhere.

My ISP is Tiscali and I know the phone number to dial, the username and I have a fair idea of what my password is to use. I also know that the DNS address is determined on connection and the ISP uses PPP transfer methods.

Can anyone shed light on my gloomy situation? I've been trying everything I can for days now and constantly switching between OS is fustrating. Can you tell me how to get my modem to work or am I just better off buying a new one (if so do you have any suggestions, I don't want anything too expensive as I will be getting broadband in the new house we are building (in about 6-8 months)).

Also can you please explain everthing in lots of detail because, even though I have some experience in programming under Windows, Linux is still very new to me and hardware wouldn't really be my strong point either.

Thanks
Ryan

[jonobr]

Hello

Im not sure i can help you much and it sounds as if you have been very methodical on your approach to getting this working

It seems from your post the closest you came is when you got the password authentication mechanism phase.
Im wondering if trying that approach again may show something in the logs.

You should usually have a related log which shows what is happening on that interface.

I believe it may be /var/log/ppp something, if try again andyou post it here it may yield some fruit.

What I will tell you is that in order to start a PPP connection- which passes the packetised data between you and the networks,
the modems at both ends must train, and connect.
At that point you would go into the two phases of PPP negotiation,
LCP, and IPCP,
I cant recall which one comes first, I think its LCP and the second one, I think its IPCP exchanges config information and password negotiation.

It appears your training, LCP and part of your IPCP may be working, however, something is wrong with you IPCP negotiation or client config which may be causing this issue.

Im hoping the results of the log may provide a hint as to what that may be.

[Mark_in_Hollywood]

Look here:

http://www.ubuntugeek.com/setting-up...in-ubuntu.html

if this doesn't work, drop me a private message and I'll try to help.

[jonobr]

THis is a good resource

Thanks!!

[ryan mckeown]

Thanks for your help so far guys.

There is no file called /var/log/ppp but there is a fille called /var/log/ppp-connect-erros which is empty.
However, when I try to connect using gnome-ppp and I click the log button (while it's stuck with the "Sending password"

message) the following appears:

--> Ignoring malformed input line: ";Do NOT edit this file by hand!"
--> WvDial: Internet dialer version 1.55
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Please enter password (or empty password to stop):

Also, if I try to connect using gnome-ppp once the message "Sending password" stays on screen but when I try to connect a

second time the message "Can not open modem" appears on screen.

I went to http://www.ubuntugeek.com/setting-up...in-ubuntu.html and I have no program in the menu System > Administration > Networking and I cannot get it by choosng which

programs to be displayed and in what menus. I tried making a connection using pppconfig and when I enter:

pon

The message "The file /etc/ppp/peers/provider does not exist. Please create it or use a command line arguement to use

another file in the etc/ppp/peers/ directory." appears even though I made my connection to be called provider.

I have already discussed what happens when I use gnome-ppp.


Can you please advise as to what to do next...
Ryan

[Mark_in_Hollywood]

Ryan, sorry to take so long to get back to you. Try this, if you haven't already:

Open a terminal. Applications/Accessories/Terminal.

please try

sudo wvdialconf

and post the output here. That will tell us if wvdial can access your modem.

After that, if you get a message with wording like:

Found one modem bla blah blahh at /etc/ttys0

then:

sudo /etc/wvdial.conf

you will get a text file with only a few lines in it.

Remove the

;

from in front of the user name / password / telephone and put those lines in this order

phone number to dial
username (or maybe it's called user ID - I forget)
password

save this file.

Open a tab in the terminal and type

wvdial

it should dial the phone and get you on the net.

[longtom]

I have had similar problems and had some extremely competent help from some awsome folks on this board.

Here is the thread:

http://ubuntuforums.org/showthread.php?t=1100310

Good luck

[ryan mckeown]

Hey no problem Mark_in_Hollywood, I've been away for a while too.

Ok, I opened a terminal and entered sudo wvdial.conf and the following appeared:

Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.


Sorry, no modem was detected!  Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <wvdial-list@lists.nit.ca>.

I guess that means that wvdial doesn't reconise my modem (as I mentioned in my original post...)

I then decided to use wvdialconf to see if it detected my modem and it said it didn't.

So do I need to see if I can find a driver (I tried already, see original post.)?


Thanks too to longtom, after reading your thread, maybe I should contact this Mervin guy (at the linemodems discussion group) and see what he has to say about the whole thing.

Please advise...
Ryan

[lkraemer]

Another suggestion is to look on ebay for an External US Robotics
Hardware Modem. These work well with wvdial/Linux, and instead of trying
for 3-4 days to get a Driver working you can be online in about 30
minutes.

Good Luck.

lkraemer

[ryan mckeown]

Thanks for your comments.

lkraemer, I have conidered buying a new modem. Can anyone suggest a good one which is not too expensive and works straight from the box with ubuntu?

Otherwise, I am currently checking my emails from discuss@linmodems.org. I will update the post if I find anything interesting...


Ryan