dear all,
what happened u guys,
i was waiting for your help but upto now no one help me on this topic
and on this group.
ok here are the ansmer i got from linmodem forum,
i am posting this because if someone encounter this kind of problem and
need help then may be this will:
--
There is a display bug in your scanModem Nov1 release, now fixed.
For
PCI ID SubsystemID Name
---------- --------- --------- --------------
e159:0001 8086:0003 Communication
You should have been directed to:
from
http://linmodems.technion.ac.il/pack...ilippe.Vouters
get the
intel-537EP_secure-2.60.80.1_21_09_2006.tgz, 24-Oct-2006 21:21 1.5M
MarvS
scanModem maintainer
....
intel read me.
Intel claiming partial source and providing binaries built on a 32-bit
Pentium aware computer, you may use the drivers ONLY on a 32-bit Linux
and a Pentium instruction set compatible processor.
The driver code also handles a SMP configuration, as found in modern
multi-core processors, such as the Opteron and Xeon processors.
</NOTICE>
1/ 536EP and 537EP installation:
First read the readme.txt file located in the detar'ed created
directory.
Make sure your computer has all the prerequisites (kernel-devel rpm
installed
in particuliar) and your /usr/src/kernels/'uname
-r'/include/linux/autoconf.h
does match your processor configuration. With this, check especially
for:
$ grep SMP /usr/src/kernels/'uname -r'/include/linux/autoconf.h
for CONFIG_SMP defined whereas your computer only contains a single
processor.
If you have such a mismatch, reinstall your Linux distribution from
scratch.
2/ From any account, you can under the detar'ed created directory:
$ make clean
$ make 536
or
$ make 537
For a 537 family modem, you may have to
$ export MODEM_TYPE=<your actual modem type>
prior to the $ make 537
3/ Only from a root account, you can
$ make install
or
$ make uninstall
Check with:
$ dmesg
for any driver's run-time problem.
The 536EP driver has proved to work fine with efax, hylafax, wvdial,
KPPP.
The 537 driver has proved to work fine on SuSE 10.1.
4/ Checking the installation.
Assuming you have a 536EP modem, you should see the following:
$ ls -l /dev/modem
lrwxrwxrwx 1 root root 10 jan 22 12:37 /dev/modem -> /dev/536ep
$ ls -l /dev/536*
crw-rw-rw- 1 root root 240, 1 jan 22 13:08 /dev/536ep
crw-rw---- 1 root root 240, 1 jan 22 13:08 /dev/536ep0
With such /dev/536ep protection modes, your modem is ready for use by
software
from any account. Such software includes efax.
Your modem being connected to a phone line, it is advised to perform
the
following quick and simple check:
$ efax -v ewinchmart
wait for efax waiting for a phone call. Then abort it with CTRL-C.
Check that driver is properly working with:
$ dmesg
5/ Testing the modem for an Internet connection with wvdial:
from a root account, gedit /etc/wvdial.conf containing information such
as:
[Modem0]
Modem = /dev/modem
Baud = 115200
SetVolume = 3
Dial Command = ATDT
Init1 = ATZ
Init2 = AT+GCI=3D
Init3 = ATM1L3
Carrier Check = no
FlowControl = CRTSCTS
#Stupid Mode = yes
[Dialer tiscali]
Username = <your ISP provided user name>
Password = <your ISP provided password>
Phone = <your ISP phone number>
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Inherits = Modem0
tiscali is my Internet provider. You may replace the string [Dialer
tiscali] by
[Dialer <your provider name>].
Do not attempt to set the Baud rate to a value greater than 115,200
bps.
Stressing TCP/IP performance tests have shown that you will not get
more
overall performance, and you may cause the modem driver to lock your
computer,
forcing you to power down it.
Still from a root account, test the Internet connection with the
command:
$ wvdial <the provider Dialer name> &
Check if the modem correctly dials.
Check if the ppp daemon is correctly synchronizing and authenticates
you with
no problem.
Providing the ppp daemon does not work correctly, then
$ kill 1%
to abort wvdial. If ppp daemon is not working properly, you might
remove in the
proposed /etc/wvdial.conf file the comment on the line:
#Stupid Mode = yes
and restart
$ wvdial <the provider Dialer name> &
Check using an Internet browser, such as Firefox, that you can display
pages
from the Web.
kill the wvdial program with the command:
$ kill %1
6/ Configuring with KPPP.
KPPP on Fedora Core 4 Gnome desktop can be configured clicking on
Applications->Internet->KPPP and clicking on Configure and New.
Enter the data relative to your Internet account.
For configuring the modem, in the peripheral tab:
Enter your string as the modem name.
As the peripheral device, select in the listbox /dev/modem.
For flow control, select hardware [CRTSCTS]
End of line CR/LF
Connection speed 115200.
Do not use a lock file and select the modem response delay to 120
secondes
(maximum). Unselect "wait tone before dialing" and set "active wait" to
50 secondes.
In the modem tab, clicking on modem commands, I set my 536EP modem to
the
following:
Pre-initialization delay: 100
Init String 1: ATZ
Init String 2 : <empty>
Post-initialization delay : 156
Dialing speed : 100
Response after initialization: OK
No tone detection : ATX3
Dialing string : ATDT
"Connected" Response: CONNECT
Busy Response: BUSY
No Carrier Response: NO CARRIER
No tone response: NO DIALTONE
Hangup command: +++ATH
Hangup response: OK
Modem query command: ATA
Ring response: RING
Response "Response": CONNECT
DLP response: DIGITAL LINE DETECTED
Escape string: +++
Escape response: OK
Guard time: 255
Mute/low/high volume: M0L0 M1L1 M1L3
If you freshly installed the modem and with KPPP you interrogate it, it
might
happen the modem does not answer ATI commands the first time. Retrying
once
again, makes the modem answer.
---
regards.
electrogeni wrote:
> dear all.
> i got luckly the RHEL4ES,but having some problems regarding modem.
> help me finding the proper driver and installation.!
> i have RHEL4ES,and trying to find proper driver and installation of
> that driver,
> i have the winmodem intel537,its works fine with windowsXP,i always
> updated my modem driver from automatics configuration tool from
> microsoft to install the drivers,
> so i find the one tool to first how recognises the modem so proceeded
> to the next step,
> so i downloaded the scantool from
> http://linmodems.technion.ac.il/packages/scanModem.gz
> and run it under RHEL4ES ,and the results are as under:
> ModemData.txt
> Red Hat Enterprise Linux ES release 4 (Nahant)
> Kernel
> Linux version 2.6.9-5.EL ((E-Mail Removed)) (gcc
> version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)) #1 Wed Jan 5 19:22:18 EST
> 2005
> scanModem update of: 2006_November_01
>
>
> USB modem not detected by lsusb
>
> Modem or host audio card candidates have firmware information:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:1b.0 8086:27d8 8086:0202 Class 0403: Intel Corp.: Unknown device
> 27d8
>
> Modem interrupt assignment and sharing:
> 11: 12 XT-PIC uhci_hcd, uhci_hcd, uhci_hcd
>
> --- Bootup diagnositcs for card in PCI slot 00:1b.0 ----
> ACPI: PCI interrupt 0000:00:1b.0[A] -> GSI 11 (level, low) -> IRQ 11
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 06:00.0 e159:0001 8086:0003 Communication controller: Tiger Jet
> Network Inc. Tiger3XX Modem/ISDN interface
>
> Modem interrupt assignment and sharing:
> 11: 12 XT-PIC uhci_hcd, uhci_hcd, uhci_hcd
>
> --- Bootup diagnositcs for card in PCI slot 06:00.0 ----
> ACPI: PCI interrupt 0000:06:00.0[A] -> GSI 11 (level, low) -> IRQ 11
>
> Completed candidate modem analyses.
>
> The base of the UDEV device file system is: /dev/.udev.tdb
>
> Versions adequately match for the compiler installed: 3.4.3
> and the compiler used in kernel assembly: 3.4.3
>
>
>
> Compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 3.4
> kernel_headers base folder /lib/modules/2.6.9-5.EL/build
>
>
> Checking pppd properties:
> -r-xr-xr-x 1 root root 251008 Nov 2 2004 /usr/sbin/pppd
>
> In case of an "error 17" "serial loopback" problem, see:
> http://phep2.technion.ac.il/linmodem.../msg02637.html
>
> To enable dialout without Root permission do:
> $ su - root (not for Ubuntu)
> chmod a+x /usr/sbin/pppd
> or under Ubuntu related Linuxes
> chmod a+x /usr/sbin/pppd
>
> Checking settings of: /etc/ppp/options
> lock
> ---------------------end.
> waiting for your replies ,
> i know there are many gurus to help me and get rid of this problem,
> so thanks in advance,
> regards.
Similar Threads
Linear Mode
