Ok I went and bought a hardware modem like you guys had suggested and linux does not have drivers for it either. I downloaded the scanModem tool and ran it, downloaded the suggested file and changed the make files and I went to the web address that the scanModem log suggested for detailed instructions.

I did the
make
make 537
make install

And it kept refering to some intel directory that did not exist and could not write a configuration file to.

Can someone please help me on istalling this. Tell me what the make file should look like or something. I think I am about $40 past throwing Linux in the trash.

here is the modem.txt


=====================================================



DO use the following line as the email Subject Line, to alert cogent experts:
scanModem, Fedora Core release 2 (Tettnang)
Kernel kernel 2.6.5-1.358
Occassionally reponses are blocked by an Internet Provider mail filters.
So do in a day also check the Archived responses at DISCUSS@linmodems.org
Code updated on: 2005_June_24
------------ -------------- System information ------------------------
Fedora Core release 2 (Tettnang)
Kernel
on System with processor: i686
currently under kernel: 2.6.5-1.358

The kernel-2.6.5-1.358 was compiled with CONFIG_REGPARM, providing more compact and faster code.

The kernel was assembled with compiler: 3.3.3
with current System compiler GCC=3.3.3

Checking for kernel-headers needed for compiling.
The kernel-headers have base folder:
/lib/modules/2.6.5-1.358/build
Please install the package WVDIAL for modem testing and dialout.

A /dev/modem symbolic link is not set.
USB modem not detected.

00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)

Modem candidates are at PCI_buses: 02:0c.0

Providing detail for device at 02:0c.0
with vendor-ID:device-ID
----:----
Class 0780: 8086:1040 Communication controller: Intel Corp. 536EP Data Fax Modem
SubSystem 8086:1000 Intel Corp.: Unknown device 1000
Flags: bus master, medium devsel, latency 32, IRQ 5

-----PCI_IDs------- --CompilerVer-
Feature List: Primary Subsystem Distr KernelVer kernel default CPU
./scanModem test 8086:1040 8086:1000 redhat 2.6.5-1.358 3.3.3 3.3.3 i686

Use driver resource Intel-536ep-MostRecentVersion.tgz
== Checking PCI IDs through modem chip suppliers ==

Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, 537 soft modem
and AC97 and MC97 controllers managing a varierty of non-Intel soft modem Subsystems.
These subSystems often have PCI_IDs assigned by the modem assembler, rather than the chip provider.
Download available drivers through: http://developer.intel.com/design/mo...rt/drivers.htm with Intel-537 types at:
http://downloadfinder.intel.com/scri...230&page_nbr=2
Also check at: http://linmodems.technion.ac.il/packages/Intel/537/
for beta releases and perhaps Already compiled drivers for some Linux distributions
A very detailed installation report cogent to 537 type modems is at:
http://linmodems.technion.ac.il/arch.../msg00541.html
Setup call id with:
Type 1 : When the phone line is not in use at+vcid=1
Type 2 : When the phone line is already in use on a call at+pcw=0
---------------------
:
The older 2.4.n driver pair have a dependency on one other.
with result that these messages may be seen upon driver loading:
depmod****Unable to resolve symbol in 536ep.o
depmod****Unable to resolve symbol in 536epcore.o
but function is NOT affected.
Bur when the message is any longer, the drivers probably have not been properly compiled.
In which case carefully read Modem/DriverCompiling.txt

A problem maintaining CONNECT under the version 4.62 drivers was resolved
by dropping back to the 4.60 version. See:
http://linmodems.technion.ac.il/arch.../msg02127.html

The Intel-537SP-MostRecentVersion.tgz driver package may alternatively provide support.

For Debian like distros, a modified install script is:
http://members.lycos.co.uk/persianli...36_inst_debian


======= PCI_ID checking completed ======
Update=2005_June_24
A PCMCIA CardBus is not detected on this System.
GCCversion=3.3.3
The following information blocks just query some ppp support items.

====================================================
grep -rs ppp /etc/modprobe.*
-------------------------------------
/etc/modprobe.conf.dist:alias tty-ldisc-3 ppp_async
/etc/modprobe.conf.dist:alias tty-ldisc-14 ppp_synctty
/etc/modprobe.conf.dist:alias ppp-compress-18 ppp_mppe
/etc/modprobe.conf.dist:install ppp-compress-21 /bin/true
/etc/modprobe.conf.dist:alias ppp-compress-24 ppp_deflate
/etc/modprobe.conf.dist:alias ppp-compress-26 ppp_deflate
-------------------------------------
PPP support module bsd_comp.ko not found!
Resident PPP support modules are properly uncompressed .
COMM services are not active
DEVPPP=crw------- 1 root root 108, 0 Feb 23 2004 /dev/ppp
A /dev/modem symbolic link is not present

No devfsd.conf file found, indicated absense of the devfsd daemon package
for device file system (devfs) symbolic link support.

DEVFSD=
---- dmesg queries -------
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)

Beginning with Fedora 2 kernel-2.6.6-1.427, kernel-headers needed
for compiling drivers are provide at: /lib/modules/kernel-version/build/
Thus upgrading above kernel 2.6.5-1.358 to 2.6.6-* is Stongly Recommended

pppd version 2.4.2 may not be fully compatible with 2.6.8 kernel releases.
If an initial CONNECT is achieved without PPP being subsequently established,
drop back to a 2.4.1 version. This has worked for PCTEL AMR modem users,
supported by the http://www.smlink.com slmodem software.
Check pppd version with:
pppd --version
See http://linmodems.technion.ac.il/arch.../msg03167.html


For kernel-version 2.4.20-8 , a failure in automatic loading of PPP related modules
has been reported. It was necessary to manually load with:
/sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_generic
/sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_deflate
/sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_synctty
/sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_async
or dialout efforts failed.

The Internet Configuration Wizard writes a configuration file:
/etc/wvdial.conf
containing a line default line
Stupid Mode = yes
Better dialup performance may be achieved by commenting out this line as:
# Stupid Mode = yes
Also non-USA Users may need to add to the [Modem0] block:
Init2 = AT+GCI=hexadecimal_country_code
but test without it first.

redhat is not yet providing pre-compiled drivers for WinModems

====================================================

Thanks if you can help

And the name of this hardware modem is... ? You appear to have a softmodem according to the output.

Well it said hardware modem on the box.

does anyone know what the make file should look like?

It sounds like you have another winmodem in addition to the one you started out with. If you want to make sure you have a hardware modem, get a external serial modem. Don't get a USB one either. I have not yet seen or heard of a external serial modem that does not work with Linux. It is as simple as pointing to the correct device, usually /dev/ttyS0 or /dev/ttyS1 but it varies, then connecting. You may have to make the link to /dev/modem but I didn't.

If you do need to make that link, here's how:
replace the * with 0 or 1, or whichever applies. You do need to be root to do that.

Hope that helps.

It keeps saying that some autoconf.h file doesnot exist. I went through the make file and I took out all of the refrences to this file and it still keeps going to it. can someone give me a step by step on how to install this modem?

any help

I would go out and buy a serial modem, dont use any other sort of modem. dont get a USB ether. Just backing up what that other guy said. I am using my serial modem now.

I probably don't know more than you about this, but managed to get my 536EP internal modem working.

I had a similar problem, I think the issue is that the driver you have is not installing correctly. I believe the autoconf.h file should be created as part of the 'make 537' process. Changing the make script is probably not the way to go.

I found this article useful in understanding what an install process was doing, and may help. Once the install worked I could then configure kppp and it worked straight away. In my case the install was not working as the kernel source was not there.

iew3.technion.ac.il/CC/Comp_news/Mandrake_CMD_line/install-free-software-chapter.html

Hope this helps....