[debian-rj] Configuração de modem.

[DPV]

Como vai pessoal??

Acho que alguns de vcs já devem conhecer da minha insistência em tentar
colocar meu debian conectado na net através de um modem dial-up.
Há pouco tempo enviei um email pedindo para alguém indicar um modem para que
meu Debian reconhecesse e ficasse tudo certo! Um infeliz que não sabe a
diferença entre um um winmodem e um linmodem me indicou um winmodem  e como
niguém se manifestou eu acreditei e fui comprar o modem.
Quando perguntei ao mesmo sobre como instalar o modem ele enrolou, enrolou e
tirou o corpo fora.
Fiquei bolado pois só falta a internet no meu Debian p/ eu riscar de uma vez
o Windows do meu HD.

Então lá vai a pergunta... alguém me ajuda a instalar o modem???
Meu PC é um K6 500, placa mãe m598lmr e o modem é um Intel 537EP.  Comprei-o
há pouco tempo.

Instalação do WinModem intel 537EP:
comecei instalando:

kerne-headers-2.6.8-2
kerne-headers-2.6.8-2-i386
kernel-kbuild-2.6-3
kernel-source-2.6.8
gcc

segui os seguintes passos:

#tar -xvzf intel-537ep-2.60.80.1.tgz
#cd intel-537ep-2.60.80.1 # (o diretório q ele criou foi + ou - isso)
#make clean
#make 537

até aí tudo legal... depois :

#insmod -f Intel537.ko

depois segui os passos que estavam no readme:


   0.  log in as root
   1.  insmod -f Intel537.o    (Intel537.ko for kernel 2.6)
   2. you can start "hamregistry &" at this point if you wish.
   3.  rm /dev/537
   4.  mknod /dev/537 c 240 1   (note "240" is the default, if it does

not
       work see what /proc/devices says 537's major number is)
   5.  ln -s /dev/537 /dev/modem
   6.  start a comm application like minicom and use the modem.

quando iniciei um arquivo q estava no diretório , aconteceu o seguinte:

#./config_check

Module precompile check
Current running kernel is : 2.6.8-2-386
/lib/modules... autoconf.h exists
diff: /boot/vmlinuz.autoconf.h: Arquivo ou diretório não encontrado
autoconf.h matches running kernel
diff: /boot/vmlinuz.version.h: Arquivo ou diretório não encontrado
version.h matches running kernel
2.6.8-2-386
(...)

Então, a partir daí não consegui mais fazer nada... Alguém pode por

favor me ajuda???  Como faço p/ saber se está td ok com o driver de um
dispositivo? discadores? intenet??? valeu pessoal pela atenção!!!

E viva ao software livre!!!rsrs ;)
-------------- Próxima Parte ----------
<NOTICE>

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.